Forum: Ruby on Rails Support Ruby(Rails) Growth

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Chris W. (Guest)
on 2009-04-07 01:17
Hey Ruby\Rails users, (like me)

I know that Prototype (*cough* "jQuery")is the library of choice for
most rails developers. When it comes to enterprise level apps and having
an extensive commercially supported library, you cannot beat ExtJS. If
you want a great case study, look at SalesForce.com and how they have
used ExtJS as their library of choice.

When I came across this poll today, I was shocked to see just how low
Ruby was voted on (only 40 votes). I don't post very often on forums,
but I could not help but to share this and hope that fellow Rails/Ruby
users will support it and vote.

Reload this Page  Most Popular Server-Side Languages
http://extjs.com/forum/showthread.php?t=43322

They have also just happened to (beta) release their new MIT Licensed
Ext Core. Which boasts some impressive features and majorly competes
with jQuery when looking for a core JS framework for websites.

http://extjs.com/blog/2009/04/04/ext-core-30-beta-released/

While I use jQuery for my website front-end, and will be very hard for
me to switch. When I think about the success of Ext Core, is that once
my customers graduate past a simple website, I know that the full ExtJS
3.0 is waiting for me. No longer do I have to worry about some small 3rd
party *jQuery* plug-in to do something my clients require. Gone is the
worry that they will update and develop for years their ‘project’
plugin. I can release my projects and be secure in my personal
reputation (and ability to support them for many years.)

Thanks all for supporting Rails (*Ruby)

Chris Westbrook
Roderick v. (Guest)
on 2009-04-07 17:15
Chris Westbrook wrote:
> I know that Prototype (*cough* "jQuery")is the library of choice for
> most rails developers. When it comes to enterprise level apps and having
> an extensive commercially supported library, you cannot beat ExtJS. If
> you want a great case study, look at SalesForce.com and how they have
> used ExtJS as their library of choice.

Yay for Ext JS. The concept of having a rich JavaScript client
application talking with a RESTful Rails application works very well for
back-end applications. I can heartily recommend everyone to try it.
SproutCore and Cappuccino are among the alternatives.

There's this little chicken-and-egg problem between Ext JS and Rails
where the two have different interpretations of RESTful resources.
Nothing that a little customization can't fix, but following Rails
tradition it'd be great if Ext JS was compatible out of the box.

--
Roderick van Domburg
http://www.nedforce.nl
Charles J. (Guest)
on 2009-04-07 18:45
(Received via mailing list)
On Tue, Apr 7, 2009 at 8:15 AM, Roderick van Domburg <
removed_email_address@domain.invalid> wrote:

>
> Yay for Ext JS. The concept of having a rich JavaScript client
> application talking with a RESTful Rails application works very well for
> back-end applications. I can heartily recommend everyone to try it.
> SproutCore and Cappuccino are among the alternatives.
>
> There's this little chicken-and-egg problem between Ext JS and Rails
> where the two have different interpretations of RESTful resources.
> Nothing that a little customization can't fix, but following Rails
> tradition it'd be great if Ext JS was compatible out of the box.

Of course, if the cost were the same as rails "out of the box" that
would be
even better.

Cheers--

Charles
Roderick v. (Guest)
on 2009-04-07 19:59
Charles J. wrote:
>> Yay for Ext JS. The concept of having a rich JavaScript client
>> application talking with a RESTful Rails application works very well for
>> back-end applications. I can heartily recommend everyone to try it.
>> SproutCore and Cappuccino are among the alternatives.
>>
>> There's this little chicken-and-egg problem between Ext JS and Rails
>> where the two have different interpretations of RESTful resources.
>> Nothing that a little customization can't fix, but following Rails
>> tradition it'd be great if Ext JS was compatible out of the box.
>
> Of course, if the cost were the same as rails "out of the box" that
> would be even better.

+1 on that one too. :-)

--
Roderick van Domburg
http://www.nedforce.nl
Chris W. (Guest)
on 2009-04-07 20:26
Roderick van Domburg wrote:
> Charles J. wrote:
>> Of course, if the cost were the same as rails "out of the box" that
>> would be even better.
>
> +1 on that one too. :-)
>
> --
> Roderick van Domburg
> http://www.nedforce.nl

It's a start, but the new beta just happens to be released as MIT
Licensed
"Ext Core".

http://extjs.com/blog/2009/04/04/ext-core-30-beta-released/

On that same note, those of you that have a hard time with RDoc, check
out the standard API Docs for ExtJS and Ext Core.

http://extjs.com/products/extcore/docs/

Even better, and not to hijack my own thread, but I started playing
around with the Documentation Generator and .... It works... Just find
yourself with the Ruby (*shakes head*) "=begins" and "=end".

I would say that this is a good "RDoc Alternative" for ruby code (And
JavaScript as well.)

http://code.google.com/p/ext-doc/
This topic is locked and can not be replied to.