Add an annotation detailing the prior versions count. Specially handled here for the case of a selector no longer in the system, whose prior version is pointed to by the lost-method pointer in the change held on to by the changeset
Obtain a file designation from the user, and file its contents into a new change set whose name is a function of the filename. Show the new set and leave the current changeSet unaltered.
Search for a changeSet by name. Pop up a menu of all changeSets whose name contains the string entered by the user. If only one matches, then the pop-up menu is bypassed
this is a hack!! makes a new change set, called the class name, adds author initials to try to make a unique change set name, files it out and removes it. kfr 16 june 2000
Compile the code in aString. Notify aController of any syntax errors.
Create an error if the category of the selected message is unknown.
Answer false if the compilation fails. Otherwise, if the compilation
created a new method, deselect the current selection. Then answer true.
Add a set of change sorter views to the given top view offset by the given amount. To create a single change sorter, call this once with an offset of 0@0. To create a dual change sorter, call it twice with offsets of 0@0 and 0.5@0.
Add a set of change sorter views to the given top view offset by the given amount. To create a single change sorter, call this once with an offset of 0@0. To create a dual change sorter, call it twice with offsets of 0@0 and 360@0.
Prompt the user for a name, and establish a new change set of
that name (if ok), making it the current changeset. Return nil
of not ok, else return the actual changeset.
File in the code from the stream into a new change set whose
name is derived from aName. Leave the 'current change set'
unchanged. Return the new change set or nil on failure.
Answer whether a change set belongs in the ProjectsInRelease category. You can hand-tweak this to suit your working style. This just covers the space of project names in the 2.9, 3.0, and 3.1a systems
Put up a menu comprising a list of change sets that hold changes for the given class and selector. If the user selects one, open a single change-sorter onto it
Establish a change-set named Aggregate which bears the union of all the changes in all the existing change-sets in the system (other than any pre-existing Aggregate). This can be useful when wishing to discover potential conflicts between a disk-resident change-set and an image. Formerly very useful, now some of its unique contributions have been overtaken by new features
Answer the number representing the threshold of what counts as 'recent' for an update number. This allow you to use the RecentUpdates category in a ChangeSorter to advantage
Change the order of the change sets to something more convenient:
First come the project changesets that come with the release. These are mostly empty.
Next come all numbered updates.
Next come all remaining changesets
In a ChangeSorter, they will appear in the reversed order.