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

unsolicited unsolicited at swiz.ca
Fri Dec 6 16:15:45 EST 2013


Remember, the xml file is being handed to me. It contains what it contains.

<task>
   stuff
   <task>
     subtask stuff
     <task>
       ad infinitum
       <task lots more of these possible>
       </task>
     </task>
   </task>
</task>

There is css in the accompanying .xsl

Remember - the question and goal here was a GUI for taking in .xml, 
.xsd, .xsl, chewing, drawing out, modifying the .xsl, and producing a 
revised xsl.

Fully expect an equivalent, later, running of 'xsltproc my.xml my.xsl -o 
my.html' type of thing.


On 13-12-06 11:11 AM, John Van Ostrand wrote:
> I imagine XLS styles are a lot like CSS styles and if you learn one moving
> to the other is easier. I expect you'll need to use "selectors" to display
> top-level tasks and sub tasks differently.
>
> An alternative to XLS is to use one of the many XML libraries in your
> favourite language. Generally speaking they import the XML into a
> hierarchical structure so you can re-organize it programmatically without
> having to get into parsing the XML text. They can then output the result
> back into HTML for processing later.
>
> However, the easiest way might be to use command line tools and xpath to
> select the elements you want to print and use a stylesheet to print it.
>
>
> On Fri, Dec 6, 2013 at 10:01 AM, Khalid Baheyeldin <kb at 2bits.com> wrote:
>
>>
>> On Dec 6, 2013 12:08 AM, "unsolicited" <unsolicited at swiz.ca> wrote:
>>>
>>> Hmmm. Interesting.
>>>
>>> Longer tool chain, but if scriptable ...
>>>
>>> Schema won't be a problem, .xsd files even provided.
>>> Even if not 100% accurate, schema won't change that
>>> often. Translation could be manually maintained.
>>>
>>> Ah ... hold on ...
>>>
>>> TDL does an infinite nest of sub-tasks. It's not a
>>> straightforward record 1:1
>>>
>>> -+ Task 1
>>> --+ Sub-Task 1.1
>>> ---+ Sub-Task 1.1.1
>>> ---| Some other notes
>>> -+ Task 2
>>> --+ Sub-Task 2.1
>>> ---+ Sub-Task 2.1.1
>>> ...
>>> ----------------------------+ ... ad inifinitum
>>
>> In generzl, such data structure would be implemented in a relational
>> database by having a column called parent task id, and then you can have it
>> point to which task is the parent of the current subtask, and you can have
>> infinite levels. A task without a parent is the top level task.
>>
>> No idea how to implement that with XML import though ...
>>
>> _______________________________________________
>> 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
>




More information about the kwlug-disc mailing list