- toolbar no longer able to be moved.
- still think the menubar is needed for things like view -> advanced/simple, but maybe in a later release we could try without. (dont want to oversimplify)
- Status bar is used when you are root and changing user. a suggestion could be to hide when editing as a normal user.

If you still have suggestions please re comment.

How do you think about the UI suggested in the following page?

Bug 419479 – Simpler and more consistent/intuitive UI suggestion
http://bugzilla.gnome.org/show_bug.cgi?id=419479


>>> still think the menubar is needed for things like view -> advanced/simple

I think this feature is not very useful... When the user is interested in the details of the task, they can simply choose the Property option. So it's violating the "Don't Repeat Yourself" principle. I think removing the menubar is not about oversimplification. It's about removing unnecessary complication.

Best,

Satoshi

> Hello,
> 
> Here's the rough sketch of my new UI suggestion:
> 
> Main Window:
> http://img173.imagevenue.com/img.php?image=60826_main_122_355lo.jpg
> 
> Task Selection in Main Window:
> http://img161.imagevenue.com/img.php?image=60828_selecttask_122_561lo.jpg
> 
> One-Time Task Create/Edit Window:
> http://img155.imagevenue.com/img.php?image=60833_onetimetask_122_339lo.jpg
> 
> Periodical Task Create/Edit Window:
> http://img175.imagevenue.com/img.php?image=60839_periodicaltask_122_483lo.jpg
> 
> I believe this enhances the usability of the application.
> 
> Any thoughts?
> 
> Best,
> 
> Satoshi
> 

*** Bug 419479 has been marked as a duplicate of this bug. ***

Hum, true, the sketch-up does not look bad. But it requires quite some work since the code is fairly deep integrated with the gui. If you feel up for the work until it is stable i would create a new branch and let you help out there. 

i dont have time now to start with this alone now. i would say if this is finished we are ready for a 2.0 release.

- gaute

Since I'm not a heavy user of the app, I don't mind waiting until you can work on rewriting it. I just pointed out what could be designed better from a user's perspective. But thanks for taking my suggestion into consideration.

Best,

Satoshi

thanks for the suggestions, they motivate.

- gaute

Work on the modified ui is located under branches/new-ui in the subversion repository.

- gaute

Statusbar is now hidden if you are not editing as root.

- gaute

What is the meaning of the Select task button, and what is the name of the widget with the arrow where you have put the Help button.

- gaute

Removed the menubar and added some more buttons to the toolbar. Icon and type is in the same column.

I am unsure if it looks any better without the menubar. Check out from: svn checkout http://svn.gnome.org/svn/gnome-schedule/branches/new-ui gnome-schedule-new-ui

Created attachment 87594 [details]
Proposal for new main window based on mockups from Satoshi Tanabe 

Here is a screenshot for the proposal for the new ui

Your proposals for new interfaces for editing at and crontab both lack options for  templates and icons, are you suggesting they should be removed?

- gaute

Hi Gaute,

"Should be removed" is a strong word. Minimal thing I can say is I think it's not necessary, and in my opinion it's better to be removed. For 3 reasons:

(1) Distinguishing pne-time tasks from periodical tasks by using two icons would be enough because normally people don't automate *that* many tasks.

(2) Choosing good description for the task and choosing good icon for the task is a duplication of users' burden. A lot of people would end up using the same icon for every task because it's not very important for usrs' purpose of scheduling tasks. Sometime it's better to have less choices.

(3) Without the space for icons UI looks simpler and more accessible to users. And that space can be used for what's more important for users, i.e. the space for task scripts.

How do you think?

Best,

Satoshi

