#game #gui #quicksilver #gamedev

mergui

A simple GUI system for use with the quicksilver game engine

10 releases

✓ Uses Rust 2018 edition

0.1.0-alpha0.5 Jun 6, 2020
0.1.0-alpha0.4 Jun 4, 2020
0.1.0-alpha0.3 May 23, 2020
0.1.0-alpha.1 Apr 26, 2020
0.0.1 Nov 30, 2019

#81 in GUI

Download history 11/week @ 2020-03-04 7/week @ 2020-03-11 15/week @ 2020-03-18 5/week @ 2020-03-25 5/week @ 2020-04-01 22/week @ 2020-04-08 16/week @ 2020-04-15 15/week @ 2020-04-22 4/week @ 2020-04-29 8/week @ 2020-05-06 2/week @ 2020-05-13 31/week @ 2020-05-20 20/week @ 2020-05-27 75/week @ 2020-06-03 6/week @ 2020-06-10 20/week @ 2020-06-17

64 downloads per month

MIT/Apache

195KB
1.5K SLoC

WARNING!

Mergui follows quicksilver 0.4, which at point of writing is in an alpha stage.

Mergui

A simple gui system for the quicksilver engine, originally developed for Arena keeper and later ported to quicksilver 0.4 to be used in my yet to be named card game .

However, I try my best to not let those 2 games shape Mergui and instead focus on how to make Mergui work the best for every game written in Quicksilver.

Why

When I first started with Quicksilver I couldn't find a gui system that worked with it. The result being predictable, every game made their own GUI system which often didn't go further than a button.

After I did the same for Arena keeper and discovered problems with mine I decided to rewrite it and publish it as its own crate so others won't have to.

Widgets

There are multiple widgets. The 3 most important ones are

  • Button.
  • Dropdown
  • Text input field.

For a complete list and how to use them, see the examples. Examples/all.rs has most listed, but doesn't show how to read the state of them. You can also see the examples in action here

Dependencies

~3.5–5MB
~107K SLoC