quote:

---

> I am attempting to conform a world I developed with Cortona viewer for
> cross-viewer compatability with CosmoPlayer and Blaxxun. The world
> works fine with Cortona under IE 6.0 and NN 7.0. Apparently,
> CosmoPlayer and Blaxxun implement relative path names to external
> proto files differently, as compared to Cortona.
>
> In Cortona, the following relative path names for external protos are
> valid:
>
> World.wrl refers to EXTERNPROTO
> --> "lib/SO_proto.wrl" which refers to EXTERNPROTO
> --> "Wire_Sphere_proto.wrl" also located in subdirectory
> lib/
>
> Cortona, correctly, determines the relative path to
> "Wire_Sphere_proto.wrl" is in subdirectory "lib/" (since
> "SO_proto.wrl" is in "lib/" when it is invoked).
>
> In CosmoPlayer and Blaxxun, the above relative referencing path is
> _invalid_. All relative path referencing must be with respect to the
> root of the world, e.g. -
>
> World.wrl refers to EXTERNPROTO
> --> "lib/SO_proto.wrl" which refers to EXTERNPROTO
> --> "lib/Wire_Sphere_proto.wrl" also located in subdirectory
> lib/
>
> The difference between the two syntaxes is:
>
> "Wire_Sphere_proto.wrl" vs. "lib/Wire_Sphere_proto.wrl"
>
> Now my problem and question is this - is there some relative path
> referencing syntax that all three viewers - Cortona, Blaxxun and
> CosmoPlayer - are happy with? "../lib/Wire_Sphere_proto.wrl" does not
> work.
>
> If you have run into this before, please let me know your work around.
>
> I came up with a temporary and inelegant solution to keep all three
> VRML viewers happy, but there has to be a better way.
>
> - Thanks Kurt

---

quote:

---

> One solution, but not the most elegant one would be to put all
> files into the same directory. > Herbert

---

quote:

---

> PrisNo6,
>
> I use relative referencing often and have no problems, perhaps you
> are doing something different. I concocted an example similar to yours
> that works in both Blaxxun and Cortona.
> My directory structure:
> test --> subdirectory
>
> test contains the file top.wrl, subdirectory contains the files
> middle.wrl and bottom.wrl.
>
> bottom.wrl
> PROTO Bottom [] { Shape { geometry Box {} } }
>
> middle.wrl
> EXTERNPROTO Bottom [] "bottom.wrl"
> PROTO Middle [] { Bottom{} }
>
> top.wrl
> EXTERNPROTO Middle [] "subdirectory/middle.wrl"
> #Middle{}
> PROTO Top [] { Middle {} }
> Top {}
>
> It also works if you uncomment the second line, and comment three and four.
>
> From the annotated spec:
>
> 2.5.3 Relative URLs
> Relative URLs are handled as described in [RURL]. The base document for
> EXTERNPROTO statements or Anchor, AudioClip, ImageTexture, Inline,
> MovieTexture, and Script node statements is:
>
> The file in which the prototype is instantiated, if the statement is
> part of a prototype definition.
> The file containing the script code, if the statement is part of a
> string passed to the createVrmlFromURL() or createVrmlFromString()
> browser calls in a Script node.
> Otherwise, the file from which the statement is read, in which case the
> RURL information provides the data itself.
> Take care,
> Muaddib

---

quote:

---

> PrisNo6,
> I use relative referencing often and have no problems, perhaps you
> are doing something different. <snip>

---

quote:

---

> I read this as Cosmo being wrong. I am not really worried about Cosmo,
> though, as I don't develop for it. I am more worried about Xj3D which
> will surely be "spec compliant". > Muaddib

---

quote:

---

> are instanced and not where they are defined I think.

---

quote:

---

> I came up with a temporary and inelegant solution to keep all three
> VRML viewers happy, but there has to be a better way.

---