From: George B. <gbr...@lu...> - 2004-08-09 14:33:48
|
That sounds like a very interesting approach. But I don't quite understand, Eloi, what you mean by asking whether Pagemaster 'fully supports page templates now'. (I don't use Article Manager any more because users protested the copyright message.) The default Pagemaster page template lumps everything together in a {CONTENT} tag, meaning it's up to Pagemaster itself to lay out the page except for add-ons like date published etc. Granted, the section templates (e.g., image_float_left.tpl) can lay out a section pretty much any way {IMAGE} and {TEXT} can be arranged, but ultimately Pagemaster just strings all those sections (each sitting in a table) in a line down the page. It's not clear to me how one would put that in a two-column layout without modifying the PageMaster code. Most of the options I can think of for a series of section templates like the one you suggest would make individual templates sensitive to the proper use of other templates (e.g. one template starts a <div> and another finishes it). George On 8/8/04 11:38 PM, "php...@li..." <php...@li...> wrote: > Send Phpwebsite-developers mailing list submissions to > php...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > or, via email, send a message with subject or body 'help' to > php...@li... > > You can reach the person managing the list at > php...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Phpwebsite-developers digest..." > > > Today's Topics: > > 1. Re: More phpWS and OOP (Eloi George) > > --__--__-- > > Message: 1 > Date: Sun, 08 Aug 2004 16:28:28 -0400 > From: Eloi George <el...@re...> > To: php...@li... > Subject: Re: [Phpwebsite-developers] More phpWS and OOP > Reply-To: php...@li... > > I don't know why, but Sourceforge almost always delays my submissions to > this list... > > I understand your goal a lot more now, but I think it can be achieved > with existing modules. Article Manager (and PageMaster if it fully > supports page templates now) is designed for just that purpose. A > specific newsletter layout is defined as the overall page template > design plus any particular combination of section templates. If you add > in section templates that utilize "div"s with "float:left/right" to > define columns, then you can end up with any layout you choose! > > Once a particular layout is designed, then all the designers have to > know is that Layout#1 consists of Page Template "Layout_1" with sections > in the order of "Right_Column_Top", any number of > "Right_Column_Middle", "Right_Column_Bottom", "Headline", and any number > of "Body". > > Or if you want to make it even easier, you could submit an RFE (or a > patch ;)) to allow either module to clone an new article/page off of an > existing blank one. > > On the other hand, if you wanted to make the newsletter module create > the articles itself, the technique is illustrated in the importation > scripts. > > Personally, I think our collective coding time would be better spent on > quite a few other core class ideas than a universal section class. > There are only a very few possible uses for the page/section paradigm, > and I'm constantly looking for an easy-to-use, non-javascript-intensive > way to get away from it and still retain the layout flexibility. > > -Eloi- > > > > > > --__--__-- > > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > End of Phpwebsite-developers Digest > ______________________________________ George Brackett, Principal George Brackett Associates 617 413 4316 / gbr...@lu... http://www.luceatlux.com/gba/ |
From: Shaun M. <sh...@ae...> - 2004-08-09 14:54:19
|
The way I've done 2 or 3 column pages in pagemaster in the past is to define a new section template which uses float:left in the class used on the DIV. Set the width dependent on the number of columns you want. A clear:both afterwards is sometimes useful or put the clear:both on the other existing section templates which you've probably modified anyway to remove tables. ;-) eg. .floaty { float: left; width: 50%; } create a new section template called floaty.tpl <div class="floaty> <h3>{TITLE}</h3> {CONTENT} </div> (or whatever you want in there. If you want 3 columns, use 33%. If using margins/padding, watch for IE's box model bugs. On 9 Aug 2004, at 15:33, George Brackett wrote: > That sounds like a very interesting approach. But I don't quite > understand, > Eloi, what you mean by asking whether Pagemaster 'fully supports page > templates now'. (I don't use Article Manager any more because users > protested the copyright message.) The default Pagemaster page template > lumps everything together in a {CONTENT} tag, meaning it's up to > Pagemaster > itself to lay out the page except for add-ons like date published etc. > Granted, the section templates (e.g., image_float_left.tpl) can lay > out a > section pretty much any way {IMAGE} and {TEXT} can be arranged, but > ultimately Pagemaster just strings all those sections (each sitting in > a > table) in a line down the page. It's not clear to me how one would > put that > in a two-column layout without modifying the PageMaster code. Most of > the > options I can think of for a series of section templates like the one > you > suggest would make individual templates sensitive to the proper use of > other > templates (e.g. one template starts a <div> and another finishes it). > > George > > On 8/8/04 11:38 PM, > "php...@li..." > <php...@li...> wrote: > >> Send Phpwebsite-developers mailing list submissions to >> php...@li... >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> or, via email, send a message with subject or body 'help' to >> php...@li... >> >> You can reach the person managing the list at >> php...@li... >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Phpwebsite-developers digest..." >> >> >> Today's Topics: >> >> 1. Re: More phpWS and OOP (Eloi George) >> >> --__--__-- >> >> Message: 1 >> Date: Sun, 08 Aug 2004 16:28:28 -0400 >> From: Eloi George <el...@re...> >> To: php...@li... >> Subject: Re: [Phpwebsite-developers] More phpWS and OOP >> Reply-To: php...@li... >> >> I don't know why, but Sourceforge almost always delays my submissions >> to >> this list... >> >> I understand your goal a lot more now, but I think it can be achieved >> with existing modules. Article Manager (and PageMaster if it fully >> supports page templates now) is designed for just that purpose. A >> specific newsletter layout is defined as the overall page template >> design plus any particular combination of section templates. If you >> add >> in section templates that utilize "div"s with "float:left/right" to >> define columns, then you can end up with any layout you choose! >> >> Once a particular layout is designed, then all the designers have to >> know is that Layout#1 consists of Page Template "Layout_1" with >> sections >> in the order of "Right_Column_Top", any number of >> "Right_Column_Middle", "Right_Column_Bottom", "Headline", and any >> number >> of "Body". >> >> Or if you want to make it even easier, you could submit an RFE (or a >> patch ;)) to allow either module to clone an new article/page off of >> an >> existing blank one. >> >> On the other hand, if you wanted to make the newsletter module create >> the articles itself, the technique is illustrated in the importation >> scripts. >> >> Personally, I think our collective coding time would be better spent >> on >> quite a few other core class ideas than a universal section class. >> There are only a very few possible uses for the page/section paradigm, >> and I'm constantly looking for an easy-to-use, >> non-javascript-intensive >> way to get away from it and still retain the layout flexibility. >> >> -Eloi- >> >> >> >> >> >> --__--__-- >> >> _______________________________________________ >> Phpwebsite-developers mailing list >> Php...@li... >> https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers >> >> >> End of Phpwebsite-developers Digest >> > > ______________________________________ > George Brackett, Principal > George Brackett Associates > 617 413 4316 / gbr...@lu... > http://www.luceatlux.com/gba/ > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source > Technology > Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > > Shaun aegis design - http://www.aegisdesign.co.uk |
From: Eloi G. <el...@re...> - 2004-08-10 13:56:28
|
>That sounds like a very interesting approach. But I don't quite understand, >Eloi, what you mean by asking whether Pagemaster 'fully supports page >templates now'. > The last time I looked at a PageMaster installation (admittedly a long time ago), it had a default template, but it didn't seem to have a way to choose another one. The function of the page template is to lay out the sections, so if there's any tags you have to enclose the page in or non-section-specific information (like date published, category information, nav links, common javascript, etc.), that can all be specified here so you don't have to mess around with the various themes. >ultimately Pagemaster just strings all those sections (each sitting in a >table) in a line down the page. It's not clear to me how one would put that >in a two-column layout without modifying the PageMaster code. > It strings the -html- in a line down the page. The tags contained therein specifies how the sections will be laid out. > Most of the >options I can think of for a series of section templates like the one you >suggest would make individual templates sensitive to the proper use of other >templates (e.g. one template starts a <div> and another finishes it). > > For the more complex layouts, yes. |
From: Shaun M. <sh...@ae...> - 2004-08-10 14:57:56
|
On 10 Aug 2004, at 14:56, Eloi George wrote: > The last time I looked at a PageMaster installation (admittedly a long > time ago), it had a default template, but it didn't seem to have a way > to choose another one. That was fixed quite a while ago. The problem was that the 'Edit Page Info' link that linked to where you selected the template, category, title etc was in the title of the box and if you didn't want 'Pagemaster vx.x' in your box title you selected a default_empty boxstyle. The templates were changed to have the link inside the content area. Shaun aegis design - http://www.aegisdesign.co.uk |