wxruby users - Oct 2004 - wxruby-swig on Windows & possible release

I''m trying to build wxruby-swig on windows with the idea of building a
windows installer for it. I think that this would go a long way toward
encouraging windows developers to try out wxruby-swig. What do you think?
Are we far enough along to contemplate a release?

Building wxruby-swig on windows is actually going pretty smoothly, but I
want to build it with vc++ 7.1 to match the one-click ruby installer (which
is also built with vc++ 7.1). But in order to do so I need to make some
changes to rakemswin.rb. The main problem I need to correct is the way debug
symbols are picked up (the linker option /PDBTYPE no longer exists in vc++
7). There might be more but I don''t know yet.

Anyway, is there any objection to my modifying and checking in rakemswin.rb
for vc++ 7.1.? Or, should I leave it as is and create a new one (like
rakemswin7.rb)?

Curt

Curt Hibbs wrote:
> I''m trying to build wxruby-swig on windows with the idea of
building a
> windows installer for it. I think that this would go a long way toward
> encouraging windows developers to try out wxruby-swig. What do you think?
> Are we far enough along to contemplate a release?
I think that''s a great idea. Nick knows better than I how close we are 
to a wxruby-swig release right now.
> Anyway, is there any objection to my modifying and checking in rakemswin.rb
> for vc++ 7.1.? Or, should I leave it as is and create a new one (like
> rakemswin7.rb)?
Can a single rakemswin.rb automatically detect 7.1 and do the right 
thing? If so, I think that would be best. That''s the beauty of 
rake--full power at build time!

Kevin

> Curt Hibbs wrote:
> > I''m trying to build wxruby-swig on windows with the idea of
building a
> > windows installer for it. I think that this would go a long way toward
> > encouraging windows developers to try out wxruby-swig. What do you
think?
> > Are we far enough along to contemplate a release?
> 
> I think that''s a great idea. Nick knows better than I how close we
are
> to a wxruby-swig release right now.
Honestly, I was considering it too, and I have no objections as long as we have
a way to
say "this isn''t ready for primetime". 
> > Anyway, is there any objection to my modifying and checking in
rakemswin.rb
> > for vc++ 7.1.? Or, should I leave it as is and create a new one (like
> > rakemswin7.rb)?
> 
> Can a single rakemswin.rb automatically detect 7.1 and do the right 
> thing? If so, I think that would be best. That''s the beauty of 
> rake--full power at build time!
Actually, I don''t think anybody changes the RUBY_PLATFORM variable to
effectively
discern the difference between MSVC 6.0 and 7.1. I say make the change with some
docs around it. There are some things that need to be added, like being able to
switch
between DEBUG and RELEASE via command line options, and maybe we merge the 
changes together. In any event, non-hackers will probably use the extconf.rb
build
system instead.

Nick

Nick wrote:
>
> > Curt Hibbs wrote:
> > > I''m trying to build wxruby-swig on windows with the idea
of building a
> > > windows installer for it. I think that this would go a long way
toward
> > > encouraging windows developers to try out wxruby-swig. What
> do you think?
> > > Are we far enough along to contemplate a release?
> >
> > I think that''s a great idea. Nick knows better than I how
close we are
> > to a wxruby-swig release right now.
>
> Honestly, I was considering it too, and I have no objections as
> long as we have a way to
> say "this isn''t ready for primetime".
>
> > > Anyway, is there any objection to my modifying and checking
> in rakemswin.rb
> > > for vc++ 7.1.? Or, should I leave it as is and create a new one
(like
> > > rakemswin7.rb)?
> >
> > Can a single rakemswin.rb automatically detect 7.1 and do the right
> > thing? If so, I think that would be best. That''s the beauty
of
> > rake--full power at build time!
>
> Actually, I don''t think anybody changes the RUBY_PLATFORM
> variable to effectively
> discern the difference between MSVC 6.0 and 7.1. I say make the
> change with some
> docs around it. There are some things that need to be added, like
> being able to switch
> between DEBUG and RELEASE via command line options, and maybe we
> merge the
> changes together. In any event, non-hackers will probably use the
> extconf.rb build
> system instead.
It should be possible to pick options that will work in both 6.0 and 7.1.
I''ll see what I can do.

