Hi,
I agree with all these good reasons.
This supports my previous recommendation.
Stephen
At 12:02 AM 6/6/2001 +0800, Gunther Birznieks wrote:
>I disagree in general with this. Having coded a lot of WML and HTML myself
>for a local mobile company, I can say pretty strongly that I do not believe
>in a 1-1 mapping between elements in WML and HTML except in a very loose
sense.
>
>You really have to code the whole template very separately for WML vs HTML
>and the choice you make (eg textfield vs textarea) is very different on WML
>vs HTML.
>
>So you would not want some generic Widget::TextField that rents a WML
>version for WML and HTML for HTML. It's quite possible that on web you may
>want to allow the user to type in a lot of info in textarea but on wap, you
>just restrict it a bit more.
>
>I think for most programmers, it will be easier to see HTML widgets and
>then dive in there and then plainttext widgets and WAP widgets etc as a
>substructure and then see when they are coding an HTML form what elements
>are available to them when they are doing so.
>
>Later,
> Gunther
>
|
