GSD5 Release 0.3beta

[Roma Hicks]

Getting-Stuff-Done 5 (GSD5) Plugin

Version 0.3beta

Introducing GSD5 v0.3beta!  I posted this a few days ago an the GTD group but it has to be approved before posted.  It has been a few days so I will post it first here.

Download: http://gsd5.tiddlyspot.com/

Added Features

• A References list. Provide a means of viewing references without going through the project tiddler.
• The pseudo-realm 'all'. Allows all actions and project to be viewed at once regardless of assigned realm.
• Allow the user to toggle the display of the realm selector on the Dashboard.

Corrected Bugs

• Newly created action/projects/contact/reference/realm trigger autosave.
  
• Projects and actions that are marked completed trigger autosave, after dependent actions/projects are properly resolved.

Bugs/Issues

Any bugs/issues please visit the projects page at:

https://github.com/roma0104/gsd5/issues

[Tobias Beer]

Thanks for sharing, Roma.

Looks very tidy and interesting.

Best wishes, Tobias.

[Danielo Rodríguez]

Hello Roma,

Why not publishing it here first? You have an huge amount of fans here. This group is also the best place to collect developers to your API-like system. I'm glad to see you continue working on this awesome project. I can't wait to see how it looks integrated with other awesome ones such the visjs felix project.

Regarding backwards compatibility... are the field names the only change? shoud I update my current copy manually?

Regards.

[Tobias Beer]

Hi Roma,

How does this relate to...

https://groups.google.com/d/msg/tiddlywiki/PaqBfARpbgQ/fswvzrdhXyYJ

?

The thing is, the site referenced on that other thread has expired, so that it's mildly difficult to relate the different tidbits and links to this work.

In that earlier group post you listed all the features, plugins, etc. which somehow don't seem to be yet mentioned in:

http://gsd5.tiddlyspot.com

Best wishes, Tobias.

[Roma Hicks]

@Danielo 

Thanks, for you interest and feedback.  Yeah the major break is the field names; I cannot think of an elegant way to correct that quickly.  Sorry for the nasty break.

Perhaps opening the html in an advance text-editor and search/replace "gtd_field" with "gsd_field"?  I haven't tried this, better experiment on a copy of your existing file.  Assuming you didn't encrypt your file, or save it as a non-encrypted file first.

@Tobias

That is essentially the same project with a more appropriate name.  I apologise, I dropped that website a bit ago but the initial code commit on github is the first iteration of the project.  Probably should tag that as a release too.

Thanks for pointing out the features list is missing from the site.  I will get those in.

--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/SQtnSfTHQoI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

--

Roma Quintin Hicks

 

[Danielo Rodríguez]

El lunes, 17 de noviembre de 2014 15:18:25 UTC+1, Roma Hicks escribió:

@Danielo 

Thanks, for you interest and feedback.  Yeah the major break is the field names; I cannot think of an elegant way to correct that quickly.  Sorry for the nasty break.

Perhaps opening the html in an advance text-editor and search/replace "gtd_field" with "gsd_field"?  I haven't tried this, better experiment on a copy of your existing file.  Assuming you didn't encrypt your file, or save it as a non-encrypted file first.

Hello Roma, here is how I fixed this problem:

1. Imported your plugin into a tw 5.1.5
2. Exported all the old tiddlers in JSON  format
   
3. Renamed the fields "gtd_ replaced by "gsd_
4. Imported the file into the gsd5.1.5. This is important because importing in 5.1.4 discards all non-standard fields.
5. Be happy.

I suggest to upgrade your wiki version to 5.1.5 as soon as it is available. 

I love to see that you included some of my suggestions like the all realm and the group by project thing. Maybe can I suggest you to add a count to each dashboard section? Is cool to see how many actions of each type do you have.

Regards.

[Danielo Rodríguez]

Hello Roma,

I'm finding some weird bugs.

• If you create a task from a project it is created as part of the current realm instead of the project realm
• If the correct realm is not selected the project of and depends on information is not displayed. I think this should not depend on realm since it is valuable information for the tag or project displayed.

Regards.

[Roma Hicks]

Thanks Danielo,

I noticed that bug.  It is because everything, at the moment, is set to '$:/currentRealm' and not the parent's 'gsd_realm'.  It should be a quick fix and something I overlooked before pushing everything.  I will get it start work on correcting it tonight.

--

You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/SQtnSfTHQoI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

