Which reminds me...

I use cffunction as an interface for calls to SPs, I came unstuck when two
blocks both included the same function, of course this causes a error. It
got me thinking about adding something the the DB so that each page knows
what functions it will need as well as the blocks to build the page. Or I
guess this could be on a block basis also, but either way, I like the idea
that one page id will give you all the things you need to construct a page.

Also, someone mentioned writing CFCs in a way that they won't bite your
behind when you come to use flash remoting, any chance of some info on that?

Ade

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 04 July 2003 11:28
To: [EMAIL PROTECTED]
Subject: RE: [ cf-dev ] Cookies anyone..


I have just started working on something similar, which I plan to release as
Open Source when I have finished. I plan that each page is generated in
index.cfm (using?page=page_name), each page is then made up of a collection
of dynamic content (stored in the dataabase) and static scripts. I also plan
to have a good user structure which supports unlimited user levels and
allows different pages to have different levels for viewing, editing and
removing, also each content part of the page can have different view, edit
and delete permissions. I have only just started coding it. My plan for the
system is that I can have a re-usable structure that I (and others) can use
to build a site on which has good CMS tools.

I haven't done any Cold Fusion in ages, and haven't done any CFMX yet. If
someone could advise me of possible pit-falls, things to look out for, or
really useful features (I haven't really used CF since the 4.5 days).

Regards,

Chris Cormack

British Telecommunications plc
Registered office: 81 Newgate Street London EC1A 7AJ
Registered in England no. 1800000
This electronic message contains information from British Telecommunications
plc which may be privileged or confidential. The information is intended to
be for the use of the individual(s) or entity named above. If you are not
the intended recipient be aware that any disclosure, copying, distribution
or use of the contents of this information is prohibited. If you have
received this electronic message in error, please notify us by telephone or
email (to the numbers or address above) immediately. 
Activity and use of the British Telecommunications plc E-mail system is
monitored to secure its effective operation and for other lawful business
purposes. Communications using this system will also be monitored and may be
recorded to secure effective operation and for other lawful business
purposes. 
Any views expressed in this email do not reflect those of BT and any of
partners and assosiates. Responsiblity for the opinions expressed are those
of the sender only


> -----Original Message-----
> From: Adrian Lynch [mailto:[EMAIL PROTECTED]
> Sent: 04 July 2003 11:13
> To: '[EMAIL PROTECTED]'
> Subject: RE: [ cf-dev ] Cookies anyone..
> 
> 
> I'm working on something right now where each page is built 
> from the DB.
> 
> What I wanted originally was one index page that could handle 
> a few page
> variations (different block layouts), a page id is passed to 
> it and the page
> is built from a bunch of possible blocks.
> 
> If you want a new page, you put in the DB the combination you 
> want and a new
> page exists for you to use.
> 
> Pages are in a parent child relationship, so all pages know 
> their place, and
> rightly so :O)
> 
> There is also a flash version of the site and the same method could be
> applied to that as well, in fact this maybe faster as a 
> complete blueprint
> for all the pages could be passed at the beginning and so the 
> need to look
> to the DB for the layout of a page is done only once.
> 
> This idea came about because of a problem we had with a site 
> where some
> pages couldn't be easily uniquely identified. It also has benefits for
> navigation and breadcrumb trails.
> 
> Unfortunately I've had to modify my idea to fit in with other 
> peoples ideas
> about the way a site should be built, but such is life.
> 
> Sorry for the waffle.
> 
> Ade
> 
> -- 
> ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
> 
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> For human help, e-mail: [EMAIL PROTECTED]
> 
> 

-- 
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]

-- 
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]

Reply via email to