*cough*modules*cough*
Seriously, we're going to wake up one day and realize we've built a
module/package system with the capability to create standalone
bundles of DHTML code and resources. I think it'd be great if we
thought through the design a bit up front... seems like a problem
with plenty of good and bad design precedent.
jim
On Nov 15, 2006, at 6:46 AM, Henry Minsky wrote:
On 11/15/06, P T Withington <[EMAIL PROTECTED]> wrote:
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.
Yeah that sounds like a good idea.
The resource info thing does not account for DHTML resources, since it
ignores runtime-loaded resources, but I might be able to fix it to
do that
bookeeping. The other alternative is to use a regexp to find the
resource
declarations in the compiled app javascript code, but that would
be a more
fragile hack.
