[Sugar-devel] Activity updater

Bernie Innocenti bernie at codewiz.org
Thu May 27 12:50:10 EDT 2010


El Sun, 23-05-2010 a las 14:50 -0400, Michael Stone escribió:
> The only purposes of the list comprehension in UpdateModel.check_updates() is
> to set self._bundles_to_check to a list containing the elements returned by
> bundleregistry.get_registry(). This purpose can be more succinctly achieved by
> means of the list() constructor.

I'll test both patches in F11-XO1 and report back.

As your eyes are already looking at this code, perhaps you may like to
help with some work. yesterday dsd and I discussed the possibility to
add back support for the microformat as a backend to the current
activity updater.

The current aslo-specific RDF protocol makes it hard for deployments to
decentralize activity management to schoolservers. It's also very slow
becase it does one HTTP query for each installed activity. Daniel wrote
a list of desired requirements in another post not long ago.

The ASLO-side of microformat support looks really trivial: we just need
edit the html template for the page displaying activity collections.
ASLO lets any registered user create custom collections and grant other
users editing rights to it. The only important feature which is missing
is locking specific versions of activities.

If it's a lot easier, we could restore support for the OLPC microformat
and ditch the RDF protocol altogether. It won't be missed because it
hasn't been used by any large deployment yet.

I'm not sure can import the old code verbatim, though. Besides being
very complex, it adds a dependency on bitfrost. A minimalistic backend
for the current updater would be a lot more maintainable, imho.

-- 
   // Bernie Innocenti - http://codewiz.org/
 \X/  Sugar Labs       - http://sugarlabs.org/



More information about the Sugar-devel mailing list