Converting a Illustrator Sliced HTML Template to a Dreamweaver Template?

Has anyone had any experience with this?
If so, does it work for BC? I am curious if I can even do this.

I have read online FireWorks is the best for slicing a website template or photoshop. Which do you guys reccommend? Also, I do have FW, if I use this to slice a web template out of it... is this compatible with BC?

Similar Messages

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/

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

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

Convert Sharepoint forms to html

Hello
My assign task is to import Sharepoint Forms to Online Forms so for that i need to convert Sharepoint forms into HTML by using any API/SDK/DLL
So I want to know how can i convert Sharepoint forms into HTML Programatically
Thanks in Advance
Manish K. Bhalodi

Hi Paul
Thanks for your such quick reply
We have a Online Form making project like Wufoo & Frevvo,
in that we have a functionality to import forms from Sharepoint List & Infopath, for Infopath i manage to convert it in HTML,
In sharepoint i have no idea, and i never work in sharepoint, but i know sharepoint has designer and whatever we design in sharepoint that i need to convert in HTML, and user can import simple textbox, checkbox, label, multiline textbox template not too
much advance control
We have a requirement of importing SharePoint List Form.
Manish K. Bhalodi

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

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.

[svn] 3120: When you point Flex Builder at a local sandbox trunk build, it couldn' t generate the html-templates folder correctly for new projects so we moved all the html templates up one level and removed the html-templates directory and adjusted build

Revision: 3120
Author: [email protected]
Date: 2008-09-05 10:44:10 -0700 (Fri, 05 Sep 2008)
Log Message:
When you point Flex Builder at a local sandbox trunk build, it couldn't generate the html-templates folder correctly for new projects so we moved all the html templates up one level and removed the html-templates directory and adjusted build.xml's to accommodate the directory change
Modified Paths:
flex/sdk/trunk/build.xml
flex/sdk/trunk/webapps/webtier/build.xml
Added Paths:
flex/sdk/trunk/templates/client-side-detection/
flex/sdk/trunk/templates/client-side-detection/AC_OETags.js
flex/sdk/trunk/templates/client-side-detection/index.template.html
flex/sdk/trunk/templates/client-side-detection-with-history/
flex/sdk/trunk/templates/client-side-detection-with-history/AC_OETags.js
flex/sdk/trunk/templates/client-side-detection-with-history/history/
flex/sdk/trunk/templates/client-side-detection-with-history/history/history.css
flex/sdk/trunk/templates/client-side-detection-with-history/history/history.js
flex/sdk/trunk/templates/client-side-detection-with-history/history/historyFrame.html
flex/sdk/trunk/templates/client-side-detection-with-history/index.template.html
flex/sdk/trunk/templates/express-installation/
flex/sdk/trunk/templates/express-installation/AC_OETags.js
flex/sdk/trunk/templates/express-installation/index.template.html
flex/sdk/trunk/templates/express-installation/playerProductInstall.swf
flex/sdk/trunk/templates/express-installation-with-history/
flex/sdk/trunk/templates/express-installation-with-history/AC_OETags.js
flex/sdk/trunk/templates/express-installation-with-history/history/
flex/sdk/trunk/templates/express-installation-with-history/history/history.css
flex/sdk/trunk/templates/express-installation-with-history/history/history.js
flex/sdk/trunk/templates/express-installation-with-history/history/historyFrame.html
flex/sdk/trunk/templates/express-installation-with-history/index.template.html
flex/sdk/trunk/templates/express-installation-with-history/playerProductInstall.swf
flex/sdk/trunk/templates/metadata/
flex/sdk/trunk/templates/metadata/AC_OETags.js
flex/sdk/trunk/templates/metadata/readme.txt
flex/sdk/trunk/templates/no-player-detection/
flex/sdk/trunk/templates/no-player-detection/AC_OETags.js
flex/sdk/trunk/templates/no-player-detection/index.template.html
flex/sdk/trunk/templates/no-player-detection-with-history/
flex/sdk/trunk/templates/no-player-detection-with-history/AC_OETags.js
flex/sdk/trunk/templates/no-player-detection-with-history/history/
flex/sdk/trunk/templates/no-player-detection-with-history/history/history.css
flex/sdk/trunk/templates/no-player-detection-with-history/history/history.js
flex/sdk/trunk/templates/no-player-detection-with-history/history/historyFrame.html
flex/sdk/trunk/templates/no-player-detection-with-history/index.template.html
Removed Paths:
flex/sdk/trunk/templates/html-templates/

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

Is it possible to convert PDF file into HTML

Dear friends
Is it possible to convert PDF file into HTML. I have few hundread PDF files i like to convert this files into HTML. I hope it can be done through Java but i don't know how to start this coding. anybody can give me a brief idea to go ahead.

Why do you want to do this yourself? I quick search on Google showed several utilities to do this, some freeware, some commercial.

