0.0
No release in over 3 years
Low commit activity in last 3 years
There's a lot of open issues
Bits of tooling I use for working with tilesets
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.0, >= 1.0.3
~> 1.11, >= 1.11.2
~> 12.3, >= 12.3.3
~> 6.2, >= 6.2.1
>= 0.90.0, ~> 0.90
~> 3.3, >= 3.3.6

Runtime

>= 1.3.0, ~> 1.3
~> 2.19, = 2.19.2
~> 2.0, >= 2.0.3
~> 4.10, >= 4.10.1
~> 4.7, >= 4.7.2
 Project Readme

tileset_tooling¶ ↑

<img src=“https://github.com/calestar/tileset_tooling/workflows/Ruby/badge.svg?branch=master” alt=“Build Status” /> <img src=“https://badgen.net/rubygems/dt/tileset_tooling” alt=“Number of downloads” /> <img src=“https://badge.fury.io/rb/tileset_tooling.svg” alt=“Gem Version” />

Bits of tooling I use for working with tilesets.

Use¶ ↑

Install if you need to:

sudo apt-get install imagemagick

You can then clone this repository, and run the following in the cloned directory:

bundle install
bundle exec tileset_tooling help

Documentation for all the commands can be found in tileset_tooling.rdoc.

Contributing to the project¶ ↑

Local setup¶ ↑

Nothing special is needed to run this tool besides the normal runtime environment. You will need to follow the Use section.

Submitting a Pull Request¶ ↑

If you want to work on something, make sure an issue for that feature/bug exists and is approved. If it is not, you might spend time on something that won’t be merged into master.

Once you select work to be done:

  1. Fork the repository

  2. Create a branch with either the issue ID as name, or a meaningful name

  3. Work on the branch, make sure to rebase often since only branches on tip of master will be accepted

  4. Make sure to add new tests/features/documentation in your branch

  5. Create pull request, wait for feedback

Generating tileset_tooling.rdoc¶ ↑

This file contains all the documentation for all the commands. It is automatically generated by gli when running:

bundle exec tileset_tooling _doc

Validating gem before pushing¶ ↑

Easiest way to validate the gem is to create a RVM virtual environment. In order to do so, simply run the following:

$ gem build tileset_tooling.gemspec
$ rvm gemset create project1
$ rvm gemset use project1
$ gem install tileset_tooling-0.0.1.gem
$ tileset_tooling  help
$ rvm gemset use default
$ rvm gemset delete project1

Credits¶ ↑

Author¶ ↑

Jean-Sebastien Gelinas (aka calestar).

Copyright © 2020 by Jean-Sebastien Gelinas

License¶ ↑

Distributes under the MIT License, see LICENSE.txt in the source distro