Case Sensitivity?
3 views
Skip to first unread message
Alan
Nov 20, 2009, 2:38:58 PM11/20/09
to OMHE
Should OMHE commands be case insensitive? Right now our parser forces
everything to lowercase. Should a well-formed OMHE parser be case
insensitive? My vote/instinct says yes. Gets around annoying iPhone
auto capitalize feature.
Also I'll try to have an updated parser in subversion sometime over
the weekend. It will implement a subset of commands for now, but will
work w/ all the recent changes.
Alan
everything to lowercase. Should a well-formed OMHE parser be case
insensitive? My vote/instinct says yes. Gets around annoying iPhone
auto capitalize feature.
Also I'll try to have an updated parser in subversion sometime over
the weekend. It will implement a subset of commands for now, but will
work w/ all the recent changes.
Alan
Rob Williams
Nov 20, 2009, 2:44:27 PM11/20/09
to omhe_mic...@googlegroups.com
+1 on case insensitive.
Mark Scrimshire
Nov 20, 2009, 5:15:32 PM11/20/09
to omhe_mic...@googlegroups.com
I agree case insensitive is the way to go.
Automatic capitalization can be a challenge that can frustrate users.
While you are at it you may want to think about alternative syntax for certain symbols. The challenge I had with Tweetdeck was the insertion of a space after an @ sign. We may want to embed an alternate (ie optional) syntax. such as allow .AT. to be interpreted as @ may also want to cope with .DOT. in email addresses
eg. could I enter Mark.DOT.Scrimshire.AT.gmail.DOT.com
This might appease some of the geeks that might be uncomfortable with using email addresses in a format that can be harvested easily.
Automatic capitalization can be a challenge that can frustrate users.
While you are at it you may want to think about alternative syntax for certain symbols. The challenge I had with Tweetdeck was the insertion of a space after an @ sign. We may want to embed an alternate (ie optional) syntax. such as allow .AT. to be interpreted as @ may also want to cope with .DOT. in email addresses
eg. could I enter Mark.DOT.Scrimshire.AT.gmail.DOT.com
This might appease some of the geeks that might be uncomfortable with using email addresses in a format that can be harvested easily.
Alan
Nov 29, 2009, 4:31:41 PM11/29/09
to OMHE
Ok I think everyone agrees case sensitive is the way to go. I added it
the main spec.
So for special chars, should '.' be the marker or some other
character?
Just .AT. and .DOT.? Any others or other comments on this?
Parser still in very beta state. Glad to share, but we are still
hacking on it.
Alan
Alan
Dec 1, 2009, 1:01:19 PM12/1/09
to OMHE
Excuse me I meant case INSENSITIVE. The parser we're working on will
force everything to lower before processing.
force everything to lower before processing.
blue dot
Dec 2, 2009, 3:11:04 PM12/2/09
to OMHE
soundsGood
this will bring up a question of strings that might be payload in
future. probably need to find a way to exempt, if ever, so the
parser functions can send original. e.g. if we use it to add a
comment to a #pn=7comment="broke my wrist"
--mike
this will bring up a question of strings that might be payload in
future. probably need to find a way to exempt, if ever, so the
parser functions can send original. e.g. if we use it to add a
comment to a #pn=7comment="broke my wrist"
--mike
Alan
Dec 2, 2009, 3:20:40 PM12/2/09
to OMHE
So you're saying only OMHE command "names" are case insensitive and
the "values" are not. The value is the value. That seems most logical
to me.
Let's discuss the best way to represent comments and escaping. Maybe
start a thread? I think theres room for improvement.
-Alan
the "values" are not. The value is the value. That seems most logical
to me.
Let's discuss the best way to represent comments and escaping. Maybe
start a thread? I think theres room for improvement.
-Alan
Reply all
Reply to author
Forward
0 new messages