[kwlug-disc] XML / XSL / XSD/ XSLT 'development' 'environment' / 'gui'?

[jvj at golden.net]

 To add to my earlier comments, I was speaking from a bit of personal 
 experience as I did some work in PERL a few years ago. (And AWK a couple 
 of decades ago.)

 While the work in PERL was not in XML it was, in a broad sense similar, 
 as the data had a hierarchy.

 In my life as an electrical designer I had a schematic diagram of a 
 design and a prited circuit board layout. And after the inital 
 generation, and for many reasons, there were changes.

 For obvious reasons, it was necessary that the schematic and the PCB 
 layout matched. The mechanisms to do this in tools did not always work. 
 (For those in the know: backannotation.)

 The tools, however, generated netlist files, text that described the 
 connections between components.
 And again the tools had shortcomings in that, even though I chose the 
 same netlists formats in both of the tools, the output was different.

 Enter PERL (and a few 10s of hours of work).

 Enter the VIM editor and the text file compare feature.

 After a few visits to the tools to correct the designs and cycles with 
 the netlists, PERL and VIM, the schematic and the pcb layout macthed. 
 And the product shipped.

 AWK: Translator of 6502 machine code listings pulled from ROM to 
 assembly w/o comments to C.

 John Johnson


 On Thu, 05 Dec 2013 08:05:56 -0500, <jvj at golden.net> wrote:
> I hesitate to suggest that your solution may be DIY.
> Tools such as AWK (dated) and PERL (current) can be used to process
> text files such as XML.
> As always, depending on the scope and complexity the work can be 
> tedious.
>
> Regards
> John
>
> On Wed, 04 Dec 2013 23:58:09 -0500, unsolicited <unsolicited at swiz.ca> 
> wrote:
>> None of this is optional. It is take in xml files, create an .xsl
>> that templates the xml database into a report.
>>
>> On 13-12-04 05:04 PM, Khalid Baheyeldin wrote:
>>> My advice is: if you can avoid development that has non trivial 
>>> amount of
>>> XML, then do so, and preserve your sanity, and hair.
>>> On Dec 4, 2013 4:32 PM, "unsolicited" <unsolicited at swiz.ca> wrote:
>>>
>>>> I know zero of xml. Lots of other languages, but haven't needed 
>>>> this until
>>>> now. No development experience in a Linux environment, well, bash
>>>> scripting. Never really made it to GUI's, either, for that matter.
>>>>
>>>> I'm using AbstractSpoon's ToDoList (http://www.abstractspoon.com/
>>>> tdl_resources.html) - one of the only todolists / tools I know of 
>>>> out
>>>> there that does (infinite) subtasks. Runs under wine. (At least 
>>>> mostly.)
>>>>
>>>> It stores its lists in xml (.tdl files), has provided schema 
>>>> (.xsd) files,
>>>> a number of stylesheets (.xsl), and will allow one to execute the 
>>>> transform
>>>> and produce an output file, e.g. .html.
>>>>
>>>> Printing is -definitely- not its strong suit, as its developer 
>>>> will admit.
>>>>
>>>> I'm looking for something that will let me pull all these files 
>>>> together,
>>>> .xsd, .xml, .xsl, let me beat up on the .xsl into a revised .xsl 
>>>> (in
>>>> essence a report template), and output that .xsl out again. For 
>>>> TDL to then
>>>> use for printing.
>>>>
>>>> I've seen that xsltproc is out there (msxsl 'equivalent'?), but 
>>>> that is a
>>>> 'filter' / pipe, not a 'development' tool. Well, other than edit a 
>>>> file,
>>>> feed xsltproc a schema and xml data file to produce an html file, 
>>>> see
>>>> what's wrong, edit a source file, repeat.
>>>>
>>>> What's out there / what am I looking for that's useful for doing 
>>>> this
>>>> easier? At least list for me the data dictionary rather than 
>>>> visually
>>>> deciphering it by studying the .xsd. Preferably slicking up the 
>>>> 'these
>>>> inputs', 'transform', 'produces these outputs' iterations.
>>>>
>>>> I guess I'm looking for an 'xml report writer'. Is there such a 
>>>> beastie?
>>>>
>>>> I've heard of iReport and 'xml notepad 2007' but know nothing of 
>>>> them.
>>>> Both are windows software.
>>>>
>>>> Not real sure what to call what I'm looking for to know what I'm 
>>>> looking
>>>> for - suggestions welcome.
>>>>
>>>>
>>>> _______________________________________________
>>>> kwlug-disc mailing list
>>>> kwlug-disc at kwlug.org
>>>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> kwlug-disc mailing list
>>> kwlug-disc at kwlug.org
>>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org
>>>
>>
>>
>> _______________________________________________
>> kwlug-disc mailing list
>> kwlug-disc at kwlug.org
>> http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org