project management - Programming time schedule for porting a program -
I am working on a large program that has an abstract GUI API, it is very GUI based, many dialogs and some dirty There are symptoms that are heavily dependent on the message flow of the GUI (the right sequence of focus / mouse / active handling, etc.) - not easy for port
Now I am currently using Fox toolkit to make it native cocoa / Want to close in MFC
I give myself a deadline till the end of the year but my main job will be to continue the development work with the existing toolkit, but
My question is how do I spend my time Do you spend
- Stop working on the main program and 90% of the GUI port (about 3 months)
- Divide everything in one month's short sessions
- Appointment for the Monday / Tuesday GUI Project and for the rest of the week
- To end the first app, then the port.
I think there are three arguments for which I need balance.
- Inspiration, I want to see something that is going on both projects
- For both brain function overflow, much more detail is needed in both my brains and sometimes, Ever enough just enough is enough.
- I think porting is interwoven so porting will require many code changes in the existing code and the new code will be written at that time.
If there is no planned release to customers, then you have the same structure of work Being able to do is luxury.
My first impression is that attempts to eliminate the app on the current platform, when you want to remove that code, at least partially in vain time (you learn something but the last There is no use of code).
Personally I'll park the current version and start with it will rewrite cocoa.
First of all, I'll split it into functional parts and see everyone as an agile style release. These end user should be focused on work and tasks, and both of them include the GUI and work at the end of the bench.
(The reason I do not like the idea of working through GUI and app logic is that they are no different. There may be opportunities to improve as part of a rewrite, and if you It is difficult if you want to keep them compatible. A rewrite is an opportunity to make fundamental changes that often do not come together - I 'd take it.)
Before moving on to the next one, work through a functional fragmentation one by one, getting into a complete, releaseable state. This will give you the sense of achievement and the ability to measure progress. It also means that if any execution exits from anywhere, then you are a completely usable part.
In addition to this, focusing on the end of the task, hopefully the overflow of mind is reduced because you always have a specific area than a single app.
Comments
Post a Comment