Tim Cross <[EMAIL PROTECTED]> writes: > From: Hadron <[EMAIL PROTECTED]> > Subject: Re: [Planner-el-discuss] Muse/Planner - how to change project > Date: Fri, 26 Jan 2007 17:43:33 +1300 > >> Tim Cross <[EMAIL PROTECTED]> writes: >> >> > From: Hadron <[EMAIL PROTECTED]> >> > Subject: [Planner-el-discuss] Muse/Planner - how to change project >> > Date: Fri, 26 Jan 2007 15:14:50 +1300 >> > >> >> >> >> Could someone please advise on how best to change the current >> >> muse/planner project? I have defined two in my >> >> muse-project-alist. Should I define a function to change >> >> planner-project? Is there not an function which can list current >> >> available projects for selection? >> >> >> >> Again, thanks for any help and information. >> >> >> > >> > have a look at some of the code in the contrib directory of the muse >> > distribution. This will probably give you enough information to create >> > such a >> > function. I've done this and used this to guide me. However, please see my >> > earlier posts and consider just working with the basic 'out of the box' >> > configuration for a while. I think your really fighting the system rather >> > than >> > working with it. Play around with some of the customization stuff and get a >> > feel for how all the different parts hang together. >> > >> > tim >> >> I understand what you are saying but multiple planner projects are a must >> for me >> before I commit fully to this. Muse "projects" are not an issue. >> >> Being able to swap between planner projects is definitely a must. >> >> I maintain several muse files, and have decided to keep these seperate >> from the planner directories or all sorts of confusion arises - this is >> fine. >> >> But a foolproof integrated way of switching between planner projects is >> a must - however I dont feel my lisp is good enough especially since I dont >> understand the program flow for the existing "insinuation" processes. >> >> Yes I could just maintain ONE planner directory but that wouldnt work >> for me. I like to keep the tasks seperate especially since I wish to >> publish them in different defaulted formats - its one of the reasons I >> am looking into using planner. >> > > Can you expand on why you need seperate planner projects? I have trouble > understanding how you want this to work. Some issues which I'm not clear on > how > you plan to handle include - > > * Task Scheduling. If you have different planner projects, how will you get an > overview of all the tasks you have scheduled. For example, I look at my day > page and it has all the scheduled tasks I am currently working on for all > projects. If/when I need to schedule a new task, I visit one of the project > pages where I add all tasks as I think of them, but don't schedule until I'm > ready to do it. I then select a task and do a C-c C-c to schedule it on a > specific date etc.
Scheduling is not an issue. Scheduled tasks will form part of my "Central" project. The other projects are totally disjoint and feature a lot of different minor tasks many not even scheduled at all. > > * How will you handle diary bookings? Will you simply reproduce the diary > bookings for all appointments in each project day page or what? I might turn off diary completely since I dont see much of a benefit in including them - but yes, diary elements are REAL appointments in real time and so i would want them shown on all planner sheets. > > To provide any real suggestions/guidance, I think we need more details on why > you have to have seperate planner projects. to me, this concept is totally > alien to the general concept of planning - its like having different diaries > for different projects. Also, I don't see what you would put into > these planner I would indeed maintain different diaries for different projects (as a journal). > project directories. Essentially, planner has only two types of files, day > planner (pages) files and one project file per project. the only way I can see > what you are proposing working would be if you had the project files > in their That is not what I am proposing. I dont want a centralised concatanated project plan page. > own directories and have all projects use one centralised day page. However, > then you would just end up with a lot of project directories with essentially > one file - the project plan file, in them. No, I would want seperate plan pages providing the logical equivalent of categories to further break down the indicidual projects. Each project would have its master TaskPool for generic tasks and the auto generated day page for tasks which have been scheduled. > > If you plan to put other files in the directories, such as documentation on > your project in muse format, then I'd say your really mixing up two different > concepts - planning and project documentation. If nothing else, this > just shows I had wanted to. Unfortunately though planner doesnt maintain its own extension and so makes this difficult. Thus I will maintain documentation/master docs seperate from the plan directories. > I don't follow what your requirements are. Perhaps if you outline the > functionality and requirements you have as well as any constraints (with the > justification/rationale underlying them), we may be able to make more useful > suggestions. Thanks for your time and comments. > > Tim -- _______________________________________________ Planner-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/planner-el-discuss
