On Thu, Jan 19, 2012 at 12:47 PM, Sebastian Karcher <
[email protected]> wrote:
> What that means is that essentially GUIfying the CSL logic is very
> likely going to lead to a bunch of poorly coded styles, even if the
> editor algorithm behind the GUI is good.
>
Let me echo Sebastian's and Bruce's sentiments. I also think that coding
high-quality styles with a GUI CSL editor that supports the full scope of
CSL is unlikely to be that much easier than hand-editing XML. Some
strengths of CSL (conditionals, macros, groups) are difficult to implement
without visualizing the hierarchical structure of styles, and properly
using these features takes a bit of know-how. So I strongly support Bruce's
advice of taking a bit of distance and identifying the best way(s) to solve
the problem.
Furthermore, I think that a tool that takes in formatted bibliographies and
finds matching styles is relatively low-hanging fruit. Such a tool would
make it easier for users and style coders to identify styles that already
give output close to what's needed, and can already be used without a
full-blown CSL editor.
Rintze
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
xbiblio-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
