Hi, On 11 October 2012 14:27, Rintze Zelle <[email protected]> wrote: > On Thu, Oct 11, 2012 at 6:25 AM, Carles Pina <[email protected]> wrote: >> Some of the tasks were simple changes in CSL styles (other tasks were >> search a CSL style, etc.): >> "23. Edit the style for the Journal of Community Health to put the >> inline citation between parentheses: ( ) instead of square brackets: [ >> ].", " >> "24. Replace the comma between the inline citation numbers with an >> ampersand: &." >> "25. Make the inline citation bold." >> "26. Give the Author names in the bibliography small-caps formatting." > > Do any of these cases require use of the XML tree? I'm wondering if it > wouldn't be clearer to hide it by default, since you're mostly > focusing on facilitating minor edits.
Some months ago I mentioned exactly it in a CSL Editor meeting. Lot of tasks could be done without the left tree. I don't remember the exact discussion but I think that we didn't remove to allow moving nodes (drag and drop on the left tree) and also to allow adding conditionals, nodes. Users needs to use the left tree for these operations. Hiding it by default and having a button to show it would be possible. I don't think that this is a blocker to have the editor in citationstyles.org, but I'm happy that these is being discussed. >>> do I make a date localize?"), and then focus on the CSL XML needed to >>> meet that goal. I like the idea, but it would be a significant >>> undertaking, probably matching or exceeding the specification in size. >> >> it also would require some extra-effort for users who never wrote XML, >> they don't know what is an element/attribute, need to validate the >> styles... > > Yes, but there will always be a class of power users that isn't afraid > of hand-editing XML. Reducing the amount of time these users need to > invest to get familiar with CSL seems worthwhile. I see it more as a > parallel approach to the CSL editor, which is more aimed at casual > users. 100% agree, this would be useful to some users. >> Documentation needs to be done, I agree. > > Where would we host it? The GitHub wiki? > (https://github.com/citation-style-editor/csl-editor/wiki) (Any place is better than no place). It could start there (that would be a good start! and good that we could all edit easily). Having said that... I don't think that this Wiki is very user friendly. It has 400 pixels before the content starts and at the end it has 500 pixels from the end of the content to the bottom of the page. To start writing I'd say that it's a very good place (public, easy to edit). And perhaps the users will not get scared by all the buttons before the content starts. Later on could be moved if we decide it (to blog posts, or something similar to the http://citationstyles.org/downloads/specification.html format, with or without docutils). If someone wants access to the Github repo (I think that to edit the Wiki it's needed) just ask me. Regards, -- Carles Pina | Software Engineer http://www.mendeley.com/profiles/Carles-Pina/ Mendeley Limited | London, UK | www.mendeley.com Registered in England and Wales | Company Number 6419015 ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
