Josh, Thanks a ton... very much appreciated. This is exactly what I was
looking for. My form consist of about 20/30 fields, so I don't think I'll
see much of a performance issue using option 1. As far as option two, I
wasn't aware tapestry allowed us to pass back a value through the parameter
varia
There are at least a few reasonable approaches to this problem,
different approaches make more sense depending on how you're storing
the data.
For instance, I can't tell from your description whether you are
determining the enable/disable state using business logic about the
workflow/role, or if y
Thanks Thiago for your response. I have a single form with a very large
workflow, throughout the workflow individual fields are either disabled or
enabled depending on user role and workflow state. I have all the field id's
stored in the db, so on render I was hoping to get my list of my
disabled/e
On Mon, 28 Nov 2011 12:08:10 -0200, George Christman
wrote:
Hi Thiago,
Hi!
thanks for the response. How would you recommend controlling the
individual fields dynamically?
The same way I've explained before. Put this logic inside isDisabled().
By the way, what do you mean by dynamicall
Hi Thiago, thanks for the response. How would you recommend controlling the
individual fields dynamically?
I tried something like this,
public boolean isDisabled() {
if
(componentResources.getEmbeddedComponent("unitPrice").getComponentResources().isRendering())
{
return fals
On Fri, 25 Nov 2011 15:21:32 -0200, George Christman
wrote:
Eric, were you able to ever get this to work? I'm attempting to
accomplish the same thing.
Have you tried:
public isDisabled() {
return ...;
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/
Eric, were you able to ever get this to work? I'm attempting to accomplish
the same thing.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-dynamically-set-disabled-attribute-tp2414476p5023268.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
--
I think I'm doing something wrong here
Following Howard post, I tried :
@Inject
private BindingSource _source;
public void setupRender () {
Binding b = _source.newBinding("Parameter Disabled",
_componentSources
.getEmbdededComponent("myComponentId").getComponentResources(),
"prop", "disab
Beginner's level Tapestry:
Bind the disabled parameter of each field to a property that returns
true when the field should be disabled and false otherwise.
Journeyman level Tapestry:
An alternative would be to define a special kind of binding for this
purpose. I'd need more details, but a Bindi
