[bug #24751] Gorm should be able to update existing class files

[Sebastian Reitenbach]

Follow-up Comment #3, bug #24751 (project gnustep):

Hi,

thanks for your replies to this request.

I don't know how the actual code generator works, but I think it is just
creating the class files, adding the outlets and actions to a template, and
writes them to the place specified by the user.

I thought it could work way like this:
gorm tracks for which classes and where it created initial class files. When
later e.g. adding outlets or actions to such a class,
 where the class files meanwhile were potentially edited by the user, there
could be an update class files menu entry.
When choosing to update the class files, gorm would have to open the existing
files, scan it for the existence of each method or variable declaration, if
found, don't touch it, otherwise add it.
Maybe in the end open a window, informing the user, what was done.
Gorm just needed to open the .h file, and e.g. scan for the name of the
method or variable. If found, it can assume that it was there from the initial
creation of the class files via gorm, and go on with the next method or
variable. If it cannot find it, it will be added. 
Renaming to rename or delete a method, gorm needs to track these actions
between creation and subsequent updates.
of course, before any update of existing files, gorm should create a backup
of the existing ones ;)

but I guess, you are probably right and that's not just easily implemented
implemented ;)

However, the other way around you suggested, let PC notify Gorm about added
outlets and actions, also sounds pretty attractive.



    _______________________________________________________

Reply to this item at:

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

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