[Sugar-devel] A Better ASLO

[Sam Parkinson]

Hi Sebastian,

It would be cool to integrate sugar network with the ASLO. I would love to
use your sign on system alongside persona. I would also like to see what
you think of the reviews. They are just text and stars, but the developers
can reply via email.

Would there be a way maybe to do a "usage showcase" using data from sugar
network?


------ Basically ------

I would really like to use your review system. This could be awesome!

School is going back tomorrow, so I won't be able to work fast :(

Sam


BTW: check out our github: https://github.com/SAMdroid-apps/aslo/ and a
hosted copy without the reviews: http://people.sugarlabs.org/~sam/aslo/web/


On Sun, Apr 27, 2014 at 4:57 PM, Sebastian Silva
<sebastian at fuentelibre.org>wrote:

> I think it might be relevant to point out we've already discussed some of
> these issues and even the implementation is alive in current Sugar Network
> effort.
>
> Discussion about .xo limitations and dependency resolve feature:
> http://lists.sugarlabs.org/archive/sugar-devel/2009-December/021522.html
> packagekit-backend-presolve:
> http://wiki.sugarlabs.org/go/Platform_Team/packagekit-backend-presolve
>
> Also I think relevant for the subject of "New ASLO" is the Sugar Network
> API.
> It exposes ASLO's data and provides a user feedback layer (comments and
> such).
> It's designed to stay in sync with ASLO or in effect be the backend of a
> "New ASLO" effort.
> http://wiki.sugarlabs.org/go/Sugar_Network/API
> List of activities
> http://node.sugarlabs.org/context?type=activity&offset=0&limit=50
> Be sure to see the object model and maybe check out the webui at
> http://network.sugarlabs.org/
>
> Sorry for sharing so many links. I hope we can push together in the same
> direction as I see we are moved by the same goals.
>
> Alsroot is the developer of the Sugar Network node, so I'm adding him on
> cc:
>
> Regards,
> Sebastian
>
>
> El sáb, 26 de abr 2014 a las 10:03 AM, Walter Bender <
> walter.bender at gmail.com> escribió:
>
> On Fri, Apr 25, 2014 at 11:52 PM, Jerry Vonau <me at jvonau.ca> wrote:
>
>  On April 25, 2014 at 8:54 PM Sam Parkinson <sam.parkinson3 at gmail.com>
> wrote: On Apr 19, 2014 11:16 PM, "Tony Anderson" <tony at olenepal.org>
> wrote: > > Hi, > > Sorry I can't submit this to the lists - my internet
> provider doesn't allow > sending to my email provider (sigh). > > There is
> an apparent policy to support the Sugar Activities distributed > with
> builds 21 and 13 although not on ASLO. Walter has provided links > to > a
> version of TuxMath which works on the current builds, but this has > not,
> so > far as I know been posted on ASLO. OK, I might not be on the same
> page, but are you talking about activities with different builds for
> different sugar versions?
>
> Think what Tony is referring to above are the versions of TuxMath &
> TuxPaint that are used in AU but require the underlying rpms to be present
> before the activity is usable. This would preclude the use in ASLO as all
> the dependencies may not be present in the OS and are not provided in the
> activity. To have these newer versions effective in ASLO sugar would need a
> way to install the needed underlying libraries(as rpms) but there is
> presently no way of doing this automatically right now and there looks to
> be no effort to add this support(1).
>
> If someone is willing to work on this problem, I am confident it would be
> accepted upstream. -walter
>
>  > I would really like to see the limited available resources devoted to >
> verifying which activities in ASLO work on build 21 (at least for XO-1) and
> > on build 13 (and on which XO (1.5, 1.75, and 4). ASLO gets the
> compatibility for each bundle by reading through the code. We currently
> classify by: * web activity * gtk3 * new/old toolbars [Suggestions
> welcome!] > If necessary, ASLO should > provide for multiple bundles where
> it takes a different bundle > depending on > the build or XO model.
> Providing a 'most recent version compatible with sugar XX' sounds like a
> good idea.
>
> You have to take into account those activities which have libraries
> shipped with then, those tend to be architecture(x86_64,i386,ARM) specific.
> The activities mentioned above fall into that category, they used to ship
> with the libraries but in an effort to make the activity cross-arch
> compatible and reduce the size of the download those are not shipped with
> the libraries for all the supported arches, relying on the OS's packaging
> to supply those packages in advance at image creation time.
>
> > While a fix was made for the incompatibility in activity.info, as far >
> as I > know it is not available for either build 21 or build 13 (i.e. to
> the installed > base). It should be a simple matter to update the
> activity.info on the bundles on ASLO to work with the distributed builds.
> I lost you there. BTW: what are these builds in sugar versions? > Tony Sam
>
> Jerry 1. http://bugs.sugarlabs.org/ticket/4623_______________________________________________ Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
> --
> Walter Bender Sugar Labs http://www.sugarlabs.org_______________________________________________ Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140427/9cced1a3/attachment-0001.html>