Converting a html template to php

How do I convert my html template to a php template? Any help
would be appreciated.
Thanks

You do not need to do anything.
"foo.dwt" can be used to create HTML, or PHP child pages.
If you really want to do it, though, you can rename foo.dwt
to foo.dwt.php
(using DW's Files panel) and let DW adjust the pages
accordingly.
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
==================
"littlemax" <[email protected]> wrote in
message
news:f1sodn$6kb$[email protected]..
> How do I convert my html template to a php template? Any
help would be
> appreciated.
>
> Thanks

Similar Messages

Convert DW html pages to PHP in Dreamweaver CS4

Created web pages in DWCS4 in html but discovered because I need some form pages to interact with MySQL that I should have created pages using DW PHP format. Is there a simple way to convert all html pages to php using dreamweaver CS4? OS is Win XP. Have access to hosting company with MySQL, PHP,PHPAdmin.

I would recommend against Nancy's suggestion here (and it's REALLY weird to see myself typing that).
I say it only because you are working within an existing site that likely already has links going to the .html file you are changing.
If you do a Save As and create a new .php file based on the still existing .html file, you will need to manually change the links on the pages that are currently pointing to the that .html file so they will point to the new .php file. You would need to either open the pages individually and fix the links, or use DW's Find & Replace feature and do a site-wide correction.
However, if you change the file extension from within the Files tab instead, DW will update any pages that link to it automatically.

SRM ITS - Modify HTML templates

Hello,
I am currently trying to understand the flow of the ITS and the SAP about how the screens are converted into HTML templates to be displayed on the web browsers. I would like to know if it is possible to modify the HTML templates and add some of our own JavaScript Validation or even add our own text field or other objects without touching the ABAP code?
Thanks,
Pramod

Hi Pramod,
You can always change the templates, If you know the standard Program ( You can get the standard program from SE80, input the template name and it gives the details of the programs related to that template) once you know the program you can do the changes in SE51( Screen painter), Input the Program name and the screen number for which this change is required.
Once you input click on Display/ change and at the top in the applicaton toolbar there will be a push button called Layout, click on that that takes you to screen painter where you can add new text fields.
For validation purpose in SRM there a badi BBP_DOC_CHECK which is used for validation purpose, but you need to do some coding depend upon your requirement
Regards
Sameer

Converting from HTML to php

Generally Dreamweaver provides good support for changes to
templates, and
automatically updates all the files using a particular
template when you change
that template. However this breaks down if you change a
template, or a file, to
.php. Dreamweaver regards this as creating a new file, and
does not offer to
update links.
My master template was basicpage.dwt. I created a new dynamic
page, copied the
guts of basicpage.dwt into it, and then saved it as basic
page.dwt.php.
I didn't really expect Dreamweaver to recognise that this was
replacing
basicpage.dwt, but when I opened the template directory I was
surprised to find
that it did not show the extensions, just two files
basicpage. So I renamed
basicpage.dwt.php to basicphpage.dwt.php so I could tell them
apart. Then I
opened index.htm, attached it to basicphpage.dwt.php,
inserted some php to
verify that it worked and resaved it as index.php. I uploaded
to my file server
and verified that the php worked. I also found that my host
system loaded
index.php by default.
Next I opened one of the existing subsidiary templates,
attached it to
basicphpage.dwt.php, and resaved it. Dreamweaver saved it
with the correct
extension, but again did not recognise that I had changed the
template.
Next I opened one of the dependent files, attached it to the
new template, and
resaved it. Again Dreamweaver regarded this as creating a new
file, and did not
offer to update links. So when I convert each template I will
then have to open
every existing page using it, manually attach the new version
of the template to
it, and manually update all the links in it, or referring to
it. Drat!
It looks as if I should only convert those pages which I want
to be dynamic, and
only do so when I am ready to add the new functionality.
Clancy

