Hi all,

In the last couple of weeks a few discussions have focused on the use of
pages and containers. One of the suggestions was to work with virtual pages
as opposed to the rather physical approach of default Spectra. What I don't
like about pages and containers is that to create a reusable container, you
need a cfa_page and a hardcoded id in a template. If I want to move or
remove a container from a page and exchange it with another one, I need to
go into the physical page and change the id. I want to swap and move around
and reuse. So I'm thinking more along the lines of the following objectType.

ObjectType: thePage
Properties
aContainers (array with ContainerIDs for purpose of switching sorting)
TemplateID
Menu (multilingual structure)
ParentID (sql searchable)
bCache

The TemplateID refers to a record that contains a reference to a piece of
Cold Fusion code that takes a set of Containers and formats them onto a
page. Perhaps one below the other, perhaps one beside the other, all
depending on the template.

This thePage record is put on a phyiscal page. When it is called it:
* Gets the relevant Containers
* Gets the Template
* Executes the containers and captures the resulting code into variables
* Renders the Template and inserts the generated container-html in the right
places

The advantage of this approach would be that you could easily move
containers around the site and you would have your multilingual menu in one
go. Creating a page would be as simple as selecting a couple of relevant
containers (or create a new one), selecting a pre-made template and
selecting a relevant spot in the sight.

The only problem I see is that Spectra requires you to have a cfa_page
around a container (we should get rid of that). You can write your own
container stuff, but I don't really want to throw all that pre-made stuff
out of the window. I guess you could create a single identical cfa_page that
is inserted around each physical page. Of course, you would get one page in
the SLM with a *lot* of containers. It would also require you to write your
own caching and security solutions.

Any comments on the validity of this approach?

Kind regards,

Marc Schipperheyn
<theFactor.e>

Premium Partner for Macromedia

The future is technological, but it will not be a world of gray steel



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Reply via email to