TaskPaper's comments

Ah, my mistake. I should ha...

Joshua Choi — Wed, 27 Aug 2008 18:30:43 -0500

Ah, my mistake. I should have checked before I posted.

In any case, though, Jesse said that there should be an "option for printing entry handles". I think this deserves a preference—it's simple, probably easy to implement, and it sort of validates the purpose of including an archiving feature. The user shouldn't have to manually do a search (or move archived tasks to another file) every time she prints her todo list.

It's more of a nuisance than anything, and it's not that urgent. But for me personally (and other people who physically print their todo lists), it'd be a simple, easy boon.

[http://hogbaysoftware.com/...

Brown — Wed, 27 Aug 2008 15:37:20 -0500

http://hogbaysoftware.com/forums/taskpaper/topics/905HideArchive

Ah, okay. Then 53 sounds li...

Eiren — Mon, 25 Aug 2008 16:04:11 -0500

Ah, okay. Then 53 sounds like the stabler of the two. Thanks. It's working okay for me presently. Looking forward to trying a post-55 build for the latest improvements in guts and good looks.

Thinking this through a bit...

jesse — Mon, 25 Aug 2008 13:48:59 -0500

Thinking this through a bit more... I've decided to get some external input. The competition idea seemed fun, but I don't think lots of different voices will really help in this case. Instead I've decided to just get some outside input on the design from someone who doesn't know anything about TaskPaper.

Heather Rivers has agreed to take a look at the problem. In the weird world of the internet I don't really know anything about her, but I'd come across her tumblr themes a few times and really liked them, and she responded first to my email. So with luck in a week or two she'll throw some new ideas into the mix.

In the meantime I'm going to try to forget about visual design issues, and get some more of the underlying code working.

In general Dev 55 works OK,...

Antonella — Mon, 25 Aug 2008 13:32:33 -0500

In general Dev 55 works OK, but there are a few things that I like less than in Dev 53, especially from an efficiency/workflow point of view.

I guess I like the app appearance more than the piece of paper appearance, and I like the search box that looks a search box, and buttons that look like buttons. It just helps me find stuff more easily.

On Tabs vs Views: I understand your reasoning, Jesse, but the current Views seem less efficient than the old tabs. I noticed that you have keyboard shortcuts for views (same as you had for tabs, but I never had the need to use them when I used tabs). Tabs put other views just one click away, and they function as a reminder of what you are working on, while the views in dev 55 are hidden. This is why tabs work better than views for me. I can see which tabs I have open and move quickly from one to another when needed both with mouse and keyboard.

Suggestion: If you keep a shortcut for next view, can you make it 2 keys rather than 3 ( Apple-Shift-} )? Againm, an efficiency issue.

Position of tools: I just noticed the distance between the search box and the other tools (projects, tags, actions, and views). Using a medium size monitor, it takes a lot of mouse travel to move from one area to the other. Again, I know that you can do most of it from the keyboard, but the GUI should still be designed to maximize efficiency. I realize also in the previous version search and tools were on the opposite side of the window, but now that there is more functionality packed in the toolbar, it seems to bother me more.

I "think" 54 was the first ...

jesse — Mon, 25 Aug 2008 13:28:39 -0500

I "think" 54 was the first version with the new UI. 55 was just a minor update. I think that's how it was anyway.

Okay, I opened Console.app,...

Henrik Christiansen — Mon, 25 Aug 2008 12:58:00 -0500

Okay, I opened Console.app, and it looks like cocoAspell is the bad wolf here. When I disable cocoAspell everything works fine, but when the dictionaries are active, it lags.

This is my output from Console.app: http://pastie.org/259603

Anyways, I solved the problem by simply deactivating cocoAspell. I didn't figure out how to use it properly with Firefox 3, so I guess it's no point in having it enabled.

Thank you very much, Jesse....

Eiren — Mon, 25 Aug 2008 12:34:45 -0500

Thank you very much, Jesse. To exchange in my own small way, I'll commit to trying each new development build which I become aware of and using it if I can limp by with it.

You recommend 53 over 54?

That doesn't sound like a n...

jesse — Mon, 25 Aug 2008 12:30:36 -0500

That doesn't sound like a normal performance problem. It should be fast unless maybe you have a really big file, but 25 lines is a really small file. I just tried TaskPaper 1.0 on leopard and for me those tag popups are instant. You might be able to work around the problem by just unchecking "Auto-complete tags when typing" in the "Text Editing" preference pane. You'd lose that feature, but losing it is probably better then a 5 second delay.

Few other thoughts:

do you have any third party haxies installed? Try uninstalling them.
if you aren't sure about haxies, try creating a new fresh user account, and try the app in that account.
if you open Console.app does it print any errors when the freeze happens?

You can also try the latest 2.0 development version. And see if the problem still happens there.

Jesse

I don't really want people ...

jesse — Mon, 25 Aug 2008 12:23:59 -0500

I don't really want people using version 53 since that's not what I need feedback on, but I understand that if for some you can't read the default fonts then it's kinda sucks having to go back to 1.0 after helping me with all the testing. So here's the plan. Here's a link to version 53. I'll leave it up for a while, but in general I don't plan to provide access to old development version. So in the future please just keep the old copies yourself if you think you might want to go back. Here's a link to 53