﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Handling javascript localization in Mono Rail</title><description>Will,
  
My users are using MS CRM, obviously usability isn't a concern.
  
That is actually fitting in to the standard UI practices in the application, not an insult, I am more direct with those.
</description><link>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment5</link><guid>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment5</guid><pubDate>Mon, 08 Oct 2007 18:38:21 GMT</pubDate></item><item><title>Will Sahatdjian commented on Handling javascript localization in Mono Rail</title><description>Its 2007, your users deserve a higher level of usability than the obnoxious alert dialog.  For all the time spent coming up with beautiful APIs you should round out all those amazing dev skills.
  
  
http://clientside.cnet.com/code-snippets/event-scripting/confirmer-widget/
  
  
With a longer delay and a better color choice you have yourself a big improvement.
</description><link>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment4</link><guid>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment4</guid><pubDate>Mon, 08 Oct 2007 18:09:18 GMT</pubDate></item><item><title>Pedro Teixeira commented on Handling javascript localization in Mono Rail</title><description>clever idea! 
  
  
  
</description><link>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment3</link><guid>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment3</guid><pubDate>Mon, 08 Oct 2007 02:49:37 GMT</pubDate></item><item><title>Ayende Rahien commented on Handling javascript localization in Mono Rail</title><description>You get a null object if you mistype something, that about it.
  
I know that you did a lot of stuff with JS and strong typing, but I don't see the need for those in many many cases.
  
Debugging JS is very easy, usually requiring merely that I would be able to run the JS in FireBug.
  
Debugging JS in IE is to be avoided.
</description><link>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment2</link><guid>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment2</guid><pubDate>Sun, 07 Oct 2007 19:28:41 GMT</pubDate></item><item><title>Justin-Josef Angel [MVP] commented on Handling javascript localization in Mono Rail</title><description>The horrer.
  
It's not strongly typed! it's evil! 
  
This is string based reference - the anti christ! 
  
  
Seriously, anything gained in "easy globalzation" is lost in "oops, I changed the name of this file/group/field and everything compiled OK". 
  
Any managed code that's compiled to Javascript should be as strongly typed as possiable as javascript is far harder to debug then managed code. 
</description><link>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment1</link><guid>http://ayende.com/2843/handling-javascript-localization-in-mono-rail#comment1</guid><pubDate>Sun, 07 Oct 2007 19:17:21 GMT</pubDate></item></channel></rss>