(In reply to comment #15)
> Hi Gaute,
> 
> "Should be removed" is a strong word. Minimal thing I can say is I think it's
> not necessary, and in my opinion it's better to be removed. For 3 reasons:
> 
> (1) Distinguishing pne-time tasks from periodical tasks by using two icons
> would be enough because normally people don't automate *that* many tasks.
> 
> (2) Choosing good description for the task and choosing good icon for the task
> is a duplication of users' burden. A lot of people would end up using the same
> icon for every task because it's not very important for usrs' purpose of
> scheduling tasks. Sometime it's better to have less choices.
> 
> (3) Without the space for icons UI looks simpler and more accessible to users.
> And that space can be used for what's more important for users, i.e. the space
> for task scripts.
> 
> How do you think?
> 

I think you are right, the only thing that would be a possibility is that for instance a antivirus program could supply a template scheme for gconf with their own icon, but I dont know about any antivirus program that uses cron in this way anyway.

At least I never use the icon option.

So then we need two icons, one for recurrent task and one for one-time tasks.

- gaute

(In reply to comment #11)
> What is the meaning of the Select task button, and what is the name of the
> widget with the arrow where you have put the Help button.
> 
> - gaute
> 

Oh, it seems I ignored this comment. 

What I meant by the 2nd screenshot is when "Select Task..." (chosen by default right after launching Gnome Schedule) is selected, the "New" button is disabled, just like the Properties/Edit button when no task is selected.

When "One-Time Task" or "Recurrent Task" is selected, the "New" button is enabled. Then, when you press the "New" button when it's enabled, the "Create/Edit Task" window appears according to the type of the task.

This way you can eliminate the popup dialog when "New" is pressed. This would feel more smooth for users.

Best,

Satoshi

Maybe it would be an idea to create a dropdown choice for recurrent or one-time after you have pressed the new task button, but disabling enabling the new task button depending on which tasks is allready selected i think is unlogical. i would like without creating too many of my own widgets a new button with an arrow on the side. if the new button is pressed then the dialog with the choices come up, if the arrow then you can choose which type of task and it is unnecessary to ask which first.

- gaute

Ok, implemented a new button with an arrow. Revision 845

The new button is now a MenuToolButton with a arrow that allows for direct selection of type of task that is intended to create. A click on the button works like earlier.

There should be icons on the menu that pops up, the same that we need for crontab and at.

- gaute

*** Bug 419214 has been marked as a duplicate of this bug. ***

(In reply to comment #0)
> I think the current "Date and Time" tab is a bit hard to read. Right now the
> format is:
> 
>     Date: [3:20 18.3.2007]
>     Hour: [3]
>     Minutes: [20]
> 
> Why not make it something like:
> 
>     Date: [18][March][2007] 
>     Time: [03]:[20]
> 
> I think the latter is more readable and takes less space.
> 
> And I don't really think the calendar is necessary. Without the calendar it
> could have one less tab and would become more accessible.
> 

*** Bug 325884 has been marked as a duplicate of this bug. ***

gtk.MenuToolButton requires pygtk >= 2.6

Created attachment 99090 [details]
at editor

Have a look at the new ui.

latest changelog:
2007-11-14  Gaute Hope  <eg@gaute.vetsj.com>

	* new crontab editor fully works
	* deleted old one
	* new field to the main treemodel for timestring_advanced; the timestring shown in advanced mode. Effectively only affecting @reboot entries now showing _("At reboot") and not 5 x @reboot
	* advanced view toggle button behaves
	* set version to 2.0.0-BETA
	* remembers size and position, but not state due to silly gtk/gnome
	
2007-11-14  Gaute Hope  <eg@gaute.vetsj.com>

	* Oh.. forgot this file, here's a summary
	* From trunk: Bugfix where some dates in the future wouldn't be accepted.
	* at editor fully works
	* added icon to at editor
	* added icons to drop down menu
	* removed exit button
	* new icon for gnome-schedule by kiddo
	* created new crontab interface in glade, needs to attached	
	* at parser locale ignorant
	* gnome-schedule desktop entry in preferences

Created attachment 99091 [details]
and the crontab editor

Check out the latest svn to test it:
svn co http://svn.gnome.org/svn/gnome-schedule/branches/new-ui gnome-schedule-new-ui

Does anyone have any thought about using the GNOME widget dateedit for 'at'? We are allready relaying on gnome on other parts so it wouldn't be a big addition I guess.

Like GConf and the gnome.program stuff.

- gaute

I couldn't install the svn version. When I typed

    ./autogen.sh --prefix=/usr/local

I got the following error:
=====================================

checking for glib-gettext >= 2.2.0...

  testing glib-gettextize... 
not found.
***Error***: You must have glib-gettext >= 2.2.0 installed
  to build gnome-schedule.  Download the appropriate package for
  from your distribution or get the source tarball at
    ftp://ftp.gtk.org/pub/gtk/v2.2/glib-2.2.0.tar.gz

[...]

Checking for required M4 macros...

  glib-gettext.m4 not found
***Error***: some autoconf macros required to build gnome-schedule
  were not found in your aclocal path, or some forbidden
  macros were found.  Perhaps you need to adjust your
  ACLOCAL_FLAGS?
=====================================

Anyway, the screenshots look nice. I like the new UI much better than the older one.

Some small things...

* In the "Create a New Scheduled Task" window for one-time tasks, the number entry boxes don't look aligned with the texts on the left ("date" and "time")

* I still don't know when the "Advanced" menu in the main toolbar is useful given that there is "Property" which shows you all the detail of the task

* Can the "Advanced" option in the "Create a New Scheduled Task" window for recurrent tasks be hidden by default using a proper widget? (And it appears when the option is chosen.) The text area for one-time task scripts is big but it is small for recurrent tasks, which seems to be creating an imbalance between them. If the Advanced option is hidden, then that space can be used for task scripts.

Keep up the good work!

Satoshi

(In reply to comment #27)
> I couldn't install the svn version. When I typed
> 
>     ./autogen.sh --prefix=/usr/local
> 
> I got the following error:
> =====================================
> 
> checking for glib-gettext >= 2.2.0...
> 
>   testing glib-gettextize... 
> not found.

[...]

Do you have your distributions gettext-dev package, glib-dev package installed? You need it for ./autogen.sh along with some other dependencies. Always when something fails look for the -dev version of the package.

> 
> Anyway, the screenshots look nice. I like the new UI much better than the older
> one.
> 
> Some small things...
> 
> * In the "Create a New Scheduled Task" window for one-time tasks, the number
> entry boxes don't look aligned with the texts on the left ("date" and "time")

Yes, will arrange them widgets in a table will ay.

> 
> * I still don't know when the "Advanced" menu in the main toolbar is useful
> given that there is "Property" which shows you all the detail of the task

You mean the properties button that open it up? I think it is useful, I want to keep it. I would often use it to switch quick between it, for someone experienced with crontab and at it will be much faster to get an overview and read the tasks if he/she could get them in the familiar format.

> 
> * Can the "Advanced" option in the "Create a New Scheduled Task" window for
> recurrent tasks be hidden by default using a proper widget? (And it appears
> when the option is chosen.) The text area for one-time task scripts is big but
> it is small for recurrent tasks, which seems to be creating an imbalance
> between them. If the Advanced option is hidden, then that space can be used for
> task scripts.

For recurrent tasks it is a one line entry because crontab normally works with one command line: one command per job. Of course you could get more commands by using ; between the commands, but we'll leave that to the user and not to us for parsing a script into a single line command.. or even start to think about creating scripts that we execute with crontab.. and so on and so on :)


> 
> Keep up the good work!
> 
> Satoshi
> 

Thanks! We are making quite some progress now. Kiddo tweaked the UI a bit more, but i will leave some excitement in case you should mangage to compile it :) remember to update with '$ svn up' inside the main gnome-schedule dir.

- gaute

>> Do you have your distributions gettext-dev package, glib-dev package installed?

Well, gettext is already installed, but apt-get on my Ubuntu couldn't find the gettext-dev package. At least one other person seems to have the same trouble:
http://ircarchive.info/ubuntu/2007/5/16/284.html

I think I'll wait for a while. Thanks for your comments though.

Oh, one more thing, although this may have been fixed already:

* I think the icon for one-time tasks should be different from the one used for "Advanced" in the main toolbar (i.e. the orange triangle with "!"). People would tend to associate the two that are not related at all. How about using a clock icon for one-time tasks?

Satoshi

(In reply to comment #29)
> >> Do you have your distributions gettext-dev package, glib-dev package installed?
> 
> Well, gettext is already installed, but apt-get on my Ubuntu couldn't find the
> gettext-dev package. At least one other person seems to have the same trouble:
> http://ircarchive.info/ubuntu/2007/5/16/284.html
> 
> I think I'll wait for a while. Thanks for your comments though.
> 

Try: libglib-2.0-dev

What I have from gettext is:
root@qwerzila:/home/gaute# apt-show-versions | grep gettext
gettext/gutsy uptodate 0.16.1-2ubuntu3
gettext-base/gutsy uptodate 0.16.1-2ubuntu3
liblocale-gettext-perl/gutsy uptodate 1.05-1build1

What I have that matches glib and dev:
root@qwerzila:/home/gaute# apt-show-versions | grep glib | grep dev
libdbus-glib-1-dev/gutsy uptodate 0.74-1
libglib1.2-dev/gutsy uptodate 1.2.10-17build1
libavahi-glib-dev/gutsy uptodate 0.6.20-2ubuntu3
libglib2.0-dev/gutsy uptodate 2.14.1-1ubuntu1
libglibmm-2.4-dev/gutsy uptodate 2.14.0-0ubuntu1

And only glib:
root@qwerzila:/home/gaute# apt-show-versions | grep glib
libdbus-glib-1-2/gutsy uptodate 0.74-1
libglib2.0-cil/gutsy uptodate 2.10.2-1ubuntu2
libglib2.0-0/gutsy uptodate 2.14.1-1ubuntu1
libpoppler-glib2/gutsy uptodate 0.6-0ubuntu2.1
libdbus-glib-1-dev/gutsy uptodate 0.74-1
libglib1.2-dev/gutsy uptodate 1.2.10-17build1
libavahi-glib-dev/gutsy uptodate 0.6.20-2ubuntu3
libtaglib2.0-cil/gutsy uptodate 2.0.2.0-1
monodoc-taglib-manual/gutsy uptodate 2.0.2.0-1
libndesk-dbus-glib1.0-cil/gutsy uptodate 0.3-2
libglib-cil/gutsy uptodate 1:1.0.10-5build3
libavahi-glib1/gutsy uptodate 0.6.20-2ubuntu3
libglib2-ruby1.8/gutsy uptodate 0.16.0-3ubuntu1
libglib1.2/gutsy uptodate 1.2.10-17build1
libglib2.0-dev/gutsy uptodate 2.14.1-1ubuntu1
libnm-glib0/gutsy uptodate 0.6.5-0ubuntu16
libglib-perl/gutsy uptodate 1:1.152-1
libglibmm-2.4-1c2a/gutsy uptodate 2.14.0-0ubuntu1
libglibmm-2.4-dev/gutsy uptodate 2.14.0-0ubuntu1

(In reply to comment #30)
> Oh, one more thing, although this may have been fixed already:
> 
> * I think the icon for one-time tasks should be different from the one used for
> "Advanced" in the main toolbar (i.e. the orange triangle with "!"). People
> would tend to associate the two that are not related at all. How about using a
> clock icon for one-time tasks?
> 
> Satoshi
> 

It is just something temporary. I need an icon!

- gaute

>> Try: libglib-2.0-dev

Thanks. Although 

    $ sudo apt-get install libglib-2.0-dev

didn't work, the follwing command worked:

    $ sudo apt-get install libglib-dev
    
And this installed libglib1.2-dev. However, after typing

    ./autogen.sh --prefix=/usr/local

I got the same error. Maybe I should update to Gutsy...

Satoshi     

Maybe, but it should work.. it is a quite basic package, I just don't know which one it belongs to.

- gaute

Have a look at the remaining bugs for gnome-schedule: http://bugzilla.gnome.org/buglist.cgi?product=gnome-schedule

The remaining tasks for the 2.0-beta is now only to re-implement templates. If you have any other new features or really good ideas now is the time to send them in, either here, to me in email or as seperate bug reports.

Check out: http://gaute.vetsj.com/log/?p=41 for details.

- gaute

See this post: http://gaute.vetsj.com/?p=45 for some screenshots of the template management, and latest changes.

Please comment and test.

- gaute

After the release of 1.2.1 (http://gaute.vetsj.com/?p=48) the new-ui branch has been merged to trunk and development continues there.

- gaute

I released rc1 of version 2.0.0, it would be great if you could test it out a bit before I release it as stable. 


Screenshots: http://gaute.vetsj.com/bilete/index.php?dir=/2007/dev/gnome-schedule/2007-12-13%20-%20gnome-schedule-2.0.0-rc1

Download: http://gaute.vetsj.com/arkiv/2007-12-13%20-%20gnome-schedule-2.0.0-rc1/gnome-schedule-2.0.0-rc1.tar.gz

Full release notes:
http://gaute.vetsj.com/?p=50

Thanks in advance!

- gaute

Noticed the following:

* This is a question: Is there a reason for changing the order of the column items (task, description, etc.) between the normal mode and the advanced mode? I don't use the advanced mode myself, but it seems to cause disorientation.

* On Ubuntu Feisty, the icon for recurrent tasks was not what I saw in your screenshots. See below images:
http://img186.imagevenue.com/img.php?image=43080_feisty-recurrent_122_177lo.jpg
http://img210.imagevenue.com/img.php?image=43358_new-task_122_67lo.jpg

* I love the dropdown calendar (and I love the fact that I don't have to go to another tab for it), but it appears on top of the button on my environment, and I think hiding the button looks unfriendly:
http://img181.imagevenue.com/img.php?image=43093_calendar-on-button_122_447lo.jpg

* Again, the calendar. It doesn't allow you to choose the year older than the current year (i.e. 2007), which I think is a reasonable decision, but it allows you to choose the date that *is* older than the current date. (For example, I can choose 2007-12-10.) Isn't it better to keep track of the current date and not allowing the user to choose the date older than that? There is no point in being able to "schedule" something in the past, and if the user did it, that's probably a mistake.

* The Help document is dated.

Satoshi

(In reply to comment #39)
> Noticed the following:
> 
> * This is a question: Is there a reason for changing the order of the column
> items (task, description, etc.) between the normal mode and the advanced mode?
> I don't use the advanced mode myself, but it seems to cause disorientation.

The idea was to make the line look like a normal crontab record and put all the useful information with higher priority further to the left.

> 
> * On Ubuntu Feisty, the icon for recurrent tasks was not what I saw in your
> screenshots. See below images:
> http://img186.imagevenue.com/img.php?image=43080_feisty-recurrent_122_177lo.jpg
> http://img210.imagevenue.com/img.php?image=43358_new-task_122_67lo.jpg

Hm, the second photo looks a bit weird, it should at least be using a bigger icon. But other than that I have been using the standard stock refresh icons. I think your icon theme still makes sense, but it would make it easier for me as well if I just included the icon the same way I do with the at icon. (which as well would fix the size issue).

> 
> * I love the dropdown calendar (and I love the fact that I don't have to go to
> another tab for it), but it appears on top of the button on my environment, and
> I think hiding the button looks unfriendly:
> http://img181.imagevenue.com/img.php?image=43093_calendar-on-button_122_447lo.jpg

Hm.. Yes it is not a perfect widget, I will have a look at it there must be something wrong with how i calculate the position and size of the button on the screen. It should definetly not hide the button since it was meant as the 'right' way to close the calendar (a toggle button: on -> show, off -> hide).

> 
> * Again, the calendar. It doesn't allow you to choose the year older than the
> current year (i.e. 2007), which I think is a reasonable decision, but it allows
> you to choose the date that *is* older than the current date. (For example, I
> can choose 2007-12-10.) Isn't it better to keep track of the current date and
> not allowing the user to choose the date older than that? There is no point in
> being able to "schedule" something in the past, and if the user did it, that's
> probably a mistake.

Yep, will fix. Trying to add a task with a date in the past will also fail while trying to add it to 'at'.

> 
> * The Help document is dated.

Im not sure I understand what you mean here.


Thanks alot for the really useful comments!

- gaute

>>> Im not sure I understand what you mean here.

Oh, by "The Help document is dated", I meant the help document that pops up when you press the "Help" button --- Gnome Schedule User Guide V2.1 --- is old (i.e. written for the older version of the app) and needs to be updated.

Satoshi

* Fixed crontab icon, is now included.

* Dropdown calendar alligns properly on my machine now, hopefully also works on setups where the decorators are included in the get_position function. Ubuntu users could test this.

* Now it is no longer possible to select dates before one minute ahead in time using the spinbuttons, unfortunatly it doesn't look possible without a lot of work to make that impossible _in_ the calendar. But the spinbuttons doesn't update if a date in the past is selected. I hope this is sufficient

* I opened another bug for the documentation and notified the initial documentors: bug 504654

Check out from latest svn from trunk/ to test.

- gaute

Hi,

This is what happened when I first launched gnome-schedule and pressed the calendar button:

http://img124.imagevenue.com/img.php?image=28584_gnome-schedule_122_1090lo.jpg

Satoshi

---

By the way, I recently came across with the following video by Linus Torvalds. I thought you might be interested in this as a Subversion user:

Tech Talk: Linus Torvalds on git
http://www.youtube.com/watch?v=4XpnKHJAok8

Hi,

Adding a template (Templates -> New) doesn't work in my environment (Ubuntu Gutsy). It simply adds a task in the main window, and nothing happens in the "Manage templates" screen.

Satoshi

hm, for the calendar problem, could you provide a full screenshot. it might be that the width and height is doubling up.

On the second; did you use the 'Add as template' button or 'Add' button?

- gaute

I am now using gtk.gdk.window.get_origin () to calculate the calendar window position, I think this should work better since it gives the position relative to the root window and not the parent window depending on what is defined as the parent window.. It might be that it looks weird when gs is run through Xnest or similar.
(http://www.pygtk.org/pygtk2reference/class-gdkwindow.html#method-gdkwindow--get-origin)

Removed irrelevant buttons and fields when choosing new template in the template_manager, that should clear up any confusion.

Could you test the calendar stuff?

- gaute

Great! Now the calendar appears exactly where I expect it to appear.

The template window is working fine too.

Satoshi

Great! finally.. don't understand what get_position () is supposed to do different than get_origin () or get_geometry ().

- gaute

oh, this is minor, but...

* "Edit" sounds better (i.e. more user-friendly) than "Properties" in the main window, and it is more consistent with the "Manage templates" window, I think.

Satoshi

Done.

That was quick! Now I have nothing to say :-)

Ah. thats a good sign, when you are silenced :)

Hi,

I don't know if you can reproduce this, but please try:

(1) Press "Templates" button -> "New" -> Select one-time task
(2) When the "New template" window appears, press "Cancel"
(3) Close the "Manage templates" window
(4) Choose "one-time task" from the dropdown menu next to the "New" button (i.e. the one with ▼) in the main window
(5) Now you get the "New template" screen, but here you should be getting the "Create a New Scheduled Task" screen (with the dropdown calendar) instead.

Satoshi

Yup, fixed. thanks!

- gaute

Hi,

Here's another suggestion before the official 2.0 release: how about using Launchpad for translations?

About Launchpad Translations
https://translations.launchpad.net/+about

I think this browser-based model is hugely better than the current model (especially for non-programmers) for getting cooperation in translation. If you use this, I'll definitely contribute my Japanese translation.

Satoshi

Hey,

here's the current translation status page: http://l10n.gnome.org/module/gnome-schedule

Also added gnome-schedule to launchpad, but will be using this bugzilla and gnome svn. but might start using the translations, will have a look at it when the source has been imported.

https://launchpad.net/gnome-schedule/

- gaute

>> might start using the translations, will have a look

ok, let me know when you decide to use launchpad for translations, then I'll start working on it.

Satoshi

Yes, allready uploaded. They are awaiting moderation: https://translations.launchpad.net/gnome-schedule/trunk/+imports

- gaute

(In reply to comment #57)
> >> might start using the translations, will have a look
> 
> ok, let me know when you decide to use launchpad for translations, then I'll
> start working on it.
> 
> Satoshi
> 

Using launchpad requires some admin to review my uploaded translations, which hasn't been done in soon two weeks. I will not continue using launchpad for translations, if you want to maintain a launchpad translation page feel free. I suggest using the gnome translation page: http://l10n.gnome.org/module/gnome-schedule

- gaute

Last (hopefully) release candidate for gs-2.0.0: https://sourceforge.net/project/showfiles.php?group_id=112183&package_id=254297&release_id=570825

It would be great if you had the chance to test soon, I will be releasing 2.0.0 in a couple of days.

- gaute

I have two relevant suggestions:

1.

Currently, GS has "Template" -> Select a template -> "Use Template." This opens up a "Create a new task" window, the same thing that appears when you press the "New" -> recurrent/one-time task button. I think this is redundant. The whole point of having the template system is that you don't have to re-create or review what you already created/reviewed in the past. If you want to review the task, you can press "Edit" in the Template window. That's what the "Edit" button is for. So, instead of

    "Template" -> Select a template -> Press "Use Template" -> Press "Add"
    (Also, it's very easy to duplicate the same task by clicking "add as template" in the last step)
    
you can do

    "Template" -> Select a template -> "Add to Task"

where the "Add to Task" button directly adds the predefined task to the active task window. I think this is simpler and more consistent.

2. 

Also, I think removing "New" -> "A task from predefined template" is a better choice. Now, if you want to use this, that means you have to do the following:

    "New" -> Press "A task from predefined template" -> Press "Use Template" -> Press "Add"
    
while this can be done with

    "Template" -> Select a timplate -> "Add to Task"
    
as I previously mentioned. This not only has the benefit of being able to add a template in a shorter period of time, it also makes the UI in "New" menu (and the dropdow menu next to it) less cluttered with unnecessary elements and hence less confusing.

What do you think?

Satoshi

-------------

I didn't know that the review process of lauchpad translation takes so much time. It's sad, but gnome translation page simply isn't a replacement. There's nothing to "use" there, unlike lauchpad.

Oh, wait, what I wrote above applies only to recurrent tasks... It may not be possible to change only the recurrent task part. In that case, please ignore the post.

Satoshi

(In reply to comment #62)
> Oh, wait, what I wrote above applies only to recurrent tasks... It may not be
> possible to change only the recurrent task part. In that case, please ignore
> the post.
> 
> Satoshi
> 

Hello

Yes, one-time tasks are the reason I have made the behavior like this. And to keep it consistent it is like this for recurrent tasks as well. (although it is possible to only do this for one-time tasks). I can also imagine that an template often will be used not as it is, but as a base for individual, different, tasks. Of course not always, but we would have to choose and I think it is an important enough point.

I left the 'Add as template' button there to keep the editor as similar to the original as possible and to make it easy to create templates derived of an already existing template.

Thanks for the feedback!

- gaute

Gnome-schedule 2.0.0 has been released!

Download: http://downloads.sourceforge.net/gnome-schedule/gnome-schedule-2.0.0.tar.gz

Thanks for all help!

- gaute

Created attachment 109452 [details]
Japanese Translation of GNOME Schedule UI (obsolete)

Hello,

I created a po file for Japanese translation of gnome-schedule UI, but don't know how to make gnome-schedule recognize it.

This is what I've done so far:

(1) create ja.po and using gtranslator
(2) create .gmo file with the following command:
    $ msgfmt -o ja.gmo ja.po
(3) $ sudo cp ja.gmo /usr/share/locale/ja/LC_MESSAGES/gnome-schedule.mo

All steps went well, but when I execute gnome-schedule, I get the following warning:

====================================
(gnome-schedule.py:15719): Gtk-WARNING **: Locale not supported by C library.
        Using the fallback 'C' locale.
lang.py:68: Warning: Locale not supported by Python. Using the fallback 'C' locale.
/usr/local/share/gnome-schedule/gnome-schedule.py:68: GtkWarning: locale not supported by C library
  pr = gnome.program_init ("gnome-schedule", config.getVersion(), properties=props)
====================================

Although gnome-schedule works fine, I see no translated strings. Could you tell me what I should (or should not) do to resolve this locale issue? The ja.po file is attached to this message. Thanks.

- Satoshi

(In reply to comment #65)
> Created an attachment (id=109452) [edit]
> Japanese Translation of GNOME Schedule UI
> 
> Hello,
> 
> I created a po file for Japanese translation of gnome-schedule UI, but don't
> know how to make gnome-schedule recognize it.
> 

Hey, great! Ill add it to the repository when i get back home, in a couple of months. what you need to do is to add it to configure.ac (look for the variable with lots of country codes and add the japanese as well) and rebuild gnome-schedule from sources, starting with running ./autogen.sh

you only need to add the .po, the other one is created automatically by the build system.

greetings from bali (hey thats not so far from japan..)

- gaute

Created attachment 109509 [details]
Updated Japanese Translation

Awesome, autogen.sh did the trick. I first did configure/make/sudo make install, and maybe that's why it didn't work as expected. Now I updated some of the translated strings, so please use this version instead of the former one.

Enjoy your stay in Bali!

- Satoshi

Comment on attachment 109452 [details]
Japanese Translation of GNOME Schedule UI (obsolete)

This file is now obsolete.