Let me fantasize even further...
All laszlo components could be compiled into lzo and and swc and js files.
So unless the user starts deliberately poking around with laszlo's own
components
there would never be a need to compile any of the laszlo specific code.
What is the situation at the moment?
- rami
On 28.6.2011 1:59, Rami Ojares / AMG Oy wrote:
What is the stuff exactly inside an lzo file?
It looks like laszlo tags and javascript.
Why is there a separate version of it for swf10 and dhtml?
(--runtime=swf10,dhtml)
And if it really speeds up the compilation why aren't lps/components
source files compiled into lzo's?
- rami
On 28.6.2011 0:10, Rami Ojares / AMG Oy wrote:
Hi,
I compiled some reusable classes to lzo.
One problem that I quickly realized was that all the links to
laszlo's own classes/files were put inside
the file thus prohibiting the moving of the generated lzo file in
relation to LPS_HOME
Eg.
<include
href='../../../../warehouse/laszlo/openlaszlo-4.7.x-servlet/lps/components/lz/window.lzx'
/>
Normally libraries do not have this kind of restriction.
It is like having to keep jar files in the same place where the
source files were...
Anyway, I started to think if it would be possible to compile swc
files directly instead of lzo files.
They would be closer to the jar concept and would speed up the
compilation even more.
Is that even a reasonable idea?
I mean if I refer to a laszlo class in a source file could laszlo
understand it if it only exists compiled inside a swc?
And if not could this be achieved by keeping both lzo and swc around?
Further does flex compiler include all the swc libraries into the
single resulting swf?
- rami
