@vovkkk:
> Look at Tomboy: you can change level of item of bullet list by press Tab
> and Backspace or Alt+right and Alt +left.
>
> So in GTG it may be like this
> 1. Ctrl+N, type name of project, Enter
> 2. -, type name of subtask, Enter
> 3. type name of subsubtask, Tab
> And get this:
> Project
> -Subtask
> --Subsubtask
> ----------------------------------------------------------
I think, it is good idea to implement something similar, I've created a
new bug for that. Bug #887089
@Lionel:
> to be able to enter tasks with subtasks and subsubtasks in GTG
> was one of our first idea. And it was even implemented.
>
> Then, we realized that it simply doesn't work because people write down
> tasks in the order they will make it:
>
> - take out the old lightbulb
> - buy a similar lightbulb
> - replace the lightbulb.
>
> The structure should be the following:
>
> 1) Replacing the lightbulb
> 2) Buying lightbulb
> 3) Taking out the old lightbulb.
I think vovkkk showed something different. You are talking about
changing linear structure into that kind of special tree. What about
giving user to ability to see all substructure right in the editor and
to be able to create a complete project from a single window just using
a keyboard? We should discuss this at the separate bug #887089
---------------
@Reda Lazri:
> My whole point was to port to GTK3 and remove the clutter. As for the
> work view, I'm not one of the developers, I'm an end-user. The fact that
> I didn't understand a functionality means it is either badly designed
> or at least no one cared about showing it to the end-users.
>
> Let's say you added an option to import documents using Zeitgeist, you
> don't add a button 'Zeitgeist' in the interface and expect people to
> know what it does, you don't expect people to read documentation either,
> you show them how it works and why you think it's a cool feature INSIDE
> the program.
FYI: Although old famous "nobody reads documentation", GTG provides
nifty tutorial as a set of introduction tasks which is IMHO fabulous
idea. All concepts are described and demonstrated. However, it doesn't
contain all features of development version at the moment.
ad Zeitgeist:
GTG has already got an infrastructure for Zeitgeist support. You are
able to write a backend which export your data into zeitgeist. There is
an option to open a certain task through gtg:// handler in GNOME. The
opportunity waits until somebody grabs those basic block, interconnect
them and then debug and polish them for smooth user experience. (The
most time consuming part)
I personally don't like Zeitgeist because the idea behind it. Some users
love it. Using backend infrastructure it is able to enable/disable this
feature on user request and ship gtg by the wish of a distributor who
can turn it on/off by default.
@vovkkk: ------- ------- ------- ------- ------- ------- ------- --
> Look at Tomboy: you can change level of item of bullet list by press Tab
> and Backspace or Alt+right and Alt +left.
>
> So in GTG it may be like this
> 1. Ctrl+N, type name of project, Enter
> 2. -, type name of subtask, Enter
> 3. type name of subsubtask, Tab
> And get this:
> Project
> -Subtask
> --Subsubtask
> -------
I think, it is good idea to implement something similar, I've created a
new bug for that. Bug #887089
@Lionel:
> to be able to enter tasks with subtasks and subsubtasks in GTG
> was one of our first idea. And it was even implemented.
>
> Then, we realized that it simply doesn't work because people write down
> tasks in the order they will make it:
>
> - take out the old lightbulb
> - buy a similar lightbulb
> - replace the lightbulb.
>
> The structure should be the following:
>
> 1) Replacing the lightbulb
> 2) Buying lightbulb
> 3) Taking out the old lightbulb.
I think vovkkk showed something different. You are talking about
changing linear structure into that kind of special tree. What about
giving user to ability to see all substructure right in the editor and
to be able to create a complete project from a single window just using
a keyboard? We should discuss this at the separate bug #887089
---------------
@Reda Lazri:
> My whole point was to port to GTK3 and remove the clutter. As for the
> work view, I'm not one of the developers, I'm an end-user. The fact that
> I didn't understand a functionality means it is either badly designed
> or at least no one cared about showing it to the end-users.
>
> Let's say you added an option to import documents using Zeitgeist, you
> don't add a button 'Zeitgeist' in the interface and expect people to
> know what it does, you don't expect people to read documentation either,
> you show them how it works and why you think it's a cool feature INSIDE
> the program.
FYI: Although old famous "nobody reads documentation", GTG provides
nifty tutorial as a set of introduction tasks which is IMHO fabulous
idea. All concepts are described and demonstrated. However, it doesn't
contain all features of development version at the moment.
ad Zeitgeist:
GTG has already got an infrastructure for Zeitgeist support. You are
able to write a backend which export your data into zeitgeist. There is
an option to open a certain task through gtg:// handler in GNOME. The
opportunity waits until somebody grabs those basic block, interconnect
them and then debug and polish them for smooth user experience. (The
most time consuming part)
I personally don't like Zeitgeist because the idea behind it. Some users
love it. Using backend infrastructure it is able to enable/disable this
feature on user request and ship gtg by the wish of a distributor who
can turn it on/off by default.