Cafe Townsend

My 12 year old and I are trying to learn how to use
dreamweaver. We are doing the cafe Townsend tutorial and are
failing to insert the Flash slide show onto the page. We get two of
the menus and no pictures. The slide show is thereand can be opened
in Flash. We've tried dragging the file fro the file panel and
looked at the code which seems to have the correct relative file
path. Can anyone help?
cheers
mickmac1

C:/Program Files/Macromedia/Flash8/Samples and
Tutorials/Tutorial Assets
The instructions do point out this path
"woudanna" <[email protected]> wrote in
message
news:et2qgk$knc$[email protected]..
>I am VERY novice to web design and I have problem in the
tutorial, chapter
>3 of
> the book "Getting started with Dreamweaver" at #1:
Finding the Dreamweaver
> application folder, #2: Locate the Cafe Townsend and #3:
Copy it to a
> local
> site folder I created, so I could move on with this
tutorial.
> Thank you for the hints!
> By the way, should I be on line while constructing that
tutorial sample
> site?
>

Similar Messages

Cafe townsend demo in dreamweaver help

In dreamweaver Studio 8 there is help menu at top and it
takes you thru for beginners. There is an example site called Cafe
townsend and on it has a 'next button" that rotates images. How do
you create that look with text on one side and images on the other
and how do you get them to rotate?
Thanks in Advance,
Dennis

Right. It's an empty local site folder until you put something into it.
Go to step 2. Download and unzip the Check_Magazine.Zip files
http://download.macromedia.com/pub/developer/check_magazine.zip
Go to step 3. Copy the check_magazine folder into your local_sites folder (Cafe Townsend).
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
www.alt-web.com/
www.twitter.com/altweb
www.alt-web.com/blogspot.com

Cafe Townsend... SOS

I am VERY novice to web design and I have problem in the
tutorial, chapter 3 of the book "Getting started with Dreamweaver"
at #1: Finding the Dreamweaver application folder, #2: Locate the
Cafe Townsend and #3: Copy it to a local site folder I created, so
I could move on with this tutorial.
Thank you for the hints!
By the way, should I be on line while constructing that
tutorial sample site?

C:/Program Files/Macromedia/Flash8/Samples and
Tutorials/Tutorial Assets
The instructions do point out this path
"woudanna" <[email protected]> wrote in
message
news:et2qgk$knc$[email protected]..
>I am VERY novice to web design and I have problem in the
tutorial, chapter
>3 of
> the book "Getting started with Dreamweaver" at #1:
Finding the Dreamweaver
> application folder, #2: Locate the Cafe Townsend and #3:
Copy it to a
> local
> site folder I created, so I could move on with this
tutorial.
> Thank you for the hints!
> By the way, should I be on line while constructing that
tutorial sample
> site?
>

Cafe Townsend Tutorial Modification

Help! I'm trying to put together a simple picture slide show
very similar to the flash_fma.fla file found in the Cafe Townsend
tutorial—but automated, with just a pause between the change
in images, and not using the next button. I know there must be
samples of that simple file type out there somewhere, but I can't
seem to find any, and I'm not yet familiar enough with the
ActionScript syntax to know what would be the best way to go. Can
anyone give me some advice or point me to an example file? The Cafe
Townsend file uses the stop() function in each of the image
keyframes and addEventListener to move the images with a button
click in the actions layer.
Thanks,
Gene Ryan

sounds like you may have crossdomain issues - serach help for
crossdomain.xml file
"jason_sot" <[email protected]> wrote in
message
news:eo4ihs$r68$[email protected]..
>I am fairly new to flash but had created a biz proposal
mimicking the cafe
> townsend tutorial. I created a web page to display the
swf file and
> uploaded
> it. Once uploaded, the swf file is not pulling in the
external images. I
> duplicated the structure on a testing server and it
works perfectly but
> when i
> post it to our server, the background images are not
showing up.
>
> I found this page
>
http://livedocs.macromedia.com/dreamweaver/8/using/wwhelp/wwhimpl/common/html/ww
> help.htm?context=LiveDocs_Parts&file=gs_05_a9.htm
> where comments are posted about some other people having
the same issue
> and
> one guy that says he figured it out. Me and our IT guy
have been messing
> with
> this ALL DAY LONG and have not found any way to get the
images to show.
>
> Any ideas??????
>

Movie clip cafe townsend.

http://www.adobe.com/devnet/dreamweaver/articles/first_website_pt1.html zip file/ fla.
Hi,
How do I make movie clip /banner like cafe townsend with Flash CS3?

Hi Kglad
how shall I make movie clip? I want to learn movie clip . Can you help me please.? I like your web site. lines to dance.

How do I look up how to put Cafe townsend tutorial into dreamweaver

How do I ask how to put Cafe Townsend Tutorial into dreamweaver. I have a mac. The tutorial notes say follow this line
(Mac OS X) Macintosh HD/Users/your_user_name/Documents/local_site. I don't understand what each section means. If someone called explain it that would be great as I ended up with an empty folder in dreamweaver with the name 'Cafe Townsend' on it. Thank you

Right. It's an empty local site folder until you put something into it.
Go to step 2. Download and unzip the Check_Magazine.Zip files
http://download.macromedia.com/pub/developer/check_magazine.zip
Go to step 3. Copy the check_magazine folder into your local_sites folder (Cafe Townsend).
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
www.alt-web.com/
www.twitter.com/altweb
www.alt-web.com/blogspot.com

