Thanks for looking - I did look at 2 of the below but they seem to be server side rather than for a standalone app.
Also scant documentation, would also be good to hear from someone who has trod this path...
Re^2: Perl and XUL app
Replies are listed 'Best First'.
What is a "standalone app", exactly? What is a "server"? Could you not think of a GUI app as having server and client components? GUI apps generally have a main loop and serve up responses to requests ("events", which are special kinds of requests).
Well I've only looked at the docs for XUL::Node, but from what I read there, XUL apps run in a web browser (i.e. Firefox) and for this particular distro, it makes use of XMLHttpRequest invocation calls (or something similar) to respond to user interaction. That's what this module comes in: taking care of responding to those XMLHttpRequest invocations. That is what makes it "server side".
I'm not absolutely sure they are real XMLHttpRequest invocations, but if they are: these don't work on file:// URLs. So in that case, local XUL apps are simply impossible.
What I meant was: why couldn't the server be run on the client machine?
For what it's worth, I pretty much gave up on XUL. It seems promising when you read about it at first, but then when I tried to do anything with it it seemed to majorly suck. (Like you're getting at, local resources that you take for granted having access to in any programming language never seem to be easy to deal with.)
Hi - Like any of these terms I guess standalone app could be debated, but in this case I mean an application that doesn't have to go over the web or the network in order to function, and is self-contained to the greatest extent possible (ie. it doesn't kick off lots of other applications in order to function).
Anyway, do you have any advice with regard to using XUL and Perl in this regard?