drneau.com

[drneau]

I've been putting a lot of work into redesigning the way consoles are managed in the app.

In v2, consoles worked okay. However, a good Object-Oriented person would look at the way I did and realize a few things:
- Jeff, you've really overloaded the purpose of the "Console" class. It extends JComponent, manages the layout of the components, knows how to paint itself, manages its own attributes and rules, knows how to persist itself and parse XML. That's really dumb.
- Jeff, you've done the same for each of the components in the console.

A good Java guy would also look at it and say:
- Dude, you can't display the same component in two places at once. Obviously, you realize that, which is why you are cloning your consoles a lot...especially over the network...and that leads to potential memory issues...which in turn can lead to performance issues.
- Dude, each and every one of the components could be a lot smart about the way they are painting themselves on the screen. You're recalculating things needlessly each and every time you paint!


I realized all that myself, which is why I've been working on fixing it. The end result will be a smaller memory footprint and a much smarter console when it comes to painting (which will improve any scrolling substantially).


For those who care, I've split the v2 "ConsoleLayout" class into:
- ConsoleDef: The definition of the console. Can be saved and cloned cheaply.
- Console: Knows how to paint what is in the ConsoleDef.

A "ConsoleLayout" used to consist of "ConsoleComponents". Those have now been split apart:
- ConsoleComponentDef: The definition of an individual console component.
- ConsoleComponent: Knows how to paint what is in the ConsoleDef.

In doing this, I've discovered a LOT of places for optimization that should make v3 much more robust and responsive.
_________________
--
Dr. Neau (not a real doctor)
http://drneau.com
http://home.comcast.net/~jneau

[Dix]

Well..... I care.... and I like the sound of all that.

I come at this more from a hardware than software standpoint... but I have noticed that TM was rather resource hoggish.

Sounds like v3 will be a lot more efficient & streamlined.... hence faster and easier on the resources..... always a good thing
_________________
- Dix

[MaxPower]

What Doc Said:

[ledge]

Doc:

I care too! I've been using your app for a while now and it has impressed a great many of my friends and colleagues. I'm not a Java guy or a programming dude by any stretch, but I now good work when I see it. Many others are using the TD app and have many issues with it, yours is not the case.

Keep up the good work man! I can't wait for you to release ver 3, because I know that you poured your heart and soul into it.

Ledge

[rumackay]

^^^ Ditto!!!







...Are we there yet...
_________________
-- Kingaroy High Rollers Poker Tour --

[rastapete]

Doc,

Why do Object-Oriented guys call you "Jeff", but Java guys call you "Dude"?

[i8dbear]

the "Jeff" guys are just objectifying him.

.n