Add your own alternative version
Stats
41.7M views 412.3K downloads 3.4K bookmarked
Posted
3 Nov 2003
|
Comments and Discussions
|
|
Ok, that should work...
Then is it possible to create a keyboard shortcut to assign a specific tag (like this "parent") to a task? Or to create (some) new tasks with such a tag already there?
Thank you, guys, M.
modified 5-Feb-16 4:40am.
|
|
|
|
|
To automate this, you can create a User-Defined Tool, which in this case is just a command-line to do something to the current task.
See the wiki on UDTs[^] and the Command Line[^]. This UDT would just assign the a tag. You can create a toolbar button and/or hotkey to activate the UDT.
I'm intentionally providing a minimal amount of info so that you can read up on these topics and learn how it works. If I just wrote it out here there wouldn't be any residual benefits. But please do ask questions if required (probably in a separate thread on UDTs...).
|
|
|
|
|
Hello.
Kanban is already implemented ? I can not find any option to turn on this board
Tnx.
|
|
|
|
|
Dan is building Kanban into v7.1. You can get more info about the latest Development Release here[^].
|
|
|
|
|
|
hmmm- download works fine for me.
|
|
|
|
|
Works fine for me too (Chrome).
|
|
|
|
|
I can also get it with Firefox and IE11. The issue seems to be PC-specific. Perhaps you have anti-malware software that's preventing the download. Try in this order:
- Right click the link and if you have a "Save link As", use it.
- Try a different browser.
- Try disabling A/V software for 1 minute.
- Try a different device/PC.
|
|
|
|
|
Hi guys,
We have observed a somewhat puzzling behavior in conjunction with updating our TDL tool from release 7.0.11 to 7.0.12 / 7.0.12.1. It appears that the 'encoding' is somewhat strange - at least we don't fully understand how it works. From the raw TDL files, we understand that TDLs are stored using encoding "windows-1252":
<?xml version="1.0" encoding="windows-1252" ?>
In our daily work we parse the raw TDLs to transfer some of its content to wiki pages. We use python and/or XSLTs for this. Up to ToDoList release 7.0.11 we never had any problems with this. However, following the upgrade to 7.0.12 our scripts wouldn't work anymore - the XML parser failed to load the XML due to encoding problems. When changing the encoding reference within the raw TDL file from "windows-1252" to "utf-16" everything work fine again.
This led us to believe that the actual encoding used by ToDoList is actually "utf-16" rather than "windows-1252", but of course we are not sure. We also changed the option on the Import/Export preference page to "utf-16", but we are not sure either if that matters in this context at all.
Questions:
Is it possible that release 7.0.12 had an encoding problem which was solved with 7.0.12.1? (I believe, Dan reported some bugfix along these lines - we're just not sure what was wrong and what got fixed). If so, how can we fix TDL files saved with 7.0.12 (potentially inconsistently encoded)? Shouldn't saving them as a new file ("Save As") under 7.0.12.1 do the trick? It doesn't appear to be the case, as our parser is still thrown off with the following error message:
Using parser com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser
Building tree for file:/C:/temp/EF6xx_BCI_Standup.xml using class net.sf.saxon.tree.tiny.TinyBuilder
Error on line 2 column 1 of EF6xx_BCI_Standup.xml:
SXXP0003: Error reported by XML parser: Content ist nicht zulässig in Prolog.
org.xml.sax.SAXParseException; systemId: file:/C:/temp/EF6xx_BCI_Standup.xml; lineNumber: 2; columnNumber: 1; Content ist nicht zulässig in Prolog.
Changing the first line of the TDL file to
<xml version="1.0" encoding="utf-16">
appears to fix the problem - the XML parser now manages to read the TDL and update our WIKI:
Using parser com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser
Building tree for file:/C:/temp/EF6xx_BCI_Standup.xml using class net.sf.saxon.tree.tiny.TinyBuilder
Tree built in 28.413938ms
Tree size: 4881 nodes, 305565 characters, 13617 attributes
Execution time: 170.567598ms
Memory used: 13050360
NamePool contents: 86 entries in 84 chains. 6 URIs
Anything else we could/should be doing instead of this workaround?
By the way, in the same context we observed that TDL sometimes creates a strange "_temp" file. For example, from an original file called "helloWorld.tdl" we get a miraculously created additional file "helloWorld_temp.tdl". Any explanation for where this file is coming from and what it is used for?
We appreciate any help anyone might be able to offer. Thanks.
|
|
|
|
|
I don't know about the _temp file, but about the encoding format, you should update to 7.0.12.1 which should temporarily reverse/fix the issue. (At least for the .tdl file, I don't know if exports are affected.) See this Google+ note[^] on the topic (similar notes were published here, in Facebook, LinkedIn, Twitter, and the Google Group). If what your seeing is not explained by that, or not fixed by 7.0.12.1, please clarify here or in the Google Group.
We created the ecosystem of social media sites to allow users to keep informed where They prefer to get news. I strongly suggest that everyone subscribe to at least one site to get frequent updates about the software. In ToDoList itself, under menu>Help, you'll find links to all sites for your consideration. You don't need to subscribe, really, just click one of those links once per week or so to see what's happening. We promise not to be trivial or annoying.
|
|
|
|
|
Hi fwornle
Thx for your comments.
fwornle wrote: TDL sometimes creates a strange "_temp" file. Any explanation for where this file is coming from and what it is used for? It's a temporary file used during the saving process, which gets deleted upon the save completing successfully.
If you have other processes that might be interacting with this file (eg. DropBox) then this can interfere with the deletion.
fwornle wrote: It appears that the 'encoding' is somewhat strange Yes, I changed TDL to save tasklists as UTF-16 as part of a migration plan to UTF-8, but failed to change the XML header to match.
So manually updating the XML header is all you need to do to fix the issue. I will also fix this in 7.0.13.
I'm sorry for the inconvenience this has caused you.
modified 28-Jan-16 20:28pm.
|
|
|
|
|
|
Comments welcome on the new wiki page[^] for translators and other speakers of other languages.
Volunteers to translate ToDoList into new languages are certainly welcome.
Anyone want to try one of these?
- a localised dialect of French
- Arabic dialects, Urdu, Farsi or other languages derived from that alphabet
- Polish
- Korean
- an update for Japanese, Hebrew, or Slovak
- Spanish (Spain) needs an update, what about Spanish (Mexico)
- Portuguese and related dialects
If there were room in the UI, I'd suggest Pig Latin, L33t, Klingon, or maybe Morse code. Alas, we'll probably need to settle for the more popular ones...
|
|
|
|
|
Hi iamstarbuck,
I can do the french part. I'm a french native.
Alexandre
|
|
|
|
|
|
Bonjour Alexandre,
J'étais en déplacement et je rentre à l'insdtant.
Jusqu'a maintenant, j'ai été le principal traduxteur (et presque le seul). Celà fait quelques mois que je n'ai actualisé la traduction mais je vais avoir un peut plus de disponibilités.
Je pense qu'il va y avoir un gros boulot de traduxtion des pages wiki. qu'en dit tu ?
PS: de l'aide est toujours la bienvenue.
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
Pardon, je dois écrire en anglais. We're not planning to translate the wiki, not yet anyway. It's still in development and as soon as someone translates a page it could be radically changed. Even when "complete" (it never will be since the software is always being enhanced), I think it would be easier for people to run pages through Google Translate or similar services to get a rough idea of what's in the pages. Then they can ask questions if required. Yes, I'm very familiar with the limitations of that technology. But I think using that and working around the limitations is better than wasting a lot of effort on dynamic content. We can re-visit this topic later.
For now, all focus is on translation of the software using the CSV files, as documented in the wiki.
|
|
|
|
|
Hello.
Pleas send me source for translation i will try Polish . korycki.sylwester@outlook.com

