unsubscribe
-Original Message- From: Ben Tomasini [mailto:[EMAIL PROTECTED] Sent: Monday, September 24, 2007 11:08 PM To: Tapestry users Subject: Checking for a logged in user globally Hi, I am working on an application that requires a logged in user for access to any of the pages. My plan is to create a login form and store the logged in user in an ASO. I understand that I can implement an onActivate() on each of my pages, check to see if the user exists in the ASO, and if not, redirect the user to the login page. I could put this method into an abstract page which all of my pages extend from; however, I would rather not put that kind of constraint and burden on page development. Is there a more global way to enforce that an ASO exists, and if not, redirect to a page? Ben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: T4: How to exclude dojo?
This is not an answer to the question nor is it about T4, but I'd really like to see more jQuery support in T5. I've left behind dojo in favor of jQuery when I discovered its existence from this list. Ariel -Original Message- From: news on behalf of Chinchih Sent: Sat 7/28/2007 4:26 AM To: users@tapestry.apache.org Subject: T4: How to exclude dojo? I know that Tapestry 4.1.x bundles with dojo, and to use the dojo functions, the @Shell component will have to be used to include the necessary js files. However, in our application we prefer to use jQuery instead of Dojo. I noticed that if a Form component is used, Tapestry will output the following code inside the generated block: Is there a way to "turn off" Dojo to avoid having to include dojo? Thanks, Chinchih - 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]
RE: T5 validation error images displayed withform.clientValidation="false"
Oops, I misread the post. Please ignore my previous post. -Original Message- From: ASTI Araza, Ariel D. [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 19, 2007 10:50 AM To: Tapestry users Subject: RE: T5 validation error images displayed withform.clientValidation="false" I was wondering about the presence of that tag myself, until I realized that for client-side validation to avoid having to go back to the server, the images must already be in the page, but it should remain hidden until needed. I just ensured that I had the right CSS (I used tapestry.css) and the client side validation performed as expected, the error images didn't show until I hit submit and there's a field violating the validation rules. Ariel -Original Message- From: Martin Grotzke [mailto:[EMAIL PROTECTED] Sent: Monday, June 18, 2007 9:28 PM To: Tapestry users Subject: T5 validation error images displayed withform.clientValidation="false" Hi, even if you set clientValidation="false" on a form, T5 renders the validation error image for all input components (for validation errors that might occur): AFAICS with clientValidation="false" this should not be needed and markup could be improved + page load time reduced. Shall we submit an issue for this / would a patch be welcome? Cheers, Martin - 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]
RE: T5 validation error images displayed withform.clientValidation="false"
I was wondering about the presence of that tag myself, until I realized that for client-side validation to avoid having to go back to the server, the images must already be in the page, but it should remain hidden until needed. I just ensured that I had the right CSS (I used tapestry.css) and the client side validation performed as expected, the error images didn't show until I hit submit and there's a field violating the validation rules. Ariel -Original Message- From: Martin Grotzke [mailto:[EMAIL PROTECTED] Sent: Monday, June 18, 2007 9:28 PM To: Tapestry users Subject: T5 validation error images displayed withform.clientValidation="false" Hi, even if you set clientValidation="false" on a form, T5 renders the validation error image for all input components (for validation errors that might occur): AFAICS with clientValidation="false" this should not be needed and markup could be improved + page load time reduced. Shall we submit an issue for this / would a patch be welcome? Cheers, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
