Skip to content
This repository has been archived by the owner on Apr 18, 2022. It is now read-only.

Legion: Final Tracker #2517

Closed
18 of 23 tasks
AlveLarsson opened this issue Nov 15, 2020 · 41 comments
Closed
18 of 23 tasks

Legion: Final Tracker #2517

AlveLarsson opened this issue Nov 15, 2020 · 41 comments
Assignees
Labels
Epic Legion Legion related issues. open-when-archived This was open when we decided to archive the repo, so we closed it as per best practices. pri: critical This issue has to be fixed ASAP. For the owning team, nothing else should be worked on.

Comments

@AlveLarsson
Copy link
Collaborator

AlveLarsson commented Nov 15, 2020

Hello! I've been out of the loop for the past months due to some life issues, but now I'm back.

Progress on the Legion port has slowed to a standstill. I'm creating this issue to track what's been done, what still needs to be done, and what our roadblocks are. This issue will act as a new, clean slate to minimize confusion and get us back on track.

Edit this comment to change the lists below, or comment below and someone with write access will update the lists for you.

Current Progress with Names & Links

Who is willing to help? What are you currently working on?

Lastly, we need to communicate frequent updates about what's being done or rather the rate of progress that's happening on each crate as we start work.

Important! Please discuss the legion port on GitHub issues (like this one, or more specific ones), not on discord or the forum. We need to keep the discussion in one place to keep things sane.

(Special thanks to @CleanCut and @jlowry for catch-ups)

@AlveLarsson AlveLarsson added the pri: critical This issue has to be fixed ASAP. For the owning team, nothing else should be worked on. label Nov 15, 2020
@AlveLarsson AlveLarsson added this to the 0.16.0 - Legion milestone Nov 15, 2020
@AlveLarsson AlveLarsson self-assigned this Nov 15, 2020
@AlveLarsson AlveLarsson pinned this issue Nov 15, 2020
@CleanCut CleanCut changed the title Legion, re tracking Legion: Final Tracker Nov 15, 2020
@CleanCut CleanCut added this to To do in Legion integration via automation Nov 15, 2020
@CleanCut CleanCut moved this from To do to Documentation in Legion integration Nov 15, 2020
@valkum

This comment has been minimized.

@jlowry

This comment has been minimized.

@jlowry
Copy link
Contributor

jlowry commented Nov 15, 2020

I am currently working working on #2404 Prefab system in legion by integrating Atelier Assets and Legion Prefab.
On my fork's assets_wip branch, I have atelier integrated and legion prefab working for non nested prefabs (also the system that applys the prefabs automatcally is not done.). This is still needs tidying up but I'm making steady progress.

Currently, I am working on the format part of legion prefab based recommendations by @kabergstrom:

  • to improve the serialisation format to make easier to use when writing prefabs by hand
  • to allow atelier asset handles can be created automatically for nested prefabs and assets within them

@jlowry

This comment has been minimized.

@CleanCut
Copy link
Member

CleanCut commented Nov 15, 2020

Everyone: For work in progress, please branch off of legion_v2 (or something downstream from it) and make a Draft Pull Request for your branch/fork against legion_v2 while you do your work. That way we have a PR to link to, see progress as it occurs, and communicate with you on. Switch the PR out of draft mode when you're ready for a review.

Note: I'm going to attempt aggressively hiding comments that have been resolved. If that ends up being more of a hindrance than a help, please let me know and I can unhide stuff.

  • @BlockCat I see you were working on amethyst_animation in Legion animation #2351 - would you be willing to pick that back up and merge legion_v2 into that branch? Should we add you to the active list?
  • @chemicstry I don't see anything "in progress" from you, but you've been very involved in the past. Should we add you to the active list? Do you have something in progress I'm unaware of?
  • @jlowry As per your comment above I've listed you as the person for amethyst_assets and linked to your PR.
  • @Jojolepro In Discord you said you were not participating any further. If you change your mind, we'd love to have you back! If you are willing to give a summary of where you left off, that would be helpful.
  • @LechintanTudor Do you have a PR out for amethyst_ui somewhere to supersede Port amethyst_ui to legion #2343? You mentioned you were working on amethyst_core in Discord as well - but I don't see a PR for that, either - are you working on both in master in your fork? Should we add you to the active list?
  • @mockersf Would you like to finish up examples? At the point fix examples for legion integration #2483 was left off, it looks like there were CI failures to address. Should I add you to the active list?
  • @thunderseethe I see you had been working on part of amethyst_core in Migrate SystemExt pauseable to Legion #2467 - shall we add you to the active list to finish that up?

I'm also going to shotgun a question to a bunch of notable folks I'm aware of who have been involved in some way in the past -> Would any of you folks like to directly contribute to this effort to finish up and ship Legion integration in Amethyst? Feel free to ignore this ping and unsubscribe from this issue if you're not interested.

