No it doesn't do anything magic with the filename extension. And I think less magic is better in general.
The compiler does write '.js' as the extension for compiled apps for the DHTML runtime, and uses .swf for Flash runtime. On 1/16/07, David Temkin <[EMAIL PROTECTED]> wrote:
are you sure that <include href="xyz.js"> isn't implemented already? I thought there was code that noticed the .js and did the right thing. On Jan 16, 2007, at 8:21 AM, Henry Minsky wrote: > There's some code which Pablo wrote for the RPC libraries which > basically just wants to include > straight javascript code, in the same way that the LFC is written. > > He had to wrap these files in <library><script> tags to get them to > work with <include> in LZX. > > I propose an option to <include> which is a "type=script" > attribute. If the tag compiler encounters this, it > will just inline the contents of the included file directly at the > top level, just like LFC code. > > So the library code which declares the <javarpc> class would say, > for example > > javarpc.lzx: > > <library> > > <include href="rpc/rpc.lzx" /> > <include href="rpc/library/javarpc.js" type="script" /> > > And the javarpc.js file is straight javascript. > > > > > > > -- > Henry Minsky > Software Architect > [EMAIL PROTECTED] >
-- Henry Minsky Software Architect [EMAIL PROTECTED]