Yeah. Clancy only wants to hear his truth....
No offense, Clancy, but my dogma beats your dogma.
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
==================
"(_seb_)" <[email protected]> wrote in message
news:[email protected]...
> sorry for the dogma. I'll stop
>
> (_seb_) wrote:
>> I sure do get your point. learning all that stuff is
rather boring in
>> itself. That's what I've told myself for years,
until I dived into PHP
>> (with a book at first, but now I just go to
>>
http://us3.php.net/manual/en/)
whenever I need to learn something new.
>>
>> Once I did, and once I managed to setup a local
testing server on my
>> machine, I was surprised at how easy it was to learn
the basic stuff that
>> allows content architecture management. It took me
about two weeks to
>> learn the most useful techniques (how to generate
html code with php, how
>> to include remote files, how to use arrays, how to
use conditionals).
>>
>> Now that I know that, I enjoy building websites much
more, and I can do
>> it much faster. For one thing, you say you have 'a
total of 300 to 400
>> pages'. That's a problem with static sites. Pages
number has become an
>> irrelevant concept since I use PHP. My sites rarely
have more than 10
>> 'pages', even if the visitor can navigate through
vast ammounts of
>> content. Because PHP templates allow me to generate
pages on the fly,
>> depending on what content needs to be displayed, so
I can add content
>> without having to build new pages... That's a lot of
fun to build sites
>> that way. I also can offer much more to my clients
in terms of
>> flexibility and content management, which allows me
to charge them
>> more... Website maintenance is a breeze. If I had
known what
>> possibilities it would open and how it would
optimize my workflow, I
>> wouldn't have waited so long to dive into it.
>>
>> But of course there is a time for everything. I just
couldn't recommend
>> anything more than learning a server-side language,
to anybody who wants
>> to make a living of webdesign (and have fun doing
it).
>>
>> Clancy wrote:
>>
>>> "(_seb_)" <[email protected]> wrote:
>>>
>>>
>>>> if you use PHP I don't see why you would use
Dreamweaver templates.
>>>> You can do with PHP more, better, and fatser
in terms of content
>>>> architecture (i.e. really functional
templates) than what DM templates
>>>> can do. AND, your dynamic PHP templates
won't be dependent on
>>>> Dreamweaver's UI.
>>>
>>>
>>>
>>> I have been working on my several web sites for
about four years now,
>>> and
>>> probably have a total of 300 to 400 pages. These
work, I think they
>>> look
>>> attractive, and user feedback has been
favorable. If I had nothing
>>> better to do, I could probably spend a year or
so working out
>>> how to do the same job without using templates.
The resulting new
>>> design MIGHT
>>> be significantly easier to modify, and perhaps
even to maintain, but the
>>> new
>>> pages would probably look much the same (I like
the way they look now!),
>>> and I
>>> very much doubt if the visitor would notice the
difference.
>>> I can see that there are a number of minor
improvements I will be able
>>> to make
>>> to my sites, once I have mastered php and mysql,
but the one major
>>> incentive I
>>> have for learning them is that I have a number
of photo albums, and it
>>> will be
>>> much easier to add new photos once I have set up
a database. I have
>>> already passed my biblical 'use by' date, and I
don't feel that I have a
>>> year to throw away just to make my web sites
comply with someone else's
>>> dogma.
>>> I have a lot more material I would like to add
to my various web sites,
>>> and I
>>> feel that this would be a much more profitable
use of my remaining time,
>>> to say
>>> nothing of it being much more fun.
>>>
>>>
>>> Clancy
>>
>>
>>
>
>
> --
> seb ( [email protected])
>
http://webtrans1.com | high-end web
design
> Downloads: Slide Show, Directory Browser, Mailing List

Converting .fmb into HTML template

I am considering moving from oracle form and report builder to the APEX. Is there any ways that we could convert the existing .fmb file to html template, other than making a new one?

Hello,
Oracle is working on something like that, but till now it's not yet possible to do that in an automated way.
Regards,
Dimitri
-- http://dgielis.blogspot.com/
-- http://www.apex-evangelists.com/
-- http://www.apexblogs.info/

HTML Template but I need php files.

Hello I have an html template but I need to create a php file for a login system. I went to the server behaviors tab and changed it to a php file but will it update based on template? Also I need to insert a form into a editable region I made into the body of the forum but everytime I do it when I look on the design screen it looks completely messed up but when I go to live view it looks fine. Any idea why?

Hello I have an html template but I need to create a php file for a login system. I went to the server behaviors tab and changed it to a php file but will it update based on template? Also I need to insert a form into a editable region I made into the body of the forum but everytime I do it when I look on the design screen it looks completely messed up but when I go to live view it looks fine. Any idea why?
If you have set up a testing server, your documents should automatically have the PHP extension. Then if you create a new document from a DWT file, this will have the PHP extension.
I think it would be a good idea to have a look at a David Powers tutorial on dynamic sites which can be found here http://www.adobe.com/devnet/dreamweaver/articles/first_dynamic_site_pt1.html
In the same section, there are also tutorials on how to use template files.
I hope this helps.
Ben

How to use html template on a php script, if possible..

Hello,
I buy it smartjobboard script which is made in php (
''SmartJobBoard software design and layout is based on ‘Templates’ system.
Templates used in the software are built on html and Smarty. '')
. This is advanced job board script with user registrations/payment getway/ search ,etc. This script have default templates which are very old and ugly. So, I deciced it to build my own template. The only problem is that I didn't knew that my script is made php, so I lost 2 weeks working on a html job template with maps and everything need it for a nice site hoping that I will only have to paste some codes on my html code.. Now I'am stuck with my template and shocked with php, although I have acces to edit php template I found it impossible to make it to the level I create it my htlml template (not that I have tried..) . I have around 30 js files and 5 css on my template.
I tried to download my own php site on pc hoping I will have html format /it works only as a template but it does not connect to database for login/register/search ,etc...
There is any hope for my to actually use my html template ?
thank you

Looks like you need a Template that is designed to work with your scripts.
They appear to have serveral you could use.
http://www.smartjobboard.com/templates.html
If you want a customized Template, contact one of their partners to help you.
http://www.smartjobboard.com/custom-design/
Nancy O.

Deciphering Aperture Web Themes: the html templates v3

version 3 of my Aperture Web Theme html template reference. enjoy
the html templates.
rkid attributes:
Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
  <ul id="nav" rkid="navbar">
These are the rkid values that I've identified so far:
  "navbar"
    a <ul> element containing all of the navigation elements.
  "active" and "inactive"
    rkid attributes to enable the coder to place different formatting on
    current and non-current page numbers in the navbar.
    eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
      <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
  "content"
    a <div> containing all of the album images and their metadata.
  "pictureblock"
    a mandatory <table> in which the images are placed, one image per <td>.
    the <table> must even be used on the Detail page where only one image is
    displayed.
    the metadata will be within the "pictureblock" table if more than one
    image is displayed so that the metadata can be tied to the image. if
    only one image is displayed; i.e., the Detail page; the metadata may be
    in a <td> outside of the table that the image is in but still within the
    "content" div, usually in the following format:
      <div rkid="content">
        <table>
          <td>metadata
          <td><table rkid="pictureblock">
  "image"
    the rkid for the <img> elements containing the album images, frequently
    placed in <dt> elements within the table's cells.
  "metadata" (added in Decipher v3)
    all metadata for the respective image is specified within this element.
    everything within the element is repeated for every metadata value.
    the Aperture themes use the <ul> element but <div> also works:
      <div rkid="metadata"><p>metaname: metavalue</p></div>
  "titleblock"
    a <div> containing the title text; usually <h3>; for Journals. the <h3>
    element within this element must be given the attribute rkid="text" or
    Aperture will ignore it.
  "textblock"
    a <div> containing the description text for Journals. as with the
    titleblock, the <p> element/s within this div must be given the
    attribute rkid="text".
  "text"
    the rkid given to the text data within the titleblock and textblock
    elements.
Place holders:
  PageTitle
    used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
  IndexPageURL
    the gallery page/s URLs; may be more than one.
  ThumbImageURL
    the href links for the images, whether thumbnails or detail full size.
  DetailPageURL
  used within navbar:
    PageCount
    PageNumber
    PreviousPageNumber
    PreviousPageURL
    NextPageNumber
    NextPageURL
    PageCount the total number of pages
    PageNumber includes all of the page numbers listed in the navbar, one
      occurrence for each page.
    _Previous and _Next are more specific and are currently used to draw the
      prev/next arrows in the navbar.
  ImageName
  ImageNameSpace
  PlateNameSpace
  PlateNumberSpaceSlash
    *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
      chosen.
    used to represent an index of the image in the album. the first image
      shown gets the index 1, the second 2 and so on.
    for the Image placeholders, the word 'Image' is used.
    for the Plate placeholders, the word 'Plate' is used.
    space indicates an extra space after the index, probably for html
      formatting purposes because it's only used within <dt> elements.
    slash indicates an extra / character after the index.
    examples:
      ImageName > 'Image 1'.
      ImageNameSpace > 'Image 1 '.
      PlateNameSpace > 'Plate 1 '.
      PlateNumberSpaceSlash > '1 / '.
  metaname
  metavalue
    the placeholders for all of the metadata names/values in the selected
    metadata set.
  PageWidth
    not sure if Aperture calculates it based on the width and number of
    images being displayed in both gallery and detail pages.
    don't know why it's only used in the Special Occasion theme.
  CellWidth
    the width of the table cells containing the album images. not
    necessarily the width of the images. may include margins as specified in
    the albuminfo.plist files.
  ImageWidth
    the width of the image.
  TableWidth
    the width of the pictureblock table. it can probably be applied to other
    elements too but it's length is almost certainly calculated from the
    pictureblock table.
Operative attributes:
  removeonfirstpage="yes"
    used in the navbar to remove the Prev link from the first page.
    because it's applied to the <a> element, the <a> element is removed
      while leaving an empty <li> in place.
  removeonlastpage="yes"
    used in the navbar to remove the Next link from the last page.
    because it's applied to the <a> element, the <a> element is removed
      while leaving an empty <li> in place.
  removeonsinglepage="yes"
    used in the navbar to remove elements when there's only one page.
    used in a <div> in the Art Collection to remove the whole navbar on
    single pages.
  contenteditable="yes"
    used in text elements to indicate that the user can customise the text.
    not necessary in titleblock and textblock rkid="text" elements.
    in elements outside of the titleblock and textblock elements, content
    will not be truly editable unless a textid is assigned to the text
    elements. unfortunately, all text elements with textids are always
    'common' and can not be specific to any one image.
  common="yes"
    the element is seen on all pages.
Other attributes:
  metaseparator="|"
    used in metadata formatting, within the metadata lists.
    you can add additional characters. for example, the metaseparator
    in the Stock Black theme is " | "; ie, a | bar with a space on both
    sides. (Decipher v3)
    if the metaseparator is specified and the html template places the
    metadata into <li> elements as it does in most of the current themes,
    then it produces non-standard html code with the metaseparator between
    concurrent <li> elements.
  metalayout="paragraph"
    used in metadata formatting, within the metadata lists.
    if not specified, the metadata will not be exported. (Decipher v3)
  singlenesting="yes"
    used in metadata formatting. not sure what it does yet.
  textid="x"
    used to id text elements outside of the titleblock and textblock
    elements.
    possibly no limit to the number and id names used.
    examples used:
      textid="copyright"
      textid="header1"
  picturename="x"
  pictureimage="true"
    picturename gives the image an id.
    pictureimage="true" tells Aperture that the image is a static image
    which can be designated by the user during setup of the album. they show
    up in Aperture as grey blank rectangles with cross-eyes in the middle.
    they do not need to be inside the "content" element
    with picturename and pictureimage, we can place as many static images on
    the page as we wish.
Assertions:
  Aperture uses the rkid values to identify the areas of the html to be
  repeated for the respective objects.
  standard id and class attributes are only used by the css for formatting and
  not by Aperture to write the html data.
Notes:
  Aperture is hardcoded to expect and require that the album images are always
  within a <table rkid="pictureblock"> element. it is not possible to place
  album images outside of the table. all album images must be placed within
  <td> cells within the table. the <td> code is repeated for each image.
  image metadata is also normally within the rkid="content" element although
  it can be outside of the rkid="pictureblock" element.
  by default, the textblock rkid="text" element is added when the T+ button is
  pressed within Aperture. the textblock element is switched with the
  titleblock element when the Title/Text toggle button is clicked.
  width and height attributes of <img> elements are rewritten by Aperture
  based on the inserted images. placeholders aren't necessary within <img>
  elements.
  comments are stripped from the html before export some but some
  Aperture-proprietary attributes are forgotten and left behind.
  some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
  doctype.
  all markup is converted and exported in UPPER-CASE. personally, I prefer
  lower-case.
  high-ascii characters entered by the user are not converted to their html
  entities when available. eg, the © character.
  multiple <p> elements can be inserted into the titleblock and textblock
  <div> elements but each of them must have the rkid="text" attribute. any
  element without this attribute will be ommitted by Aperture.
  the reason there are Smart Galleries but no Smart Journals is because you
  need to write text between each row of images.
  titleblock and textblock elements will not be applied to Galleries or Detail
  templates; only to Journals.
  if there are more than one titleblock or more than one textblock, only the
  first will be used by Aperture.
  upon export, Aperture will remove everything from within the rkid="content"
  element which is not the pictureblock, titleblock or textblock elements.
  (Decipher v3)
  some of the Aperture templates have xhtml doctypes but are exported from
  Aperture with html 4.0 loose doctypes. weird! worthy of note is the fact
  that UPPER-CASE element names is not permitted with xhtml which is
  case-sensitive. (Decipher v3)
Questions:
  are there variable scopes with each rkid? eg, within the "content" rkid, can
  every variable/placeholder be accessed?
  why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
  the images and related metadata in the table? easier css formatting?
JavaScript: (Decipher v3)
  you can include JavaScript in the html code but cannot wrap it in html
  comments because Aperture will remove everything within comments.
  Aperture variables such as PageNumber will not be replaced within
  attributes such as <body onload="dialog(PageNumber);">.
  it is very difficult to use document.write anywhere within the html <body>.
  Aperture seems to be using JavaScript to export the html and its code is not
  able to cope with more than one instance of document.write in the html
  templates. after hours of trial and error, I found that the most stable way
  to use JavaScript within the html <body> was to only use one <script>
  element and place everything within it. using document.write within a second
  <script> element would almost certainly lead to unpredictable exported html,
  and instability and crashes in Aperture.
iMac Duo Core 2GHz 2GB Mac OS X (10.4.6)

It worked. I still have a few tweaks to do on my final template, but the method I described above works. I've set up my templates like this:
1) one large image per thumbnail page (like a photo essay or photo blog style)
2) same size image on detail page, but with paypal buttons directly below in their own table (I have several different paypal buttons - for different print sizes and a couple other things like postcards, etc.)
The neatest thing about this setup is that since it's all controlled by flat html and css, it looks almost like javascript the way the paypal buttons pop up - the image stays in exactly the same place and the buttons just appear below it (haven't tried it on a slow connection, though, probably a slight delay).
This is great because I hate javascript but sometimes like the immediate visual effects it allows.
This template makes it trivial to create a reverse chronological gallery/journal - kind of like a photoblog - and allows visitors to view the large images without the extra clutter of the buttons, but then they can just click on the image to reveal the buttons and click the image again to hide them.
The benefit of putting these buttons directly into the Aperture templates rather than using a find-replace script to add them to iWeb pages after processing? Well, using Aperture, I can add the PageTitle tag to the Paypal button - it doesn't work in hidden form fields or anything that needs to go inside an attribute, but it does parse using a textarea field, which I hid with CSS - This alleviates the problem many photographer sites have where they ask the buyer to email them with the image name/number they want - this way, the shopping cart automatically knows which image they're ordering.
PageTitle uses the following format: Gallery/Journal Name - Image/Version Name
So using this tag in the Paypal button tells me which image the buyer wants and which gallery they were viewing when they ordered - simple but effective.
Anyway, I know it's been a few weeks since I last replied, but I thought I would post this for others who might be interested in doing something similar - entirely through Aperture. Sorry about the run-on sentences; I'm a bit pre-occupied to proofread today.

