Current list of wxUE generated controls not implemented in wxRuby about wxruby3 HOT 3 CLOSED

wxBannerWindow and wxInfoBar will be added when I merge the latest PR.
For wxRearrangeCtrl (and wxRearrangeList), wxSpinCtrlDouble and wxCommandLinkButton I have created separate issues and these will most likely also be added before the first final release.

The DataView classes will definitely NOT be added in the first release. I want to have a close look at these to see if adding is really beneficial or that maybe a pure Ruby solution might be preferable.

Also wxWebView will definitely NOT be added yet (if ever) for at least two reasons:

• Current support seems spotty to say the least. I tried but had no luck getting this to work with GTK3 and seeing the documentation did not even try to get it to work on Windows and Mac;
• I'm not sure I really want this in. wxRuby is targeted at building desktop application with Ruby not some glorified container for yet another web application 😉

Just add any other missing classes you encounter to this issue and I'll have a look.

from wxruby3.

I've made it through my list of controls, and it looks like you have implemented wxRuby versions for everything else that wxUiEditor creates.

The one exception is wxTreeListCtrl. That's just a wrapper around wxDataViewCtrl, so I wouldn't expect you to support it. Neither wxPython or XRC supports it either. If you do at some point decide to implement DataView classes, then this might make sense to implement as well.

Understood on the wxWebView. I actually use it as a tab in wxUiEditor just because I need to display documentation for whatever control the user has selected using whichever programming language the user is generating code for. That makes it handy to have it automatically switch between wxWidgets, wxPython or wxRuby URLs. So not really a browser, but useful in a desktop application. I could potentially see someone else using it when they've got a fixed documentation set. I'm not going to worry about it unless I get a specific request to support it in wxRuby -- then I'll point them in your direction. 😄

from wxruby3.

Right, so this issue can now be closed.
I created 2 issues for the two remaining open areas of possible interest for sometime in the future.

from wxruby3.