OpenEuphoria

1. Autogenerating wxEuphoria wrappers

• Posted by dcuny Dec 03, 2014
• 3650 views

I figured since I've diverged from my original topic, I'd at least give the new thread a proper title.

I'm writing a wrapper generator for wxEuphoria. Input function prototypes (like a .h file) and it auto-generates wrappers.

I have a couple more stupid questions. Given this prototype:

wxScrollBar(wxWindow* parent, wxWindowID id, const wxPoint& pos = wxDefaultPosition, const wxSize& size = wxDefaultSize, long style = wxSB_HORIZONTAL, const wxValidator& validator = wxDefaultValidator, const wxString& name = "scrollBar")

The wrapper code generates:

Again, the ?? indicates where the program doesn't know how to handle a datatype. In this case, it's a long.

How should I be casting the long? And is there anything else obviously wrong with the code? I've got my doubts about the handling of the string literal.

Thanks!

- David

3. Re: Autogenerating wxEuphoria wrappers

• Posted by dcuny Dec 03, 2014
• 3618 views

Hrm... Well there's a larger problem I'm trying to deal with here. How is the wrapper generator supposed to know that style is a inptr_t? Based on the prototype, it looks like it's declared as a long:

long style = wxSB_HORIZONTAL

Obviously, the code generator isn't going to be able to know to look at the NEW_CONTROL macro.

I'll just assume that all long datatypes can be treated like this.

But again, how does the code generator know that? The prototypes that I'm using came from the wxWidgets website. Obviously, there was a decision that wxEuphoria would have constructors that didn't match those of wxWidgets.

That's fine, but the question then becomes how the wrapper generator gets informed of this, so it can generate the proper code.

You can't just change the parameters in the prototype, because the wrapper generator still needs to construct the correct call internally.

There are a couple ways to handle this. One is to make the assumption that all constructor calls that reference wxPoint and wxSize expect an integer pair, and have it generate appropriate code.

Another option would be to manually replace wxPoint and wxSize with WXPOINT and WXSIZE to inform the wrapper generator that these are intended to be replaced. I could add a flag like this:

so you could declare additional expansions if you needed, instead of having to modify the code generator.

Thoughts?

Again, this is something that can be handled fairly easily by adding a flag to the prototype.

Since wxValidator is an optional parameter, it's a non-issue in this case. For places where wxEuphoria deviates from the wxWidgets prototypes, the fallback solution would be to use the {% ... }% directives to insert the new prototype, and then some additional directive telling it to create glue for that code.

Excellent. I think I've got the "basic prototype to C++" code working fairly well, so I'll turn my attention to handling events and constants, since the wxStyledTextControl has a whole lot of those. I read your comments, but didn't have a chance to look through the wxEuphoria code yet.

Thanks!

- David

5. Re: Autogenerating wxEuphoria wrappers

• Posted by ghaberek (admin) Dec 05, 2014
• 3468 views

That looks great. However, in the prototype you provide, pos and size are still optional, so that should probably be accounted for in the wrapper code.

wxPoint pos = wxDefaultPosition; 
if (seq_len >= 4) pos = wxPoint( get_int( parms, 3 ), get_int( parms, 4 ) ); 
 
wxSize size = wxDefaultSize; 
if (seq_len >= 6) size = wxSize( get_int( parms, 5 ), get_int( parms, 6 ) );  

Yeah, we're screwed...

                    virtual int wxBookCtrlBase::HitTest (const wxPoint &pt, long *flags=NULL) const  
virtual wxCalendarHitTestResult wxCalendarCtrl::HitTest (const wxPoint &pos, wxDateTime *date=NULL, wxDateTime::WeekDay *wd=NULL) 
                   virtual void wxDataViewCtrl::HitTest (const wxPoint &point, wxDataViewItem &item, wxDataViewColumn *&col) const  
                               long wxListCtrl::HitTest (const wxPoint &point, int &flags, long *ptrSubItem=NULL) const 
    wxPropertyGridHitTestResult wxPropertyGrid::HitTest (const wxPoint &pt) const  
            wxTextCtrlHitTestResult wxTextCtrl::HitTest (const wxPoint &pt, long *pos) const  
                       wxTreeItemId wxTreeCtrl::HitTest (const wxPoint &point, int &flags) const  

And I'm sure there are more HitTest methods I haven't found yet.

Nope. But there needs to be. My plan is to wrap each class function discretely and then separate each class into their own include file (e.g. wx/class/wxScrollBar.e) so that we can separate functions by namespace, and then public include those from corresponding wxWidgets-style include files (e.g. wx/scrollbar.e) to better match wxWidgets coding styles. So this is where the automation comes in.

-Greg

7. Re: Autogenerating wxEuphoria wrappers

• Posted by ghaberek (admin) Dec 17, 2014
• 3418 views

Where can I find the latest source code for wxBasic? It appears there are two sites: wxbasic.sourceforge.net and wxbasic.net. The files on SourceForge appear to be outdated.

I discovered those differences as well. I had previously tried using the Doxygen XML output to a similar effect.

I hadn't thought of this, but that's a great idea. And the constant names can still be derived from from the parsed data.

I have considered it for a long time. Development has stalled out over the past few years and I think reorganizing it will help foster future development.

Automating the wrapping process is well worth the effort to keep the entire wxEuphoria in check with the upstream wxWidgets library.

-Greg