Deciphering web themes: the html templates; expanded reference.

the html templates.
RKID attributes:
Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
   <ul id="nav" rkid="navbar">
These are the rkid values that I've identified so far:
   "navbar"
      a <ul> element containing all of the navigation elements.
   "active" and "inactive"
      rkid attributes to enable the coder to place different formatting on
      current and non-current page numbers in the navbar.
      eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
         <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
   "content"
      a <div> containing all of the album images and their metadata.
   "pictureblock"
      a mandatory <table> in which the images are placed, one image per <td>.
      the <table> must even be used on the Detail page where only one image is
      displayed.
      the metadata will be within the "pictureblock" table if more than one
      image is displayed so that the metadata can be tied to the image. if
      only one image is displayed; i.e., the Detail page; the metadata may be
      in a <td> outside of the table that the image is in but still within the
      "pictureblock" table, usually in the following format:
         <div rkid="content">
            <table>
               <td>metadata
               <td><table rkid="pictureblock">
   "image"
      the rkid for the <img> elements containing the album images, frequently
      placed in <dt> elements within the table's cells.
   "titleblock"
      a <div> containing the title text; usually <h3>; for Journals. the <h3>
      element within this element must be given the attribute rkid="text" or
      Aperture will ignore it.
   "textblock"
      a <div> containing the description text for Journals. as with the
      titleblock, the <p> element/s within this div must be given the
      attribute rkid="text".
   "text"
      the rkid given to the text data within the titleblock and textblock
      elements.
