667
edits
Changes
consolidated docs/mdc
==== Local Versions of Remote Mozilla Tools ====
===== "Front Page" =====
The local apps app would include a "Front Page" that allows navigation to the tools, documentation, and other resources. One idea is to include a news feed so that developers could start to get connected to the community and see what's happening in the developer space.
* [http://developer.mozilla.org/devnews/ Mozilla Developer News]
I'm not sure the best way to do this, in terms of having a usermode, lightweight web server that can run this on Windows. We could use something like [http://www.lighttpd.net/ lighttpd] or one of the other [http://en.wikipedia.org/wiki/Tiny_web_servers small servers] for win32. Ideally, this could run as an app vs. a service--people won't want to install a service just to search source code.
===== Local MDC ===== 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-Documentation 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 ==== The user will get copies of the latest stable releases of popular Mozilla software. This is not strictly necessary for development, but helps give a sense of what's possible with the Mozilla platform. NOTE: these could be bundled on a supplementary disc: * Firefox* Thunderbird* XULRunner* Prism* Miro* KomodoEdit* Songbird Learning Materials ==== Documentation ====
* Documentation on using each of the tools included in the kit
* Reference and other Documentation (much from [http://developer.mozilla.org MDC]). 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. In addition, some docs would need to be changed sho they reference the contents of the kit (i.e., where multiple tools can be used, focus on the one(s) that are included in the kit).
* Learning materials (much from [http://zenit.senecac.on.ca/wiki Seneca courses])
* Glossary of Terms
==== Software ====
The user will get copies of the latest stable releases of popular Mozilla software. This is not strictly necessary for development, but helps give a sense of what's possible with the Mozilla platform. NOTE: these could be bundled on a supplementary disc:
* Firefox
* Thunderbird
* XULRunner
* Prism
* Miro
* KomodoEdit
* Songbird
==== Questions/Issues ====
