[x3d-public] [x3dom-developers] ElevationGrid for the modern age

[Joe D Williams]

> as I wanted to see first that anyone can contribute useful 
> improvements to the X3D spec, not just ...

Now you don't need no ticket
You Don't pay no Fee

updated keystrokes for new or changed spec keystrokes is the goal.
Typically, the X3D team wants to start with a comment made to the web 
comments, then entered into the 'bug' tracker. See Don or Leonard for 
a special time to discuss progress on what you have done to date.

time at the editor's meeting and multiple running examples and 
historical background really helps a lot always major filtering going 
on.

Because that was the River,
This is the Sea.

> well, it was discouraging, to be honest.

well, maybe something else important was happening in this ponderous 
upgrade of VRML and implication of the idea that HTML will support 
X3D.
seem to recall several folks working on various aspects of texture and 
wondering about new opportunites of X3DOM. - lots of connections - and 
the key is collaboration of experts to define best practices and 
expected results and get those communicated to the appropriate working 
group.

Thanks, Joe

----- Original Message ----- 
From: "Michalis Kamburelis" <michalis.kambi at gmail.com>
To: "Don Brutzman" <brutzman at nps.edu>
Cc: "x3dom mlist" <x3dom-users at lists.sourceforge.net>; "X3D Graphics 
public mailing list" <X3D-Public at web3d.org>; "x3dom-developer mlist" 
<x3dom-developers at lists.sourceforge.net>
Sent: Saturday, January 31, 2015 4:14 PM
Subject: Re: [x3d-public] [x3dom-developers] ElevationGrid for the 
modern age


>> If you or others have a good example scene or two that can be 
>> released as
>> part of the Web3D Consortium's open-source example archives, that 
>> would be
>> an important step towards encouraging support.  Probably would land 
>> in the
>> Basic archives somewhere.
>
> My testcases on
> http://castle-engine.sourceforge.net/x3d_multi_texturing.php were
> specifically released as public domain (including data, i.e. images
> and movies inside) in the hopes of getting included in official X3D
> example/testcase archive :) Please do use them.
>
> It is *very* good to know that the issue is still on the roadmap of
> next X3D version, thanks :) The lack of any actual change in the X3D
> spec, after I reported the problems of multi-texturing a couple of
> times, on the mailing list and as spec comments, and prepared test
> cases... well, it was discouraging, to be honest. It is also made me
> unsure about joining the consortium --- as I wanted to see first 
> that
> anyone can contribute useful improvements to the X3D spec, not just
> people that officially joined the consortium (and signed some papers
> and paid some fee).
>
> Maybe I gave up too quickly:) Thanks for the good words,
> Michalis
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org