Place holders:
   PageTitle
      used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
   IndexPageURL
      the gallery page/s URLs; may be more than one.
   ThumbImageURL
      the href links for the images, whether thumbnails or detail full size.
   DetailPageURL
   used within navbar:
      PageCount
      PageNumber
      PreviousPageNumber
      PreviousPageURL
      NextPageNumber
      NextPageURL
      PageCount the total number of pages
      PageNumber includes all of the page numbers listed in the navbar, one
         occurrence for each page.
      _Previous and _Next are more specific and are currently used to draw the
         prev/next arrows in the navbar.
   ImageName
   ImageNameSpace
   PlateNameSpace
   PlateNumberSpaceSlash
      *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
         chosen.
      used to represent an index of the image in the album. the first image
         shown gets the index 1, the second 2 and so on.
      for the Image placeholders, the word 'Image' is used.
      for the Plate placeholders, the word 'Plate' is used.
      space indicates an extra space after the index, probably for html
         formatting purposes because it's only used within <dt> elements.
      slash indicates an extra / character after the index.
      examples:
         ImageName > 'Image 1'.
         ImageNameSpace > 'Image 1 '.
         PlateNameSpace > 'Plate 1 '.
         PlateNumberSpaceSlash > '1 / '.
   metaname
   metavalue
      the placeholders for all of the metadata names/values in the selected
      metadata set.
   PageWidth
      not sure if Aperture calculates it based on the width and number of
      images being displayed in both gallery and detail pages.
      don't know why it's only used in the Special Occasion theme.
   CellWidth
      the width of the table cells containing the album images. not
      necessarily the width of the images. may include margins as specified in
      the albuminfo.plist files.
   ImageWidth
      the width of the image.
   TableWidth
      the width of the pictureblock table. it can probably be applied to other
      elements too but it's length is almost certainly calculated from the
      pictureblock table.
