LzResourceLibrary.lzfocusbracket_topleft_rsrc={frames:["/legals/lps/components/lz/resources/focus/focus_top_lft.png"],width:7.0,height:7.0}
LzResourceLibrary.lzfocusbracket_topleft_shdw_rsrc={frames:["/legals/lps/components/lz/resources/focus/focus_top_lft_shdw.png"],width:9.0,height:9.0}
LzResourceLibrary.lzfocusbracket_topright_rsrc={frames:["/legals/lps/components/lz/resources/focus/focus_top_rt.png"],width:7.0,height:7.0}
LzResourceLibrary.lzfocusbracket_topright_shdw_rsrc={frames:["/legals/lps/components/lz/resources/focus/focus_top_rt_shdw.png"],width:9.0,height:9.0}
LzResourceLibrary.lzfocusbracket_bottomleft_rsrc={frames:["/legals/lps/components/lz/resources/focus/focus_bot_lft.png"],width:7.0,height:7.0}
LzResourceLibrary.lzfocusbracket_bottomleft_shdw_rsrc={frames:["/legals/lps/components/lz/resources/focus/focus_bot_lft_shdw.png"],width:9.0,height:9.0}
LzResourceLibrary.lzfocusbracket_bottomright_rsrc={frames:["/legals/lps/components/lz/resources/focus/focus_bot_rt.png"],width:7.0,height:7.0}
LzResourceLibrary.lzfocusbracket_bottomright_shdw={frames:["/legals/lps/components/lz/resources/focus/focus_bot_rt_shdw.png"],width:9.0,height:9.0}
So how about the server writes out
"lps/components/..." for the resources, then the runtime can add the
"/legals/" if needed. Or maybe that would add too much opportunity for
version skew, and we should write the resources out relative to the
current app working dir. This would make the solo deployment be not so
self contained, but maybe the "external" resources could be packed up
in a separate archive that you could deploy optionally.
On 11/14/06, Max Carlson <[EMAIL PROTECTED]> wrote:
Take a look at a longer resource table, including some components...
-Max
Henry Minsky wrote:
> Well, the resource lib looks like this now, for a view like this
>
> <view resource="logo.gif"/>
>
> The compiler outputs
>
>
LzResourceLibrary.$LZ1={frames:["/legals/test/lfc/logo.gif"],width:178.0,height:124.0}
>
>
> So we could have the compiler write out this without the leading slash, and
> the runtime could have a flag which says whether to interpret the
> paths as relative or absolute.
>
>
>
> On 11/14/06, Henry Minsky <[EMAIL PROTECTED]> wrote:
>> Yeah maybe the compiler should output relative paths only for
>> resources, and the runtime is responsible for turning them into URLs.
>>
>> On 11/14/06, Max Carlson <[EMAIL PROTECTED]> wrote:
>> > You'll need to, if the app is going to be self-contained :(. Also,
>> this
>> > makes it more difficult to share resources across apps...
>> >
>> > Perhaps we can put them in 'lps/includes/resources'? That would mean
>> > you'd replace any leading '../' with 'lps/includes/resources'.
>> >
>> > This could be handled by the runtime. If so, it's another reason for
>> > LzApplicationRoot!
>> >
>> > -Max
>> >
>> >
>> >
>> > Henry Minsky wrote:
>> > > Do you think I should try to rewrite the resource URLs to put them
>> > > into a subdirectory of the SOLO app instead of
>> > > ../../lps/components/lz/blah...?
>> > >
>> > >
>> > >
>> > >
>> > > On 11/14/06, Max Carlson <[EMAIL PROTECTED]> wrote:
>> > >> We will need LzApplicationRoot for other reasons, including
>> loading a
>> > >> static LFC file. Please file a bug to add a client-generated 1x1
>> pixel
>> > >> transparent image - but it's only required for IE6.
>> > >>
>> > >> For SOLO DHTML, you will need:
>> > >> + the LFC and object code for the app
>> > >> + any media resources the app needs (which include component
>> > >> directories). These should all be relative URLs. The resource
>> table
>> > >> for the app has the list of media you need.
>> > >> + lps/includes/blank.gif - Only needed for IE 6
>> > >> + lps/includes/embed-dhtml.js
>> > >>
>> > >> -Max
>> > >>
>> > >> P T Withington wrote:
>> > >> > I know there is a secret 1x1 .gif that is needed.
>> > >> >
>> > >> > I gave LPP-2916: 'Get rid of LzApplicationRoot' to you, because
>> I think
>> > >> > it is relevant to this task.
>> > >> >
>> > >> > On 2006-11-13, at 10:52 EST, Henry Minsky wrote:
>> > >> >
>> > >> >> Can anyone tell me what they think is required for DHTML SOLO
>> deploy?
>> > >> >> That is, what
>> > >> >> auxiliary include files are needed?
>> > >> >>
>> > >> >> Since we serve up the LFC and the app as separate files in
>> DHTML, the
>> > >> >> new SOLO wizard will at least have to write out copies of
>> static files
>> > >> >> for these.
>> > >> >>
>> > >> >> For reference the current swf solo wizard makes
>> > >> >>
>> > >> >> 1) recursive copy of all files in the directory in which the app
>> > >> >> resides, and also includes
>> > >> >> 2) An html wrapper file (app.swf.html)
>> > >> >>
>> > >> >> 3) these include files
>> > >> >> filenames.add("lps/includes/embed.js");
>> > >> >> filenames.add("lps/includes/h.html");
>> > >> >> filenames.add("lps/includes/h.swf");
>> > >> >> filenames.add("lps/includes/vbembed.js");
>> > >> >>
>> > >> >> I will make a master list of what needs to be packaged up, and
>> make
>> > >> >> fork a version of the
>> > >> >> SWF solo deployment tool for DHTML.
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> --Henry Minsky
>> > >> >> Software Architect
>> > >> >> [EMAIL PROTECTED]
>> > >> >
>> > >>
>> > >
>> > >
>> >
>>
>>
>> --
>> Henry Minsky
>> Software Architect
>> [EMAIL PROTECTED]
>>
>
>
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
