[FX.php List] Re: thoughts on FX.php in an IFRAME?

[Joel Shapiro]

Thanks so much for your suggestions, Gjermund and Steve.

My plan was to do basically Steve's #2 suggestion (although I was  
planning on putting the divs in the includes themselves, instead of  
putting the divs on each page and putting an include inside each  
div).  Thinking about it now, I suppose I could even put both divs  
into one include and just add one include to each of my pages instead  
of two.

I know a number of people on this list use the everything-called-on- 
one-index-page structure.  I think it would take me more time at this  
point to change to this structure now, but I would like to understand  
it a bit better (at least for next time).  I'll post my question in a  
separate thread, though, to keep things cleaner.

Best,
-Joel


On Nov 30, 2006, at 2:24 AM, Gjermund Gusland Thorsen wrote:

> I double that, but what about doing it a little bit further?
>
> I would like to say make header.php, footer.php
> and just have each php file be a bodyfile that includes header.php and
> footer.php
>
>
> Example header.php could be something like
> ---
> <div id="page">
> <div id="header">
> <div id="menu">
> <ul id="nav">
> <li><a href="">menuchoice 1</a></li>
> <li><a href="">menuchoice 2</a></li>
> <li><a href="">menuchoice 3</a></li>
> <li><a href="">menuchoice 4</a></li>
> <li><a href="">menuchoice 5</a></li>
> </ul>
> </div>
> </div>
> ---
>
> 2006/11/30, Steve Winter <steve at bluecrocodile.co.nz>:
>> Hi Joel,
>>
>> Just before you rush too far into this, here's a couple of  
>> suggestions for
>> you...
>>
>> 1. What about working down the line that you were thinking, but only
>> redevelop the layout once, using good valid css to position all of  
>> the
>> elements, then you could create one index.php page, which has all the
>> generic elements in it, and an include within a div on that page  
>> where
>> your dynamic content needs to go, the what you could do is call
>> index.php?p=theRealFile, then within that div you could do <?php
>> include('pathToIncludes'.$_REQUEST['p']);
>>
>> 2. Do the same thing as above, but reformat each of your current  
>> pages,
>> creating a div at the top for the graphic, a div down the side for  
>> the
>> menu, and a div for your primary content... then create top.php and
>> side.php and call them as includes into the divs on each of your  
>> pages...
>>
>> This way, when they make changes to either the top or left  
>> content, all
>> you have to do is resize the relevant divs within you external css  
>> sheet,
>> and alter two included files... rather than having to go through  
>> and make
>> substantial changes to each page...
>>
>> Just my 2c worth... let me know if you need further details of  
>> eaither of
>> my suggestions...
>>
>> Cheers
>> Steve
>>
>>
>>
>> > Never mind. (poor old Emily Litella)
>> >
>> > I just looked at my test page in Firefox (after testing in Safari)
>> > and it looks like crap:  the iframe is way too low, their imagemap
>> > with javascript no longer works, and it's not worth my  
>> troubleshooting.
>> >
>> > I'll go back to my original plan of using includes within my php
>> > pages.  I guess I coulda done more testing before posting ;)
>> >
>> > Thanks anyway.  Sorry for the bandwidth.
>> >
>> > -Joel
>> >
>> >
>> > On Nov 29, 2006, at 9:39 PM, Joel Shapiro wrote:
>> >
>> > > Hi all
>> > >
>> > > A client for whom I'm designing an FX.php site wants the  
>> design of
>> > > the FX part of their site to match the rest of their (static)
>> > > site.  Their main design includes a wide graphic along the  
>> top, and
>> > > a tall graphic along the left side (both with imagemap links) --
>> > > all within a body-filling table, with misc. colspans, etc.
>> > >
>> > > The FX.php pages are mostly completed, functionality-wise, but  
>> the
>> > > design doesn't match their new site.  (They've known I've been
>> > > waiting for their design templates since I started working on the
>> > > project, but only sent them to me this week -- and they do
>> > > understand that I'll now need to do some re-designing).
>> > >
>> > > At first I was thinking I'd place their graphics (and respective
>> > > imagemaps) as included files in my php files.  Then I started
>> > > thinking maybe it would be easier to just use their base page/
>> > > template and place my FX.php site within an IFRAME object in  
>> one of
>> > > their table cells.  I did a quick test and both GET and POST
>> > > requests seem to work as expected, even though the displayed url
>> > > remains at the main page (even an .html).
>> > >
>> > > I generally stay away from using frames, but this could be a
>> > > quicker implementation than re-formatting all my FX.php pages to
>> > > fit their structure.
>> > >
>> > > Note: Their static site is hosted elsewhere, while their FMSA/WPE
>> > > server is located in their office.  I haven't tested yet if the
>> > > main page (that holds the IFRAME) functions differently when
>> > > located at their external webhost or locally on their FMSA box).
>> > >
>> > > I'd be happy to keep their costs down, but not at the expense  
>> of a
>> > > less stable / weaker etc. site.
>> > >
>> > > Any thoughts/experience/advice?
>> > >
>> > > TIA,
>> > > -Joel
>> >
>> > _______________________________________________
>> > FX.php_List mailing list
>> > FX.php_List at mail.iviking.org
>> > http://www.iviking.org/mailman/listinfo/fx.php_list
>>
>>
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
>>
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list