[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Pyatcron-devel-list] Cron backend: a correction
From: |
Childers, Matthew |
Subject: |
RE: [Pyatcron-devel-list] Cron backend: a correction |
Date: |
Thu, 13 Nov 2003 15:21:21 -0600 |
> -----Original Message-----
> From: Julien Olivier [mailto:address@hidden
> Sent: Thursday, November 13, 2003 2:57 PM
> To: address@hidden
> Subject: RE: [Pyatcron-devel-list] Cron backend: a correction
>
> > As a user I want an easy, well laid out GUI that I can quickly
> > modify the following (which I think we are already close to):
> >
> > o Add, modify, delete cron and at jobs (of course)
> > o Use a 3 step wizard/druid to quickly create cron/at jobs (see
> > Juliens earlier post on exacts specs)
> > o Offer pluggins (I am so lost on how to spell this now) to
> > choose
>
> Congrats Xavier, you lost him now :) it's PLUGIN, for g**'s sake :)
>
> > and modify the task the user will be using.
> > o Allow "easy" scheduling, or predefined schedules for users
> > such
> > Daily at x time, or Weekly on x days at x time...
> > o Add an Advanced Tab/Button/Dialog that allows a user to
> > define
> > a much more precise schedule.
>
> And maybe, even, tweak the command if it has been generated by a
plugin.
>
> > o A Preferences dialog to set cron variables. ???
>
> If, as a user, you're not sure you need it, maybe you don't need it :)
> What I mean is: do users know what a cron variable is ? If they do,
they
> probably don't need/want a graphical tool to configure their cron
> jobs...
The question marks were asking if you all wanted to add this feature,
not whether or not I would use it. I agree that the average user will
never use it, and that most that do don't need a graphical tool.
However, I don't agree that we should make our interface lacking in
options. If someone that comes to linux from a windows background may
like using a graphical tool to set up there tasks. When I came to
linux, and didn't know any of the commands, I really liked the graphical
tools, because I could actually use them.
I just think that we need to hide from the users things that they may
not need, but not leave them out completely.
>
> > o An option to show/hide old at commands
> >
> > Any others that I am missing?
>
> --
> Julien Olivier <address@hidden>
>
>
> _______________________________________________
> Pyatcron-devel-list mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/pyatcron-devel-list
- Re: [Pyatcron-devel-list] Cron backend: a correction, (continued)
RE: [Pyatcron-devel-list] Cron backend: a correction, Childers, Matthew, 2003/11/13
RE: [Pyatcron-devel-list] Cron backend: a correction,
Childers, Matthew <=
RE: [Pyatcron-devel-list] Cron backend: a correction, Childers, Matthew, 2003/11/13
RE: [Pyatcron-devel-list] Cron backend: a correction, Childers, Matthew, 2003/11/14
RE: [Pyatcron-devel-list] Cron backend: a correction, NICOLOVICI Xavier, 2003/11/17