--

Roma Quintin Hicks

 

[Danielo Rodríguez]

Damn! I wrote a large response on mobile and a connection issue destroyed it!!

El lunes, 17 de noviembre de 2014 17:34:48 UTC+1, Roma Hicks escribió:

Thanks Danielo,

I noticed that bug.  It is because everything, at the moment, is set to '$:/currentRealm' and not the parent's 'gsd_realm'.  It should be a quick fix and something I overlooked before pushing everything.  I will get it start work on correcting it tonight.

Nice to hear that.

Do you have plans to implement any kind of cascade mechanism to reflect changes to parents ?

Regarding the realms issue... would you consider to distinguish between view mode and edit mode within actions/projects? This will address the empty drop-down issue. Do you know what I'm talking about? If you don't have selected the correct realm then important information regarding the current tiddler is not shown. This information should not depend on selected realm since it is contained on the viewed tiddler, no matter the selected realm. 

[Danielo Rodríguez]

I knew I was forgetting something.

Would you consider adding a button (or something else) to turn a task into a project? As far as I saw is just a matter of changing the gsd_type field.

Other annoying thing is not knowing to which project a task belongs when you are selecting it, for example, on depends on. I suggest to order the tasks based on: first current project task, after other projects task with project title.

Other suggestion: Why not displaying sub-projects under its parent project with some indentation? This can be on the Dashboard. And it could be cool to see the task of a subproject within the project view. I suppose those things will be possible implement with your API system, right?

[Seann Hamilton]

Hey Roma, that delay was my fault.  I was away from email, and the group is set up to require approval for one's first post (cuts down on spam).  You shouldn't have that issue ever again.  GSD5 is looking good, btw! 

~ Seann

[Roma Hicks]

The blank drop-list is also a result of the same bug. A similar fix will correct that too. https://github.com/roma0104/gsd5/issues/16

I will get the conversion action/project planned for another release.  I do see the merit of having that built-in.

Can you reword/re-describe your issue with identifying which project a task belongs to?  So far:  Action lists can be grouped by project, per your request.  And action tiddlers have drop-list identifying its parent project; plus a link to jump to the parent project.  Where are you having trouble identifying an action's project?  I keep reading two blended ideas in that paragraph.

The cascade mechanism is not something I am planning on doing.  Not at this time anyhow.  I wanted to avoid recreating a bunch of widgets.  Perhaps tagging might fit the usage you are describing better than changing realms often?  I specifically avoided using tags to power the "behind the scenes" mechanism.  This was to allow users the freedom to tag without cluttering tiddlers with lots of tags that only the GSD5 plugin cares about or can decipher.  

I think of Realms as more static constructs that are assigned at creation and rarely changed.  I rarely decide maintenance on my work vehicle no longer belongs in my Personal realm and instead in my Professional realm; if that is how one uses Realms.  In "Getting Things Done" there is a section about contexts, and this is even implemented in mGSD.  Actions can now be further sorted into categories and be done by context.  Would this meet you requirements better?  If so, I do plan on creating such a feature and has been on the meta-to-do-list as well.  Contexts will probably use the tagging feature of TiddlyWiki as tags would be both important to the plugin and allow quick reference by the user.

Your last suggestion might definitely be a plugin.  It did make me think about another tag-API that would allow such a list, so thank you.

@Seann  Thanks for the update.  I understand the level of security.  I had thought I posted that group a while back but is obvious that I did not.

***

Finally,

I believe I have the blank-list and realm mismatch bug corrected and v.0.3.1b is already available.

http://gsd5.tiddlyspot.com

Thank you to everyone getting involved on the project page.

--

You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/SQtnSfTHQoI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

--

Roma Quintin Hicks

 

[Danielo Rodríguez]

Hello Roma

Just to show you some of my ideas already working I set up a small space: http://gsd5customizations.tiddlyspot.com/

El martes, 18 de noviembre de 2014 16:51:27 UTC+1, Roma Hicks escribió:

The blank drop-list is also a result of the same bug. A similar fix will correct that too. https://github.com/roma0104/gsd5/issues/16

Ok. I will wait for that fix and let you know if I still experiencing any problem.

 

I will get the conversion action/project planned for another release.  I do see the merit of having that built-in.

Nice!

 