I've surely missed some people from these lists. (Sorry--unintentional!) Please pass this along to them! Please speak up if you're willing to contribute.

@CleanCut

This comment has been minimized.

@LechintanTudor

This comment has been minimized.

@CleanCut

This comment has been minimized.

@CleanCut

This comment has been minimized.

@CleanCut

This comment has been minimized.

@jlowry

This comment has been minimized.

@Blisto91

This comment has been minimized.

@jlowry

This comment has been minimized.

@CleanCut

This comment has been minimized.

@chemicstry

This comment has been minimized.

@LechintanTudor
Copy link
Contributor

Here's my draft for amethyst_core #2521

@CleanCut

This comment has been minimized.

@CleanCut
Copy link
Member

For building the amethyst root crate I run:
cargo build --features "metal"

To test things are working, I've been running an example, e.g.:

cargo run --features "metal" --example "asset_custom"

It doesn't solve your problem of crates not compiling with unrelated features. But I find it useful to see what is compiling from the dependency graph (cargo tree | grep amethyst) :

@jlowry Awesome, thank you. That unblocks for reviewing and helping out with other stuff at least.

I still find it maddening not to be able to compile individual crates, so I'm going to continue on my quest to eliminate mandatory features altogether in #2522

@tigleym

This comment has been minimized.

@ezpuzz
Copy link
Contributor

ezpuzz commented Dec 8, 2020

I've updated the pong examples to get through example 4 working and 5 ready for amethyst_ui new version at #2531

@valkum
Copy link
Contributor

valkum commented Dec 9, 2020

Got tiles nearly ready but got stuck with the camera_switch in the tiles example: https://github.com/valkum/amethyst/blob/legion_v2_tiles/examples/tiles/main.rs#L141
I am in a state where the example runs but without the functionality implemented in the camera_switch system.

@CleanCut I would appreciate your input if you got time, hit me up on discord too explain further.

@ezpuzz
Copy link
Contributor

ezpuzz commented Dec 9, 2020

@valkum thanks for this! I'm really glad to see an example of using the legion system macros inside an amethyst project.

@grzi

This comment has been minimized.

@CleanCut
Copy link
Member

CleanCut commented Dec 12, 2020

As per this Discord comment It would be super useful if serde-diffsupported:

#[serde(from = "TransformValues", into = "TransformValues")]
and
#[serde_diff(opaque)]

@jlowry PR is ready for review in amethyst/serde-diff#22

@CleanCut
Copy link
Member

CleanCut commented Dec 14, 2020

Here's a quick status roundup of what I see with a quick look around (I'm sure I've missed some things):

@ezpuzz ezpuzz added Legion Legion related issues. Epic labels Dec 23, 2020
@ezpuzz
Copy link
Contributor

ezpuzz commented Jan 2, 2021

Remaining Tasks for Release:

@ezpuzz ezpuzz linked a pull request Jan 2, 2021 that will close this issue
@ezpuzz ezpuzz removed a link to a pull request Jan 2, 2021
@grzi

This comment has been minimized.

@ezpuzz ezpuzz moved this from Documentation to In progress in Legion integration Jan 19, 2021
@grzi

This comment has been minimized.

@grzi
Copy link
Member

grzi commented Feb 27, 2021

The GLTF port is ready at : #2631

@grzi
Copy link
Member

grzi commented Mar 3, 2021

Spotlights example port to legion : #2651

@B-Reif
Copy link

B-Reif commented Apr 14, 2021

Hey, I'm just exploring amethyst for the first time, I'd be happy to take a stab at working on updating the book. Might need a little guidance.

@aakashhemadri
Copy link

Hey not sure if I should start using 0.15.3 with 0.16 around the corner, Do I wait for the 0.16 release?

@neogeek23
Copy link

In the same boat as @aakashhemadri but a few months later (not wanting to get started with 15.3 if 16.0 is close). The checklist is looking nearly complete atm the only sub crate missing is amethyst_test. Is it reasonable to expect this to release this year?

@CaesarXInsanium
Copy link

oh my goodness,its getting done yass

@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had recent activity. Maybe it's time to revisit this?

@stale stale bot added the stale Issue had no recent activity label Apr 16, 2022
@CleanCut CleanCut added the open-when-archived This was open when we decided to archive the repo, so we closed it as per best practices. label Apr 18, 2022
@stale stale bot removed the stale Issue had no recent activity label Apr 18, 2022
Legion integration automation moved this from In progress to Done Apr 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Epic Legion Legion related issues. open-when-archived This was open when we decided to archive the repo, so we closed it as per best practices. pri: critical This issue has to be fixed ASAP. For the owning team, nothing else should be worked on.
Projects
No open projects
Development

No branches or pull requests