MozillaWiki

Calendar:Lightning:Integration Issues: Difference between revisions

Calendar Discussion

Calendar:Lightning:Integration Issues (view source)

Revision as of 21:52, 1 April 2005

90 bytes added ,  1 April 2005
no edit summary
No edit summary
No edit summary
Line 1: Line 1:
This is a very rough doc; I use it to keep track of problems we need to address for Lightning and likely for other extension authors as well.  I need to find/file bugs on these to track and suggest improvements in.
This is a very rough doc; I use it to keep track of problems we need to address for Lightning and likely for other extension authors as well.  I need to find/file bugs on these to track and suggest improvements in.
--[[User:Shaver|Shaver]] 10:51, 30 Mar 2005 (PST)
--[[User:Shaver|Shaver]] 10:51, 30 Mar 2005 (PST)
Thunderbird Related Issues and Implementation Ideas
* 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.)
* Can't search addressbook
** Have to retrieve all cards and enumerate (!)
* hard to plug in new addressbook implementations (more RDF stuff, painful interfaces)
** The GroupDAV guy is suffering under this, proposing new ifaces, stuck between a rock and a hard place!
* Need to participate in the folder/server/msgdbheader model to get into the Tbird search model.
** Can't participate in server/folder model without security-risky, leak-prone, JS-incompatible RDF work.
** Also need to implement large and baroque nsIMsgIncomingServer and nsIMsgFolder interfaces.
** 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.
* 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.
* Thunderbird skin/chrome build system very confusing, with classic and qute and mailnews and mail.  Some docs or fixes there would be greatly helpful.
General Platform Development Issues


* Little-to-no error reporting for overlay errors.
* Little-to-no error reporting for overlay errors.
Line 14: Line 35:


* 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.
* Need to participate in the folder/server/msgdbheader model to get into the Tbird search model.
** Can't participate in server/folder model without security-risky, leak-prone, JS-incompatible RDF work.
** Also need to implement large and baroque nsIMsgIncomingServer and nsIMsgFolder interfaces.
** 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.  And by hard, I mean impossible.
* 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.
* Can't search addressbook
** Have to retrieve all cards and enumerate (!)
* hard to plug in new addressbook implementations (more RDF stuff, painful interfaces)
** The GroupDAV guy is suffering under this, proposing new ifaces, stuck between a rock and a hard place!
* Thunderbird skin/chrome build system very confusing, with classic and qute and mailnews and mail.  Some docs or fixes there would be greatly helpful.


* Venkman doesn't help at all for debugging with JS component issues for which we have well-isolated (xpcshell) test cases; have to choose between running easily in xpcshell and having venkman available (by loading it into tbird or such).  Maybe xulrunner can help here?
* Venkman doesn't help at all for debugging with JS component issues for which we have well-isolated (xpcshell) test cases; have to choose between running easily in xpcshell and having venkman available (by loading it into tbird or such).  Maybe xulrunner can help here?


* 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.  (Just analyzing the IMAP protocol code is Very Hard, in fact, due to the multi-variable state machines.)
ChrisHofmann
Confirmed users, Bureaucrats and Sysops emeriti
1,531

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/5251"