[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] Installation stellation
|
Hi Martin,
At 11:56 PM 8/12/2002 +0200, Martin Möbius wrote:
Hi,
eclipse is downloading the stellation sources from cvs, so I can write a bit
(btw. the javadocs should not be below org.eclipse.stellation.misc, to much
for a modem).
Doh! (hand slapping head). You're absolutely right.
I'll move the javadocs to a more suitable location (tbd).
I want to install stellation at a win2k workstation, Mark told me in the
newsgroup that Ringo already has experiences with that, so I would be happy
to hear from him.
I tried to follow
http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/org.eclipse.stellati
on/plugins/org.eclipse.stellation.misc/doc/manuals/setting-up.html
.
An important step which is easy to miss is to set eclipse where it searches
for plugins (preferences|Plug-In Development|Target Platform|Not in
workspace). If you do not do so, the needed libs are not found and you end
up with many compile errors.
I will update setting-up.html soon, for this and other corrections.
In future, I hope to use the Eclipse Update Manager for installing the
necessary 3rdparty jars; I've done this locally, but we need permission
(which I've asked for) to post the actual jars on eclipse.org.
I've also built an Eclipse "Feature Project" for creating a Stellation CM
"feature": this installs all the Stellation CM plugins for use as part of
Eclipse.
This will come in handy for deploying Stellation; for development work,
CVS seems like the best way to go for now.
I noticed that all fields are at the end of a class, imo unusual, is this
the code style or the result from using svc?
As Mark noted, it's part of our coding style (but not stated in the Coding
Guidelines doc; another thing to update!). Reasons include:
* Information hiding: keeping fields at the end discourages casual use.
* Clutter reduction: it's easier (fmo) to understand a class API if I'm
not tripping over internal fields and other plumbing -- I keep
protected/private
methods towards the end of a file for similar reasons.
* Centralized plumbing: keeping fields together makes it easier both to
estimate instance size and to understand internal class design when I need to.
Constants which are part of the public class API are typically kept either
at the top of the class, or by the public methods using them.
Regards,
Jim
_________________________________________________
Jim Wright
The Stellation Project (Advanced Programming Tools Group)
IBM T.J. Watson Research Center
