Talk:ResourceTagging
From Create Wiki
Contents |
How to identify resources
File path
Absolute vs. relative. Relative path is kind of more portable, but on the other hand it is meaningful only for application which knows where it's resource folders are located (no support for external applications). Paths are also useful for user who want to edit tags manually.
Checksum
Which type(s) should be supported? Can there be multiple (in that case there would be a need for attribute)?
Additional content
Perhaps categories such as "brush", "pattern" for each resource would be useful?
Multiple languages
Should translations be provided when resource package is installed (later changed only by user directly)? (Currently done in GIMP). Distribution version is different from what is installed for user. vs. Should tags always have translation information associated so that translation would change when user switches language. Causes some issues as tags can be edited by user. What happens when user deletes/add new tag? What if user "renames" a tag - should it be changed in all resources where the tag was or only in one?
Sharing between applications
If resources are shared between applications, it would make sense to share tags too. Probably would be more difficult if relative paths are used instead of absolute.
Shipping resources with tags
It would be nice to allow shipping resources in a single archive (ie., *.tar.gz) which could be drag-dropped on application so that it would be automatically installed and resources would immediately appear in applications' windows. This should involve packaging tags.xml together with resources. Manifest (list of files) might also be useful, as user might want to "uninstall" what was previously installed.
Common GUI elements
User experience with GUI elements should be similar in all applications.
Order of Items
Shouldn't it be possible for the user to reorder items within a tag? If so, how would this be saved? Maxy 13:55, 31 October 2009 (UTC)
