2009/11/27 Aleksey Lim <alsr...@member.fsf.org>: > On Fri, Nov 27, 2009 at 06:13:55AM +0000, Aleksey Lim wrote: >> Hi all, >> >> Want to know what people think about Journal Plugins feature[1] >> and particularly that design team think about UI changes[2] involved >> in this feature. >> >> [1] http://wiki.sugarlabs.org/go/Features/Journal_Plugins# >> [2] http://wiki.sugarlabs.org/go/Features/Journal_Plugins#UI_changes > > I tweaked "Benefit to Sugar" section a bit > > * browsing different types of sugar object looks the same in many cases > (search, tagging etc.). So, keep unified code base and do not split it could > be useful idea. > * for now, some activities have similar functionality(browsing Journal > entries), so having plugins, we will use the same theme for browsing features > in sugar > * encourage developers create new view for different purposes(books, media > etc.) > * having plugins we don't stick to sugar releases, deployers could > create/change plugins that support not only last sugar but version which is > in deployment > * having bookmarks, users can have fast access to his books/media-files/etc > in the Journal(and using proper view plugin to browse them) > * shared bookmarks is more powerful and useful method of network sharing(in > comparing with "Send to" option)
Can anyway relate these benefits from actual requests from deployments? I think this is something that would be good to do in Sugar at some point, but I'm not convinced we are yet in the best moment for that. Regards, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
