[x3d-public] Availability of X3D viewers -- despite the resource list?
highaspirations at hotmail.com
Mon Jun 8 12:13:59 PDT 2015
Besides object, you can also do an href to your .x3d with most plugins.
Freewrl ignors all params in object, except "src".
KIOSK ~= NO DASHBOARD
I used Flux for a kiosk scenario once, and in kiosk mode you give the user no way to exit except by keyboard, then hide/remove the keyboard. Great for science fairs, museum exhibits etc where people will be using the mouse (or touch screen) to navigate. Flux recognized DASHBOARD=FALSE and would take away any menu bar that would allow the user to use the mouse to exit, or minimize or pick files or in general get out of the scene and into the operating system. Instead of DASHBOARD=FALSE it could have said KIOSK=TRUE.
I used InternetExplorer in kiosk mode:
iexplore -k mypage.html
And in mypage.html I did the object with param DASHBOARD = FALSE and once running, I would unplug the keybaord.
Freewrl doesn't have an exact kiosk mode, although some have hacked it for kiosk. Wouldn't be too hard.
> Date: Mon, 8 Jun 2015 19:20:57 +0200
> From: anthony.judge at gmail.com
> To: x3d-public at web3d.org
> Subject: Re: [x3d-public] Availability of X3D viewers -- despite the resource list?
> Further to my earlier rant on this thread, introduced by the comment
> below, this is a brief note on how I have now resolved my issue in the
> document in question.
> Realizing I needed some kind of "wrapper" for the X3D file, I searched
> using: embed x3d html
> I got the page at:
> and substituted my x3d file in the example (as was the intention) --
> saving it as an htm
> file as at
> This worked, giving me the FreeWRL viewer -- but I believe ONLY
> because I had previously downloaded FreeWRL in earlier explorations.
> Had I not done so, I assume it would not have worked and I would have
> received the default message.
> My point would be, in the spirit of my earlier rant, that the range of
> options for export from X3D Edit could have been more helpful in
> enabling me to get to that point -- especially since I was operating
> against a deadline.
> My recommendation is that some more thought be given to the wording of
> the export options and their relation to the help search. Having just
> used the latter, I could not find the pathway which I had to discover
> otherwise. Casual developers would be similarly frustrated. The issue
> is what kind of wrapper is required for the x3d export and how a
> relatively ignorant person is to find the embed guidance indicated
> I am also amused that at this precise moment I have not yet determined
> what values the params in that example might usefully take. Tjhe
> comments there are not helpful on this matter. I took the default but
> this does not currently give me direct access to the FreeWRL
> dashboard, if I have understood the purpose of that option. There is
> nothing more obscure than the obvious
> On 07/06/2015, Anthony Judge <anthony.judge at gmail.com> wrote:
>> I assume that this comment is somewhat pointless, but for the record...
>> Having struggled successfully over a number of days to produce an
>> animation using X3D Edit, reviewing it locally at each .stage with
>> H3DViewer, and with occasional successful test exports to VRML 97, I
>> reached the point of needing to make the result available in a web
>> document. (now via the document
>> http://www.laetusinpraesens.org/docs10s/infohea5.php) in WRL format at
> Anthony Judge
> <anthony.judge at gmail.com>
> x3d-public mailing list
> x3d-public at web3d.org
More information about the x3d-public