Do you have a patch that we could look at?
The only funny thing sounds like the code it the security component,
which is what I'd want to look at in the patch.
A really generic interface for this could very well seem funny as it's
really a lower level tool. Interfaces with more of a purpose should
seem more normal, like on a WorkEffort or when scheduling a service job.
-David
On Sep 25, 2008, at 11:38 AM, Adrian Crum wrote:
I've been working on getting the temporal expression UI artifacts
ported over from my local copy to the trunk.
As was suggested earlier, I put some reusable UI artifacts in the
common component, and I set up a temporal expression maintenance tab
and screen in the webtools component (we need a screen *somewhere*
in the project to manage the expressions).
Everything works great, but I'm not happy with it. It's spread out
over too many components. Because of build file dependencies, the
java code is in the security component, the reusable screen
artifacts are in the common component, and the maintenance screen
(that uses the artifacts in common) is in the webtools component.
Before I commit this, does anyone have any better ideas?
-Adrian