Curt

Ok, I''ve got a working build of wxruby-swig. Whenever you are ready,
label
the cvs repo for the release and I''ll build a windows installer.

Curt

Curt Hibbs wrote:
>
> Nick wrote:
> >
> > > Curt Hibbs wrote:
> > > > I''m trying to build wxruby-swig on windows with the
idea of
> building a
> > > > windows installer for it. I think that this would go a long
> way toward
> > > > encouraging windows developers to try out wxruby-swig. What
> > do you think?
> > > > Are we far enough along to contemplate a release?
> > >
> > > I think that''s a great idea. Nick knows better than I
how close we are
> > > to a wxruby-swig release right now.
> >
> > Honestly, I was considering it too, and I have no objections as
> > long as we have a way to
> > say "this isn''t ready for primetime".
> >
> > > > Anyway, is there any objection to my modifying and checking
> > in rakemswin.rb
> > > > for vc++ 7.1.? Or, should I leave it as is and create a new
> one (like
> > > > rakemswin7.rb)?
> > >
> > > Can a single rakemswin.rb automatically detect 7.1 and do the
right
> > > thing? If so, I think that would be best. That''s the
beauty of
> > > rake--full power at build time!
> >
> > Actually, I don''t think anybody changes the RUBY_PLATFORM
> > variable to effectively
> > discern the difference between MSVC 6.0 and 7.1. I say make the
> > change with some
> > docs around it. There are some things that need to be added, like
> > being able to switch
> > between DEBUG and RELEASE via command line options, and maybe we
> > merge the
> > changes together. In any event, non-hackers will probably use the
> > extconf.rb build
> > system instead.
>
> It should be possible to pick options that will work in both 6.0 and 7.1.
> I''ll see what I can do.
>
> Curt
>
> _______________________________________________
> wxruby-users mailing list
> wxruby-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wxruby-users
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.769 / Virus Database: 516 - Release Date: 9/24/2004
>

It built fine on the Mac, and has been tagged as v_MSW_PREVIEW. We''re 
good to go.

Nick

Curt Hibbs wrote:
>Ok, I''ve got a working build of wxruby-swig. Whenever you are
ready, label
>the cvs repo for the release and I''ll build a windows installer.
>
>Curt
>
>Curt Hibbs wrote:
>  
>
>>Nick wrote:
>>    
>>
>>>>Curt Hibbs wrote:
>>>>        
>>>>
>>>>>I''m trying to build wxruby-swig on windows with the
idea of
>>>>>          
>>>>>
>>building a
>>    
>>
>>>>>windows installer for it. I think that this would go a long
>>>>>          
>>>>>
>>way toward
>>    
>>
>>>>>encouraging windows developers to try out wxruby-swig. What
>>>>>          
>>>>>
>>>do you think?
>>>      
>>>
>>>>>Are we far enough along to contemplate a release?
>>>>>          
>>>>>
>>>>I think that''s a great idea. Nick knows better than I
how close we are
>>>>to a wxruby-swig release right now.
>>>>        
>>>>
>>>Honestly, I was considering it too, and I have no objections as
>>>long as we have a way to
>>>say "this isn''t ready for primetime".
>>>
>>>      
>>>
>>>>>Anyway, is there any objection to my modifying and checking
>>>>>          
>>>>>
>>>in rakemswin.rb
>>>      
>>>
>>>>>for vc++ 7.1.? Or, should I leave it as is and create a new
>>>>>          
>>>>>
>>one (like
>>    
>>
>>>>>rakemswin7.rb)?
>>>>>          
>>>>>
>>>>Can a single rakemswin.rb automatically detect 7.1 and do the
right
>>>>thing? If so, I think that would be best. That''s the
beauty of
>>>>rake--full power at build time!
>>>>        
>>>>
>>>Actually, I don''t think anybody changes the RUBY_PLATFORM
>>>variable to effectively
>>>discern the difference between MSVC 6.0 and 7.1. I say make the
>>>change with some
>>>docs around it. There are some things that need to be added, like
>>>being able to switch
>>>between DEBUG and RELEASE via command line options, and maybe we
>>>merge the
>>>changes together. In any event, non-hackers will probably use the
>>>extconf.rb build
>>>system instead.
>>>      
>>>
>>It should be possible to pick options that will work in both 6.0 and
7.1.
>>I''ll see what I can do.
>>
>>Curt
>>
>>_______________________________________________
>>wxruby-users mailing list
>>wxruby-users@rubyforge.org
>>http://rubyforge.org/mailman/listinfo/wxruby-users
>>---
>>Incoming mail is certified Virus Free.
>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>Version: 6.0.769 / Virus Database: 516 - Release Date: 9/24/2004
>>
>>    
>>
>
>_______________________________________________
>wxruby-users mailing list
>wxruby-users@rubyforge.org
>http://rubyforge.org/mailman/listinfo/wxruby-users
>
>
>
>  
>

