Hello,
On 9/8/06, Sebastian Werner <[EMAIL PROTECTED]> wrote:
> I want to try to help you to understand the material a bit better. Maybe
> it's possible for you to enhance the documentation afterwards to make it
> even clearer for new qooxdoo users.
Thanks a lot for your explanation and here are so
This doesn't answer the question about re-initializing the qooxdoo system from page to page. If you go from one HTM page to another, the qooxdoo system will have to re-initialize/re-load. At that point you are loosing any benefit you might gain by having a smaller file with additional initializatio
Jim Hunter schrieb:
> One more thing to think about, if you include the same JS file on every
> page (IE: the full build version with everything), you only get a load
> hit on the first page. Every other page will use the cached file on the
> browser. So by using the full JS file on every page y
One more thing to think about, if you include the same JS file on every page (IE: the full build version with everything), you only get a load hit on the first page. Every other page will use the cached file on the browser. So by using the full JS file on every page you actually make the subsequent
Hi Jose,
I want to try to help you to understand the material a bit better. Maybe
it's possible for you to enhance the documentation afterwards to make it
even clearer for new qooxdoo users.
The build is better than the source. Especially for the final release of
the product. The reason is may
Hello,
On 9/7/06, Sebastian Werner <[EMAIL PROTECTED]> wrote:
> > The problem I have is that I don't want to include a 900Kb .js file on
> > a page that has a single button, so I don't want to use the build
> > system, and the alternative seems to be to include the separate source
> > files, but in
Another alternative is to use the skeletons as a starting base for your
application. The included Makefiles automatically reduce qooxdoo to the
required parts needed by your application.
Please take a look here:
http://qooxdoo.org/documentation/user_manual/skeleton
Cheers,
Sebastian
Jose Leo
Jose Leon schrieb:
> Hello,
> On 9/7/06, dperez <[EMAIL PROTECTED]> wrote:
>> The build system works ok. Dependencies are handled automatically.
> Thanks for replying.
>
> The problem I have is that I don't want to include a 900Kb .js file on
> a page that has a single button, so I don't want to
Hello,
On 9/7/06, dperez <[EMAIL PROTECTED]> wrote:
> The build system works ok. Dependencies are handled automatically.
Thanks for replying.
The problem I have is that I don't want to include a 900Kb .js file on
a page that has a single button, so I don't want to use the build
system, and the al
Hola Jose,
The build system works ok. Dependencies are handled automatically.
Jose Leon wrote:
>
> Hello,
> On 9/7/06, dperez <[EMAIL PROTECTED]> wrote:
>> and have saved a little more bytes in qx.js.
> I'm creating PHP classes to allow me use the components from PHP with
> ease, I have read
Hello,
On 9/7/06, dperez <[EMAIL PROTECTED]> wrote:
> and have saved a little more bytes in qx.js.
I'm creating PHP classes to allow me use the components from PHP with
ease, I have read the manual sections about the build system and the
source version and what I want to do it's to include just th
Hi,
Now I use
qx.ui.table.Table instead of qx.ui.listview.ListView
and
qx.ui.treefullcontrol.Tree instead of qx.ui.tree.Tree
because they are more feature rich.
Then I have created a custom build without those components, by adding this
command line parameters:
--exclude-without
12 matches
Mail list logo
