> 1) The stub projector is now asking for  "Flash Component" xtra.  I only see
> Flash Agent, Flash Asset and Flash Asset options which are all in the stub's
> Xtras folder. What the heck is it looking for, or why is it now looking for
> this? (The app has been fully tested and is bug free- up until trying to
> 'bundle' it.)

The Flash Component Xtra is used by Director MX 2004 as an alternate/new
(though default) button technology. Unless you switch to "Classic" tool
view, your buttons will be Flash Components. If you don't see that xtra,
it's probably been omitted. Are you trying to create the bundle on a machine
that only has MX, while assets were created with MX 2004?

> 2) The app utilizes companion assets that live in folders at the projector
> level. Where do these go now relative to the top level of the bundle? Same
> level, or inside the bundle? Wondering how projector resolves the pathname.
> Is this handled by the system/bundle relationship?

Think of the bundle as nothing more than a directory structure. Because the
projector is inside a folder, any access to assets must be accomplished from
that point. The projector is always found at "the applicationPath". The best
thing to do--especially considered the hybrid question to follow--is keep
all media (everything except your executables) inside a media folder at the
root level fo the CD. You then create a stub projector that does nothing
more than climb out of the bundle directories, and into the media directory,
etc., to go to the first movie you need.

> 3) In the contents level of the bundle I am using DXR and CXTs and pointing
> to them with my stub. Is this correct, or do they need to be shockwave
> projectors too?

They are the correct file format, but you'll probably have to move them out
to a media folder, as described above.

> 4) Also in the example, there was no mention of needing an INI file,
> however, I had to add one with a [Movies] section and "Movie01=::MyDXR.dxr"
> for the projector to start up properly.

An .ini file should not be required, but is recommended if you want to use
any of its benefits. You shouldn't have to use the Movies section, if the
pathname in your stub is correct.

> 5) How  does this effect an hybrid disk where the PC side needs to share the
> companion resources in order to fit all the content on one disk by avoiding
> duplicate content for each side?

As stated above, the media should be in a root folder called "media". The PC
projector is at the root level of the ISO folder, and an alias of the media
folder is created in the root directory of the ISO folder. That takes care
of the PC side. On the Mac side, you just alter your stub's pathnames to
navigate out of the bundle and then into the media folder.

> Overall, this whole bundle structure has wreaked havock on an otherwise
> 'ready to go' app. I need to deliver and don't have a few days to play with
> it until I figure it all out.

If you don't have a few days to test, I would recommend abandoning the
bundle, and just using a folder for OS 9 and a folder for OS X. However,
even that requires that your Mac stubs (or, better, a cross-platform stub
that uses "the platform" in a conditional) be adjusted to navigate out of
the OS folder. If you want to use a bundle, just think of the bundle as
nested folders and adjust your stub paths accordingly.

I hope this helps,
--Rich Shupe


[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[email protected]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for 
learning and helping with programming Lingo.  Thanks!]

Reply via email to