a bit more info: in wicket 1.3 (default with SLC) the change objects aren't
really used anymore
(they are not stored). They only cause an increment of the page version
number..
johan
On 9/3/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
igor.vaynberg wrote:
On 8/23/07, Sam Hough [EMAIL
commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12473771
Sent from the Wicket - User mailing list archive at Nabble.com
On 9/4/07, Sam Hough [EMAIL PROTECTED] wrote:
Thanks Johan and Eelco,
I'm going to consider the model as opaque as far as change tracking is
concerned. I just want an easy way to track dirty components so looks like
this is the way to go unless it is going away completely. Since so many
...
Perhaps coming from GWT I imagined Wicket would magically handle all the
state changes for me. All the AjaxTarget stuff seems very low level for
writing user interfaces.
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12483783
I have the habit of having a fixUpTheStateOfThisWidget method (real name
changed to protect the guilty) that I'm starting to wonder if I can hook
this into marking components as dirty. So maybe I can get away with explicit
marking of components as dirty.
Or e.g. work with bean properties and
not that many
choices...
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12461509
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe
igor.vaynberg wrote:
On 8/23/07, Sam Hough [EMAIL PROTECTED] wrote:
heh, there is nothing that automatically marks components as dirty()
because
wicket doesnt know what you do inside your components. wicket is
unmanaged.
If I do Component.setVersioned(true) and hook in my own
this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12308606
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e
advice.
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12308606
Sent from the Wicket - User mailing list archive at Nabble.com
? Restricting the set
of
components can presumably end up with a more consistent UI...
Anyway, thanks for all your time and sage advice.
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12308606
Sent from the Wicket - User
this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12308606
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
]
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12426453
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL
as
dirty
so
they can be sent back via Ajax (Echo like)? I think that would
handle
90%
of
our Ajax like stuff.
Cheers
Sam
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface
:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12290179
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
consistent UI...
Anyway, thanks for all your time and sage advice.
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12308606
Sent from the Wicket - User mailing list archive at Nabble.com
On 8/24/07, Johan Compagner [EMAIL PROTECTED] wrote:
We can do that because all our components implement specific interfaces
which changes
the state of the component. For example
interface ILabelMethods
{
setBackground(Color color)
setForeground(Color color)
// and so on
}
://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12308606
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
as dirty
so
they can be sent back via Ajax (Echo like)? I think that would handle 90%
of
our Ajax like stuff.
Cheers
Sam
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12290179
Sent from the Wicket - User mailing list
like)? I think that would handle 90%
of
our Ajax like stuff.
Cheers
Sam
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12290179
Sent from the Wicket - User mailing list archive at Nabble.com
in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12290179
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
but it seems like a reasonable thing to
do? Anbody else tried this? Worked out well? Top tips?
--
View this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12272781
Sent from the Wicket - User mailing list archive at Nabble.com
this message in context:
http://www.nabble.com/Component-Factory-and-code-against-interface-tf4311047.html#a12272781
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
22 matches
Mail list logo
