Hi to all of you, especially core members,
I started to work on wxRuby3 taking into account a bunch of the goals
defined in the wxRuby wiki
(http://wxruby.rubyforge.org/wiki/wiki.pl?DevelopmentRoadmap)
- builds against wxWidgets HEAD (the upcoming 2.9.5 which will be the
last before 3.0)
- Use wxWidgets interface files
- No more hand maintenance of custom wxRuby C headers
- No more hand maintenance of documentation
- Multiple shared libs (no more big monolithic build)
I''m currently at the stage of proof of concept, I have this minimal
script running:
require ''wx''
Wx::App.run { Wx::Frame.new(nil, -1, "Yop").show }
I work on MacOS (SL), it also runs on CentOS 6.3 (x64), I did a quick
try on Windows XP but gcc is segfaulting (MingW), I postpone Windows for
now.
Now the questions:
1. Where to publish the code of this new release?
I propose a move to github.com with an import of the current SVN.
The move to git will allow us to easily create dev branches and merge
them together.
If you agree on that, we''ll have to find someone to do it as this is
beyond my skills.
2. Rework the building process for every platform.
After point 1 will be done, I''ll publish my code and so we may start
hacking on.
I just moved to MacOS, so I have no particular skills on building
details on this platform.
Thus I''m looking for people wanting to hack the build process for every
platform (wxWidgets build process changed slightly in 2.9)
3. SWIG interface files reorganization.
Because of the use of wxWidgets interface file and the enhancement of
the wxWidgets API in 2.9, the current content of the wxRuby swig files
(for all swig''ed classes) have to be moved and checked against
wxWidgets
2.9, volunteers needed.
Of course, this will be a community effort, so if you want to contribute
in any way, let us know here.
Best Regards and Happy New Year to all of you.
Pascal Hurni
Hello Pascal, Thank you for taking an interest in getting these things build with wxRuby 3.0. I am currently setting up a Git Repository on GitHub right now out of the Subversion repository, and hope to have it setup initially to get everything properly done. This of-course may not actually happen, but give me some time, while I do this, and get everything up and going. I will send out an email when I have the repository completed with at-least trunk available. On Wed, Jan 2, 2013 at 12:49 PM, Pascal Hurni <pascal_hurni at fastmail.fm>wrote:> Hi to all of you, especially core members, > > I started to work on wxRuby3 taking into account a bunch of the goals > defined in the wxRuby wiki > (http://wxruby.rubyforge.org/**wiki/wiki.pl?**DevelopmentRoadmap<http://wxruby.rubyforge.org/wiki/wiki.pl?DevelopmentRoadmap> > ) > - builds against wxWidgets HEAD (the upcoming 2.9.5 which will be the > last before 3.0) > - Use wxWidgets interface files > - No more hand maintenance of custom wxRuby C headers > - No more hand maintenance of documentation > - Multiple shared libs (no more big monolithic build) > > I''m currently at the stage of proof of concept, I have this minimal > script running: > require ''wx'' > Wx::App.run { Wx::Frame.new(nil, -1, "Yop").show } > > I work on MacOS (SL), it also runs on CentOS 6.3 (x64), I did a quick > try on Windows XP but gcc is segfaulting (MingW), I postpone Windows for > now. > > Now the questions: > > 1. Where to publish the code of this new release? > I propose a move to github.com with an import of the current SVN. > The move to git will allow us to easily create dev branches and merge > them together. > If you agree on that, we''ll have to find someone to do it as this is > beyond my skills. > > 2. Rework the building process for every platform. > After point 1 will be done, I''ll publish my code and so we may start > hacking on. > I just moved to MacOS, so I have no particular skills on building > details on this platform. > Thus I''m looking for people wanting to hack the build process for every > platform (wxWidgets build process changed slightly in 2.9) > > 3. SWIG interface files reorganization. > Because of the use of wxWidgets interface file and the enhancement of > the wxWidgets API in 2.9, the current content of the wxRuby swig files > (for all swig''ed classes) have to be moved and checked against wxWidgets > 2.9, volunteers needed. > > Of course, this will be a community effort, so if you want to contribute > in any way, let us know here. > > Best Regards and Happy New Year to all of you. > > Pascal Hurni > > ______________________________**_________________ > wxruby-development mailing list > wxruby-development at rubyforge.**org <wxruby-development at rubyforge.org> > http://rubyforge.org/mailman/**listinfo/wxruby-development<http://rubyforge.org/mailman/listinfo/wxruby-development> >-- Mario Steele Fleet Captain CO - Geo 99 CO - USS T''hy''la XO - Diplomatic Corps - Second Life http://www.iftcommand.com/chapters/thyla/ http://www.trekfederation.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/wxruby-development/attachments/20130103/f6233791/attachment-0001.html>
Hello Pascal, Alex, and whoever else may be listening in on this, ;-) I have created a Git repository at http://github.com/eumario/wxruby.git It includes the full Subversion repository, along with all the major tags available ever since the subversion repository was created. Anyone wanting commit access, please let me know your github user account, and I will add you to the master repository. Of course, you don''t have to have commit access to the master repository, and instead just fork the code and submit back a pull request for the code, but it''s just easier on me if you request the access. ;-) Enjoy, Mario On Thu, Jan 3, 2013 at 3:47 PM, Mario Steele <mario at ruby-im.net> wrote:> Hello Pascal, > > Thank you for taking an interest in getting these things build with wxRuby > 3.0. I am currently setting up a Git Repository on GitHub right now out of > the Subversion repository, and hope to have it setup initially to get > everything properly done. This of-course may not actually happen, but give > me some time, while I do this, and get everything up and going. I will > send out an email when I have the repository completed with at-least trunk > available. > > > On Wed, Jan 2, 2013 at 12:49 PM, Pascal Hurni <pascal_hurni at fastmail.fm>wrote: > >> Hi to all of you, especially core members, >> >> I started to work on wxRuby3 taking into account a bunch of the goals >> defined in the wxRuby wiki >> (http://wxruby.rubyforge.org/**wiki/wiki.pl?**DevelopmentRoadmap<http://wxruby.rubyforge.org/wiki/wiki.pl?DevelopmentRoadmap> >> ) >> - builds against wxWidgets HEAD (the upcoming 2.9.5 which will be the >> last before 3.0) >> - Use wxWidgets interface files >> - No more hand maintenance of custom wxRuby C headers >> - No more hand maintenance of documentation >> - Multiple shared libs (no more big monolithic build) >> >> I''m currently at the stage of proof of concept, I have this minimal >> script running: >> require ''wx'' >> Wx::App.run { Wx::Frame.new(nil, -1, "Yop").show } >> >> I work on MacOS (SL), it also runs on CentOS 6.3 (x64), I did a quick >> try on Windows XP but gcc is segfaulting (MingW), I postpone Windows for >> now. >> >> Now the questions: >> >> 1. Where to publish the code of this new release? >> I propose a move to github.com with an import of the current SVN. >> The move to git will allow us to easily create dev branches and merge >> them together. >> If you agree on that, we''ll have to find someone to do it as this is >> beyond my skills. >> >> 2. Rework the building process for every platform. >> After point 1 will be done, I''ll publish my code and so we may start >> hacking on. >> I just moved to MacOS, so I have no particular skills on building >> details on this platform. >> Thus I''m looking for people wanting to hack the build process for every >> platform (wxWidgets build process changed slightly in 2.9) >> >> 3. SWIG interface files reorganization. >> Because of the use of wxWidgets interface file and the enhancement of >> the wxWidgets API in 2.9, the current content of the wxRuby swig files >> (for all swig''ed classes) have to be moved and checked against wxWidgets >> 2.9, volunteers needed. >> >> Of course, this will be a community effort, so if you want to contribute >> in any way, let us know here. >> >> Best Regards and Happy New Year to all of you. >> >> Pascal Hurni >> >> ______________________________**_________________ >> wxruby-development mailing list >> wxruby-development at rubyforge.**org <wxruby-development at rubyforge.org> >> http://rubyforge.org/mailman/**listinfo/wxruby-development<http://rubyforge.org/mailman/listinfo/wxruby-development> >> > > > > -- > Mario Steele > Fleet Captain > CO - Geo 99 > CO - USS T''hy''la > XO - Diplomatic Corps - Second Life > http://www.iftcommand.com/chapters/thyla/ > http://www.trekfederation.com >-- Mario Steele Fleet Captain CO - Geo 99 CO - USS T''hy''la XO - Diplomatic Corps - Second Life http://www.iftcommand.com/chapters/thyla/ http://www.trekfederation.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/wxruby-development/attachments/20130103/73ccefdd/attachment.html>
Hello all again, I just finished re-organizing all the branches into a more sane environment, and ensured that we had a proper trunk with the last bit of code committed by Alex. I only retained major release point branches as they were in the svn, but I did not retain all release points. We have wxruby_010 branch, which is from Kevin Smith, the original author of the wxRuby bindings. wxruby_0036, which was a quirk one, and didn''t know if Alex wanted to keep that one around or not. ;-), wxruby_060, which is the last wxRuby bindings to be hybrid created, between a makeshift parser, and hand coding of the routines, master holds the latest wxRuby code, as committed a year ago by Alex, and then finally, wxsugar, since that''s always been a sub-project of wxRuby, I put it into it''s own branch. If you would prefer all point releases that we currently have in the Subversion in the Git repository, I will see what I can do to make that happen, but it may just be me creating branches specifically for those point releases, without any history associated with them. L8ers, Mario On Thu, Jan 3, 2013 at 5:29 PM, Mario Steele <mario at ruby-im.net> wrote:> Hello Pascal, Alex, and whoever else may be listening in on this, ;-) > > I have created a Git repository at http://github.com/eumario/wxruby.git It includes the full Subversion repository, along with all the major tags > available ever since the subversion repository was created. Anyone wanting > commit access, please let me know your github user account, and I will add > you to the master repository. Of course, you don''t have to have commit > access to the master repository, and instead just fork the code and submit > back a pull request for the code, but it''s just easier on me if you request > the access. ;-) > > Enjoy, > > Mario > > > On Thu, Jan 3, 2013 at 3:47 PM, Mario Steele <mario at ruby-im.net> wrote: > >> Hello Pascal, >> >> Thank you for taking an interest in getting these things build with >> wxRuby 3.0. I am currently setting up a Git Repository on GitHub right now >> out of the Subversion repository, and hope to have it setup initially to >> get everything properly done. This of-course may not actually happen, but >> give me some time, while I do this, and get everything up and going. I >> will send out an email when I have the repository completed with at-least >> trunk available. >> >> >> On Wed, Jan 2, 2013 at 12:49 PM, Pascal Hurni <pascal_hurni at fastmail.fm>wrote: >> >>> Hi to all of you, especially core members, >>> >>> I started to work on wxRuby3 taking into account a bunch of the goals >>> defined in the wxRuby wiki >>> (http://wxruby.rubyforge.org/**wiki/wiki.pl?**DevelopmentRoadmap<http://wxruby.rubyforge.org/wiki/wiki.pl?DevelopmentRoadmap> >>> ) >>> - builds against wxWidgets HEAD (the upcoming 2.9.5 which will be the >>> last before 3.0) >>> - Use wxWidgets interface files >>> - No more hand maintenance of custom wxRuby C headers >>> - No more hand maintenance of documentation >>> - Multiple shared libs (no more big monolithic build) >>> >>> I''m currently at the stage of proof of concept, I have this minimal >>> script running: >>> require ''wx'' >>> Wx::App.run { Wx::Frame.new(nil, -1, "Yop").show } >>> >>> I work on MacOS (SL), it also runs on CentOS 6.3 (x64), I did a quick >>> try on Windows XP but gcc is segfaulting (MingW), I postpone Windows for >>> now. >>> >>> Now the questions: >>> >>> 1. Where to publish the code of this new release? >>> I propose a move to github.com with an import of the current SVN. >>> The move to git will allow us to easily create dev branches and merge >>> them together. >>> If you agree on that, we''ll have to find someone to do it as this is >>> beyond my skills. >>> >>> 2. Rework the building process for every platform. >>> After point 1 will be done, I''ll publish my code and so we may start >>> hacking on. >>> I just moved to MacOS, so I have no particular skills on building >>> details on this platform. >>> Thus I''m looking for people wanting to hack the build process for every >>> platform (wxWidgets build process changed slightly in 2.9) >>> >>> 3. SWIG interface files reorganization. >>> Because of the use of wxWidgets interface file and the enhancement of >>> the wxWidgets API in 2.9, the current content of the wxRuby swig files >>> (for all swig''ed classes) have to be moved and checked against wxWidgets >>> 2.9, volunteers needed. >>> >>> Of course, this will be a community effort, so if you want to contribute >>> in any way, let us know here. >>> >>> Best Regards and Happy New Year to all of you. >>> >>> Pascal Hurni >>> >>> ______________________________**_________________ >>> wxruby-development mailing list >>> wxruby-development at rubyforge.**org <wxruby-development at rubyforge.org> >>> http://rubyforge.org/mailman/**listinfo/wxruby-development<http://rubyforge.org/mailman/listinfo/wxruby-development> >>> >> >> >> >> -- >> Mario Steele >> Fleet Captain >> CO - Geo 99 >> CO - USS T''hy''la >> XO - Diplomatic Corps - Second Life >> http://www.iftcommand.com/chapters/thyla/ >> http://www.trekfederation.com >> > > > > -- > Mario Steele > Fleet Captain > CO - Geo 99 > CO - USS T''hy''la > XO - Diplomatic Corps - Second Life > http://www.iftcommand.com/chapters/thyla/ > http://www.trekfederation.com >-- Mario Steele Fleet Captain CO - Geo 99 CO - USS T''hy''la XO - Diplomatic Corps - Second Life http://www.iftcommand.com/chapters/thyla/ http://www.trekfederation.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/wxruby-development/attachments/20130103/61e4d943/attachment.html>
let me point you to something i did: https://github.com/Hanmac/rwx
its an "rewrite" of wxRuby against wxWidgets2.9.* but with my own
hands.
its may not be what you want becausethe binding is still monolithic, but
it also comines features into the "main" functions ... so you could
use
WX::Frame.new for loading xrc files too.
there are other BIG differences, like
- the IDs are not ugly constants anymore, they are automatic wrapped
into beautyful symbols and user setted symbols are automatic wrapped
into IDs
- the same is for ArtProvider icons, and enum values
- wxWindow objects are rememberd so it does not create new ruby
objects everytime you ask for it (like when you do get_child(name)) so
you could add ruby instance variables to the objects
- wxVariant is automatic converted into the right ruby object and reverse
- rwx does not use the EVTTABLE from wx2.8 but the newer Connect and
Bind functions, the proc objects are used for bind are also protected
like the window objects from the Rubys GC
- wxEvents are automatic mapped into the right ruby Class if defined
(so wxKexEvent is WX::Event::Key but wxPaintEvent is generic WX::Event)
- eventTypes are like enums automatic turned into symbols too
- all child classes of wxWindow support an opts Hash as parameter (and
use then in the right order when doing the 2-step creation of the Objects)
- generic classes like wxSize and wxColour automatic wrap from similar
objects, so [10,20] can be used as size parameter too, while an ruby
Struct with red,green,blue methods can be converted into an wxColour object
BIGGEST Diff: i dont use swig because it is the root of evil and even
its own creator does not like it
PS:
your line changed a bit into
WX::App.run { WX::Frame.new(nil, title: "Yop").show }
would work on my system (this is only not commited yet)
Best Regards
Hanmac
PS: i am sending it again because wxruby mailing list did ignore me
Hi Mario, Great news! Thanx for the work. I think that it''s totally acceptable to have only the branches you set up. For the write access, here''s my github account: https://github.com/phurni I''ll create a new branch for wxruby3_alpha. Best Regards, Pascal Le 04.01.13 00:13, Mario Steele a ?crit :> Hello all again, > > I just finished re-organizing all the branches into a more sane > environment, and ensured that we had a proper trunk with the last bit > of code committed by Alex. I only retained major release point > branches as they were in the svn, but I did not retain all release > points. We have wxruby_010 branch, which is from Kevin Smith, the > original author of the wxRuby bindings. wxruby_0036, which was a > quirk one, and didn''t know if Alex wanted to keep that one around or > not. ;-), wxruby_060, which is the last wxRuby bindings to be hybrid > created, between a makeshift parser, and hand coding of the routines, > master holds the latest wxRuby code, as committed a year ago by Alex, > and then finally, wxsugar, since that''s always been a sub-project of > wxRuby, I put it into it''s own branch. > > If you would prefer all point releases that we currently have in the > Subversion in the Git repository, I will see what I can do to make > that happen, but it may just be me creating branches specifically for > those point releases, without any history associated with them. > > L8ers, > > Mario > > > On Thu, Jan 3, 2013 at 5:29 PM, Mario Steele <mario at ruby-im.net > <mailto:mario at ruby-im.net>> wrote: > > Hello Pascal, Alex, and whoever else may be listening in on this, ;-) > > I have created a Git repository at > http://github.com/eumario/wxruby.git It includes the full > Subversion repository, along with all the major tags available > ever since the subversion repository was created. Anyone wanting > commit access, please let me know your github user account, and I > will add you to the master repository. Of course, you don''t have > to have commit access to the master repository, and instead just > fork the code and submit back a pull request for the code, but > it''s just easier on me if you request the access. ;-) > > Enjoy, > > Mario > > > On Thu, Jan 3, 2013 at 3:47 PM, Mario Steele <mario at ruby-im.net > <mailto:mario at ruby-im.net>> wrote: > > Hello Pascal, > > Thank you for taking an interest in getting these things build > with wxRuby 3.0. I am currently setting up a Git Repository > on GitHub right now out of the Subversion repository, and hope > to have it setup initially to get everything properly done. > This of-course may not actually happen, but give me some > time, while I do this, and get everything up and going. I > will send out an email when I have the repository completed > with at-least trunk available. > > > On Wed, Jan 2, 2013 at 12:49 PM, Pascal Hurni > <pascal_hurni at fastmail.fm <mailto:pascal_hurni at fastmail.fm>> > wrote: > > Hi to all of you, especially core members, > > I started to work on wxRuby3 taking into account a bunch > of the goals > defined in the wxRuby wiki > (http://wxruby.rubyforge.org/wiki/wiki.pl?DevelopmentRoadmap) > - builds against wxWidgets HEAD (the upcoming 2.9.5 which > will be the > last before 3.0) > - Use wxWidgets interface files > - No more hand maintenance of custom wxRuby C headers > - No more hand maintenance of documentation > - Multiple shared libs (no more big monolithic build) > > I''m currently at the stage of proof of concept, I have > this minimal > script running: > require ''wx'' > Wx::App.run { Wx::Frame.new(nil, -1, "Yop").show } > > I work on MacOS (SL), it also runs on CentOS 6.3 (x64), I > did a quick > try on Windows XP but gcc is segfaulting (MingW), I > postpone Windows for now. > > Now the questions: > > 1. Where to publish the code of this new release? > I propose a move to github.com <http://github.com> with an > import of the current SVN. > The move to git will allow us to easily create dev > branches and merge > them together. > If you agree on that, we''ll have to find someone to do it > as this is > beyond my skills. > > 2. Rework the building process for every platform. > After point 1 will be done, I''ll publish my code and so we > may start > hacking on. > I just moved to MacOS, so I have no particular skills on > building > details on this platform. > Thus I''m looking for people wanting to hack the build > process for every > platform (wxWidgets build process changed slightly in 2.9) > > 3. SWIG interface files reorganization. > Because of the use of wxWidgets interface file and the > enhancement of > the wxWidgets API in 2.9, the current content of the > wxRuby swig files > (for all swig''ed classes) have to be moved and checked > against wxWidgets 2.9, volunteers needed. > > Of course, this will be a community effort, so if you want > to contribute in any way, let us know here. > > Best Regards and Happy New Year to all of you. > > Pascal Hurni > > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > <mailto:wxruby-development at rubyforge.org> > http://rubyforge.org/mailman/listinfo/wxruby-development > > > > > -- > Mario Steele > Fleet Captain > CO - Geo 99 > CO - USS T''hy''la > XO - Diplomatic Corps - Second Life > http://www.iftcommand.com/chapters/thyla/ > http://www.trekfederation.com > > > > > -- > Mario Steele > Fleet Captain > CO - Geo 99 > CO - USS T''hy''la > XO - Diplomatic Corps - Second Life > http://www.iftcommand.com/chapters/thyla/ > http://www.trekfederation.com > > > > > -- > Mario Steele > Fleet Captain > CO - Geo 99 > CO - USS T''hy''la > XO - Diplomatic Corps - Second Life > http://www.iftcommand.com/chapters/thyla/ > http://www.trekfederation.com > > > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/wxruby-development/attachments/20130104/a6521818/attachment.html>
Hello Hans and Pascal, I''ll address a few things here. First, I want to address Hans work. Do not consider this in any way to be against you, or meant to be of ill-will towards you. Your work with rwx, is pretty good so far. And I wish you all the best on your work, I really do. It was decided a long time ago, with wxRuby, that hand-coding the API, was a major under-taking, to get all the events, features, and such built into the library. It was at that time, wxRuby 0.6.0 was the last combination of generated code, and hand-coded code to be used. From that point, wxRuby2 was created, with the specific goal of using SWIG to wrap all the classes, and features of wxWidgets into a Ruby API. Stuff like what you have started to work on, can be done as well in wxRuby, and is partly why wx_sugar exists, to provide methods that are more Ruby like, and provide simpler access to the wxRuby pipework. It has been the goal of wxRuby since wxRuby2 was released, that work be done with SWIG, as though it''s faults do have their "pitfalls", it has been the best to get all the features that are available in the wxWidgets library, available to wxRuby. And I believe I speak for both myself, and Alex Fenton, who took over the wxRuby project from Kevin Smith, that we will continue to work with SWIG to generate the bindings, and further our goals with wxRuby. As I said before, don''t take this the wrong way, or as a means to discount your work. What you have done, is pretty good, and I wish you all the luck. Pascal, I have added you to have Access to the repository, and should be able to create new branches, and such, and commit them. If you have any issues, please let me know, and I will see what I can find out about the issues. Thank you for your work to continue bringing wxRuby3 to life. Mario Steele On Fri, Jan 4, 2013 at 4:37 PM, Pascal Hurni <pascal_hurni at fastmail.fm>wrote:> Hi Mario, > > Great news! Thanx for the work. I think that it''s totally acceptable to > have only the branches you set up. > > For the write access, here''s my github account: https://github.com/phurni > > I''ll create a new branch for wxruby3_alpha. > > Best Regards, > > Pascal > > Le 04.01.13 00:13, Mario Steele a ?crit : > > Hello all again, > > I just finished re-organizing all the branches into a more sane > environment, and ensured that we had a proper trunk with the last bit of > code committed by Alex. I only retained major release point branches as > they were in the svn, but I did not retain all release points. We have > wxruby_010 branch, which is from Kevin Smith, the original author of the > wxRuby bindings. wxruby_0036, which was a quirk one, and didn''t know if > Alex wanted to keep that one around or not. ;-), wxruby_060, which is the > last wxRuby bindings to be hybrid created, between a makeshift parser, and > hand coding of the routines, master holds the latest wxRuby code, as > committed a year ago by Alex, and then finally, wxsugar, since that''s > always been a sub-project of wxRuby, I put it into it''s own branch. > > If you would prefer all point releases that we currently have in the > Subversion in the Git repository, I will see what I can do to make that > happen, but it may just be me creating branches specifically for those > point releases, without any history associated with them. > > L8ers, > > Mario > > > On Thu, Jan 3, 2013 at 5:29 PM, Mario Steele <mario at ruby-im.net> wrote: > >> Hello Pascal, Alex, and whoever else may be listening in on this, ;-) >> >> I have created a Git repository at http://github.com/eumario/wxruby.git It includes the full Subversion repository, along with all the major tags >> available ever since the subversion repository was created. Anyone wanting >> commit access, please let me know your github user account, and I will add >> you to the master repository. Of course, you don''t have to have commit >> access to the master repository, and instead just fork the code and submit >> back a pull request for the code, but it''s just easier on me if you request >> the access. ;-) >> >> Enjoy, >> >> Mario >> >> >> On Thu, Jan 3, 2013 at 3:47 PM, Mario Steele <mario at ruby-im.net> wrote: >> >>> Hello Pascal, >>> >>> Thank you for taking an interest in getting these things build with >>> wxRuby 3.0. I am currently setting up a Git Repository on GitHub right now >>> out of the Subversion repository, and hope to have it setup initially to >>> get everything properly done. This of-course may not actually happen, but >>> give me some time, while I do this, and get everything up and going. I >>> will send out an email when I have the repository completed with at-least >>> trunk available. >>> >>> >>> On Wed, Jan 2, 2013 at 12:49 PM, Pascal Hurni <pascal_hurni at fastmail.fm>wrote: >>> >>>> Hi to all of you, especially core members, >>>> >>>> I started to work on wxRuby3 taking into account a bunch of the goals >>>> defined in the wxRuby wiki >>>> (http://wxruby.rubyforge.org/wiki/wiki.pl?DevelopmentRoadmap) >>>> - builds against wxWidgets HEAD (the upcoming 2.9.5 which will be the >>>> last before 3.0) >>>> - Use wxWidgets interface files >>>> - No more hand maintenance of custom wxRuby C headers >>>> - No more hand maintenance of documentation >>>> - Multiple shared libs (no more big monolithic build) >>>> >>>> I''m currently at the stage of proof of concept, I have this minimal >>>> script running: >>>> require ''wx'' >>>> Wx::App.run { Wx::Frame.new(nil, -1, "Yop").show } >>>> >>>> I work on MacOS (SL), it also runs on CentOS 6.3 (x64), I did a quick >>>> try on Windows XP but gcc is segfaulting (MingW), I postpone Windows >>>> for now. >>>> >>>> Now the questions: >>>> >>>> 1. Where to publish the code of this new release? >>>> I propose a move to github.com with an import of the current SVN. >>>> The move to git will allow us to easily create dev branches and merge >>>> them together. >>>> If you agree on that, we''ll have to find someone to do it as this is >>>> beyond my skills. >>>> >>>> 2. Rework the building process for every platform. >>>> After point 1 will be done, I''ll publish my code and so we may start >>>> hacking on. >>>> I just moved to MacOS, so I have no particular skills on building >>>> details on this platform. >>>> Thus I''m looking for people wanting to hack the build process for every >>>> platform (wxWidgets build process changed slightly in 2.9) >>>> >>>> 3. SWIG interface files reorganization. >>>> Because of the use of wxWidgets interface file and the enhancement of >>>> the wxWidgets API in 2.9, the current content of the wxRuby swig files >>>> (for all swig''ed classes) have to be moved and checked against >>>> wxWidgets 2.9, volunteers needed. >>>> >>>> Of course, this will be a community effort, so if you want to >>>> contribute in any way, let us know here. >>>> >>>> Best Regards and Happy New Year to all of you. >>>> >>>> Pascal Hurni >>>> >>>> _______________________________________________ >>>> wxruby-development mailing list >>>> wxruby-development at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/wxruby-development >>>> >>> >>> >>> >>> -- >>> Mario Steele >>> Fleet Captain >>> CO - Geo 99 >>> CO - USS T''hy''la >>> XO - Diplomatic Corps - Second Life >>> http://www.iftcommand.com/chapters/thyla/ >>> http://www.trekfederation.com >>> >> >> >> >> -- >> Mario Steele >> Fleet Captain >> CO - Geo 99 >> CO - USS T''hy''la >> XO - Diplomatic Corps - Second Life >> http://www.iftcommand.com/chapters/thyla/ >> http://www.trekfederation.com >> > > > > -- > Mario Steele > Fleet Captain > CO - Geo 99 > CO - USS T''hy''la > XO - Diplomatic Corps - Second Life > http://www.iftcommand.com/chapters/thyla/ > http://www.trekfederation.com > > > _______________________________________________ > wxruby-development mailing listwxruby-development at rubyforge.orghttp://rubyforge.org/mailman/listinfo/wxruby-development > > > > _______________________________________________ > wxruby-development mailing list > wxruby-development at rubyforge.org > http://rubyforge.org/mailman/listinfo/wxruby-development > >-- Mario Steele Fleet Captain CO - Geo 99 CO - USS T''hy''la XO - Diplomatic Corps - Second Life http://www.iftcommand.com/chapters/thyla/ http://www.trekfederation.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/wxruby-development/attachments/20130105/fcb2b574/attachment-0001.html>