What version number do you want to use for the release? I was thinking 0.4.0
since its not that far off from wxRuby. If so then I would name my release
installer:

wxruby-swig-0.4.0-mswin.exe

Curt
> -----Original Message-----
> From: wxruby-users-bounces@rubyforge.org
> [mailto:wxruby-users-bounces@rubyforge.org]On Behalf Of Nick
> Sent: Wednesday, October 06, 2004 6:14 AM
> To: General discussion of wxRuby
> Subject: Re: [Wxruby-users] wxruby-swig on Windows & possible release
>
>
>
> It built fine on the Mac, and has been tagged as v_MSW_PREVIEW.
We''re
> good to go.
>
> Nick
>
> Curt Hibbs wrote:
>
> >Ok, I''ve got a working build of wxruby-swig. Whenever you are
> ready, label
> >the cvs repo for the release and I''ll build a windows
installer.
> >
> >Curt
> >
> >Curt Hibbs wrote:
> >
> >
> >>Nick wrote:
> >>
> >>
> >>>>Curt Hibbs wrote:
> >>>>
> >>>>
> >>>>>I''m trying to build wxruby-swig on windows
with the idea of
> >>>>>
> >>>>>
> >>building a
> >>
> >>
> >>>>>windows installer for it. I think that this would go a
long
> >>>>>
> >>>>>
> >>way toward
> >>
> >>
> >>>>>encouraging windows developers to try out wxruby-swig.
What
> >>>>>
> >>>>>
> >>>do you think?
> >>>
> >>>
> >>>>>Are we far enough along to contemplate a release?
> >>>>>
> >>>>>
> >>>>I think that''s a great idea. Nick knows better
than I how close we are
> >>>>to a wxruby-swig release right now.
> >>>>
> >>>>
> >>>Honestly, I was considering it too, and I have no objections as
> >>>long as we have a way to
> >>>say "this isn''t ready for primetime".
> >>>
> >>>
> >>>
> >>>>>Anyway, is there any objection to my modifying and
checking
> >>>>>
> >>>>>
> >>>in rakemswin.rb
> >>>
> >>>
> >>>>>for vc++ 7.1.? Or, should I leave it as is and create a
new
> >>>>>
> >>>>>
> >>one (like
> >>
> >>
> >>>>>rakemswin7.rb)?
> >>>>>
> >>>>>
> >>>>Can a single rakemswin.rb automatically detect 7.1 and do
the right
> >>>>thing? If so, I think that would be best. That''s
the beauty of
> >>>>rake--full power at build time!
> >>>>
> >>>>
> >>>Actually, I don''t think anybody changes the
RUBY_PLATFORM
> >>>variable to effectively
> >>>discern the difference between MSVC 6.0 and 7.1. I say make the
> >>>change with some
> >>>docs around it. There are some things that need to be added,
like
> >>>being able to switch
> >>>between DEBUG and RELEASE via command line options, and maybe
we
> >>>merge the
> >>>changes together. In any event, non-hackers will probably use
the
> >>>extconf.rb build
> >>>system instead.
> >>>
> >>>
> >>It should be possible to pick options that will work in both
> 6.0 and 7.1.
> >>I''ll see what I can do.
> >>
> >>Curt
> >>
> >>_______________________________________________
> >>wxruby-users mailing list
> >>wxruby-users@rubyforge.org
> >>http://rubyforge.org/mailman/listinfo/wxruby-users
> >>---
> >>Incoming mail is certified Virus Free.
> >>Checked by AVG anti-virus system (http://www.grisoft.com).
> >>Version: 6.0.769 / Virus Database: 516 - Release Date: 9/24/2004
> >>
> >>
> >>
> >
> >_______________________________________________
> >wxruby-users mailing list
> >wxruby-users@rubyforge.org
> >http://rubyforge.org/mailman/listinfo/wxruby-users
> >
> >
> >
> >
> >
>
> _______________________________________________
> wxruby-users mailing list
> wxruby-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wxruby-users
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.769 / Virus Database: 516 - Release Date: 9/24/2004
>

Curt Hibbs wrote:
>
> What version number do you want to use for the release? I was
> thinking 0.4.0
> since its not that far off from wxRuby. If so then I would name my release
> installer:
>
> wxruby-swig-0.4.0-mswin.exe
Also, I won''t be able to make the installer until this weekend. My 32
hours
per day are already booked for the remainder of this week!  ;-)

