[Win32utils-devel] Futzing with TaskScheduler

win32utils-devel at rubyforge.org win32utils-devel at rubyforge.org
Fri Apr 2 22:35:19 EST 2004


I agree ! Go right ahead ...

----- Original Message ----- 
From: <win32utils-devel at rubyforge.org>
To: <win32utils-devel at rubyforge.org>
Sent: Friday, April 02, 2004 9:27 PM
Subject: Re: [Win32utils-devel] Futzing with TaskScheduler


> Hi,
>
>
> > Hi all,
> >
> > Thought I should say something - it's been a little while. :)
> >
> > Anyway, I'm still futzing with how I want the Ruby API to look.  The
more
> I
> > look at the Perl version, the more I think it was too faithful to the C
> API.
> >   Right now I'm looking at the trigger() method.  For example, I don't
see
> > any reason to make the "type" key take a hash as an argument (thus
> creating
> > a nested hash) when none of the keys are duplicate.  We should just DTRT
> (do
> > the right thing).
> >
> > Also, I mostly dislike camel case and I'm not sure what logic MS used
when
> > it chose "BeginX" versus "StartX".  I'm just going to use "start".  So
for
> > now I'm looking at something like this:
> >
> > t = Trigger.new(task_name,some_host)
> > t.trigger = {
> >    :start_year => 2004
> >    :start_month => 4
> >    :start_day => 25
> >    :start_hour => 23
> >    :start_minute => 5
> >    :trigger_type => DAILY
> >    :week => FIRST | LAST
> >    :dow => MONDAY | TUESDAY | WEDNESDAY
> >    :months => JANUARY | FEBRUARY | MARCH
> > }
> >
> > How's that look?
>
> I fully agree with you.
>
> I think the taskscheduler C API is too complicated and inconsistent in
> naming.
>
> Go ahead as you want.
>
> Cheers,
>
> Park Heesob
>
>
> _______________________________________________
> win32utils-devel mailing list
> win32utils-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/win32utils-devel



More information about the win32utils-devel mailing list