Juergen Donnerstag wrote:
I'm not very deep in that piece of code, but I like the idea of having just one interface to format and convert the data.
Pattern: would it be used to temporarily replace a default pattern (e.g. Date)?
Not nescesarily replace. The converter could (optionally!) use this for conversion. It could have a default pattern (e.g. the SHORT date type pattern), that is used for the whole application. However, for e.g. a display (labels, you could use another pattern instead while using the conversion mechanism for the same type.
ConversionContext: Would it be automatically created and initialized
with lets say the current locale or would that be a task of the
framework user?
That would never be the task of a framework user. Even if a framework user would like to use the conversion utility directly (which is now from experience is something users will want sooner or later), it would be hidden.
Eelco
Juergen
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
