NetBeans not ready for Rails 2.0

[bruparel]

All,
Just wanted to run my observations by you.
I have tried over the week-end to make NetBeans 6.0, 6.0.1, and 6.1 (dev 200801201200) work with Rails 2.0 and have reached the conclusion that it is too painful and clumsy.  NetBeans 6.0 and 6.0.1 are simply not Rails 2.0 aware, understandably so.  Whereas the 6.1 build mentioned above is too unpredictable.  For example, it spends an enormous amount of time trying to index the Depot application that I have already closed.  Even if it is open, NetBeans 6.0 does it at the speed of light compared to the dev build of 6.1
For time being, until 6.1 stabilizes a bit, I will stay away from trying to work with NetBeans and Rails 2.0.  I must point out that the Tutorial Diva article about working with NetBeans 6.0 and Rails 2.0.2 to create a blog did work, but feels quite clumsy though.  The command line feels better.  NetBeans 6.0 with Rails 1.2.3 which I have with InstantRails 1.7 works quite well and feel good too.
I would like to see how others "feel" about this?  Mind you, it is not a cut-and-dry discussion and different people have different opinions.  The reason for this post is not to start something, but more like to get a response from people who know something I don't and can tell me that I am wrong and here is how it will work well.
Regards,
Bharat

[bartee]

I am new to Rails so I am not fast at anything. So I don't know when NB is slowing me down or my lack of experience.

I am on Windows XP so textmate is not an option and e-editor is really weak in my opion.

So I have been trying to work with NB.

I too have big problems with indexing.  I had not considered this to be a  Rails 2.0 vs Rails 1.2.3 problem.  It could be and something the NB teams should look at. 

