On 10/20/06, ChuckDeal [EMAIL PROTECTED] wrote:
Could someone update the Wiki to point to the apache svn instead ofsourceforge?Specifically,http://cwiki.apache.org/WICKET/wicket-from-source.html
referenceswicket-parent/README.TXT in branch 1.x.Changed. You can change these things in the Wiki
I'm not sure about other browsers, but IE6 doesn't allow scrolling of a
disabled TextArea. TextArea extends FormComponent and form component has an
internal Behavior that adds the disabled attribute when the field is set to
disabled (setEnabled(false)). This causes my project grief because we
Hi,
It is up to the component on how to interpreted the disabled property.
In your case you could make a new form component (use TextArea as
template) that shows a div with scroll bars instead of an input element.
If you still need the input element, simply add it, but make it hidden.
On 10/20/06, ChuckDeal [EMAIL PROTECTED] wrote:
Then to use it, in my code:TextArea description = new TextArea(description);add(description);TextAreaFixer.updateTextArea(description);Is ther a better way to do what I am trying to accomplish?
I'm not sure what it is that you want but can't you
His problem is that the disabled attribute is added by a behavior and
that he can not remove the behavior.
Erik.
Frank Bille schreef:
On 10/20/06, *ChuckDeal* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Then to use it, in my code:
TextArea description = new
That actually happens via some other code that I snipped. But because
TextArea (specifically FormComponent) also puts the disabled attribute, I
need to make sure that the disabled attribute gets removed prior to
rendering because even though I put the readonly attribute on it, the
disabled
To be clear, you are proposing that I create a new component that generates a
div with css that makes it appear to be a TextArea, then when I determine
(determination based upon the user/data) that I want a readonly TextArea, I
replace the real TextArea with a FakeTextArea prior to rendering?
Yeah, sorry about that. I committed a fix for this. Added method
protected void onDisabled(final ComponentTag tag) to FormComponent,
which is called during rendering when the component is disabled. By
default, an disabled=disabled attribute is added, but clients may
override this method. In your
Yes indeed.
Although I would not attempt to make the div look exactly like a text
area, that would be a very painful exercise.
My thoughts were along the lines of:
.readonlytextearea {
width: 500px;
height: 150px;
overflow: auto;
border: thin solid #000;
}
Erik.
ChuckDeal
Excellent! That was the solution I was hoping for!
You mentioned that you committed this change, to where? 1.2-SNAPSHOT? If
so, are there any other maven2 repos that host the SNAPSHOT builds? This
repo http://maven.sateh.com/repository; is giving me grief. Otherwise, I
suppose that I could
Agreed, I was not looking forward to attempting that! Anyway, Eelco's
solution is more of what I was looking for. Thanks for the help.
Chuck
Erik van Oosten wrote:
Yes indeed.
Although I would not attempt to make the div look exactly like a text
area, that would be a very painful
I don't know how often those snapshots are being build. Building from
source is easy though.
Eelco
On 10/20/06, ChuckDeal [EMAIL PROTECTED] wrote:
Excellent! That was the solution I was hoping for!
You mentioned that you committed this change, to where? 1.2-SNAPSHOT? If
so, are there
OK, so I did all that and nothing changed, then I remembered the move to the
Incubator, but apparently the Wiki didn't remember that :).
Could someone update the Wiki to point to the apache svn instead of
sourceforge? Specifically,
http://cwiki.apache.org/WICKET/wicket-from-source.html
13 matches
Mail list logo
