[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

Re: [xsl] getting javascript into an xsl variable

---

---

Dan,

I would be delighted.  The tool is 'Dexter'
http://code.google.com/p/dexter-xsl/  (In the process of moving it to
github).

To use dexter, you created a *well-formed* example of your output
document, ie. HTML with all tags closed, somthing that an XML
processor can groc.  To that document, attributes in the dexter
namespace (dx:each, dx:text, dx:ignore ...) can be added to elements
with XPath expressionx as values.  Using that now-modified example,
use dexter to generate XSLT-1.0 stylesheets.

The documentation has taken some criticism for not being well
laid/thought out.  Contact me off-list if you have any questions.  I
swear, this system is powerful and easy, no matter how poorly the
documentation reflects. Using this tool, I had a developer working
under my direction create a website with dozens of distinct, all using
in-browser XSLT and the developer having no knowledge  of XSLT, even
after the project was completed.

On Wed, May 29, 2013 at 9:33 AM, dan haig <haig@xxxxxxx> wrote:
> Thanks for the responses!
>
> Michael, is your experimental system something you'd care to share?
> I'm willing to take a hatchet to this thing.
>
> Cheers,
> Dan
>
> On Tue, May 28, 2013 at 6:52 PM, Michael Dykman <mdykman@xxxxxxxxx> wrote:
>> I have an experimental system that I and others have built some large
>> applications on.  It outputs XML with XSL processing instructions to
>> be transformed in browser and have found no real limitations in what
>> Javascript I can use.  Anything I have thrown at it, including google
>> ads, google map widgets, heavy-handed jquery usage or obscure widgets,
>> anything that worked in the static context, has continued to work for
>> me via XSLT-1.0 in-browser.
>>
>>
>>
>> On Tue, May 28, 2013 at 6:31 PM, Liam R E Quin <liam@xxxxxx> wrote:
>>> On Tue, 2013-05-28 at 16:32 -0400, Michael Dykman wrote:
>>>>  By the time it has become
>>>> executable as a script node in an HTML document, all memory of XSL
>>>> origins are gone.
>>>
>>> Note also that there are restrictions on what JavaScript can happen in
>>> HTML generated by XSLT in the browser, for reasons that elude me.
>>>
>>> Liam
>>>
>>> --
>>> Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
>>> Pictures from old books: http://fromoldbooks.org/
>>> Ankh: irc.sorcery.net irc.gnome.org freenode/#xml
>>>
>>
>>
>>
>> --
>>  - michael dykman
>>  - mdykman@xxxxxxxxx
>>
>>  May the Source be with you.
>



-- 
 - michael dykman
 - mdykman@xxxxxxxxx

 May the Source be with you.

---