I don't know if it makes a difference or not, since I haven't been
following the 1.8.2 developments. But if there were any significant
changes in the Ruby 1.8.2 header files, it could potentially break
FXRuby, and other extensions, for that matter.
The only reason for having minor numbers is that they are binary
compatible. I hope the core ruby team members know that they are
responsible to garantee this.
···
--
Best regards, emailto: scholz at scriptolutions dot com
Lothar Scholz http://www.ruby-ide.com
CTO Scriptolutions Ruby, PHP, Python IDE 's
> I have uploaded a release candidate for Ruby Installer that
was built using
> the stable snapshot of the Ruby CVS dated 2004-06-30 (yes,
that *is* today).
> While this snapshot is not an official release of Ruby, it
has been reported
> that many Ruby bugs have been fixed. I have also updated a
few extension
> packages to their latest release.
Couldn't you wait 2 more weeks! There is a deadline from matz on
7-july-2004 for the next official 1.8.2 release and about 1 week later
the offical 1.8.2 release or one more release candidate is expected.
I wasn't aware of that. Its unlikely that I would post the final version
before then, so if the official release comes out I would definitely use it.
"Curt Hibbs" <curt@hibbs.com> wrote in message
news:<EAENKKNOJPMNCDMLDOMLOEPPENAA.curt@hibbs.com>...
> I have uploaded a release candidate for Ruby Installer that was
built using
> the stable snapshot of the Ruby CVS dated 2004-06-30...
<snip>
Excellent! I'd like to note that win32ole seems to play nicer with
1.8.2 RC2, even though I was using the latest win32ole (0.5.5) with
1.8.1. Segfaults I was seeing with 1.8.1 have (seemingly)
disappeared, though I'll keep testing.
RC3 adds back the missing support for OpenGL. There were no other changes,
so if you don't need OpenGL, then you don't need to download RC3.
Curt
···
-----Original Message-----
The original release candidate that I posted earlier today did not include
FXRuby. I just posted release candidate 2 which corrects this.
Curt
> -----Original Message-----
>
> I have uploaded a release candidate for Ruby Installer that was
> built using
> the stable snapshot of the Ruby CVS dated 2004-06-30 (yes, that
> *is* today).
> While this snapshot is not an official release of Ruby, it has
> been reported
> that many Ruby bugs have been fixed. I have also updated a few extension
> packages to their latest release.
>
> NOTE: I currently have very little free time, so I intend to move this
> quickly to a final release (possibly within a week) unless
> someone reports a
> very serious problem with this release candidate.
>
> You can download this release candidate from:
>
> http://rubyinstaller.rubyforge.org/
>
> You can check for reported problems (or report new problems) at:
>
> http://rubyforge.org/tracker/?group_id=167
>
>
> What is the Ruby Installer for Windows?
> ---------------------------------------
>
> The Ruby Installer for Windows is a "one-click", self-contained Windows
> installer that contains the Ruby language itself, dozens of popular
> extensions and packages, a syntax-highlighting editor and execution
> environment, and a Windows help file that contains the full text of the
> book, "Programming Ruby: The Pragmatic Programmer's Guide".
>
>
> Change Log for 1.8.2-14
> -----------------------
> - This is a build of the 1.8.2 stable snapshot
> of Ruby dated 2004-06-29. Many Ruby bugs have
> been reported fixed since the official 1.8.1
> release.
> - Fixed a typo in a windows registry entry
> (bug 643).
> - Upgraded Expat to version 1.95.7
> - Upgraded Ruby-odbc to version 0.993
> - Upgraded FXRuby to version 1.0.29
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.699 / Virus Database: 456 - Release Date: 6/4/2004
>
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.699 / Virus Database: 456 - Release Date: 6/4/2004
Is it possible to use a schema like python for adding information to
the registry about installed ruby versions. Every tool writer (like
me) needs this to detect the core library etc and also installer
programs for libraries should use it to install there stuff in the
right ruby directory.
"InstallPath", and "Help\Main Python Documentation"
The later one would be the pragmatic programmer *.chm file.
It would be a great help if we could do the same.
What's your oppinion about this ?
This is fine with me. When there are multiple versions installed, there also
needs to be a pointer to the default installation (the one that is on the
path). wxRuby currently uses this to decide where to install itself.
Is there anyone out there (other than wxRuby) that is using the current
registry schema?
How's this look (as an example relative to "HKEY_LOCAL_MACHINE\SOFTWARE"):
It was a typo that I thought I corrected -- I will check again.
The separation was partially inherited, and partially a quick hack to get
things working. There are quite a few cleanup activities that I want to
persue for the building of the installer, itself, but they will have to
wait -- I just don't have the extra time right now.
Curt
···
nobu.nokada@softhome.net wrote:
Hi,
At Thu, 1 Jul 2004 04:45:43 +0900,
Curt Hibbs wrote in [ruby-talk:104934]:
> You can check for reported problems (or report new problems) at:
>
> http://rubyforge.org/tracker/?group_id=167
Though I don't know why you separate directories devel and
stable, ruby.nsi in the former sets a registory
"\\HKLM\software\www.ruby-lang.orgy\InstallVersion", instead of
"\\HKLM\software\www.ruby-lang.org\InstallVersion".
I’m pleased to announce the kickoff of RubyForge project called “Why
Ruby?”
whose goal is to help spread the use of ruby by providing a central
repository of presentations, papers and advice on promoting Ruby.
Please visit (and contribute to) our site:
Are you looking for technical articles (introductions to the language),
or less technical advocacy pieces?
Just a reminder: ruby-doc.org [0], the home site for the Ruby
Documentation Project (now in its second smash year!) continues its
long-standing offer to host any and all Ruby documentation, be it
promotional, technical, API, how-to, or whatever.
So, if something may not be a good fit for Why Ruby?, it always has a
home on ruby-doc.org.
Yes! I should be more explicit about this on the Why Ruby site…
The primary focus of Why Ruby is advocacy and presentation materials, while
ruby-doc’s focus is on documentation for the practicing Ruby developer. They
server a complimentary purpose.
Some of the markup on that page is being rendered literally. This is
what I see:
If this is your first visit here, please click on Preferences above
to register so that your name can be associated with your changes and
contributions.
Thanks for pointing this out – I did this at 3am when I was probably too
tired!
It might look better if this wiki was written in Ruby. Instiki is quite good.
I love Instiki, and use it on all of my personal machines.
Unfortunately, its really not appropriate to use on RubyForge. Because it
uses Object Prevalence (via Madeleine), this means that the entire wiki is
resident in memory at runtime. This may be alright for a single server, but
for a community resource like RubyForge that hosts many hundreds of projects
(and potentially as many wikis), using Instiki would be too much of a drain
on its system resources.
It might look better if this wiki was written in Ruby. Instiki is quite good.
That’s a really nice find! I had been looking for a slim wiki that works
with Apache and MySQL, since I just need it as a local workspace (todo
lists, notes, articles, text dump, etcetera). Instiki meets all of my
requirements. Thanks for the tip!
A minor misunderstanding…
I like insticki, too, but that recommendation was text I was quoting
from the “Why Ruby” page, http://whyruby.rubyforge.org, just to show the
markup problems.
Are you looking for technical articles (introductions to the
language), or less technical advocacy pieces?
Just a reminder: ruby-doc.org [0], the home site for the Ruby
Documentation Project (now in its second smash year!) continues its
long-standing offer to host any and all Ruby documentation, be it
promotional, technical, API, how-to, or whatever.
So, if something may not be a good fit for Why Ruby?, it always has a
home on ruby-doc.org.
Here’s an idea. How about a wiki for Wanted/Requested Libraries?
Most of the time I had to use good ol’ Perl instead of Ruby is because
of libraries. CPAN is so complete, while Ruby still trails quite
behind (not just behind Perl, Python too). Several personal examples of
mine:
a fast/C-based buffer XOR (last time I checked there are several libs
to do bitwise operation but strangely none can XOR two string buffers);
diff algorithms (there are several in Perl);
interacting with subversion (there are already several SVN::* Perl
modules showing up in CPAN);
The Requested Libraries wiki could let people tell what modules they
need, and let other people vote too what they would like to see most.
Then yet some other looking for projects will know what is currently on
demand.
Are you looking for technical articles (introductions to the
language), or less technical advocacy pieces?
Just a reminder: ruby-doc.org [0], the home site for the Ruby
Documentation Project (now in its second smash year!) continues its
long-standing offer to host any and all Ruby documentation, be it
promotional, technical, API, how-to, or whatever.
So, if something may not be a good fit for Why Ruby?, it always has a
home on ruby-doc.org.
Here’s an idea. How about a wiki for Wanted/Requested Libraries?
Most of the time I had to use good ol’ Perl instead of Ruby is because
of libraries. CPAN is so complete, while Ruby still trails quite
behind (not just behind Perl, Python too). Several personal examples of
mine:
a fast/C-based buffer XOR (last time I checked there are several libs
to do bitwise operation but strangely none can XOR two string buffers);
diff algorithms (there are several in Perl);
interacting with subversion (there are already several SVN::* Perl
modules showing up in CPAN);
The Requested Libraries wiki could let people tell what modules they
need, and let other people vote too what they would like to see most.
Then yet some other looking for projects will know what is currently on
demand.
This is fine with me. When there are multiple versions installed, there also
needs to be a pointer to the default installation (the one that is on the
path). wxRuby currently uses this to decide where to install itself.
Is there anyone out there (other than wxRuby) that is using the current
registry schema?
How's this look (as an example relative to
"HKEY_LOCAL_MACHINE\SOFTWARE"):
I vote against it because it assumes that your installer is the only
one in the windows world. For example in the first month i shipped my
own ruby distribution with my IDE and maybe i will do this later again
when i target people at "download.com" or "winfiles.com" to try
another programming language. While the core should be the same, the
"site-lib" directory tree could be different.
"pp14" is a shortcut for "pragmatic programmers" or however you want
call it, maybe only 14 because this is the installer for the masses.
You see the problem in the python world where there is the www.python.org installer and then there exists also a few
"scientific" pythons and of course the one from ActiveState.
Think that my solution is a little bit more flexible, and its only a
few lines more for persons who use it/write it.
···
--
Best regards, emailto: scholz at scriptolutions dot com
Lothar Scholz http://www.ruby-ide.com
CTO Scriptolutions Ruby, PHP, Python IDE 's
Sure, I will apply this patch in the next Release Candidate (this could be a
few days, I'm recovering from a crashed system, plus I hope the 1.8.2 Ruby
release will be out soon).
Thanks,
Curt
Lothar Scholz wrote:
···
Hello Curt,
The Ruby Installer still conflicts with because the TCL_LIBRARY is set
to a value that python can't handle (python needs TCL 8.4).
I think this is a show stopper bug.
I really get angry every time i install Ruby and can't access "idle"
(which is Python's standard IDE) anymore.
Can you please patch the main function in rubys "main.c" file
until the tk maintainer fixes this in the right place.
As you see in the patch, when require 'tcltklib', environment variables
which starts 'RUBYTK_' replace to the one removed 'RUBYTK_' (e.g.
RUBYTK_TCL_LIBRARY --> TCL_LIBRARY).
If the target enviromnent variable already exists and the backup
variable does not exist (it means that to make backup is only once),
the backup variable are make (e.g. TCL_LIBRARY --> X_RUBYTK_TCL_LIBRARY).
Can it satisfy you?
--
Hidetoshi NAGAI (nagai@ai.kyutech.ac.jp)
Have you tried Ruwiki? It’s missing some of Usemod’s features, but it
wouldn’t take long to surpass Usemod with Ruwiki. It’s good stuff so
far.
No I haven’t.
I chose UseMod about two and a half years ago for the FreeRIDE wiki because
all of the Ruby-based wikis at that time were missing one essential feature:
tracking page revisions (with the ability to rollback to a previous
version). Since FreeRIDE was the first RubyForge project, all RubyForge
project wikis since then have just been UseMod, by default.
RubyForge is using an old version of UseMod, and if I was starting today I
would add one new basic requirement: ability to generate an RSS newsfeed.