Curt

Hmmm... if possible, I''d like to attach some sort of
"preview" postfix
so people don''t get the wrong idea.

Nick


Curt Hibbs wrote:
>What version number do you want to use for the release? I was thinking 0.4.0
>since its not that far off from wxRuby. If so then I would name my release
>installer:
>
>wxruby-swig-0.4.0-mswin.exe
>
>Curt
>
>  
>
>>-----Original Message-----
>>From: wxruby-users-bounces@rubyforge.org
>>[mailto:wxruby-users-bounces@rubyforge.org]On Behalf Of Nick
>>Sent: Wednesday, October 06, 2004 6:14 AM
>>To: General discussion of wxRuby
>>Subject: Re: [Wxruby-users] wxruby-swig on Windows & possible
release
>>
>>
>>
>>It built fine on the Mac, and has been tagged as v_MSW_PREVIEW.
We''re
>>good to go.
>>
>>Nick
>>
>>Curt Hibbs wrote:
>>
>>    
>>
>>>Ok, I''ve got a working build of wxruby-swig. Whenever you
are
>>>      
>>>
>>ready, label
>>    
>>
>>>the cvs repo for the release and I''ll build a windows
installer.
>>>
>>>Curt
>>>
>>>Curt Hibbs wrote:
>>>
>>>
>>>      
>>>
>>>>Nick wrote:
>>>>
>>>>
>>>>        
>>>>
>>>>>>Curt Hibbs wrote:
>>>>>>
>>>>>>
>>>>>>            
>>>>>>
>>>>>>>I''m trying to build wxruby-swig on windows
with the idea of
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>building a
>>>>
>>>>
>>>>        
>>>>
>>>>>>>windows installer for it. I think that this would go
a long
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>way toward
>>>>
>>>>
>>>>        
>>>>
>>>>>>>encouraging windows developers to try out
wxruby-swig. What
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>do you think?
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>>>>Are we far enough along to contemplate a release?
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>I think that''s a great idea. Nick knows better
than I how close we are
>>>>>>to a wxruby-swig release right now.
>>>>>>
>>>>>>
>>>>>>            
>>>>>>
>>>>>Honestly, I was considering it too, and I have no objections
as
>>>>>long as we have a way to
>>>>>say "this isn''t ready for primetime".
>>>>>
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>>>>Anyway, is there any objection to my modifying and
checking
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>in rakemswin.rb
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>>>>for vc++ 7.1.? Or, should I leave it as is and
create a new
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>one (like
>>>>
>>>>
>>>>        
>>>>
>>>>>>>rakemswin7.rb)?
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>Can a single rakemswin.rb automatically detect 7.1 and
do the right
>>>>>>thing? If so, I think that would be best.
That''s the beauty of
>>>>>>rake--full power at build time!
>>>>>>
>>>>>>
>>>>>>            
>>>>>>
>>>>>Actually, I don''t think anybody changes the
RUBY_PLATFORM
>>>>>variable to effectively
>>>>>discern the difference between MSVC 6.0 and 7.1. I say make
the
>>>>>change with some
>>>>>docs around it. There are some things that need to be added,
like
>>>>>being able to switch
>>>>>between DEBUG and RELEASE via command line options, and
maybe we
>>>>>merge the
>>>>>changes together. In any event, non-hackers will probably
use the
>>>>>extconf.rb build
>>>>>system instead.
>>>>>
>>>>>
>>>>>          
>>>>>
>>>>It should be possible to pick options that will work in both
>>>>        
>>>>
>>6.0 and 7.1.
>>    
>>
>>>>I''ll see what I can do.
>>>>
>>>>Curt
>>>>
>>>>_______________________________________________
>>>>wxruby-users mailing list
>>>>wxruby-users@rubyforge.org
>>>>http://rubyforge.org/mailman/listinfo/wxruby-users
>>>>---
>>>>Incoming mail is certified Virus Free.
>>>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>>>Version: 6.0.769 / Virus Database: 516 - Release Date: 9/24/2004
>>>>
>>>>
>>>>
>>>>        
>>>>
>>>_______________________________________________
>>>wxruby-users mailing list
>>>wxruby-users@rubyforge.org
>>>http://rubyforge.org/mailman/listinfo/wxruby-users
>>>
>>>
>>>
>>>
>>>
>>>      
>>>
>>_______________________________________________
>>wxruby-users mailing list
>>wxruby-users@rubyforge.org
>>http://rubyforge.org/mailman/listinfo/wxruby-users
>>---
>>Incoming mail is certified Virus Free.
>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>Version: 6.0.769 / Virus Database: 516 - Release Date: 9/24/2004
>>
>>    
>>
>
>_______________________________________________
>wxruby-users mailing list
>wxruby-users@rubyforge.org
>http://rubyforge.org/mailman/listinfo/wxruby-users
>
>
>
>  
>

