Re: [Evolution-hackers] Question about Groupwise and Memos (see bug 389668)

2007-02-21 Thread chenthill
Hi nathan,  
I added the summary and start date fields looking at the
supported fields for the VJOURNAL component. I have not observed the
initial discussions which had happened in the e-hackers list. I feel its
better to have a start field  so that the notes can be sorted well and
would be really useful to know when a note was created. The summary
field can be made optional depending on the backend's needs. I really
did not want to write another backend or a component for just supporting
the summary field in addition to what the memos component intially
supported. The UI changes can be probably taken up for evolution-2.12.

thanks, Chenthill.
On Sat, 2007-02-10 at 09:39 -0800, Nathan Owens wrote:
 Back when the Groupwise functionality was implement for the Memos component, 
 the summary and
 start date fields were added to the Memos GUI. I was wondering why this is 
 done.
 
 IMO, Memos shouldn't have a start date, or a summary. In fact, when I 
 originally implemented the
 component, the Summary field was just a cut-off portion of the Description. 
 It was done
 on-the-fly, and only because I wanted a portion of the Description to show up 
 in the Memos
 component table view. Showing the Description field in the Memos component 
 table didn't look very
 good.

 Adding the summary field has now caused this bug:
 http://bugzilla.gnome.org/show_bug.cgi?id=389668.
 
 As for the Start Date - the memos component isn't meant to be a Journal. It 
 only uses the VJOURNAL
 format because I didn't want to write a new backend (and at the time, the 
 consensus on the
 evolution-hackers list was that VJOURNAL would be appropriate). If we want a 
 true journal, then we
 need a new component. Memos are just little notes (think of the Notes feature 
 in Outlook, or the
 Memos feature in PalmOS - the PalmOS feature is what made me create the Memos 
 component in the
 first place).
 Here's my proposal that I'd like to get feedback on:
 - Remove the Summary and Start Date fields from the GUI
 - Start Date is never set (could always be set to 0, but I don't believe I 
 needed to do that when
 Memos was first implemented)
 - The summary field is automatically filled in (on-the-fly, or whenever the 
 Description gets
 updated) based on the Description.

 I don't know much about GW, but I believe the core code should not support 
 the Date and Summary
 fields as they are currently supported. If we need something different for 
 GW, then it should be
 implemented differently.
 
 Any thoughts? Anyone have insight into the Groupwise changes and why they 
 were made?


 
 Thanks,
 Nathan Owens
 
 
 
 
 
 
  
 
 Don't get soaked.  Take a quick peak at the forecast
 with the Yahoo! Search weather shortcut.
 http://tools.search.yahoo.com/shortcuts/#loc_weather
 ___
 Evolution-hackers mailing list
 Evolution-hackers@gnome.org
 http://mail.gnome.org/mailman/listinfo/evolution-hackers

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] Where to put UI items for templates (Bug #127529)

2007-02-21 Thread Matthew Martin
On 2/16/07, Sankar P [EMAIL PROTECTED] wrote:
 On Fri, 2007-01-26 at 16:59 -0600, Matthew Martin wrote:
  I'm working on templates for evolution. I need to know where to put all
  the UI items for templates. There would need to be a save template,
  default new mail, and default reply items. I read some of the HIG and
  stuck them in there so I could write the code. Here's a link to the
  patches. http://mtt.martin.googlepages.com/ The first one is for
  evolution, and the second is for evolution-data-server.


 I looked at the patches attached in the above url. The patches are not
 yet complete so I am not doing an in-line patch-analysis reply. Some of
 my comments are :

 - An account should be able to choose, what should be the default
 template that it has to use and it should be noted that NONE should also
 be an option here.
  Where should this be added? Isn't this what the Default New Mail
thing is for? Do we even need the default new mail? How useful would
that be anyway?

 - You can add an option, File-New from templates which should list
 the templates and the user should be able to choose a template and start
 composing a mail. I will recommend getting a nod from Srini (CCed) for
 any usability/UI aspects regarding this, before you start coding.

 - You need to add a view-column, Template name that will be available
 for the Templates folder (only).  All messages stored as templates
 should have a name associated to identify the message-template. It is
 far more usable to read, Status Report, Release Announcement Mail,
 String Announcement Mail, ABI Break announcement ;-) etc., rather
 than opening every mail and seeing, Is this what I want to send now ?

Shouldn't this act just like drafts?  Where are we going to get this
template name? Would this even be all that useful?

 - You need to close the composer once an user chooses Save
 Template (as of now it is not doing and it keeps on creating new
 templates) .
Why should it do that? Saving a draft doesn't do this. Wouldn't this
just annoy the user?

 - Reopening a template and saving it again should not create a new
 template.

 - Your patch misses mail.error.xml changes as a result none of the user
 choice-asking dialogs appear.

 - All mail operations like copy/move/DnD on templates folder should be
 disabled. (IMO, it is a lot more easier to implement a new tab under
 Composer-preferences than a new templates folder)

 - When there is a clash between account's default signature and the used
 template's signature, the template's signature should be given more
 priority.

 - The code to save a template should ensure teh uniqueness in naming
 etc.

 - There must be a way to create a normal new mail when the user has set
 a default-template. (May be a default Empty-mail template)

 This isn't clear enough. How should this be done? Should the whole
default new mail idea be rethought? Should we just make this like a
draft that doesn't delete itself?

  ___
  Evolution-hackers mailing list
  Evolution-hackers@gnome.org
  http://mail.gnome.org/mailman/listinfo/evolution-hackers
 --
 Sankar


___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] Where to put UI items for templates (Bug #127529)

2007-02-21 Thread Sankar P
If all you need is just a non-deleting draft, you can use Edit as new
message. I have felt that this shouldn't be restricted to Sent-items
alone as we allow configurable sent-folders. IIRC, there is a bug for
this as well. 

Srini: Shall we make this available on all folders ?

-- 
Sankar

___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] Where to put UI items for templates (Bug #127529)

2007-02-21 Thread Andre Klapper
Am Donnerstag, den 22.02.2007, 00:38 -0700 schrieb Sankar P:
 If all you need is just a non-deleting draft, you can use Edit as new
 message. I have felt that this shouldn't be restricted to Sent-items
 alone as we allow configurable sent-folders. IIRC, there is a bug for
 this as well. 
 
 Srini: Shall we make this available on all folders ?

at least make it available for the Sent folders that are defined in the
preferences (for each[!] account), and subfolders of those Sent folders
(because i still think that one cannot re-send something that has
never been sent before). bug 205728.

cheers,
andre

-- 
 mailto:[EMAIL PROTECTED] | failed!
 http://www.iomc.de


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers


Re: [Evolution-hackers] Where to put UI items for templates (Bug #127529)

2007-02-21 Thread Andre Klapper
Am Donnerstag, den 22.02.2007, 00:38 -0700 schrieb Sankar P:
 If all you need is just a non-deleting draft, you can use Edit as new
 message.

err, well. this sounds as intuitive as possible to me, a kind of draft
feature (where i probably will always have to remove some email text
because i abuse a sent email as a draft), hidden as edit as new in
some obscure context menu...
i think that it will be you who will have to add this feature to the
FAQ, if this proposal was really meant seriously.

andre

-- 
 mailto:[EMAIL PROTECTED] | failed!
 http://www.iomc.de


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
___
Evolution-hackers mailing list
Evolution-hackers@gnome.org
http://mail.gnome.org/mailman/listinfo/evolution-hackers