Better example structure (Organize examples better) #117

New issue

Closed

opened 2024-05-21 12:04:05 +00:00 by SakulFlee · 0 comments

SakulFlee commented

2024-05-21 12:04:05 +00:00

(Migrated from github.com)

There is still a lot of duplicated code required for each example.
We even moved out the Android bindings for this reason.

Instead of having each example in its own crate, it might be better to make a single crate with ALL examples.
Ideally, we would have some way of selecting an example and running it, but for now feature flags might be the best solution.

We could even add back the Android project.

I just don't know yet how to manage the feature flags for Android dynamically.

OLD BELOW:

We should organize examples better.
Instead of going with super long names like "Examples/RenderServerTriangle", we should split examples into subfolders to group them into categories.

Such categories could be:

Runtime (using the crate, but only Runtime)
RenderServer (using the render server)
Engine (using the full engine) [Note: no examples yet!]

There is **still** a lot of duplicated code required for each example. We even moved out the Android bindings for this reason. Instead of having each example in its own crate, it might be better to make a single crate with **ALL** examples. Ideally, we would have some way of selecting an example and running it, but for now feature flags might be the best solution. We could even add back the Android project. > I just don't know yet how to manage the feature flags for Android dynamically. --- > OLD BELOW: We should organize examples better. Instead of going with super long names like "Examples/RenderServerTriangle", we should split examples into subfolders to group them into categories. Such categories could be: - Runtime (using the crate, but only Runtime) - RenderServer (using the render server) - Engine (using the full engine) [**Note**: no examples yet!]

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

SakulFlee/Orbital#117

No description provided.

Rows
Columns