Doug Scott wrote: > Hmmm, the poxy Open Solaris Website trashed my original reply. Attempt > 2..... > > Hey Brian, > I had done some work on something like this with netbeans awhile > ago. The only problem that stopped me from going much further, was the > large changes (for the better) between Netbeans 5 and Netbeans 6. I > would suggest that if you do any work on this, use Netbeans 6 beta, as > it should be easier (especially work around the editor), and you will > not have to change too much when version 6 is released. I would be > keen to help out if needed. Thanks for the suggestion. I was assuming at least Netbeans 5.5.
> > The only problem I can see is if your are building Gnome from scratch. > As Java can rely on JDS, you have to be careful that you can still use > Netbeans while you are building the code. At the moment most of the > JDS developers build in a chroot environment (I use a brandz zone). > You might have to consider this in your design. > > Doug > Good point, you don't want to overwrite the environment you're running on. I was assuming that most people would use it for applications rather than for building and fixing the underlying GNOME libraries, but increasing the number of contributors to GNOME would be a good side effect. I hadn't thought about using a zone as the test deployment environment. It would be really interesting to have zone > > Brian Nitz wrote: >> This proposal was a bit late to make it into the google summer of >> code list of suggestions, but I wonder if anyone has suggestions on >> whether this could be useful: >> >> Netbeans OpenSolaris desktop Common Build Environment plugin >> >> Summary: >> A netbeans plugin enhancement would integrate CBE, SVN and the C/C++ >> plugin pack for NetBeans to allow automatic retrieval of code and >> dependencies into an environment which could be built, edited, >> debugged, patched and redeployed. >> >> Why: >> When developer tools are rolled into an IDE, it helps cross-platform >> developers and beginning developers know what tools are available >> under OpenSolaris. Automating the generation of the IDE project from >> the spec file saves time and could encourage more people to become >> involved in development software for and on OpenSolaris. >> >> Details: >> >> The JDS Common Build Environment (CBE) >> <http://www.opensolaris.org/os/project/jds/contributing/building/> >> contains the tools necessary to build GNOME, Mozilla, Evolution and >> other common open source desktop applications on Opensolaris >> distributions such as Solaris 10 and Nevada. These tools allow SPEC >> files to be used to specify how to build the software and how the >> software is to be packaged and deployed. These tools make it easy to >> build software for which opensolaris spec files already exist. >> Netbeans is an IDE commonly used for Java development. It is >> possible to develop Java based desktop software from within netbeans, >> either using native Swing/AWT or the new Java-Gnome bindings. >> However developing native GNOME applications within the IDE only >> became possible recently with the development of optional NetBeans >> plug-in packs for alternative languages such as C and C++: >> www.netbeans.org/products/cplusplus/ >> <http://www.netbeans.org/products/cplusplus/> Netbeans' language >> specific plugin features include syntax highlighting, code >> completion, integrated build, profiling and debug. >> >> This proposal would automate the process of creating a Netbeans >> project from a .SPEC file. The Netbeans CBE plugin would read a SPEC >> file and use it along with #includes with the specified source >> tarballs to automatically pull appropriate source tars and checkouts >> of patches into the build environment. The developer could build, >> test, patch and check patches back into SVN/CVS all from within the >> Netbeans build environment. >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> desktop-discuss mailing list >> desktop-discuss at opensolaris.org
