Hey Folks, in bug 1517162 I'm aiming to provide a new global on MailExtension windows because using browser.* can be really confusing if there is not actually a browser. Two questions for discussion: 1) Let's bikeshed on a name for the global. I originally used mail.* in the patch, but this doesn't work well for when we have chat or calendar APIs. Adding a new global for calendar or chat doesn't seem like a good idea to me, and mail.calendar.* is confusing as well. Using thunderbird.* seems too product specific. In the browser namespace it started with chrome.* but when Firefox adopted the API they chose browser.* to be more generic. Geoff suggested messenger.* which I like a lot. This would work well with messenger.chat.* , less so but still acceptable with messenger.calendar.* 2) Should we restrict Thunderbird specific APIs to the messenger.* namespace? Firefox does this I think in very few cases, I think in the browser.menus.* namespace there are functions that are not available on chrome.menus.*. This would be more work from a technical perspective, but I think it is possible. Looking forward to your input Philipp

On 24.04.19 13:13, Philipp Kewisch wrote: > Hey Folks, > > in bug 1517162 I'm aiming to provide a new global on MailExtension > windows because using browser.* can be really confusing if there is not > actually a browser. Two questions for discussion: > > > 1) Let's bikeshed on a name for the global. I originally used mail.* in > the patch, but this doesn't work well for when we have chat or calendar > APIs. Adding a new global for calendar or chat doesn't seem like a good > idea to me, and mail.calendar.* is confusing as well. > > Using thunderbird.* seems too product specific. In the browser namespace > it started with chrome.* but when Firefox adopted the API they chose > browser.* to be more generic. > > Geoff suggested messenger.* which I like a lot. This would work well > with messenger.chat.* , less so but still acceptable with > messenger.calendar.* communicator.* also comes to mind, and would put the emphasis more on the terminal/tool than the message delivery agency. Calendar and Email for example have many properties of local storage, which semantically would feel a bit out of scope in messenger.*. Best Claudio

I don't mind messenger.* as it kind of encapsulate the whole TB ecosystem without creating too much confusion. I'm not sure if this is a silly suggestion, but what about using something more generic like extension.* or actually api.*? Cheers On 2019-04-24 4:58 a.m., Claudio Luck wrote: > On 24.04.19 13:13, Philipp Kewisch wrote: >> Hey Folks, >> >> in bug 1517162 I'm aiming to provide a new global on MailExtension >> windows because using browser.* can be really confusing if there is not >> actually a browser. Two questions for discussion: >> >> >> 1) Let's bikeshed on a name for the global. I originally used mail.* in >> the patch, but this doesn't work well for when we have chat or calendar >> APIs. Adding a new global for calendar or chat doesn't seem like a good >> idea to me, and mail.calendar.* is confusing as well. >> >> Using thunderbird.* seems too product specific. In the browser namespace >> it started with chrome.* but when Firefox adopted the API they chose >> browser.* to be more generic. >> >> Geoff suggested messenger.* which I like a lot. This would work well >> with messenger.chat.* , less so but still acceptable with >> messenger.calendar.* > communicator.* also comes to mind, and would put the emphasis more on > the terminal/tool than the message delivery agency. Calendar and Email > for example have many properties of local storage, which semantically > would feel a bit out of scope in messenger.*. > > Best > Claudio > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net -- *Alessandro Castellani* Lead UX Architect Thunderbird

