tw2org

[djp]

Hello Herb and VimOrganizer team!
I'm a taskwarrior.org user (nominally the Designer, actually) and quite a fan of vimorg.
I'd like to build a bridge from one to the other, so that taskwarrior users can also benefit from all that vimorg has to offer, without abandoning the wiz-bang features of tw.

Now obviously this is non-trivial, but I have a fairly clear idea of how it might work, even if I don't actually write code. Some description can be found at http://taskwarrior.org/boards/8/topics/208#message-2704 and https://github.com/hsitz/VimOrganizer/issues/37 although there's some fuzzy, half-baked thinking there, but the thing that keeps me thinking about this is the 90+% correlation of fields between tw and vimorg.
 
It only makes sense to take this journey one step at a time, and I think the first step would be a taskwarrior plug-in that mirrors some tasks to an orgmode file, translating the many aspects of a taskwarrior task to orgmode, including the tw uuid as a property.
My question here (the first of many) is what mechanisms (existing code) exist to accomplish that?
I've looked at various tools posted on http://orgmode.org/worg/org-tools/index.html, and while some of them look promising, upon closer inspection I don't see anything full-featured or mature enough to make the conversion possible, much less easy. The tw devs are fluent in c++, speak python and some perl, and are decidedly on the vim side of the fence.

Can anyone suggest existing code or libraries that the clever-but-busy tw Devs might use to parse an orgmode/ vimorg file (for matching tw-uuid property, or, failing that matching project) and then to write a properly block?

ideas? clever ? or crazy? you tell me :)
thanks

[Herbert Sitz]

On Wed, Jan 2, 2013 at 4:44 PM, djp <dava...@gmail.com> wrote:
> Hello Herb and VimOrganizer team!
> I'm a taskwarrior.org user (nominally the Designer, actually) and quite a
> fan of vimorg.
> I'd like to build a bridge from one to the other, so that taskwarrior users
> can also benefit from all that vimorg has to offer, without abandoning the
> wiz-bang features of tw.
>
> Now obviously this is non-trivial, but I have a fairly clear idea of how it
> might work, even if I don't actually write code. Some description can be
> found at http://taskwarrior.org/boards/8/topics/208#message-2704 and
> https://github.com/hsitz/VimOrganizer/issues/37 although there's some fuzzy,
> half-baked thinking there, but the thing that keeps me thinking about this
> is the 90+% correlation of fields between tw and vimorg.

David -- Sounds interesting. I know I've seen a couple threads in the
orgmode newslist at gmane.org where they talked about taskwarrior
interoperability, but I don't know whether anyone's done anything.

I would suggest that rather than building this interoperability into
VimOrganizer that it would be better to build it into orgmode itself,
i.e., into Emacs Orgmode. That way all the many orgmode users would
have it available, and for VimOrganizer users functions could be
called to process things on the emacs server.

I'm not very proficient at elisp (the emacs scripting language) but i
don't think this would be terribly complicated. I think first step
would be to ask around/look around in orgmode newslist to find out
whether anybody might have done this or have a start on this.

-- Herb

[David J Patrick]

On 2 January 2013 21:26, Herbert Sitz <hes...@gmail.com> wrote:

David -- Sounds interesting.  I know I've seen a couple threads in the
orgmode newslist at gmane.org where they talked about taskwarrior
interoperability, but I don't know whether anyone's done anything.

no doubt those threads are my earlier kicks at the can :)

I would suggest that rather than building this interoperability into
VimOrganizer that it would be better to build it into orgmode itself,
i.e., into Emacs Orgmode.   That way all the many orgmode users would
have it available, and for VimOrganizer users functions could be
called to process things on the emacs server.

I agree, and would be strongly recommending that any such "bridge" would be from tw to orgmode, and that vimorg users (such as myself) could use it too. It makes no sense to exclude the many emacs-heads and their accumulated cleverness. One such emacsienne is sacha chua, who wrote a not-dissimilar plugin for toodledo (http://sachachua.com/blog/2010/05/org-toodledo/) and although that's a web-app, there must be some similar field-mapping and org-file-writing going on. Unfortunately, I couldn't read the code if my life depended on it. (and it doesn't ;)

I'm not very proficient at elisp (the emacs scripting language) but i
don't think this would be terribly complicated.  I think first step
would be to ask around/look around in orgmode newslist to find out
whether anybody might have done this or have a start on this.

you're probably right, although I am so totally ignorant of the ways of emacs that I would be asking the wrong questions, and not understanding the answers. The other fundamental problem of that approach might be a general consensus that if they're using full-on emacs + orgmode.. why would they need taskwarrior?

thanks Herb!

[Herbert Sitz]

On Wed, Jan 2, 2013 at 6:53 PM, David J Patrick <dava...@gmail.com> wrote:
>> I'm not very proficient at elisp (the emacs scripting language) but i
>> don't think this would be terribly complicated. I think first step
>> would be to ask around/look around in orgmode newslist to find out
>> whether anybody might have done this or have a start on this.
>
>
> you're probably right, although I am so totally ignorant of the ways of
> emacs that I would be asking the wrong questions, and not understanding the
> answers. The other fundamental problem of that approach might be a general
> consensus that if they're using full-on emacs + orgmode.. why would they
> need taskwarrior?
> thanks Herb!
>

I think in thread I saw they were talking about a way to export org
data so they could get what they thought were nifty graphs from
taskwarrior. . . I'll put this on my list of things to take a look
into. -- Herb

[David J Patrick]

FYI, a github location for Sachas code;
https://github.com/sachac/org-toodledo

and an updated version;
https://github.com/christopherjwhite/org-toodledo