Townsend php file not showing using mamp

Hi
I'm not sure exactly whether to publish this question in the general dw forum or php forum, so please bear with me.
Thank you in advance for your help.
I am using dw cs3 and am currently doing the David Powers tutorial on setting up a MAMP site for PHP using the Cafe Townsend detail and the comments.php file.
My MAMP is set up with the Apache port on 8888, and the SQL port on 8889.
(This has worked fine as a localhost for sites built with both xhtml and xsl so I think the problem may be the SQL)
The fact that the timetest.php displays fine in both Safari and Firefox supports this view.
In both Firefox and Safari, the following addess displays:
http://localhost:8888/php_test/comments.php
But the page remains blank.
In Live Data I am told that the problem is:
1 - the testing server is not executing php files, or
2 - or the folder does not map to the testing server (the fact that the timetest works suggests it does)
Dw tells me the connection has been made successfully on:
localhost:8889
The column fields from the sql database, appear in the databases window with (text required etc, as a parameter behind them).
Am I doing something wrong, or could the comments.php file be corrupt?
Please help.
Tx.
Regards,
Gordon Eddey

Murray, you superstar. Thanks.
It's 17h37 here in Johannesburg,so I'll go on line later and mark the
question answered, as the broadband becomes fat and sluggish at this hour.
Using the suggested:
<?php ini_set('display_errors',1); ?>
Showed me that the file was still picking up an earlier
('Connections/connTest.php');
in which I had taxed up the settings and had replaced with
('Connections/phptest.php').
Simply changing to ('Connections/phptest.php'); and replacing the
connTest.php file with phptest.php throughout the page resulted in the file
working.
I have to say that you have helped me most of my dw3 questions and I thank
you for that.
Regards,
Gordon

Can't View Live Data in DW8

I am trying to view MS Access database records in a jsp page
using Dreamweaver 8.0.2 (as part of the Cafe Townsend tutorial)
In the Databases panel I can see the database objects. The
test to database connection successfuly returns database records.
However, when I click on LIVE DATA VIEW icon, a red exclamation
mark(!) appears next to the Recordset(rs_Comment) #prior version#
line of the Server Behaviors tab.
When I select this line and double-click a message box
saying: "This server behavior was created with a prior version of
UltraDev. It will be replaced with the current version when you
click OK in the server behavior dialog box." appears. I hit OK in
the box, and hit OK in the Recordset dialog box that also appears.
The exclamation marked line disappears from the Server Behavior
tabbed pane, but the problem remains unsolved.
I uninstalled and reinstalled DW8, but the problem persists.
Any help would be appreciated.

"RogerLH" <[email protected]> wrote in
message
news:fgnke1$qqi$[email protected]..
> I am trying to view MS Access database records in a jsp
page using
> Dreamweaver
> 8.0.2 (as part of the Cafe Townsend tutorial)
>
> In the Databases panel I can see the database objects.
The test to
> database
> connection successfuly returns database records.
However, when I click on
> LIVE
> DATA VIEW icon, a red exclamation mark(!) appears next
to the
> Recordset(rs_Comment) #prior version# line of the Server
Behaviors tab.
>
> When I select this line and double-click a message box
saying: "This
> server
> behavior was created with a prior version of UltraDev.
It will be replaced
> with
> the current version when you click OK in the server
behavior dialog box."
> appears. I hit OK in the box, and hit OK in the
Recordset dialog box that
> also
> appears. The exclamation marked line disappears from the
Server Behavior
> tabbed
> pane, but the problem remains unsolved.
>
> I uninstalled and reinstalled DW8, but the problem
persists.
>
> Any help would be appreciated.
Does the code get changed in any way, or does the code stay
exactly the same
and is dreamweaver somehow not recognizing it anymore?
Joris

Can't View Live Data in DW8 Tutorial

I am trying to view MS Access database records in a jsp page
using Dreamweaver 8.0.2 (as part of the Cafe Townsend tutorial)
In the Databases panel I can see the database objects. The
test to database connection successfuly returns database records.
However, when I click on LIVE DATA VIEW icon, a red exclamation
mark(!) appears next to the Recordset(rs_Comment) #prior version#
line of the Server Behaviors tab.
When I select this line and double-click a message box
saying: "This server behavior was created with a prior version of
UltraDev. It will be replaced with the current version when you
click OK in the server behavior dialog box." appears. I hit OK in
the box, and hit OK in the Recordset dialog box that also appears.
The exclamation marked line disappears from the Server Behavior
tabbed pane, but the problem remains unsolved.
I uninstalled and reinstalled DW8, but the problem persists.
Any help would be appreciated.

quote:
Originally posted by:
RogerLH
I am trying to view MS Access database records in a jsp page
using Dreamweaver 8.0.2 (as part of the Cafe Townsend tutorial)
In the Databases panel I can see the database objects. The
test to database connection successfuly returns database records.
However, when I click on LIVE DATA VIEW icon, a red exclamation
mark(!) appears next to the Recordset(rs_Comment) #prior version#
line of the Server Behaviors tab.
When I select this line and double-click a message box
saying: "This server behavior was created with a prior version of
UltraDev. It will be replaced with the current version when you
click OK in the server behavior dialog box." appears. I hit OK in
the box, and hit OK in the Recordset dialog box that also appears.
The exclamation marked line disappears from the Server Behavior
tabbed pane, but the problem remains unsolved.
I installed and reinstalled DW8, but the problem persists.
Any help would be appreciated.
I'm new to the Forum and DW I need some help saving a file
and then opening back up in the interface lol

