| Re: preg_match() oddities and question [message #176108 is a reply to message #176105] |
Thu, 24 November 2011 07:20   |
Sandman
Messages: 32
Registered: August 2011
Karma:
|
Member |
|
|
In article <4778042(dot)ypaU67uLZW(at)PointedEars(dot)de>,
Thomas 'PointedEars' Lahn <PointedEars(at)web(dot)de> wrote:
>>>> It is at this point that most people that have an actual need to solve
>>>> these kinds of problems turn to the available commercial software and
>>>> decide to solve it with money instead of manpower.
>>>
>>> Where the question must be allowed: How came that the data has not been
>>> requested and stored in a structured form to begin with? That is, for
>>> example, why only an address field in a form – why not a street, house
>>> number aso. field?
>>
>> Convenience for the user, of course.
>
> You can't be serious.
I can :)
>> This is a form that says "Are you connected to the citynet?" and then
>> you just enter your address to search the database. If the user has to
>> provide street name, street number and street letter in separate
>> fields, it's inconvenient for them.
>
> No, it's not.
Actually, yes it is :)
> With separate controls they can be sure where to enter what;
> it is accessible, and you have no problem processing the data. With one
> control, neither applies.
Well, I have been doing this for about ten years now, and recived tons
of feedback from my clients on things like this. When I say it's
inconvenient for the end user, it's not something I make up on the
spot to be obnoxious.
Just like with my examples, I have a pretty clear picture of what
problem I need to solve. I find it curious that no one in CLP even
attempt to look at that, and instead trying to find other examples, or
claiming that the frontend should be changed.
Makes me think that you guys deem the examples I gave as unsolvable,
which of course I refuse to agree with. :)
No offense though.
--
Sandman[.net]
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]