In the server I see that the locale.default is: es,ES,
I open a client and look in “Application Preferences” > “Locale” and I see: English (United States).
I believe that it should say spanish (Spain) or espaM-qol (EspaM-qa).
If you think this is not a bug, could you please explain why and how you can set the locale of the clients in the server.
I can’t reproduce the problem. I’ve set es,ES, on a Servoy Server (not Developer acting as a server) and it works perfect.
I did the test with the server and I re-did the test this moring: I can reproduce the bug.
I’m using:
Servoy version R2 2.1beta4-build 302, repository version 22
JDK Information
java.vm.name=Java HotSpot™ Client VM
java.vm.version=1.4.2_03-b02
java.vm.info=mixed mode
java.vm.vendor=Sun Microsystems Inc.
Operating System Information
os.name=Windows 2000
os.version=5.0
os.arch=x86
Repository on Oracle9i.
What can I do to help you reproduce the bug?
I was actually mistaken in my previous post. On the server adminstration screen you configure the locale for the server. The client will by default use the locale defined on the client’s operating system. Once a client makes a change in the servoy client preferences this preference will be stored locally.
Is there a method that can set the locale of the client?
I would like this feature very much: to be able to set the locale using a script within the solution.
Will this be possible?
why would you do that?
i would hate that if a program just sets my locale to something else that i specified. For example if you constantly try to set the locale to dutch… I never want dutch only english.
Besides that a locale change in the middle solution (or loading of a solution) isn’t really possible because to fully initialise the new locale you have to restart.
I want to be able to set the locale in the client because the client’s OS doesn’t have the right locale.
Their default is “es,ES,” but they want “es,Mx,” which is essentially the same except for the decimal symboly which is a dot instead of a coma. That way they can use the numeric key pad the enter the decimal point.
I would like to avoid having someone going from desktop to desktop to change the locale from “es,ES,” to “es,MX,”.
By the way, what is the purpose of having a locale on the server if it doesn’t change the setting on the client? What is it for?
the server could be also be in a wrong locale. For example when connecting to the database, especially when using dates ect.
Therefor there is that locale setting. Most of the time you don’t have to touch it.
We still think that servoy should honor the default locale setting of the clients machine the first time. After that the user can change it to what ever they want.
We still think that servoy should honor the default locale setting of the clients machine the first time. After that the user can change it to what ever they want.
I think that the developer should be able to customize every aspect of the aplication (set locale, restrict access to menus in menubar, etc..).
The developer doesn’t make the rules.
The rules comes from the boss/client and if the boss/client doesn’t want the employees to have access to xyz or to do xyz I believe that the developer should be able to say: “I can do it!” and complie with the requirements.
I don’t like to be obliged to say to my boss/client: sorry I can’t do that, the user has to be able to change/do xyz!
Just my opinion.
there is no change of how it works. Just how it looks.
If there is a case that a solution does have a different behaviour because of a locale setting that this is a bug (from servoy itself or the solution developer)
Once a client makes a change in the servoy client preferences this preference will be stored locally
What does this mean? Does it mean something is stored on the computer where the client is run?
What if a user works everyday on a different machine by default (like many callcentres operate)?
Paul
Settings like dialog/window sizes. Locale settings and other preference things are stored locally.
There is no such thing as remote properties (except ofcourse default) Because the properties are read long before a users logs in (if he/she logs in)
So, if the user is on a different machine every day, he/she has to reconfige the solution daily to his/her preferences?
Not too happy about that…
Paul
what kind of preferences should he or she change all time in youre eyes?
Sizes and positions can only be stored on local computer because of different screen sizes.
And other things like services (like 2 way socket preference on the client) is really a setting specific for a machine.
Locale settings are stored at windows level (the default one)
So what setting would you change everytime?
Depends which settings are stored on the local machine offcourse…
Formsizes are partially dependent on the Displaysize, but if you use many dialogs in your app and the user has to put them in the preffered place/resize them everytime when he/she switches machine, I would think this would be quite anoying.
Paul