I think we both would agree that someone here needs a paradigm shift, we just disagree about which one.
> Yup, but you're not the author of the rainbow core. If you've got some time you can have some chit chat
with the core team to discuss about localization
-- I only mentioned rainbow because you threw it out there as if I was not aware of it.
The fact that I did not write the core in no way diminishes my arguments.
If you think rainbow is the pinnacle of good design then use it.
>yes I choose a traditional way because the .NET way doesn't really solve the problem, only a small part of it.
3. Please learn alot, have some .NET articles would be good for you.
You can read this one to open your eyes:
-- that article is more of the same and does not address my points
> The way you think you do localization is actually not a localization, it's actually a string/text customization.
Localization actually beyond just changing label or text , it also affects Number format, Date Time Format,
Currency format ,etc.
-- date time and number formats have not been part of our discussion.
don't assume I don't understand those issues just because we have not discussed them.
>Based on that, Rainbow definitely supports localization while MojoPortal only supports string customization so
I'd suggest you that you can change the localization in the MojoPortal feature list in the HomePage with easy text
customization feature which I think more appropriate for MojoPortal now.
-- your opinion is duly noted here for all to see and make their own determination, I will keep my own counsel on this.
In my arguments I have stuck to the specific issues while you have thrown in subtle little insults such as suggesting
my thinking is like a "newby" and telling me I have a lot to learn.
You are free to think what you want as am I.
Everyone can always learn more including you.
I think you are overly enamoured with the .NET localization guidelines as are many others.
I say its works for Winforms and console apps but falls miserably short in web applications.
I follow the KISS principle and know from experience that anything you want to be able to change easily for a web application
should not be stored in a resource file.