Operative attributes:
   removeonfirstpage="yes"
      used in the navbar to remove the Prev link from the first page.
      because it's applied to the <a> element, the <a> element is removed
         while leaving an empty <li> in place.
   removeonlastpage="yes"
      used in the navbar to remove the Next link from the last page.
      because it's applied to the <a> element, the <a> element is removed
         while leaving an empty <li> in place.
   removeonsinglepage="yes"
      used in the navbar to remove elements when there's only one page.
      used in a <div> in the Art Collection to remove the whole navbar on
      single pages.
   contenteditable="yes"
      used in text elements to indicate that the user can customise the text.
      not necessary in titleblock and textblock rkid="text" elements.
   common="yes"
      the element is seen on all pages.
Other attributes:
   metaseparator="|"
      used in metadata formatting, within the metadata lists.
   metalayout="paragraph"
      used in metadata formatting, within the metadata lists.
   singlenesting="yes"
      used in metadata formatting. not sure what it does yet.
   textid="x"
      used to id text elements outside of the titleblock and textblock
      elements.
      possibly no limit to the number and id names used.
      examples used:
         textid="copyright"
         textid="header1"
   picturename="x"
   pictureimage="true"
      picturename gives the image an id.
      pictureimage="true" tells Aperture that the image is a static image
      which can be designated by the user during setup of the album. they show
      up in Aperture as grey blank rectangles with cross-eyes in the middle.
      they do not need to be inside the "content" element
      with picturename and pictureimage, we can place as many static images on
      the page as we wish.
