Can you explain how wrapping a C/C# DOM implementation and using that from
Perl is in conflict with using Perl's regex engine?
John
On Thu, 23 Nov 2006, Christopher Hart wrote:
For one particular application, I need the speed of Perl's regex engine and
I have not been able to match it in C#
Well, maybe it isn't in conflict, but I failed to mention another
requirement - the application that I'm referring to also has to run on
Linux. Perhaps that still doesn't represent a problem - could Mono be
workable? I haven't worked with it enough to know.
On 11/24/06, John J Lee <[EMAIL PROTE
For one particular application, I need the speed of Perl's regex engine and
I have not been able to match it in C# or even with limited attempts using
C++ and Boost's regex library. So, regardless of feature availability on
other platforms, I'm going to continue pursuing DOM & JS functionality in
On Wed, 22 Nov 2006, Christopher Hart wrote:
Would an "easier" (yet still monumental) starting point be to tackle the DOM
implementation independent of a JS engine?
[...]
This seems like a great open source project - it's way too much to handle
for most individual developers, but I think could
On Wed, 22 Nov 2006, Christopher Hart wrote:
I agree that folks have been talking about JS for a long time, and that it's
frustrating, but what I'm suggesting is that we need to tackle a different
problem first.
[...]
An HTML DOM implemention is a necessary part of JS support, sure (though
St
On Wed, 22 Nov 2006, Christopher Hart wrote:
I'm willing to take a crack at laying out a vision, high level objectives
and some implementation requirements based on my experiences and see how
[...]
Everyone who's seriously interested is willing to do that. Indeed, many
have surely done that
On Wed, 22 Nov 2006, apv wrote:
I've also been interested for a long time and tried to work on
this 2 years ago but didn't get far enough to bother trying
to release anything.
[...]
I would gladly throw down if there was a group effort with a
real plan. I'm not the right hacker to lead this pr
2006 2:35 PM
To: Stefan Seifert
Cc: libwww@perl.org
Subject: Re: State of the AJAX Union
On Wed, 22 Nov 2006, Stefan Seifert wrote:
[...]
> I too thought about that. Maybe using the JavaScript or
> JavaScript::Spidermonkey module and XML::DOM. I will certainly
> experiment around with th
I've also been interested for a long time and tried to work on
this 2 years ago but didn't get far enough to bother trying
to release anything.
DOM could be tackled in an HTML::Tree-->XML::"parser" fashion.
That way, bad mark-up could be legitimized and something like
XML::LibXML could handle the
I'm willing to take a crack at laying out a vision, high level objectives
and some implementation requirements based on my experiences and see how
much interest there is for a group effort if others are interested in
helping out. I'm sure I'll miss a lot that others with different
experiences cou
I agree that folks have been talking about JS for a long time, and that it's
frustrating, but what I'm suggesting is that we need to tackle a different
problem first.
This isn't an academic question - without knowing how the DOM is going to
work (or even if there is one), the JS conversation can'
On Nov 22, 2006, at 2:51 PM, Christopher Hart wrote:
Would an "easier" (yet still monumental) starting point be to
tackle the DOM
implementation independent of a JS engine?
All of this is pointless unless someone is willing to step up and
JFDI. Otherwise, it's just rehashing the same the
Would an "easier" (yet still monumental) starting point be to tackle the DOM
implementation independent of a JS engine?
It seems like attempting to create any kind of a JavaScript framework
implementation would be pretty useless (and horribly incomplete) without the
DOM being present first. An i
On Wed, 22 Nov 2006, Stefan Seifert wrote:
[...]
I too thought about that. Maybe using the JavaScript or
JavaScript::Spidermonkey module and XML::DOM. I will certainly
experiment around with them, as we need it at work. Doesn't seem to be
Sigh, we've had this same little discussion at least fiv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John J Lee wrote:
> On Fri, 3 Nov 2006, Christopher Hart wrote:
>
>> I know there is a rich history of challenges implementing any kind of
>> JavaScript interpretation using Mechanize or any other web
>> scripting/automation utility, but I was wonderi
On Fri, 3 Nov 2006, Christopher Hart wrote:
I know there is a rich history of challenges implementing any kind of
JavaScript interpretation using Mechanize or any other web
scripting/automation utility, but I was wondering if anyone has tried to
focus on "Mechanizing" AJAX?
I realize this would
16 matches
Mail list logo
