tsoding / gross Goto Github PK

• Introduced in #10

It would be good to have support for some bitmaps, but at the moment I don't know how the signature of Picture::Bitmap should look like.

Gloss implements some kind of BitmapData. Maybe we should implement something similar

• Suggested by @NinjaTrappeur

Research how to enforce order of transformations on the typelevel.

NinjaTrappeur: yes, I am not familiar enough with rust for having a precise idea. Is there any way to make a type polymorphic? In haskell I would create a Picture typeclass with a render function and would use the data constructor in order to "incorporate" the operation in the type system

It should look good to represent the project.

• Introduced in #10

• Introduced in #10

I think in Gloss it behaves a little bit different. We apply the closest color. But Gloss I think does the opposite. We need to research that.

Uses of the library should be able to define their own event handler the allow them to mutate state when something happens.

It should translate Vec<Picture> to Picture::Pictures

• Introduced in #26

• Introduced in #10

• Derived from #11
• Blocked by #13

Use https://github.com/rexim/working-opengl-example-in-rust-omg-iwanna-die

• Blocked by #6

simulate entry point from Gloss provides a default navigation. We have to have something like that.

I don't really want to implement it as it's done in Gloss. In Gloss it looks like simulate and play are implemented separately. I want our simulate to be implemented in terms of play with some default event handlers that provide the navigation abilities. Furthermore I want those navigation handlers to be available to the user so they can wrap around them if they need to extend the navigation behaviour.

• Introduced in #26

• Introduced in #10

• Introduced in #10

• Introduced in #10
• Blocks #21

From Graphics.Gloss.Data.Picture:

Picture elements we definetly need:

• Blank
• Line
• Polygon
• Circle
• Text
• Bitmap

Picture combinators we definetly need:

• Color
• Pictures
• Translate
• Rotate
• Scale

Picture elements I'm not sure we need:

• ThickCircle
• Arc
• ThickArc

• Introduced in #10

• Introduced in #10

• Introduced in #28