117214 - (mdrk) Create a Mozilla Developer Resource Kit

Status: RESOLVED WONTFIX

(Core :: General, enhancement)

Description

[andreww]

Comment 1

[andreww]

This is a bug for the creation of a downloadable Software Developers Kit for 
folks who want to develop on the mozilla platform. This would include scripts, 
examples, docs, etc. to help someone get started working on mozilla as an 
application development platform.

Comment 2

[andreww]

setting milestone - we should try to have at least a beta of this by 1.1....

Comment 3

[Asa Dotzler [:asa]]

I'm thinking mozilla minus all the apps except for DOM Inspector and XULkit. As
small as we can make it. Would be nice if DOM Inspector would let you save
changes (even if it blows formatting). Setting myself as QA and Andreww as owner
for now. 

Comment 4

[Michael Hearn]

It'd have to have Venkman in as well.

Is there some kind of super-tracker bug for "Make Mozilla kick ass as an
application platform" that this could block?

Comment 5

[andreww]

it should also have the dom - inspector... if we got dom inspector able to 
write to files, we'd almost have a crude IDE.

Comment 6

[andreww]

Note to self: We gotta add this http://xulplanet.com/tutorials/xulapp/ 
This tutorial is pretty cool.

Comment 7

[Benjamin Smedberg]

Embedders could really use this.  Rather than using CVS checkout or pulling a
source tree, we could just download an SDK. It should contain:

1) All binaries shipped with the standard mozilla release.
2) All frozen interface definitions and header files
3) Non-frozen headers and interfaces that an embedder/developer might need (with
some sort of warning "These are not frozen")

Comment 8

[Akkana Peck]

It doesn't need the binaries and libraries -- they will be downloaded as part of
the app or the GRE, once GRE packages are available, so why download that part
twice?  It would be nice to separate the developer-specific stuff from the
runtime stuff.  Headers, tools, and examples would make a really nice package.

I see that mozilla.org is offering Windows GRE and SDK downloads, but they
aren't available for any other platform.  I couldn't find a bug tracking that --
is this it?

Comment 9

[Doug Turner (:dougt)]

It needs *some* libraries.  right now, it needs nspr (including the pl* libs),
the xpcom glue lib, and embed string.  The reason for nspr is described here in
bug 191049.

Any other libs should probably be removed.

Also, I believe that this bug should be marked FIXED.  You can download a GECKO
sdk from ftp.mozilla.org.

Comment 10

[Akkana Peck]

> You can download a GECKO sdk from ftp.mozilla.org

Where?  I just went through all the nightly directories for the last couple of
days as well as the releases/1.3 directory, and I see sdk and gre builds for
Windows, but I don't see anything with either gre or sdk in the name for linux
or mac.

Comment 11

[Doug Turner (:dougt)]

for 1.4a:
ftp://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4a/gecko-sdk-i686-pc-linux-gnu-1.4a.tar.gz
ftp://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4a/gecko-sdk-win32-1.4a.zip

for 1.3:
file a bug against leaf.  i am not sure where they are.

Comment 12

[David Humphrey (:humph)]

I wasn't aware of this bug, but since I'm doing exactly this right now, I'll take it instead of filing a new one.

See http://zenit.senecac.on.ca/wiki/index.php/Mozilla_Developer_Resource_Kit

and a current prototype:

http://142.204.133.123/mxr

What's the right way to re-categorize this in terms of Product/Component?

Comment 13

[Philip Chee]

> What's the right way to re-categorize this in terms of Product/Component?

Probably Other Applications since the CCK is in that Product. Perhaps you could post to mozilla.dev.planning and ask for suggestions there.

Comment 14

[Robert Kaiser]

Moving at least to Core as SeaMonkey is even more wrong.