667
edits
Changes
no edit summary
==== Tools ====
Ideally these would be installable via a single setup/wizard/installer as options, or perhaps in the model of the Open CD (i.e., a XUL Runner web based installer, where you choose each package separately).
* [http://go.microsoft.com/fwlink/?LinkId=51410&clcid=0x409 Visual C++ 2005 Express Edition] - checking with Microsoft to see what choices there are for including or auto-downloading this
** vi
** komodo
* .mozconfig files for standard development scenarios
=== Source Code ====
As much as possible, provide source code for the Mozilla-based tools included in the kit. This is partly done to make it possible to write learning and other resource material that discusses code explicitly, but also in order to provide an example of the importance of providing open source code.
* Firefox
** Tagged major release version (probably Firefox 3). This version of the code would be used in almost all examples and document resources
** Trunk version. This would be useful for people with limited bandwidth, because they could cvs update this version instead of having to pull the entire tree
* Thunderbird
* OpenKomodo
* Miro
=== Local Versions of Remote Mozilla Tools ===
Because both of these projects assume a web application being used locally, it might make sense to do a Prism or XUL Runner app, specialized to host them (cf. http://wiki.oxymoronical.com/Projects:MozDevDocs)
* Local MXR
The local MXR would index only the trees in the kit (see the Source Code section). The look of the HTML pages should be modified somewhat to make it clear that this is a separate resource to what is on the web, and therefore the code indexed is not the same.
* Local MDC not the entire
Where MDC is a wiki meant for distributed collaboration, the documentation in the kit is read-only. Furthermore, where wikis prefer writers to readers, the documentation in the kit needs more top-down organization to link everything together (cf. MSDN). Getting rid of the wiki would mean that the content can be distributed as files vs. needing a web/wiki server.
Like the local MXR, the look-and-feel of the pages should be altered so that they don't appear to be MDC, and it's clear that this is something separate. Again, a Prism app could be used, and perhaps/hopefully the same one as for the local MXR.
==== Software ====
* KomodoEdit
* Songbird
==== Documentation ====
Many different types of documentation would be included in the kit, some of which exist
==== Questions/Issues ====
* How to deal with localization?
* Can we allow the user to modify VS such that it knows about the symbol/source server when debugging?
* Is it wise to give source that can't be built? I'm thiking of Miro, OpenKomodo, etc. for which you need a different toolchain than Firefox (version wise). My idea in including them is that you can refer to them. Maybe this makes it more difficult rather than less so.
* What's the best way to use MDC and other Mozilla documentation in this such that future releases don't need a lot of manual work to pull in new material?
* Should source code for popular extensions be included and indexed? This might be nice in terms of providing learning/teaching materials for extension developers.