|
|
|
|
|
Dziękuję Firdea! Merci Alexandre!
All of the information is on the wiki page for Internationalization[^]
If you have any questions you can post them here or in the Google Group and either Peter or I will respond.
Please note: The "Clean Up" button and automatic file update is not working in v7.0.12. Please learn how the process works, do some translations, and ask questions if necessary. I'm sure Dan will fix the issues soon to help with your effort.
As you will see in the wiki:
* Backup Often
* Copy your file after every update.
* Take no chances of losing your work
|
|
|
|
|
|
Hello guys
I like to use the different views allowed by Todolist :
- All tasks
- Incomplete tasks
- Completed tasks
etc
But it's a bit of a hassle to set the right sort each time for a given view.
For example, I like to sort "All tasks" by priority and start date.
But then for completeed tasks, it makes more sense to sort them by completed date.
It would so nice that "Todolist" keep in memory the sort of each view, and even the sort of custom Searches. So that we don't have to set the right sorts, again and again when swiching between views.
Kind regards
Alexandre
|
|
|
|
|
That's potentially a big change so I'll look at it for 7.2.
|
|
|
|
|
Hello Dan,
I can imagine it's not an easy enhancement.
Thanks for considering it.
Kind regards
Alexandre
|
|
|
|
|
I really appreciate command line options as they make it easy to call ToDoList from my Autohotkey scripts.
However, are they command line options for custom task attributes? I can't find it in the documentation?
Regards, Nils
|
|
|
|
|
Thx Nils, I'll add that to 7.1.
modified 27-Jan-16 1:21am.
|
|
|
|
|
|
General News Suggestion Question Bug Answer Joke Praise Rant Admin
Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.
|
|