#39 Exports Section Confusing (UI issue)

[Aaron Powers]

This is a UI problem, not a bug.

The separation between "exports" and stuff that's
visible will be very confusing for novice users (and
sometimes for experts). The best way to solve this
problem is to make the exports list automatically
generated from the list of sheets (this is a suggestion
aphid made some time ago). Below are a couple
scenarios that are particularly problematic. Note that
these could be fixed in other ways besides getting rid
of "exports", but those would skirt around the real
confusing problem: most users don't think about
"exports" because they aren't thinking about the
database itself.

Scenario 1:
User right-clicks on a fragment and hits "remove". The
fragment is no longer visible anywhere, but is still in
the exports list. You can get compile errors and other
problems from this error.

Scenario 2:
Sometimes in the past a small bug in sheets has made a
fragment only show up in the exports list. The user
will have no idea where it's coming from

Scenario 3:
User creates a class with tons of methods and
variables, and sorts various methods into sub-sheets to
organize better. They hit "Go to references" on a
method used in multiple functions on that class, but
that are segmented into multiple subsheets. Instead of
opening the references up into a new sheet, the exports
list opens up (since sheets has correctly decided that
that sheet contains all of the fragments).

[Aaron Powers]

Logged In: YES
user_id=338208

Addendum: There are two real bugs here. Scenario 1-2 can be
fixed this way: Making sure fragments that exist nowhere
elne but in exports. Scenario 3 can be fixed by making the
exports sheets never visible to the user. (Also getting rid
of the icon)

Also related to similar generation of file-header-for section.