I am also pro that rename but...
I find that StaticResourceReference thing a bit strange (and i agree
here wilt Gili)
I see these things a lot in the code:
new StaticResourceReference("xxxx");
new StaticResourceReference("yyyy");
new StaticResourceReference("zzzz");
without any assignment, without nothing.
It is purely for making one time a bind, but when to do that???
You can't do it static because then you don't have the current
Application object or only assign it to one application object.
So to be sure, you have to do it now, every time you make a page that
reference those things.
I am still not very happy with this approach. It is very counter intuitive
PackageResourceReferences/StaticResourceReferences are always fixed.
They are there.
And they are fixed over every wicket application that you currently run
in youre webapplication.
So my vote is still for storing those resources really static. in a
ApplicationResources.storeStatic() call.
they you only have to specify them once (what developers already think
they can do)
and they can do it static in a class.. The DatePicker would be some much
simpler..
and REALLY fixed because deserializing stuff without a new DatePicker
object is made through the normal way
is still not working.
johan
Martijn Dashorst wrote:
+1
Martijn
SourceForge.net wrote:
Bugs item #1255537, was opened at 2005-08-10 00:08
Message generated for change (Tracker Item Submitted) made by Item
Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1255537&group_id=119783
Please note that this message will contain a full copy of the comment
thread,
including the initial issue submission, for this request,
not just the latest update.
Category: core
Group: 1.1
Status: Open
Resolution: None
Priority: 9
Submitted By: Jonathan Locke (jonathanlocke)
Assigned to: Jonathan Locke (jonathanlocke)
Summary: Rename StaticResource and StaticResourceReference
Initial Comment:
PackageResource and PackageResourceReference are much
better names for these classes. There has been much
confusion about the intended use of these classes
because StaticResourceReference is NOT
Static(ResourceReference) but rather
(StaticResource)Reference. In fact, a
StaticResourceReference CANNOT be static and must be
created within a request to allow the resource to bind
to the application. The word static was being used
simply to mean that the resource is loaded from a
package (a static (unchanging) resource) and not
dynamically generated. Anyway, a VASTLY better name
for these classes would be PackageResource and
PackageResourceReference, which are fairly
self-explanatory. I would like to rename these for 1.1
to get rid of all the confusion.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1255537&group_id=119783
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing
& QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing
& QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
