Just to make it a little more complicated, but still en vivo scenario:
Just imagine a normal site with 20 pages. Every page can have one or two
widgets connected in the page flow, such as an image, hyperlink text etc. When
the widget is clicked some action takes place.
You have a set of widgets developed. One of them is used on every page. Another
is used in some of the pages. A third might be used in only one page etc. From
this we can understand that we have to create ONE BIG application:
1. one "compilation" loaded on every page, even though not all widgets are used
2. have many different "compilations" of the widgets, one for each page using
widgets
Speed and size in general can be saved to a certain extent by loading packages
at runtime.
Two questions concerning this:
1. where is the static data loaded? such as paths to resources etc. in the
start package? or in each of the runtime packages?
2. how would you do in development time to keep package separation and still
get smallest size of initial package when loaded?
Stefan
------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web. Learn how to
best implement a security strategy that keeps consumers' information secure
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
