Project Templates
 

Useful or not useful?

I vote useful - I would love to have project templates, especially for things like vacations where they don't repeat on a regular or predictable basis.

Is there another thread where this is described in more detail? I'm not sure what you mean by a project template.

Okay, I thought the name was pretty self explanatory, but here it goes.

Being able to set up a project, and then save it as a template, and then to create a new project using that template, and it makes a project automatically populated with the templates tasks tasks, like for a vacation template: Stop the mail, Give spare key to neighbors, Take dog to kennel.

Something that you can expand on with tasks unique to the situation, but has your own prebuilt scaffolding for the project.

1 vote yes ... maybe
 

I've already created some for my own use (lesson planning, trip packing, etc.) - any automation would be great. But then again, since I can kind of do it myself, maybe the omni folks should spend their time working on things that I can't do for myself.

I can see that being pretty useful. I don't see myself using it that much because most of my projects are unique, but I can definitely see the utility of such a feature.

[QUOTE=MEP;18577]I can see that being pretty useful. I don't see myself using it that much because most of my projects are unique, but I can definitely see the utility of such a feature.[/QUOTE]

That's precisely my situation. My wife would love it though -- she has lots of checklists for things like packing.

[QUOTE=pjc;18587]My wife would love it though -- she has lots of checklists for things like packing.[/QUOTE]

Checklists! That's really what they are isn't it. I use checklists all the time (OmniOutliner) but most of them aren't projects. It would be cool if there were a way to import a checklist from OOP to OF. I smell Applescript in the air.

[url]http://www.rose-hulman.edu/~clifton/software.html[/url]

You mean like those?

Curt did an awesome job, the only thing I would ask OmniGroup to do would be to wrap it into native functionality.

Other than that, you should check out the AppleScript.

BZ

Here's another thought: what if you had a project called "Templates" which was permanently on hold (so you could hide it when you don't want to see it). From there, you could duplicate a template, and drag it whereever you want.
This amounts to a reference topic which arguably could be stored elsewhere. However, this could be more convenient if you use it often.
There's nothing wrong with the Outliner plan, of course--it's nice to have more than one way to do things.
This does beg the question of whether there should be another entry on the projects sidebar called Templates. If it gets added, it might be worth adding a show/hide checkbox in Preferences. Some people might hate it, and this would allow them never to see it.

I find template projects incredibly useful as a freelancer. I have a recurring process that I use for each client's project... a set of recurring tasks with a built in timeline (using due dates offset from a start date). Not every project is exactly the same, but starting from a template I can refine the process each time and learn from past projects. I like the on-hold project solution above, since that's essentially what's going on, but I wouldn't mind having templates as a bonifide feature of OF eventually, since I'm sure the Omni folk would have some really sexy way of implementing it.

Creating a "Templates" folder works extremely well, actually:
[LIST=1][*]Create a folder called "Templates".[*]Right-click on the folder and deselect "Active".[*]Create template projects. [I]You don't need to put them on hold because the parent folder is already marked inactive.[/I][*]Copy your template into an active folder to use (option-dragging works well).[/LIST]Btw, I've submitted feedback to Omni that inactive folders should be greyed out to avoid confusion. Same should probably go for sub-projects.

Dan

I have a related request. Would it be possible to develop a type of list that is non-action in nature--for lists of quotes, phone numbers, gift ideas, standard meeting agendas, etc. etc. etc. These aren't projects. The items don't have start dates or due dates or contexts or anything like that. They're just lists. Now, one may say, "Why do you want OF to handle simple lists?" Because as much of my system as I can put in one place, the more efficient I am. And, in the case of lists like gift ideas, for example, items could be promoted to actionable items by drag-and-drop into a "Next Actions" list. In this case, I would envision a separate item on the sidebar along side "Library" (which, by the way, I suggest could be better named to, say, "Projects" or something like that) called, say, "Lists". What do you think?

I think one of the several list/clipping-management apps already available for the mac would serve you better. There are loads, ranging in sophistication from Stickies and TextEdit through to apps like Yojimbo and DevonThink. Why reinvent the wheel?

[QUOTE=al_f;36671]Why reinvent the wheel?[/QUOTE]

Or even OG's excellent OmniOutliner. If you've never tried it, and you're already using OmniFocus, you'll feel right at home. The similarities are significant.

On the other hand, I can see jonwalthour's point. It's nice having your lists all in one place, using the same organizational tools, key combinations, and user experience with ability to drag items around, etc. After all, OmniFocus is already an excellent "list manager" at its most basic level. So would it really be reinventing the wheel?

I keep some lists in OmniFocus as it is. These are mostly things that I see as actionable at some point in the future, like books I want to read, films I want to see, possible activities to entertain my kids, and even a list of OmniFocus issues I've either reported to Omni Group or that I'm trying to figure out. I keep most on hold so they don't cloud my everyday to do lists. For easy access, I have perspectives set up to open a new window focused on those items.

I see it as kind of an extension of my someday/maybe workflow. It's worked well for me and certainly makes it easy to "promote" items to an actionable status.