Tuesday, May 1, 2007

OpenLaszlo and PHP

I successfully integrated OpenLaszlo with Code Igniter tonight. I'm pretty happy. The solution is stupidly simple, yet I had to search for it. Simply run OpenLaszlo, then do a local proxy-request for certain URLS. Now, when I call for http://myserver.com/lzx/somefile.lzx, it throws me http://localhost:8080/lps-4.0.0/lzx/somefile.lzx, which causes the LZX file to be compiled (or drawn from the cache) and served up. In code, I just dump the request to http://myserver.com/lzx/somefile.lzx using file_get_contents (or curl, if you please), so I can maintain my pretty URLs (i.e., no one ever has to request an LZX file directly).

Pretty effing slick. Now, what to do with it?

The part I hate most about web-application development is creating beautiful administrative interfaces. Yes, I like them. Yes, I think they are great. The problem is I suck at it. So if I can pass OpenLaszlo my list of required fields and data URLS and have it generate a usable interface for me, more power to it.

Too bad OpenLaszlo is such a beast to run. Moreover, it's too bad I'm on shared hosting and can't run it. Guess that means I'm limited to playing around on my local machine.

Santa, for Christmas, please buy me five years of dedicated hosting. Or two. I'd even settle for one. Thank you, Santa.

posted by Mason Browne @ 2:44 AM   2 Comments  

2 Comments:

At May 1, 2007 5:53 AM , Raju said...

No problem if you don't have a Tomcat server running or your root server running. Just compile the LZX program into an SWF file (or JavaScript for DHTML), embedd the SWF into a web page. Upload the files to your web space and it works. Lot's of professional OpenLaszlo applications run SOLO deployed (without the OpenLaszlo server running).

There's a description of the process in the Developers Guide. If you have any questions, get back to us in the mailing lists and forums.
Regards,
Raju
OpenLaszlo Community Evangelist

 
At May 1, 2007 12:53 PM , Mason Browne said...

I was under the impression that certain functions weren't available under SOLO deployment, and that if I wanted these functions, I'd have to write my own proxy functions.

Thanks for your comment!

 

Post a Comment

<< Home