Win a copy of Terraform in Action this week in the Cloud forum!

Greg Moose

Greenhorn
+ Follow
since Jul 26, 2006
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Greg Moose

If it is that simple and you are just starting out, use the free NetBean IDE and take advantage of Matisse. JGoodie's Form Layout Manager has always gotten good press.
15 years ago
Thanks for the reply. Just curious why it was made so difficult to alter current configurations? The YourKit folks had the inside scoop, so they were able to figure it out, so it's not impossible, I guess. It just seems to me that making folks completely redo their Run Configs to take advantage of a new runtime addition doesn't allow for an easy adoption of a new plugin of that type. Perhaps you make it hard on purpose since it could easily interfere with the very basic debugging aspect of the IDE...
First off, love the IDE and I am amazed and how often IDEA plesantly surprises me. I wanted to participate and was kicked into action with the announcement of your Plugin competition back in Sept/Oct. I had the killer tool. Got the basic tool created soon enough and then went to integrate it into IDEA. On aspect of the integration sought to add an additional tab to the Run/Config dialog much like CodeCoverage or YourKit adds behavior to existing configurations.

That turned out to be quite impossible. As disappointing as that was since it seemed to me a natural enhancement path to augment current configs, the real pisser was how long I did this trying to come to that conclusion. Just documenting the API's and the trivial examples here seemed to fall short quickly.

Will your book assist the Plugin developer beyond what is presently available on your plugin page?

That would be nice, but I would think that Plugin development is crucial to perpetuating your client-base's enthusiasm and bolstering freely available plugin development information would be important.

Originally posted by Ilja Preuss:

MyDoitClass.super.doit();



Brilliant Ilja! (At least I hope it is a sign of brilliance if someone tells me something that I didn't already know )

This protects the API for leaking out such sillyness. I could have made superdoit() private, but total unnecessary now... My only fear is that I leaked out a way for Singhal or other to call the super on the api..
15 years ago

Originally posted by Clifton Craig:
It seems as though you are not understanding the purpose of method overriding...



Certainly, one would agree that an overriden method should itself, in many cases, call the overriden super before or perhaps after the overriden functionatiy is performed. Let's consider the latter case. I want to call the super after I do my overriding task:



Now consider that domore() needs to be threaded and the super.doit cannot be called until the domore() finishes:



The only way that I know how to do it (refecting on the Class.getSuperclass() does not work) is this ugly bit:
15 years ago