I know I'm coming late to this party, but I thought about it quite a lot over the past couple of weeks and I really like messenger.* For all the reasons that Philipp laid out, I didn't really like the alternatives. Ryan Sipes Community and Business Development Manager Thunderbird <https://thunderbird.net> On 4/24/19 10:02 AM, Alessandro Castellani wrote: > > I don't mind messenger.* as it kind of encapsulate the whole TB > ecosystem without creating too much confusion. > > I'm not sure if this is a silly suggestion, but what about using > something more generic like extension.* or actually api.*? > > Cheers > > On 2019-04-24 4:58 a.m., Claudio Luck wrote: >> On 24.04.19 13:13, Philipp Kewisch wrote: >>> Hey Folks, >>> >>> in bug 1517162 I'm aiming to provide a new global on MailExtension >>> windows because using browser.* can be really confusing if there is not >>> actually a browser. Two questions for discussion: >>> >>> >>> 1) Let's bikeshed on a name for the global. I originally used mail.* in >>> the patch, but this doesn't work well for when we have chat or calendar >>> APIs. Adding a new global for calendar or chat doesn't seem like a good >>> idea to me, and mail.calendar.* is confusing as well. >>> >>> Using thunderbird.* seems too product specific. In the browser namespace >>> it started with chrome.* but when Firefox adopted the API they chose >>> browser.* to be more generic. >>> >>> Geoff suggested messenger.* which I like a lot. This would work well >>> with messenger.chat.* , less so but still acceptable with >>> messenger.calendar.* >> communicator.* also comes to mind, and would put the emphasis more on >> the terminal/tool than the message delivery agency. Calendar and Email >> for example have many properties of local storage, which semantically >> would feel a bit out of scope in messenger.*. >> >> Best >> Claudio >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > -- > *Alessandro Castellani* > Lead UX Architect > Thunderbird > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Thanks all, Alex, I don't think extension or api is a silly suggestion. You are right it would be more generic and I can see how it makes sense. For my personal taste it would be a bit too generic though. I'm sensing a slight preference for messenger and will go with that unless there are grave disagreements. Philipp On 5/8/19 8:30 PM, Ryan Sipes wrote: > > I know I'm coming late to this party, but I thought about it quite a > lot over the past couple of weeks and I really like messenger.* > > For all the reasons that Philipp laid out, I didn't really like the > alternatives. > > Ryan Sipes > Community and Business Development Manager > Thunderbird <https://thunderbird.net> > > On 4/24/19 10:02 AM, Alessandro Castellani wrote: >> >> I don't mind messenger.* as it kind of encapsulate the whole TB >> ecosystem without creating too much confusion. >> >> I'm not sure if this is a silly suggestion, but what about using >> something more generic like extension.* or actually api.*? >> >> Cheers >> >> On 2019-04-24 4:58 a.m., Claudio Luck wrote: >>> On 24.04.19 13:13, Philipp Kewisch wrote: >>>> Hey Folks, >>>> >>>> in bug 1517162 I'm aiming to provide a new global on MailExtension >>>> windows because using browser.* can be really confusing if there is not >>>> actually a browser. Two questions for discussion: >>>> >>>> >>>> 1) Let's bikeshed on a name for the global. I originally used mail.* in >>>> the patch, but this doesn't work well for when we have chat or calendar >>>> APIs. Adding a new global for calendar or chat doesn't seem like a good >>>> idea to me, and mail.calendar.* is confusing as well. >>>> >>>> Using thunderbird.* seems too product specific. In the browser namespace >>>> it started with chrome.* but when Firefox adopted the API they chose >>>> browser.* to be more generic. >>>> >>>> Geoff suggested messenger.* which I like a lot. This would work well >>>> with messenger.chat.* , less so but still acceptable with >>>> messenger.calendar.* >>> communicator.* also comes to mind, and would put the emphasis more on >>> the terminal/tool than the message delivery agency. Calendar and Email >>> for example have many properties of local storage, which semantically >>> would feel a bit out of scope in messenger.*. >>> >>> Best >>> Claudio >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> -- >> *Alessandro Castellani* >> Lead UX Architect >> Thunderbird >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

messenger.* indeed sounds like a great option!  -Magnus On 08-05-2019 23:47, Philipp Kewisch wrote: > Thanks all, > > Alex, I don't think extension or api is a silly suggestion. You are > right it would be more generic and I can see how it makes sense. For > my personal taste it would be a bit too generic though. > > I'm sensing a slight preference for messenger and will go with that > unless there are grave disagreements. > > Philipp > > On 5/8/19 8:30 PM, Ryan Sipes wrote: >> >> I know I'm coming late to this party, but I thought about it quite a >> lot over the past couple of weeks and I really like messenger.* >> >> For all the reasons that Philipp laid out, I didn't really like the >> alternatives. >> >> Ryan Sipes >> Community and Business Development Manager >> Thunderbird <https://thunderbird.net> >> >> On 4/24/19 10:02 AM, Alessandro Castellani wrote: >>> >>> I don't mind messenger.* as it kind of encapsulate the whole TB >>> ecosystem without creating too much confusion. >>> >>> I'm not sure if this is a silly suggestion, but what about using >>> something more generic like extension.* or actually api.*? >>> >>> Cheers >>> >>> On 2019-04-24 4:58 a.m., Claudio Luck wrote: >>>> On 24.04.19 13:13, Philipp Kewisch wrote: >>>>> Hey Folks, >>>>> >>>>> in bug 1517162 I'm aiming to provide a new global on MailExtension >>>>> windows because using browser.* can be really confusing if there is not >>>>> actually a browser. Two questions for discussion: >>>>> >>>>> >>>>> 1) Let's bikeshed on a name for the global. I originally used mail.* in >>>>> the patch, but this doesn't work well for when we have chat or calendar >>>>> APIs. Adding a new global for calendar or chat doesn't seem like a good >>>>> idea to me, and mail.calendar.* is confusing as well. >>>>> >>>>> Using thunderbird.* seems too product specific. In the browser namespace >>>>> it started with chrome.* but when Firefox adopted the API they chose >>>>> browser.* to be more generic. >>>>> >>>>> Geoff suggested messenger.* which I like a lot. This would work well >>>>> with messenger.chat.* , less so but still acceptable with >>>>> messenger.calendar.* >>>> communicator.* also comes to mind, and would put the emphasis more on >>>> the terminal/tool than the message delivery agency. Calendar and Email >>>> for example have many properties of local storage, which semantically >>>> would feel a bit out of scope in messenger.*. >>>> >>>> Best >>>> Claudio >>>> >>>> _______________________________________________ >>>> Maildev mailing list >>>> Maildev@lists.thunderbird.net >>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>> -- >>> *Alessandro Castellani* >>> Lead UX Architect >>> Thunderbird >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

