[Chandler-dev] [Proposal] Tbird - First Pass

[Brian Kirsch]

> Oh I meant uninstalling the plugin, not sure what the standard way  
> to uninstall add-ons is in T-bird.
>

Hi Mimi, there is a standard mechanism in Mozilla apps for  
uninstalling Extensions so no custom
Chandler code needs to be written.

-Brian


On Feb 8, 2008, at 12:58 PM, Mimi Yin wrote:

> Hi Brian, See in-line.
>
> On Feb 8, 2008, at 1:13 PM, Brian Kirsch wrote:
>
>> On Feb 8, 2008, at 10:06 AM, Mimi Yin wrote:
>>
>>> Here is the proposal Brian Kirsch and I came up with after  
>>> meeting briefly yesterday re: next steps for the Thunderbird  
>>> plugin. (I have embellished with mock-ups). Again, we are looking  
>>> to implement an 'easy' first pass at getting messages from T-bird  
>>> into users' Chandler Hub accounts.
>>>
>>> 1. Add 'Set up Chandler Account' to the Tools>>Add-ons menu
>>> Q. Do we need a menu item for 'Remove'?
>>>
>>
>>
>> Hum, how about an Enable / Disable this account checkbox on the  
>> Chandler account setup page.
>
>>
>>
>>> 2. See account set-up mock-up below.
>>> + Enter user name + password
>>> + Select collection you want messages to be sent to - We'd like  
>>> users to be able to have more flexibility around what collections  
>>> messages are sent to. But as a first pass, we're going to force  
>>> you to choose one a priori.
>>> + Test button to make sure it's working
>>>
>>
>> I don't think the test button is needed since it is implied that  
>> the account has to be correctly set up before
>> the user will be able to select the collection to send messages  
>> to. If the account is not correct then
>> an error will be raised when contacting the server to get the user  
>> collection list.
>
> Got it.
>
>>
>> Perhaps this should be moved to a wizard type dialog where the  
>> information can be added
>> in stages.
>>
>> Page One:
>>    Enter username and account - clicking next will retrieve the  
>> collections for the account.  With this
>>                                                           type of  
>> workflow the Test button should remain so the user can
>>                                                           try the  
>> account before hitting next.
>>
>>    Page Two:
>>       Select the collection to use to send mail to.
>>
>>    Page Three:
>>         Done page with settings to confirm. This page would have a  
>> cancel, go back, and done.
>>
>>     Done = save the settings and activate Chandler menus in the UI  
>> and Toolbar.
>
> I'm not sure we need to do all that given that there are only 3  
> fields to fill out. I think if we end up needing to add more steps  
> we should definitely keep that in mind.
>
> For example, we could provide options for how much functionality  
> people want to add to the UI:
> - Toolbar button?
> - Column in the list?
> - Stamping buttons?
> etc...
>
>
>>
>>
>> Another option is to try and tie in to the existing TB account  
>> wizard dialog. It would
>> be more complicated to implement but might be better for users. I  
>> will investigate this
>> as well to see how hard it is. There is an rdf format for  
>> registering new account types
>> so I need to play with it a bit. Do you think this option would be  
>> better if easily
>> implementable?
>
> I'm not sure. Email accounts are pretty confusing. Let's try  
> staying out of it and if users get confused, re-address this issue  
> later.
>
>>
>>
>>> + Cancel + Okay buttons
>>>
>>> 3. Add 'Send to Chandler' to the Message and Context menus below  
>>> 'Mark'
>>> - Nice to have: Add sub-menu to select from a list of available  
>>> collections
>>>
>>
>> +1
>>
>>> 4. Nice to have: Add a 'Chandler' toolbar button.
>>> - Even nicer to have: Toolbar button + pulldown to select from a  
>>> list of available collections
>>>
>>
>> +1 will start with a Toolbar icon and then expand with the drop  
>> down in the second iteration.
>>
>>> 5. Nice to have: Add a 'Chandler' column to the list view so that  
>>> users can just mark up items they want to send to Chandler in-place.
>>>
>>> BIG OPEN ISSUE
>>> + How do we reconcile the OOTB Hub collection + Desktop  
>>> 'Dashboard' collection? Both are obvious candidates to serve as  
>>> the 'default' collection to send Thunderbird messages to.  
>>> However, my guess is that many Desktop users don't even know that  
>>> the Hub OOTB collection exists in their account and unless they  
>>> do so explicitly, Desktop users will not have their Dashboard  
>>> collection available to them on the server.
>>>
>>> This is on the agenda of our Monday web strategy meeting. I  
>>> imagine that we will most likely rely on the user to understand  
>>> what is going and make the right decision. However, this is an  
>>> usability issue we need to address eventually.
>>>
>>> Questions for Brian
>>> + Are the icons for all 3 platforms the same?
>>
>> I believe so, but will confirm.
>>
>>> + Are their size requirements for the toolbar and list view icons?
>>
>> 32px X 32 px for the toolbar in png format.
>>
>>> + Naming conventions?
>>>
>>
>> No naming convention required at this point. I can always rename
>> the files at a later date.
>>
>> I have attached the png that TB uses for the toolbar. Each icon is
>> selected from the series using css and rect coordinate values.
>
> Great thanks!
>
>>
>>> <Tbird_account.png><Tbird_list.png>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _  
>>> _ _ _
>>>
>>> Open Source Applications Foundation "chandler-dev" mailing list
>>> http://lists.osafoundation.org/mailman/listinfo/chandler-dev
>>
>>
>> <mail-toolbar.png>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "chandler-dev" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/chandler-dev
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "chandler-dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/chandler-dev