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)

Similar Messages

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.

Difficulty using an Aperture Web gallery with Iweb and custom domain

I am not using a .Mac account. I do however, use Aperture to create web galleries. I cannot get Iweb to link to all my Aperture web galleries. Aperture web galleries create index.html files. When I link to a file called index.html nothing happens. Can someone please help. Thank you. Tom

You need to use the entire URL and have your folders already uploaded to your server.
Syntax would be something like this:
http://myserver.com/foldername
Since index.html is default you can leave it out of the URL.
I don't use Aperture so I don't know the method it uses. I would suspect it allows you to name a folder for the files and inside it is the index.html file and maybe a folder of images and other support files.

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.

Web Browsing with Parental Controls

Question: I have a daughter that is almost 8 now and is starting to get around the net quite well now. My issues is I'm on Tiger 10.4.11 and it don't have the parental controls that leopard 10.5 has. Is there a quick fix for this or is my only 2 options would be to upgrade to leopard which I really don't want to or purchase a security software.
David

sorry my recent post on logs kind of speaks forebodingly about safe eyes...somehow a logger that I cannot track with anti-vandal has found way in...other than that their program works well...You may also check out intego's Content Barrier X%.
Apples parental controls work but they do not filter well...all you can really do is allow only certain websites...WATCH OUT FOR THE KIDS GAMES>>A Close friend had over 70 viruse hit because they were latching onto the games
Hope you have success
Also check out K-9 web protection....Email them to see if the Mac version has been upgraded enough to get out the bugs..Mac version was new 6 mos ago
Their program is totally free.

New Patch (Web)Forms with Sun's Java Plugin 1.4 certified - when?

Hello,
We are waiting for the new patch version for Forms6i or Forms9i with
Sun's java Plugin on client platforms like Linux,... certified.
But when will it be available?
Peter

Peter,
Sun's Plugin 1.4 was certified with Forms6i patch 12. The forms9i certification comes with teh first patch set.
Frank

Linking Aperture Web Galleries together

I am trying to make my first web site using Web Galleries created by Aperture. I can not figure out how to have an index page (a page one first goes to when one goes to your site) and then have links to the Aperture Web Galleries.
Can Aperture do this ? Or do I need other software that create the central index page ?
What software are Aperture users maintaining the Aperture web Galleries with ?
Thanks very much in advance.
Dick Barrett
Mac OS X (10.4.8) Power Mac G5 and Powerbook

you will need to create your own main index if that is what you are referring to ...
i used to do something similar ...
here are a few threads ...
http://discussions.apple.com/thread.jspa?messageID=3297833&#3297833
this talks about adding links into a web theme ...
http://discussions.apple.com/thread.jspa?messageID=3897773

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>);

Saving WebI report with links to desktop in pdf format

I have a user who is asking if a WebI report with drill down links can be saved to his desktop as a pdf and still have the links work. Has anyone had the same request?

it´s ocurrs because the drill down that you have in the query, try with another query and export this to a PDF and if you can access ... is that is not possible to use the link for a drill down in a PDF.
good luck!

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.

Insert Record with Parent/Child Tables doesn't work with Oracle - unlike AC

Hi,
I just Migrated a MS Access 2010 Database to an Oracle 11g Backend with the SQL Developer Tool.
The Migration went fine, all the Tables and Views are migrated.
I'm working with MS Access as Frontend.
The application has some Datasheets with Subdatasheets with Parent/Child Relationship. (1-n Relationship)
After changing to Oracle, it's not possible, to Insert a new Record in a Subdatasheet I always get the following Error Message:
"The Microsoft Access database engine cannot find a record in the table 'xxxx' with key matching field(s) 'zzzzz'"
It used to work perfect with the MS Access Backend, do I need a trigger which first adds the child Record ?
Or what should I do?
Thank you

Hi Klaus,
Thanks for your answer. I still haven't solved my problem. The only way would be to use a singel 1:n Relationship, but in fact I need a n:m Relationship.
I tried the same scenario with a new Access Application, same result.
To clearify my problem.
Goal: Parent Form with Parent Records, Linked Child Form with Child Records in a Datasheet View => Insert of a NEW Child Record.
I have 3 Tables (table1 = Parent tabel, table2 = Child Table, table12 = n:m Tabel with PK and two FK)
The Recordsource of the Parent Form is Tabel1
The Recordsource of the Child Form is Table2 joined with Table12.
In my Old Access Project, Access Triggered the Insert and filled Table12 with the NEW PK of Table2.
It seems like Access can't do that anymore....
I'm pretty desperate and I'm sure it is just a litte thing to fix.....

