Date: 07/21/01
- Next message: Tarique Sani
email protected>>: "[phplib] BEA Weblogic (was) Re: [phplib] [RFC] Future of phplib" - Previous message: nathan r. hruby: "RE: [phplib] [RFC] Future of phplib"
- Next in thread: Richard Archer: "Re: [phplib] common document api vs templates"
- Reply: Richard Archer: "Re: [phplib] common document api vs templates"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I have not used templates, and do expect to get flammed, but the reason
evry body gives for using templates is to seperate idiot web page
designers
from the code. i can agree with that, but having to design the same
template
over ands over again for the flavor of the month mark up laguage seems a
waste of time too. there is currently 3 hand held device markup
languages and
from what ive read wap seems like its going to win but how many old
devices
are there still in use that dont understand wap. I would like to see a
common
document class that would handle what ever markup language the browser
can handle.
Yes this means mixing content and code, but maybe the solution is to
have the
mixed code / content be the template and use the updated content from
the web
designer to update the code / content page, then there web content could
be in
html, xml or whatever flavor of the month is, or there comftorble with.
call me old fashoin but if you dont need or have a gui being able to
look up
a phone number address whatever text from php-cgi using a ttyclass
document api
would be nice. and having this same page work when hit with html browser
work
and if they have javascript turned on then you can hit them with baners
ads
saying you may have already won click here.
and desinging multiple web sites for different browsers is going to be
more of
pain then its worth. Myself i brows with java off cookies off, and don't
use
any web sites that don't with that unless i absolutly have too. Iv'e
looked at
the source for some of these sites and theress so much code thats if
this browser
do this if that browser do that argggg thats the crap that should be in
a class.
then you could train the web designer to use a common simple api to
achive
what they want.
this works for me and is direction im going, but i only design
applications.
i make them work, then i make them fast, then if theres money left over
i make them
pretty, surprise most of my clients don't care about pretty, and if i
was paying
people to do data enty, run a busness do inventory why would i care if
the web app
was pretty, your already paying them to work, do we really need to
entertain them too.
but i would want the app to work with what ever hand held device i could
get for cheep
that would do the job, and not have to pay the develper to write another
web site for
that specific device. instead i would want the device to work with the
existing web app
/site maybe with some loss of prettiness but with is little loss of
functionaly as possible.
-- My opinions are my own and not that of my employer even if I am self employed Tech Net, Inc. --FREE THE MACHINES-- 651.224.2223 627 Palace Ave. #2 karner <email protected> karner <email protected> St. Paul, MN 55102-3517 www.tnss.com wanted : adsl/cable modem with static ip at reasonable price accept-txt: us-ascii,html,pdf accept-dat: ascii-delimited,sql insert statments-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Tarique Sani
email protected>>: "[phplib] BEA Weblogic (was) Re: [phplib] [RFC] Future of phplib" - Previous message: nathan r. hruby: "RE: [phplib] [RFC] Future of phplib"
- Next in thread: Richard Archer: "Re: [phplib] common document api vs templates"
- Reply: Richard Archer: "Re: [phplib] common document api vs templates"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

