Layers in Tables

I want to stack layers in a table cell. However, I can't seem
to find a way to stack them properly. I've tried absolute
positioning in CSS but the layers do not auto size with my browser.
I have also tried the relative positioning, but instead of stacking
the layers, it just puts one below the other. Can anyone help me
stack layers in a table cell so that they also auto size with the
browser - i.e. an absolute position inside a table cell? Is this
possible?
Thanks

You do not need to use layers to do this. And you never
should put
absolutely positioned elements directly into table cells!
Investigate the use of DW's SetText behavior. It allows you
to change the
text content of any non-anonymous element on the page in
response to an
event. For example, your selection of a radio button could
call this
behavior to change the text displayed in any other cell on
the page,
provided that cell has been given an ID value, e.g.,
<td id="special">This cell has an ID</td>
> But, when I set
> the positioning of these children layers, they resort
back to the body as
> the
> parent layer
Before using 'layers' or any absolutely positioned element,
it's a good
thing to take the time to understand positioning -
This may help you understand positioning a bit -
There are 4 different types of positioning:
Absolute
Relative
Fixed
Static
Here is a brief explanation of each kind of positioning (with
regard to
placement of elements on the page only)....
Position:absolute (or A/P elements)
This does several things -
1. It 'removes' the element from the flow of the code on
the page so that
it can no longer influence the size or position of any other
page element
(except for those contained within it, of course).
2. The absolutely positioned element takes its position from
the position of
its closest PARENT *positioned* element - in the
absence of any explicitly
positioned parent, this will default to the <body> tag,
which is always
positioned
at 0,0 in the browser viewport.
This means that it doesn't matter where in the HTML code the
layer's code
appears (between <body> and </body>), its
location on the screen will not
change (this assumes that you have not positioned the A/P
element within
a table or another A/P element, of course).
Furthermore, the space in
which
this element would have appeared were it not positioned
is not preserved
on the screen. In other words, absolutely positioned elements
don't take
up any space on the page. In fact, they FLOAT over the page.
Position:relative (or R/P elements)
In contrast to absolute positioning, a relatively positioned
page element is
*not* removed from the flow of the code on the page, so
it will use the
spot
where it would have appeared based on its position in
the code as its
zero point reference. If you then supply top, right,
bottom, or left
positions
to the style for this element, those values will be
used as offsets from
its
zero point.
This means that it DOES matter where in the code the
relatively positioned
element appears (, as it will be positioned in that location
(factoring in
the offsets) on the screen (this is true for any placement in
the code).
Furthermore, the space where this element would have
appeared is
preserved in the display, and can therefore affect the
placement of
succeeding elements. This means that the taller a relatively
positioned element is, the more space it forces on the page.
Position:static
As with relative position, static positions also "go with
the flow". An
element with a static position cannot have values for
offsets (top, right,
left, bottom) or if it has them, they will be ignored. Unless
explicitly
positioned, all div elements default to static positioning.
Position:fixed
A page element with this style will not scroll as the page
content scrolls.
Support for this in elements other than page backgrounds is
quirky
There are several other things you need to know:
1. ANY page element can be positioned - paragraphs, tables,
images, lists,
etc.
2. The <div> tag is a BLOCK level tag. This means that
if it is not
positioned or explicitly styled otherwise, a) it will always
begin on a new
line on the screen, and b) it will always force content to a
new line below
it, and c) it will always take up the entire width of its
container (i.e.,
width:100%).
3. The placement of A/P elements *can* affect the BEHAVIOR of
other
elements
on the page. For example, a 'layer' placed over a hyperlink
will mask that
hyperlink.
You can see a good example of the essential difference
between absolute and
relative positioning here -
http://www.great-web-sights.com/g_layersdemo.asp
You can see a good demonstration of why using layers for a
page layout tool
is dangerous here -
http://www.great-web-sights.com/g_layer-overlap.asp
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"brywilson88" <[email protected]> wrote in
message
news:[email protected]...
> The table is how I layout my page. I want to stack
layers in a cell so
> that
> when a visitor toggles a radio button, the layers will
appear or disappear
> based on what is toggled. I've tried to set a blank
layer in the cell as
> a
> parent layer and nest the other layers inside of that
layer. But, when I
> set
> the positioning of these children layers, they resort
back to the body as
> the
> parent layer. I just don't know what to do.
>

