I don't see why not, we can achieve both things :). Maybe someone have another opinion regarding this?
On Tue, Aug 21, 2012 at 3:07 PM, Bert Freudenberg <[email protected]>wrote: > On 2012-08-21, at 20:17, Martin Abente wrote: > > > The design I implemented works like this: > > > > a. activity developers or deployments add a new "examples" folder inside > the activity bundle with their examples objects. > > b. when the activity starts, the example folder will be accessible > through the journal as new volume option, and also from __any__ > ObjectChooser. > > c. Only one volume button will be shown, even when many instances of the > activity are running. > > d. The example folder will disappear from the journal when the last > instance is closed. > > [...] > > Waiting for more feedback... :) > > And in another thread: > > >> instead of a magic directory name, couldn't the activity.info file > have a new entry giving the examples path? > > > > > What I tried, or I am trying, to do is to make this feature available as > easy as we can, so even deployments could add their own examples with very > little technical knowledge requirements. That why I try this convention > (magical) idea. > > > Okay, so by default it should look for a directory named "examples". But > maybe a different path could be set in activity.info? > > - Bert - > > > _______________________________________________ > Sugar-devel mailing list > [email protected] > http://lists.sugarlabs.org/listinfo/sugar-devel >
_______________________________________________ Sugar-devel mailing list [email protected] http://lists.sugarlabs.org/listinfo/sugar-devel