Nick wrote:
>
> Hmmm... if possible, I''d like to attach some sort of
"preview" postfix
> so people don''t get the wrong idea.
>
> Nick
Well from that perspective, how about:

   wxruby-swig-preview_1-mswin.exe

A subsequent release can =1 the preview number, and when we are ready to
replace the legacy wxruby  we can just call it wxruby using whatever the
next wxruby release number would be. I like this!

What do you think?

Curt

> Curt Hibbs wrote:
>
> >What version number do you want to use for the release? I was
> thinking 0.4.0
> >since its not that far off from wxRuby. If so then I would name
> my release
> >installer:
> >
> >wxruby-swig-0.4.0-mswin.exe
> >
> >Curt

Works for me. I say ship it!

Nick

Curt Hibbs wrote:
>Nick wrote:
>  
>
>>Hmmm... if possible, I''d like to attach some sort of
"preview" postfix
>>so people don''t get the wrong idea.
>>
>>Nick
>>    
>>
>
>Well from that perspective, how about:
>
>   wxruby-swig-preview_1-mswin.exe
>
>A subsequent release can =1 the preview number, and when we are ready to
>replace the legacy wxruby  we can just call it wxruby using whatever the
>next wxruby release number would be. I like this!
>
>What do you think?
>
>Curt
>
>
>  
>
>>Curt Hibbs wrote:
>>
>>    
>>
>>>What version number do you want to use for the release? I was
>>>      
>>>
>>thinking 0.4.0
>>    
>>
>>>since its not that far off from wxRuby. If so then I would name
>>>      
>>>
>>my release
>>    
>>
>>>installer:
>>>
>>>wxruby-swig-0.4.0-mswin.exe
>>>
>>>Curt
>>>      
>>>
>
>_______________________________________________
>wxruby-users mailing list
>wxruby-users@rubyforge.org
>http://rubyforge.org/mailman/listinfo/wxruby-users
>
>
>
>  
>

Curt Hibbs wrote:
> Well from that perspective, how about:
> 
>    wxruby-swig-preview_1-mswin.exe
> 
> A subsequent release can =1 the preview number, and when we are ready to
> replace the legacy wxruby  we can just call it wxruby using whatever the
> next wxruby release number would be. I like this!
I like it too.

