Embedding php in html code?

[Ken Ward]

Hi All,

I'm a new boy to php and working on a web site with long sections of
code that could be done as includes apart from one or two things
changing.
I've tested the following and it works, but what I really want to know
is am I OK placing php code inside a html line like this, or could there
be problems?
<!-- html code for test.php -->
<!-- lot of code cut -->
<a href="<?php print $filename; ?>"><?php print $title; ?></a>
<!-- lot of code cut -->
<!-- end of test.php -->

<!-- which is called in the main file like this -->
<?php
$filename="inde x.php";
$title="Index Page";
include ("test.php") ;
?>

--
Ken Ward in Norwich ke*@oldcity.f2s .com
For Norwich and East Anglia visit www.oldcity.org.uk

[.:Ninja]

Ken Ward wrote:

Hi All,

I'm a new boy to php and working on a web site with long sections of
code that could be done as includes apart from one or two things
changing.
I've tested the following and it works, but what I really want to know
is am I OK placing php code inside a html line like this, or could there
be problems?
<!-- html code for test.php -->
<!-- lot of code cut -->
<a href="<?php print $filename; ?>"><?php print $title; ?></a>
<!-- lot of code cut -->
<!-- end of test.php -->

<!-- which is called in the main file like this -->
<?php
$filename="inde x.php";
$title="Index Page";
include ("test.php") ;
?>

Yeah I guess you're ok. You can actually use a shorter syntax to just print
a variable: <?= $varname ?>

I suspect someone will suggest you use some kind of template system that
separates your PHP from your HTML. Well, they have a lot of time on their
hands :)

..:A

--
http://www.ninja.up.ac.za

[Juha Suni]

..:Ninja wrote:

Yeah I guess you're ok. You can actually use a shorter syntax to just
print a variable: <?= $varname ?>

This, however, will only work if the PHP directive "short_open_tag " is
se to On, and by default many hosts have it off.

--
Suni

[Five Cats]

In message <10************ ***@inet2.up.ac .za>, ".:Ninja"
<al**@it.up.ac. za> writes

Ken Ward wrote:

Hi All,

I'm a new boy to php and working on a web site with long sections of
code that could be done as includes apart from one or two things
changing.
I've tested the following and it works, but what I really want to know
is am I OK placing php code inside a html line like this, or could there
be problems?
<!-- html code for test.php -->
<!-- lot of code cut -->
<a href="<?php print $filename; ?>"><?php print $title; ?></a>
<!-- lot of code cut -->
<!-- end of test.php -->

<!-- which is called in the main file like this -->
<?php
$filename="inde x.php";
$title="Index Page";
include ("test.php") ;
?>
Yeah I guess you're ok. You can actually use a shorter syntax to just print
a variable: <?= $varname ?>

I suspect someone will suggest you use some kind of template system that
separates your PHP from your HTML. Well, they have a lot of time on their
hands :)

Takes more time initially but probably saves it in the long term.
.:A

--
Five Cats
Email to: cats_spam at uk2 dot net

[Garp]

".:Ninja" <al**@it.up.ac. za> wrote in message
news:10******** *******@inet2.u p.ac.za...

I suspect someone will suggest you use some kind of template system that
separates your PHP from your HTML. Well, they have a lot of time on their
hands :)

Oi! ;-)

Garp

[Chung Leong]

"Five Cats" <ca*******@[127.0.0.1]> wrote in message
news:Ev******** ******@[127.0.0.1]...

I suspect someone will suggest you use some kind of template system that
separates your PHP from your HTML. Well, they have a lot of time on their
hands :)

Takes more time initially but probably saves it in the long term.

I doubt it. Using a template system is a little like going back to using PHP
1--you get a far less powerful, less flexible system to work with.

I'm not saying that template systems are bad. People just need to remember
that their raison d'etre is to limit what can be done within a page. If that
is your requirment then it makes sense. Otherwise it can hardly be
advisable. The benefits of "separating presentation from logic" is abstract
and often times cosmetic, whereas the impact of bumping into a template
system limitation is very real.

[Five Cats]

In message <qo************ ********@comcas t.com>, Chung Leong
<ch***********@ hotmail.com> writes

