I agree completely.

- Brill

On 15-Jul-08, at 3:28 AM, Wilhelmsen Tor Iver wrote:

Brill Pappin [EMAIL PROTECTED] wrote:
I'd say that WIcket *is a product*, and as such the consumers
of that product have the final say.

Not any more than you can e.g. go to Ford Motor Co. and demand they make
this and that modification to the design of the Mustang, for instance.
Like most consumers your way of "saying" is to choose whether to buy/ use the product or not, and it falls on the developer/manufacturer to fuind
out why you do or do not buy/use it.

(Walton's famous "the customer is always right" has a corollary: If
someone is wrong they simply is not a customer. :) )

It's up to the "core committers" to do the best job they can to make
sure their
"consumers" are getting what they need...

Not unless you want to start paying them to do so, becoming their "boss"
in the process. As they have pointed out, Wicket is not their job but
their "hobby" of sorts.

However: Since it is an OSS product you can download the source and
modify it as much as you like (like I did when I applied the portlet 2.0 patch to the 1.3 and 1.4 trees locally), even creating your own fork of
it if you so desire. You see, the "consumers" are also the potential
workers in the OSS world: if only a group of users want a feature it
falls on them to implement it.

just because it's
an OS project that we don't have to buy, doesn't mean that
the project doesn't depend on people using it.

It does, but if it does not suit people's need they will look elsewhere.
There is a ton of web application frameworks out there to choose from.
If you like the separation of template and code in Wicket, try looking
into e.g. Facelets, which is JSF without the cursed mess called JSP.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to