<div dir="ltr">On Mon, Jul 21, 2008 at 6:29 PM, Chia-liang Kao <<a href="mailto:clkao@bestpractical.com">clkao@bestpractical.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div>I wonder why the Do/Execute class wouldn't be simply Jifty::Action::Record?</div><div><br></div><div>in your case of use base qw/ CubicleLog::Action::Record::Execute /,you still need do declare record_class such as Timer right?</div>
<div><br></div><div>would it make sense to generate CubicleLog::Action::ExecuteTimer with class::loader which uses base simply action::record?</div></div></blockquote><div><br>Also conceivable. There's quite a bit of argument handling logic in ::Create/::Update/::Delete to make them go. I believe something would need to be rolled up. <br>
<br>There's also ::Search to consider and how it would be effected. I have been vaguely disturbed by it being related to Collections and being side-by-side with the Record-related actions in hierarchy and organization. Yet, I haven't researched my misgivings enough to know if my disquiet is just aesthetic or an actual inconsistency (i.e., I'm assuming it's probably okay unless I ever learn otherwise). ^_^<br>
<br>Cheers,<br>Sterling<br></div></div></div>