One thing to observe is the two guys doing the NB work are NOT Ruby or Rails guys.   So they do not think like highly productive RoR developers.  They are ( I'm Sure ) excellent Java guys.  I am sure they are learning Ruby and Rails as they go, but when I watch some guys on Textmate it is truly amazing the speed at which they can crank out code.   I think NB will have to approach the speed of Textmate to become widely accepted.

One thing I cannot get is when look ahead works and when the textmate bundle type of shortcuts works.  I would really like to get a list of the textmate bundle type of short cuts so I can see them and learn where to use them. 

I have talked with Gregg Spoar and I KNOW he is committed to this project. 

Thanks for starting this and I hope that we can find a path to making NB work. I think it is a GREAT IDE with the integrated debugging and features that will draw more developers into the RoR movement.

...bartee...

On Jan 22, 2008 8:40 AM, bruparel <ruparel@...> wrote:

All,
Just wanted to run my observations by you.
I have tried over the week-end to make NetBeans 6.0, 6.0.1, and 6.1 (dev
200801201200) work with Rails 2.0 and have reached the conclusion that it is
too painful and clumsy.  NetBeans 6.0 and 6.0.1 are simply not Rails 2.0
aware, understandably so.  Whereas the 6.1 build mentioned above is too
unpredictable.  For example, it spends an enormous amount of time trying to
index the Depot application that I have already closed.  Even if it is open,
NetBeans 6.0 does it at the speed of light compared to the dev build of 6.1
For time being, until 6.1 stabilizes a bit, I will stay away from trying to
work with NetBeans and Rails 2.0.  I must point out that the Tutorial Diva
article about working with NetBeans 6.0 and Rails 2.0.2 to create a blog did
work, but feels quite clumsy though.  The command line feels better.
NetBeans 6.0 with Rails 1.2.3 which I have with InstantRails 1.7 works quite
well and feel good too.
I would like to see how others "feel" about this?  Mind you, it is not a
cut-and-dry discussion and different people have different opinions.  The
reason for this post is not to start something, but more like to get a
response from people who know something I don't and can tell me that I am
wrong and here is how it will work well.
Regards,
Bharat

--
View this message in context: http://www.nabble.com/NetBeans-not-ready-for-Rails-2.0-tp15018872s27022p15018872.html
Sent from the NetBeans Ruby - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[bruparel]

Hello Bartee,
You wrote below:

One thing to observe is the two guys doing the NB work are NOT Ruby or Rails
guys.   So they do not think like highly productive RoR developers.  They
are ( I'm Sure ) excellent Java guys.  I am sure they are learning Ruby and
Rails as they go, but when I watch some guys on Textmate it is truly amazing
the speed at which they can crank out code.   I think NB will have to
approach the speed of Textmate to become widely accepted.

Actucally, I have to respectfully disagree with you.  I am simply amazed at how good Tor is.  I am beginning to understand the programming lore that a really good developer is better than 20 average developers.  Tor is simply one of the best developers judging from his work.  I have used NetBeans since 6.0 was in bea past Spring and have seen it grow by leaps and bounds.  As a long time Eclipse user, I have not seen anything that even comes close to NetBeans Ruby combination.  My interest was to provide general feedback and sound out the user community to find out if I was missing something in Rails 2.0 and NetBeans combination?  After all, I am primarily interested in NetBeans because of Rails not Ruby.

I do not believe that it is important to compare an editor and IDE speed-wise.  I use VIM/GVIM/CREAM combination which is quite fast.  An IDE is a different animal.  It has to index everything.  But I think that something is broken in the NetBeans 6.1 dev build which the developers may not be aware of (or always a possiblity that I am doing something wrong).

Regards,

Bharat

[Martin Krauskopf]

bruparel wrote:
> All,
> Just wanted to run my observations by you.
> I have tried over the week-end to make NetBeans 6.0, 6.0.1, and 6.1 (dev
> 200801201200) work with Rails 2.0 and have reached the conclusion that it is
> too painful and clumsy.  NetBeans 6.0 and 6.0.1 are simply not Rails 2.0
> aware, understandably so.  Whereas the 6.1 build mentioned above is too
> unpredictable.  For example, it spends an enormous amount of time trying to
> index the Depot application
[...]

Hi Bharat,

I do not know this code (in NetBeans) well so I can't comment, but I
heard this from more people already. Could you file an issue into
Issuezilla, so it is tracked and not forgotten. Thanks.
Personally I do not feel it that much. But it likely depends on the
configuration, like number of gems installed, etc.

        m.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[bruparel]

Hello Martin,
You wrote below:

Hi Bharat,

I do not know this code (in NetBeans) well so I can't comment, but I
heard this from more people already. Could you file an issue into
Issuezilla, so it is tracked and not forgotten. Thanks.
Personally I do not feel it that much. But it likely depends on the
configuration, like number of gems installed, etc.

        m.


I will be happy to file an issue, I just don't know how and where?
Bharat

[Martin Krauskopf]

bruparel wrote:

> Hello Martin,
> You wrote below:
>
> Hi Bharat,
>
> I do not know this code (in NetBeans) well so I can't comment, but I
> heard this from more people already. Could you file an issue into
> Issuezilla, so it is tracked and not forgotten. Thanks.
> Personally I do not feel it that much. But it likely depends on the
> configuration, like number of gems installed, etc.
>
> m.
>
> I will be happy to file an issue, I just don't know how and where?

Just go to:

http://www.netbeans.org/community/index.html

register, and once you are logged in, you can file an issue (into ruby
category).

You should be guided on the site after you logged in. Or just go
directly to this link (once you are logged in):

http://www.netbeans.org/issues/enter_bug.cgi?component=ruby

Regards,
        m.

PS: more info here: http://wiki.netbeans.org/wiki/view/RubyFeedback

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Gregg Sporar]

>I would really like to get a list of the textmate bundle type of short cuts so I can see them and learn where to use them. 

Hi Bartee -

Is this what you are looking for:

  http://wiki.netbeans.org/wiki/view/RubyCodeTemplates

HTH,
Gregg Sporar


Bartee Lamar wrote:

I am new to Rails so I am not fast at anything. So I don't know when NB is slowing me down or my lack of experience.

I am on Windows XP so textmate is not an option and e-editor is really weak in my opion.

So I have been trying to work with NB.

I too have big problems with indexing.  I had not considered this to be a  Rails 2.0 vs Rails 1.2.3 problem.  It could be and something the NB teams should look at. 

One thing to observe is the two guys doing the NB work are NOT Ruby or Rails guys.   So they do not think like highly productive RoR developers.  They are ( I'm Sure ) excellent Java guys.  I am sure they are learning Ruby and Rails as they go, but when I watch some guys on Textmate it is truly amazing the speed at which they can crank out code.   I think NB will have to approach the speed of Textmate to become widely accepted.

One thing I cannot get is when look ahead works and when the textmate bundle type of shortcuts works.  I would really like to get a list of the textmate bundle type of short cuts so I can see them and learn where to use them. 

I have talked with Gregg Spoar and I KNOW he is committed to this project. 

Thanks for starting this and I hope that we can find a path to making NB work. I think it is a GREAT IDE with the integrated debugging and features that will draw more developers into the RoR movement.

...bartee...

On Jan 22, 2008 8:40 AM, bruparel <ruparel@...> wrote:

All,
Just wanted to run my observations by you.
I have tried over the week-end to make NetBeans 6.0, 6.0.1, and 6.1 (dev
200801201200) work with Rails 2.0 and have reached the conclusion that it is
too painful and clumsy.  NetBeans 6.0 and 6.0.1 are simply not Rails 2.0
aware, understandably so.  Whereas the 6.1 build mentioned above is too
unpredictable.  For example, it spends an enormous amount of time trying to
index the Depot application that I have already closed.  Even if it is open,
NetBeans 6.0 does it at the speed of light compared to the dev build of 6.1
For time being, until 6.1 stabilizes a bit, I will stay away from trying to
work with NetBeans and Rails 2.0.  I must point out that the Tutorial Diva
article about working with NetBeans 6.0 and Rails 2.0.2 to create a blog did
work, but feels quite clumsy though.  The command line feels better.
NetBeans 6.0 with Rails 1.2.3 which I have with InstantRails 1.7 works quite
well and feel good too.
I would like to see how others "feel" about this?  Mind you, it is not a
cut-and-dry discussion and different people have different opinions.  The
reason for this post is not to start something, but more like to get a
response from people who know something I don't and can tell me that I am
wrong and here is how it will work well.
Regards,
Bharat

--
View this message in context: http://www.nabble.com/NetBeans-not-ready-for-Rails-2.0-tp15018872s27022p15018872.html
Sent from the NetBeans Ruby - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Tor Norbye]

On Jan 22, 2008, at 4:10 PM, bruparel wrote:

> Actucally, I have to respectfully disagree with you.  I am simply  
> amazed at
> how good Tor is.  I am beginning to understand the programming lore  
> that a
> really good developer is better than 20 average developers.  Tor is  
> simply
> one of the best developers judging from his work.  I have used  
> NetBeans
> since 6.0 was in bea past Spring and have seen it grow by leaps and  
> bounds.

Thank you very much - I'm honored and flattered. But I'm really  
getting too much credit. The NetBeans Ruby debugger is entirely  
Martin's work, as well as the Ruby Platforms work and various other  
fixes. Erno just joined the dev team and is cruising ahead.  And of  
course, all the editing support is building on top of great new  
NetBeans 6.0 infrastructure (lexer, retouche, etc) written by lots of  
great engineers. Just standing on the shoulders of giants etc. etc.

This is starting to sound like an awards acceptance speech... so let  
me also thank the Academy, as well as our users whose involvement  
inspires harder work and whose bug reports help track down our  
mistakes, our QE engineers who keep us on our toes, our doc writers  
who make our work accessible, .... Oh the music is fading in,  I'm out  
of time

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[bartee]

Gregg,

Thanks, that's exactly what I was hunting for.  I spent a while trying understand what is available in the wiki.

This has been a great thread.  The commitment of Sun to the Rails/Ruby NB is amazing. 

Now all I have to do is get time away from my real job to put this into practice.

thanks to the whole team... looking forward to more stuff...

...bartee...

On Jan 22, 2008 2:24 PM, Gregg Sporar <Gregg.Sporar@...> wrote:

>I would really like to get a list of the textmate bundle type of short cuts so I can see them and learn where to use them. 

Hi Bartee -

Is this what you are looking for:

  http://wiki.netbeans.org/wiki/view/RubyCodeTemplates

HTH,
Gregg Sporar

Bartee Lamar wrote:

I am new to Rails so I am not fast at anything. So I don't know when NB is slowing me down or my lack of experience.

I am on Windows XP so textmate is not an option and e-editor is really weak in my opion.

So I have been trying to work with NB.

I too have big problems with indexing.  I had not considered this to be a  Rails 2.0 vs Rails 1.2.3 problem.  It could be and something the NB teams should look at. 

One thing to observe is the two guys doing the NB work are NOT Ruby or Rails guys.   So they do not think like highly productive RoR developers.  They are ( I'm Sure ) excellent Java guys.  I am sure they are learning Ruby and Rails as they go, but when I watch some guys on Textmate it is truly amazing the speed at which they can crank out code.   I think NB will have to approach the speed of Textmate to become widely accepted.

One thing I cannot get is when look ahead works and when the textmate bundle type of shortcuts works.  I would really like to get a list of the textmate bundle type of short cuts so I can see them and learn where to use them. 

I have talked with Gregg Spoar and I KNOW he is committed to this project. 

Thanks for starting this and I hope that we can find a path to making NB work. I think it is a GREAT IDE with the integrated debugging and features that will draw more developers into the RoR movement.

...bartee...

On Jan 22, 2008 8:40 AM, bruparel <ruparel@...> wrote:

All,
Just wanted to run my observations by you.
I have tried over the week-end to make NetBeans 6.0, 6.0.1, and 6.1 (dev
200801201200) work with Rails 2.0 and have reached the conclusion that it is
too painful and clumsy.  NetBeans 6.0 and 6.0.1 are simply not Rails 2.0
aware, understandably so.  Whereas the 6.1 build mentioned above is too
unpredictable.  For example, it spends an enormous amount of time trying to
index the Depot application that I have already closed.  Even if it is open,
NetBeans 6.0 does it at the speed of light compared to the dev build of 6.1
For time being, until 6.1 stabilizes a bit, I will stay away from trying to
work with NetBeans and Rails 2.0.  I must point out that the Tutorial Diva
article about working with NetBeans 6.0 and Rails 2.0.2 to create a blog did
work, but feels quite clumsy though.  The command line feels better.
NetBeans 6.0 with Rails 1.2.3 which I have with InstantRails 1.7 works quite
well and feel good too.
I would like to see how others "feel" about this?  Mind you, it is not a
cut-and-dry discussion and different people have different opinions.  The
reason for this post is not to start something, but more like to get a
response from people who know something I don't and can tell me that I am
wrong and here is how it will work well.
Regards,
Bharat

--
View this message in context: http://www.nabble.com/NetBeans-not-ready-for-Rails-2.0-tp15018872s27022p15018872.html
Sent from the NetBeans Ruby - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[bruparel]

Tor,
You wrote:
"Thank you very much - I'm honored and flattered."
Now that you are honored and flattered, you did not answer my original question:

Is NetBeans ready for Rails 2.0.x?  6.0 or 6.1?
What is your informed opinion?

Regards,
Bharat

[Martin Krauskopf]

bruparel wrote:
> Tor,
> You wrote:
> "Thank you very much - I'm honored and flattered."
> Now that you are honored and flattered, you did not answer my original
> question:
>
> Is NetBeans ready for Rails 2.0.x?  6.0 or 6.1?
> What is your informed opinion?

I'm rather on the lower levels (platform, gems infrastructure, debugger,
...), but from what I know, NetBeans (6.1, dev build more) should be
ready for Rails 2.0.x. If it does not seems to you please come with any
ideas you have and the best is to file RFEs into Issuezilla. It might
happen that the responsible developer is really busy in the meantime you
writing on ML and forget later to respond (usually not, bot
sometime...). This can't happen with Issuezilla RFEs. So it is always
the 'sure' way.
You know, we are getting different feedback. "NetBeans are great for
Rails development", but sometime "NetBeans are clumsy...". So any
feedback, ideas are welcomed.

Wrt. to "indexing is slow" problem. What exactly do you mean.

1) It should happen only first time (per IDE with userdir). So next time
you start the IDE or create another project or do whatever it should not
trigger the indexing again. It is really *first* time ever, until you
delete the userdir. So if it is e.g. 1-5 minutes, it should be still OK.
I will work weeks then until you delete userdir again.

