Some preliminary suggestions/questions:
- are there plans to hook the editor up to GitHub? I'm wondering if it
would be a good idea to make it possible for users to click a button, write
a description of the changes they've made, and have the editor handle the
creation of a pull request. (my concern is that obviously somebody would
have to moderate all those pull requests)
- elements such as cs:text have a long list of possible attributes. I think
it would be clearer to group these in the bottom-right frame in a group of
active attributes at the top, and inactive attributes at the bottom.
- it would be nice to have tooltips for all the attributes. It might be
possible to pull these from the CSL schema, since it contains annotations
for most of them.
- many attributes are mutually exclusive (e.g. "macro", "term", "value",
and "variable" on cs:text). Maybe these attributes should be presented in a
dropdown menu?
- it might be helpful to provide a bit more information on the nodes in the
tree, and list the most important node information. E.g. "Text (variable:
"page")" instead of just "Text"
Rintze
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
