Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rt-pmc] SDK Discussion

Great pointer John.  Thanks.  This is exactly the kind of reaction we have been talking about. Some folks at least expect to *install* the "SDK" into their IDE (their development environment) and then start a hacking.

It is really pretty impressive just how confusing it can be when expectations/assumptions are mismatched!

BTW, in the interest of shared understanding, I would like to point out a few things about your comment 20.
1) They can install tools directly in the IDE (Help > Install New Software).
This is intended for installing purely runtime components that make up the IDE.
As Paul and Remy have mentioned, SWT is always already installed here since it
is required by the platform.

Would be better here to say "install purely *tooling* components in the IDE". 
2) They can install tools into their "target platform". This is the set of
Something like "...can *add runtime components (and source)* to their target platform" would be clearer.  Tools go in the IDE, runtime components in the target.
software that the user of the IDE is developing against. Typically they will want source code and documentation to come along with it. In the Eclipse community we typically refer to this trio of source, binaries, and documentation as an "SDK", although there has been some recent discussion on renaming this term because it is overloaded and means different things to different people.
Putting the doc in the target platform does not help as PDE does not contribute target help extensions to the IDE's help system.  Developer doc and JavaDoc is not read from the target (well, java doc is read from the source but is not the full production JavaDoc).  I've opened Bug 310688 to track this.

Jeff

On 2010-04-27, at 1:16 PM, John Arthorne wrote:

I just wanted to point those interested in the "SDK" discussion to this recent bug report from a developer trying to install everything needed to develop with SWT (binaries, source, and javadoc). It is exactly along the lines of the recent RT discussions, with the possible difference that he is *not* a plug-in developer, but rather a Java developer wanting to use SWT as a pure Java library. I don't know if this is beyond the scope of your discussions, or if the notion of "target" extends to things beyond OSGi runtime instances. The bug nicely illustrates both the frustration for users of our tools, and the confusion about what it means to "install" a software package into your IDE.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=310399

John

On Sun, Apr 25, 2010 at 6:05 AM, Christian Campo <Christian.Campo@xxxxxxxxxxxx> wrote:
Hi,

I started the discussion page about the SDK. http://wiki.eclipse.org/Talk:SDK. Its not much but I put down what I think about the naming the SDK.

Hope that more people express their opinion.

christian
-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: 069 / 27 22 18 0
fax: 069 / 27 22 18 22
web: www.compeople.de
Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
Ust-Ident.-Nr: DE207665352
-------------------------------------------------------------
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc

_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc


Back to the top