2) What do you mean "enormous amount of time". If it is 15 minutes, it's
really not good and should be better (filing a bug). Or if it happens
every time you start the IDE or create a new sample/project, it's also bug.

Regards,
        m.

PS: I know you filed, probably wait a little bit, until Tor is 'back'
(see other thread)
http://www.netbeans.org/issues/show_bug.cgi?id=125790

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[James Moore]

On Jan 25, 2008 3:32 PM, bruparel <ruparel@...> wrote:
> Is NetBeans ready for Rails 2.0.x?  6.0 or 6.1?
> What is your informed opinion?

I'm using 6.1 (a daily build - right now I'm running whatever was
current at 6am on the 25th) with 2.0.1 and 2.0.2, and MRI (not much
JRuby yet).  It's a fine combination.

--
James Moore | james@...
blog.restphone.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[James Moore]

On Jan 26, 2008 1:50 AM, Martin Krauskopf <Martin.Krauskopf@...> wrote:
> Wrt. to "indexing is slow" problem. What exactly do you mean.
>
> 1) It should happen only first time (per IDE with userdir). So next time
> you start the IDE or create another project or do whatever it should not
> trigger the indexing again. It is really *first* time ever, until you
> delete the userdir. So if it is e.g. 1-5 minutes, it should be still OK.
> I will work weeks then until you delete userdir again.