Assertions:
   Aperture uses the rkid values to identify the areas of the html to be
   repeated for the respective objects.
   standard id and class attributes are only used by the css for formatting and
   not by Aperture to write the html data.
Notes:
   Aperture is hardcoded to expect and require that the album images are always
   within a <table rkid="pictureblock"> element. it is not possible to place
   album images outside of the table. all album images must be placed within
   <td> cells within the table. the <td> code is repeated for each image.
   image metadata is also normally within the rkid="content" element although
   it can be outside of the rkid="pictureblock" element.
   by default, the textblock rkid="text" element is added when the T+ button is
   pressed within Aperture. the textblock element is switched with the
   titleblock element when the Title/Text toggle button is clicked.
   width and height attributes of <img> elements are rewritten by Aperture
   based on the inserted images. placeholders aren't necessary within <img>
   elements.
   comments are stripped from the html before export some but some
   Aperture-proprietary attributes are forgotten and left behind.
   some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
   doctype.
   all markup is converted and exported in UPPER-CASE. personally, I prefer
   lower-case.
   high-ascii characters entered by the user are not converted to their html
   entities when available. eg, the © character.
   multiple <p> elements can be inserted into the titleblock and textblock
   <div> elements but each of them must have the rkid="text" attribute. any
   element without this attribute will be ommitted by Aperture.
   the reason there are Smart Galleries but no Smart Journals is because you
   need to write text between each row of images.
   titleblock and textblock elements will not be applied to Galleries or Detail
   templates; only to Journals.
   if there are more than one titleblock or more than one textblock, only the
   first will be used by Aperture.
