The problem is that there is only one developer and adding more people will bring problems and delays.
That's a known problem in the short run, but on a long running project adding people as "apprentices" usually works to get someone up to speed in less than 3 months. Adding a technical writer would also slow Jeremy down, but it would be really nice to have great manuals. I would expect that the biggest problem would be how to pay for the developers, which is why I suggested raising the renewal price to $40 and calling it all a subscription.
Jeremy has decided to change the way data is stored and like you I am waiting for the end of that re-factoring. I have been told that afterwards, it will easier to implement new functionality.
Cool, any eta on that. And by eta I don't mean a date, "probably second quarter" next year is would be good enough to keep us at bay.
Now if you can come up with a list of urgent functionality which does not require changes into the data model, I can try to push for them. A transaction for moving projects to future (rather than cut and paste) could be one.
I don't know what is going to require a data model change. Most of my issues are in the UI, but I've got enough of a programming background to know that sometimes a seemingly simple task requires a complete rewrite of the back end.
I'd like to see the cut-and-paste model revised a little bit, right now you can only cut a compressed project and the only way you know you have cut it is when you try to paste it. If you paste a second copy of your last paste, then no, you didn't get the new one.
I'm using the future tab to push stuff back into the future, so I'm throwing lots of stuff back there and the current method works but is slightly irritating.
I would like an automatic closure of TR if idle for user defined minutes. I often leave it open on one computer and be worried that if I open it on another one, I will lose some entries.
A user defined timeout would be nice. Or maybe you could instead handle it like a lot of MMOs. If the client gets opened in a second location, the first one then closes itself. That way you don't get timed out if you don't want to be. I have no idea how you would cause TR to save it's state and exit out at that point, but it would be cool.
You mention an alert when project is moved from future to current project tab. What king of alert are you thinking of?
My "simplest" answer would be to have a color code for "recently moved from Future" but that gets us into the whole realm of color coding and until we start playing with it, it would be hard to tell what scheme would work best.
Another possible solution would be to have a log of recent activity.
"the due date triggered on task ABC in Projects\XYZ\DEF\QRS\ABC"
"the start date triggered on project QRS i Projects\XYZ\DEF\QRS"
A log would probably be the shortest most useful tool.
Right now I'm just putting __FP__ at the front of everything in Future so that when it gets moved on it's start date over to Projects I can see, "Oh, this got moved recently, what did I want to do with it today?"
For Lack of ability to associate files with a project, what about adding links to your project notes? You could also add the files as references items and then add a link to the reference item in your notes (if the files are used by more than one project).
I don't know how to associate files with a project. I also don't know how to add references to files.
How do I use, or set up this functionality?
This is where a dedicated Technical Writer comes in handy. A good one is great with setting up screen shots and creating walk throughs.
