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.

Similar Messages

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.

[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.

Has anybody modified the Aperture Web Themes for a Fluid Grid or Responsive Web design

I have had some experience modifigying Apple's WebThemes inside Aperture in
Aperture.app/Contents/Resources/WebThemes
I would like to create or modify an existing Web Theme in order to have my site follow the Fluid Grid principles of Responsive Web design.
Has anybody done this who would like to provide some advice?
Thanks, in advance.

Hi jonfreed77,
People facing similar issue, posted following resolution in another thread recently.
Please give it a try and confirm if they work for you.
8. pcepp,
20 Jun, 2013 8:24 AM in reply to pcepp
Report
I found a solution that worked for me.
I removed all the fonts that Adobe CC installed out of my Library:Fonts folder and just left in the Apple Basic fonts like Arial, Courier etc... Launched Dreamweaver CC and the CSS designer panel works. I have no idea exactly which font it is, or creating the conflict. All I know is that it works great now.
|
9. dogdog63,
20 Jun, 2013 10:11 AM in reply to dogdog63
Report
very strange - I installed Illustrator CC and then I had no more problems with Dreamweaver! No more crashes when close or create files and no more problems with the CSS designer. Error messages during create fluid grid layouts are also gone ...
Michel:
I think I figured it out on the Mac. Be sure that Verdana is activated in Font Book. What tipped me off to this was a warning I was receiving when trying to open After Effects. It was saying that the program needed Verdana for the user interface to work. I thought that maybe Dreamweaver needed Verdana too. Sure enough! Hope this helps you guys.

Can't find the HTML templates in Encore for use with Flash output

Anyone know where these are located in CS4?

Its easy to write HTML templates. If you have an image that you want to use as Template, create an index.html file with <encoreswfobject> tag in it. This tag will be replaced by the SWF code.
In following example of index.HTML file, <EncoreSWFObject> is compulsory tag, rest of the tags are optional. This will take boy.jpg (in Images folder) as background.
<head>
<title><EncoreSWFTitle></title>
</head>
<body bgcolor="#ffffff" background="Images/boy.jpg">
<table width="100%" height="100%" border="0">
<tr>
<td valign="middle"><center>
<div style="border: 2px solid #000; width: <EncoreSWFWidth>px; height: <EncoreSWFHeight>px;">
<EncoreSWFObject>
</div>
</center></td>
</tr>
</table>
</body>
</html>

New Aperture Web Themes with 'Parent INDEX' link

Hi all,
I've hacked up the Stock themes to create a Stock Grey and also add a link back to the parent directory of a web gallery in order to make it easier to put together a full site with Aperture. No, it doesn't help create the initial top level index of all sub-galleries, but it does make it easier for viewers to navigate back out of one album and into another.
I've made an installer for it that searches for Aperture.app no matter where it was installed, so it can take a minute or so to complete, but I've put it up on my site:
http://minimal.cx/2006/08/15/four-free-aperture-themes/
and have a sample set of images for viewing at:
http://gallery.minimal.cx/
The top level page was done by hand, everything else simply came out of Aperture and was dropped directly onto the web space with no other changes.
Hope that's of some use to other people.
TTFN,
ian.
Mac OS X (10.4.7)

Your comment about searching for Aperture.app reminded me that I'd been meaning to look into the proper way to do this.
There doesn't seem to be a convenient command-line tool to do it (you can use lsregister and dump the LaunchServices database, but that's ugly).
But here's a Perl one-liner, that would be callable from a preflight script:
$ perl -MMac::Processes -e 'print LSFindApplicationForInfo(undef, "com.apple.Aperture"),"\n" '
which on my system returns:
/Applications/Aperture.app
the Mac::Processes module is standard with Tiger (comes in Essentials.pkg)

Can we debug the Html template in Internet service

Hi ,
I need to change the name of a filed in srm portal "confirmation of good and service" for that i had a template but i am not able to find the label in that
How can i find the label ?
can i debug the template
help me
thanks
Channappa Sajjanar

Hi Pradeep,
Thanks for reply .Actually i found one solution which is as follow just guide me is it correct or not?
I gone to the screenpainter (se51) their i given the
program name =SAPLBBP_PDH_SEARCH.
screen number = 3001.
in this screen only the speeling mistakes are found for the variable's
Confirmatn Value : BBPS_SEARCH_SUBLIST_PO_WEB-VAL_CF and
Calculatd : BBPS_SEARCH_SUBLIST_PO_WEB-QUAN_IV.
So i just changed the spelling mistakes there in IDES SRM and they are reflection when i exceute the t-code BBPCF02 in SE80.
now just tell me is the way i am going is correct or not ?
what are the side effetcts of this?
and is any way i can solve the proble from the template?
please give your valuable sugetions i am very new to SRM.
Regards
Channappa Sajjanar

Using javascript in modified Aperture web page themes

