(sorry for this very scattered email, I'm commenting relevant lines of the modified table.)
> Corrected and expanded version: > > | export formats | See muse | HTML LaTeX IMO a full list of supported formats for planner would be useful here. I plan to publish this table in HTML/LaTeX at some point. Actually, the export options for planner/muse are so useful that you should add them! > | RSS support | RSS 1.0, 2.0 | in development What kind of development are you refering to? I'd be very interested in knowing this, since I've written blorg, which have support for RSS. > | add-ons | more than org | TOC blorg registry Again, could you make a (even short) list of add-ons, possibly with a short description? > | mailers support | same as org | gnus vm wl mh rmail > | link types | >> than org | http file bbdb w3 w3m info Which links are supported in planner that are not natively supported in planner? BTW Org has the capacity to let people define new link types. > | calendar/diary/appt | native | native > | use it as a wiki | native | thru file links? > | allow multiple projects | yes | yes > | allow project overview | yes | quick (Dunno if this should appear in this table, but I'd be interested by some examples of project overview for planner.) > | GTD implementation | has been done | yes Link? > | infile time manipulation | what is that? | yes Timestamps? > | update same task, >1 pg. | yes | no Can you explain this a bit further? > | revision control integr. | Xtla and psvn | none Wow! This is great. I guess the right place to mention this is "link". But this is something we could add for Org. BTW, I forgot to mention shell links that Org support -- i guess it's already there in planner. > | load individ. feature | yes | no What do you mean? I cannot think of a set of features that an average Org user would not like to load. > | eval elisp during display | yes | no Same for xtla/pcvs, it's more like a link functionality than a real add-on. And Org supports this: http://orgmode.org/org.html#External-links > | escape specials @ publish | yes | no Can you explain this a bit more? > | maintainer | John Sullivan | Carsten Dominik > | community | active | very active Well. "Community" is too vague. We should distinguish mailing lists activity web "community" (maybe in terms of webpages talking about planner/org), because I guess there are more information on planner out there. > I assert that the reason that you don't see as much activity on this > mailing list as the org list is that Planner is a more mature product, True. > and has numerous extensions that satisfy most of its users (and > additionally, it has a top-notch manual to document all these > features). Yes, it's very clean and simple. In fact nobody needs a planner vs. org show. Often, people who like software are too much entangled in them and can't honestly see any reason to use the "other one". But they are not able to see any good reason *not to use* the other one because because... simply because there aren't such reasons :) > I find it rather rude to suggest "phasing out" Planner, and am irritated > that you bring up the topic by vacuously casting doubt on the current > maintainer's ability by alleging "maintenance difficulties". Hey guys! No phasing out or whatsover. Softwares are made of collective sweat and joy, and this is the real salt of life! So, no code should be murdered before he kills himself (like a perverted recursive defun.) -- Bastien _______________________________________________ Planner-el-discuss mailing list [email protected] https://mail.gna.org/listinfo/planner-el-discuss
