Confirmed users
455
edits
Calendar:Lightning:Integration Issues: Difference between revisions
Calendar:Lightning:Integration Issues (view source)
Revision as of 19:25, 30 March 2005
, 30 March 2005no edit summary
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
* Also, extension manager error reporting is sorely lacking. Some of that is because the RDF datasource stuff sucks, and doesn't report errors back up the chain. F.e. update.rdf served as wrong (but RDF-legal: application/rdf+xml) MIME type. | * Also, extension manager error reporting is sorely lacking. Some of that is because the RDF datasource stuff sucks, and doesn't report errors back up the chain. F.e. update.rdf served as wrong (but RDF-legal: application/rdf+xml) MIME type. | ||
* Reload-to-test cycle painful -- can't even use "reload chrome" extension in tbird for those cases, let alone where JS components change, etc. | * Reload-to-test cycle painful -- can't even use "reload chrome" extension in tbird for those cases (it doesn't work), let alone where JS components change, etc. | ||
* DOMi and Venkman don't work well with Thunderbird -- DOMi was dropped in Tbird 0.8 for DL-size reasons, and people said it was available as an extension, but I can only find an old one from Chris Neale that I have to hack install.rdf for. | * DOMi and Venkman don't work well with Thunderbird -- DOMi was dropped in Tbird 0.8 for DL-size reasons, and people said it was available as an extension, but I can only find an old one from Chris Neale that I have to hack install.rdf for. | ||
| Line 19: | Line 19: | ||
** Also need to implement large and baroque nsIMsgIncomingServer and nsIMsgFolder interfaces. | ** Also need to implement large and baroque nsIMsgIncomingServer and nsIMsgFolder interfaces. | ||
** MsgDbHeader stuff looks very mork-centered, hard to use with other stores. | ** MsgDbHeader stuff looks very mork-centered, hard to use with other stores. | ||
* Similarly with the threading model; having calendar events threaded into email discussions resulting from the invitations (quite common, I find) looks to be largely impossible. | |||
* Overlaying new columns into tree widgets is hard. | * Overlaying new columns into tree widgets is hard. And by hard, I mean impossible. | ||
* Everyone seems to have to write their own "is a message selected?" sorts of command handlers, since we don't have any good ones to reuse. | * Everyone seems to have to write their own "is a message selected?" sorts of command handlers, since we don't have any good ones to reuse. | ||
| Line 35: | Line 36: | ||
* xpcshell doesn't work well with components installed in firefox/tbird profiles, which makes reproducing and testing bugs/fixes much harder. | * xpcshell doesn't work well with components installed in firefox/tbird profiles, which makes reproducing and testing bugs/fixes much harder. | ||
* Would be nice to be able to use IMAP as a calendar store, and maybe for centralized prefs, etc., but driving the IMAP protocol code from non-mailnews apps looks to be Very Hard. | * Would be nice to be able to use IMAP as a calendar store, and maybe for centralized prefs, etc., but driving the IMAP protocol code from non-mailnews apps looks to be Very Hard. (Just analyzing the IMAP protocol code is Very Hard, in fact, due to the multi-variable state machines.) | ||