Kevin

Sorry to be holding things up - work came up again.

I''m having some trouble making a new Mac installer. The problem comes 
from the interaction between the OS X installer and the various rubies 
of OS X. It may take a few days for me to come up with a wxuby-swig 
installer for OS X. Should I just release Curt''s build in the meantime?

In good news, I''ve checked in my patches for wxruby regarding the 
missing XRC and static methods. It''s been tested on OS X and Win32, so 
I''ll wait for Kevin''s ok before tagging anything.

Nick


Nick wrote:
>
> Works for me. I say ship it!
>
> Nick
>
> Curt Hibbs wrote:
>
>> Nick wrote:
>>  
>>
>>> Hmmm... if possible, I''d like to attach some sort of
"preview" postfix
>>> so people don''t get the wrong idea.
>>>
>>> Nick
>>>   
>>
>>
>> Well from that perspective, how about:
>>
>>   wxruby-swig-preview_1-mswin.exe
>>
>> A subsequent release can =1 the preview number, and when we are ready
to
>> replace the legacy wxruby  we can just call it wxruby using whatever
the
>> next wxruby release number would be. I like this!
>>
>> What do you think?
>>
>> Curt
>>
>>
>>  
>>
>>> Curt Hibbs wrote:
>>>
>>>   
>>>
>>>> What version number do you want to use for the release? I was
>>>>     
>>>
>>> thinking 0.4.0
>>>   
>>>
>>>> since its not that far off from wxRuby. If so then I would name
>>>>     
>>>
>>> my release
>>>   
>>>
>>>> installer:
>>>>
>>>> wxruby-swig-0.4.0-mswin.exe
>>>>
>>>> Curt
>>>>     
>>>
>>
>> _______________________________________________
>> wxruby-users mailing list
>> wxruby-users@rubyforge.org
>> http://rubyforge.org/mailman/listinfo/wxruby-users
>>
>>
>>
>>  
>>
>
> _______________________________________________
> wxruby-users mailing list
> wxruby-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wxruby-users
>
>
>

Nick wrote:
>
> Sorry to be holding things up - work came up again.
>
> I''m having some trouble making a new Mac installer. The problem
comes
> from the interaction between the OS X installer and the various rubies
> of OS X. It may take a few days for me to come up with a wxuby-swig
> installer for OS X. Should I just release Curt''s build in the
meantime?
I don''t think a few more days will make much difference. I''d
rather wait for
a single coordinated relapse.

Curt
> In good news, I''ve checked in my patches for wxruby regarding the
> missing XRC and static methods. It''s been tested on OS X and
Win32, so
> I''ll wait for Kevin''s ok before tagging anything.
>
> Nick
>
>
> Nick wrote:
>
> >
> > Works for me. I say ship it!
> >
> > Nick
> >
> > Curt Hibbs wrote:
> >
> >> Nick wrote:
> >>
> >>
> >>> Hmmm... if possible, I''d like to attach some sort of
"preview" postfix
> >>> so people don''t get the wrong idea.
> >>>
> >>> Nick
> >>>
> >>
> >>
> >> Well from that perspective, how about:
> >>
> >>   wxruby-swig-preview_1-mswin.exe
> >>
> >> A subsequent release can =1 the preview number, and when we
> are ready to
> >> replace the legacy wxruby  we can just call it wxruby using
> whatever the
> >> next wxruby release number would be. I like this!
> >>
> >> What do you think?
> >>
> >> Curt
> >>
> >>
> >>
> >>
> >>> Curt Hibbs wrote:
> >>>
> >>>
> >>>
> >>>> What version number do you want to use for the release? I
was
> >>>>
> >>>
> >>> thinking 0.4.0
> >>>
> >>>
> >>>> since its not that far off from wxRuby. If so then I would
name
> >>>>
> >>>
> >>> my release
> >>>
> >>>
> >>>> installer:
> >>>>
> >>>> wxruby-swig-0.4.0-mswin.exe
> >>>>
> >>>> Curt
> >>>>
> >>>
> >>
> >> _______________________________________________
> >> wxruby-users mailing list
> >> wxruby-users@rubyforge.org
> >> http://rubyforge.org/mailman/listinfo/wxruby-users
> >>
> >>
> >>
> >>
> >>
> >
> > _______________________________________________
> > wxruby-users mailing list
> > wxruby-users@rubyforge.org
> > http://rubyforge.org/mailman/listinfo/wxruby-users
> >
> >
> >
>
> _______________________________________________
> wxruby-users mailing list
> wxruby-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wxruby-users
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.775 / Virus Database: 522 - Release Date: 10/8/2004
>