Similar Messages

  • Converting layers to table - Mine won't work!

    Hi,
    In Dreamweaver I first created a template of my website. Using the template I then wanted to create my very first official home page, called index.htm. This is the problem i've got; when I open a blank white Dreamweaver page i go to 'File > New from Template' and then create my index.htm page based on the template of course. So far so good. Within the index.htm page I am trying to convert layers to table but it won't let me click on the 'convert layers to tables' button because its grayed out. My layers definitely do not overlap because within the layers option I have the 'Prevent layer overlap' box ticked.. The weird thing is that if I were in the template and then tried to 'File > Save As' to create my index.htm page this way, it will let me covert layers to table within the index page, however surely by doing it this way the index page would not be updated with any changes that I make within the template as the index page would not technically be based on the template. I hope this makes sense and was wondering if someone could help me with this?
    Thanks
    Maxi

    There is no doctype declared in your pages code.
    First you need to open your .dwt template file, switch to code view and change the line below, which is at the start of your pages code:
    <html><!-- #BeginTemplate "/Templates/template.dwt" -->
    To this:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml"><!-- #BeginTemplate "/Templates/template.dwt" -->
    While still in your .dwt template file locate the opening <body> tag (see below) and insert the opening <div> wrapper tag and inline css directly after it (see below)
    <body bgcolor="#E4227C" text="#000000">
    <div id="wrapper" style="width: 1000px; margin: 0 auto; position: relative;">
    Next scroll to the very bottom of the page and insert the closing </div> wrapper tag (see below)
    <div id="Layer15" style="position:absolute; left:44px; top:671px; width:193px; height:18px; z-index:16"><img src="Templates/linebreak.jpg" width="910" height="20"></div>
    </div><!-- closing wrapper tag -->
    </body>
    </html>
    Thats it. If you follow the instrcutions correctly your page will now center horizontally in the brower window.

  • Comment Forms? Layers within Tables? Crazy Idea?

    Good Day Dear Folk,
    I have designed a webpage using tables. I want to be able to
    put text in the table with the ability for viewers to scroll within
    the table. Layers have the option for scrolling text, correct? So I
    would like to put a layer in the table. I like using a table to
    center the content of the page. Is there a better way? Also, my
    friend wants visitors to be able to sign up for a newsletter and
    have the ability to leave comments about the site. I know this
    involves forms but I don't know about script writing. I'm more
    concerned about the comment form. She would like the comments to
    post directly to the page. Any ideas? Please help if you can.
    Thanks.

    > i converted my tables to layers and now it's like a
    whole new world.
    This could be equivalent to leaping from the frying pan into
    the volcano. I
    never recommended that you do that. Using Layers as a layout
    method is a
    very bad practice in general.
    1. ... any ideas?
    Are these PNG files NATIVE FW PNG files? Or did you export
    from FW as 8bit
    (or 32bit) PNG files? Try using GIF/JPG images instead.
    > 2. i want to create a page where people can leave a
    comment about the
    > website. i would like the comment to post automatically.
    i'm not sure
    > how
    > involved this is but if you can direct me to what i need
    to do, i would
    > appreciate it. if there is a high learning curve, it's
    ok. i want to
    > learn.
    > am i crazy?
    Crazy? No. It's needs like this that drive you to learn. Such
    a
    capability would require server-side scripting and database
    access. You can
    try some 'canned' approaches by Googling for 'guestbook' and
    see what you
    find....
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "Itiyopiya Ewart" <[email protected]> wrote
    in message
    news:[email protected]...
    > thanks ACE!
    > i converted my tables to layers and now it's like a
    whole new world.
    > thank
    > you thank you!!! i'm learning css now... i have some
    more questions that
    > i
    > hope you can help me with:
    > 1. i'm using dreamweaver 8. i'm using OSX. my browsers
    for checking my
    > pages are safari, firefox, and opera. for some reason
    certain images
    > won't
    > show in firefox and opera. i can see them in safari, but
    the other two
    > only
    > show the alt image info. this also happens in IE. the
    files are .png.
    > they
    > were all created in photoshop from the same .psd but two
    images for the
    > navigation menu don't show. any ideas?
    >
    > 2. i want to create a page where people can leave a
    comment about the
    > website. i would like the comment to post automatically.
    i'm not sure
    > how
    > involved this is but if you can direct me to what i need
    to do, i would
    > appreciate it. if there is a high learning curve, it's
    ok. i want to
    > learn.
    > am i crazy?
    >
    > thanks!
    >

  • Detailed layered ADF tables and reports; CSV

    I have implemented this http://kuba.zilp.pl/?id=361 to produce CSV files from view objects and BC's. This worked fine when dealing with one simple queried View object. I have hit a wall because my data and queries have become more involved. Example:
    Sponsor 112234
    Item Qty Site Cost Description
    NSN 0000-00-000-0003 122 122 $0.00 SCDR TST
    NSN 0000-00-000-0003 30 PHL $0.00 SCDR TST
    Total Cost for 112234: $0.00
    Sponsor ARMY-TACOM
    Item Qty Site Cost Description
    C/P (*0000) 29742 1 PHL $100.00 PUMP, BRONZE
    C/P (*0000) 320 01434 02 1 PHL $10.00 POWER SWITCH
    C/P (*0000) 320 01437 01 1 PHL $10.00 SWITCH, WATER DRAIN
    C/P (*0000) 321 30671 01 1 PHL $2,637.18 SAMPLING, MEASURE
    C/P (*0000) 321 30676 1 PHL $10.00 HOUSING, VIBRATOR
    View the above data as ONE table, and not TWO seperate tables.
    In this example, I am showing all the info. for EACH sponsor.
    Is is possible to create ONE table/View Object to give me this information? And can an HTML report be produced from that View Object?
    Thanks.

    Hi,
    sure, you can create read-only VO that are based on SQL queriesincluding one to many tables. If you need the Views to be updateable then you create Entities for each table and createa VO on top of that
    Frank

  • Cannot add layers/tables to an editable region

    I created a template the other day, and then created pages
    from that template. The main editable region which was meant to be
    for all my info, pictures, wont let me add layers or tables to
    position my text/images.... Have I missed something here?
    \Robert

    Yes, there would be no restriction on what you can place in
    that editable
    region. But I don't like the way you have started with this
    page. Layers
    should not be used as a primary layout methodology....
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "the full monty" <[email protected]> wrote
    in message
    news:epqp0m$lrc$[email protected]..
    > This is the code: The whole of the layer region should
    be editable... ie.
    > be
    > able to add layers/tables to position text?
    >
    > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
    Transitional//EN"
    > "
    http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    > <html xmlns="
    http://www.w3.org/1999/xhtml">
    > <head>
    > <meta http-equiv="Content-Type" content="text/html;
    charset=iso-8859-1" />
    > <!-- TemplateBeginEditable name="doctitle" -->
    > <title>Untitled Document</title>
    > <!-- TemplateEndEditable -->
    > <!-- TemplateBeginEditable name="head" --><!--
    TemplateEndEditable -->
    > <style type="text/css">
    > <!--
    > #Layer1 {
    > position:absolute;
    > left:382px;
    > top:30px;
    > width:329px;
    > height:268px;
    > z-index:1;
    > }
    > -->
    > </style>
    > </head>
    >
    > <body>
    > <div id="Layer1"><!-- TemplateBeginEditable
    name="EditRegion1" --> <!--
    > TemplateEndEditable --></div>
    > </body>
    > </html>
    >
    > \Robert
    >

  • Layers, tables and Foxfire

    I am using Dreamweaver 8 and am having trouble with layers
    and tables in Foxfire. For example my page at
    http://www.ouachitamaps.com/Eagle%20Rock.html
    is fine in IE6. As you can see, I have a table structure and put
    layers in them to hold text. In Foxfire, the layers extend below
    the bottom of the table. Any suggestion about how to fix this.
    Maybe there is another way to get this design without layers, but I
    am a novice and this was what I was able to figure out (I am
    intimadated by css).

    Layers or absolutely positioned divs should *never* go inside
    a table, hence
    all your problems.
    There is no need whatsoever for that layout of your page to
    be using layers.
    Insert the text directly into a table cell, that will contain
    your text with
    no overflow. You will need to nest some tables, so that the
    table doesn't
    expand incorrectly however when you insert content into the
    left or right
    cells.
    This is a quick and dirty example. I've given the outer
    tables a black
    border and centered each table in the browser (personal
    preference) Other
    styles I've used I wouldn't normally I'd control it by css,
    but as you are a
    beginner, this should get you started until you learn some
    basic css for
    yourself. :)
    Copy and paste the following code into a new DW window and
    you'll see how
    I've set it all up. 1 table for the top graphic and a couple
    of nested
    tables within an outer table for your content area and
    another separate
    table for footer. I've set each table at 955px wide to
    accomodate your
    header image... plus a bit extra for padding . No layers in
    sight :-)
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
    Transitional//EN"
    http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="
    http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html;
    charset=utf-8" />
    <title>Untitled Document</title>
    <style type="text/css">
    <!--
    body {
    margin-left: 0px;
    margin-top: 0px;
    margin-right: 0px;
    margin-bottom: 0px;
    background-color:#FFFFFF;
    /* gives all tables a 1px black border */
    .outertable {border: 1px solid black; margin-bottom: 5px;}
    table td {padding: 4px;} /* gives some padding to each table
    cell */
    -->
    </style>
    </head>
    <body>
    <table border="0" align="center" cellpadding="0"
    cellspacing="0"
    class="outertable">
    <tr>
    <td><a href="/index.html"><img
    src="
    http://www.ouachitamaps.com/picture_library/Hiking%20Trail%20Banner.jpg"
    width="954" height="114" border="0"
    /></a></td>
    </tr>
    </table>
    <table width="955" border="0" align="center"
    cellpadding="0" cellspacing="0"
    class="outertable">
    <tr>
    <td valign="top"><table border="0" cellpadding="0"
    cellspacing="0">
    <tr>
    <td valign="top"><img
    src="
    http://www.ouachitamaps.com/picture_library/Eagle%20Rock/Eagle%20Rock%20Map%20East.jpg"
    width="300" height="470" vspace="5" />
    <img
    src="
    http://www.ouachitamaps.com/picture_library/Eagle%20Rock/Eagle%20Rock%20Map%20West.jpg"
    width="300" height="470" vspace="5" />
    <p>More pictures in this cell</p></td>
    </tr>
    </table></td>
    <td width="100%" valign="top"><table width="100%"
    border="0" align="center"
    cellpadding="0" cellspacing="0">
    <tr>
    <td><h1>Eagle Rock Loop
    </h1>
    <p>A 26.8 mile loop through the Ouachita Mountains of
    Arkansas made up of
    three trail, the Little Missouri, Athens-Big Fork and Viles
    Branch Trail.
    </p>
    <p><strong>The Maps: </strong>The Eagle
    Rock Loop is comprised of two maps,
    east and west. They are nominal 1:24,000 based on USGS 7.5
    minute
    quadrangle topographic maps and printed in color on 11x17,
    &quot;Rite in the
    Rain” all weather writing paper. The loop was mapped
    with a WAAS enabled
    GPS and is drawn in three colors to designate the three
    trails. Also shown
    is the Winding Stair scenic area and Eagle Rock Vista. Other
    features
    include trailheads, segment mileage, general directions to
    park, waypoints
    and waypoint coordinates. </p>
    <p><strong>The Hike:</strong> The Eagle
    Rock Loop just may be the best hike
    in the Ouachita Mountains, combining rugged hill climbs
    though the mixed
    hardwood and pine forest with strolls along crystal clear
    streams. The loop
    is made of three trails and, with 5 trailheads, offers a
    multitude of hiking
    options. The hardwoods in this section of the Ouachita
    National Forest are
    oak with some maple. The pines are short leaf and loblolly.
    In the winter
    the smaller but evergreen holly trees are a striking contrast
    to the gray
    brown of the forest floor.</p>
    <p>This trip starts near the north end of the Highway
    369 at the Albert Pike
    Recreation Area. The recreation area has a campground and
    showers ($10
    without utilities) and makes a good place to camp if you come
    in late after
    work and want an early start. Follow the Little Missouri
    Trail (white
    blazes) north along the Little Missouri River. The trail is
    fairly level
    but crosses the river three times and two significant
    tributaries making it
    impassible when the water is high. Call the ranger station if
    there has
    been heavy rains or take note of the water level when you
    cross the bridge
    at Albert Pike. </p>
    <p>Rest of the text content in this cell</p>
    <p> </p>
    <p> </p></td>
    </tr>
    </table></td>
    <td valign="top"><table height="259" border="0"
    cellpadding="0"
    cellspacing="0">
    <tr>
    <td><a href="/picture_library/Eagle Rock/Eagle Rock
    GE W View
    Page.html"><img src="
    http://www.ouachitamaps.com/picture_library/Eagle
    Rock/Eagle Rock GE W View sm.jpg" width="200" height="93"
    vspace="5"
    border="0" /></a>
    <a href="/picture_library/Eagle Rock/Eagle Rock GE E View
    Page.html"><img
    src="
    http://www.ouachitamaps.com/picture_library/Eagle%20Rock/Eagle%20Rock%20GE%20E%20View%20sm .jpg"
    width="200" height="116" vspace="5" border="0"
    /></a>
    <img
    src="
    http://www.ouachitamaps.com/picture_library/Eagle%20Rock/Eagle%20Rock%20Little%20Mo%202074 .jpg"
    width="200" height="150" vspace="5" />
    <img
    src="
    http://www.ouachitamaps.com/picture_library/Eagle%20Rock/Eagle%20Rock%20Little%20Mo%20Fall s%202082.jpg"
    width="200" height="150" vspace="5" />
    <img
    src="
    http://www.ouachitamaps.com/picture_library/Eagle%20Rock/Eagle%20Rock%20Vista%202034.jpg"
    width="200" height="150" vspace="5" />
    <p>more pictures in this cell</p>
    <p> </p>
    <p> </p>
    <p> </p>
    <p> </p>
    <p> </p></td>
    </tr>
    </table>
    <p> </p>
    <p> </p></td>
    </tr>
    </table>
    <table width="955" border="0" align="center"
    cellpadding="0" cellspacing="2"
    class="outertable">
    <tr>
    <td align="center"><p><span
    class="style4">Weatherproof Topographic Maps at
    OuachitaMaps.com - Hiking Trails of the Ouachitas and
    Ozarks</span><br />
    <strong>Featured Topographic Maps in Oklahoma and
    Arkansas</strong> <br />
    <strong>Ouachita Trail Loops: </strong><a
    href="/Horsethief.html">Billy
    Creek Trail</a> - <a
    href="/Boardstand.html">Boardstand Trail</a> - <a
    href="/Holson.html">Holson Valley Loop</a> - <a
    href="/Horsethief.html">Horse Thief Springs
    Trail</a> - <a
    href="/Boardstand.html">Old Military Road Trail</a>
    - <a
    href="/TalimenaBo.html">Talimena-Bohannon
    Loop</a><br />
    <strong>Other Ouachita Hikes: </strong><a
    href="/Beech Creek.html">Beech
    Creek Trail</a> - <a href="/Buckeye.html">Buckeye
    Trail</a> - <a
    href="/Caney Area.html">Caney Creek Area</a> - <a
    href="/Buckeye.html">Caney
    Creek Trail</a> - <a href="/Eagle
    Rock.html">Eagle Rock Loop</a><br />
    <strong>Selected Ozark Hikes: </strong><a
    href="/Butterfield.html">Butterfield Trail (Devils
    Den)</a> - <a
    href="/White Rock.html">White Rock-Shores Lake
    Loop</a> </p>
    <a
    href="/index.html"><strong>Home</strong></a></td>
    </tr>
    </table>
    <p> </p>
    <p> </p>
    </body>
    </html>
    Nadia
    Adobe® Community Expert : Dreamweaver
    CSS Templates |Tutorials |SEO Articles
    http://www.DreamweaverResources.com
    ~ Customisation Service Available ~
    http://www.csstemplates.com.au

  • How do I create a webpage in Dreamweaver WITHOUT using layers?

    I'm reading a lot about how we should not use layers and
    tables when creating a website in Dreamweaver because of something
    called "absolute placement" (or something), which is the reason the
    text in my website is constantly misaligned or overlapping when
    opened up in Firefox. Although, I've never had this problem before
    for the past three years I've been using Dreamweaver to create my
    sites, which is what's most frustrating I think.
    So, I guess I'm wondering how, then, do I create a webpage in
    Dreamweaver WITHOUT using layers and tables? The only thing I've
    been able to do w/o layers/tables is to literally hit "enter" and
    "tab" continuously until the cursor is somewhere close to where I
    want it to be on the page. But that seems a little old-school (for
    lack of a better term) to really be the way to do it.
    Also, if I've used a lot of layers/tables already in my
    website, is the general recommendation for be to rebuild my site
    completely w/o layers/tables, or is it feasible for me to have
    someone who knows HTML just come in and fix the actual HTML code
    for me to make it all work?
    Ideally, I just want something to help me fix this problem
    w/o having to hire someone else to come in, cause I've been working
    this site for about a year now and am just now finally getting it
    up online only to find that the way it looks online is not the way
    it looks in Dreamweaver. I'd really really appreciate any
    suggestions/advice.
    Thank you so much!

    Hello,
    The first bit of advice, which you may already be doing, it
    to learn HTML
    and CSS.
    CSS is used to style and position elements.
    Instead of adding numerous   to add spacing, for
    example, you can use
    CSS to add margins or padding to elements to move them away
    from other
    elements.
    Also, IMHO there is nothing wrong with using tables,
    specially as you learn.
    You can also use <divs> and CSS to position them (a
    table-less layout).
    There are a number of threads in this forum comparing them
    and giving many
    designer's views.
    It's Dreamweaver's "Layout Mode" you should stay away
    from.Use "Standard
    Mode"
    It creates tables with rowspanss and colspans that are very
    fragile.
    Something as simple as a user having a different text size
    setting in their
    browser than what you had in yours when you designed can make
    the page break
    apart.
    More info:
    http://apptools.com/rants/spans.php
    Also, "Layers" are an older DW term for AP Divs (Absolutely
    Positioned).
    They can cause you a lot of frustration.
    More info:
    http://apptools.com:80/examples/pagelayout101.php
    I would strongly suggest you take a couple of hours to do
    these tutorials.
    They are a great introduction to using CSS, making a
    stylesheet and using
    DW's "wizards".
    They are very well written, illustrated and easy to follow.
    I promise you will walk away with a different outlook on how
    you can design
    a page.
    They are not intended to replace learning HTML or CSS in any
    way, I just
    think it will benefit you greatly seeing what you can do.
    http://projectseven.com/tutorials/css/css_td/index.htm
    http://projectseven.com/tutorials/css/qdmacfly/index.htm
    I hope that helps.
    Take care,
    Tim
    "darkpwca" <[email protected]> wrote in
    message
    news:[email protected]...
    > I'm reading a lot about how we should not use layers and
    tables when
    > creating a
    > website in Dreamweaver because of something called
    "absolute placement"
    > (or
    > something), which is the reason the text in my website
    is constantly
    > misaligned
    > or overlapping when opened up in Firefox. Although, I've
    never had this
    > problem
    > before for the past three years I've been using
    Dreamweaver to create my
    > sites,
    > which is what's most frustrating I think.
    >
    > So, I guess I'm wondering how, then, do I create a
    webpage in Dreamweaver
    > WITHOUT using layers and tables? The only thing I've
    been able to do w/o
    > layers/tables is to literally hit "enter" and "tab"
    continuously until the
    > cursor is somewhere close to where I want it to be on
    the page. But that
    > seems
    > a little old-school (for lack of a better term) to
    really be the way to do
    > it.
    >
    > Also, if I've used a lot of layers/tables already in my
    website, is the
    > general recommendation for be to rebuild my site
    completely w/o
    > layers/tables,
    > or is it feasible for me to have someone who knows HTML
    just come in and
    > fix
    > the actual HTML code for me to make it all work?
    >
    > Ideally, I just want something to help me fix this
    problem w/o having to
    > hire
    > someone else to come in, cause I've been working this
    site for about a
    > year now
    > and am just now finally getting it up online only to
    find that the way it
    > looks
    > online is not the way it looks in Dreamweaver. I'd
    really really
    > appreciate any
    > suggestions/advice.
    >
    > Thank you so much!
    >

  • Multi layer table view/navigation controller hierarchy best practice

    Hi,
    I am new to iPad/iPhone development and wondering what the best practice for multiple layers of table views is? I understand the principle of a navigation controller providing the framework for moving up and down a list but have not yet quite got my head around if you should have one navigation controller for the whole tree or several navigation controllers.
    In my app I need to have the following:
    Main view -> window view showing some interactive elements (picker, buttons etc.)
    Setup view -> Hierarchy managed by nav controller/table views
    The setup view needs to manage the following hierarchy...
    - Level A:
    - Global app variables (one table view)
    - Level B Items (table view showing list of items at belonging to Level B)
    - Level B Item 1 (table view showing list of items at level C belonging to level B item 1)
    - Level C Item 1 (table view showing list of items at level D belonging to level C item 1)
    - Level D Item 1 (table view showing list of items at level E belonging to level D item 1)
    - Level E item (table view for properties of item at Level E)
    - Level D Item n
    - Level C Item n
    - Level B Item n
    Each level in this has some properties and then a list of child items.
    What would be the best way of structuring this? I would assume that creating a class that extends a view controller for each level is a given but what about the control of the navigation? Should this be handled by one navigation controller or one per level? I think I know the right answer but have not seen a neat way of implementing
    I think I am also best off having each level in it's own xib but, once again, am not 100% sure that this is the best design pattern.
    Many thanks in advance for any help/pointers!
    Cheers
    jez

    Hi Julian,
    I have struggled with the same questions you are addressing. On a previous project we tried to model based on packages, but during the course of the project we encountered some problems that grew overtime. The main problems were:
    1. It is hard to enforce rules on package assignments
    2. With multiple developers on the project and limited time we didn't have time to review package assignment
    3. Devopelers would click away warnings that an object was already part of another project and just continue
    4. After go-live the maintenance partner didn't care.
    So, my experience is is that it is a nice feature, but only from a high level design point of view. In real life it will get messy and above all, it doesn't add much value to the development. On my neew assignment we are just working with packages based on functional area and that works just fine.
    Roy

  • Building Websites with Layers

    I have had many problems in building websites with layers,in
    particular with Template Changes , I take it that Tables are a more
    reliable and better method then using Layers , my concern are that
    Tables from what I can see are not as easy to position and when I
    go into Layout mode and Try adding table cells I cannot put a Table
    cell at the Top of the screen , there is allways a small gap that
    leaves a White bar at the top of my website.
    So what are the Best Methods .?. Use Frames to dive up your
    page then use tables for the majority of the content with the
    occasional layer.?.

    >I have had many problems in building websites with
    layers,in particular
    >with
    > Template Changes
    These two are not related. Poor development methods will
    break in new and
    confusing ways at the drop of a pin, with no causal
    relationship between the
    two.
    > I take it that Tables are a more reliable and better
    method
    Tables are not more reliable, and they are sometimes a better
    way of doing
    certain layout requirements. Layers are a poor method to use
    for layer
    period.
    > So what are the Best Methods
    Learn HTML and learn tables and learn CSS. There are no magic
    wands here.
    You are stuck in this 'layers/frames/tables' mentality. Leave
    that at the
    door.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "SPECTRASORT" <[email protected]> wrote in
    message
    news:ehl3ab$1ro$[email protected]..
    >I have had many problems in building websites with
    layers,in particular
    >with
    > Template Changes , I take it that Tables are a more
    reliable and better
    > method
    > then using Layers , my concern are that Tables from what
    I can see are not
    > as
    > easy to position and when I go into Layout mode and Try
    adding table cells
    > I
    > cannot put a Table cell at the Top of the screen , there
    is allways a
    > small gap
    > that leaves a White bar at the top of my website.
    >
    > So what are the Best Methods .?. Use Frames to dive up
    your page then use
    > tables for the majority of the content with the
    occasional layer.?.
    >

  • Tables, CSS or XML ?

    Hi there, I'm new on WEB design and programming, I'm using
    the Studio 8 suite, and I've started from the dreamweaver "livedoc"
    to create a site, there are three different ways explained in that
    document tables, CSS levels and XML/XLT. What is the best way and
    why?
    I have some problems already to make it works with the CSS
    levels, because once I've added the colour to the levels and to the
    main page the levels aren't visible. Why? thank you.

    > tables, CSS levels and XML/XLT.
    CSS levels?
    Here's a post I have repeated (and updated) more than once
    here about layers
    and tables -
    you may find it helpful -
    > If you need to use layers, then use them. If you want to
    begin using
    > CSS-P
    > methods, then use them by all means! But learn how to
    use them first -
    >
    >
    http://www.great-web-sights.com/g_layerlaws.asp
    >
    > The word "layer" was first coined by Netscape when it
    introduced its
    > heinous
    > and ill-fated <layer> tag with NN4x. It has since
    been adopted by the
    > community to generally refer to absolutely positioned
    <div> tags, and
    > Dreamweaver has
    > propagated that usage. In fact, there is really no such
    HTML thing as a
    > layer, but for the purposes of this discussion let's use
    the Dreamweaver
    > sense of applying that term to absolutely positioned
    <div>s.
    >
    > ==============================
    > In plain talk, a layer is like a magic carpet - it
    floats above your page
    > content (any page content, including tables, images,
    text, etc.). It is
    > unaffected by page margin settings because it is not
    really *on* the page.
    > You can whisk it around on the page to provide motion
    (using timelines).
    > You can make it visible or invisible using any of the
    actions appropriate
    > to
    > your browser selection (like onMouseOver, onClick,
    onLoad, etc.). You can
    > dynamically clip or scroll the contents of layers to
    provide a windowed
    > effect within a page. Layers are wondrous constructs
    that let you bring
    > your pages to life! Get to know them - they are your
    friends....
    > =================
    >
    > I would add in clarification and elaboration that layers
    are positionable
    > elements and as such allow you to put content at any
    location you desire,
    > regardless of the remainder of the content on the page.
    >
    > The downside to layers is the flip-side of their real
    benefit. Because
    > they
    > are absolutely positioned, they will be static page
    elements, i.e., they
    > will not move to reflect changes in your browser
    viewport size *unless*
    > you
    > apply some custom javascript to the page that makes the
    layers move, or
    > *unless* you use
    > specific CSS-P techniques to make them move. There
    > is no native support in HTML for moving layers - that's
    why it must be
    > done
    > with custom js or advanced CSS.
    >
    > If you consider that a 'layer' is really just a
    'division' or <div> tag on
    > the page, and that you can use
    > CSS to position this <div> tag, as well as control
    the format of its
    > contents and how it interacts with
    > other content around it, then you can see how valuable
    it might be for use
    > as a page layout tool!
    > This impression is certainly true. As you become more
    familiar with CSS,
    > you will learn how to
    > replace a large part of your current page layout
    methodology with pure CSS
    > positioned page
    > elements. But it's something you should take your time
    with. It *is* the
    > way of the future, so at
    > some point we will all have to come to grips with using
    CSS in this
    > manner.
    >
    > Some people use layers exclusively for page layout
    because of the ease
    > with
    > which they can be positioned. I do not recommend this
    approach for anyone
    > that is new to layers or to CSS in general because it
    can be confusing and
    > troublesome. This is partucularly the case if you will
    have multiple
    > layers, each
    > containing nominally uncontrolled/unstyled text. Viewers
    resizing this
    > text in their
    > browsers will see a disappointing overlap of paragraphs
    that is surely NOT
    > what you desire.
    >
    >
    http://www.great-web-sights.com/g_layer-overlap.asp
    >
    > Tables, on the other hand, are most everything that
    layers are not! They
    > are flexible page elements, in that native HTML can
    center, or right or
    > left
    > align a table - in other words, they can float around on
    your page
    > depending
    > on the browser's viewport width. Although originally
    added to HTML as a
    > means of displaying tabular data *only*, tables quickly
    became the
    > principal
    > structural element used in page layout. They can be made
    rigid in order
    > to
    > provide a stable base for your page elements, including
    text, images,
    > Flash,
    > etc. They are easy to use and to learn (more or less),
    and behave in
    > (mostly) predictable ways across browser and platform
    combinations - but
    > there are quirks that must be learned to use them
    successfully. Luckily,
    > most of these quirks are discussed here daily and are
    illuminated on the
    > several sites devoted to Dreamweaver/HTML issues,
    including the Macromedia
    > Technotes link in my sig below. In spite of these
    quirks, however, if you
    > intend
    > to be a credible web developer, you must learn how to
    build stable tables
    > with
    > your hands behind your back!
    >
    > So - to summarize...
    >
    > If you want motion on your page, you must use layers. If
    you want bedrock
    > for your page layout, you must use tables at this point.
    Or not
    > (particularly when you
    > consider what you can do with CSS positioned page
    elements and NO tables
    > at
    > all -
    http://www.csszengarden.com).
    And make sure that you understand this -
    http://apptools.com/examples/pagelayout101.php
    >
    > Bear in mind that advanced use of these two page
    elements can
    > *significantly* blur these two criteria.
    >
    > And remember, the use of one does not preclude the use
    of the other on the
    > same page.
    > Use them both if the spirit moves you.
    >
    > There you go....
    >
    >
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "Francesco Marchese" <[email protected]>
    wrote in message
    news:[email protected]...
    > Hi there, I'm new on WEB design and programming, I'm
    using the Studio 8
    > suite,
    > and I've started from the dreamweaver "livedoc" to
    create a site, there
    > are
    > three different ways explained in that document tables,
    CSS levels and
    > XML/XLT. What is the best way and why?
    > I have some problems already to make it works with the
    CSS levels, because
    > once I've added the colour to the levels and to the main
    page the levels
    > aren't visible. Why? thank you.
    >

  • Working with layers with centered page

    Is it possible to work with layers (Draw Layer) when you want
    your site to
    be centered. So far I´ve worked with centered (middle)
    Layout Table, but
    then I have to work with Laoyt Cells - i.e. I cannot use
    layers.

    Of course you can use layers with tables. Just work in
    Standard mode, not
    layout mode to do that. And please take the time to learn
    about layers
    before you use them -
    http://www.great-web-sights.com/g_layerlaws.asp
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "ojorus" <[email protected]> wrote in message
    news:epckvr$spo$[email protected]..
    > Is it possible to work with layers (Draw Layer) when you
    want your site to
    > be centered. So far I´ve worked with centered
    (middle) Layout Table, but
    > then I have to work with Laoyt Cells - i.e. I cannot use
    layers.
    >
    >
    >

  • Centering pages built with layers

    I've built a website using layers (not tables) in GoLive (Windows). How do I center it in the browser window? (Because my layers overlap, I can't put them into a table.) Is it possible?

    > Is it possible?
    Certainly, although when you finish you will still have a sow's ear of
    problems with content in your absolutely positioned containers ('layers').
    Do you know about those? The most troublesome one is the one that occurs
    when you browse to the page and increase the browser's text size display.
    The problem is caused by the inherent nature of absolute positioned
    elements - they expand vertically (or even overflow if a height has been
    specified for them) without regard for any other content on the page.
    At any rate here's how to center -
    It depends on whether you are using absolute positioning on the page, as to
    which method might be best, but in either event, this will work -
    Change this -
    to this -
    #wrapper { width:760px; margin:0 auto;position:relative; }
    /* 760px will display on an 800px screen maximized browser window without */
    /* horizontal scrollbars. */
    change this -
    (the ellipsis represents any other attributes that might be mentioned in the
    body tag, and SHOULD NOT BE INCLUDED EXPLICITLY!)
    to this -
    and this -
    to this -
    and see if that helps.
    Murray

  • HOW TO: Add /manipulate columns for a GridControl

    HOW TO: Add /manipulate columns for a GridControl when the columns (attributes) are from different entity objects.
    This HOWTO describes the basic steps of using attributes from different entity objects for a GridControl.
    One way you can create a GridControl which contain attributes from different entity objects is to create a view object and base it on the entity objects which contain
    the desired attributes.
    Here are the basic steps:
    1.Create a new view object (or use an existing view object) by selecting File>New from the menu, clicking the Business Components tab and double-clicking
    on the View Object icon.
    2.In the View Object wizard change the name to something meaningful.
    3.Select the entity objects you will base your view object on.
    4.Nivigate to the attribute screen and select the attributes you would like to include in your view object from each entity object. At this point you can also create
    a new attribute by clicking the "New" button. The new attribute can be a concatenation of other attributes, derived from a calculation etc.
    5.In the query panel of the View Object wizard, click "Expert mode" and enter a query statement. You write complex queries such as decoding a set of attribute
    values.
    6.Add your newly to your newly created view object to the application module by double-clicking on the application module in the navigation pane and selecting
    your view object from the list.
    7.Create a new row set.
    8.Bind row set to a query by editing their queryinfo property and selecting your view object and its attributes from the queryInfo pane.
    9.Create a GridControl and bind it to the row set by editing the dataItemName property of the GridControl. Since the GridControl is bound at the row set level
    all of the related attributes are automatically added.
    null

    Michael,
    Are you intending this as a commercial solution or a work around?
    To take an existing equivalent, one would build a view in the database tailored for each grid in an Oracle Forms application. Or a separate query layered over tables for each form/grid in a Delphi or Access application? Even if it is ninety nine percent the same over half a dozen forms/grids?
    And now you've added a whole slew of "slightly different" rowSetInfos to maintain.
    So if you wanted to add a column that needs to appear everywhere... you've just increased the workload multi-fold?
    That would be a management nightmare, wouldn't it? Not to mention yet more performance cost and a slower system?
    Hmmmm..... I'm not sure I like where this is headed... someone needs to do some convincing...
    null

  • How to add Navigation attributes values via ABAP while creation of CVC

    Hi,
    I have a requirement like, I have to add navigational attributes to the cvc record while CVC creation ( /sapapo/mc62 transaction).
    There were two scenarios: 1. Usually when they load master data from BW side those navigation attributes available and when we do CVC creation it's automatically picks those values. If NOT then i have to bring Market segment and Business unit navigational attributes values from ECC via RFC function module by passing MPN and End customer division as a input.
    I am facing problem when BW side if business unit and Market segment were blank.
    Do we have any Function modules available to add navigational attributes data and should update corresponding master data tables.
    Please help me step by step process on this.
    Thanks
    Ravi
    Edited by: REDDY KALLURI on Jan 22, 2011 10:30 PM

    Michael,
    Are you intending this as a commercial solution or a work around?
    To take an existing equivalent, one would build a view in the database tailored for each grid in an Oracle Forms application. Or a separate query layered over tables for each form/grid in a Delphi or Access application? Even if it is ninety nine percent the same over half a dozen forms/grids?
    And now you've added a whole slew of "slightly different" rowSetInfos to maintain.
    So if you wanted to add a column that needs to appear everywhere... you've just increased the workload multi-fold?
    That would be a management nightmare, wouldn't it? Not to mention yet more performance cost and a slower system?
    Hmmmm..... I'm not sure I like where this is headed... someone needs to do some convincing...
    null

  • HELP...images not showing up in internet explorer, but show up in Safari

    Somebody please help. My images are showing up fine in Safari
    but when I view them with internet explorer they show an x and
    won't open. I am using layers and tables. Please help!
    Here is my webpage if you need to see code.
    http://www.puddlefoot.com/Tees.html
    Thanks!

    Yonion.jpg is in CMYK colorspace, that's why it doesn't
    display in most
    browsers.
    make it an optimized RGB jpeg file.
    Alan
    Adobe Community Expert, dreamweaver
    http://www.adobe.com/communities/experts/

Maybe you are looking for

  • Meggaging server security problem

    Hi All, We have messaging server 7.3 and convergence 1_U3. Client site we are using Iexplorer 7.X and Mozilla 3.X . Now we are facing problem is, If we shut down the system with out logging messaging server console. Next login is not asking user name

  • Bapi for address change

    hi friend, i change  customer telephone noumber in revelent T.code in my R/3 system and i want to update this change in CRM system so kindly give me sutiable bapi for this change.

  • Overhead costing sheet in easy cost planning

    Hello, I have created a overhead costing sheet (having base as material cost elements where a %age is defined to be applied on the material cost) and attached it to the valuation variant of easy cost planning in PS module. Now for a given project whe

  • Is it possible to un Webdynpro java without SAP EP?

    Hi, I have a unique requirement. My customer is new to SAP EP / Java Webdynpro. He requires Webdynpro components to run without SAP EP. In other words, he wants create an ALIAS for Webdynpro component URL which is displayed when we run the component

  • Master page doubts

    Dear All, I have used ID only rarely, for single page documents but this time I'm trying to make a several pages manual and I can't seem to get around the very first steps (even though I tried following tutorials and help): 1st problem: I have a coup