I heard that Apple will ship Mac OS X Jaguar with Ruby.
Are there any plans for making this a well-rounded and integrated package?
I just thought that it might be good if Mac users from the Ruby
community would offer to give them advice on what to package with it
etc, so that people new to Ruby will find the right libs, and to improve
platform independence of Ruby programs (perhaps it should have a
similiar list as the PragProg installer).
I also think that it would be awesome if Apple worked on native GUI
toolkit for Ruby. (no AppleScript required)
I just thought that it might be good if Mac users from the Ruby
community would offer to give them advice on what to package with it
etc, so that people new to Ruby will find the right libs, and to improve
platform independence of Ruby programs (perhaps it should have a
similiar list as the PragProg installer).
The one thing I can’t get working is eRuby. mod_ruby works fine, but as I
have reported before on comp.lang.ruby, the httpd.conf line
I heard that Apple will ship Mac OS X Jaguar with Ruby.
I heard that it was going to be in the server version. This is the first
I’ve heard about the desktop version.
Are there any plans for making this a well-rounded and integrated package?
Apple is still making the videos available only to paying ADC members. I’d
like to hear from anyone who has seen them
I just thought that it might be good if Mac users from the Ruby
community would offer to give them advice on what to package with it
etc, so that people new to Ruby will find the right libs, and to improve
platform independence of Ruby programs (perhaps it should have a
similiar list as the PragProg installer).
I have very mixed feelings about the platform independence thing. The
positive aspects of platform independence are obvious. But I can’t help
feeling that Ruby won’t penetrate very far in the mac market until it’s a
macro language as well as a scripting language. Right now it leaves way to
much on the table. RubyAEOSA is a good start but it doesn’t really compare
with what’s available in Python, Perl and AppleScript. And that’s really sad
because syntactically and semantically Ruby is a nearly perfect macro
language.
I also think that it would be awesome if Apple worked on native GUI
toolkit for Ruby. (no AppleScript required)
You lost me a bit there. What’s missing from the C binding to Cocoa or even
Carbon/Core Foundation?
There is, nevertheless, a certain respect and a general duty of humanity
that ties us, not only to beasts that have life and sense, but even to
trees and plants. -Michel de Montaigne, essayist (1533-1592)
I just thought that it might be good if Mac users from the Ruby
community would offer to give them advice on what to package with it
etc, so that people new to Ruby will find the right libs…
agreed!!
are you offering to gather all of our suggestions and make them
available to apple
as one complete list, or are you suggesting we just individually contact
them?
i think it would be great if there were a more organized os x/darwin
ruby community.
in any case, i think one person should compile all of our suggestions
into one list and send it
off to apple as a cohesive whole. i would be only too glad to volunteer.
also, would any body care to host an os x ruby web site, i would
volunteer to do all the front end.
A friend of mine has started building his own blogging software, called
Burger, with Ruby. You can read his blog report at http://tesugen.com:80/cgi-bin/blosxom/2002/Jun/28#burger, including code
snippets. It’ll be really nice to be able to write templates using Ruby!
You could add something like #{“HOORAY!!!” if (Time.now.month = 9 &&
Time.now.day = 4)} for an automatic Hooray on you birthday!
···
Urban Nilsson, Oops AB
“My inbox is a sacred shrine, none shall enter that are not worthy.”
–Ted.Dziuba
I just thought that it might be good if Mac users from the Ruby
community would offer to give them advice on what to package with it
etc, so that people new to Ruby will find the right libs…
agreed!!
are you offering to gather all of our suggestions and make them
available to apple
as one complete list, or are you suggesting we just individually contact
them?
Why not do both. We can still submit feedback at Feedback - macOS - Apple. An organized list might get attention
too. We have to be a little careful though. Apple hasn’t announced a
decision to preload Ruby in the desktop version.
i think it would be great if there were a more organized os x/darwin
ruby community.
in any case, i think one person should compile all of our suggestions
into one list and send it
off to apple as a cohesive whole. i would be only too glad to volunteer.
The people who have authorized access to those pre-release builds
should be the only one contacting Apple about what is or is not
on those pre-release, non-disclosure builds. The fact that “some
little bird” is chirping somewhere does not guarantee that ruby
will be in the final public release.
···
At 1:13 PM +0900 6/30/02, ccos wrote:
I just thought that it might be good if Mac users from the Ruby
community would offer to give them advice on what to package
with it etc, so that people new to Ruby will find the right libs…
agreed!!
are you offering to gather all of our suggestions and make them
available to apple as one complete list, or are you suggesting
we just individually contact them?
–
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
are you offering to gather all of our suggestions and make them
available to apple
as one complete list, or are you suggesting we just individually contact
them?
You could submit your suggestions on
i think it would be great if there were a more organized os x/darwin
ruby community.
in any case, i think one person should compile all of our suggestions
into one list and send it
off to apple as a cohesive whole. i would be only too glad to volunteer.
You could set up a page on the Wiki, then send them the URL; or open a
section on
A friend of mine has started building his own blogging software, called
Burger, with Ruby. You can read his blog report at http://tesugen.com:80/cgi-bin/blosxom/2002/Jun/28#burger, including code
snippets. It’ll be really nice to be able to write templates using Ruby!
You could add something like #{“HOORAY!!!” if (Time.now.month = 9 &&
Time.now.day = 4)} for an automatic Hooray on you birthday!
Your friend may want to look at PageTemplate to handle the templating. It
seems very applicable to the idea of building blogs.
-pate
···
On Fri, 28 Jun 2002, Urban Nilsson wrote:
Urban Nilsson, Oops AB
“My inbox is a sacred shrine, none shall enter that are not worthy.”
–Ted.Dziuba
On Fri, Jun 28, 2002 at 11:10:09PM +0900, Urban Nilsson wrote:
A friend of mine has started building his own blogging software,
called Burger, with Ruby. You can read his blog report at http://tesugen.com:80/cgi-bin/blosxom/2002/Jun/28#burger, including
code snippets. It’ll be really nice to be able to write templates using
Ruby!
You could add something like #{“HOORAY!!!” if (Time.now.month = 9 &&
Time.now.day = 4)} for an automatic Hooray on you birthday!
The people who have authorized access to those pre-release builds
should be the only one contacting Apple
No.
about what is or is not
on those pre-release, non-disclosure builds. The fact that “some
little bird” is chirping somewhere does not guarantee that ruby
will be in the final public release.
I do not see this point at all.
Obviously, people should not reference any leaked info, but anyone is
free and encouraged to submit Ruby related wishes, suggestions,
requests, and tips for features of future versions of Mac OS to Apple, at
Nothing wrong with that.
“Please include Ruby in the Desktop version”, or “If you include Ruby,
then it would be great to package it with X and Y”, or even “I heard
that you are interested in Ruby. We are a group of Ruby enthusiasts, and
want to make sure that if you ship Ruby with Mac OS X, your users will
have a smooth experience, so here’s a list of suggestions: …”
I think that’s just Fujimoto being conservative. Maybe I’ll discover a flaw
with his implementation as I use it more, but I think it’s more of a comment
on the rapid evolution of Ruby. I haven’t seen a performance difference
between the bindings to Cocoa and the ones to Fx or Qt.
Ruby AEOSA, on the other hand, works but needs to be more convenient. People
in the workflow business just can’t be expected to look up 4 letter codes.
There needs to be a way to use the dictionary vocabulary directly. Apple
could be of great help here by open sourcing Script Editor or even
publishing the tricky bits as sample code.
I have read on their Project Builder list that they intend at some point to
have a public interface for adding languages to PB. As I think of it, that
might work as well.
Apple could help turn this into a fully solid kit.
–
There is, nevertheless, a certain respect and a general duty of humanity
that ties us, not only to beasts that have life and sense, but even to
trees and plants. -Michel de Montaigne, essayist (1533-1592)
if you have stuff you’d like to see for os x, you
can post it up here:
the page is linked to from the RubyOnMacintosh WIKI page as well:
from the page:
"This is a place where you can state what you would like to see
implemented for future versions of Mac OS X.
Add your request to the list below. Once the list gains some weight we
can send it off to Apple as representative of the desires of the Mac
Ruby Community. Whether Apple takes notice or not, we can use this list
as a starting point for organizing our own support community. "
it’s a wiki, so if you’d like to add/subtract something please feel free.
_c
hey there,
thanks, don’t know why the thought hadn’t crossed my mind before.
i think the mind often glides right by the simplest solutions. too good
to be
true it says.
regards,
c
p.s. i also made a link to the RubyOnMacintosh page from the WIKI home
page.
i’ll be trying to link from other sites across the web as well just to
get the ball rolling.
do you know if there are any ruby mac resources in japanese? it might be
an idea
to get a bit of cross cultural fertilization happening, or at least get
some cross linkage happening.
And I’ve written some classes to work with Cherry Blosxom, making it dead
simple to build “sidebar” content areas. I’m looking to clean up the code,
then decide how or if to turn it loose.
Ruby AEOSA, on the other hand, works but needs to be more convenient. People
in the workflow business just can’t be expected to look up 4 letter codes.
There needs to be a way to use the dictionary vocabulary directly.
I’m sure Apple would appreciate it if you would share your views,
insights, and suggestions with them, so that they can offer a smooth
Ruby experience to their users.
(I didn’t yet have a chance to use OSX)
