Hey, Ah that's great, if you'll post when you have updated the files I'll check it out.
I have researched a bit on the flow control, it seems nice for some uses but I highly doubt I'll have use for it in my "community system". Will the pages appear as they have prior to that version by using the SecureScreen/VelocityScreen, or what is needed to disable it so it works like before? I see some warnings for RUNDATA, that it is deprecated - what is replacing it? Currently im using rundata to store for instance a Query object and arguments for it in there for pagination in say a search result. Thanks /Martin -----Original Message----- From: Ben Gidley [mailto:[EMAIL PROTECTED] Sent: 8. januar 2005 11:21 To: Turbine Users List Subject: Re: Duplicate Parameter in Validation.xml file :template.index.vm .template Hi, Aarrgh - I think is the correct statement. A simple explaination is that the Antelope is generally created by taking the bits we want to open source from much bigger Anite applications - now those missing files are sat in the other application. I am quite busy and won't have time for a few days to sort through and locate them and fix it all. On the back button. This is a trick we have added to turbine to let us control the back button. What happens is if you press back the SessionValidator detects this and redirects you back to the task list. The reason you would want to do this it in workflow a screen submit can trigger another user doing something - so you can't go back cos it will often be too late. You can disable this behavious per page if you want. On Why workflow is useful. Firstly it is not useful at all and just a pain if you are doing read-only data display. If however you are doing a process where the user does A then B and if it is sunny do D if raining do C and D etc, it control the flow. The GUI designer lets you model the flow as a chart in front of the users. Then the app picks it up. You then implement each screen. Also workflow gives us some toys such as - A Pause Button on each form that let us save unvalidated data can come back later - Ability to assign tasks to users, groups of users, set permissions on a row level dynamically - A PropertySet which works like a HTTPSession but lasts forever and is persisted in the DB (using serializable objects - or if you don't mind the performance hit you can plug in XStream). Workflow is only really useful for systems with a lot of state. Ben --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
