Sorry for my poor English.
I've been using the "calendar" plugin. It's great.
Hey boys ... do not kill me for this question but, have you thought about the ability to add "events" in the task list? or would that be asking something that does not correspond TDL. Sorry!
Why I ask?
I use TDL for many different things. One of them is to organize an event of five days (that's what does the event itself). One thing is the task "to organize such an event", with corresponding sub tasks. And another thing is the event itself, that has start date and end date. And I would like it to appear in the calendar in each of the days of the calendar. But ... as TDL works, as I understand, there is no ability to add "events".
I hope you understand the question and, again, sorry if I ask TDL more than appropriate.
TDL is realy fantastic.
Having different types of tasks has been discussed in the past, and the consensus at the time (from memory) was to not complicate things. The current 'Task' can be used as an event (even though the common attributes for a task and an event might be slightly different). Representing different attributes for different types of tasks in the grid becomes problematic for instance.
I appreciate the time taken to write your comment:
I understand the criteria. Sounds good. Actually the only problem to use a "task" like an "event", in my case, it was in the case of an event that lasted several days. Perhaps this could be solved by adding a new property for a task like "Time of execution" or something like this. After all, an "event" is a task that can take several days ...
I know, it may be too complex ... life such as.
You are welcome.
Not sure I follow though. Lots of tasks can take several days (in my case, most do). That is why you have a start and due date.
At the moment the calendar only displays the task on those two days. In future, the calendar will display the task on all affected days in-between, using a bar.
In future, the calendar will display the task on all affected days in-between, using a bar.
With this option I can create two jobs (one of which function as "event"):
1) the task of "preparation" of the event (with infinite sub-tasks)
2) The task of "execution" of the event (ie a convention of several days)
This second task (execution) is what interests me particularly appears in the calendar, and which otherwise could not have done it without this new feature of TDL, calendar. I want to appear because it reminds me that I can not be taking care of other things during those days.
I am currently upgrading my stylesheets to handle the change from attribute to task element of CATEGORY, PERSON etc... This is fine. Could you explain the following to me though.
I was testing my stylesheet on one of the testing tasklists I have, that has very long HTML comments. I used this when you were trying something to try to deal with comments over a certain length losing their formatting...
What I found was that some comments didn't show in the report. On investigation, it seems most of these comments are task attributes (as expected), but one is a task sub-element (unexpected). Is this expected? Is it due to size?
Also, I have noticed reference tasks have no title value. I can't see how it can be represented successfully in the stylesheet. It appears as a blank line. Would it be possible to add the title? I could then add the task name in the line, and label it as a reference (and hence not show any other attributes). Otherwise I need to work out how to skip this type of task.
Actually one other thing you may be able to help with. When dropping out the COMMENTS to the stylesheet output, I can limit the number characters (keeps the report smaller). Doing this to HTMLCOMMENTS doesn't seem to work - truncating the comment leads to random results. Any idea why? Is it that when the HTMLCOMMENT is output, it has tags that get chopped off?
I have got the stylesheets updated. To let you know. It seems when the comments get beyond a certain size, the tasklist saves the comment as a task element rather than as an attribute.
When printing the stylesheet now, the rich text formatting is maintained for these longer comments. So it appears you have fixed the issue.
This is as you expect?
[Edit] Actually on further testing things don't fully match up. I have a large comment (1381 words 4393 characters 25 paragraphs), which is rich text, but saves as a task attribute, and loses its rich text formatting in the output.
Did you see the post where, if you start TDL (6.7) with -g for logging, the temporary tasklists generated for the transform are saved to your Temp folder so that you can inspect them?
ps. I thought I had changed 6.7 to _always_ save COMMENTS and HTMLCOMMENTS as _elements_, but it seems it was a fantasy So I'm going to implement this for A4. That will give you a single way to handle comments.
Could you step me through this please?
As I read this, I add -g to the shortcut target. I then print preview a tasklist, using a stylesheet. I should then find a file appearing in the temp directory on my C drive?
Something is not working, as no file has appeared.
The XML declaration of my old todo.tdl was <?xml version="1.0" encoding="windows-949" ?> and Encoded in ANSI. In this case, iTDL didn't seem to support multi-lingual. So I changed it like this. - <?xml version="1.0" encoding="utf-16" ?> - Encode in UCS-2 little endian
Now it works well.
Anyway.. I've been using for several years, and I'm very satisfied. Today I see iTDL. It's what I want. Thank you.