NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
XUL and Perl? (Score:1)
Re:XUL and Perl? (Score:1)
Nice... I see it's a rather recent addition to CPAN. This is rather nice, but without proper xpcom support, wouldn't be as extensible. With XPCOM, everything that you can do DOM wise in the browser with javascript you can automatically do with perl, giving you the ability to have:
-Scott McWhirter- | -kungfuftr-
"JAWK - Just Another Whiny Kid"
Re:XUL and Perl? (Score:1)
Window(Label(value => 'Hello World'));
It is just a little Perl sugar over the API you showed.
What can you do in Javascript with XPCOM that you cannot in XUL-Node, which makes it more extensible?
Re:XUL and Perl? (Score:1)
the full DOM API (including most of DOM2), things like dynamically append and reappend element nodes to different locations within the document. XUL::Node allows you to print elements very easily, but it doesn't let you mess about with that document once its been rendered. Some good documentation on this sort of stuff is along the lines of is to have a look at seamonkey's XPCONNECT ability and the python/ruby xpcom bindings.
What would it mean... well say for example you've got a javascript event that fires when you've got a dropdown box that would populate a text field. Using XPCOM, you can get javascript to call a perl method that will return text based on the option you've selected, etc. Has a heck of a lot of nice stuff...
-Scott McWhirter- | -kungfuftr-
"JAWK - Just Another Whiny Kid"
Reply to This
Parent
Re:XUL and Perl? (Score:1)
> append and reappend element nodes to different locations within the
> document
Next version will have support for disposal of nodes, and re-parenting.
Very easy to add.
> XUL::Node allows you to print elements very easily
Yes it allows you add nodes to the document very easily.
> but it doesn't let you mess about with that document once its been
> rendered.
You mean re-parenting and disposal?
Or do you mean calling attribut
Re:XUL and Perl? (Score:1)
I suppose what i mean is, that XUL::Node is very dependant on their being an external engine which does lots of different bits and bobs. There's also this issue that you're using 2 extra layers (HTTP+JavaScript) which means that it's more prone to error.
We've been doing something similar my current employer, but more on a HTML basis as posed to an XUL one and there are quite a few limitations to the RPC mechanism... for example:
How do you make the software interact with external devices such as barcode
-Scott McWhirter- | -kungfuftr-
"JAWK - Just Another Whiny Kid"
Re:XUL and Perl? (Score:1)
> being an external engine which does lots of different bits and bobs.
Do you mean the XUL::Node code itself? But if there was a viable Perl-
XPCOM bridge you would be dependant on that. What is the difference?
Anyway, nothing in XUL-Node does lots of anything. It is a very simple
tool.
> There's also this issue that you're using 2 extra layers
> (HTTP+JavaScript) which means that it's more prone to error.
Yes, you can now be hurt