[x3d-public] Browser Comparison > sorting, Levels for GLTF and HTML
GPU Group
gpugroup at gmail.com
Thu Feb 2 08:46:20 PST 2023
https://docs.google.com/spreadsheets/d/1p51wgwlGxUfgWOaCM6QkJ9AJ6VONimYu/edit?usp=share_link&ouid=100938900505038082978&rtpof=true&sd=true
- .xlsx (no macros)
- VLOOKUP in one column
Don don't lose too much sleep over this, it's me trying to answer the
question 'these guys are weird, why don't they do it like I would' which is
more about automation.
And gaining respect for 'Archival Quality' which I don't yet understand,
but seems important to you.
The CN columns look ugly and technical, perhaps not archival quality? One
idea is to gray them out, put a QC super header on those columns,
-- presumably people understand their may be QC (Quality Control) columns
in archival quality spreadsheets, and they can ignore if greyed out
There is another way, and that's to use external automation and
semi-automation
- a python or ruby-on-rails or PowerShell script would load the 'archival
quality' .xlsx,
-- add any temporary columns for processing
-- do the processing in passive mode - looking for missing or wrong things
based on the central data store / schematron - and reporting them to the
console for human manual fixing
-- do automated generation - sheets could be marked as 'manually
maintained' and 'autogenerated', so humans would directly edit the manually
maintained sheets, and let the tool auto-generate the other sheets.
- then the process could strip out the extra processing columns and print
out the flat .xlsx.
-Doug
On Thu, Feb 2, 2023 at 9:03 AM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:
> Doug, please send me the “plain” .xslx modification you’ve prepared and I
> will see if this can be diffed/integrated.
>
>
>
> Otherwise let’s simply modify the existing version-control spreadsheet
> step by step, as possible, during the Friday conference. It will also be
> good to discuss your related efforts on browser support and Audio nodes,
> thanks for steadily sharing these important steps.
>
>
>
> We might need to reserve some of the time for the Metaverse Standards
> Forum proposal first, hopefully that is nearing escape velocity.
>
>
>
> all the best, Don
>
> --
>
> Don Brutzman Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA
> +1.831.656.2149
>
> X3D graphics, virtual worlds, Navy robotics https://
> faculty.nps.edu/brutzman
>
>
>
> *From:* GPU Group <gpugroup at gmail.com>
> *Sent:* Tuesday, January 31, 2023 12:36 PM
> *To:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
> *Cc:* X3D Graphics public mailing list <x3d-public at web3d.org>
> *Subject:* Re: [x3d-public] Browser Comparison > sorting, Levels for GLTF
> and HTML
>
>
>
> NPS WARNING: *external sender* verify before acting.
>
>
>
> Don,
>
> Details of changes I made to the X3DNodeInventoryComparison.xlsx to sort
> by component
>
> -Doug
>
>
>
> 1. on 'Node Profiles Component Levels' sheet
>
> a. inserted column 'CN' (component number) after the Component column, and
> made it 2 digits wide
>
> b. populated CN with the component number, using the chapter number for
> components in the Architecture guide
>
> beside Core I put 7
>
> b. deleted 'damaged text' preventing LOOKUP, from X3D
> Abstract Specification Nodes, Statements column, and retyped:
>
> ProtoBody
>
> ProtoDec;lare
>
> ProtoInstance
>
> ProtoInterface
>
> 2. on X3D Players and Tools Sheet
>
> a. deleted damaged text and retyped, in Node and Statement Support column:
>
> Matrix3VertexAttribute
>
> Matrix4VertexAttribute
>
> b. inserted column 'CN' as first column and made 2 digits wide
>
> c. added a VLOOKUP function in A5 (first row and new CN column - we'll
> pull CN numbers from the Profiles sheet)
>
> =VLOOKUP(B5,'Node Profiles Components Levels'!A4:G280,5,FALSE)
>
> -then duplicated that function down the CN column (by dragging with +) to
> row 280
>
> (CN column should now have the component number for the node)
>
>
>
> 3. Macros (they are handy but unsafe if from untrusted sources)
>
> I'll give you the 'algorithm' first so they can be re-recorded or done
> manually. then append the VB macros
>
> SORT_BY_NODENAME
>
> - select range A5:I280
>
> - custom sort, no headers, ascending, column B
>
> - unselect all
>
> SORT_BY_COMPONENT
>
> -- select range A5:I280
>
> - custom sort, first level no headers, column A, ascending
>
> - add second level to custom sort, no headers, column B, ascending (this
> keeps node names ascending within a component)
>
> - deselect all
>
>
>
> By showing the recorded and edited macros here, you can see how the sorts
> are done on the X3D Players and Tools sheet
>
> Sub SORT_BY_NODENAME()
>
> '
>
> ' SORT_BY_NODENAME Macro
>
> '
>
> ' Keyboard Shortcut: Ctrl+Shift+N
>
> '
>
> Range("A5:I280").Select
>
> ActiveWorkbook.Worksheets("X3D Players and
> Tools").Sort.SortFields.Clear
>
> ActiveWorkbook.Worksheets("X3D Players and
> Tools").Sort.SortFields.Add2 Key:= _
>
> Range("B5:B280"), SortOn:=xlSortOnValues, Order:=xlAscending,
> DataOption _
>
> :=xlSortNormal
>
> With ActiveWorkbook.Worksheets("X3D Players and Tools").Sort
>
> .SetRange Range("A5:I280")
>
> .Header = xlGuess
>
> .MatchCase = False
>
> .Orientation = xlTopToBottom
>
> .SortMethod = xlPinYin
>
> .Apply
>
> End With
>
> Range("A3:A3").Select
>
> End Sub
>
>
>
> Sub SORT_BY_COMPONENT()
>
> '
>
> ' SORT_BY_COMPONENT Macro
>
> '
>
> ' Keyboard Shortcut: Ctrl+Shift+C
>
> '
>
> Range("A5:I280").Select
>
> ActiveWorkbook.Worksheets("X3D Players and
> Tools").Sort.SortFields.Clear
>
> ActiveWorkbook.Worksheets("X3D Players and
> Tools").Sort.SortFields.Add2 Key:= _
>
> Range("A5:A280"), SortOn:=xlSortOnValues, Order:=xlAscending,
> DataOption _
>
> :=xlSortNormal
>
> ActiveWorkbook.Worksheets("X3D Players and
> Tools").Sort.SortFields.Add2 Key:= _
>
> Range("B5:B280"), SortOn:=xlSortOnValues, Order:=xlAscending,
> DataOption _
>
> :=xlSortNormal
>
> With ActiveWorkbook.Worksheets("X3D Players and Tools").Sort
>
> .SetRange Range("A5:I280")
>
> .Header = xlGuess
>
> .MatchCase = False
>
> .Orientation = xlTopToBottom
>
> .SortMethod = xlPinYin
>
> .Apply
>
> End With
>
> Range("A3:A3").Select
>
> End Sub
>
>
>
> On Tue, Jan 31, 2023 at 1:02 PM Brutzman, Donald (Don) (CIV) <
> brutzman at nps.edu> wrote:
>
> Please send all changes to me (Don Brutzman) and cc: X3D-Public list. If
> there is discussion we get to it Fridays. If people send something way
> convoluted then nothing happens. Same as always.
>
>
>
> all the best, Don
>
> --
>
> Don Brutzman Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA
> +1.831.656.2149
>
> X3D graphics, virtual worlds, Navy robotics
> https://faculty.nps.edu/brutzman
> ------------------------------
>
> *From:* GPU Group <gpugroup at gmail.com>
> *Sent:* Tuesday, January 31, 2023 11:40:16 AM
> *To:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
> *Cc:* X3D Graphics public mailing list <x3d-public at web3d.org>
> *Subject:* Re: [x3d-public] Browser Comparison > sorting, Levels for GLTF
> and HTML
>
>
>
> NPS WARNING: *external sender* verify before acting.
>
>
>
> Don how do I submit changes to the archival quality spreadsheet you gave a
> link to?
>
> Thanks, Doug
>
>
>
> On Tue, Jan 31, 2023 at 9:59 AM Brutzman, Donald (Don) (CIV) <
> brutzman at nps.edu> wrote:
>
> John, why not use our published links? I won’t be maintaining documents
> at Google Docs links, they are not archival.
>
>
>
> - https://www.web3d.org/specifications
> - *Updated.* X3D Node Inventory Comparison
> <https://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx>
> (.pdf
> <https://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf>)
> shows node-by-node implementation coverage of the
> X3D Abstract Specification: validation using X3D Schema, X3D DOCTYPE, and
> X3D Schematron; X3D Tooltips and VRML97 node sets; plus selected
> open-source implementations: FreeWrl, X3DOM, X_ITE, view3dscene (Castle
> Game Engine), X3D-Edit, Xj3D.
> - https://www.web3d.org/specifications/X3dNodeInventoryComparison.xlsx
> - https://www.web3d.org/specifications/X3dNodeInventoryComparison.pdf
>
>
>
> As ever, I am happy to integrate and publish all changes and additions to
> the spreadsheet. It is also maintained in version control so that we have
> the reliability of a full change-by-change history.
>
> -
> https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsourceforge.net%2Fp%2Fx3d%2Fcode%2FHEAD%2Ftree%2Fwww.web3d.org%2Fspecifications&data=05%7C01%7Cbrutzman%40nps.edu%7C7084ff45e87d43c9aa3908db03cad775%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638107941956975660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DtrZYFuEG%2FeSjdxHH81PvwkXAAsfsfoC9gLnO8VJps8%3D&reserved=0>
>
>
>
> If the spreadsheet above contains macros that should be removed, we can
> work on that. Meanwhile the PDF version (published from the spreadsheet)
> should be secure to everyone’s satisfaction, on whatever operating system
> and tool setup that they are using.
>
>
>
> Some of your notes below sound pretty extensive… feel free to explore new
> comparisons using whatever document you like, we can integrate later once
> it reaches some level of stability.
>
>
>
> Further improvements always welcome, this is a recurring weekly topic on
> X3D Working Group videoconferences. Again thanks for further pursuit of
> progress.
>
>
>
> all the best, Don
>
> --
>
> Don Brutzman Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA
> +1.831.656.2149
>
> X3D graphics, virtual worlds, Navy robotics https://
> faculty.nps.edu/brutzman
>
>
>
> *From:* x3d-public <x3d-public-bounces at web3d.org> *On Behalf Of *GPU Group
> *Sent:* Monday, January 30, 2023 6:41 PM
> *To:* X3D Graphics public mailing list <x3d-public at web3d.org>
> *Subject:* [x3d-public] Browser Comparison > sorting, Levels for GLTF and
> HTML
>
>
>
>
> https://drive.google.com/file/d/1pJ4vuOAAH_rToCsDNlKqrWv7QvlLmX1f/view?usp=share_link
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1pJ4vuOAAH_rToCsDNlKqrWv7QvlLmX1f%2Fview%3Fusp%3Dshare_link&data=05%7C01%7Cbrutzman%40nps.edu%7C7084ff45e87d43c9aa3908db03cad775%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638107941956975660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=12%2BKaIsuNW1PQ064a%2Fdw%2B4PLDJy7jIMKSAm1UXsla38%3D&reserved=0>
>
>
> X3DNode_DRAFT2.xlsm - has VB macros
>
>
>
>
> https://docs.google.com/spreadsheets/d/1p51wgwlGxUfgWOaCM6QkJ9AJ6VONimYu/edit?usp=share_link&ouid=100938900505038082978&rtpof=true&sd=true
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1p51wgwlGxUfgWOaCM6QkJ9AJ6VONimYu%2Fedit%3Fusp%3Dshare_link%26ouid%3D100938900505038082978%26rtpof%3Dtrue%26sd%3Dtrue&data=05%7C01%7Cbrutzman%40nps.edu%7C7084ff45e87d43c9aa3908db03cad775%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638107941956975660%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xwwyIRAMSC76ONSkABja8AXSpsEg9%2FfC8lxbzNg0Buk%3D&reserved=0>
>
> X3DNode_DRAFT2.xlsx
>
>
>
> the xlsm variant has 2 recorded macros for sorting
>
> SORT_BY_NODENAME
>
> SORT_BY_COMPONENT
>
>
>
> Suggested enhancements:
>
> Levels of GLTF support
>
> Level 0 None
>
> Level 1 .gltf loaded as Inline, basic geometry with materials
>
> Level 2 any enhancements over Level 1: .glb, loading materials as library
> for use in x3d scene, animations and skinning
>
>
>
> Levels of HTML support
>
> Level 0 None
>
> Level 1 hybrid, can show html and scene but no standard
> communicatio between layers / frames
>
> Level 2 standardized way to communicate between scene and html
>
> Level 3 full integration
>
>
>
> -Doug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230202/aa893780/attachment-0001.html>
More information about the x3d-public
mailing list