The big Radiance merge

kazhnuz commented

2022-07-20 14:18:04 +02:00

Owner

Basically : merge all the work on Radiance back to Birb.

The Plan

Adapt naming changes (object -> Classes)
Make a diff and use the list of commit to find all changes between Radiance and Birb
See what to do with divergence like the asset system
Add every self-contained additions, and the one with some changes
Add the modifications
Make gamesystem use the serialization system, port actors to timers system
See what should be part of birb/ in Radiance's game/

All these changes should be done in separate commits, with necessary ports to the examples and looking at what bugs we fixes.

Basically : merge all the work on Radiance back to Birb. The Plan 1) Adapt naming changes (object -> Classes) 2) Make a diff and use the list of commit to find all changes between Radiance and Birb 3) See what to do with divergence like the asset system 4) Add every self-contained additions, and the one with some changes 5) Add the modifications 6) Make gamesystem use the serialization system, port actors to timers system 7) See what should be part of birb/ in Radiance's game/ All these changes should be done in separate commits, with necessary ports to the examples and looking at what bugs we fixes.

kazhnuz commented

2022-07-28 09:13:11 +02:00

Author

Owner

Doing it this way is too much work, so I won't (it's sad for the commit history, but whatever). So I'll replace birb by Radiance's just with one commit, backport birb parts as I can, then replace entirely the exemple for new, Birb-compatible one.

So new plan
-> Replace birb by the whole Radiance one
-> Replace lost API (like Scene:start)
-> Replace the whole exemples
-> Add to birb as much elements from Radiance game/scenes

Later :
-> Rework the asset system

Doing it this way is too much work, so I won't (it's sad for the commit history, but whatever). So I'll replace birb by Radiance's just with one commit, backport birb parts as I can, then replace entirely the exemple for new, Birb-compatible one. So new plan -> Replace birb by the whole Radiance one -> Replace lost API (like Scene:start) -> Replace the whole exemples -> Add to birb as much elements from Radiance game/scenes Later : -> Rework the asset system

kazhnuz referenced this issue

2022-08-03 11:41:20 +02:00

Rebase on Radiance #71

kazhnuz commented

2022-08-03 11:44:35 +02:00

Author

Owner

Maybe for the moment just port the core and adapt the exemple, and create tickets for every interesting modules not in core to backport them to the new birb

kazhnuz commented

2022-08-03 11:54:34 +02:00

Author

Owner

Which would mean:

This ticket
-> Replace the birb folder DONE
-> Replace lost API (like Scene:start and rebase the gamesystem module to use the datasources and serializable)
-> Replace all exemple

Phase two
-> (TODO) List all non-core feature of Radiance, and create tickets to add them to birb (Might be part of a bigger milestone with every tickets, and can be done before this ticket, in a way)
-> Rework the asset system and port exemple to the new one
-> Port the things in the tickets

Which would mean: This ticket -> Replace the birb folder *DONE* -> Replace lost API (like Scene:start and rebase the gamesystem module to use the datasources and serializable) -> Replace all exemple Phase two -> (TODO) List all non-core feature of Radiance, and create tickets to add them to birb (Might be part of a bigger milestone with every tickets, and can be done before this ticket, in a way) -> Rework the asset system and port exemple to the new one -> Port the things in the tickets

kazhnuz added this to the epervier 0.7.0 milestone 2022-08-08 11:30:21 +02:00

kazhnuz added the

labels 2022-08-08 11:50:06 +02:00

kazhnuz closed this issue

2022-08-12 10:38:27 +02:00

The big Radiance merge #66