hi,

a long term goal of many users is to embed their existing SWFs into an
OpenLaszlo Application.
Or the other way tound: To load a compiled OpenLaszlo SWF into ... weather
and existing SWF compiled with Flex or into another OpenLaszlo SWF.

Do you have plans for that kind of extension?
It would be very useful in terms of Modularization to be able to compile and
load Modules at runtime into a Core without the need to have those Modules
all available while you are compiling the Core. So that you can load and
initiate new Classes dynamically at Runtime.
Or just compile a Core Product and ship Modules separated.

I read some posts in the forums about loading a canvas into another but it
does not seem to me that it was a solution to the problem. Does anyone work
or have ideas of that kind of extension?
I think the main Issue here is just that you have to load two canvas tags
into another and have to register classes and assets at runtime. The
*import* tag does something similar. The problem is just => The import tag
still needs to code of the module to be available while you compile the
core. So there is no real advantage in using this Tag compared to an
*include* (if you ignore those Kbits that are loaded at runtime with
import.load() instead of an initial include).

So my idea for a workaround was: Is there a way of cheating the compiler by
:
1) having a tiny container-class that is linked with an *import* tag
2) this gets compiled into the core
3) replace this compiled container-SWF at runtime with the actual module?
the problem would be just that you still need the hole core to compile the
module ... and some mystery if the this is going to work.


Also the other way round is a bummer for users: They see a nice OpenLaszlo
Application and want to integrate it into their existing Flex, Flash
environment, but they can't as the canvas tag is not compatible for loading
it into another SWF.


thanks,
sebastian

-- 
Sebastian Wagner
http://www.webbase-design.de
http://openmeetings.googlecode.com
http://www.laszlo-forum.de
[email protected]

Reply via email to