[news.eclipse.technology.ercp] Re: ConstrainedText questions

["Gorkem Ercan" <gorkem.ercan@xxxxxxxxxxxxxxxx>]

I think it should be up to the platform specific implementation of eSWT to 
decide on the allowed characters. There are two reasons for that, first the 
users of a platform are already familiar with  the usage. And also this way 
we utilize the native components better.
--
Gorkem

"Mark Rogalski" <rogalski@xxxxxxxxxx> wrote in message 
news:e66s9l$9vp$1@xxxxxxxxxxxxxxxxxxxx
> Part of the purpose of this widget is to prevent the user from entering 
> invalid data without requiring the app to do input validation itself.  As 
> such, when a user is asked to enter a phone number he is likely to want to 
> enter locale specific "white space" characters. However, there is also the 
> chance that he'll want to enter an "out of country" phone number. 
> Therefore, I think all possible valid phone number characters should be 
> allowed regardless of locale.
>
> For Hyperlink, you are right that a phone number is set to the widget in 
> plain form and then displayed in a locale specific manner.
>
> But the initial question is still unanswered... Should we allow  ( ) - / 
> to be entered?
>
>
>
> "Gorkem Ercan" <gorkem.ercan@xxxxxxxxxxxxxxxx> wrote in message 
> news:e63vb3$sug$1@xxxxxxxxxxxxxxxxxxxx
>>I think the allowed characters are very much platform/device specific
>> since the allowed characters may differ on different locales
>> I think it is best to rely on the devices which are presumably optimized 
>> for a specific locale would provide the best character set.
>>
>> Displaying a phone number in Hyperlink is very much locale specific as 
>> well.
>> For example, even the data at hand do not have it, platform can put 
>> brackets around the area code for some locales while presenting it.
>>
>> Of course if  the underlying platform does not provide such native 
>> support then it may become a tedious job to trying to accomodate all
>> different locales but then this is still an implementation specific 
>> effort and should not affect other implementations.
>> --
>> Gorkem
>>
>> "Mark Rogalski" <rogalski@xxxxxxxxxx> wrote in message 
>> news:e5msdu$b1c$1@xxxxxxxxxxxxxxxxxxxx
>>> It seems the ConstrainedText PhoneNumber style does not allow a few 
>>> "white space"  characters which are typically used for North American 
>>> phone numbers. These are "(", ")", and "-". They have no meaning for 
>>> dialers but are almost always used to make reading a number easier. The 
>>> Hyperlink widget does display these characters. I think for consistency 
>>> and usability we should add these as valid characters for 
>>> ConstrainedText PhoneNumber style.
>>>
>>> Also, less of an issue but still something that we should consider, is 
>>> that a user may wish to use "white space" numeric separators like "," in 
>>> the ConstrinedText Numeric and Decimal styles. For instance, 
>>> "123,456.78". What do you think about this?
>>>
>>
>>
>
>