T4: Broken date picker or something else?

2007-05-15 Thread William Keller
Hi all, I'm trying to build a page which has a few basic components, and a few EventListeners that update 'select' components etc etc. Recently, I've been trying to add a @DatePicker, but I get horrible errors. Stack trace is attached: ERROR: 11:51:47 PM: Error evaluating script: //![CDATA[

Re: Some Basic Form Handling

2007-05-03 Thread William Keller
From my understanding, T5 is much different in that there is an '@OnEvent' annotation e.g. class Page { @Component private Form form; @InjectPage NextPage nextPage; @OnEvent(value=submit) public Object submit() { return nextPage; } } and on your corresponding page:

Re: tapestry-acegi

2007-05-03 Thread William Keller
I've got this working. Code supplied. Please customise for your purpose :) hivemodule.xml module id=com.ews.tapestry.acegi version=1.0.0 contribution configuration-id=hivemind.ApplicationDefaults default symbol=hivemind.acegi.dao.passwordEncoder value=

Re: tapestry-acegi

2007-05-03 Thread William Keller
I forgot to mention that you will need to map your User and GrantedAuthority as per usual on Acegi. The stuff I gave you doesn't go in depth on setting up your models (your User needs to implement UserDetails). Once you set up yoru GrantedAuthority for your users your tapestry pages can now use

Re: Tapestry 4.1.1 and @EventListener on IE7

2007-05-02 Thread William Keller
Would moving to T5.0.3 solve this ? On 5/2/07, William Keller [EMAIL PROTECTED] wrote: thanks for the prompt replies! I'm wondering if this is something related to DOJO? If so, and I know this is a very simplistic view of things, I wonder if updating DOJO could yield a working version? On 5

Re: Tapestry 4.1.1 and @EventListener on IE7

2007-05-02 Thread William Keller
is fine) - if your updated value contains any HTML escape entity (like eacute;), it won't work on IE. Replace with the UTF-8 value instead. HTH Ch. 2007/5/2, William Keller [EMAIL PROTECTED]: Would moving to T5.0.3 solve this ? On 5/2/07, William Keller [EMAIL PROTECTED] wrote: thanks

T5: SelectModel vs T4 IPropertySelectionModel

2007-05-02 Thread William Keller
I briefly tried out T5 (5.0.3) yesterday and was impressed! One of the areas I couldn't convert my app easily though, was the Select boxes (that required IPropertySelectionModel). Currently, in T4 I use a global static helper that automatically prepares my lists as per code: code public class

T5: SelectModel vs T4 IPropertySelectionModel

2007-05-02 Thread William Keller
I briefly tried out T5 (5.0.3) yesterday and was impressed! One of the areas I couldn't convert my app easily though, was the Select boxes (that required IPropertySelectionModel). Currently, in T4 I use a global static helper that automatically prepares my lists as per code: code public class

Re: T5: SelectModel vs T4 IPropertySelectionModel

2007-05-02 Thread William Keller
for this ? On 5/3/07, Weisu [EMAIL PROTECTED] wrote: You can use List or TreeMap in T5.0.3. William Keller wrote: I briefly tried out T5 (5.0.3) yesterday and was impressed! One of the areas I couldn't convert my app easily though, was the Select boxes (that required IPropertySelectionModel

Re: Tapestry 4.1.1 and @EventListener on IE7

2007-05-01 Thread William Keller
out. Unfortunately I can't make any promises about 4.1.1 definitely working on it but the still-in-development 4.1.2 version doesn't have this problem. On 5/1/07, William Keller [EMAIL PROTECTED] wrote: Hi all, Sorry if this is a repost, but I can't get any of my working pages to run on IE7

Re: Tapestry 4.1.1 and @EventListener on IE7

2007-05-01 Thread William Keller
2.7 stabilizes. It's getting close but the reports are still too frequent to feel safe. I'd like to have at least a week or two of no ognl issues reported before heading down that path. On 5/1/07, William Keller [EMAIL PROTECTED] wrote: Ouch. I guess the only logical answer for me to ask now

@EventListener and submitForm

2007-02-04 Thread William Keller
Hi all, I've been using the great new features of T4.1.1, and I'm having a few issues with the @EventListener. You see, I require multiple cascading PropertySelections that are re-usable, and can appear multiple times on the same page. These are wrapped in an 'AddressDefinition' component.