Menu
▾
▴
#6 Make "Exports" Useless
I've been trying to think of uses of having a
separate "exports" section for each class. I can't think of
any benefits.
We should get rid of the "exports" list and make it
automatically generated based upon the things that are in
the class.
(This would also work around a wierd bug I've found that
sometimes, in very strange circumstances, one class's
function can end up in another's export list without me
wanting it there -- this could be almost impossible for first-
time-users of sheets to get around).
Logged In: YES
user_id=532847
The main reason the export sheet is there is to impose an
order. Without that, you can't be sure what order the
methods and variables should be exported to disk.
In the distant past there were "magical" sheets that were
used to determine order (usually turned out to be the sheet
with all of the children), however, this was a bit hokey.
After that the list of exports was automatically generated,
however, there are some nasty cases with default initializers
where order actually matters...
Anyway, we should probably target in on the specific
problems with the current export list. If stuff is getting added
or removed that doesn't belong that is a bug.
Logged In: YES
user_id=338208
That bug (mentioned in both comments) is sorta described in bug
585197.
Actually, an additional thing is that it would be very cool if the
exports, which are automatically generated, would be in the order
they are found in the sheets (this may be very difficult, and be a
long-term issue). Right now, reordering stuff in the main sheets
list doesn't put it in a different order in the file, which will confuse
many novice users who go and try to debug by looking at line
numbers.
Basically, I strongly agree that the oddities of the "Exports" will be
a big bar to novice users. I'd give up pretty quickly if I ran into a
database that exported a DatabaseNode to my
JMainWindowDialog, even though it's quick to fix if you know
what you're doing.