+1 for asking this. I like mail.* messenger.* is also OK Ben Philipp Kewisch wrote on 24.04.19 13:13: > Hey Folks, > > in bug 1517162 I'm aiming to provide a new global on MailExtension > windows because using browser.* can be really confusing if there is not > actually a browser. Two questions for discussion: > > > 1) Let's bikeshed on a name for the global. I originally used mail.* in > the patch, but this doesn't work well for when we have chat or calendar > APIs. Adding a new global for calendar or chat doesn't seem like a good > idea to me, and mail.calendar.* is confusing as well. > > Using thunderbird.* seems too product specific. In the browser namespace > it started with chrome.* but when Firefox adopted the API they chose > browser.* to be more generic. > > Geoff suggested messenger.* which I like a lot. This would work well > with messenger.chat.* , less so but still acceptable with > messenger.calendar.* > > > 2) Should we restrict Thunderbird specific APIs to the messenger.* > namespace? Firefox does this I think in very few cases, I think in the > browser.menus.* namespace there are functions that are not available on > chrome.menus.*. This would be more work from a technical perspective, > but I think it is possible. > > > Looking forward to your input > > Philipp > > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >

Aren't we (TB) coming from communicator ? god old netscape days. So why not reanimate it? +1  for communicator.* Am 24.04.19 um 13:13 schrieb Philipp Kewisch: > Hey Folks, > > in bug 1517162 I'm aiming to provide a new global on MailExtension > windows because using browser.* can be really confusing if there is not > actually a browser. Two questions for discussion: > > > 1) Let's bikeshed on a name for the global. I originally used mail.* in > the patch, but this doesn't work well for when we have chat or calendar > APIs. Adding a new global for calendar or chat doesn't seem like a good > idea to me, and mail.calendar.* is confusing as well. > > Using thunderbird.* seems too product specific. In the browser namespace > it started with chrome.* but when Firefox adopted the API they chose > browser.* to be more generic. > > Geoff suggested messenger.* which I like a lot. This would work well > with messenger.chat.* , less so but still acceptable with > messenger.calendar.* > > > 2) Should we restrict Thunderbird specific APIs to the messenger.* > namespace? Firefox does this I think in very few cases, I think in the > browser.menus.* namespace there are functions that are not available on > chrome.menus.*. This would be more work from a technical perspective, > but I think it is possible. > > > Looking forward to your input > > Philipp > > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

actually, i didn't consider name conflicts. mail is likely to conflict with local variables. messenger is much less likely to conflict. so, i change my vote from mail to messenger.* Ben Am 9. Mai 2019 23:41:20 MESZ schrieb Ben Bucksch <ben.bucksch@beonex.com>: >+1 for asking this. > >I like mail.* >messenger.* is also OK > >Ben > >Philipp Kewisch wrote on 24.04.19 13:13: >> Hey Folks, >> >> in bug 1517162 I'm aiming to provide a new global on MailExtension >> windows because using browser.* can be really confusing if there is >not >> actually a browser. Two questions for discussion: >> >> >> 1) Let's bikeshed on a name for the global. I originally used mail.* >in >> the patch, but this doesn't work well for when we have chat or >calendar >> APIs. Adding a new global for calendar or chat doesn't seem like a >good >> idea to me, and mail.calendar.* is confusing as well. >> >> Using thunderbird.* seems too product specific. In the browser >namespace >> it started with chrome.* but when Firefox adopted the API they chose >> browser.* to be more generic. >> >> Geoff suggested messenger.* which I like a lot. This would work well >> with messenger.chat.* , less so but still acceptable with >> messenger.calendar.* >> >> >> 2) Should we restrict Thunderbird specific APIs to the messenger.* >> namespace? Firefox does this I think in very few cases, I think in >the >> browser.menus.* namespace there are functions that are not available >on >> chrome.menus.*. This would be more work from a technical perspective, >> but I think it is possible. >> >> >> Looking forward to your input >> >> Philipp >> >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> >http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> > > >_______________________________________________ >Maildev mailing list >Maildev@lists.thunderbird.net >http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net -- Sent from my phone. Please excuse the brevity.