Not sure but sometimes errors like this are caused by an action or a project
has a single or double quote or a square bracket character in it's name.
On Wed, Aug 4, 2010 at 1:06 AM, d...@emu wrote:
> The mGSD "Next and Waiting Actions by Context Single Col" view shows
&g
uot;Next Actions" in the mGSD "Next and Waiting Actions
> by Context" view. All I see are "Waiting" actions. I suspect there is
> a bug in the code, but I am not sufficiently versed in tiddlywiki
> javascript to fix it without investing a lot of time. Has anyone else
>
The mGSD "Next and Waiting Actions by Context Single Col" view shows
an "Error in macro <>" at the top of the window. Does anyone
know what that's all about and how to fix. Thanks.
--
You received this message because you are subscribed to the Google Groups &quo
I do not see any "Next Actions" in the mGSD "Next and Waiting Actions
by Context" view. All I see are "Waiting" actions. I suspect there is
a bug in the code, but I am not sufficiently versed in tiddlywiki
javascript to fix it without investing a lot of time. Has any
that's what i ' looking for
many thanks
On Dec 25, 2:55 pm, Erlend Leganger wrote:
> 2009/12/25 himeary
>
> > hi
>
> > is there a way to give a date to a Waiting Actions ,It's an expected
> > date for others to finished their task .
>
> > usi
2009/12/25 himeary
> hi
>
> is there a way to give a date to a Waiting Actions ,It's an expected
> date for others to finished their task .
>
> using Tickler for this is a little confusion . and now I'm putting
> the date in the title of the action .. Is ther
hi
is there a way to give a date to a Waiting Actions ,It's an expected
date for others to finished their task .
using Tickler for this is a little confusion . and now I'm putting
the date in the title of the action .. Is there any "Better" way to do
this?
--
You received
"Waiting actions by person"
Think of it more as
Waiting Actions (grouped by person).
Try adding a bunch of waiting actions and give some of them an associated
contact then it might make more sense.
A long time ago it used to be Waiting Actions by Context but then someone
suggested th
I can't make sense out of the "waiting actions by person" list and
tiddler creation at the bottn of a project tiddler.
I was half expecting it to give me list of contacts I have. However,
it simply lets me create a tiddler with a Waiting tag. Once created I
can of course t
Well, as long as we're messing with core code, here's a quick and
dirty hack. Find the line in multiSelectTag that reads:
if(includeNew)
replace it with
if(includeNew && tag != "Action")
Voila! No more New Action...
As for the "dependent action" problem, could you create a dependent
action of
I just took a look at the wiki and it seems all correct. Arma, you say
with the code at the bottom that it is not being tagged correctly as
Future? It's in the list of tags... do you have the newest version of
TW?
As for removing the "New Action..." prompt: I see a reference to
includeNew in mult
OK, a few haphazard thoughts:
1) I think I meant !Tickler instead of !Tiddler. I get those confused
all of the time. =P TaggyTagging shows a list of all tiddlers tagged
with the title of the current tiddler. In other words, if any actions
are dependent on a certain action, they will be listed and
Hi there,
thank you for helping me out with the wiki pre-tag, bkh!
I adjusted the other code.
But I am still not really sure about the last part.
As Kralik mentioned, he still includes
_
To show dependent actions, add the following to TitleButtons under !
Action and !Tiddler (also ri
Thanks Arma and Mat!
I looked at it and I found out about the pre tag. That seems to allow
pre-formated text and ignore the code. There is the nowiki tag for
inline things you don't want wikified. There is also a source tag
that would add fancy color to the code, but I wasn't sure what
languag
Hi there again,
I would like to make an additional comment.
The "instructions" in the wiki are only readable in edit-mode.
I just tried to improve on the final step (I talked about just some
minutes
ago) but I am so unfamiliar with this wiki-markup that I was not
really getting
anywhere... I help
Hi there,
thank you all very much!!
This is just what makes mGTD even more useful.
I have just two remarks:
1) On the wikipage
>
> > If you're gonna write a summary, don't do it here -- do it on the
> > wiki:http://tiddlywiki.org/index.php?title=MonkeyGTD/Customization_Guide/W...
>
the instruct
Ok, trying to put in my two cents, I put it where Simon appointed.
I'm not very good with mediawiki though, so the formatting it
horrible. Factually I believe it sums up all that has to be done, but
anyone is of course free to make it more readible there.
:-)
/Mat
On 8 Apr, 12:10, Daniel Bair
On Wed, Apr 8, 2009 at 5:05 AM, bkh wrote:
>
> I'm wondering if someone could summarize all the steps it takes to
> implement this feature with the most up to date instructions and code
> (including that curly close bracket thing)?
If you're gonna write a summary, don't do it here -- do it on th
I'm wondering if someone could summarize all the steps it takes to
implement this feature with the most up to date instructions and code
(including that curly close bracket thing)? I'm very new at this and
having a hard time following the bits and pieces of instructions in
the chain of messages.
ot;Future"
> actions should be auto-set to Next. (Less serious is that also Done
> actions seem to get an extra Next).
>
> :-)
>
I think the problem you are seeing is in the original
SequencedActionsPlugin design. I fiddled with it a bit and here's what
you could do to ma
This is getting GREAT
I did a little testing and found the following; If an action B is set
as dependant on A, but B is marked as "Waiting for". Then, finishing
A, auto-sets B to *both* Next and Waiting for. I think only "Future"
actions should be auto-set to Next. (Less serious is that also
> Another thing; it is a bit inconsistent now in that the default for
> created actions is 'next'. I suggest a quick-fix(?): Setting a
> "Depends on" pretty much by definition means that an action is
> "Future" and IMO should be changed into that by default (if it was
> tagged Next, but not Someda
For the record, in the last code provided by Kralik, the final "}"
becomes hidden because of googlegrups "hide quoted message" feature.
I.e the whole thingy should end with a }
Another thing; it is a bit inconsistent now in that the default for
created actions is 'next'. I suggest a quick-fix(?)
DOH! disregard my last post.
I only meant; Thank you Kralik!
:-)
On 2 Apr, 13:23, Mat wrote:
> Kralik - fantastic! I think this may just be fully usable now!
>
> Does anyone know how to make the "Depends on list" only show the
> actions in the specified project (if any)?
>
> Thank you!!!
>
Kralik - fantastic! I think this may just be fully usable now!
Does anyone know how to make the "Depends on list" only show the
actions in the specified project (if any)?
Thank you!!!
On 25 Mar, 23:33, Kralik wrote:
> Even better than the last tweak (though you could certainly use both),
> he
On Mar 25, 6:49 pm, "Jorge A. Ramos M." wrote:
> Excelent! Thank you,
>
> There is only one way to show the actions that belong only to this project
> and not to show all Action of the mGTD?
Well, despite my previous post, I went and figured out a way anyway.
=P
With this code, dependent actions
> There is only one way to show the actions that belong only to this project
> and not to show all Action of the mGTD?
I don't know off-hand, though I did try to figure it out. This was the
quickest solution I could whip up.
I suggest that if you use the "dependent action" toolbar button, that
y
Excelent! Thank you,
There is only one way to show the actions that belong only to this project
and not to show all Action of the mGTD?
On Wed, Mar 25, 2009 at 4:33 PM, Kralik wrote:
>
> Even better than the last tweak (though you could certainly use both),
> here is a GUI-dropdown addition tha
Even better than the last tweak (though you could certainly use both),
here is a GUI-dropdown addition that lets you assign an action a
dependent action. It's pretty easy:
1) Edit MgtdConf and add "Action", to the tagsToIndex list.
2) Edit TitleButtons and add the following code under the !Action
I just installed and tested - this is a great plugin!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "GTD
TiddlyWiki" group.
To post to this group, send email to GTD-TiddlyWiki@googlegroups.com
To unsubscribe from t
> I love the concept of SequencedActionsPlugin but in practice use I've
> found it too iffy with all the additional manual work it requires to
> write or copy-paste the names of actions as tags etc etc.
>
> For it to be practical, I say it would have to be integrated more -
Humbly asking if ther
On Wed, Jan 14, 2009 at 8:17 AM, Mat wrote:
>
> > I like the idea of a drop down List. The TaggerPlugin suggested by Mat
> > may help. But i think that the list of tags should be filtered
> > somehow.
> >
> > E.g. only Tags that are used together with Action- or Tickler-Tags
> > should be display
I'm using it. It's fabulous.
I like the idea of including a drop down so that dependencies can be set
without editing the tiddler manually. You'd want a multi-select list box,
if such a thing exists in MonkeyGTD, because some actions depend on more
than one prior action.
On Mon, Jan 12, 2009 at
Carsten,
I'm excited about this. Nice work. As for Jim's comments, I think this seems
lightweight enough so you can just ignore it if you don't want to use it.
When I get a chance I will have a play with this and hopefully include it in
MGTD. I have some ideas about the UI also, something similar
On Tue, Dec 30, 2008 at 7:04 AM, jdunham wrote:
> [...]
> I tested some circular dependencies (e.g. Action1 depending
> on Action5 in your demo), and nothing broke, which was good.
> I don't think there is a good way to handle this, but at least the
> TW didn't go into an infinite loop.
You don'
Carsten:
Brilliant plug-in. Thanks for the Christmas present!
I agree that rather than turning this into a project management mess,
it just automates a very repetitive task. I think this will let me
keep more stuff out of my next actions, since urgent follow-on actions
won't have to wait for t
Hi Jim,
thank you for your comment. Yes your are right, the right order of
Actions is more related to Project planning.
But for me it is just a convenience feature. There are Projects (in
the GTD meaning of a project) where you exactly know what you have to
do after one Action. Normaly you finis
Hi,
Well done on the coding. Action dependancies are outside of GTD
though, and within the realm of project planning. There are loads of
free and commercial project planning tools on the market, that will do
dependancies, critical path ananlysis, "float", resource management
etc. MS Project
Hello,
i converted my "Hack" to a complete plugin. I Uploaded a Demo into
this group as file: monkeygtd-SequencedActionsPlugin-demo.zip (
http://gtd-tiddlywiki.googlegroups.com/web/monkeygtd-SequencedActionsPlugin-demo.zip
) The html-Upload did not work, so i added the zip-File, that can be
downl
Hello,
i modified my monkeygtd to support "sequenced"-Actions. I use the
normal Tag-Feature to Control the sequence of the actions. When i
create an action that depends on another action i just "Tag" it with
the name of the first one, and set it to "Future". When the first
Action is marked as "Do
40 matches
Mail list logo