Can you reword/re-describe your issue with identifying which project a task belongs to?  So far:  Action lists can be grouped by project, per your request.  And action tiddlers have drop-list identifying its parent project; plus a link to jump to the parent project.  Where are you having trouble identifying an action's project?  I keep reading two blended ideas in that paragraph.

Hello, maybe you're right and I blended two ideas. What I was triying to express is, when you are on an action tiddler, and you want to set the depends on field the list you get is an inmense list of task. What I propose is to use optgroups to group task by project. I made a pull request with my proposal:

https://github.com/roma0104/gsd5/pull/24

Even if you don't want to implement it that way in the core, I created some plugin-like add-in. The problem is that I can not remove the current one without editing the shadow-tiddlers. You can see this customization on the mentioned space.

 

The cascade mechanism is not something I am planning on doing.  Not at this time anyhow.  I wanted to avoid recreating a bunch of widgets.  Perhaps tagging might fit the usage you are describing better than changing realms often?  I specifically avoided using tags to power the "behind the scenes" mechanism.  This was to allow users the freedom to tag without cluttering tiddlers with lots of tags that only the GSD5 plugin cares about or can decipher.  

I also like your "avoid tags" politic. The implementation seems cleaner.

 

I think of Realms as more static constructs that are assigned at creation and rarely changed.  I rarely decide maintenance on my work vehicle no longer belongs in my Personal realm and instead in my Professional realm; if that is how one uses Realms. 

Your right, and maybe my problem comes from the fact that I was using realms in the wrong way.

 

 Actions can now be further sorted into categories and be done by context. 

How?

 

Would this meet you requirements better?  If so, I do plan on creating such a feature and has been on the meta-to-do-list as well.  Contexts will probably use the tagging feature of TiddlyWiki as tags would be both important to the plugin and allow quick reference by the user.

Yes, it will fit better my use case.

 

Your last suggestion might definitely be a plugin.  It did make me think about another tag-API that would allow such a list, so thank you.

 Actually I setup a small list-view using your plugin mechanism. You can see it at the mentioned tiddlyspace.

[Roma Hicks]

Just to show you some of my ideas already working I set up a small space: http://gsd5customizations.tiddlyspot.com/

Yeah I think that might work great for a plugin.  I don't know if that might belong in the core; I want to treat the core more as a bonsai tree.  Prune any extra but leave it with enough content to produce a beautiful system of plugins that don't look awkward (unless you really abuse it, ha).  But I am very interested in seeing how editing shadow tiddlers from the gsd5 plugin works.  To my knowledge, you cannot control plugin loading order and I am not sure even what order boot.js even does it in.  Ideally I would rather see a good API that allows multiple plugins without overwrites for obvious reasons.

The blank drop-list is also a result of the same bug. A similar fix will correct that too. https://github.com/roma0104/gsd5/issues/16

Ok. I will wait for that fix and let you know if I still experiencing any problem.

So you know, I noted it at very bottom of my previous post.  No fanfare.  I patched that and the build is already up as v0.3.1b. 

 

Can you reword/re-describe your issue with identifying which project a task belongs to?  So far:  Action lists can be grouped by project, per your request.  And action tiddlers have drop-list identifying its parent project; plus a link to jump to the parent project.  Where are you having trouble identifying an action's project?  I keep reading two blended ideas in that paragraph.

Hello, maybe you're right and I blended two ideas. What I was triying to express is, when you are on an action tiddler, and you want to set the depends on field the list you get is an inmense list of task. What I propose is to use optgroups to group task by project. I made a pull request with my proposal:

https://github.com/roma0104/gsd5/pull/24

Even if you don't want to implement it that way in the core, I created some plugin-like add-in. The problem is that I can not remove the current one without editing the shadow-tiddlers. You can see this customization on the mentioned space.

 

I think that might be a usability improvement and could benefit the core in general.  I will try it out and consider it.

 

 Actions can now be further sorted into categories and be done by context. 

How?

Excuse me, I meant conceptually, from the reading in the book.  I haven't implemented it yet.  That would be the goal of issue #15.

Your last suggestion might definitely be a plugin.  It did make me think about another tag-API that would allow such a list, so thank you.

 Actually I setup a small list-view using your plugin mechanism. You can see it at the mentioned tiddlyspace.

The ProjectViewBody isn't API ready yet.  It is still hard-coded together.  I want it more like the Dashboard.  In this situation you would simple tag your new Subproject list with the right tag and... it is in the ProjectViewBody.  Might need some more options so we can hide the stock Subproject.