NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
Replies:
19 -
Pages:
2
[
12
| Next
]
Threads:
[
Previous
|
Next
]
Well my real concern is that if 5.0 picks up my 4.1 project setting and then does something with them so that I can no longer use the 4.1.
What I really want to do is carry on using 4.1 for my work but also have a 5.0 installation just to have a play around with which doesn't effect my existing stuff.
NB has a great demo making community, I think this should be supported in the IDE, the Welcome screen should have a nice list of links to demos like this one, and others.
Thanks to Roman and Javalobby for the demo. NB 5 looks really appealing; depending on how stable/responsive the final product is on OS X, I may switch to NB.
Some of the architects of NetBeans are using MacOSX so it should work quite well I'm glad you guys liked my presentation. I promis that I will use proper pronunciation of Matisse in my next demos... I learned how to pronunce it properly right after the demo was published.
Well, well done.
Editor and CVS wise it seems that NB is catching up with Eclipse. Matisse seems very good, and the J2EE support is good as well.
In my next Swing project I may decide to get back to Netbeans for the UI coding, but leaving Eclipse behind is still difficult, since I rely on it for plug-ins that are developed exclusively for Eclise (like JasperAssistant, the Hibernate and Spring tools). Netbeans is still very lacking in this area, I mean, you should recognize that there are lots of people using those non standard tools to overcome the complexity/poor performance/poor productivity or standard J2EE.
I hope this can change with the new plugin support (from the open source plugins side) and the EJB3 spec (from the JEE standard tools side).
Also bear in mind that to make people switch back you have to provide an advantage that overcomes the switch cost. When I switched to Eclipse from NB 3.4 I really needed better editor, refactoring and CVS support. After two years on Eclipse I really don't feel the "find the plugin that suits you" problem like I newbie, but I still have to pay the price of changing habits (especially keyboard shortcuts, I'm not a "mouse programmer").
> Well, well done.
> Editor and CVS wise it seems that NB is catching up
> with Eclipse. Matisse seems very good, and the J2EE
> support is good as well.
>
> In my next Swing project I may decide to get back to
> Netbeans for the UI coding, but leaving Eclipse
> behind is still difficult, since I rely on it for
> plug-ins that are developed exclusively for Eclise
> (like JasperAssistant, the Hibernate and Spring
> tools). Netbeans is still very lacking in this area,
> I mean, you should recognize that there are lots of
> people using those non standard tools to overcome the
> complexity/poor performance/poor productivity or
> standard J2EE.
I think that now that Module development has got a big boost but there is definitely still room for improvement, there is a need to produce more documentation and diverse examples especially using 3rd party libraries/modules and then you will see many more plugins for non standard tools like Hibernate and Spring...
> I hope this can change with the new plugin support
> (from the open source plugins side) and the EJB3 spec
> (from the JEE standard tools side).
>
> Also bear in mind that to make people switch back you
> have to provide an advantage that overcomes the
> switch cost. When I switched to Eclipse from NB 3.4 I
> really needed better editor, refactoring and CVS
> support. After two years on Eclipse I really don't
> feel the "find the plugin that suits you" problem
> like I newbie, but I still have to pay the price of
> changing habits (especially keyboard shortcuts, I'm
> not a "mouse programmer").
I think the real advantage right now for people like me (J2ME programmer) is that NetBeans is the best tool for (J2ME), but i may be getting back to J2SE programming i simply love Matisse it's a killer feature, any UI programmer will find nothing like it in Eclipse for a very long time.
Also i like NetBeans best because it is more integrated, but it is definitely not a perfect IDE it still has a long way to go, but it's getting there, IMHO it is the open source IDE where you will see the most innovative things coming out, and also allot of catch up wend necessary.
There is also a need to make it more enterprise friendly, but that's another story...
> There is also a need to make it more enterprise
> friendly, but that's another story...
I'd be interested to know what you would like to see in this area. I know that you need a lot more than an EJB wizard to make an IDE enterprise friendly, but everyone has a different idea of enterprise friendliness. Can you please explain yours? Thanks.
* Use bundled Struts 1.2.7 library with javadoc.
* Create new web application with Struts support.
* Add Struts support to an existing web application.
* Create new Action and Form Bean using wizards.
* Use help for Struts tags in editor.
* Edit Struts configuration file using context sensitive dialogs for adding:
o Form Bean,
o Action,
o Forward/Include Action,
o Forward,
o Exception,
o Form Property.
* Use hyperlinking in configuration files for JSP files, Java classes and Struts actions.
* See Struts configuration files in web application's Configuration Files node.
* Use multiple Struts configuration files.
As for Spring, there is no extra support, but we have a decent XML editor, which was improved for 5.0. A good XML editor is important for Spring.
NetBeans 5.0
At 5:39 PM on Oct 4, 2005, Matthew Schmidt wrote:
Fresh Jobs for Developers Post a job opportunity
Watch the whole presentation now!
19 replies so far (
Post your own)
Re: NetBeans 5.0
Nice demo and the new version of Netbeans seems very cool.I'm currently using 4.1 at work. If I download the 5.0 Beta do I run the risk of it screwing up my 4.1 settings ?
Re: NetBeans 5.0
The settings are stored in different locations, so you'll be ok.Project compatibility is another issue. Backup your 4.1 projects before opening them in 5.0 unless you're ready to commit to 5.0 for development.
Re: NetBeans 5.0
Well my real concern is that if 5.0 picks up my 4.1 project setting and then does something with them so that I can no longer use the 4.1.What I really want to do is carry on using 4.1 for my work but also have a 5.0 installation just to have a play around with which doesn't effect my existing stuff.
Im using Win2K and Linux
Re: NetBeans 5.0 - Demo Support on the IDE
Sweet demo,NB has a great demo making community, I think this should be supported in the IDE, the Welcome screen should have a nice list of links to demos like this one, and others.
Re: NetBeans 5.0
Thanks to Roman and Javalobby for the demo. NB 5 looks really appealing; depending on how stable/responsive the final product is on OS X, I may switch to NB.Re: NetBeans 5.0
Some of the architects of NetBeans are using MacOSX so it should work quite wellRe: NetBeans 5.0
Well, well done.Editor and CVS wise it seems that NB is catching up with Eclipse. Matisse seems very good, and the J2EE support is good as well.
In my next Swing project I may decide to get back to Netbeans for the UI coding, but leaving Eclipse behind is still difficult, since I rely on it for plug-ins that are developed exclusively for Eclise (like JasperAssistant, the Hibernate and Spring tools). Netbeans is still very lacking in this area, I mean, you should recognize that there are lots of people using those non standard tools to overcome the complexity/poor performance/poor productivity or standard J2EE.
I hope this can change with the new plugin support (from the open source plugins side) and the EJB3 spec (from the JEE standard tools side).
Also bear in mind that to make people switch back you have to provide an advantage that overcomes the switch cost. When I switched to Eclipse from NB 3.4 I really needed better editor, refactoring and CVS support. After two years on Eclipse I really don't feel the "find the plugin that suits you" problem like I newbie, but I still have to pay the price of changing habits (especially keyboard shortcuts, I'm not a "mouse programmer").
Re: NetBeans 5.0
> Well, well done.> Editor and CVS wise it seems that NB is catching up
> with Eclipse. Matisse seems very good, and the J2EE
> support is good as well.
>
> In my next Swing project I may decide to get back to
> Netbeans for the UI coding, but leaving Eclipse
> behind is still difficult, since I rely on it for
> plug-ins that are developed exclusively for Eclise
> (like JasperAssistant, the Hibernate and Spring
> tools). Netbeans is still very lacking in this area,
> I mean, you should recognize that there are lots of
> people using those non standard tools to overcome the
> complexity/poor performance/poor productivity or
> standard J2EE.
I think that now that Module development has got a big boost but there is definitely still room for improvement, there is a need to produce more documentation and diverse examples especially using 3rd party libraries/modules and then you will see many more plugins for non standard tools like Hibernate and Spring...
> I hope this can change with the new plugin support
> (from the open source plugins side) and the EJB3 spec
> (from the JEE standard tools side).
>
> Also bear in mind that to make people switch back you
> have to provide an advantage that overcomes the
> switch cost. When I switched to Eclipse from NB 3.4 I
> really needed better editor, refactoring and CVS
> support. After two years on Eclipse I really don't
> feel the "find the plugin that suits you" problem
> like I newbie, but I still have to pay the price of
> changing habits (especially keyboard shortcuts, I'm
> not a "mouse programmer").
I think the real advantage right now for people like me (J2ME programmer) is that NetBeans is the best tool for (J2ME), but i may be getting back to J2SE programming i simply love Matisse it's a killer feature, any UI programmer will find nothing like it in Eclipse for a very long time.
Also i like NetBeans best because it is more integrated, but it is definitely not a perfect IDE it still has a long way to go, but it's getting there, IMHO it is the open source IDE where you will see the most innovative things coming out, and also allot of catch up wend necessary.
There is also a need to make it more enterprise friendly, but that's another story...
Re: NetBeans 5.0
> There is also a need to make it more enterprise> friendly, but that's another story...
I'd be interested to know what you would like to see in this area. I know that you need a lot more than an EJB wizard to make an IDE enterprise friendly, but everyone has a different idea of enterprise friendliness. Can you please explain yours? Thanks.
tomcat web services ?
Hello and well done!Does 5.0 has support for tomcat web services?
Re: tomcat web services ?
Hi, see this blog entry.Re: tomcat web services ?
Does 5.0 has support for struts and spring?Java email verify
http://www.wisesoft.biz/
Re: tomcat web services ?
what is the benefit of 5.0 than eclipse?http://www.wisesoft.biz/
Re: tomcat web services ?
5.0 does support Struts. You can:* Use bundled Struts 1.2.7 library with javadoc.
* Create new web application with Struts support.
* Add Struts support to an existing web application.
* Create new Action and Form Bean using wizards.
* Use help for Struts tags in editor.
* Edit Struts configuration file using context sensitive dialogs for adding:
o Form Bean,
o Action,
o Forward/Include Action,
o Forward,
o Exception,
o Form Property.
* Use hyperlinking in configuration files for JSP files, Java classes and Struts actions.
* See Struts configuration files in web application's Configuration Files node.
* Use multiple Struts configuration files.
As for Spring, there is no extra support, but we have a decent XML editor, which was improved for 5.0. A good XML editor is important for Spring.