[osg-users] Announcement: VulkanSceneGraph and SceneGraphTestBed!

[michael kapelko]

Since we're talking about standard proposals now, here are some I would want:

1. Provide an option of single header and source file per each module:
vsg.h/cpp, vsgViewer.h/cpp, vsgUtil.h/cpp, etc.

This would greatly simplify referencing VSG across platforms because
CMake has issues under Android (it's part of Android Studio project,
so CMake does not drive building) and iOS (one can build a library
with CMake to be referenced by Xcode project).
So, simple header/source inclusion still wins distribution battle when
you target desktop, mobile, and web at the same time.

2. Conform to `Best Practices Criteria for Free/Libre and Open Source
Software (FLOSS)`
The rules: https://github.com/coreinfrastructure/best-practices-badge/blob/master/doc/criteria.md
Here's how a conforming project looks like:
https://bestpractices.coreinfrastructure.org/ru/projects/289


On 7 June 2018 at 12:32, Björn Blissing <bjorn.blissing at vti.se> wrote:
>
> robertosfield wrote:
>>
>>
>> > And maybe this time we will get header files with the .h extension. ;)
>> >
>>
>> Maybe, no decisions made yet, but I'm also not polling for opinions,
>> the VulkanSceneGraph isn't a design by committee.
>>
>> My initial code experiments have .hpp but frankly it's ugly as hell as
>> well as stupid - there's no header plus plus language so I'm rapidly
>> tiring of .hpp. Code should to be a thing of beauty not some ugly
>> kludge.  .h makes sense as it's a header, .cpp makes sense for source
>> files as it's C++.
>
>
> The ISO cpp guidelines recommend using .h for headers and .cpp for source:
> https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Rs-file-suffix
>
>
> robertosfield wrote:
>> However, public headers are placed into include
>> directories and that's their role, we know they are headers because
>> that's why we put them there, so the .h should be superfluous for
>> public headers and the standard C++ headers illustrate this.  If 3rd
>> party tools/editors can't even handle the extension less C++ standard
>> library headers then they aren't really up to the job.
>>
>
>
> As a Visual Studio user I do disagree (since Visual Studio really seems to dislike extensionless headers). But I also recognize that the decision is your prerogative to make as creator.
>
> Regards,
> Björn
>
> ------------------
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=73993#73993
>
>
>
>
>
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org