[Systems] API for activities.sugarlabs.org?

[Pablo Flores]

I agree that 2 seems to be a better solution for integrating our works...

What I don't like of this choice is the impossibility to skin the page. I
think is a very important usability issue.

I don't know if this may sound like a hack for you, but... isn't it possible
to fix ASLO to change the <base href=...> folder depending on the locale, so
different css (or other templates) may be used?

BTW, where's tech info about ASLO and AMO?


Saludos,
Pablo Flores


On Thu, Mar 11, 2010 at 11:09 PM, Bernie Innocenti <bernie at codewiz.org>wrote:

> On Thu, 2010-03-11 at 18:41 -0200, Pablo Flores wrote:
> > Ok. So, putting in black & white we have 2 choices:
>
> > Choice 1: ceibalJAM keeps using its own Activities publishing
> > interface.
> >       * Develop an API so that new activities and updates go
> >         automatically to ASLO
> >       * In this case we don't need a new locale ES_UY, as we can use
> >         our own rating system (disconnected from ASLO or not). We also
> >         wouldn't need a single sign on system.
> > Choice 2: Redirect to ASLO for uploading or updating Activities
> >       * Implement a single sign on system
> >       * Create a locale ES_UY, to filter easily local reviews and
> >         statistics. Would not have the chance to see local rating
> >         averages for activities
> >       * Filter ceibalJAM Activities with a collection
> >       * Would keep sugarlabs look & feel. At most we could add a
> >         ceibalJAM frame at the top
> > Did I miss something important?
>
> Very good summary!
>
>
> > Choice 1 seems to be much easier and intuitive. Anyway, in this moment
> > we are having a big discussion on how to go on and maintain our
> > portal. From this discussion we may define which direction to
> > choose...
>
> I'd slightly prefer to see option (2) happening as it would mean more
> synergy between Sugar Labs and the largest OLPC deployment out there.
>
> However, I see how it would take more effort. Since I lack the means to
> make all requisites of (2) happen, my opinion doesn't matter much. If
> Aleksey, David and someone from ceibalJAM could step forward to do this,
> I think it would benefit us in the long term.
>
> If it looks like there's there risk that we're going to block halfway in
> between, then option (1) would be more logical. The "API" may be as
> simple as one or more HTTP GET or POST pages containing all relevant
> data as form fields [1].
>
> Could ceibalJAM designate a technical person to evaluate the feasibility
> of both options on the actual ASLO codebase? I can provide access to
> aslo development sandboxes if needed.
>
>
> [1] Jorge, my colleague here in Paraguay, asked me for similar
> functionality in order to repackage and upload his activity directly
> from a shell account on sunjammer. This would save him a 35MB upload on
> a low-bandwidth network every time he needs to update the activity.
>
> --
>    // Bernie Innocenti - http://codewiz.org/
>  \X/  Sugar Labs       - http://sugarlabs.org/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/private/systems/attachments/20100312/a9531142/attachment.htm