If you were to change abtBuildInternals, how many methods would need to change total?
Not sure exactly what you're asking, these are the changes I see:classes
AbtPortableWINNotebookView -> AbtCwTabStripView
AbtPortableNotebookPageView -> AbtCwTabViewpage/tab methods
tabLabel: -> labelString:
pageLabel: -> (not available, omit)notebook/tabstrip events
currentPage -> currentTab
aboutToChangePages -> (not available, omit)
I agree entirely that native Windows widgets should be wrappered properly, but that's a tall order, I was looking for something much simpler.
It's possible to create GUIs in VA Smalltalk that avoid all the OS/2-era controls, but it's a lot of work, fighting the tool all the way. And sadly, there is no alternative to EwTableList. Support for the native Windows table control, ListView, is at the top of my wish list. I have extended EwTableList many times to add sorting and filtering controls, make its appearance better match XP, etc. If ListView was supported, we would get those features for free and wouldn't have to keep chasing Microsoft's fashion trends in widget appearance.
Having said that, all I want right now is a way to replace portable table controls that doesn't require me to recreate each GUI manually. If I was working at the Common Widgets level, or using WindowBuilder, I could modify the code directly, but VA parts don't seem to allow that.
As for the absence of some events on CwTabStripView, I can easily work around that, it's the bulk of GUI creation I'm trying to avoid redoing manually.