Hi Axel,
I'm sorry I hadn't noticed your messages yet...
> Nevermind, I found out about ib_external_class_defs.yml the second
> after
> I pressed the send button for my initial message. Although it would
> be
> nice if rucola would discover such subclasses automatically and add
> them
> to the NIB file without an additional yaml file...
I totally agree with you.
There are 2 ways of fixing this, neither is easy :)
- Add every ruby source file that's created to the xcodeproject and
keep xcode open during development so IB can interact with it and
update your source files.
Leaving xcode open at all times is not such a big problem, but
adding files externall to a xocdeproject isn't that easy. However not
so long ago I enhanced the rucola lib that opens/modifies
xcodeprojects so it might not be that hard anymore. I would have to
look into that again.
But also if I recall correctly, the same problem exists with the way
xcode/ib update the definitions. Because they also use rb_nibtool.rb
which doesn't follow require statements and thus only loads a
definition that's found in one file and doesn't go out looking for
your custom NSView superclass.
- Do it all through nibtool. At the moment this isn't possible, as it
doesn't allow you to add classes. But I have filed a report for this
on Apple's Radar and I have heard that the request might be fulfilled.
Unfortunately Apple doesn't let you know until they're done...
I'll give it some more thought.
As always any input on the subject is appreciated.
Cheers,
Eloy