Hi Tim,
On May 29, 2007, at 4:57 PM, Timmy wrote:
So, any changes a user makes on the CalendarComponent are
recorded as TimeEntry records associated with a Timesheet.
PayPeriod and Job are both mandatory to a Timesheet. It seems to
me that this Calendar object we've been talking about coul
Chuck:
On May 29, 2007, at 4:20 PM, Chuck Hill wrote:
Hi Tim,
On May 29, 2007, at 12:51 AM, Timmy wrote:
I've attached a pic that demonstrates what I'm doing. My prior
working version has many more controls but this should give an
idea. This is only the representation for an exempt employ
Hi Tim,
On May 29, 2007, at 12:51 AM, Timmy wrote:
I've attached a pic that demonstrates what I'm doing. My prior
working version has many more controls but this should give an
idea. This is only the representation for an exempt employee.
On May 28, 2007, at 10:34 PM, Chuck Hill wrote:
H
Hi Tim,
On May 28, 2007, at 9:53 PM, Timmy wrote:
I thought it might be useful for me to give some more details about
the app and model to make sure that the concensus is that I'm way
off the mark. :-) The Calendar and Day representations in the
respective components really are for displa
Chuck, et al:
I thought it might be useful for me to give some more details about
the app and model to make sure that the concensus is that I'm way off
the mark. :-) The Calendar and Day representations in the respective
components really are for display only. So, the calendar itself is
j
Hello Tim;
Am I approaching this the wrong way or is there a simple way for me to
address actions in a child component using an enclosing form and
widgets that are both resident on the parent?
I think you want a child component's WOSubmitButton etc... to fire
actions on it's parent component
You are going about it the wrong way. This is making you want to do
things that you can not and should not want to do.
"Logic is driven by an inner class CalendarComponent.DayCell"
"can't figure out how to execute the working actions in
CalendarComponent from this perspective"
It seems you
Daniele:
Thanks for the response. No, I'm not really sure what is better and
you're probably right that it is best to put the form buttons on
CalendarComponent itself. I was searching for a solution that would
allow me not to do that so that I could simply leave the component
clean. I sup
2007/5/25, Timmy <[EMAIL PROTECTED]>:
WO List:
My project has a large monolithic WOComponent that draws a calendar
(WOTable) with the ability to select checkboxes in each day to effect
a change on that day. This has functioned very well for some time now.
But I've decided to try and split this
WO List:
My project has a large monolithic WOComponent that draws a calendar
(WOTable) with the ability to select checkboxes in each day to effect
a change on that day. This has functioned very well for some time now.
But I've decided to try and split this component into multiple
subcompo
10 matches
Mail list logo