Questions:
   are there variable scopes with each rkid? eg, within the "content" rkid, can
   every variable/placeholder be accessed?
   why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
   the images and related metadata in the table? easier css formatting?
iMac Duo Core 2GHz 2GB Mac OS X (10.4.6)

IMPORTANT!
An updated version is available in thread:
Deciphering Aperture Web Themes: the html templates v3.

HTML Template to JSC

Hi, How can I use an HTML template from Dreamweaver in Java Studio Creator?
I�ve tried File>Add existing item > Web page but after the conversion there are still many tags in html <tr> and others that were not converted and they appear in the design view as trasparent tables that dont allow me to work properly. Is there another way to convert them or to do something?
The original code is the next one:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>

<head>

<title>Text</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="mm_training.css" type="text/css">
</head>
<body bgcolor="#64748B">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
     <tr bgcolor="#26354A">
     <td width="15" nowrap="nowrap"><img src="mm_spacer.gif" alt="" width="15" height="1" border="0"></td>
     <td height="70" colspan="2" class="logo" nowrap="nowrap">Insert Website Name <span class="tagline">| OPTIONAL TAGLINE HERE</span></td>
     <td width="100%"> </td>
     </tr>
     <tr bgcolor="#FF6600">
     <td colspan="4"><img src="mm_spacer.gif" alt="" width="1" height="4" border="0"></td>
     </tr>
     <tr bgcolor="#D3DCE6">
     <td colspan="4"><img src="mm_spacer.gif" alt="" width="1" height="1" border="0"></td>
     </tr>
     <tr bgcolor="#FFCC00">
     <td width="15" nowrap="nowrap"> </td>
     <td width="705" colspan="2" height="24">
     <table border="0" cellpadding="0" cellspacing="0" id="navigation">
<tr>
<td class="navText" align="center" nowrap="nowrap">HOME</td>
</tr>
</table>     </td>
     <td width="100%"> </td>
     </tr>
     <tr bgcolor="#D3DCE6">
     <td colspan="4"><img src="mm_spacer.gif" alt="" width="1" height="1" border="0"></td>
     </tr>
     <tr bgcolor="#FF6600">
     <td colspan="4"><img src="mm_spacer.gif" alt="" width="1" height="4" border="0"></td>
     </tr>
     <tr bgcolor="#D3DCE6">
     <td colspan="4"><img src="mm_spacer.gif" alt="" width="1" height="1" border="0"></td>
     </tr>
     <tr bgcolor="#D3DCE6">
     <td width="15" valign="top"> </td>
     <td width="35"><img src="mm_spacer.gif" alt="" width="35" height="1" border="0"></td>
     <td width="710" valign="top"><br>
      <br>
     <table border="0" cellspacing="0" cellpadding="2" width="500">
          <tr>
          <td class="pageName">Page Name Here</td>
          </tr>
          <tr>
          <td class="bodyText">
          <p>Write text here </p>
          <br></td>
          </tr>
     </table>
     �<br>     </td>
     <td> </td>
     </tr>
     <tr>
     <td width="15"> <br>
      <br>     </td>
<td width="35"> </td>
<td width="710"> </td>
     <td width="100%"> </td>
</tr>
</table>
</body>
</html>

Hi,
Please take a look at the articled titled "Importing HTML Pages in the Sun Java Studio Creator 2 IDE". This is available at:
http://developers.sun.com/prodtech/javatools/jscreator/reference/fi/2/html-page-import.html
Hope this helps
Cheers
Girish

Why only 2 templates creating php document

Hi,
When I try to create a php page, onbly have 2 templates, why?? dreamweaver has more templates for php, html etc.
thnks

With a few minor modifications, you can create any CSS Layout you need from either of those starter CSS pages.
Or you can build a custom one with:
FluidGrid Layouts,
or jQuery Mobile,
or any of the freely available Responsive Frameworks online:
Foundation Zurb- http://foundation.zurb.com/templates.php
Skeleton Boilerplate - http://www.getskeleton.com/
Initializr (HTML5 Boilerplate, Responsive or Bootstrap) - http://www.initializr.com/
DMX Zone's Bootstrap extension for DW - http://www.dmxzone.com/go/21759/dmxzone-bootstrap/
Project Seven's Page Packs (Commercial CSS Templates) - http://www.projectseven.com/products/templates/index.htm
Nancy O.

HTML Templates in integrated ITS

