Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove CoreRegistry usage: Part IV #1804

Merged
merged 10 commits into from
Jul 3, 2015

Conversation

flo
Copy link
Contributor

@flo flo commented Jun 29, 2015

Reduces CoreRegistry usage.

It does not conflict with #1797

flo added 4 commits June 29, 2015 20:59
It is done by getting the context from the StateIngame.

It is the only context that contains the wanted property providers.
Only during StateIngame it was actually getting something from the
CoreRegisty.
@GooeyHub
Copy link
Member

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/157/
Hooray Jenkins reported success with all tests good!

@GooeyHub
Copy link
Member

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/158/
Hooray Jenkins reported success with all tests good!

@GooeyHub
Copy link
Member

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/159/
Hooray Jenkins reported success with all tests good!

@Cervator
Copy link
Member

Cervator commented Jul 3, 2015

@immortius able to give this a spin with some review now that #1797 is merged?

@emanuele3d - ping, maybe a bit of interest, there's some rendering and TeraEd in there.

immortius added a commit that referenced this pull request Jul 3, 2015
Remove CoreRegistry usage: Part IV
@immortius immortius merged commit 0376dd9 into MovingBlocks:develop Jul 3, 2015
@emanuele3d
Copy link
Contributor

@immortius was way too efficient for me. Perhaps he wanted to save @flo from a barrage of comments from me? =D

I just had a look and I only found one thing I would have commented about. But it's a very minor, non functional, code style issue and we don't need to worry about. At some point I'll have to put my hands on the WorldRendererImpl class again and I'll do the change then.

@flo
Copy link
Contributor Author

flo commented Jul 5, 2015

@emanuele3d feel free to still create a comment. It is not the last CoreRegistry removal pull request I am creating. So I am happy that @immortius merged it.

@Cervator Cervator modified the milestone: v0.54.0 Jul 28, 2015
@flo flo deleted the no-static-access-part4 branch August 2, 2015 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants