Hello all,
I have been doing some repackaging to aid some unexpected reuse. I
would have wagered a beer or two that the idea would go down in flames
(but didn't see what else to do). So far it looks good, though I
haven't yet checked for cycles.
First, something that helped was (of course) to create the new package,
and then to select both it and the source package in the SB. Then I was
able to easily move classes to the new package w/o "disturbing the view".
I vaguely recall earlier discussions of this, but I noted that dragging
classes to the new package (in the SB's package list) did not take
subclasses. I expected it to. I also must confess that this was not
always desireable, so the behavior might well be correct. Right drag
and drop displays a menu with Copy and move options, so that might be
better with Repackage class and Repackage with subclasses???
I tend to use the SB mostly for reading vs. changing code, mostly
because I have to resize it quite a bit. My browser filter goodie also
offers higher granularity, so it works better for me in many situations.
One thing that I think would make the SB easier to resize would be to
put the class list/hierarchy in a container view with the filters and
method list. That way, one could quickly slide the package list largely
out of the way once a selection is made, and the remaining panes would
size more naturally; as it is now, only the class list/hierarchy grows.
It sounds like a simple change, but I became concerned when I noted that
the class list/hierarchy is part of class selector and not the "rest of
the browser". Is there a simple workaround?
Have a good one,
Bill
--
Wilhelm K. Schwab, Ph.D.
[hidden email]
Locked
