Talk:Extension Manager:Sqlite Storage: Difference between revisions
No edit summary |
No edit summary |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
So how will that affect [http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/suite/browser/navigatorOverlay.xul&mark=&rev=1.334&mark=443-459#443 this]? | So how will that affect [http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/suite/browser/navigatorOverlay.xul&mark=&rev=1.334&mark=443-459#443 this]? | ||
Seamonkey should be able to query the extension manager for a list of themes on startup and display those, then respond to notifications to alter the list. This is assuming sqlite templates aren't available of course. | |||
: [[User:Mossop|Mossop]] | : [[User:Mossop|Mossop]] | ||
''Rather than being customised for displaying appropriately in the UI the database should instead be properly normalised with whatever information we need now and may need in the future. It should not include transient data that is only needed before the app restarts to keep the UI correct.'' | |||
It isn't clear to me how database normalization applies to customised for displaying appropriately in the UI. | |||
--[[User:Robert Strong|Robert Strong]] 12:54, 10 July 2008 (PDT) | |||
Yeah that paragraph is a bit mixed up. My point is that I don't think we should try to include all the the currently calculated properties that are available on the rdf datasource in the database. For example for the iconURL property we should just include whatever was in the install.rdf rather than convert it to a file uri for themes and so on. The API for accessing it can handle that. | |||
: [[User:Mossop|Mossop]] | |||
Not directly related to the conversion of the existing rdf to Sqlite but how about adding history for installs and updates? | |||
--[[User:Robert Strong|Robert Strong]] 09:54, 18 July 2008 (PDT) | |||
Latest revision as of 16:54, 18 July 2008
So how will that affect this?
Seamonkey should be able to query the extension manager for a list of themes on startup and display those, then respond to notifications to alter the list. This is assuming sqlite templates aren't available of course.
Rather than being customised for displaying appropriately in the UI the database should instead be properly normalised with whatever information we need now and may need in the future. It should not include transient data that is only needed before the app restarts to keep the UI correct.
It isn't clear to me how database normalization applies to customised for displaying appropriately in the UI. --Robert Strong 12:54, 10 July 2008 (PDT)
Yeah that paragraph is a bit mixed up. My point is that I don't think we should try to include all the the currently calculated properties that are available on the rdf datasource in the database. For example for the iconURL property we should just include whatever was in the install.rdf rather than convert it to a file uri for themes and so on. The API for accessing it can handle that.
Not directly related to the conversion of the existing rdf to Sqlite but how about adding history for installs and updates? --Robert Strong 09:54, 18 July 2008 (PDT)