I know it's wrong, but that panel widget makes me want a tiling window
manager <http://en.wikipedia.org/wiki/Tiling_window_manager> written in JS.

Given the amount of mindshare jQuery now has among Rails developers (a trend
which seems to correlate with dedication to Javascript), I wonder if we'll
see jQuery nudge its way into Rails as an optional replacement for
Prototype.

Not that it's necessary (aside: http://www.railsboost.com/templates/new will
allow you to generate a Rails template which includes jQuery), but a JS
analogue of `rails -d $myfavouriteRDBMS` seems increasingly appropriate.

Is YUI3 any more "streamlined" (in terms of feel / API) than YUI2 ?

On Sat, Oct 3, 2009 at 9:42 AM, Mark Mansour <[email protected]> wrote:

>
> Lachie, I think you've nailed it here
>
> > If you build web apps that feel at home on the web, it means special
> > something to people. Think GMail or flickr.
> > If you build a kick-arse Mac native app it means something special to
> > people, too. Think iPhoto, Tweetie or lots of others.
>
> I'm using the YUI library a lot and it is pretty hard to go past their
> widget set if you need a web *application*.  If you style your "heavy"
> widgets to look more modern and web native (rather than like a desktop
> app) then a lot of the prejudices fall away.  Most of the widgets I've
> come across appear heavy because they support all browsers and
> sometimes that means extra cruft in the DOM (i.e. div-itis) and a JS
> framework on which to build upon.
>
> YUI 2's native syntax is a bit long winded (they have a design goal of
> not polluting the global name space) but it pretty easy to make it
> look more jQuery-esque.
>
> > What I simply don't get are the 1/2 arsed attempts at shoehorning
> > desktoppy stuff into the web browser.
> >
> > Lightboxes are one thing but this
> >
> http://developer.yahoo.com/yui/examples/container/panel-resize_source.html
> > kind of thing is so WTF to me.
>
> Panel's are useful, but you don't have to use this stuff to emulate a
> desktop metaphor - just think of them as building blocks.
>
> Mark
>
> > :lachie
> > http://plus2.com.au
> > http://smartbomb.com.au
> > http://www.flickr.com/photos/lachie/
> >
> >
> >
> > On Fri, Oct 2, 2009 at 8:01 AM, Julio Cesar Ody <[email protected]>
> wrote:
> >>
> >> Or it's because "most", for pulling out of my ass values of most,
> >> Rails developers can't *really* use Javascript, hence it's easier to
> >> just get a set of pre-baked components to run (enough googling around
> >> and you can integrate Dojo/ExtJS/whatever) rather than writing
> >> something that addresses your specific case from scratch.
> >>
> >> You know, the old "I don't do front-end" adage. I know it's becoming
> >> popular these days, but there's still reminiscences of it apparently.
> >>
> >>
> >> On Fri, Oct 2, 2009 at 7:28 AM, Korny Sietsma <[email protected]>
> wrote:
> >>>
> >>> There's also the issue of bugs; these complex frameworks are not
> >>> without bugs, and debugging can be a world-of-pain.
> >>>
> >>> Upgrading your JS framework is also always tricky, and hard to justify
> >>> to whoever is paying the bills.  We had a complex project written a
> >>> couple of years ago using Dojo 0.4, and we attempted to upgrade to
> >>> Dojo 1.something - and gave up; the framework had changed at a
> >>> fundamental level, and upgrading would have been harder than
> >>> re-writing.
> >>>
> >>> - Korny
> >>>
> >>> On Fri, Oct 2, 2009 at 12:33 AM, Colin Campbell-McPherson
> >>> <[email protected]> wrote:
> >>>>
> >>>> I've been working on a project recently that makes a great deal of use
> >>>> of the YUI widgets, similar to those in dojo and exjs I believe. I'd
> >>>> avoid them in my own work (rails) mostly because I feel they quickly
> >>>> complicate the UI and make your application harder to use. My
> >>>> experience has also been that they're very difficult to get working,
> >>>> and where I going from the productivity of Rails to YUI I'd soon
> >>>> become frustrated and feel like I wasn't making any progress.
> >>>>
> >>>>
> >>>> On 01/10/2009, at 2:42 PM, Joshua Partogi wrote:
> >>>>
> >>>>>
> >>>>> Hi all,
> >>>>>
> >>>>> Please correct my false understanding about this. But from what I
> have
> >>>>> observed, lots of rails applications does not use fullblown
> javascript
> >>>>> widgets like extjs or dojo. Why is the tendency of rails apps only
> >>>>> rely on basic javascript framework like jquery or prototype? Or
> >>>>> perhaps to simplify it, why does your rails apps does not use extjs
> >>>>> (despite of the license) or dojo?
> >>>>>
> >>>>> Is anyone willing to share based on their experience? Thanks very
> much
> >>>>> for the insights.
> >>>>>
> >>>>> regards,
> >>>>>
> >>>>> --
> >>>>> Certified Scrum Master
> >>>>> http://blog.scrum8.com
> >>>>> http://twitter.com/scrum8
> >>>>>
> >>>>> >
> >>>>
> >>>>
> >>>> >
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Kornelis Sietsma  korny at my surname dot com
> >>> kornys on twitter/fb/gtalk - korny on wave sandbox
> >>> "Every jumbled pile of person has a thinking part
> >>> that wonders what the part that isn't thinking
> >>> isn't thinking of"
> >>>
> >>> >
> >>>
> >>
> >> >
> >>
> >
> > >
> >
>
>
>
> --
> Mark Mansour
> [email protected]
> http://agilebench.com/
>
> >
>


-- 
cheers,
David Lee

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to