Kartal Konut Projeleri ile ?stanbul Anadolu yakas?n?n en çok de?er kazanabilecek konutlar?n? sizlere sunmaktay?z. Sizler için yap?lan ara?t?rmalar neticesinde web sitemizde yer alan iskanl? konutlar? incelemenizi tavsiye ediyoruz. Bilgilendirmeler için 7 gün 24 saat ça?r? merkezimizde sizlerin ça?r?lar?n? beklemekteyiz.
Sevdikleriniz için ya?am?n önemini iyi biliyoruz bu yüzden en kaliteli mekanlarda en gözde mekanlar? sizler için derledik.
]]>So you are saying using jQuery and unobtrusive JS = ‘my legs are not working?’ Can’t really agree with that
I did a round-up on JavaScript litterature before christmas, unfortunately it’s in norwegian, but maybe google translate can help. Anyway, you could check out the links there.
]]>* Simulating even the most trivial things like $(’element’).toggle(); with RJS
In rjs it’s easier to test, easier to read, and less code to maintain.
* Using oberve_field for everything. The problem is that observe_field in it’s vanilla form sends a request to the server every time you hit a key. It’s easy to replace it with a bit of Javascript knowledge and stop hogging the bandwidth.
This one I mostly agree with, except premature optimisation is the root of all evil, so do it last. Why not submit a rails patch?
* Instead using Javascript functions like setInterval / setTimeout they are simulating the desired behavior with Prototype / RJS
Again, harder to test.
* Trying to create great AJAX sites without much clue about Javascript (and just minimal knowledge about Prototype/RJS - spending a week or so on #rubyonrails was enough to experience this in it’s full glory ‘hey plz help bro cuz Im new to AJAX’)
* Doing all of the above obtrusively - who cares about the totally littered HTML, just get it done somehow
Of course this isn’t a good idea. I think the generally better idea is to submit rails patches if you have more efficient ways of doing things.
]]>