Re: decustmomising

On Wed, 30 Jul 2008 18:19:31 -0700, Daniel Pitts
<newsgroup.spamfilter@xxxxxxxxxxxxxxxxxxx> wrote, quoted or indirectly
quoted someone who said :


Basically, what you should ask yourself is,
"Am I applying a process in a mechanical way?"
"Are all of my decisions non subjective, or are those decisions simple
enough to present a dialog to the tool user?"

There are two pieces to the work, the decision, then the
implementation of the decision.

for example in IntelliJ when you move a method, it shows you a list of
associated variables you might also like to move, with the ones its
thinks most probable already ticks. All you have to is fine tune the
choice thin click Ok. it handle the mechanics of the move.

I would imagine I would show you a list of all literals used in a
program. You tick them off as either
1. leave alone
2. convert to named constant.
3. select some of the instances for conversion to a named constant.
4. convert to a pre-existing named constant possibly in some other
class. I often centralise a constants in class, e.g. configuration
constants. As it is, IntelliJ extract does each class independently.

Again you might decide which constants count as "configuration
constants". These would be pulled together in one class. You would
fill in a dialog of extra info about each one, e.g. lowest legal,
highest legal, default, prompt, label, and it would compose a little
GUI to let the user build the config file. You might then would tweak
the layout, with all the rest mechanically generated. you probably
could invent some layout, where you visually manually position the
elements, dragging tem around on a crude grid, and the positions
becomes part of the little database used to generate the code.

--

Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com
.