passed as a parameter and the component uses
renderSupport.addScript() to add the script to the ajax response. Tapestry
will then automatically execute this script as part of the ajax processing.
-Nathan
On Thu, Mar 11, 2010 at 2:23 AM, Nathan Kopp wrote:
> I have a page that uses ChenilleKit to po
If anyone is interested in this code, let me know.
BTW, is there an "insider's guide" to the tapestry.js file?
-Nathan
On Thu, Mar 11, 2010 at 1:23 AM, Nathan Kopp wrote:
> I have a page that uses ChenilleKit to pop up a window that contains a
> component. That componen
I have a page that uses ChenilleKit to pop up a window that contains a
component. That component contains a form enclosed in a zone. The form get
submitted under a variety of circumstances primarily for the purpose of
storing the state and redrawing the form based on some option the user just
sel
context
for other purposes.
So far, this is working very well for my application. I haven't tested its
compatibility with the formEncode feature of the normal Loop component. If
other people are interested, I'm willing to share the source code... but I
probably won't have time to
ust
> kept repeating the same message. So, is this just a case of having to
> learn the tricks of the trade or is there something we could
> collectively do to improve things?
>
> Kalle
>
>
> On Tue, Feb 16, 2010 at 7:18 PM, Nathan Kopp
> wrote:
> > For future re
who offered the recommendations that eventually led me to locate my
bug and resolve the problem.
-Nathan
On Tue, Feb 16, 2010 at 9:32 AM, Nathan Kopp wrote:
>
>
> On Mon, Feb 15, 2010 at 3:21 PM, Thiago H. de Paula Figueiredo <
> thiag...@gmail.com> wrote:
>
>> O
solution works perfectly, as
expected... without the need for the code I wrote below.
Thanks much for your help and patience!!!
-Nathan
On Tue, Feb 16, 2010 at 10:01 AM, Nathan Kopp wrote:
> Thanks for the suggestion. This looks like a great idea, but it didn't
> work for me exactl
Thanks for the suggestion. This looks like a great idea, but it didn't work
for me exactly as-is. I still get an NPE when Tapestry is trying to bind
component parameters in the level just above ViewDonkeyInlineEdit.
The point of code with the problem is where I'm passing
in Test.tml. When T
On Mon, Feb 15, 2010 at 3:21 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Mon, 15 Feb 2010 03:51:08 -0200, Nathan Kopp
> wrote:
>
> This looks like a bug in your code, most probably by working in a T4-ish
>>> way in T5.
>>>
>>
&
shouldn't be too many lines of complicated
> code either, so the code listed here confuses me a bit.
>
> Someone should post the rather simple code needed to do this. I don't have
> the time right now :)
>
> On Mon, Feb 15, 2010 at 12:06 AM, Thiago H. de Paula Figueiredo
On Sun, Feb 14, 2010 at 3:07 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Sun, 14 Feb 2010 00:10:02 -0200, Nathan Kopp
> wrote:
>
> There are two things preventing this from working:
>> First, Tapestry does not replay the loop when processing the e
ur event onEdit etc.
>@Persist @Property private Boolean isEditing;
>
>
>public void onSaveEditDonkey() {
> foo.getDonkey().saveToDB();
>}
> }
>
>
> Description:
>
> Its that simple.
>
> Peter
>
>
> - Original Message -
>
Hey everyone! I'm new here and I apologize for not lurking long before
posting. I have searched the archives extensively for this issue and have
come up empty, so I'm just going to jump in.
I'm working in Tapestry 5.1.0.5 (the latest as far as I know) and I've run
into a use-case that I can't fi
13 matches
Mail list logo