Gregory Casamento

> In my opinion, this is not an improvement, it is a bug. A very serious bug. I don't know who will fix it, but without a doubt, having said...

> I don't want to discuss, really. > > > > > > I wasn't trying to start an argument. I am working on shadows as you have seen so...

It might... but... Strictly speaking layers are not needed to support shadows. Also layer support is backend specific as it is already implemented in the Opal backend. Opal uses our...

> The best information I could find for this format is here [dkimitsa.github.io/2018/02/13/wl-tech-details-2-robovm](https://dkimitsa.github.io/2018/02/13/wl-tech-details-2-robovm/) Ah, very cool! Thanks!

This is very likely not needed. NIBArchive is a "compiled" format that is created from XIB files defined by Xcode. So, theoretically, we should be able to support this simply...

One thing about this. Defining the border radius of a window (or menu) needs a compositor as this is technically a "non linear" window. Is this correct @fredkiefer ?

> I understand your concern. I can tell you in the branch we have been using, NSTabView.m : 288 `[self setNextKeyView: firstResponder];` has been replaced with `[super setNextKeyView: firstResponder];` This...

Work on this might result in refactoring some of the GSThemeDrawing stuff into NSTableView. The methods rowViewAtRow:... and viewAtColumn:row:... might be centric to this process as this seems the best...

@fredkiefer Please take a look at this and let me know. The changes clean up the code a great deal.

@fredkiefer let me know what you think please. :)