Difference between revisions of "User talk:Wade/Unified Bundles"
m (update link)
m (moved Talk:Unified Bundles to User talk:Wade/Unified Bundles: Archiving this idea until it can be reconstituted as a feature request, if it still makes sense.)
Revision as of 20:44, 19 September 2009
Making FCAs inside other activities
An interesting idea which might be relevant to this proposal is the spawning of FCAs from other activities. The general idea is that I created this killer Etoys app and I want to share it with the world, not as a journal entry but as a activity itself. LFaraone 23:17, 6 April 2009 (UTC)
Yet another scheme of implementing viewers
startup scripts(launchers) could be parts of sugar itself and contain only metadata about viewer activity.
It should mean that sugar all time has the full list of possible launchers. When user starts bundle with launcher mentioned in exec section, launcher will check if proper viewer activity is installed if it doesn't launcher will install it from ASLO, otherwise(for example in case of bad internet connection) distributor should preinstall these activities(anyway this case is only distribution specific).
In that case we have list of stable launchers(since they don't have much code) and in anytime we could download last version of viewer activity from ASLO.
Alsroot 00:40, 7 April 2009 (UTC)
See also Unified Objects
Alsroot 06:14, 8 April 2009 (UTC)
content viewers should get the functionality of being made as slide-shows. For example, inside the jukebox activity, one should be able to add various media files, i.e., a playlist. It would appear in the journal as a jukebox activity. The same with image viewer, creating slideshows of images. Just some thoughts on the idea that launching new viewer activities, and these viewer activities could be usefull. HoboPrimate 19:27, 10 April 2009 (UTC)
Just open Browse!
A dedicated "Web Content Viewer" makes little sense. Just pass the file:/// URL to existing machinery to open a URL (thus opening up Browse) and declare victory!
I don't see much benefit to opening web content in something that's sort of like Browse but isn't. Look at the 8.2.0 Help activity, the moment you follow an external URL you might as well be running Browse instead of the same code in a different skin.
Any changes to Browse (like remembering your current location, annotating books, etc.) seem best handled by an extension, like the existing eReader one.
-- Skierpage 02:45, 10 August 2009 (UTC)
Mozilla can open compressed files, including bundles
BTW, one trick of Mozilla code is that it can open compressed files using the jar: protocol;
Thus the activity.info can tell Browse to open the URL jar:file:///home/olpc/Activities/SomeBrowserStuff.xo!/content/index.html and you need never unpack the ZIP file, browsing the HTML just works. I've verified this with the Net Bible collection, I believe it's true for other collections. -- Skierpage 02:45, 10 August 2009 (UTC)