SeaMonkey:Suite Directory Layout: Difference between revisions

Line 138: Line 138:


== IRC discussion snippets ==
== IRC discussion snippets ==
=== [2007-01-12 13:39 PST] - topic: mailnews locale organization in suite ===
<br><KaiRo> Standard8Away: btw, as we usually have only one or two files there, we tend not to do a separate *-region in suite/
<br><KaiRo> phew, locale/en-US/messenger/ in en-US.jar really has all the files of the different dirs merged, (almost) no subdirs? wow...
<br><NeilZZZ> KaiRo: my memory is that addressbook and messengercompose have their own subdirs, but everything else is in that dir
<br><KaiRo> NeilZZZ: yes, that's what I'm seeing... which means that we probably need/want(?) to mirror that in the new structure in suite/locales/
<br><KaiRo> hmm, even pref panels are directly in mailnews/
<br><NeilZZZ> well, there are two things to consider
<br><NeilZZZ> 1) we could reorganise mailnews under suite but in jar.mn it would still be mapped to the original locations
<br><NeilZZZ> 2) we could then reorganise messenger.jar with the new locations
<br><NeilZZZ> but we could only do that for forked files
<br><KaiRo> hmm, true, we could reorganize in the source tree, but as you said, matching chrome structure to that would be a good idea, and that's hard because of shared files
<br><KaiRo> though somehow I start thinking that it might be a good idea to think of forking the whole mailnews UI and make mozilla/mailnews/ only have backend code in the long term
<br><KaiRo> NeilZZZ: it might be safe and perhaps a good idea in any case to move pref panels the way you describe, like Standard8Away proposes in his doc
<br><KaiRo> just not sure if it's correct/good to move the MAPI one there as well
<br><KaiRo> wait, that's not even a panel, that's just an overlay


=== [2006-01-17 07:00 PST] - topic: suite/ organization ===
=== [2006-01-17 07:00 PST] - topic: suite/ organization ===
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628

edits