I created a form with a single text field. To my surprise Tapestry 4.1
rendered an HTML-page that contained a piece of javascript with dojo-commands.
Since the "dojo.js" was not loaded into the HTML-page it gave me an error. So
I surrounded the form component with a shell component. After all, m
Bernard man.poznan.pl> writes:
>
> Beat Hoermann wrote:
> > I surrounded the form component with a shell component. After all, my tiny
web-
> > app, just displaying a simple text field and a submit button, not using
ajax
> > nor any dojo things, was forced
Jesse Kuhnert gmail.com> writes:
> You should find that no XmlHttpObject's will be created against your will
> unless you specifically set a parameter or call a method that is designed to
> do it. (whether directly or as a side effect).
Good idea!
> The framework does continue to include javasc
Jesse Kuhnert gmail.com> writes:
>
> Just as an update on this thread, it looks like they've been working on
> build size and I'm currently able to create a 23kb file for dojo..So, I hope
> that will speed things up a little bit.
>
Great, what a progress!
Reducing the size of the "dojo.js" is
Sometimes I would like to pack a Tapestry component into a single jar-file
without being forced to include it into a library. All my components are i18n
capable, hence, they have a non-empty component message catalog. Strange
enough, Tapestry cannot find the message keys as soon as the component
Jesse Kuhnert gmail.com> writes:
>
> There has been some signifcant tooling going on by those crazy guys at aol.
> It looks like with the move of all tapestry javascript into dojo packages
> which has already happened - people who care will be able to create special
> compressed js versions that
Tapestry web components are made of Tapestry jwc-components and Tapestry page
components. The Tapestry jwc-component comprises all the logic and resources
related to a component specification whereas the Tapestry page component
comprises all the logic and resources related to a page specificatio
