Discussion: Temporal Expression UI Artifacts

[Adrian Crum <ad...@hlmksw.com>]

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

Re: Discussion: Temporal Expression UI Artifacts

[David E Jones <jo...@hotwaxmedia.com>]

Oh yeah, duh. I knew they were there too since that where we discussed  
them going, and that's a good enough place for them.

If the code has to use the service engine it can't go in anything  
below it, and if the service engine uses it then it can't go anywhere  
above it! So, it gets to be part of the service engine and I guess  
that makes enough since. It's really not too strange I guess, it's a  
feature of the service engine that higher level framework and  
application components can use as well.

-David


On Sep 25, 2008, at 4:25 PM, Adrian Crum wrote:

> Oops, you're right. It's in service.
>
> Ugh. I can't wait for this day to be over. ;-)
>
> -Adrian
>
> Adam Heath wrote:
>> Adrian Crum wrote:
>>> The temporal expression Java code in the security component is  
>>> already
>>> in the trunk. I didn't mean to say that UI artifacts are in the  
>>> security
>>> component. Instead, I was listing all of the temporal expression  
>>> related
>>> files and how they are scattered all over the place. Sorry for the
>>> confusion.
>> Are you certain it's in security?  I just went thru all the commit
>> emails since you started adding this stuff, and I see stuff in  
>> service,
>> but not security.

Re: Discussion: Temporal Expression UI Artifacts

[Adrian Crum <ad...@hlmksw.com>]

Oops, you're right. It's in service.

Ugh. I can't wait for this day to be over. ;-)

-Adrian

Adam Heath wrote:
> Adrian Crum wrote:
>> The temporal expression Java code in the security component is already
>> in the trunk. I didn't mean to say that UI artifacts are in the security
>> component. Instead, I was listing all of the temporal expression related
>> files and how they are scattered all over the place. Sorry for the
>> confusion.
> 
> Are you certain it's in security?  I just went thru all the commit
> emails since you started adding this stuff, and I see stuff in service,
> but not security.
> 

Re: Discussion: Temporal Expression UI Artifacts

[Adam Heath <do...@brainfood.com>]

Adrian Crum wrote:
> The temporal expression Java code in the security component is already
> in the trunk. I didn't mean to say that UI artifacts are in the security
> component. Instead, I was listing all of the temporal expression related
> files and how they are scattered all over the place. Sorry for the
> confusion.

Are you certain it's in security?  I just went thru all the commit
emails since you started adding this stuff, and I see stuff in service,
but not security.

Re: Discussion: Temporal Expression UI Artifacts

[Adrian Crum <ad...@hlmksw.com>]

The temporal expression Java code in the security component is already 
in the trunk. I didn't mean to say that UI artifacts are in the security 
component. Instead, I was listing all of the temporal expression related 
files and how they are scattered all over the place. Sorry for the 
confusion.

I will submit a patch to Jira later today.

-Adrian

David E Jones wrote:
> 
> 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
> 
> 

Re: Discussion: Temporal Expression UI Artifacts

[David E Jones <jo...@hotwaxmedia.com>]

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