wired error / firewall depending? / javascript float number error

Hi! I know that this error is not a (or at least it think it is not) a tapestry related error. But it is an error which i cannot "categorize" and for that reason i also dont know, where to ask.. so maybe someone knows the answer or can direct me to the right "forum". My private project is a loca

Disable operations caused due to back and forward buttons

Hi, I am working on a web app and in this we add test xml scripts to run them. I have a page ViewTest.tml(test/view) and this page has Run button to trigger the execution which then navigates to next page (/execution/run/progress).After it is done we navigate to next page ShowResults. Now if the

Progress bar component in Tapestry5

Hi All, I have to implement Progress bar in my project. I don't know whether Progress Bar is a component in tapestry or not. Could someone help me if they have any idea how to implement Progress bar in Tapestry? Regards, Mahendra

Re: [5.4-alpha-2] core_**.properties got wrong encoding?

No, I don't think it's just you. I see it too. I think some of the files might have got munged in the merge into the "core" property files a few weeks back. I checked the corresponding (original) files in the 5.3 branch and they look right there, in contrast. On Wed, Jan 30, 2013 at 6:34 PM, Chris

[5.4-alpha-2] core_**.properties got wrong encoding?

Hi, I'm currently testing alpha-2 and it seems that the encoding of the translations in a few properties files got mixed up. The file says it's UTF-8, my editor uses UTF-8 (and in 5.3 they were all ok!) and I'm reading things this: core-palette-up-label=Aufwärts core-palette-up-label=Ввер

datatables tapestry-jquery refresh

Guys, I have functionality on place where I remove a record from datatables(server-side support). What's the easiest way to refresh it after deleting a record? Thanks a lot for any suggestions... -- View this message in context: http://tapestry.1045711.n5.nabble.com/datatables-tapestry-jquer

Re: form with dynamic extensible content

There are a couple of options you may not have considered: 1. You could fire a component event from your component to your page. This event may expect a specific return type (perhaps a map) 2. Your component could require a parameter of a specific interface type. This interface might be a decora

Re: form with dynamic extensible content

Thanks Lance, I had to use the Environment object..., as my hierarchy of components was the following: PageA --- form -- delegate---> delegate returns the block from pageB using ComponentSource service =-=-=-=-=-=-=-=- PageB ---

Re: [T5.4-alpha-2] Ajax alerts not rendered after a call to dismissAll()

The mailing list doesn't allow attachments. Can you please open an issue and attach the patch there? Kalle On Wed, Jan 30, 2013 at 6:01 AM, Steve Eynon wrote: > So... my last email was a little, um, wrong! > > The error is actually to do with dismissOne() removing the inner > container - but wo

Re: form with dynamic extensible content

Your block will contain fields, these fields will be bound to properties in your page. When the form submits these page properties will be updated. You might choose to fire an event from your component via component resources.fireEvent() to let your page perform some action. All the normal form

Re: [T5.4-alpha-2] Ajax alerts not rendered after a call to dismissAll()

So... my last email was a little, um, wrong! The error is actually to do with dismissOne() removing the inner container - but wotever, it boils down to a typo on Line 77 (ish) of alert.coffee: container.on "click button.close", -> should actually be: container.on "click", "button.close"

Re: AJAX Filtered Grid and Firefox

I'm not familiar with all the javascript in tapestry.js but isn't clicking a submit button equivalent to form.submit() and not form.performSubmit()? -- View this message in context: http://tapestry.1045711.n5.nabble.com/AJAX-Filtered-Grid-and-Firefox-tp5719647p5719669.html Sent from the Tapestr

[T5.4-alpha-2] Ajax alerts not rendered after a call to dismissAll()

When first rendered via a call to setupUI the alerts HTML looks like: ... alerts ... After a call to dismissAll() the HTML looks like: With the inner container nowhere to be found. So when an attempt is next made to show an alert after an ajax call: (t5/core/alert.cof

Re: AJAX Filtered Grid and Firefox

Here's the cause and a solution... It happens if you try to do a manual AJAX submit by calling form.performSubmit(), in Firefox. performSubmit() will try to stop the window.event, but window.event is not defined in Firefox. I'm solving it by scrapping the manual submit. Instead, I've added an i

Re: AJAX Filtered Grid and Firefox

Well spotted. Thanks. On 30/01/2013, at 12:45 AM, Lance Java wrote: > This won't solve your problem but I would change: > onchange="document.getElementById('filterCriteria').performSubmit()" > > to: > onchange="this.form.performSubmit()" > > > > -- > View this message in context: > http://ta