Well I vote for enums in search. Nice addition.
If you can automate dependencies from one select to another, then that would be even better... dynamic dependencies could clutter it up but if it is simple then thats fine.
How about optional checkboxes in addition to select... then we can
search any/all. This might present a new UI on certain condition.
If you have any need for @OneToOne semantics let me know. I am sure you might. I chiseled this area out last year. Got some good constructs if your interested, but they impact trails-core a bit. They never made it into the project.
Best regards
Ken in nashua
> Date: Mon, 7 Jul 2008 11:13:48 -0300
> From:
pablo.grana@...> To:
users@...> Subject: [trails-users] Enum in search
>
> Hi there.
>
> We added search by enums in our project. Can that be incorporated in the
> project? We did it as an extension to trails, but I can send a diff against
> 1.2-SNAPSHOT this week if you like.
>
> We also added the NONE search option in the association search block.
>
> And somebody in the team implemented 'cascaded combos': when one combo changes,
> the other combos are refreshed based on this changing combo. For example:
>
> Client -> Project -> Task. Create a new task and select a client. This populates
> the project combo with the projects of that client.
>
> And finally, 2 minor things: an unbalanced <li> and a clarification in the
> message for an exception.
>
> I can send diffs for these.
>
> regards
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
Need to know now? Get instant answers with Windows Live Messenger.
IM on your terms.
Best regards
Ken in nashua