Spry menu bar places vertically, not horizontally?

I followed the tutorial on using the widget browser to download Spry Menu Bar 2.0 and after configuring for a horizontal bar placed the bar in the tutorial index.html. The placement results in a vertical menu bar. What am I doing wrong?
SPRY CODE
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
<title>Spry Menu Bar - Basic : tcm.menu</title>
<link type='text/css' href='Spry-UI-1.7/css/Menu/basic/SpryMenuBasic.css' rel='stylesheet'/>
<script type='text/javascript' src='Spry-UI-1.7/includes/SpryDOMUtils.js'></script>
<script type='text/javascript' src='Spry-UI-1.7/includes/SpryDOMEffects.js'></script>
<script type='text/javascript' src='Spry-UI-1.7/includes/SpryWidget.js'></script>
<script type='text/javascript' src='Spry-UI-1.7/includes/SpryMenu.js'></script>
<script type='text/javascript' src='Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarKeyNavigationPlugin.js'></script>
<script type='text/javascript' src='Spry-UI-1.7/includes/plugins/MenuBar2/SpryMenuBarIEWorkaroundsPlugin.js'></script>
<style type="text/css">
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
These assume the following widget classes for menu layout (set in a preset)
.MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
.MenuBarVertical - vertical main bar; all submenus are pull-right.
You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
They only apply to horizontal menu bars:
MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
and centered in its parent container.
MenuBarFullwidth - Grows to fill its parent container width.
In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
background-color:#b0c9d9;
font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
MenuItem, and MenuItemLabel
at a given level all use same definition for ems.
Note that this means the size is also inherited to child submenus,
so use caution in using relative sizes other than
100% on submenu fonts. */
font-weight: bold;
font-size: 18px;
font-style: normal;
padding:0;
border-color: #cddce7 #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
display:none;
.MenuBarLeftShrink {
float: left; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuBarRightShrink {
float: right; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuBarFixedLeft {
float: left;
width: 960px;
.MenuBarFixedCentered {
float: none;
width: 960px;
margin-left:auto;
margin-right:auto;
.MenuBarFixedCentered br {
clear:both;
display:block;
.MenuBarFixedCentered .SubMenu br {
display:none;
.MenuBarFullwidth {
float: left;
width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
padding: 0px 0px 0px 0px;
margin: 0; /* Zero out margin on the item containers. The MenuItem is the active hover area.
For most items, we have to do top or bottom padding or borders only on the MenuItem
or a child so we keep the entire submenu tiled with items.
Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
padding: 0px 10px 0px 0px;
background-color:transparent;
border-width:2px;
border-color: #cddce7 #5c6a72 #5c6a72 #cddce7;
border-style: solid solid solid solid;
#MenuBar .MenuItemFirst {
border-style: solid solid solid solid;
#MenuBar .MenuItemLast {
border-style: solid solid solid solid;
#MenuBar .MenuItem .MenuItemLabel{
text-align:center;
line-height:1.4em;
color:#333333;
background-color:transparent;
padding: 6px 15px 6px 25px;
width: 138px;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif;
font-weight: bold;
font-size: 16px;
font-style: normal;
background-color:#677e8c;
padding:0px 2px 0px 0px;
border-width:1px;
border-color: #cccccc #cccccc #cccccc #cccccc;
/* Border styles are overriden by first and last items */
border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
text-align:left;
line-height:1em;
background-color:transparent;
color:#ffffff;
padding: 6px 12px 6px 5px;
width: 171px;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
background-color: #677e8c;
border-color: #697278 #b8c4ca #b8c4ca #697278;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
background-color: transparent; /* consider exposing this prop separately*/
color: #ffffff;
#MenuBar .MenuItemHover .MenuItemLabel{
background-color: transparent;
color: #ffffff;
#MenuBar .SubMenu .MenuItemHover {
background-color: #b0c9d9;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
background-color: transparent;
color: #000000;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
background-color: transparent;
min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
border-color: #ffffff #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
top: 100%; /* 100% is at the bottom of parent menuItemContainer */
left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
and your personal taste.
0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
on MenuItemContainer and MenuItem on the parent
menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
the dropdown with the left of the menu item label.*/
z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
top: 0px;
left:100%;
min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
background-color: transparent;
min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
top: 0px; /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
vertically 'centered' on its invoking item */
left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
background-color: transparent; /* consider exposing this prop separately*/
color: #ffffff;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
background-color: transparent; /* consider exposing this prop separately*/
color: #000000;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
</style>
</head>
<body>
<ul id="MenuBar">
<li> <a href="#">Home</a> </li>
<li> <a href="#">Entertainment</a>
<ul>
    <li> <a href="#">TV Listings</a> </li>
    <li> <a href="#">Music</a>
      <ul>
        <li> <a href="#">Hits</a> </li>
        <li> <a href="#">Ragga</a>
          <ul>
            <li> <a href="#">Roots</a> </li>
            <li> <a href="#">Reggaeton</a> </li>
            <li> <a href="#">Dancehall</a> </li>
          </ul>
        </li>
        <li> <a href="#">Country</a> </li>
      </ul>
    </li>
    <li> <a href="#">The Dirt</a>
      <ul>
        <li> <a href="#">Hollywood</a> </li>
        <li> <a href="#">NY Beat</a> </li>
        <li> <a href="#">London Scene</a> </li>
      </ul>
    </li>
    <li> <a href="#">The Web</a> </li>
</ul>
</li>
<li> <a href="#">Politics</a> </li>
<li> <a href="#">Sports</a>
    <ul>
      <li> <a href="#">Football</a> </li>
      <li> <a href="#">Baseball</a> </li>
      <li> <a href="#">Basketball</a> </li>
      <li> <a href="#">Racing</a>
        <ul>
          <li> <a href="#">F1</a> </li>
          <li> <a href="#">Indy Car</a> </li>
          <li> <a href="#">Stock Car</a> </li>
        </ul>
</li>
    </ul>
</li>
</ul>
<script type="text/javascript">
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetID: "MenuBar",
widgetClass: "MenuBar MenuBarLeftShrink",
insertMenuBarBreak: true,
      mainMenuShowDelay: 100,
      mainMenuHideDelay: 200,
      subMenuShowDelay: 200,
      subMenuHideDelay: 200
</script>
</body>
</html>
INDEX.HTML
<!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>Bayside Pulse</title>
<link href="styles/bayside.css" rel="stylesheet" type="text/css" />
<style type="text/css">
</style>
<link href="file:///C|/Users/John Bachelor/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eam5844.tmp/Spry-UI-1.7/css/Menu/basic/SpryMenuBasic. css" rel="stylesheet" type="text/css" />
<script src="file:///C|/Users/John Bachelor/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eam5844.tmp/Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="file:///C|/Users/John Bachelor/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eam5844.tmp/Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="file:///C|/Users/John Bachelor/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eam5844.tmp/Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
<script src="file:///C|/Users/John Bachelor/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eam5844.tmp/Spry-UI-1.7/includes/SpryMenu.js" type="text/javascript"></script>
<script src="file:///C|/Users/John Bachelor/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eam5844.tmp/Spry-UI-1.7/includes/plugins/MenuBar2/Spr yMenuBarKeyNavigationPlugin.js" type="text/javascript"></script>
<script src="file:///C|/Users/John Bachelor/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eam5844.tmp/Spry-UI-1.7/includes/plugins/MenuBar2/Spr yMenuBarIEWorkaroundsPlugin.js" type="text/javascript"></script>
<style type="text/css">
/* BeginOAWidget_Instance_2141544: #MenuBar */
/* Settable values for skinning a Basic menu via presets. If presets are not sufficient, most skinning should be done in
these rules, with the exception of the images used for down or right pointing arrows, which are in the file SpryMenuBasic.css
These assume the following widget classes for menu layout (set in a preset)
.MenuBar - Applies to all menubars - default is horizontal bar, all submenus are vertical - 2nd level subs and beyond are pull-right.
.MenuBarVertical - vertical main bar; all submenus are pull-right.
You can also pass in extra classnames to set your desired top level menu bar layout. Normally, these are set by using a preset.
They only apply to horizontal menu bars:
MenuBarLeftShrink - The menu bar will be horizontally 'shrinkwrapped' to be just large enough to hold its items, and left aligned
MenuBarRightShrink - Just like MenuBarLeftShrink, but right aligned
MenuBarFixedLeft - Fixed at a specified width set in the rule '.MenuBarFixedLeft', and left aligned.
MenuBarFixedCentered - - Fixed at a specified width set in the rule '.MenuBarFixedCentered',
and centered in its parent container.
MenuBarFullwidth - Grows to fill its parent container width.
In general, all rules specified in this file are prefixed by #MenuBar so they only apply to instances of the widget inserted along
with the rules. This permits use of multiple MenuBarBasic widgets on the same page with different layouts. Because of IE6 limitations,
there are a few rules where this was not possible. Those rules are so noted in comments.
#MenuBar {
background-color:#b0c9d9;
font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif; /* Specify fonts on on MenuBar and subMenu MenuItemContainer, so MenuItemContainer,
MenuItem, and MenuItemLabel
at a given level all use same definition for ems.
Note that this means the size is also inherited to child submenus,
so use caution in using relative sizes other than
100% on submenu fonts. */
font-weight: bold;
font-size: 18px;
font-style: normal;
padding:0;
border-color: #cddce7 #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
/* Caution: because ID+class selectors do not work properly in IE6, but we want to restrict these rules to just this
widget instance, we have used string-concatenated classnames for our selectors for the layout type of the menubar
in this section. These have very low specificity, so be careful not to accidentally override them. */
.MenuBar br { /* using just a class so it has same specificity as the ".MenuBarFixedCentered br" rule bleow */
display:none;
.MenuBarLeftShrink {
float: left; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuBarRightShrink {
float: right; /* shrink to content, as well as float the MenuBar */
width: auto;
.MenuBarFixedLeft {
float: left;
width: 960px;
.MenuBarFixedCentered {
float: none;
width: 960px;
margin-left:auto;
margin-right:auto;
.MenuBarFixedCentered br {
clear:both;
display:block;
.MenuBarFixedCentered .SubMenu br {
display:none;
.MenuBarFullwidth {
float: left;
width: 100%;
/* Top level menubar items - these actually apply to all items, and get overridden for 1st or successive level submenus */
#MenuBar .MenuItemContainer {
padding: 0px 0px 0px 0px;
margin: 0; /* Zero out margin on the item containers. The MenuItem is the active hover area.
For most items, we have to do top or bottom padding or borders only on the MenuItem
or a child so we keep the entire submenu tiled with items.
Setting this to 0 avoids "dead spots" for hovering. */
#MenuBar .MenuItem {
padding: 0px 10px 0px 0px;
background-color:transparent;
border-width:2px;
border-color: #cddce7 #5c6a72 #5c6a72 #cddce7;
border-style: solid solid solid solid;
#MenuBar .MenuItemFirst {
border-style: solid solid solid solid;
#MenuBar .MenuItemLast {
border-style: solid solid solid solid;
#MenuBar .MenuItem .MenuItemLabel{
text-align:center;
line-height:1.4em;
color:#333333;
background-color:transparent;
padding: 6px 15px 6px 25px;
width: 138px;
.SpryIsIE6 #MenuBar .MenuItem .MenuItemLabel{
width:1em; /* Equivalent to min-width in modern browsers */
/* First level submenu items */
#MenuBar .SubMenu .MenuItem {
font-family: "Lucida Sans Unicode", "Lucida Grande", sans-serif;
font-weight: bold;
font-size: 16px;
font-style: normal;
background-color:#677e8c;
padding:0px 2px 0px 0px;
border-width:1px;
border-color: #cccccc #cccccc #cccccc #cccccc;
/* Border styles are overriden by first and last items */
border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst {
border-style: solid solid none solid;
#MenuBar .SubMenu .MenuItemFirst .MenuItemLabel{
padding-top: 6px;
#MenuBar .SubMenu .MenuItemLast {
border-style: solid solid solid solid;
#MenuBar .SubMenu .MenuItemLast .MenuItemLabel{
padding-bottom: 6px;
#MenuBar .SubMenu .MenuItem .MenuItemLabel{
text-align:left;
line-height:1em;
background-color:transparent;
color:#ffffff;
padding: 6px 12px 6px 5px;
width: 171px;
/* Hover states for containers, items and labels */
#MenuBar .MenuItemHover {
background-color: #677e8c;
border-color: #697278 #b8c4ca #b8c4ca #697278;
#MenuBar .MenuItemWithSubMenu.MenuItemHover .MenuItemLabel{
background-color: transparent; /* consider exposing this prop separately*/
color: #ffffff;
#MenuBar .MenuItemHover .MenuItemLabel{
background-color: transparent;
color: #ffffff;
#MenuBar .SubMenu .MenuItemHover {
background-color: #b0c9d9;
border-color: #cccccc #cccccc #cccccc #cccccc;
#MenuBar .SubMenu .MenuItemHover .MenuItemLabel{
background-color: transparent;
color: #000000;
/* Submenu properties -- First level of submenus */
#MenuBar .SubMenuVisible {
background-color: transparent;
min-width:0%; /* This keeps the menu from being skinnier than the parent MenuItemContainer - nice to have but not available on ie6 */
border-color: #ffffff #ffffff #ffffff #ffffff;
border-width:0px;
border-style: none none none none;
#MenuBar.MenuBar .SubMenuVisible {/* For Horizontal menubar only */
top: 100%; /* 100% is at the bottom of parent menuItemContainer */
left:0px; /* 'left' may need tuning depending upon borders or padding applied to menubar MenuItemContainer or MenuItem,
and your personal taste.
0px will left align the dropdown with the content area of the MenuItemContainer. Assuming you keep the margins 0
on MenuItemContainer and MenuItem on the parent
menubar, making this equal the sum of the MenuItemContainer & MenuItem padding-left will align
the dropdown with the left of the menu item label.*/
z-index:10;
#MenuBar.MenuBarVertical .SubMenuVisible {
top: 0px;
left:100%;
min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse */
/* Submenu properties -- Second level submenu and beyond - these are visible descendents of .MenuLevel1 */
#MenuBar .MenuLevel1 .SubMenuVisible {
background-color: transparent;
min-width:0px; /* Do not neeed to match width to parent MenuItemContainer - items will prevent total collapse*/
top: 0px; /* If desired, you can move this down a smidge to separate top item''s submenu from menubar -
that is really only needed for submenu on first item of MenuLevel1, or you can make it negative to make submenu more
vertically 'centered' on its invoking item */
left:100%; /* If you want to shift the submenu left to partially cover its invoking item, you can add a margin-left with a
negative value to this rule. Alternatively, if you use fixed-width items, you can change this left value
to use px or ems to get the offset you want. */
/* IE6 rules - you can delete these if you do not want to support IE6 */
/* A note about multiple classes in IE6.
* Some of the rules above use multiple class names on an element for selection, such as "hover" (MenuItemHover) and "has a subMenu" (MenuItemWithSubMenu),
* giving the selector '.MenuItemWithSubMenu.MenuItemHover'.
* Unfortunately IE6 does not support using mutiple classnames in a selector for an element. For a selector such as '.foo.bar.baz', IE6 ignores
* all but the final classname (here, '.baz'), and sets the specificity accordingly, counting just one of those classs as significant. To get around this
* problem, we use the plugin in SpryMenuBarIEWorkaroundsPlugin.js to generate compound classnames for IE6, such as 'MenuItemWithSubMenuHover'.
* Since there are a lot of these needed, the plugin does not generate the extra classes for modern browsers, and we use the CSS2 style mutltiple class
* syntax for that. Since IE6 both applies rules where
* it should not, and gets the specificity wrong too, we have to order rules carefully, so the rule misapplied in IE6 can be overridden.
* So, we put the multiple class rule first. IE6 will mistakenly apply this rule. We follow this with the single-class rule that it would
* mistakenly override, making sure the misinterpreted IE6 specificity is the same as the single-class selector, so the latter wins.
* We then create a copy of the multiple class rule, adding a '.SpryIsIE6' class as context, and making sure the specificity for
* the selector is high enough to beat the single-class rule in the "both classes match" case. We place the IE6 rule at the end of the
* css style block to make it easy to delete if you want to drop IE6 support.
* If you decide you do not need IE6 support, you can get rid of these, as well as the inclusion of the SpryMenuBarIEWorkaroundsPlugin.js script.
* The 'SpryIsIE6' class is placed on the HTML element by the script in SpryMenuBarIEWorkaroundsPlugin.js if the browser is Internet Explorer 6. This avoids the necessity of IE conditional comments for these rules.
.SpryIsIE6 #MenuBar .MenuBarView .MenuItemWithSubMenuHover .MenuItemLabel /* IE6 selector */{
background-color: transparent; /* consider exposing this prop separately*/
color: #ffffff;
.SpryIsIE6 #MenuBar .MenuBarView .SubMenu .MenuItemWithSubMenuHover .MenuItemLabel/* IE6 selector */{
background-color: transparent; /* consider exposing this prop separately*/
color: #000000;
.SpryIsIE6 #MenuBar .SubMenu .SubMenu /* IE6 selector */{
margin-left: -0px; /* Compensates for at least part of an IE6 "double padding" version of the "double margin" bug */
/* EndOAWidget_Instance_2141544 */
</style>
<script type="text/xml">

</script>
</head>
<body>
<div id="wrapper">
<div id="header"><img src="images/bayside_pulse.jpg" width="960" height="150" alt="Bayside Pulse" /></div>
<div id="nav">
    <ul id="MenuBar">
      <li> <a href="#">Home</a></li>
      <li> <a href="#">Entertainment</a>
        <ul>
          <li> <a href="#">TV Listings</a></li>
          <li> <a href="#">Music</a>
            <ul>
              <li> <a href="#">Hits</a></li>
              <li> <a href="#">Ragga</a>
                <ul>
                  <li> <a href="#">Roots</a></li>
                  <li> <a href="#">Reggaeton</a></li>
                  <li> <a href="#">Dancehall</a></li>
                </ul>
              </li>
              <li> <a href="#">Country</a></li>
            </ul>
          </li>
          <li> <a href="#">The Dirt</a>
            <ul>
              <li> <a href="#">Hollywood</a></li>
              <li> <a href="#">NY Beat</a></li>
              <li> <a href="#">London Scene</a></li>
            </ul>
          </li>
          <li> <a href="#">The Web</a></li>
        </ul>
      </li>
      <li> <a href="#">Politics</a></li>
      <li> <a href="#">Sports</a>
        <ul>
          <li> <a href="#">Football</a></li>
          <li> <a href="#">Baseball</a></li>
          <li> <a href="#">Basketball</a></li>
          <li> <a href="#">Racing</a>
            <ul>
              <li> <a href="#">F1</a></li>
              <li> <a href="#">Indy Car</a></li>
              <li> <a href="#">Stock Car</a></li>
            </ul>
          </li>
        </ul>
      </li>
    </ul>
    <script type="text/javascript">
// BeginOAWidget_Instance_2141544: #MenuBar
var MenuBar = new Spry.Widget.MenuBar2("#MenuBar", {
      widgetID: "MenuBar",
widgetClass: "MenuBar MenuBarLeftShrink",
insertMenuBarBreak: true,
      mainMenuShowDelay: 100,
      mainMenuHideDelay: 200,
      subMenuShowDelay: 200,
      subMenuHideDelay: 200
// EndOAWidget_Instance_2141544
    </script>
</div>
<div id="sidebar">
    <h3>Check This Out</h3>
    <p>Consectetur adipisicing elit, sed do eiusmod tempor incididunt quis nostrud exercitation. Lorem ipsum dolor sit amet, ut aliquip ex ea commodo consequat.</p>
    <p>Sunt in culpa qui officia deserunt ullamco laboris nisi. Duis aute irure dolor mollit anim id est laborum. Sed do eiusmod tempor incididunt ut enim ad minim veniam, in reprehenderit in voluptate.</p>
    <p>Lorem ipsum dolor sit amet, duis aute irure dolor cupidatat non proident. Sed do eiusmod tempor incididunt. </p>
</div>
<div id="maincontent">
    <h2>There’s More to San Francisco than Cafe Townsend</h2>
    <p>Sure, Cafe Townsend's cool, and Chef Ipsum provides a great range of international cuisine. But San Francisco is the city where you can weave dreams of your own. Come, explore!</p>
    <h3>Scott’s For a Night to Remember</h3>
    <p>It's certainly one you're unlikely to forget—or should that be Fegette? Lorem ipsum dolor sit amet. Ut labore et dolore magna aliqua. <img src="images/adobeduo.jpg" alt="Scott and Duane" width="400" height="233" class="floatright" />In reprehenderit in voluptate quis nostrud exercitation ut aliquip ex ea commodo consequat. Eu fugiat nulla pariatur.</p>
    <p>Velit esse cillum dolore mollit anim id est laborum. Ut enim <a href="#">ad minim veniam</a>, ullamco laboris nisi in reprehenderit in voluptate. Excepteur sint occaecat duis aute irure dolor consectetur adipisicing elit. Ut labore et dolore magna aliqua.</p>
    <p>Sed do eiusmod tempor incididunt ut enim ad minim veniam, duis aute irure dolor. Ullamco laboris nisi in reprehenderit in voluptate excepteur sint occaecat. Cupidatat non proident, sunt in culpa lorem ipsum dolor sit amet. Ut labore et dolore magna aliqua. Consectetur adipisicing elit, <a href="#">ullamco laboris nisi</a> in reprehenderit in voluptate.</p>
    <p>Eu fugiat nulla pariatur. Ut enim ad minim veniam, sunt in culpa. Ut aliquip ex ea commodo consequat.</p>
    <p>Eu fugiat nulla pariatur. Sed do eiusmod tempor incididunt in reprehenderit in voluptate velit esse cillum dolore. Ullamco laboris nisi cupidatat non proident, ut aliquip ex ea commodo consequat. Sunt in culpa ut labore et dolore magna aliqua.</p>
</div>
</div>
</body>
</html>

Please upload your file to a server and give us a link. It is extremely difficult to work with pasted-in code...much more useful to see it in working order.
Beth

Saving Projects and Organizing Files

I am having trouble storing my Sites in folders and accessing
them after I've done so. As described in the DW tutorial, I saved
the test Site (Cafe Townsend), to a folder called Local_Sites.
However, when I created a NEW Site and also tried to Save it in the
Local_Sites folder, DW told me that it would create a conflict. (In
Windows you can save many documents to one folder. Can I only save
one Site to a folder in DW?) To get around the problem, I created a
folder called Local_Sites2. When I named my next Site ("Exciting
Web Site"), and put it in Local_Sites2, and moved my mouse over the
folder, DW showed a long path (C:/........), and showed the name as
"Local_Sites2/Exciting Web Site." Finally, at other times when I
looked for a Site that I created it didn't show in DW dialog boxes.
(I notice that some folders show as green, and some as yellow). I
would like to be able to store my Sites correctly, give them root
names I intend, and retrieve the sites when I want to. Any ideas
would be appreciated. Thanks.

It would not be out of place to say that the F1 Help files
have a full and
comprehensive explanation of sites, and how to define
them....
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
==================
"Alan" <[email protected]> wrote in
message
news:C1D711A4.2B9B6D%[email protected]...
>
>
>> What's a root folder? And how do you
create/designate a root folder?
>> Thanks
>> for your help. I appreciate it.
>
> from reading your other reply- did you define a site's
local site folder
> as
> being just C: ?? the entire drive??
>
> The concept is you make a new site definition for each
site. Every
> different
> domain name is a unique site definition. You don't put a
bunch of "sites"
> into one folder and mingle the files together.
>
> Here's what most people do-
> go to where you want to store your sites on your hard
drive.
> maybe in "my documents' or anyplace else.
>
> Make a new folder, name it "sites" or "my_sites" or
"fred"
>
> Inside of that folder- make a new folder for EACH site
you want to
> create/work on.
>
> when making a site definition in dreamweaver- use the
"browse" button
> where
> it says "Local Site Folder" to drill down to the folder
for THAT site.
> You should define the local site folder to the folder
that contains this
> site's "homepage" index.html file.
>
> So after a while, using imaginary names- you'll have
something like this
> for
> Local Site Folders
> c C:\Documents
> and Settings/All Users/MyName/MyDocuments/Local
Sites/Site One
>
> C:\Documents
> and Settings/All Users/MyName/MyDocuments/Local
Sites/Site Two
>
> C:\Documents
> and Settings/All Users/MyName/MyDocuments/Local
Sites/The Other Site
>
> C:\Documents
> and Settings/All Users/MyName/MyDocuments/Local
Sites/The other other site
>
> and use Dw menu-->Sites-->OPEN SITE to change what
site you are working
> in.
> That menu will show the list of names you've given those
site definitions.
>

Photo Gallery/Slideshow Components

I am looking to make a photo gallery and want my images to be
pulled from a folder on my webserver. Does anyone know how to do
this either by a movie clip and script or by some type of
components plug-in that works well.
I am using Flash Pro 8 and really want to put together and
nice well working photogallery with multiple images but don't want
to embed them into the flash file for file size reasons.
Any help or general information would be a huge help. Thanks.
Luke

Look at the Cafe Townsend example that you can find on the
Adobe site. Choose the Tutorial: Developing a Web Application from
the DreamWeaver Live Docs site (
http://livedocs.adobe.com/dreamweaver/8/using/wwhelp/wwhimpl/js/html/wwhelp.htm)
You don't need DreamWeaver to download the files and the
flash_fma.fla file in the example site's root does what I think
you're asking.
Good luck!
Beth

Connecting to database via Dreamweaver

Hi All
I am trying to build a site using asp.net and SQL Server via
Dreamweaver.!!!! To help me on my way I decided to build a tiny
test site just to establish the connections. However, try as I
might I can’t make a connection to a database and am now
rapidly loosing the will to live due to the quite unbelievable time
I have spent trying to sort this out. Now this post is my last best
chance.
I am trying to connect to either of the databases that come
with the freebee SQL Server package (Is it called express or
something?). They are pubs and Northwind.
I am using Dreamweaver 8, XP Professional with the .Net
framework v2.0 and IIS.
However, when testing the connection in Dreamweaver I get a
choice of two different error messages depending on my
computer’s mood (I don’t change ANYTHING) The first is
the beautifully succinct and entirely unhelpful “an
unidentified error has occurred”. The second reads:
1) There is no testing server running on the server machine
2) The testing server specified for this site does not map to
the
ttp://Localhost/RootFolder/_mmServerScripts/MMHTTPDB.asp URL,
Verify that the URL Prefix maps to the root of the site.
After more hours trawling the net for answers, than I care to
admit to I decided in desperation to try out the Dreamweaver
tutorial that deals with these things (Café Townsend) to see
if it offered any clues. However, when attempting to connect to the
database (tutorial.mdb) I get the same two error messages:
“an unidentified error has occurred”.
1) There is no testing server running on the server machine
2) The testing server specified for this site does not map to
the
ttp://Localhost/MySampleApps/_mmServerScripts/MMHTTPDB.asp
URL, Verify that the URL Prefix maps to the root of the site. Again
dependent on my computer’s mood.
I am convinced that I have all the necessary components in
place and my connection strings are correct (I am aware that the
path given in the Dreamweaver tutorial for Café Townsend is
incorrect and have altered the string accordingly).
I now strongly believe the problem is something to do with
the MMHTTPDB.asp file in the _mmServerScripts folder but could
easily be wrong.
Does anyone know of a problem with Dreamweaver of this nature
or one that would result in my error message for either an Access
database or a SQL Server database?
I know Dreamweaver MX had a problem viewing database tables
whilst using .net and Adobe created a patch to fix the problem. Has
Dreamweaver 8 any similar problems?
I’m sorry this post is a bit long but trust me I could
have made it three times as long if I included everything I have
tried to resolve this!
Any help in the right direction would be appreciated more
than you can imagine.
Cheers
Burnsie

Sorry for jumping into the thread with a bit of an off topic question, but how do you find out what kind of a db the asp server is using? I've asked my company's web host a number of times for info/help in getting connected using Dreamweaver so I can redesign our site and I never hear back from them. It's a very specialized web hosting server set up for rubber stamp web sites. Looks like most of their customers use the online website design tool that they provide, but it is very limited in what it can do. Very limited.
They give me ftp access and I've changed what I can on the page, but with out access to the db it's hard to really change the look of the site.
Here's the link:
http://www.tacomarubberstamp.com

Background color missing

I'm a newbie just working on the Adobe Dreamweaver tutorial.
It instructs me to go to modify>page properties> click on the
background color box and select black (#000000). I did this and the
background color is still without color. When I open the page in
Safari, the black color is there in the background. It also is in
the code.....
I also tried this before only with a large background image.
It would not appear on the page in Dreamweaver but was in the code
and showed up when I opened it in Safari. Please advise. Thanks so
much!!
Text

This page will definitely be black in DW. Are you sure you
are looking at
the right page? Do you have styles enabled (VIEW | Style
Rendering >
Display Styles)?
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
==================
"Bennibird" <[email protected]> wrote in
message
news:[email protected]...
>
> I'm a newbie just working on the Adobe Dreamweaver
tutorial. It instructs
> me
> to go to modify>page properties> click on the
background color box and
> select
> black (#000000). I did this and the background color is
still without
> color.
> When I open the page in Safari, the black color is there
in the
> background. It
> also is in the code.....
> I also tried this before only with a large background
image. It would not
> appear on the page in Dreamweaver but was in the code
and showed up when I
> opened it in Safari. Please advise. Thanks so much!!
>
>
>
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=UTF-8" />
> <title>Cafe Townsend</title>
> <style type="text/css">
> body {
> background-color: #000000
> }
> -->
> </style>
> </head>
>
> <body>
> <table width="700" border="0" cellspacing="0"
cellpadding="0">
> <tr>
> <td height="90"><img src="" alt=""
name="banner_graphic" width="700"
> height="90" id="banner_graphic" style="background-color:
#993300" /></td>
> </tr>
> <tr>
> <td height="166"> </td>
> </tr>
> <tr>
> <td height="24"> </td>
> </tr>
> </table>
> <p> </p>
> <table width="700" border="0" cellspacing="0"
cellpadding="0">
> <tr>
> <td width="140" bgcolor="#993300"><span
class="style1"></span></td>
> <td width="230"
bgcolor="F7EEDF"> </td>
> <td width="330"
bgcolor="F7EEDF"> </td>
> </tr>
> </table>
> Cafe Townsend
> <table width="700" border="0" cellspacing="0"
cellpadding="0">
> <tr>
> <td height="24"> </td>
> </tr>
> </table>
> </body>
> </html>
>

No images in Test Movie

?I am following the Studio 8 Cafe Townsend Tutorial.
I have copy and pasted the ActionScript code that makes the
slideshow animate. In the Test Movie, the title and descriptions
are working but no images - which I have checked are in the
cafe_townsend/images folder. I am stuck!

I am working through the Studio 8 handbook / pdf which I am
following to the letter. I am wondering if I made a mistake in
Fireworks (Tutorial 7 : Handling Photographs) althoug I have the
images in cafe_townsend/images. Any ideas?

Cafe Townsend

Similar Messages

Maybe you are looking for