GNOME Bugzilla – Bug 200821
We need a Notes component.
Last modified: 2013-09-10 14:04:09 UTC
I want to sync my notes from the Pilot, and we should have a way of syncing the Memo to Evolution Notes (or memos).
Marked for post-1.0.
*** bug 210540 has been marked as a duplicate of this bug. ***
This would be really nice but my (offhand) feeling is that it is too large for 1.2?
*** bug 209206 has been marked as a duplicate of this bug. ***
*** bug 220776 has been marked as a duplicate of this bug. ***
*** bug 220766 has been marked as a duplicate of this bug. ***
*** bug 223506 has been marked as a duplicate of this bug. ***
*** bug 219123 has been marked as a duplicate of this bug. ***
*** bug 218306 has been marked as a duplicate of this bug. ***
bug 223673 also requests a datestamp on note
*** bug 223673 has been marked as a duplicate of this bug. ***
*** bug 217603 has been marked as a duplicate of this bug. ***
*** bug 227405 has been marked as a duplicate of this bug. ***
*** bug 230117 has been marked as a duplicate of this bug. ***
*** bug 232642 has been marked as a duplicate of this bug. ***
is this really gonna be implemented for 1.4?
I bet not. Futuring everything futurable.
*** bug 200700 has been marked as a duplicate of this bug. ***
When trying to schedule a meeting the drop down calendar retains the month view as each week starting on Monday regardless of setting in Calendar view. When cancelling this action, Calendar crashed.
*** bug 246897 has been marked as a duplicate of this bug. ***
I've been thinking about writing an Evolution component that'll do just this. I use memos a lot (more than anything else, really), so I'd like to see something like this in Evolution. While I don't have a design as of yet (I'm just starting to work on it, as I wanted to figure out how to use the libraries that Evolutionn uses first), I'd welcome any suggestions. To me, it looks like the Tasks component could be a starting point, or at least a model, of how a Notes component should work/act. The main question I have, though, is should a new backend be created in the Wombat component (say, a Personal Notes Server) or should the PCS that exists be modified? I would tend to go with a separate back end as that way changes would only affect that backend and not the PCS backend. However, I don't know which way would be easier to create and then maintain. I'd like any suggestions, comments, etc. anyone might have on a Notes component being implemented.
Nathan: It would be great that you subscribe to evolution-hackers mailing list and share your thoughts with the community. To do that, please follow the instructions at http://developer.ximian.com/community/lists.html Thanks a lot!
I'm sorry to see this didn't make it into 1.5. I use notes/memos extensively, and Evolution is really hobbled without it for my use. Are there any plans to incorporate this in a future version, or is this three year old feature request really dead?
I think it's too often requested to be forgoten.
*** bug 258153 has been marked as a duplicate of this bug. ***
Any chance for 2.0? It'd be great to have in the fall ...
*** bug 217381 has been marked as a duplicate of this bug. ***
*** bug 246131 has been marked as a duplicate of this bug. ***
Still waiting for a notes component. Is handling syncing with PDA the holdup? I'll echo the request also to be able to associate a note with a task or calander event, but that's a much less vital feature.
I've created a memos (same as "notes", but I've called it "memos" since that's what the PDA uses - and I don't like copying Outlook) component. The project is at http://sourceforge.net/projects/evolution-memos/ . It *mostly* works. It's based on the gnome-2-8-branch of Evolution. I think this is 2.0.4. The download is a patch to that CVS branch. I've also uploaded the whole source of Evolution and Evolution-Data-Server with the component in it to CVS on sourceforge - copyrights maintained. I do have an updated version for 2.3.1, but haven't had time to release it yet. I haven't sent it to the evolution-hackers list yet because I just updated it to 2.3.1 and haven't had a chance to put that on sourceforge (let alone create a patch to 2.3.x or CVS for it). The one problem I have: the Click to Add feature isn't working - I'm still working on fixing that. How the component works: - based on the Tasks component - uses VJOURNAL in the ical implementation (suggested in a 2003 e-mail) - works like the Memos on the PalmOS - Summary is used to hold the content - I'm probably going to make the Description hold it and just ignore the summary (comments?) Next on the list is to create the gnome-pilot conduit. I was playing around with the todo-conduit (to get category syncing to work), so I think I now understand how the memos-conduit will work. I'll post that when I get it working.
This is great, but since it won't be accepted for 2.2, could you please provide a patch for e-d-s/evolution HEAD? Also, I added some code recently to HEAD to deal with VJOURNAL, so you might have to merge that with your patch
I've actually spent the last week or so getting it working with evo 2.3.3.1 and then to CVS (incremental is easier than 2.3.1 to CVS - and I like running releases myself, instead of the CVS version). That being said, I've released patches for both evo-2.3.3.1/eds-1.3.3.1 as well as evo-cvs/eds-cvs (cvs on June 21, 2005) at my sourceforge site (http://sourceforge.net/projects/evolution-memos/). I'll attach both sets here as well as tarballs. Also, CVS on the sourceforge project will be kept up-to-date with CVS from evolution every few days or so. The way the summary and description are used has changed. I noticed that if I display the description (i.e. memo content) in an e-table, each row of the e-table expands to the number of lines for that particular memo. This makes it unreadable. Instead, I'm storing the memo content in the description, but taking the first line up to 40 characters and placing that in the summary. This enables 1-line entries in the table and is very similar to how the Palm Memos program looks - which I think works very well. I've created a memos-conduit for Gnome-Pilot. It's almost a clone of the todo-conduit, but uses the 'struct memo' from pilot-link instead of 'struct todo'. It includes the category syncing patch that I worked on for the todo-conduit, so categories will sync 99% of the time (copy-to-pilot still needs to write over all categories on the palm side with our own categories). The description is synchronized, and the summary is not looked at (hence why the summary is computer-generated and not user-generated). There is only one field in the 'struct memo', the 'text' element. About VJOURNAL: I noticed the vjournal backend, so I started using it. I had been using essentially the same thing before myself, but had called it a "memos" backend. Right now, there's an E_CAL_COMPONENT_JOURNAL, which corresponds to RFC 2445 (iCal). However, if a REAL journal (i.e. weblog or some such thing) is ever created, a new e-cal component would have to be created for memos. The VJOURNAL backend could still be used, but the Memos component has a .evolution/memos directory, not a .evolution/journal directory. I think that's all. I'll be sending an e-mail to evolution-hackers to get comments on what I have over at the sourceforge site. I'm also working on sending in the copyright assignment form in hopes of getting this accepted for 2.4 (or at least 2.5-2.6).
Created attachment 48166 [details] patch against CVS for evolution and the evolution-data-server - done 6/21/05
Created attachment 48167 [details] patch against evolution 2.3.3.1 and evolution-data-server 1.3.3.1 created one against the latest development release as well for those who are using that. Should work against evo-2.3.3 and eds-1.3.3 as well
Created attachment 48169 [details] Screenshot of the Memos component, grouping by categories
Created attachment 48170 [details] Screenshot of creating/editing a memo entry might want to create that E_CAL_COMPONENT_MEMOS now, though it'd violate the RFC. Notice the title of the window.
Created attachment 49179 [details] patch against CVS for evolution and the evolution-data-server - done 7/13/05 Updated to the latest CVS as of 7/13/05. This is a .tar.gz file.
Created attachment 49602 [details] [review] patch against Evolution HEAD - need EDS as well (see below) updated - works from clean build
Created attachment 49603 [details] [review] patch against EDS HEAD again, updated - see above for Evolution patch
Created attachment 49604 [details] [review] patch against Evolution HEAD updated - had unncessary files in the patch
Created attachment 49605 [details] [review] patch against EDS HEAD updated - had unncessary files in the patch
Created attachment 49755 [details] [review] patch against EDS HEAD update with changelogs and a few other minor changes (formatting, mainly)
Created attachment 49756 [details] [review] patch against Evolution HEAD update with changelogs and a few other minor changes (formatting, mainly)
Moving to harish and CCing calendar maintainers so this actually gets reviewed.
Created attachment 53152 [details] [review] Patch for evolution against CVS - Oct 6, 2005
Created attachment 53153 [details] [review] Patch against evolution data server - Oct 6, 2005
Both patches just submitted are against HEAD on October 6, 2005 (EDT). Sorry for the misnaming of the evolution patch. No real changes have been made. Just updated to patch against HEAD.
Created attachment 53158 [details] [review] Pathc for evolution against CVS - Oct 6, 2005 - updated Updated. When I built it and ran it, I found a few problems with the patch. Updated so that it works again.
targetting to 2.5.
Patch committed to HEAD ....finally :-)