bugGNUstep - Bugs: bug #18035, Friendlier handling of re-loading...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #18035: Friendlier handling of re-loading of classes please

Submitted by:  Richard Frith-Macdonald <CaS>
Submitted on:  Tue 17 Oct 2006 06:05:13 AM UTC  
 
Category: GormSeverity: 3 - Normal
Item Group: Change RequestStatus: Fixed
Privacy: PublicAssigned to: Gregory John Casamento <gcasa>
Open/Closed: Closed

Tue 19 Feb 2008 11:34:37 PM UTC, comment #3:

Verified that this is fixed. After thinking a bit about the "super friendly" option, it would be confusing since I would have to display broken connections and give some indication that they are broken in the inspector. GJC

Gregory John Casamento <gcasa>
Project AdministratorIn charge of this item.
Fri 20 Oct 2006 03:18:04 AM UTC, comment #2:

This has been implemented, except for the "Super-friendly" part, which I'll leave for later as a "nice to have". :)

It will now warn you that it "may" break connections. The warning

Please test and let me know if you find any issues.

GJC

Gregory John Casamento <gcasa>
Project AdministratorIn charge of this item.
Wed 18 Oct 2006 10:32:39 PM UTC, comment #1:

This is a frequent request. I'm working on implementation.

Gregory John Casamento <gcasa>
Project AdministratorIn charge of this item.
Tue 17 Oct 2006 06:05:13 AM UTC, original submission:

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.

Richard Frith-Macdonald <CaS>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by gcasa (Posted a comment)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 19 Feb 2008 11:34:37 PM UTCgcasaOpen/ClosedIn Test=>Closed
    Fri 20 Oct 2006 03:18:04 AM UTCgcasaStatusIn Progress=>Fixed
      Open/ClosedOpen=>In Test
    Wed 18 Oct 2006 10:32:39 PM UTCgcasaStatusNone=>In Progress
      Assigned toNone=>gcasa

    Back to the top


    Powered by Savane 3.1-cleanup1