That's interesting - I've never seen the behavior that you're
describing, Martin.  NetBeans doesn't have to reindex all of Ruby, but
definitely it says that it's reindexing my own projects on every
NetBeans startup.  Using MRI, not JRuby, if that matters.  On the
project I'm working on today, it's only taking about 10 seconds to
index (but it's a tiny project - a dozen or so models/controllers).

Tried it on :

Product Version: NetBeans Ruby IDE 20080125120439
Java: 1.6.0_03; Java HotSpot(TM) Server VM 1.6.0_03-b05
System: Linux version 2.6.18-8.1.15.el5xen running on i386; UTF-8;
en_US (nbrubyide)
Userdir: /home/james/.nbrubyide/dev

--
James Moore | james@...
Interested in hooking up phone calls to your Ruby on Rails site?
Send me mail about the RESTPhone beta.
blog.restphone.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Erno Mononen]

Martin Krauskopf wrote:

> bruparel wrote:
>> Tor,
>> You wrote:
>> "Thank you very much - I'm honored and flattered."
>> Now that you are honored and flattered, you did not answer my original
>> question:
>>
>> Is NetBeans ready for Rails 2.0.x?  6.0 or 6.1?
>> What is your informed opinion?
>
> I'm rather on the lower levels (platform, gems infrastructure,
> debugger, ...), but from what I know, NetBeans (6.1, dev build more)
> should be ready for Rails 2.0.x. If it does not seems to you please
> come with any ideas you have and the best is to file RFEs into
> Issuezilla. It might happen that the responsible developer is really
> busy in the meantime you writing on ML and forget later to respond
> (usually not, bot sometime...). This can't happen with Issuezilla
> RFEs. So it is always the 'sure' way.

