RE: [cgmo-webcgm] ISSUE: aci/viewer association

["Weidenbrueck, Dieter" <dweidenbrueck@ptc.com>]

Lofton,

You are right, I added #2 only for completeness reasons. That's why I
called it a hack, because I don't think that it would be a good
solution.

Dieter 

-----Original Message-----
From: Lofton Henderson [mailto:lofton@rockynet.com] 
Sent: Dienstag, 20. Mai 2008 14:24
To: Weidenbrueck, Dieter; CGM Open WebCGM TC
Subject: RE: [cgmo-webcgm] ISSUE: aci/viewer association

Hi Dieter,

Perhaps I'm misunderstanding the nature of option #2, but it looks like
a fragment.

If so, the assessment of the option should include that we banished ACI
reference from the fragment.

(Perhaps you had some more limited fragement-based ACI file referencing
in mind for option #2?)

-Lofton.

At 05:06 PM 5/19/2008 -0400, Weidenbrueck, Dieter wrote:
>David,
>
>I can see several ways forward here:
>
>(setting an environment variable is not one of them because IT folks 
>don't like if we intrude the system more then necessary)
>
>1. Standardize the location
>Agree on a single location that a viewer has to look at for the file.
>Don't think this would work, too many variants here with Vmware and 
>with server hosted prefs.
>
>2. Use a URL to tell the viewer about a prefs file Create a URI that 
>would tell the viewer where to find a prefs file, e.g.
>...dummy.cgm#acifile(pathToFile)
>The viewer could ignore dummy.cgm and only download the aci file I 
>consider this to be a hack (possibly a bad one)
>
>3. Create a DOM call to tell the viewer myViewer.loadACIFile(fullPath);

>This would be a straightforward way to tell the viewer where to find 
>the file and what to do with it.
>The viewer could then copy the file into a location that it likes, and 
>merge the content with whatever ist own prefs are.
>
>4. Simply provide the aci file to the end user and ask him to store it 
>in a special location Not a good solution, we could stay with what we 
>have now, should be more reliable.
>
>Did I miss an option?
>
>Regards,
>Dieter
>
>-----Original Message-----
>From: Cruikshank, David W [mailto:david.w.cruikshank@boeing.com]
>Sent: Montag, 19. Mai 2008 22:56
>To: CGM Open WebCGM TC
>Subject: [cgmo-webcgm] ISSUE: aci/viewer association
>
> >From the minutes of the TC telecon of 14 May:
>
>AI - Someone should draft an informative annex on how an environmental 
>variable or some such method could be used to specify the file
>
>I think this tells me that the result of the discussion was that we 
>could standardize the format of the the aci, but how it was attached to

>a viewer was "unspecified" except for an informative suggestion?
>
>Can the viewer vendors not implement a common association method?
>
>In the case of myself building an IETP, there is probably not a problem

>if I have to deal with a different method for each vendor, because my 
>IETP is going to use a single viewer.
>
>However, remember, my use case is delivering a web site to a customer 
>with the only requirement that he have an html browser with a WebCGM 
>plugin.
>
>I don't think an informative annex solves this problem.  Or am I 
>missing something?
>
>Dave
>Technical Fellow - Graphics/Digital Data Interchange Boeing Commercial 
>Airplane 206.544.3560, fax 206.662.3734 david.w.cruikshank@boeing.com
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that 
>generates this mail.  You may a link to this group and all your TCs in 
>OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>---------------------------------------------------------------------
>To unsubscribe from this mail list, you must leave the OASIS TC that 
>generates this mail.  You may a link to this group and all your TCs in 
>OASIS
>at:
>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>
>
>--
>No virus found in this incoming message.
>Checked by AVG.
>Version: 7.5.524 / Virus Database: 269.23.21/1455 - Release Date: 
>5/19/2008 5:04 PM