On Sat, Apr 21, 2012 at 08:31, Roger Luedecke
Not really sure to be frank. But one thing I'd like is the ability to easilly browse cllasses/functions. Especially since it is really the API libraries that do all the magic, and I am as of yet entirely unfamilar. ANd once again, I need Javascript. Though I'm aware Eclipse can run in ~Home, I don't like the mess that and other such things make. I prefer the clean organization and integration that a proper .rpm install does. Plus, Eclipse packages are available for everything BUT 12.1. Also heard about Aptana, which looks pretty damn sharp. I'd happily do it myself if I could figure out OBS or .rpm spec files. I thought Monodevelop had Javascript support, but it coughs up so many errors I'm afraid to use it.
On my setup, I have a separate drive where I keep all my external development tools (all being Eclipse and Netbeans). Eclipse is there in a directory called /Eclipse and then in that same directory I've got directories for my SDKs (Android for example) and all my project directories as well as a directory containing the Eclipse binaries plus any configuration... add an icon for Eclipse to my desktop and it's done. It's a nice neat package that keeps *everything* conveniently in one spot if I need to move it around. I find it "better" to manage this way than to use the RPMs (and this is a fairly consistent opinion of most people who use Eclipse)... and I've done this for several openSUSE releases. The only real difference between this and installing Eclipse from RPM is I've got the Eclipse binaries in that same directory, and it's not available to other users (then again, I'm the only user on this machine so it's not an issue). What got me started on installing Eclipse from the download vs RPM was that the RPM packaged Eclipse had something broken or messed up that prevented me from installing Android components using the Android SDK Manager)... it showed in the list of available bits, appeared to download, but failed to install... run the downloaded Eclipse and everything "just worked". Honestly, I'd say you're just making it hard on yourself. If you like Eclipse and woudl like to use it, then just download the latest and install it wherever you want. It does not need to be managed by RPM as it is completely self contained... there are really virtually zero benefits to installing it from RPM (other than updates, and that is a simple process with the standalone Eclipse too). C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org