I can only second Martin here - I'm not aware of any major issues with
Rails 2.0.x and NB  6.1 dev. So if anybody has encountered any issues in
that area, please let us know; we'd certainly like to make sure that 6.1
final will work smoothly with Rails 2.

Thanks,
Erno

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Martin Krauskopf]

James Moore wrote:

> On Jan 26, 2008 1:50 AM, Martin Krauskopf <Martin.Krauskopf@...> wrote:
>> Wrt. to "indexing is slow" problem. What exactly do you mean.
>>
>> 1) It should happen only first time (per IDE with userdir). So next time
>> you start the IDE or create another project or do whatever it should not
>> trigger the indexing again. It is really *first* time ever, until you
>> delete the userdir. So if it is e.g. 1-5 minutes, it should be still OK.
>> I will work weeks then until you delete userdir again.
>
> That's interesting - I've never seen the behavior that you're
> describing, Martin.  NetBeans doesn't have to reindex all of Ruby, but
> definitely it says that it's reindexing my own projects on every
> NetBeans startup.  Using MRI, not JRuby, if that matters.  On the
> project I'm working on today, it's only taking about 10 seconds to
> index (but it's a tiny project - a dozen or so models/controllers).

Hi James,

I would let Tor to reply the definitive answer. I suppose 10s each time
is OK. What I mainly wanted to say that the *huge* indexing should
happen just once, not more - otherwise it is a bug.
How it is with "smaller" indexing actions, I do not know.

        m.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[bruparel]

OK.  I downloaded the latest 6.1 build 200801260000 to try to reproduce the index time.  I intalled it without any problems.  Installed ruby-debug .93 gem (windows platform).  When I try to start it, I get the following stacktrace (it starts though):

java.lang.AssertionError
        at org.netbeans.modules.mercurial.util.HgCommand.execEnv(HgCommand.java:2178)
        at org.netbeans.modules.mercurial.util.HgCommand.execForVersionCheck(HgCommand.java:2294)
        at org.netbeans.modules.mercurial.util.HgCommand.getHgVersion(HgCommand.java:365)
        at org.netbeans.modules.mercurial.Mercurial.checkVersion(Mercurial.java:139)
        at org.netbeans.modules.mercurial.Mercurial.init(Mercurial.java:118)
        at org.netbeans.modules.mercurial.Mercurial.getInstance(Mercurial.java:94)
        at org.netbeans.modules.mercurial.MercurialVCS.<init>(MercurialVCS.java:63)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at org.openide.util.lookup.MetaInfServicesLookup$P.getInstance(MetaInfServicesLookup.java:428)
        at org.openide.util.lookup.AbstractLookup$R.allInstances(AbstractLookup.java:932)
        at org.openide.util.lookup.ProxyLookup$R.computeResult(ProxyLookup.java:521)
        at org.openide.util.lookup.ProxyLookup$R.allInstances(ProxyLookup.java:462)
        at org.netbeans.modules.versioning.VersioningManager.refreshVersioningSystems(VersioningManager.java:150)
        at org.netbeans.modules.versioning.VersioningManager.init(VersioningManager.java:140)
        at org.netbeans.modules.versioning.VersioningManager.getInstance(VersioningManager.java:94)
        at org.netbeans.modules.versioning.VersioningAnnotationProvider.getOwner(VersioningAnnotationProvider.java:79)
        at org.netbeans.modules.versioning.VersioningAnnotationProvider.annotateNameHtml(VersioningAnnotationProvider.java:98)
        at org.netbeans.modules.masterfs.filebasedfs.FileBasedFileSystem$StatusImpl.annotateNameHtml(FileBasedFileSystem.java:384)
        at org.netbeans.modules.project.ui.ProjectsRootNode$BadgingNode.getHtmlDisplayName(ProjectsRootNode.java:494)
        at org.openide.explorer.view.VisualizerNode.getHtmlDisplayName(VisualizerNode.java:553)
        at org.openide.explorer.view.NodeRenderer.getTreeCellRendererComponent(NodeRenderer.java:125)
        at javax.swing.plaf.basic.BasicTreeUI$NodeDimensionsHandler.getNodeDimensions(BasicTreeUI.java:2807)
        at javax.swing.tree.AbstractLayoutCache.getNodeDimensions(AbstractLayoutCache.java:475)
        at javax.swing.tree.VariableHeightLayoutCache$TreeStateNode.updatePreferredSize(VariableHeightLayoutCache.java:1342)
        at javax.swing.tree.VariableHeightLayoutCache$TreeStateNode.expand(VariableHeightLayoutCache.java:1469)
        at javax.swing.tree.VariableHeightLayoutCache$TreeStateNode.expand(VariableHeightLayoutCache.java:1270)
        at javax.swing.tree.VariableHeightLayoutCache.rebuild(VariableHeightLayoutCache.java:725)
        at javax.swing.tree.VariableHeightLayoutCache.treeStructureChanged(VariableHeightLayoutCache.java:626)
        at javax.swing.plaf.basic.BasicTreeUI$Handler.treeStructureChanged(BasicTreeUI.java:3931)
        at javax.swing.tree.DefaultTreeModel.fireTreeStructureChanged(DefaultTreeModel.java:561)
        at javax.swing.tree.DefaultTreeModel.nodeStructureChanged(DefaultTreeModel.java:347)
        at javax.swing.tree.DefaultTreeModel.setRoot(DefaultTreeModel.java:117)
        at org.openide.explorer.view.NodeTreeModel$1.run(NodeTreeModel.java:106)
        at org.openide.util.Mutex.doEvent(Mutex.java:1335)
        at org.openide.util.Mutex.readAccess(Mutex.java:345)
        at org.openide.explorer.view.NodeTreeModel.setNode(NodeTreeModel.java:92)
        at org.openide.explorer.view.TreeView.synchronizeRootContext(TreeView.java:764)
        at org.openide.explorer.view.TreeView.lookupExplorerManager(TreeView.java:606)
        at org.openide.explorer.view.TreeView.addNotify(TreeView.java:586)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at org.netbeans.swing.tabcontrol.TabbedContainer.addNotify(TabbedContainer.java:920)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addNotify(Container.java:2592)
        at javax.swing.JComponent.addNotify(JComponent.java:4665)
        at java.awt.Container.addImpl(Container.java:1062)
        at java.awt.Container.add(Container.java:903)
        at org.netbeans.core.windows.view.ui.MainWindow.setDesktop(MainWindow.java:500)
        at org.netbeans.core.windows.view.ViewHierarchy.setDesktop(ViewHierarchy.java:785)
        at org.netbeans.core.windows.view.ViewHierarchy.setMainWindowDesktop(ViewHierarchy.java:775)
        at org.netbeans.core.windows.view.ViewHierarchy.updateDesktop(ViewHierarchy.java:668)
        at org.netbeans.core.windows.view.DefaultView.showWindowSystem(DefaultView.java:556)
        at org.netbeans.core.windows.view.DefaultView.windowSystemVisibilityChanged(DefaultView.java:498)
        at org.netbeans.core.windows.view.DefaultView.changeGUI(DefaultView.java:180)
        at org.netbeans.core.windows.ViewRequestor.dispatchRequest(ViewRequestor.java:269)
        at org.netbeans.core.windows.ViewRequestor.processVisibilityRequest(ViewRequestor.java:258)
        at org.netbeans.core.windows.ViewRequestor.postVisibilityRequest(ViewRequestor.java:195)
        at org.netbeans.core.windows.ViewRequestor.scheduleRequest(ViewRequestor.java:117)
        at org.netbeans.core.windows.Central.setVisible(Central.java:118)
        at org.netbeans.core.windows.WindowManagerImpl.setVisible(WindowManagerImpl.java:758)
        at org.netbeans.core.windows.WindowSystemImpl.show(WindowSystemImpl.java:87)
[catch] at org.netbeans.core.NonGui$3.run(NonGui.java:210)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
        at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
    &n