[bug #18035] Friendlier handling of re-loading of classes please

[Richard Frith-Macdonald]

URL:
  <http://savannah.gnu.org/bugs/?18035>

                 Summary: Friendlier handling of re-loading of classes please
                 Project: GNUstep
            Submitted by: CaS
            Submitted on: Tuesday 10/17/2006 at 06:05
                Category: Gorm
                Severity: 3 - Normal
              Item Group: Change Request
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open

    _______________________________________________________

Details:

Now that the gui intrerface for the classes is really nice to use, I find I
have another usability issue.  This is because I never know exactly what I'm
going to be doing right from the start, so my classes need to go through
several iterations during development, with testing taking place throughout,
and usually adding new actions and outlets at various stages.

At present, if you change a class and need to re-load it in Gorm to make new
connections for the new actions/outlets, Gorm warns you that all existing
connections will be broken ... and breaks them, so you have to re-make all
connections for instances of the class.

What would be really nice would be for Gorm to keep existing connections
intact where possible, retain the knowledge that the loaded class is NSOwner
and NSFirst (where appropriate), and perhaps also raise a panel listing any
connections that it actually had to break (ie where an outlet/action has been
removed or renamed).

Super-friendly would be if clicking on one of the broken connections in the
listing was to select the two objects concerned in the connections inspector
so that they could be easily reconnected.






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?18035>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/