Re: Tomboy in 2.16

[Harish Krishnaswamy <kharish novell com>]

What I had in mind when I mentioned 'integration' was not :

        making e-d-s the 'only' backend for Tomboy. I do not see any
        point making Tomboy to use e-d-s a requirement for inclusion in
        GNOME either.

What I did have in mind was :

         Ability for Tomboy and EDS to share information - each acting
        as an *additional* source for the other. I am a heavy user of
        both Tomboy and the Memos - I _do_ not want every single Tomboy
        note inside my Memos or under e-d-s.
 
But if the two work together - they do open a lot of interesting
possibilities.  Just to name a few...

      * Ideas-capture is best done by Tomboy for me - but while
        operating out of my calendar/todo list - I always prefer to park
        a bunch of notes relevant to a given task/appointment inside my
        e-d-s information space.
          I would like to able to associate a live reference to the
        notes rather than a stale snapshot of the notes. I want to read
        them inside my memos, associate them with my projects and
        schedule but retain the flexibility of entry/modification via
        Tomboy).

      *  I have the habit of tracking open-loops with individuals my
        devoting a Tomboy note for each of them and I look it up
        whenever I am mailing the person. I would certainly love if a
        hover on the contact in evolution can bring up my Notes
        associated with that person.

        
Harish


On Thu, 2006-04-20 at 12:10 -0700, Alex Graveley wrote:
> Two questions:
> 1) Can you explain the actual user-benefit to keeping Tomboy notes in e-d-s?
> 2) Is moving Tomboy to use e-d-s going to be a requirement for inclusion 
> in Gnome?
> 
> -Alex
> 
> Rodrigo Moya wrote:
> > On Thu, 2006-04-20 at 17:27 +0530, Harish Krishnaswamy wrote:
> >> Embedded GTKHTML in the calendar/memos/tasks component is under works.
> >> It should be available by the second or the third dot release in the
> >> current dev cycle :-)
> >>
> >> And yes, I think the HTML approach would be the shortest-path for the
> >> integration too.
> >>
> > great! Then let's move all apps to e-d-s API. Any objection?