Re: Features soup: another county heard from
Mikael Hallendal <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.mr-project.user |
|---|---|
| Message-ID | <[email protected]> |
ons 2002-08-21 klockan 18.28 skrev Dudley Irish: > LTLFTC. ^^ What does that mean? :) just curious. > First some credentials, I have been managing strictly software > projects for many years now. I have used most of the available (and > some no longer available) project management tools. I am currently > coming up to speed on GTK2 so that I can start contributing to > projects like MRProject. Yay! Great news. > If we concentrate on the file format and extend it to support > everything, then we can write independant tools which share the file > format. For example, I have just spent three hours in a tedious > meeting working through the detailed task breakdown for a project. I > have lots of notes and now I need to enter all of this into MRProject > so that I can start the planning process. Since I don't like MR > Project's task entry form when I am entering tasks in bulk I fire up > Dudley's Task Breakdown Super Program. The details of the interface > don't matter, because it was designed by me to enter tasks from notes > the way that I do things, but I can use it because it uses the same > file format. Once the task breakdown has been entered, I can fireup > MRProject and start planning. We just added a better way of inputing tasks, but that's not really the point :) Anyway, I think the correct way to do this is to do it through libmrproject. You can write your own little tool (in C or Python, though python support is currently not there but could be added really easy), where you input all your data into a project and then save it and you don't have to care about the file format at all. > An alternative to this is the loadable module approach. We could > depend on GLibs loadable module routines to create a system in which > you can add lots of modules to the basic tool. I think that this is > more work than the increased sense of having an integrated tool is > worth, but you may disagree. I think for tools that we want to ship with MrProject we should make them into modules loaded through GModule (which we are currently using). For third party utilities it doesn't really matter, though for the user that is going to use them it's obviously nice to have them integrated into Mrproject. Thanks for your comments and hope to see you hacking on MrProject in the future, Mikael Hallendal -- Mikael Hallendal [email protected] CodeFactory AB http://www.codefactory.se/ Office: +46 (0)8 587 583 05 Cell: +46 (0)709 718 918