ckroon
Posts: 869
|
| Posted: 10/01/2007, 9:44 PM |
|
Hello all.
I am diving right in and attempting a website with codecharge.
I have codechargetools javascript menu builder and I love it!
I need a few points of advice however.
1) How do you (or is it even possible) to get the submenus to pop OVER the content in the next cell next over. Right now its pops under and you can't see the links. (using vertical menu along the left side of the page)
2) What is the best approach to "templating" this site? I want a picture header and a vertical menu (left side) to be on every page. Do I do this with one includable page (with both top graphic and vertical menu), 2 include pages (1 for each)? Or do I make a template page and create all new pages from that template.
The menu will be database driven, not static.
Thanks!
_________________
Walter Kempees...you are dearly missed. |
 |
 |
JimmyCrackedCorn
Posts: 583
|
| Posted: 10/01/2007, 10:33 PM |
|
you need to set the z-index so the menu is the topmost layer.
this might be helpful, http://www.softcomplex.com/forum/viewthread.php?tid=1647#pid4636
or just search on Google for z-index
_________________
Walter Kempees...you are dearly missed. |
 |
 |
datadoit
|
| Posted: 10/02/2007, 8:40 AM |
|
ckroon wrote:
> 2) What is the best approach to "templating" this site? I want a picture header
> and a vertical menu (left side) to be on every page. Do I do this with one
> includable page (with both top graphic and vertical menu), 2 include pages (1
> for each)? Or do I make a template page and create all new pages from that
> template.
>
> The menu will be database driven, not static.
>
> ---------------------------------------
I would make both the header and left menu each an include.
For your main content, I would make that an inline frame referencing
'content' files. I like to use iframes because:
1. It hides the referencing URL as you navigate within the frame.
2. By hiding the URL, it prevents folks from bookmarking with URL
parameters (security thing). Though real techies know how to circumvent
this, it works for the everyday user.
3. The iframe can be set to auto-scroll, thus only that portion of the
screen scrolls, leaving intact your menu and image header.
+-------------------------------------+
| H E A D E R |
+-------------------------------------+
| | |
| M | Main |
| E | Content |
| N | in |
| U | iframe |
| | |
+-------------------------------------+
You can lay this out in a table or a style, and in your main content
area, add an HTML label, and in the label's BeforeShow, do something like:
$FrameValue = "<iframe name='main' src='" . CCGetParam("module","index")
.. "/" . CCGetParam("ret_link","index_mainframe_overview.php");
$FrameParams = "' width='100%' border='0' frameborder='0'
height='100%'>Your browser does not support inline frames, or is
currently configured to not display inline frames.</iframe>";
$QueryString = CCGetQueryString("QueryString","");
if ($QueryString !== "") {
$QueryString = CCRemoveParam($QueryString, "ccsForm"); //NEVER want this!
$FrameValue .= "?" . $QueryString;
}
$Component->SetValue($FrameValue . $FrameParams);
This allows you to create just one primary page (index.php), then
reference the appropriate subpages via the 'module' and 'ret_link'
parameters. On disk your app kinda looks like this:
+ images
- includes
- header.php
- menu.php
+ parents
- students
- grades.php
- attendance.php
+ teachers
+ Styles
index.php
login.php
This method also allows you to create role-based permissions not only on
each individual page, but also the module (or folder on disk).
Your menu items will always target the 'main' frame. For links inside
the iframe, no need to set a target, unless you want to load everything,
for which you then specify '_parent' (ie: links going from one module to
another).
Finally, the beauty of this is that it allows you to swap around the
design elements (ex: Put the menu on top instead of on the left) by
changing only a single page - the index.php if tabled, and/or the
stylesheet.
|
|
|
 |
|