Sorry - I hit [tab] then [enter] too quickly after typing the subject and ended up inadvertently posting... My question was regarding xslt 2.0 and if there were any plans to use this for the xml / html generation for the webdash and the emailers. I'd like to be able to use some regex goodness to only pick lines that _begin_ with error / warning. As it stands it will consider those words anywhere in the output.
There are no current plans to include it. We are currently using the default XSL-T engine that comes with the .NET framework, so we would have to look at an external component to handle it.
However if there is enough interest (plus a good OS component) then we can look into it for the 1.6 release.
Craig
________________________________ From: Robin Anderson <whatcouldpossiblygowrong...@hotmail.com> To: ccnet-devel <ccnet-devel@googlegroups.com> Sent: Tue, 26 January, 2010 10:34:48 AM Subject: [ccnet-devel] Re: xslt 2.0
Sorry - I hit [tab] then [enter] too quickly after typing the subject and ended up inadvertently posting... My question was regarding xslt 2.0 and if there were any plans to use this for the xml / html generation for the webdash and the emailers. I'd like to be able to use some regex goodness to only pick lines that _begin_ with error / warning. As it stands it will consider those words anywhere in the output.
FYI, I upgraded our drop of CCNET 1.4.0 at my company to use Saxon which has XSLT 2.0 support, and things went quite smoothly. It would be GREATLY appreciated if somewhere down the line, sooner rather than later, you guys provide said support.
XSLT 1.0 is quite outdated...
-Rashin
On Mon, Jan 25, 2010 at 1:56 PM, Craig Sutherland <cj.sutherl...@xtra.co.nz>wrote:
> There are no current plans to include it. We are currently using the > default XSL-T engine that comes with the .NET framework, so we would have to > look at an external component to handle it.
> However if there is enough interest (plus a good OS component) then we can > look into it for the 1.6 release.
> Craig
> ------------------------------ > *From:* Robin Anderson <whatcouldpossiblygowrong...@hotmail.com> > *To:* ccnet-devel <ccnet-devel@googlegroups.com> > *Sent:* Tue, 26 January, 2010 10:34:48 AM > *Subject:* [ccnet-devel] Re: xslt 2.0
> Sorry - I hit [tab] then [enter] too quickly after typing the subject > and ended up inadvertently posting... > My question was regarding xslt 2.0 and if there were any plans to use > this for the xml / html generation for the webdash and the emailers. > I'd like to be able to use some regex goodness to only pick lines that > _begin_ with error / warning. As it stands it will consider those > words anywhere in the output.
> rob
> On Jan 25, 9:29 pm, Robin Anderson > <whatcouldpossiblygowrong...@hotmail.com> wrote: > > Hi All
> FYI, > I upgraded our drop of CCNET 1.4.0 at my company to use Saxon which has XSLT > 2.0 support, and things went quite smoothly. > It would be GREATLY appreciated if somewhere down the line, sooner rather > than later, you guys provide said support.
> XSLT 1.0 is quite outdated...
> -Rashin
> On Mon, Jan 25, 2010 at 1:56 PM, Craig Sutherland > <cj.sutherl...@xtra.co.nz>wrote:
> > Hi Rob,
> > There are no current plans to include it. We are currently using the > > default XSL-T engine that comes with the .NET framework, so we would have to > > look at an external component to handle it.
> > However if there is enough interest (plus a good OS component) then we can > > look into it for the 1.6 release.
> > Craig
> > ------------------------------ > > *From:* Robin Anderson <whatcouldpossiblygowrong...@hotmail.com> > > *To:* ccnet-devel <ccnet-devel@googlegroups.com> > > *Sent:* Tue, 26 January, 2010 10:34:48 AM > > *Subject:* [ccnet-devel] Re: xslt 2.0
> > Sorry - I hit [tab] then [enter] too quickly after typing the subject > > and ended up inadvertently posting... > > My question was regarding xslt 2.0 and if there were any plans to use > > this for the xml / html generation for the webdash and the emailers. > > I'd like to be able to use some regex goodness to only pick lines that > > _begin_ with error / warning. As it stands it will consider those > > words anywhere in the output.
> > rob
> > On Jan 25, 9:29 pm, Robin Anderson > > <whatcouldpossiblygowrong...@hotmail.com> wrote: > > > Hi All
From that message, I can tell you know much more about XSLT than I do. Can I ask you, is XSLT 2.0 completely backwards compatible with 1.0? In other words, if we upgraded to 2.0, would users with custom XSLTs face any potential breakages from the upgrade?
> FYI, > I upgraded our drop of CCNET 1.4.0 at my company to use Saxon which has > XSLT 2.0 support, and things went quite smoothly. > It would be GREATLY appreciated if somewhere down the line, sooner rather > than later, you guys provide said support.
> XSLT 1.0 is quite outdated...
> -Rashin
> On Mon, Jan 25, 2010 at 1:56 PM, Craig Sutherland < > cj.sutherl...@xtra.co.nz> wrote:
>> Hi Rob,
>> There are no current plans to include it. We are currently using the >> default XSL-T engine that comes with the .NET framework, so we would have to >> look at an external component to handle it.
>> However if there is enough interest (plus a good OS component) then we can >> look into it for the 1.6 release.
>> Craig
>> ------------------------------ >> *From:* Robin Anderson <whatcouldpossiblygowrong...@hotmail.com> >> *To:* ccnet-devel <ccnet-devel@googlegroups.com> >> *Sent:* Tue, 26 January, 2010 10:34:48 AM >> *Subject:* [ccnet-devel] Re: xslt 2.0
>> Sorry - I hit [tab] then [enter] too quickly after typing the subject >> and ended up inadvertently posting... >> My question was regarding xslt 2.0 and if there were any plans to use >> this for the xml / html generation for the webdash and the emailers. >> I'd like to be able to use some regex goodness to only pick lines that >> _begin_ with error / warning. As it stands it will consider those >> words anywhere in the output.
>> rob
>> On Jan 25, 9:29 pm, Robin Anderson >> <whatcouldpossiblygowrong...@hotmail.com> wrote: >> > Hi All
There were some minor incompatibilities with 2-3 of the existing xsl files when I upgraded which I had to correct. I suspect that's because Microsoft's XSL parser isn't entirely standards compliant (what's new), and allowed for some errors in the xsl files to be ignored. I can say though, that we're happy with the upgrade, as we can finally use regular expressions and some other less neat stuff. :)
In response to Robin, I can provide you with the specific changes, though be warned, this is 1.4.0 code (quite old). I will, however, be upgrading to 1.5 soon and port our changes there, if you're willing to wait.
On Mon, Feb 1, 2010 at 8:44 PM, David Cameron <dave...@gmail.com> wrote: > Rashin
> From that message, I can tell you know much more about XSLT than I do. Can > I ask you, is XSLT 2.0 completely backwards compatible with 1.0? In other > words, if we upgraded to 2.0, would users with custom XSLTs face any > potential breakages from the upgrade?
> On 26 January 2010 13:33, Rashin RamazanArab <s2000ma...@gmail.com> wrote:
>> FYI, >> I upgraded our drop of CCNET 1.4.0 at my company to use Saxon which has >> XSLT 2.0 support, and things went quite smoothly. >> It would be GREATLY appreciated if somewhere down the line, sooner rather >> than later, you guys provide said support.
>> XSLT 1.0 is quite outdated...
>> -Rashin
>> On Mon, Jan 25, 2010 at 1:56 PM, Craig Sutherland < >> cj.sutherl...@xtra.co.nz> wrote:
>>> Hi Rob,
>>> There are no current plans to include it. We are currently using the >>> default XSL-T engine that comes with the .NET framework, so we would have to >>> look at an external component to handle it.
>>> However if there is enough interest (plus a good OS component) then we >>> can look into it for the 1.6 release.
>>> Craig
>>> ------------------------------ >>> *From:* Robin Anderson <whatcouldpossiblygowrong...@hotmail.com> >>> *To:* ccnet-devel <ccnet-devel@googlegroups.com> >>> *Sent:* Tue, 26 January, 2010 10:34:48 AM >>> *Subject:* [ccnet-devel] Re: xslt 2.0
>>> Sorry - I hit [tab] then [enter] too quickly after typing the subject >>> and ended up inadvertently posting... >>> My question was regarding xslt 2.0 and if there were any plans to use >>> this for the xml / html generation for the webdash and the emailers. >>> I'd like to be able to use some regex goodness to only pick lines that >>> _begin_ with error / warning. As it stands it will consider those >>> words anywhere in the output.
>>> rob
>>> On Jan 25, 9:29 pm, Robin Anderson >>> <whatcouldpossiblygowrong...@hotmail.com> wrote: >>> > Hi All
Hi Rashin - I can wait - we have a mixture of 1.4 / 1.5 servers here but we'll be upgrading all of them to 1.5 soon. When were you thinking of upgrading ?
thanks rob
On Feb 2, 10:28 pm, Rashin RamazanArab <s2000ma...@gmail.com> wrote:
> There were some minor incompatibilities with 2-3 of the existing xsl files > when I upgraded which I had to correct. > I suspect that's because Microsoft's XSL parser isn't entirely standards > compliant (what's new), and allowed for some errors in the xsl files to be > ignored. > I can say though, that we're happy with the upgrade, as we can finally use > regular expressions and some other less neat stuff. :)
> In response to Robin, I can provide you with the specific changes, though be > warned, this is 1.4.0 code (quite old). > I will, however, be upgrading to 1.5 soon and port our changes there, if > you're willing to wait.
> Cheers.
> -Rashin
> On Mon, Feb 1, 2010 at 8:44 PM, David Cameron <dave...@gmail.com> wrote: > > Rashin
> > From that message, I can tell you know much more about XSLT than I do. Can > > I ask you, is XSLT 2.0 completely backwards compatible with 1.0? In other > > words, if we upgraded to 2.0, would users with custom XSLTs face any > > potential breakages from the upgrade?
> > On 26 January 2010 13:33, Rashin RamazanArab <s2000ma...@gmail.com> wrote:
> >> FYI, > >> I upgraded our drop of CCNET 1.4.0 at my company to use Saxon which has > >> XSLT 2.0 support, and things went quite smoothly. > >> It would be GREATLY appreciated if somewhere down the line, sooner rather > >> than later, you guys provide said support.
> >> XSLT 1.0 is quite outdated...
> >> -Rashin
> >> On Mon, Jan 25, 2010 at 1:56 PM, Craig Sutherland < > >> cj.sutherl...@xtra.co.nz> wrote:
> >>> Hi Rob,
> >>> There are no current plans to include it. We are currently using the > >>> default XSL-T engine that comes with the .NET framework, so we would have to > >>> look at an external component to handle it.
> >>> However if there is enough interest (plus a good OS component) then we > >>> can look into it for the 1.6 release.
> >>> Craig
> >>> ------------------------------ > >>> *From:* Robin Anderson <whatcouldpossiblygowrong...@hotmail.com> > >>> *To:* ccnet-devel <ccnet-devel@googlegroups.com> > >>> *Sent:* Tue, 26 January, 2010 10:34:48 AM > >>> *Subject:* [ccnet-devel] Re: xslt 2.0
> >>> Sorry - I hit [tab] then [enter] too quickly after typing the subject > >>> and ended up inadvertently posting... > >>> My question was regarding xslt 2.0 and if there were any plans to use > >>> this for the xml / html generation for the webdash and the emailers. > >>> I'd like to be able to use some regex goodness to only pick lines that > >>> _begin_ with error / warning. As it stands it will consider those > >>> words anywhere in the output.
> >>> rob
> >>> On Jan 25, 9:29 pm, Robin Anderson > >>> <whatcouldpossiblygowrong...@hotmail.com> wrote: > >>> > Hi All
whatcouldpossiblygowrong...@hotmail.com> wrote: > Hi Rashin - I can wait - we have a mixture of 1.4 / 1.5 servers here > but we'll be upgrading all of them to 1.5 soon. > When were you thinking of upgrading ?
> thanks > rob
> On Feb 2, 10:28 pm, Rashin RamazanArab <s2000ma...@gmail.com> wrote: > > There were some minor incompatibilities with 2-3 of the existing xsl > files > > when I upgraded which I had to correct. > > I suspect that's because Microsoft's XSL parser isn't entirely standards > > compliant (what's new), and allowed for some errors in the xsl files to > be > > ignored. > > I can say though, that we're happy with the upgrade, as we can finally > use > > regular expressions and some other less neat stuff. :)
> > In response to Robin, I can provide you with the specific changes, though > be > > warned, this is 1.4.0 code (quite old). > > I will, however, be upgrading to 1.5 soon and port our changes there, if > > you're willing to wait.
> > Cheers.
> > -Rashin
> > On Mon, Feb 1, 2010 at 8:44 PM, David Cameron <dave...@gmail.com> wrote: > > > Rashin
> > > From that message, I can tell you know much more about XSLT than I do. > Can > > > I ask you, is XSLT 2.0 completely backwards compatible with 1.0? In > other > > > words, if we upgraded to 2.0, would users with custom XSLTs face any > > > potential breakages from the upgrade?
> > > On 26 January 2010 13:33, Rashin RamazanArab <s2000ma...@gmail.com> > wrote:
> > >> FYI, > > >> I upgraded our drop of CCNET 1.4.0 at my company to use Saxon which > has > > >> XSLT 2.0 support, and things went quite smoothly. > > >> It would be GREATLY appreciated if somewhere down the line, sooner > rather > > >> than later, you guys provide said support.
> > >> XSLT 1.0 is quite outdated...
> > >> -Rashin
> > >> On Mon, Jan 25, 2010 at 1:56 PM, Craig Sutherland < > > >> cj.sutherl...@xtra.co.nz> wrote:
> > >>> Hi Rob,
> > >>> There are no current plans to include it. We are currently using the > > >>> default XSL-T engine that comes with the .NET framework, so we would > have to > > >>> look at an external component to handle it.
> > >>> However if there is enough interest (plus a good OS component) then > we > > >>> can look into it for the 1.6 release.
> > >>> Sorry - I hit [tab] then [enter] too quickly after typing the subject > > >>> and ended up inadvertently posting... > > >>> My question was regarding xslt 2.0 and if there were any plans to use > > >>> this for the xml / html generation for the webdash and the emailers. > > >>> I'd like to be able to use some regex goodness to only pick lines > that > > >>> _begin_ with error / warning. As it stands it will consider those > > >>> words anywhere in the output.
> > >>> rob
> > >>> On Jan 25, 9:29 pm, Robin Anderson > > >>> <whatcouldpossiblygowrong...@hotmail.com> wrote: > > >>> > Hi All
|
