Here is the latest version of the solo deployer - it works in the Legals
top-of-tree branch, I'm pretty
sure it will work in 4.0b1 but haven't tested yet.
The way the compiler works now for DHTML, it writes out the full pathname of
all the image assets,
and if they come from a directory which is a parent of the application
directory, they are tagged as
"server relative" (as opposed to "application relative"). This is to make it
easier to share common assets,
such as the components artwork, among multiple SOLO apps.
In the compiled javascript, the resources end up declared like this
LzResourceLibrary.lzfocusbracket_topleft_rsrc={ptype:
"sr",frames:["lps/components/lz/resources/focus/focus_top_lft.png"],width:7,height:7}
The SOLO DHTML deployer finds all of these references and copies the files
into a subdirectory named lps/resources/... in the zip file.
To get the runtime to look at this directory instead of an absolute path,
you need to change this line in the
.lzx.html file that it writes, to make the lzOptions.ServerRoot point to a
relative ("lps/resources") path prefix rather than absolute path on the
server:
</script><script type="text/javascript">
lzOptions = { ServerRoot: 'lps/resources', splashhtml: '<img
src="lps/includes/spinner.gif">', appendDivID: 'lzdhtmlappdiv'};
</script>
I'm going to modify the deployer script to set this by default, since it
seems like the common case is someone
deploying a single app, or else wanting the app to be totally self contained
with all the assets.
On 1/2/07, DL <[EMAIL PROTECTED]> wrote:
On 2 Jan 2007 at 13:18, Henry Minsky wrote:
> Also, which unzip utility are you using? I was having trouble with
the
> unzip program from InfoZip, on Linux, it was not reproducing the
> directory hierarchy properly, it was substituting "_" for "/" path
> separators in pathnames.
I use Total Commander from *http://www.ghisler.com*
<http://www.ghisler.com> .. but Windows only.
DL
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