Web services with JAXB

Hi All,
I am new to Web services with JAXB in ECLIPS.
When I tried to unmarshal the XML file, I am getting the following exception.
javax.xml.bind.UnmarshalException: unexpected element (uri:"", local:"order"). Expected elements are <{http://webservices/}read>,<{http://webservices/}readResponse>
     at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.handleEvent
xml , schema and java class are in follow.
Please help me to solve this issue.
Mohseni Rad.
----------------------------------po.xsd-----------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="order" type="OrderType"/>
<xsd:complexType name="OrderType">
<xsd:sequence>
<xsd:element name="shipTo" type="xsd:string"/>
<xsd:element name="billTo" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
------------------------------------po.xml----------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<order>
<shipTo>shipto</shipTo>
<billTo>billto</billTo>
</order>
------------------TestWS.java---------------------
import java.io.FileInputStream;
import java.io.IOException;
import javax.xml.bind.JAXBContext;
import javax.xml.bind.JAXBElement;
import javax.xml.bind.JAXBException;
import javax.xml.bind.Unmarshaller;
import wsclient.*;
public class TestWs {
     public static void main(String[] args) {
          try{
               SecondWebServices webService = new SecondWebServicesService
.getSecondWebServicesPort();
               JAXBContext jctx = JAXBContext.newInstance("wsclient");
               Unmarshaller unmarshaller = jctx.createUnmarshaller();
               FileInputStream fl = new FileInputStream( "etc//po.xml" );
     JAXBElement<?> order = (JAXBElement<?>)unmarshaller.unmarshal( fl );
               OrderType orderType = (OrderType)order.getValue();
               webService.read( orderType);
          }catch (JAXBException je) {
               je.printStackTrace();
          catch (IOException ioe) {
               ioe.printStackTrace();
}

Hi,
When you are using JAX-WS, there is a tool wsimport, with which you are going to generate the artifacts required to implement the web service.
When you pass the WSDL as a parameter to the wsimport tool, it will be create the required beans also(JAXB Objects).
So need of any other external implementation of JAXB when you are working with JAXWS
Thanks,

Books for web developement with oracle 10.1.2 Jdeveloper

I a new to web developement with ADF BC. Steve's toystore is of great help.However to built of my basics and sharpen my knowledge,I want to buy a few books.Can anyone recommend any good books with project oriented approach for webdevelopment.
For nowI am buying:
1 Oracle Application Server 10g Administrative HAndBook
2. Oracle Application Server 10g Web Development
3. Enterprise Java Developemnt with JDeveloper
Can anyone tell me how these books are? If now, what should I buy?
Thanks

I am having similar issues, did you ever find a solution?

Web services with XFire.

Hi,
I am completely new to web service with XFire topic and want to work on any sample application to get some idea on web services with XFire.

check your Tomcat documentation and try to test with relative path
Edited by: RezaRavasizadeh on Sep 2, 2008 5:40 PM

Customizing parent folder link options in DiscussionForum Layout set

Hi All,
I have created a forum page with discussionForum layout set.Now, it shows the discussion groups inside it with parent folder link at the top.this parent folder link has some options like view,coolaboration,details etc which I need to customize...
By parent folder I mean like if A has x,y,z discussion groups:
If you click on x then, parent folder link changes to:
A-->x...there is a option menu just besides this link which I need to customize.
Can anyone give a clear idea to this problem??
With Regards,
Udit

Hi Udit,
Pls follow the below steps,
1. Go to sys admin> sys configuration> Knowledgemanagement --> content management -- >user interface.> settings> layout set
2. Search for Discussion layout set and open it.
3. In Collection renderer field, click on the link discussion group bread crumb
4. In the subsequent window, click on the collection command group : discussiongroupbreadcrumbcommandgroup.
5.in the next window, edit the command list field as per your requirement and save.
Pls reward for helpful answer.
Rgds,
Siva

New Aperture Web Themes with 'Parent INDEX' link

Similar Messages

Maybe you are looking for