Hi,
I am using certain ITS services in integrated ITS. However, their look and feel is like WebGUI. For two of the services, there are HTML templates defined but still their look and feel is like WebGUI. If I do not definr ~GENERATEDYNPRO = 1, then I get an internal error. If I use this parameter, then the look and feel is SAP like.
Any pointers?
Thank you.
Abhijeet.

Hi abhijeet,
Set by Service file
~ generateDynpro = 0 -Automatic screen generation
                      disabled.
                   1 -Automatic screen generation
                      enabled.
can you re-publish service again on your ITS and re-start ITS server and test this.
Please share the result.
Thnx,
Suriya.

Page includes in html templates

I see <% include file="header.html" %> in html template working for 'HTML' gallery type web engines.
<br />
<br />But, it doesn't work if the gallery type is 'Flash'. It seems the only supported directive includes are %variablename% format.
<br />
<br />Why LR is restricting lots of features for Flash based galleries? Is this by design or restricted for some other reasons or a bug?
<br />
<br />I wish if there is some flag somewhere that can be turned on so that Flash gallery type will have all the features of html. Currently I don't think it'll encourage any developer to write/adapt flash based web plugin for LR.
<br />
<br />Chris

Sean, Thanks for your reply. SlideShowPro is no different. Please check any of the html pages in the SlideShowPro plugin. It doesn't use <% %> directives. Only %var% is used.
<br />
<br />Yes, I'm aware of what include does. That's exactly the reason why I need it in Flash gallery type. Keep the header and footer outside the template for easy user editing.
<br />
<br />To explain the issue in easier terms, lua coding is allowed in the template files only if you set gallery type as 'Html'. If you change it to 'Flash', it won't work.
<br />
<br />Even simpler,
<br />You can use <% %> only in html gallery types.
<br />
<br />It's not just 'include'. If <% ... %> is allowed for Flash gallery type, you can do a lot of lua scripting in your html templates. All spoiled by LR limitation :-)

How to take data from HTML Template into BSP Variable?

hi all,
            can we take the data from the input field of HTML Template and collect into BSP variable? i have the shown the HTML Template into BSP page by passing the url in <IFRAME> tag now i have to take the data form the into field of HTML Template and save it back to the BSP table onclicking the Save button of BSP Page. please help me out thanks in advance.
Thanks & Regards,
Amol

Hi Amol,
This is very simple....
In the onInputProcessing event of the page use the following code to read data from the InputField into an ABAP variable...
Then you can use it at will..!
Code is :
data : event       TYPE REF TO if_htmlb_data,
       but_event   TYPE REF TO cl_htmlb_event_button.
event = cl_htmlb_manager=>get_event( request ).
IF event->EVENT_NAME = 'button' and event->EVENT_TYPE = 'click'.
      but_event ?= event.
      CASE event->EVENT_ID.
        when 'your_button_id'.
          data : lw_inf type ref to cl_htmlb_inputfield.
             lw_inf ?= cl_htmlb_manager=>get_data(
                            request = runtime->server->request
                            name    = 'inputField'
                            id      = 'your_inputField_id' ).
          if lw_inf->value is not initial.
            lw_variable = lw_inf->value.
          endif.
     ENDCASE.
ENDIF.

XML to convert creative html to jsp?

I am trying to find a way to use XML, XSL, etc., to make the process of building web pages at my company easier between the creative team and developers:
1.) The creative team creates the images, text, and html (using Dreamweaver). Please note, the creative team barely knows html, much less xml, xsl, or taglibs.
2.) The creative team then sends me the html pages.
3.) I then need to "convert" the html into jsps. That is, I remove the mock/dummy dynamic content, and replace it with the scriptlets or taglibs that will produce the real dynamic content.
This takes alot of time. On top of that, if the creatives ever need to be changed, I need to send the newly converted jsps back to the creative team. They inevitably mess the jsps up, because they do not understand scriptlets or taglibs. Is there some standard way of dealing with this scenario, so that the creative team and I can work better together, and so that I dont constantly "convert" the html pages to jsps? I know one option is Enhydra's xmlc, but I will have a hard time getting the creative team to adopt that.
thank you,
David

y don't u eliminate your jsp from your HTML. you can inculde html files as a header and footer.
tell to write a comment tag in html <Html code> <table><tr><td> </td></tr></table> <Html code>. you can write a small jsp which can String.indexOf("");. you can easily create header and footer files. for your jsp, u can also change your jsp code like this.

Converting a html template to php

Similar Messages

Maybe you are looking for