Thanks to the many well-written tutorials on the subject, I've been able to modify an existing Aperture web theme to export customized web pages that have the exact look I'm after. I've successfully copied the Stock theme, edited the detail and journal-gallery html along with the global.css files and merged with a professional template I purchased, so now my Aperture-generated galleries look just like the rest of the pages on my web site.
Of course, there's always a problem:
If I reference any Javascript from the Aperture template files, Aperture EXECUTES the script during the process of exporting the web pages, and includes the result of the Javascript execution in the rendered HTML. It does this IN ADDITION to correctly writing the Javascript reference to the rendered page. The end result is TWO of everything. An example will make this more clear:
If I include the following line in journal-gallery.html:
<script language="JavaScript" type="text/javascript" src="assets/scripts/sidebar.js"></script>
and the file sidebar.js contains:
document.write('Home
document.write('<'t find a single reference to the use of scripts. CLEARLY APERTURE KNOWS ABOUT JAVASCRIPT AND EXPECTS TO FIND IT BECAUSE IT'S EXECUTING ANY SCRIPT IT COMES ACROSS!!!
The goal of all this, of course, is what any large professionally-done web site strives for: I don't want to re-render all my static content (the photo galleries) every time I add or remove a link in the sidebar. Editing sidebar.js should be all that's required to change the links.
Anyone?

Sorry, I see that the Javascript snippets in my original post are being executing by the web browser when the message is read.
The 2 lines of Javascript, cleverly (ahem) encoded, might be visualized:
document (dot) write ( <html anchor tag>Home<close html anchor tag>);
document (dot) write ( <html anchor tag>Site Map<close html anchor tag>);

Where is the code for html template stored on the server

I would like to make changes to the html template source code, mainly to update the hard coded server name in it.
Instead of doing one by one in portal builder, I would like to search for all on the server.
Can someone tell me where are they stored?
Thanks.

wow!
well, if you wish to do it programmatically, you will have something generic to search and replace (like the hardcoded servername as you said). that will not be sitting in any variable to go and edit. in other words, you wanna edit an uncategorized content value so it will be a job to search and find it in a general text attribute/field value. it will be a pain.
one method could be to write a script (shell, nt, csh, sh, or simply sed) to make all of those generic changes in any template content. now copy and paste all items out in a temp file, run the script, and paste back the output to the template.
however, if you're determined to modify uncategorized content using APIs, you might wanna try this:
Look into wwsbr_api.set_attribute and look for wwsbr_api.ATTRIBUTE_ITEM_TEMPLATE to focus on the template you have. It might work out. more on it is here.
hope that helps!

How do you edit the HTML export template?

Fireworks HTML and images export does not render correctly when viewing in IE9 due to the default browser padding values. I'm a little disappointed the Fireworks dev team didn't see this coming and add some code to prevent this rendering issue. Anyway... I've come up with a work around to edit the html pages by adding my own style sheet which includes the yahoo CSS reset styles to take care of this problem and it works great. The only problem is, adding it to every page of a multiple page export is tedious. So, I'd like to directly edit the HTML template fireworks uses to generate the html in the head of each page it exports so it includes a reference to my own external style sheet. I just need to know where/if I can make this change. Any help would be greatly appreciated!
Thanks,
Greg

I've never tried it, but the HTML Code folder inside Fireworks' application Configuration folder contains a number of items related to HTML Export. (Incidentally, I'd never mess with this folder without first saving a backup, and even then it's at your own risk.)
There's no simple HTML template file here, but there are files like "DreamweaverLibrary.htt", which is a "hypertext template" file that looks a lot like JavaScript to me. So if you're comfortable modifying JavaScript, then you could take a crack at it. I'm not sure, but it looks like this library file might govern what gets written into the head of an exported HTML document. If not, you could try a different one.
Another, less invasive approach might be to do some kind of Find and Replace on the exported HTML documents—using Dreamweaver or a text editor.

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.

In ITS-Service ITSMOBILE no HTML-Template ALV_GRID.html

Hi all,
i use its-mobile with alv grid. In my Template i changed text:
Unknown type CUST_CTRL for element CONTAINER1
with:
`include(~service="itsmobile", ~theme="99", ~name="alv_grid.html");
alv_grid("ALV", 52, 8);`
But now i get the error: ITS_CANT_LOAD_INCLUDE - that file alv_grid.html is not found. That is right! When i look into ITSMOBILE -> Thema 99 -> HTML-Templates no file called alv_grid.html is there. So how do i get this file?
System is SAP ECC 6.0, Release 700 Support Package SAPKA70016.
Best Regards,
Max

Hi Max,
What is the BASIS Support pack that you are on?
I presume its the same level as your Application Support Pack SAPKA70016? i.e SAPKB70016
For ITSMobile - I thing you would need to be on SAPKB70018?
See notes:
[BC-FES-ITS #1320125 ITSmobile: fixed ALV Grid row selection|http://service.sap.com/sap/support/notes/1320125]
[BC-DWB-TOO-WAB #1142337 Generating program creates slow HTML mobile templates|http://service.sap.com/sap/support/notes/1142337]
Regards,
Oisin

Creating a simple HTML template

Hello All,
I have to create a simple HTML template for a screen in SRM for Mass change of a field on contracts. I have ITS service ready and I have created a HTML template with reference to the prorgam and screen. It generated following code. what change do I need to make to make the template displayed. When i run the template it gives me an error 'URL http://XXXXX/sap/bc/gui/sap/its/ysrm_ctr_mass/ call was terminated because the corresponding service is not available'.I have never worked on HTML templates before. Anybody wannna help me, pls?
Here's the generated code:
`include(~service="system", ~language="", ~theme="dm", ~name="TemplateLibraryDHTML.html")`
      `SAP_DynproLayerBegin(003,001,028,001)`
      `SAP_Label("%#AUTOTEXT001")`
      `SAP_DynproLayerEnd()`
      `SAP_DynproLayerBegin(003,003,020,001)`
      `SAP_Label("YSRMS_CTR_MASS_NEG_AMEND-YYNEG_AMEND_OLD")`
      `SAP_DynproLayerEnd()`
      `SAP_DynproLayerBegin(030,003,005,001)`
      `SAP_InputField("YSRMS_CTR_MASS_NEG_AMEND-YYNEG_AMEND_OLD")`
      `SAP_DynproLayerEnd()`
      `SAP_DynproLabelLine(003,003,030)`
      `SAP_DynproLayerBegin(003,004,020,001)`
      `SAP_Label("YSRMS_CTR_MASS_NEG_AMEND-YYNEG_AMEND_NEW")`
      `SAP_DynproLayerEnd()`
      `SAP_DynproLayerBegin(030,004,005,001)`
      `SAP_InputField("YSRMS_CTR_MASS_NEG_AMEND-YYNEG_AMEND_NEW")`
      `SAP_DynproLayerEnd()`
      `SAP_DynproLabelLine(003,004,030)`
      `SAP_DynproLayerBegin(004,006,014,001)`
      `SAP_Button("CTR_NEG_AMEND_REJ")`
      `SAP_DynproLayerEnd()`
Thanks,
Chandra

Hi
Which SRM version are you using ?
Please do the following steps ->
-->Activate the services through SICF - SRM transaction code.
> Go to SICF transaction and activate the whole tree under the node Default host>sap>bc>gui>sap>its.
Right click on any of the services (there you will find option to De-actiave / activate the service)
Related links ->
Note 851940 - Launchpad in BBPSTART has wrong URL for services
Re: Service Cannot be Reached
Please ensure IACOR service must be running correctly before publishing the HTML Templates using the report - W3_PUBLISH_SERVICES
When you are using the Internal ITS,you need not run the report W3_PUBLISH_SERVICES.(only SIAC_PUBLISH_ALL_INT )
Re: Activating a Service in SICF
Regards
- Atul

Html template change and refresh on ITS Admin

hi all,
I need to change the HTML templates sent via email to the users. I found the files on the ITS server and changed them but when I view the same templates in ITS Admin then it is still showing the previous version.
The mentioned HTML templates are only present in the ITS server not as an internet service in SE80 so I cannot change and publish them from SAP.
Please advise that how can they be changed and refreshed so the changes to the layout appear.
Thanks,
FS

Hello FS,
ITSAdmin and local files - so you are using an external ITS 6.20?
If you did not start up the ITS in debug mode with ~adminenabled you will need to restart the ITS to apply the changes (that will be preparsed and cached in the ITS for performance reasons).
With best regards,
TJ

Servlet HTML Template

Hi, there.
I have a Servlet that among many other things, return a HTML to the user.
At the beggining, the HTML was so simple that it worth write the String and output it. The HTML now became much more complex, and I'd like to make it an external resource (.html), for mantainance purposes, and only replace the dynamic content inside it. I don't know which is the best way to accomplish it, to replace the variables inside the HTML Template I've just created. What should I look for?
Searched the web and found this solution: [HTML.Template.java|http://html-tmpl-java.sourceforge.net/]
Anyone knows it? Is it the fastest way? The best? Does anyone know a better solution?
Thank you in advances,
CaioToOn!

CaioToOn! wrote:
Hi, Kayaman.
I'm searching over "velocity template" just right now, didn't knew it. Are you talking about it http://velocity.apache.org/engine/releases/velocity-1.5/user-guide.html
Yes.
On JSP, I have no familiarity with it. I can achieve anything with a JSP that I could achieve with a servlet? Like starting a second thread, reading headers, sending custom headers, etc? I'd also, for "fancy" reasons, like not to have a ".jsp" at the end of my URL. May I do it without a URL rewriting rule?Ideally you wouldn't do that logic in the JSP. You would do it in the servlet, then forward to the jsp which would only display and have minimal logic in it.
And you can do it without having .jsp at the end of the URL.

Deciphering Aperture Web Themes: the html templates v3

Similar Messages

Maybe you are looking for