wxD and wx.NET codesharing was "Active Developers using each OS"

To All:

 

I am planning to email with the wxD Team to figure out how we can work together on the wx-c dll source code.

Does anyone disagree with this?

 

I think we need a better long term plan, but I don’t know enough to decide what is best for the long term. I think SWIG is the way to go, I am thinking this because the following projects use it.

1. wxPython
2. jwx! (brand new project at http://jwx.sourceforge.net)
3. wxRuby2
4. wxLua

But, I have looked into SWIG and it is beyond my knowledge level at this time in order to decide if it is a good choice. So, I figure to wait till wxC is resurrected by the wxHaskell project and look into wxC and SWIG again. Also, I hope a new active developer with more knowledge than me can help the group decide which way to go.

 

I consider working with the wxD Team to be continuing on the current path of wx.net team was following. From my point of view, deciding to work with the wxD Team should mainly just be a code formatting and macro adoption issue. I do assume that scripts will be needed to convert from one project to the other.  I plan on waiting till the wxD Team goes to using SVN before doing any major changes in our code. I also plan to wait until I get feedback from the rest of you.

 

Tim Stahlhut

 

 

Hey,
As you know Ive been basically inactive on the project but I have been talking to jabber.fr">"Kowey" from the wxHaskell project about resurrecting wxC from its grave - to make binding easier for people who want to use wxWidgets from different languages and platforms.

They are currently working on a refactor of their C binding layer - as I understand this will be complete after their next release. Maybe we should start binding against their wxC implementation so that we don't have to maintain our own?

~James D