What''s the status on this release now? Looking forward to trying it.

David

On Thu, 2004-10-14 at 08:13 -0500, Curt Hibbs wrote:
> Nick wrote:
> >
> > Sorry to be holding things up - work came up again.
> >
> > I''m having some trouble making a new Mac installer. The
problem comes
> > from the interaction between the OS X installer and the various rubies
> > of OS X. It may take a few days for me to come up with a wxuby-swig
> > installer for OS X. Should I just release Curt''s build in the
meantime?
> 
> I don''t think a few more days will make much difference.
I''d rather wait for
> a single coordinated relapse.
> 
> Curt
> 
> > In good news, I''ve checked in my patches for wxruby regarding
the
> > missing XRC and static methods. It''s been tested on OS X and
Win32, so
> > I''ll wait for Kevin''s ok before tagging anything.
> >
> > Nick
> >
> >
> > Nick wrote:
> >
> > >
> > > Works for me. I say ship it!
> > >
> > > Nick
> > >
> > > Curt Hibbs wrote:
> > >
> > >> Nick wrote:
> > >>
> > >>
> > >>> Hmmm... if possible, I''d like to attach some
sort of "preview" postfix
> > >>> so people don''t get the wrong idea.
> > >>>
> > >>> Nick
> > >>>
> > >>
> > >>
> > >> Well from that perspective, how about:
> > >>
> > >>   wxruby-swig-preview_1-mswin.exe
> > >>
> > >> A subsequent release can =1 the preview number, and when we
> > are ready to
> > >> replace the legacy wxruby  we can just call it wxruby using
> > whatever the
> > >> next wxruby release number would be. I like this!
> > >>
> > >> What do you think?
> > >>
> > >> Curt
> > >>
> > >>
> > >>
> > >>
> > >>> Curt Hibbs wrote:
> > >>>
> > >>>
> > >>>
> > >>>> What version number do you want to use for the
release? I was
> > >>>>
> > >>>
> > >>> thinking 0.4.0
> > >>>
> > >>>
> > >>>> since its not that far off from wxRuby. If so then I
would name
> > >>>>
> > >>>
> > >>> my release
> > >>>
> > >>>
> > >>>> installer:
> > >>>>
> > >>>> wxruby-swig-0.4.0-mswin.exe
> > >>>>
> > >>>> Curt
> > >>>>
> > >>>
> > >>
> > >> _______________________________________________
> > >> wxruby-users mailing list
> > >> wxruby-users@rubyforge.org
> > >> http://rubyforge.org/mailman/listinfo/wxruby-users
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > > _______________________________________________
> > > wxruby-users mailing list
> > > wxruby-users@rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/wxruby-users
> > >
> > >
> > >
> >
> > _______________________________________________
> > wxruby-users mailing list
> > wxruby-users@rubyforge.org
> > http://rubyforge.org/mailman/listinfo/wxruby-users
> > ---
> > Incoming mail is certified Virus Free.
> > Checked by AVG anti-virus system (http://www.grisoft.com).
> > Version: 6.0.775 / Virus Database: 522 - Release Date: 10/8/2004
> >
> 
> _______________________________________________
> wxruby-users mailing list
> wxruby-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wxruby-users
> 
-- 
David Mitchell
Software Engineer
Telogis

NOTICE:
This message (including any attachments) contains CONFIDENTIAL
INFORMATION intended for a specific individual and purpose, and
is protected by law.  If you are not the intended recipient,
you should delete this message and are hereby notified that any
disclosure, copying, or distribution of this message, or the
taking of any action based on it, is strictly prohibited.