Flow Logic jumping to HTML Template (with SAP dialog) & back again

Hello
Overview
========
Within a HTML Template that uses flow logic, can I call a HTML Template that has SAP dialog behind it. The SAP dialog is a function module that has a screen requesting user input and then follows on to display selection based on user input. The user can then select a value that I would like returned to the flow logic screens. Just like an F4 help.
Detail
======
This is for SRM (EBP):
-Internet Service: BBPATTRMAINT
-Theme: 99
-HTML Template and flow logic: MAINTAIN_ATTRIBUTES
Basically I want to give the user more functionality and be able to select addresses using an F4 type scenario.
The function module I want to call is as follows:
CALL FUNCTION <b>'F4IF_FIELD_VALUE_REQUEST'</b>
       <b>EXPORTING</b>
            TABNAME           = 'ADRC'
            FIELDNAME         = 'ADDRNUMBER'
            SEARCHHELP        = 'BBP_ADDR_BUPA_BUYER'
            SHLPPARAM         = 'ADDRNUMBER'
            DYNPPROG          = 'BBP_ADDR_MAINTAIN'
            DYNPNR            = SY-DYNNR
            DYNPROFIELD       = 'BBP_PARTNER_ORG-ADDR_SELECTED'
            CALLBACK_PROGRAM = 'BBP_ADDR_MAINTAIN'
            CALLBACK_FORM     = 'PRESET_COMPANY_PARTNER'
       <b>TABLES</b>
            RETURN_TAB        = IT_RETVALUES
       <b>EXCEPTIONS</b>
            FIELD_NOT_FOUND   = 1
            NO_HELP_FOR_FIELD = 2
            INCONSISTENT_HELP = 3
            NO_VALUES_FOUND   = 4
            OTHERS            = 5.
This displays a screen for the user to better define search criteria and follows on to display possible selections. The user selection is returned in IT_RETVALUES.
If anyone knows of a similar SAP example where they go from flow logic to HTML templates then that would help a lot.
Any help or direction would be greatly appreciated.
Regards
Peter

Hey Orcasound, welcome to the forum, and also welcome to Logic.
Nice setup BTW, especially the Dangerous 2BUS into the BC1 coming back to the Rosetta 800"s, that gonna sound sweet mate.
OK Q1: The master fader for output 1-2 is always gonna be there, I've never found a way of getting rid of it, you can fortunately set up the mixer so that it won't show though. At the top of the mix window is a heap of boxes highlighted in blue, all you need to do is deselect the master and the output as per this screen shot:
Save this in your template and you'll never have to see those pesky faders again.
Q2: Same thing really, logic will always show 1-2 output as stereo out. Which is annoying, even if you manually name them from the I/O labels window it's always stereo, everything else if fine apart from 1-2. To be honest I've just learned to live with it.
Glad you made the switch, I find DP to be bloated and a bit tired nowadays.

How to convert word documents to html page in sharepoint online 2013

Hi,
I am new SharePoint and still learning it.
I have been tasked to do the following on office 365 E3 SharePoint 2013 Online edition.
1) I have to create a Web page in asp.net
2) This page needs to show document from a given SharePoint folder and bind them in a grid or dropdown on the asp .net web page
3) On selecting the document from the drop down or gird (on asp .net webpage), I need to show the SharePoint word document as HTML on the webpage (something like word to html) Note: These SharePoint word document may contain Images, bullets, tables etc.
What I have been able to do till now
1) I have been able to connect to SharePoint from ASP .net application.
2) I have been able to retrieve document from a specific SharePoint folder.
3) Read the document from SharePoint folder and bind them to a drop down on the asp .net page.
What is missing?
I am not aware about any API that SharePoint Online provides to convert Word document to HTML. Any code sample or reference on how to will be much appreciated.
I am not also not sure what is the best way of achieving the functionality this?
Thanks
Krishna

If this was SharePoint server then it would be easy however in O365 You need to create a app which will use the word automation service and below is powershell which you can use for the conversion:-
# This script will convert Docx to PDF using word automation and similarly it can be used to convert to HTML
$wordFile="http://contoso/kick.docx"
$pdfFile="http://contoso/kick.pdf"
$wasp = Get-SPServiceApplicationProxy | where { $_.TypeName -eq "Word Automation Services Proxy" }
$site = Get-SPSite "http://contoso"
$ConvertJob = New-Object Microsoft.Office.Word.Server.Conversions.SyncConverter($wasp)
$ConvertJob.UserToken = $site.UserToken
$ConvertJob.Settings.UpdateFields = $false
$ConvertJob.Settings.OutputFormat = "PDF"
$ConvertJob.Convert($wordFile, $pdfFile)

Converting a Illustrator Sliced HTML Template to a Dreamweaver Template?

Similar Messages

Maybe you are looking for