[Metadata GUI] Discussion about improvements
As some of you know I'm working on improving attribution and license features in Inkscape. I've the basic functionality for the backend (modifications in the XML structure) done and have focused on learning Gtkmm the last week. I wanted to show a mockup with Gtk but I was not able to finish it today so I made a drawing of how I want it to be so the discussion can get started. Any suggestions are welcome.
### Current functionality Metadata GUI consist of two "pages" in the document properties tab/notebook view, "Metadata" and "License".
### Limitations Only one entry can be modified from the GUI. With addition of extra metadata elements as child elements for different SVG-elements there must be a way to modify multiple metadata tags.
### Goals Main goal is to give the user an overview of all the metadata included in the document open i Inkscape.
### Discussion In the attached image I've the basic structure on how I envision this GUI could look like. To the left a list view of all metadata elements available, similiar to the XML editor. The right pane include all the settings [1].
The right pane has at the top a preview "image" of the part affected with the current license/attribution information. So in the image I have made a collage of a "car" and a "sun". In the image I've selected the metadata element for the car so only the car is visible in this preview image. This makes it easier for the user to understand which part of an image is affected by the current attribution and license information.
As this GUI is very heavy on forms it's hard to copy and paste the information between different objects and could be very cumbersome. Therefore I have added the two options "Copy" and "Append/Paste". This would copy the entire object's metadata to the clipboard and be available to append/paste in another object (instead of copy-pasting ~15 different fields one at a time).
License information can be moved to a dropdown/EntryCompletion option instead of a separate notebook tab. (License would also need one Entry field for the URI that is not in the image).
Any comments, ideas or thoughts about this are appreciated.
[1] In the image I've only drawn "title" and "Creator" but the real thing would include all options available now from the "Metadata" and "License" tabs.
Regards
Creator is one of several fields. As mentioned in the first post but perhaps not very clearly is that "title" and "creator" is only two of several Dublin Core Entities just as it is today. The right pane will probably require a scrolled window to fit the entire form already available today.
Below is the definition of "Creator" in this case. http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=elements#terms-crea...
Ok, the image didn't attract so much attention. Here is a video about it, hopefully this gives you a better picture on how I envision it. Any feedback is appreciated before I start making changes in Inkscape.
http://www.youtube.com/watch?v=aFs_7ZPpuDA
On Thu, 2013-07-11 at 10:04 +0200, Christoffer Holmstedt wrote:
Ok, the image didn't attract so much attention. Here is a video about it, hopefully this gives you a better picture on how I envision it. Any feedback is appreciated before I start making changes in Inkscape.
Great video, I hope I've started a trend of making videos :-D
The only design comment is the negative space to the left and right of the preview image. If the target dialog is full-screen, then the design might want to push a few of the input lines up. OTOH if it's going to be a side panel those spaces might just disappear anyway.
Martin,
It might make sense to make it a bit more compact, as well as more extensible. For example, rather than having a fixed list of properties, it might make more sense to have a kind of "table", where the first column is the property name and the second column the value. The property name could be selected from a list of possible options (from Dublin Core for example), perhaps including an option to specify a custom property. I'm thinking of something not unlike what is used by many e-mail applications for specifying the list of recipients.
Also, I would be interested in seeing some of the most important data figure more prominently in the GUI. Perhaps the license (for the complete file) could be shown somewhere for example (in abbreviated form). Also, the title and possibly the creator could be shown more prominently (in the title bar for example).
On 11-07-13 10:04, Christoffer Holmstedt wrote:
Ok, the image didn't attract so much attention. Here is a video about it, hopefully this gives you a better picture on how I envision it. Any feedback is appreciated before I start making changes in Inkscape.
http://www.youtube.com/watch?v=aFs_7ZPpuDA
-- Christoffer Holmstedt
2013/7/8 Christoffer Holmstedt <christoffer.holmstedt@...400... mailto:christoffer.holmstedt@...400...>
Creator is one of several fields. As mentioned in the first post but perhaps not very clearly is that "title" and "creator" is only two of several Dublin Core Entities just as it is today. The right pane will probably require a scrolled window to fit the entire form already available today. Below is the definition of "Creator" in this case. http://dublincore.org/documents/2012/06/14/dcmi-terms/?v=elements#terms-creator -- Christoffer Holmstedt 2013/7/8 Martin Owens <doctormo@...400... <mailto:doctormo@...400...>> On Mon, 2013-07-08 at 16:34 +0200, Christoffer Holmstedt wrote: > License information Should the box say Creator or Owner? Because a creator may not own the copyright on a work. Martin,
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clk...
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Great comments!
@Martin Owens Yes, videos are awesome =) The current layout is done with a table (grid for gtkmm3.0?), so no rows should jump up in the table as far as I know, only tested with table so far ;)
@Jasper van de Gronde Concerning a more extensible table with property:value and include list of possible options (the vocabulary from dublin core). This is actually the solution we have been discussing in "commons machinery" for next iteration so really happy that you see it as a good solution as well.
Concerning your second comment. I can try to add some kind of infobar at the top or bottom that will show a short list of all the information that is for the entire document. The problem I can see with this is that it might be hard to actually figure out which information is for the document and for the selected object.
participants (3)
-
Christoffer Holmstedt -
Jasper van de Gronde -
Martin Owens