On 10/11/12 9:58 AM, Carles Pina wrote: > My *personal* opinion (I'd be happy if someone proves that I'm > wrong!): CSL is so complex and so rich that an editor to create styles > from the scratch without knowing some advanced CSL concepts (macros, > choose, variables, types) cannot be done... or, at least, I don't see > at the moment how can be done. Again, I may be wrong. > > [...] > > Somehow it would be like building a Python/any programming language > user interface. It can be done, but if you want to build things from > the scratch you really need to understand what's underneath... tools > helps, IDEs helps, but doesn't avoid of studying the programming > language.
On this point, I've wondered if it'd make sense in the current editor to optionally expose the underlying XML and highlight the relevant section. (This could be hidden by default.) As someone who's done almost no CSL coding, I can imagine the visual editor being a good way to learn about the structure of CSL files and how the various options translate to code, where I'd ultimately be more comfortable working. I recognize that I'm not exactly in the target demographic and that this is less important than making it easy for non-programmers to make small changes, but if it's easy to do this, I think it could be helpful for some users. ------------------------------------------------------------------------------ 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
