The size profiler is supposed to also do this, to give you the size
of your app. Perhaps there is code there you can share, or fix to
work for DHTML.
I think you want to make 2 pieces: The LFC + component resources,
which can go in a fixed place and be shared, and the user's app + its
resources, which go in a relative place.
On 2006-11-14, at 22:07 EST, Henry Minsky wrote:
So I'm making a pass at writing a SOLO deploy script for DHTML,
based on the jsp
we have for swf apps.
The question is what to do with the absolute paths that are in the
app's resource table.
I may start by just writing some code which scrapes the list of
resources from the app's compiled javascript,
or else write a new servlet responder which returns the list of
resources for an app as XML or something even more easily machine
readable.
My plan is is to copy all the resources into a subdirectory of the
app's home directory, prefixed with "lps/resources", and then we can
decide what modifcations to the runtime are needed to get the app to
read them from there instead of from the server root directory.
It's easiest to just copy every resource that is referenced, but I
have some question whether this
is worth doing for all the component libraries, seems kind of
fragile. Maybe we
should say that if you're going to use components in the app, you need
to include the whole lps/components directory on the server someplace?
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