"Five Cats" <ca*******@[127.0.0.1]> wrote in message
news:Ev******* *******@[127.0.0.1]...

>I suspect someone will suggest you use some kind of template system that
>separates your PHP from your HTML. Well, they have a lot of time on their
>hands :)
Takes more time initially but probably saves it in the long term.

I doubt it. Using a template system is a little like going back to using PHP
1--you get a far less powerful, less flexible system to work with.

I'm not saying that template systems are bad. People just need to remember
that their raison d'etre is to limit what can be done within a page. If that
is your requirment then it makes sense. Otherwise it can hardly be
advisable. The benefits of "separating presentation from logic" is abstract
and often times cosmetic, whereas the impact of bumping into a template
system limitation is very real.

I would have said the reason for using a template (in the way I mean it)
is to make it easy to get a uniform page layout across a site.

--
Five Cats
Email to: cats_spam at uk2 dot net

[Tony Marston]

"Chung Leong" <ch***********@ hotmail.com> wrote in message
news:qo******** ************@co mcast.com...

"Five Cats" <ca*******@[127.0.0.1]> wrote in message
news:Ev******** ******@[127.0.0.1]...

I suspect someone will suggest you use some kind of template system thatseparates your PHP from your HTML. Well, they have a lot of time on theirhands :)
Takes more time initially but probably saves it in the long term.

I doubt it. Using a template system is a little like going back to using

PHP 1--you get a far less powerful, less flexible system to work with.
I totally disagree. My system is based around an amalgamation of the 3 tier
architecture (refer to
http://www.tonymarston.co.uk/php-mys...structure.html) and the
Model-View-Controller design pattern (refer to
http://www.tonymarston.co.uk/php-mys...ontroller.html) and it
has proved to be very powerful and very flexible.
I'm not saying that template systems are bad. People just need to remember
that their raison d'etre is to limit what can be done within a page. If that is your requirment then it makes sense. Otherwise it can hardly be
advisable. The benefits of "separating presentation from logic" is abstract and often times cosmetic, whereas the impact of bumping into a template
system limitation is very real.

I use XSL stylesheets to generate all my HTML and I have never found any
limitations. In fact my level of reusable code has gone up considerably
since using XSL. Take a look at
http://www.tonymarston.co.uk/xml-xsl/reusable-xsl.html for details.

--
Tony Marston

http://www.tonymarston.net

[Berislav Lopac]

Chung Leong wrote:

I'm not saying that template systems are bad. People just need to
remember that their raison d'etre is to limit what can be done within
a page. If that is your requirment then it makes sense.

Than it always makes sense. You see, you *must* limit what happens in a
page; specifically, the only thing that happens in a page is what is needed
to display it.

Everything else: database queries, calculations, text translations etc
should be done separately. When it comes to HTML, all data should already be
prepared for display. This is why templates are a good tool, despite their
performance penalty.

Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.

[Tony Marston]

"Berislav Lopac" <be************ @dimedia.hr> wrote in message
news:c7******** **@ls219.htnet. hr...

Chung Leong wrote:

I'm not saying that template systems are bad. People just need to
remember that their raison d'etre is to limit what can be done within
a page. If that is your requirment then it makes sense.
Than it always makes sense. You see, you *must* limit what happens in a
page; specifically, the only thing that happens in a page is what is

needed to display it.
I disagree with your emphasis on *must*. It is possible to write a component
which contains presentation, business and data access logic, but this does
not offer much opportunity for reusability. Personally I use a combination
of the 3 tier architecture and the Model-View-Controller design model to
produce a great deal of reusable code. However, the design and
implementation of such an infrastructure is beyond the capabilities of most
developers.
Everything else: database queries, calculations, text translations etc
should be done separately. When it comes to HTML, all data should already be prepared for display. This is why templates are a good tool, despite their
performance penalty.
All my HTML is produced from XML data using XSL stylesheets. There may be a
performance overhead but the savings are made in short development times and
large amounts of reusable code.

--
Tony Marston

http://www.tonymarston.net
Berislav

--
If the Internet is a Marx Brothers movie, and Web, e-mail, and IRC are
Groucho, Chico, and Harpo, then Usenet is Zeppo.