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.

Sign up for GitHub

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

Jump to bottom

Introduce one canvas technique #41

Open
rexim opened this issue Sep 10, 2015 · 4 comments
Open

Introduce one canvas technique #41

rexim opened this issue Sep 10, 2015 · 4 comments
Assignees
@rexim
Labels
feature meta

Comments

@rexim
Copy link
Member

rexim commented Sep 10, 2015

Introduce one canvas technique discovered in #9

In the future I'll split this issue into the set of smaller ones.
@rexim rexim self-assigned this Sep 10, 2015
@rexim
Copy link
Member Author

rexim commented Sep 11, 2015

I don't know... The last Tsoding has shown that it looks pretty well even with the cell sprite technique. Maybe we don't even need this.

@rexim rexim added the meta label Sep 11, 2015
@rexim
Copy link
Member Author

rexim commented Sep 29, 2015

We don't need that in this game

@rexim rexim closed this as completed Sep 29, 2015
@rexim rexim removed the backlog label Oct 3, 2015
@rexim rexim reopened this Dec 13, 2015
@rexim rexim mentioned this issue Dec 13, 2015
Open
This was referenced Jan 30, 2016
Closed
Closed
rexim added a commit that referenced this issue Jan 31, 2016
@rexim
Start branch for #41 meta feature, retarget badges
3bf437a 
Meta feature #41 requires lots of changes that are pretty risky. We
gonna develop it in a separate branch. All the subtasks related to #41
should be merged to this branch. Once the implementation is ready and
has sufficent performance, we gonna merge this branch to the
master. This makes it easier to decline everything related to the one
canvas technique if something goes wrong.
@rexim rexim mentioned this issue Jan 31, 2016
Closed
@rexim
Copy link
Member Author

rexim commented Jan 31, 2016

After finishing this feature, the game should not change visually. The only difference is gonna be that the game field is a single image. The game mechanic should remain tiled. After that we will be able to compare the performance of the tiled and single image rendering approaches. Once the performance of the single image rendering is sufficiently optimized we gonna start implementing #185. That's basically the plan.

@rexim rexim mentioned this issue Jan 31, 2016
Closed
@rexim
Copy link
Member Author

rexim commented Feb 7, 2016

This feature requires lots of changes that are pretty risky. We gonna develop it in a separate branch. All the subtasks related to this task should be merged to the branch. Once the implementation is ready and has sufficent performance, we gonna merge the feature branch to the master. This makes it easier to decline everything related to the one canvas technique if something goes wrong.

This was referenced Feb 7, 2016
Merged
Open
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rexim rexim

Labels
feature meta
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rexim