Re: JS space pollution in wicket-extensions
JIRA issue created: https://issues.apache.org/jira/browse/WICKET-898 WICKET-898 Frank Bille-2 wrote: I guess most of us share your view on this. But these things has evolved. wicket-ajax.js also started as some simple functions. If you create an issue for it in JIRA, we have it so we don't remember it. If you even attach a patch I'm sure it will be addressed. :) Frank On 8/27/07, Alex Objelean [EMAIL PROTECTED] wrote: It is not a bug. It is a kind of RFE or a request for usage of best practices when coding client-side code. I was curious if you share the same thoughts. igor.vaynberg wrote: file a bug and preferrably create a patch. -igor On 8/27/07, Alex Objelean [EMAIL PROTECTED] wrote: I've noticed that wicket-extension components (for instance palette.js) pollute the js namespace. Wouldn't it be better to create a namespace for them? Something like this would be pretty: Wicket.Extensions.Palette. This proposal is valid for any other components which contribute with js files. What do you think? Thank you! Alex. -- View this message in context: http://www.nabble.com/JS-space-pollution-in-wicket-extensions-tf4333870.html#a12343022 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JS-space-pollution-in-wicket-extensions-tf4333870.html#a12356503 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JS-space-pollution-in-wicket-extensions-tf4333870.html#a12363372 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JS space pollution in wicket-extensions
JIRA issue created: https://issues.apache.org/jira/browse/WICKET-898 WICKET-898 Frank Bille-2 wrote: I guess most of us share your view on this. But these things has evolved. wicket-ajax.js also started as some simple functions. If you create an issue for it in JIRA, we have it so we don't remember it. If you even attach a patch I'm sure it will be addressed. :) Frank On 8/27/07, Alex Objelean [EMAIL PROTECTED] wrote: It is not a bug. It is a kind of RFE or a request for usage of best practices when coding client-side code. I was curious if you share the same thoughts. igor.vaynberg wrote: file a bug and preferrably create a patch. -igor On 8/27/07, Alex Objelean [EMAIL PROTECTED] wrote: I've noticed that wicket-extension components (for instance palette.js) pollute the js namespace. Wouldn't it be better to create a namespace for them? Something like this would be pretty: Wicket.Extensions.Palette. This proposal is valid for any other components which contribute with js files. What do you think? Thank you! Alex. -- View this message in context: http://www.nabble.com/JS-space-pollution-in-wicket-extensions-tf4333870.html#a12343022 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JS-space-pollution-in-wicket-extensions-tf4333870.html#a12356503 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JS-space-pollution-in-wicket-extensions-tf4333870.html#a12363390 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JS space pollution in wicket-extensions
I guess most of us share your view on this. But these things has evolved. wicket-ajax.js also started as some simple functions. If you create an issue for it in JIRA, we have it so we don't remember it. If you even attach a patch I'm sure it will be addressed. :) Frank On 8/27/07, Alex Objelean [EMAIL PROTECTED] wrote: It is not a bug. It is a kind of RFE or a request for usage of best practices when coding client-side code. I was curious if you share the same thoughts. igor.vaynberg wrote: file a bug and preferrably create a patch. -igor On 8/27/07, Alex Objelean [EMAIL PROTECTED] wrote: I've noticed that wicket-extension components (for instance palette.js) pollute the js namespace. Wouldn't it be better to create a namespace for them? Something like this would be pretty: Wicket.Extensions.Palette. This proposal is valid for any other components which contribute with js files. What do you think? Thank you! Alex. -- View this message in context: http://www.nabble.com/JS-space-pollution-in-wicket-extensions-tf4333870.html#a12343022 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/JS-space-pollution-in-wicket-extensions-tf4333870.html#a12356503 Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
