![]() I use my apps more as thinking tools than list trackers. ![]() That approach definitely has drawbacks, but it also means I don't have an impossible, always growing list of tasks. I have temporary ones that I work off for a while, but I don't often keep a well maintained list of everything. The thing is I'm not that good at todo lists. How does your to-do list look, is there no problem with tasks only growing? People know how to navigate and edit text, so if the entire interface is text then it's all accessible to them without much thought. I think uniformity of the user interface. What are the main advantages of using text-based syntax instead of the standard GUI with a spectacular design? I'm not sure if that represents my main audience or not, since it's not a big percentage of users that participate in the forms. Most people that I interact with in my user forums are quite technical and interested in tinkering with things. In your opinion, who is your main audience, who buys TaskPaper? I think both approaches have benefits, but I find the simple and flexible approach more interesting. I think most apps are most user tasks focused, they provide more structure, but are more complex and less flexible. My goal for an app is to create a world with a few concepts that can be recombined in different ways. Unhappy might be strong, but my preference is for minimal apps. What things have you been unhappy with in other todo managers? ![]() I've ended up programming, but I am at least a bit sensitive to UI designs. In college I did computer science and studio art. I was interested in graphic design and computers in general when in high school. What is your background, how did you start your way in development? To-do manager will suit those who like text interfaces and quick data input via keyboard, as well as those who'd like to adapt all programs to their needs. The functionality of the application is limited only by your desire to read documentation. TaskPaper contains everything you need to flexibly organize tasks. As we are quoting paths to prevent problems with spaces, we need to ensure the paths do not end with a backslash that will escape the path's closing quote and make the command fail.TaskPaper price is $29.99. The additional for %%r is included just to prevent a usual problem using robocopy. This line is retrieved with a separate cmd instance (this avoids a time problem with a for /f reading long lists of data) so the for /f only reads one line.Īs the robocopy lines contain the date, time and file name, to retrieve this last field, we request the for /f to retrieve two tokens: one containing the hour (will be stored in %%a) and the remaining text until the end of the line (stored in %%b) ![]() This timestamp prefixed list (UTF yyyy/mm/dd hh:mm:ss last file write) is then sorted in reverse order to get the last file in the first line. This code uses robocopy to generate the list of files with a timestamp prefix (the switches just request no job header, no job summary, no file class, no file size, timestamp, recursive, no directory list, no directory information copy, include same files, no retry, no wait, don't copy only generate list). Setlocal enableextensions disabledelayedexpansionįor %%r in ("%root%\.") do for /f "tokens=2,*" %%a in ('
0 Comments
Leave a Reply. |