On Thu, Jun 23, 2011 at 2:15 PM, Gary Martin <<a href="mailto:garycmartin@googlemail.com">garycmartin@googlemail.com</a>> wrote: <div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> Hi Sascha, On 20 Jun 2011, at 10:21, Sascha Silbe wrote: > Excerpts from Gary Martin's message of Sun Jun 19 18:20:54 +0200 2011: > >> Just caught up with the 2nd half of last weeks meeting and thought I'd pass along a screenshot of the Labryinth activity toolbar as it includes export icons for both pdf and png objects: >> >> а а<a href="http://wiki.sugarlabs.org/go/File:Labyrinth_Toolbar_1.png" target="_blank">http://wiki.sugarlabs.org/go/File:Labyrinth_Toolbar_1.png</a> > > Interesting. Would you consider that icon good enough for a first > release of Browse with the PDF export feature? I'll happily include any > updated icon later on. I would, but then it's one I generated for Labyrinth so I'm biased ;) Would like someone more +1s (or -1s) as well as this suggests we move forward on this as the import/export visual generic design. I originally went for this three letter extension document design as there are a number of such export file types that may need different icons and have no obvious visual (or as in the pdf case uses a commercial trade mark). I would rather have avoid text use in icons, for localisation issues,</blockquote> <div> Couldn't we used icons badged by a reduced version of the object's icon?а They might appear something like those made for Memorize, here, <a href="http://wiki.sugarlabs.org/go/Design_Team/Toolbar_Catalog#Memorize">http://wiki.sugarlabs.org/go/Design_Team/Toolbar_Catalog#Memorize</a> аааааааааа --Fred </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> but exporting content to specific object formats already would seem to require a user has some deeper level of understanding or instruction. The other option is to have a generic single 'export to journal' icon (like the Keep icon), and then have each supported export format as a text menu item in its palette. This would allow covering any format without need for an icon for each, but is less obvious/discoverable (in the old toolbars export options were sometimes placed in the Keep palette, but not many discovered that for themselves Ц Write activity being general example). One general idea that has been rattling around my head is that on clicking an export icon/menu choice (or even perhaps the Keep if we keep the tool button but correct the implementation so it is a plain duplicate object feature**) should raise the naming dialogue (or it's new replacement if that lands in time). This would give immediate user feedback as to the event and allow them to see/change the Journal name and other details if needed. </blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> ** this can be in addition to Simon's Journal duplicate/copy-to-->.... feature work, > Once we have a nice set of export icons, we should ship them in > sugar-artwork so all activities can use them easily. +1 though that is not backwards compatible, activities would still need to include them in their own bundles for some time to come if they want to support deployments (e.g. 11.2.0 will include the updated toolbars but wouldn't have the extra icons). Regards, --Gary >> Regarding the icon placement, keeping import/export options in the activity secondary toolbar seems like the correct place (same place as Keep). Though I do notice that Walter (in Turtle Blocks) decided to make a new Journal like toolbar (need to chat to Walter about the motivation behind this choice). > > OK, in the activity toolbar it stays then. > > Sascha > > -- > <a href="http://sascha.silbe.org/" target="_blank">http://sascha.silbe.org/</a> > <a href="http://www.infra-silbe.de/" target="_blank">http://www.infra-silbe.de/</a> </blockquote></div>