Wrap functions to work with files
Avatar style for DiceBear
Stylish, intuitive and user-friendly prompt system. Fast and lightweight enough for small projects, powerful and extensible enough for the most advanced use cases.
Make a directory and its parents if needed - Think `mkdir -p`
Fun with Iterables
A generalized and simple hooking API for adding extensibility to applications
Winston-lite-esque Log lib for terminal and browser debugging, with piles of unignorable log tags and marker styles.
a streaming interface for archive generation
Local Lambda development environment
TypeScript SDK for Pump Agent Payments
Trie Data Structure to support cspell.
The command line interface for PostHog 🦔
No description provided.
Opal Runtime for Asciidoctor.js
The magical sticky regex-based parser generator 🧙
Opal Runtime for Asciidoctor.js
Real profanity words banned by Google, extracted from their hidden API before shutdown. Now available as an easy-to-use Node.js library for content filtering.
Elixir grammar for the [Lezer](https://lezer.codemirror.net) parser system.
simple, flexible, fun test framework
[](https://github.com/mongodb-js/zstd/actions/workflows/test.yml)
simple, flexible, fun brightscript test framework for roku scenegraph apps - roku brighterscript plugin
UI Components + streaming, async, high performance, HTML templating for Node.js and the browser.
A node.js module for javascript minification
`Start a promise chain
A more intuitive syntax for performing a variety of file actions. Examples: "/".fwf_filepath.join('usr', 'bin', 'bash').touch FunWith::Files::FilePath.home("Music").glob(:ext => "mp3", :recurse => true) home = FunWith::Files::FilePath.home home.touch( "Music", "CDs", "BubbleBoyTechnoRemixxxx2011", "01-jiggypalooza.mp3" ) home.touch_dir( "Music", "CDs", "ReggaeSmackdown2008" ) do |dir| dir.touch( "liner_notes.txt" ) dir.touch( "cover.jpg" ) dir.touch( "01-tokin_by_the_sea.mp3" ) dir.touch( "02-tourists_be_crazy_mon.mp3" ) end
Manage caveatPatchor.js files for Propane
Funny facts! Create a database with fun facts and share it with your friends! Read file README first!
Navigating noise in your log files can be like trying to cross a busy road and avoid the cars. Frogger makes your log files more fun by adding some good ol' 8 bit color and a bit of formatting.
This RubyGem contais a nice and fun game called Knucleheads (once using the code in your computer, you can call it anything! :) ) The game runs into the command-line, using just the command 'studio_game'. You can choose the number of rounds you want to play and, when exiting, you'll receive the stats of the rounds. You can create a '.csv' file to push new player into the game. The file must have the following structure: ---NAME----|---HEALTH--- (This is just explanatory, not to put into file) Player-name,100 (The comma should appear into each string.) Well what else can I say? Just...have fun, playing and using this humble code into your robust and well-tested program. Good-bye !!!
This is a fun treasure game written in the Ruby programming language. ## Getting Started 1. Install gem: $ gem install treasure_adventure_game 2. At the command prompt: $ treasure_game ## Playing the game Enter a number for the number of game rounds you'd like to play. Enter `quit` to exit and see a listing of the high scores. The program will also write output to a `high_scores.txt` file. ## Upload your own players You have the option to load your own players into the game by passing a `csv` file as an argument: $ treasure_game my_players.csv Your `csv` file should be formatted with player names and initial health numbers. For example: Bob,100 George,60 Sally,125
This RubyGem contains a nice-n-easy funding projects simulation, called FundList. The sim runs in command-line, calling just the command crowd_fund (easy as that :0 ) You can choose the number of funding rounds and it will display the current stats of the projects. You can also create a '.csv' file to hold projects, with a current amount and a target. This file should be put next to the command when calling the sim. File structure: --NAME--|--TARGET--|--AMOUNT-- (This is just for explanatory purpose) Project,1000,100 (The commas must be put into each string of projects, without blankspace.) Have fun on this simulation. If you have any ideas, you can use the code, which already is tested, to create a new, different, sim! Good-bye !! =)
Bus Scheme is a Scheme written in Ruby, but implemented on the bus! Every programmer must implement Scheme as a rite of passage; this is mine. Note that at least half of the implementation of Bus Scheme must be written while on a bus. Documentation, tests, and administrivia may be accomplished elsewhere, but the majority of actual implementation code is strictly bus-driven. Bus Scheme is primarily a toy; using it for anything serious is (right now) ill-advised. Bus Scheme aims for general Scheme usefulness optimized for learning and fun. It's loosely targeting R5RS, but varies in huge ways. (For the purposes of this project we pretend that R6RS never happened.) See the file R5RS.diff for ways in which Bus Scheme differs from the standard, both things that are yet unimplemented and things that are intentionally different. == Usage $ bus # drop into the REPL
Welcome to the "Knuckleheads" game, a (slightly enhanced version of the) fully functional text driven game written in Ruby 1.9 and used as a teaching aid for the excellent web-based Ruby course administered by Pragmatic Studios. W00t! W00t! Before playing, fill the default csv file "players.csv" with any number of players by putting the name of each followed by their initial health (an integer separated from the name by a comma). Each player must be on a new line. You may also create an alternate file formatted the same way with a different name. (A sample alternate player file called "more_nuts.csv" is provided as an example.) Invoke an alternate file simply by entering the file name when prompted. How fun is that!! To start the game, start the Ruby file "studio_game.rb" in Ruby 1.9 (or later should work as well) and follow the directions. By the way, there are two players added in hard code with modified behavior. One is "sandro" a LOSER or "clumsy" player who damages his treasure upon collecting it, resulting in the value of each treasure being worth only half of it's original value. What a klutz! The other is a wild-ass player, "bright_eyes." He's a serious partyier! After every other player is spent, he "finds the last beer in the fridge" and can't help but w00t. Bright_eyes starts off just like everyone else. But after being w00ted six times he goes freak'n w00t-crazy and w00ts EVERY TIME! You better think long and hard before committing to joining Mr. bright_eyes. Legend has it that he eats the livers of his prey after he parties them to death, and in this way remains an immortal player! Now fire up that command line for some outrageous fun! CAUTION: It is addictive. My cousin, Schneebo (the Schneebo on my Dad's side, NOT Schneebo Salifronski) once sat down and played Knuckleheads non-stop for 176.39 hours. It's the truth - you've been warned. Oh, and by the way: Three w00ts for Pragmatic Studios - woot, woot, h00ray! - woot, woot, h00ray! - woot, woot, h00ray!
<!-- TABLE OF CONTENTS --> <details open="open"> <summary>Table of Contents</summary> <ol> <li> <a href="#about-the-project">About The Project</a> <ul> <li><a href="#built-with">Built With</a></li> </ul> </li> <li> <a href="#getting-started">Getting Started</a> <ul> <li><a href="#prerequisites">Prerequisites</a></li> <li><a href="#installation">Installation</a></li> </ul> </li> <li><a href="#usage">Usage</a></li> <li><a href="#roadmap">Roadmap</a></li> <li><a href="#contributing">Contributing</a></li> <li><a href="#license">License</a></li> <li><a href="#contact">Contact</a></li> <li><a href="#acknowledgements">Acknowledgements</a></li> </ol> </details> <!-- ABOUT THE PROJECT --> ## About The Project [![Product Name Screen Shot][Screenshot of gameplay and test list]](https://www.dropbox.com/s/mu1rrbx2mqowjkn/studio-game.png?dl=0) This game is a project built following the [Pragmatic Studio Ruby Course](https://online.pragmaticstudio.com/courses/ruby/). I absolutely adored going through this course, because it was unlike other courses in that the main focus wasn't syntax, but how to build a principle-driven, object-oriented program that contains many of the skills we'd need to build real-world projects. The instructors purposefully created exercises to let us build a program using the skills they demonstrated by building a different program. This wasn't a copy and paste kind of course. This game was actually my second run-through, where I test-drove everything from the start based on the objectives only. Skills I valued developing further with this project: - Test-driven development (50+ tests). - Using inheritance to model "is-a" relationships. For example, a clumsy player *is a* kind of player. - Using mixins (modules) to reuse behaviours that are common between classes, but should not be modeled with an inheritance relationship. A good tip was to look for 'able' behaviors in a class to extract, like 'playable', 'printable', 'taxable' etc. - Using a file block which lets you add in class usage examples that are only run when you run the class file specifically. - Overriding default methods (like sort, and renaming things so that they keep a specific format) Things I struggled with: - Testing behaviour that uses blocks. I had a lightbulb moment when I realised I should test the behaviour performed inside the block on a single item. Testing the output of an entire block is like testing Ruby syntax works. Alternatively, test the before and after state of something that changes as a result of using a block. Cooool. - Puts. It felt wrong to use puts to show the output in the console. I'd like to learn how to seperate the view logic for a command-line project later. Things I did to make it my own: - Wrote a lot more tests for my second run-through. - Noticed and extracted further 'able' behaviours into modules (like printing stats, formatting output and handling csv files). ### Built With * [Ruby (language)](https://www.ruby-lang.org/en/) * [RSpec (framework)](https://rspec.info/) * [Vim (text-editor)](https://www.vim.org/) <!-- GETTING STARTED --> ## Getting Started To get a local copy up and running follow these steps: ### Prerequisites This is an example of how to list things you need to use the software and how to install them. * gem ```sh npm install npm@latest -g ``` ### Installation 1. Install the gem ```sh gem install studio_game_2021 ``` <!-- USAGE EXAMPLES --> ## Usage To play a game from the command-line, open a new command project and run the command-line script like so: ```sh studio_game ``` Or, if you'd like to use the game as a library, here's an example of how to use it in `irb`. You can also check the bottom of each class or module file for further usage instructions ``` >> require 'studio_game/game' => true >> game = StudioGame::Game.new("Knuckleheads") => #<StudioGame::Game:0x007fdea10252d8 @title="Knuckleheads", @players=[]> >> player = StudioGame::Player.new("Moe", 90) => I'm Moe with health = 90, points = 0, and score = 90. >> game.add_player(player) => [I'm Moe with health = 90, points = 0, and score = 90.] >> game.play(1) ``` <!-- ROADMAP --> ## Roadmap I plan to customize this game further now that I have a solid foundation to explore from. It'll be fun to let the players interact with each other more, like swapping treasures, and maybe add some kind of board game with it's own features. That's my next focus. ## Contributing Feel free to fork this project and play around with it. Open to feedback-related pr requests. <!-- LICENSE --> ## License Distributed under the MIT License. See `LICENSE` for more information. <!-- CONTACT --> ## Contact Becca - [@becca9941](https://twitter.com/Becca9941) - becca@essentialistdev.com Project Link: [https://gitlab.com/EssentialistDev/studio-game](https://gitlab.com/EssentialistDev/studio-game) <!-- ACKNOWLEDGEMENTS --> ## Acknowledgements - [Pragmatic Studio](https://online.pragmaticstudio.com/courses/ruby/) for empowering me with awesome new development skills. - [Best-README-Template](https://github.com/Becca9941/Best-README-Template) for helping me write a README for this project.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.