I’ve been working with rails for a while now. Rails is the second web
framework I’ve tried. It blows the doors off catalyst (perl’s best
framework). I even just wrote my first plugin (broomstick). Ruby’s
ability to meta-program blew me away with it’s ease of use. I’ve been
so impressed with the helpers that rails uses to make a lot of tasks
ridiculously easy, but of course rails isn’t perfect. That brings me to
my question.
What’s in your wishlist for rails?
My biggest wish is a queue system for rjs. Synchronous rjs call would
be great!
I’m really curious what everyone else is waiting to see!
I completely agree with better documentation and sample code, especially
coming from what PHP has to offer in that regards. Though I am just
beginning.
Thomas S. wrote:
Updated documentation that includes sample code, not just source code.
Hi, I would like to see the following on the wishlist:
o better documentation with code snippets
o better deployment mechanism for rails application… Mongrel???
Note: It took me 20 minutes or so to build an application but I
took me
3 times as look to deploy it.
Hi Joe, thanks for your post because I wasn’t sure if there was a
better mechanism. I’ll check with TextDrive.com to see if this is an
option for me. I’m looking for an easier deployment option(s) onto
Unix hosts.
Hi, I would like to see the following on the wishlist:
o better documentation with code snippets
o better deployment mechanism for rails application… Mongrel???
Deploying with mongrel is pretty easy:
$ sudo mongrel_rails start -p 80 -d -e production
(from memory)
More options (or more easier options) to deploy rails apps on Windows
for production. (I run Windows, so you will have to speak slowly.)
Particularly if you have existing Apache PHP installs. Oh, for added
complexity I develop on a mac. I have Apache, MySQL and PHP running
smoothly and consistently on both Windows and OS X. Ruby and Rails are
installed.
So I don’t know what path to take… replace apache with Lighttpd, then
get all my PHP stuff to work again (with a whole new config file to deal
with) or pass through Apache to mongrel.
Call me lame but I would love a Windows Mongrel installer (“point to
your existing Apache (or Lighttpd) install, now point to your rails app
directory”) etc. And a little control panel to show me Mongrel’s status,
logs and graceful restart, shut down or start would be groovy as well. I
know none of these are on anyone’s priority list… ans maybe it is too
early for this (took Apache for windows a while to offer this kind of
hand holding).
On Fri, Apr 28, 2006 at 01:32:08PM -0400, Charlie B. wrote:
What’s in your wishlist for rails?
I’m relatively new to Rails. My Rails wish list is pretty small, mainly
because almost every time I think of something I need I find that it’s
either already included in Rails or available as a
plugin/generator/engine.
So, here are a few items I’d wish for:
Ensure that new versions of Rails don’t break older Rails
applications.
Since I’m still working on my first Rails app I haven’t had a
problem
with this myself. But, I’ve seen enough posts about problems when
upgrading to newer versions of Rails to know it’s a problem for many
people.
Remove ALL frames from api.RubyOnRails.org, add a search
function,
and generate a PDF version for those who prefer printed
documentation.
Well, I was trying for a few items but could only think of a couple.
Rails
makes things so easy it’s tuff to think of things it needs.
You know, these are both pretty good suggestions. #1 I think has
become a priority for the core team, and #2 would be a pretty
worthwhile side project. If I had more time I might do it myself –
just download the API docs and feed them to PDF::Writer and Bob’s your
uncle.
Currently, if you have a 50 line rjs file, each line is sent to the
browser and executed as soon as the file is read. If you want each line
to wait until the previous line is finished you have to program in
delays. If there was a queue system you wouldn’t have to do this.
Fixing or replacing rdoc documentation on rails. No good searching
provided. Spotty
coverage. Terrible screen layout, everything is truncated on the right
or left. Ugly
colors. Sometimes you have to know the name of the thing you’re looking
for. Lousy
index. I am immensely grateful for rdoc’s existence but cannot help
but start grumbling
when I use it, whether for rails or anything else.
Mixing api docs with source code means the documentation writers need
write access to the
source code. Not every organization will want this. Maybe the rails
developers do.
Actually that post is not what I was talking about. Yes there are
visual effects queues, but not all rjs is visual effects. The queue
system you referenced is only available to visual effects.