5,705
edits
Changes
Jump to navigation
Jump to search
Line 64:
Line 64: − + + + +
User:Alsroot/trash/Frame Panels (view source)
Revision as of 11:54, 27 November 2009
, 11:54, 27 November 2009→Benefit to Sugar
* 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.
* 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
* 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
* 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)
== Scope ==
== Scope ==