[emacs-wiki-discuss] Re: My Requiremnts - Your recommandiations.

[Edgar Gonçalves]

On Monday the 20th, Paul D. Kraus wrote:
> I have been digging and experimenting with all of the planner options and
> programs trying to figure out how to get it to work for me and its just making
> these really confusing. So I figure if I tell you guys what I want out of my
> planner and you can help me use the right tools and configuration.
>
> I want to be able to have ABC123 tasks the prioritize and sort based on both 
> the
> letter and the number when ever I change a tasks priority. I should be able to
> create reoccurring tasks.
I'm not sure about the first, but I think there's some hooks you can use to plug
a sort function that do what you want. About the second part, there's
planner-cyclic, I think it should solve your problems.
>
<...>
> I want to be able to "Publish" my work related tasks and schedule to a web 
> page
> so that my managers can get a good idea of what I am working on. I do not want
> my personal calendar, appointments, tasks to get published.

This is my greatest problem with planner, so far. I have an idea on how I may
correct this, but I'll need some more time to jot some code down.

I'd like to have all my emacs planning together, just as they are now. The
publishing would have to be different, so that I may have a
Personal-Info-Manager and a Public-Info-Manager. This could be done by marking
the top of project files (say, with an header like "#private", or something),
and then the publishing would occur as follows:
1. Publish everything just as it is now to a local folder (I may want to look at
   everything on HTML on my PC, and this would be my full version of the
   information)
2. Publish every non-private (ie, public, lol) project page to the remote folder
3. Publish day files to store every task and note of the public project pages'
   tasks on the remote folder (so that my personal tasks and notes for that day
   are not published).
4. Publish an RSS for each project file, as well as one for every update on the
   public pages (ie, a "News" feed). I gess one for the whole system of plan
   pages are useless, since it's for my eyes only, but you never know...

The links to personal pages would also have to be removed, eventually.
   
I understand that there's another level that could be added, but I don't need it
right now. But it could be handy, for a multi-project environment, to have the
concept of project-publishing, so that instead of an header like "#private"
there was one like "#project:CarSales  #remote-folder
sftp://super-imaginary-cars.site:/public_html";, and I could do \M-x
publish-project <RET> CarSales <RET> to publish all the related project files
and it's notes/tasks also on appropriate day pages.

Note also that this would not cut any existing functionality - anyone could opt
not to use such a scheme by having a default public project

>
> I want to be able to keep a daily journal/diary where I can just jot down my
> thoughts of the day and be able to easily find and review them at my
> leisure. This should not be built into my task pages. These writing our of a
> very personal nature. I should be able to publish these to a pdf document or 
> web
> page for easy reading over several days/months.

Some options:
1. Using my concept explained above, I would like to have a project named MyBlog
   where I could keep everything integrated with the rest of my planner files.
2. Use emacs-wiki-journal. I don't know if it's being mantained, but I've used
   it for a week, or so, and it was ok. then I moved my things to planner.
3. Make a way of keeping the RSS entries (generated they way I said above)
   stored somewhere, so that one may have an automatically generated journal. So
   that you could add entries just as any other plan note, and see the published
   version (use muse to publish to latex/pdf/html/...). The only aspect I'm not
   so sure about is the archiving feature. I would have to think a bit more on
   that. (not enough experience, I suppose...)

>
> Thanks for all your help. Emacs is a great tool but its a bit complicated to 
> get
> it setup and understand how to use it so that all the various parts work
> together rather then independently.

Tell me about it! but still, there's nothing that can beat it, for now!

>
> Paul

-- 
Edgar Gonçalves
Software Engineering Group @ INESC-ID
Portugal