<FONT face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size=2><P style="MARGIN: 0px">Derek,</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">Re Tohu 13 (<A href="https://jira.jboss.org/jira/browse/TOHU-13" target=blank>https://jira.jboss.org/jira/browse/TOHU-13</A>)</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">Another option for this one might have been to keep the structure as it is just using group.items but instead change the mechanism that handles moving from page to page so that if you try to move to a page that isn't there then it skips it and goes on to the next one in sequence.</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">This means you could just set questionnaire.items to the full list of steps and don't define the groups for the steps that you want to skip over.</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">I think this can be achieved by doing:</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">- make Questionnaire remember what the lastActiveItem was, which can just be set inside setActiveItem.</P><P style="MARGIN: 0px">- write a rule (with a high salience) that checks whether questionnaire.activeItem exists and if not then it changes the activeItem, and it knows which direction to go (forward or back) by looking at lastActiveItem. (Can just get the index of both activeItem and lastActiveItem and then +/- 1).</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">I'm pretty sure this would work, and it would be simpler than what you've got now. It certainly simplifies the model anyway by not adding another list attribute to it. I think simplicity of the model is paramount.</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">Sorry, I need to get myself added to the notifcation list in Jira so I hear about these things sooner.</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">Damon</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">P.S. I notice Ronan made a small change too (to always open the completion action in a new tab/window), but there is no associated Jira. Please can we do this for all changes. It means that users of Tohu have visibility of what <STRONG>features</STRONG> have changed from one release to the next without having to look through the SVN history of <STRONG>individual code changes</STRONG>. Also I wonder if the change made should actually be optional, as I'm not sure you'd want that behaviour in most situations.</P><P style="MARGIN: 0px"> </P><P style="MARGIN: 0px">P.P.S. I think we should start using the mailing list more for discussion on changes etc as others (outside Solnet/Suncorp) have started using Tohu, and may have useful contributions they can make too. Ronan/David you should join the list too: <A href="https://lists.jboss.org/mailman/listinfo/tohu-users" target=blank>https://lists.jboss.org/mailman/listinfo/tohu-users</A></P><P style="MARGIN: 0px"> </P></FONT>
Attention:
This email may contain information intended for the sole use of
the original recipient. Please respect this when sharing or
disclosing this email's contents with any third party. If you
believe you have received this email in error, please delete it
and notify the sender or postmaster@solnetsolutions.co.nz as
soon as possible. The content of this email does not necessarily
reflect the views of Solnet Solutions Ltd.