you should call again setChannelSetup(..) after
changing the list, the other way is to fire some
event, but I do not remember - this is described @
http://tapestry.apache.org/
--- Jabbar <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've been struggling all day editing persistent page
> properties and
Hello,
Thank you all for your help :
I have sorted the problem after a very long time...
I have a page which shows all the properties of List.
On the page I have a disable button which disables the textfield for
two of the properties. After rewind I couldn't understand why tapestry
wasn't as
it's more of an HTML thing than Tapestry - if a field is marked disabled -
then it doesn't figure in the HTTP request that the Browser sends to the
server.
and hence tapestry in turn will not assign these values, as they're not part
of the HTTPRequest at all.
On 10/15/06, Jabbar <[EMAIL PROTECT
I never thought of that ...
On 15/10/06, Karthik N <[EMAIL PROTECTED]> wrote:
it's more of an HTML thing than Tapestry - if a field is marked disabled -
then it doesn't figure in the HTTP request that the Browser sends to the
server.
and hence tapestry in turn will not assign these values, as
Mark Stang wrote:
Hi,
I am using Tapestry 3.x and wondering how to customize my .css file with the
Shell component. I want to be able to swap out my Shell component by putting
it inside of a Library. If I do that can I still just reference it in my
.html? I don't know why I think it is any
Yah it works! Wonderful job (as usual), Jesse! Thank you s much.
If -- one day -- I ever ascend to the position of one of the leading
innovativing forces in the cutting edge iteration of a framework on
which you're happily and critically reliant, take heart in the
knowledge that I would
Hello all!
I think I way be experiencing a bug in tapestry but wanted to find out
if anyone else had experienced it or has heard about it.
When I have a large dynamic form, with fields rendered for a couple
hundred objects in my collection, the Form component seems to wig out
and not render the f
Sorry about that, this is with version 4.0.2.
> Original Message
> Subject: Bug with large dynamic forms?
> From: [EMAIL PROTECTED]
> Date: Sun, October 15, 2006 4:16 pm
> To: users@tapestry.apache.org
>
> Hello all!
>
> I think I way be experiencing a bug in tapestry but want
Hello,
I've never had to show hundreds of objects. Can't you reduce the
number of objects to show?
On 15/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Sorry about that, this is with version 4.0.2.
> Original Message
> Subject: Bug with large dynamic forms?
> From: [EMA
Of course I can design around the issue, but I would prefer not to.
This component of the application is internal only, to the amount of
data passed in the request is not as big of a deal. The point was to
eliminate unneccessary pagination, which I have seen have a history of
aggrivating users wo
Never heard of anything like this...
On 10/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Of course I can design around the issue, but I would prefer not to.
This component of the application is internal only, to the amount of
data passed in the request is not as big of a deal. The point
No need for thanks. I'm having the time of my life doing this stuff. I've
never had access to learning so much from so many smart people. Each line of
code written or change made brings me a great amount of joy.
The only way things could possibly get better is if I could spend ~more~
time working
You should create a JIRA issue with an attached test case.
Regards,
Norbi
[EMAIL PROTECTED] wrote:
Hello all!
I think I way be experiencing a bug in tapestry but wanted to find out
if anyone else had experienced it or has heard about it.
When I have a large dynamic form, with fields rendered
13 matches
Mail list logo
