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

Re: [xsl] Replacing = with == and ===

Subject: Re: [xsl] Replacing = with == and ===
From: "L2L 2L emanuelallen@xxxxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 4 Aug 2014 22:13:59 -0000

..... Wow how funny is this....

> everyone seems to expect browser-based technology to be free

... Why you--a wizard(meaning experience developer)-- the one making it?
Wouldn't it be better to get people to do it for free? Isn't that what GitHub
for? You have the source code on sourceforge. sourceforge is not like GitHub
AT ALL. Having it on GitHub would allow multiple people to take interest with
it and help work on it. As stated, this would be a beautiful feature for all
xml native database to have. I say get in contact with them after putting the
source code on GitHub.... I'll get in contact with them for you. I would even
put the source code on GitHub for you, but I'm not qualified for such a
delicate task.... I tried. Please consider this; posting it up on GitHub under
it's own account call xqib, upload the source code--if you want, I could do
the rest of the task, like the introduction, read, etc part-- than if you
want, contact me, and I'll alert all xml native database of this repository.
This will allow all wizard across the world at their leisure, to browsing
through the source code, and pick and choose what part of the code they would
like to contribute to updating and improving.

You make your money on accessory; text editor, xqib libraries, framework.

XQIB is better than google dart language.... And you can use that as a gimmick
to farther people interest in xqib too!

You don't even have to do that, I will!

Please consider posting the source code on GitHub...

As captain American would say:

The choice, is yours!

Thank you for reading.


> On Aug 4, 2014, at 5:13 PM, "Michael Kay mike@xxxxxxxxxxxx"
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Thank you, I'm very well aware of XQIB, and the fact that they were able to
create it was one of the things that spurred me to create Saxon-CE, which
implements XSLT in the browser.
> I think XSLT is much better suited for this purpose than XQuery, for a
number of reasons: the main task is transformation from XML to HTML; and as we
have shown with Saxon-CE the rule-based programming model extends well to
handling user interaction as well as XML processing.
> Nevertheless we have found it hard to find the resources to invest in taking
Saxon-CE forward, so from that point of view Saxon-CE and XQIB suffer the same
problem. The main difficulty from our point of view is that everyone seems to
expect browser-based technology to be free, which makes it hard to find the
money needed to take it forward. A secondary difficulty is that the technology
used by both Saxon-CE and XQIB, namely the GWT Java-to-Javascript
cross-compiler, has technical limitations which mean the size of the product
will always be uncomfortably large. A native Javascript implementation would
get around that difficulty, but it's a very large investment with no promise
of making a return.
> Michael Kay
> Saxonica
> mike@xxxxxxxxxxxx
> +44 (0) 118 946 5893
>> On 4 Aug 2014, at 21:04, L2L 2L emanuelallen@xxxxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>> On Aug 4, 2014, at 3:11 PM, "Michael Kay mike@xxxxxxxxxxxx"
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
>>>> Question:
>>>> Why does it seem xslt is favorite over xQuery?
>>> You might get different answers on a different list.... But I do think
it's true that XSLT continues to have much wider usage than XQuery.
>>> I think the reason for that is primarily that people want to do
transformation (which retains most of the information in a document, but in
different form) rather than query (which extracts small amounts of information
from a document).
>>> Although XQuery is capable of doing transformation, XSLT is better at it
for two reasons:
>>> (a) the built-in rule-based processing model using template rules
>>> (b) the customization capability provided by xsl:import
>>> neither of which have any parallel in XQuery.
>>> XQuery is much better at doing complex joins, but that's not the kind of
processing people are mostly doing.
>>> Michael Kay
>>> Saxonica
>> Thank you for the email.
>> .... I.... If they are using xslt, than it's a large chance, that they are
using xQuery....
>> I just want xqib revive!
>> Look at it:
>> Xqib:
>>  <!DOCTYPE html>
>> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>XQIB: Sample
page</title> <meta charset="UTF-8"/>
>>  </head> <body> <h1>Onclick Event</h1>
>> <input id="myButton" type="button" value="Click me"/>
>>  </body> </html>
>> ----------------------------
>> <!DOCTYPE html> <html xmlns="http://www.w3.org/1999/xhtml"> <head>
<title>XQIB: Sample page</title> <meta charset="UTF-8"/>
>>  </head> <body> <h1>Event Location</h1>
>>  Click on one of the following words:
>> <div id="paragraph1">Foo</div><div id="paragraph2">Bar</div>
>> </body> </html>
>> For more example, please visit this link: http://www.xqib.org/js/
>> ...........
>> Wouldn't this be a great feature for xml native database to have....
>> They can't ignore all of us. We can demand it!
>> Just think of it! You can use the same language to send a large fragment
document to the browser, than let it be hold their in memory, and when a query
is require, you can use xQuery in the browser to query it, avoiding making a
trip to the browser....
>> Don't you see the benefit of having this in the browser through a XML
native database....
>> If you do, please, put your email, name, and a message for this. I will
gladly post/send it to all xml native database that I can reach.
>> XQIB!!!!!!
>> XSL-List info and archive
>> EasyUnsubscribe (by email)
> XSL-List info and archive
> EasyUnsubscribe (by email)

Current Thread