[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Basic program structures in XSLT (was: Re: Data-d

• From: Dave Pawson <dave.pawson@gmail.com>
• To: Rick Jelliffe <rjelliffe@allette.com.au>
• Date: Fri, 9 Dec 2022 09:14:06 +0000

Sorry Rick, I was expanding on your input, not correcting your suggestions,
i.e. suggesting what I needed when first faced with James xslt 1 offering.

regards

On Fri, 9 Dec 2022 at 08:40, Rick Jelliffe <rjelliffe@allette.com.au> wrote:
>
>
>
> On Fri, 9 Dec 2022, 7:06 pm Dave Pawson, <dave.pawson@gmail.com> wrote:
>>
>> Yes, but Rick....
>>
>> On Fri, 9 Dec 2022 at 07:01, Rick Jelliffe <rjelliffe@allette.com.au> wrote:
>> >
>> > Most basic?
>> >
>> > 1. Push versus pull.
>>
>> Not enough? Why? explain these please? What's the impact of wrong choice?
>> When to 'break' this rule (guidance)
>
>
> Pull programming is where you pull in values into a template. Push programming is where the structure of the incoming document determines the templates that are run.
>
>
>> > 2. Event-based programming =  template matching descent default
>>
>> Wozzat?
>>   Template match? Never heard of it.
>>   Descent... of what? Why default? alternatives
>
>
> <xsl:template match="..."
>     <xsl:apply-templates />
>>
>>
>> > 3. XPaths 1.0 location steps, and value-of
>>     What, how does xpath help / cause problems?
>>     How used in this funny 'language'
>>      The real nugget of XSLT, but quite alien to procedural programmers?
>
>
> Yes.
>>
>>
>> > 4. If and choose
>>   Yep, at last, something  most will recognise recognise!
>>   But where is my 'repeat until'?
>
>
> Xsl has if and choose. It does not have repeat until: it uses Xpath for that.
>>
>>
>> > 5. Rearranging and repeating things: variables,  apply-templates/@select, modes
>>      I'd split
>>         Rearranging and repeating things, again quite key (why etc...)
>>    variables? Oh no they're not.
>>        (hope apply templates explained before now)
>>        BIG session on select 'rules'
>>        modes? Another foreign language.
>>
>> >
>> > Not basic: key, function, anything in xpath 2 or 3 but not in xpath 1.
>>
>> +10
>>
>>
>>
>> >
>> > In other words, developers should be trained to first use the distinctive language features before (and instead of) rushing to use generic (I.e. vanilla) functional features.
>>
>> +1
>>
>> Thanks Rick.
>>
>>
>> regards
>>
>>
>>
>> --
>> Dave Pawson
>> XSLT XSL-FO FAQ.
>> Docbook FAQ.



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

• Follow-Ups:
  • Re: Basic program structures in XSLT (was: Re: Data-driven application --> the data is essentially "machine code" to theapplication, right?)
    • From: Thomas Passin <list1@tompassin.net>

• References:
  • Data-driven application --> the data is essentially "machine code" tothe application, right?
    • From: Roger L Costello <costello@mitre.org>
  • Re: Data-driven application --> the data is essentially"machine code" to the application, right?
    • From: Shlomi Fish <shlomif@shlomifish.org>
  • Re: Data-driven application --> the data is essentially"machine code" to the application, right?
    • From: Michael Kay <mike@saxonica.com>
  • Basic program structures in XSLT (was: Re: Data-drivenapplication --> the data is essentially "machine code" to the application,right?)
    • From: "C. M. Sperberg-McQueen" <cmsmcq@blackmesatech.com>
  • Re: Basic program structures in XSLT (was: Re: Data-driven application --> the data is essentially "machine code" to theapplication, right?)
    • From: Ihe Onwuka <ihe.onwuka@gmail.com>
  • Re: Basic program structures in XSLT (was: Re: Data-driven application --> the data is essentially "machine code" to theapplication, right?)
    • From: Rick Jelliffe <rjelliffe@allette.com.au>
  • Re: Basic program structures in XSLT (was: Re: Data-driven application --> the data is essentially "machine code" to theapplication, right?)
    • From: Dave Pawson <dave.pawson@gmail.com>
  • Re: Basic program structures in XSLT (was: Re: Data-driven application --> the data is essentially "machine code" to theapplication, right?)
    • From: Rick Jelliffe <rjelliffe@allette.com.au>