On Thu, Jan 19, 2012 at 3:49 PM, Charles Parnot <[email protected]> wrote:
> I also agree with the overall sentiment that sticking too close to the XML > specs of CSL will not lead to a very useful tool. It would clearly be nice to > be able to magically create a CSL style from analyzing an existing > bibliography, and it looks like it could work quite well, which I am > impressed by. But there will also always be the need to refine things more, > so you would still need to provide more user interface elements to edit the > details. Yes, good point here. It's just a question whether you start from the general and move to the particular (the approach we're advocating here), or vice versa (often the first impulse). Bruce > I also like the idea of automatically scanning existing styles for similar > output. This is a great way to either get done before you even started, or to > at least provide a good starting point. > > Charles > > > On Jan 19, 2012, at 12:24 PM, Rintze Zelle wrote: > >> 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 > > -- > Charles Parnot > [email protected] > twitter: @cparnot > http://mekentosj.com > > > > ------------------------------------------------------------------------------ > 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 ------------------------------------------------------------------------------ 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
