Results for comma-number

Yukichi is a Gem of money. Now I can only separate them with commas every 3 digits, but I will add a function to add a yen mark.

Commatose makes it easy to split your numbers by commas.

Command prompt that can use comma-separated numbers

You can combine your N strings/arrays on a delimeter by using method 'Stringify.Combine_with(delimeter, <comma separated strings/arrays>)'. You can join any number of strings with strings or strings with arrays or arrays with arrays.

This a command line Ruby game developed through the PragmaticStudio Ruby programming online course. It can read in a player comma delimited file containing the player's name and their starting health. Then the user can select the number rounds to play, and the game will cycle through wooting and blamming the players and along they way the pickup treasures for points.

A simple, text-based crowdfunding simulator. Run a group of projects through a series of funding rounds, in which they either receive or lose funds, or are skipped. They also receive a random pledge. Grant projects never lose funds. Match projects have all future funding matched after they reach half-funding. Statistics are printed to the console at the end of the simulation. The normal projects can be specified in a '.csv' file that is given as a command line argument when loading the program, or the default projects can be used. The format for 'csv' entries is Project Name,Goal,Initial_funding with a comma and no spaces between entries and underscores in place of commas within larger numbers (e.g. Your Project,10_000,0). The option is given to save a list of underfunded projects upon exiting the program. The list is saved in 'underfunded.txt' in the top-level folder of the application. Created as a bonus project while completing the Pragmatic Studio Ruby Programming course.

Studio Game is a simple text-based, fully random game. To install the gem, run `gem install pragma_studio_game-1.0.0.gem`. To play, run `studio_game` and choose the number of rounds. The players will be loaded from the `bin/players.csv` file. If you want to load your own players, pass the path as an argument to the `studio_game. Players should be provided with their names and health value, comma separated. At the end of the game, high scores will be sorted and written to the `high_scores.txt` file. To quit any time, type in `quit` or `exit`. To uninstall the gem, run `gem uninstall studio_game`.

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 !! =)

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 !!!

Welcome to Banco ! Banco has been developed to summarize statements downloaded from your bank. Install as a Rubygem, navigate to the directory your .csv files are in and execute from the command line with 'banco'. Banco will only accept comma seperated value files (.csv) and will produce a summary for the period uploaded from the file. Remove the header line from your downloaded bank statement, ensure the columns are ordered date, description, type of charge, money in an money out from left to right, any columns right of the fifth will be ignored. Banco will total the incoming & outgoing transactions for the period. Reporting the bottom line aswell as summing up the values for similar transactions. This is achieved by matching the description name, currently set at the first 9 characters of the string, (:total_outgoing :total_incoming - class Reporter), you can change this to be more or less exact. Hope your numbers are positive ! https://github.com/s33dco/banco https://rubygems.org/gems/banco

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!

The Tripletex API is a **RESTful API**, which does not implement PATCH, but uses a PUT with optional fields. **Actions** or commands are represented in our RESTful path with a prefixed `:`. Example: `/v2/hours/123/:approve`. **Summaries** or aggregated results are represented in our RESTful path with a prefixed <code>&gt;</code>. Example: <code>/v2/hours/&gt;thisWeeksBillables</code>. **"requestID"** is a key found in all validation and error responses. If additional log information is absolutely necessary, our support division can locate the key value. **Download** the [swagger.json](/v2/swagger.json) file [OpenAPI Specification](https://github.com/OAI/OpenAPI-Specification) to [generate code](https://github.com/sveredyuk/tripletex_ruby). This document was generated from the Swagger JSON file. **version:** This is a versioning number found on all DB records. If included, it will prevent your PUT/POST from overriding any updates to the record since your GET. **Date & DateTime** follows the **ISO 8601** standard. Date: `YYYY-MM-DD`. DateTime: `YYYY-MM-DDThh:mm:ssZ` **Sorting** is done by specifying a comma separated list, where a `-` prefix denotes descending. You can sort by sub object with the following format: `project.name, -date`. **Searching:** is done by entering values in the optional fields for each API call. The values fall into the following categories: range, in, exact and like. **Missing fields or even no response data** can occur because result objects and fields are filtered on authorization. **See [FAQ](https://tripletex.no/execute/docViewer?articleId=906&language=0) for more additional information.** ## Authentication: - **Tokens:** The Tripletex API uses 3 different tokens - **consumerToken**, **employeeToken** and **sessionToken**. - **consumerToken** is a token provided to the consumer by Tripletex after the API 2.0 registration is completed. - **employeeToken** is a token created by an administrator in your Tripletex account via the user settings and the tab "API access". Each employee token must be given a set of entitlements. [Read more here.](https://tripletex.no/execute/docViewer?articleId=853&language=0) - **sessionToken** is the token from `/token/session/:create` which requires a consumerToken and an employeeToken created with the same consumer token, but not an authentication header. See how to create a sessionToken [here](https://tripletex.no/execute/docViewer?articleId=855&language=0). - The session token is used as the password in "Basic Authentication Header" for API calls. - Use blank or `0` as username for accessing the account with regular employee token, or if a company owned employee token accesses <code>/company/&gt;withLoginAccess</code> or <code>/token/session/&gt;whoAmI</code>. - For company owned employee tokens (accounting offices) the ID from <code>/company/&gt;withLoginAccess</code> can be used as username for accessing client accounts. - If you need to create the header yourself use <code>Authorization: Basic &lt;base64encode('0:sessionToken')&gt;</code>. ## Tags: - <div class="tag-icon-beta"></div> **[BETA]** This is a beta endpoint and can be subject to change. - <div class="tag-icon-deprecated"></div> **[DEPRECATED]** Deprecated means that we intend to remove/change this feature or capability in a future "major" API release. We therefore discourage all use of this feature/capability. ## Fields: Use the `fields` parameter to specify which fields should be returned. This also supports fields from sub elements. Example values: - `project,activity,hours` returns `{project:..., activity:...., hours:...}`. - just `project` returns `"project" : { "id": 12345, "url": "tripletex.no/v2/projects/12345" }`. - `project(*)` returns `"project" : { "id": 12345 "name":"ProjectName" "number.....startDate": "2013-01-07" }`. - `project(name)` returns `"project" : { "name":"ProjectName" }`. - All elements and some subElements : `*,activity(name),employee(*)`. ## Changes: To get the changes for a resource, `changes` have to be explicitly specified as part of the `fields` parameter, e.g. `*,changes`. There are currently two types of change available: - `CREATE` for when the resource was created - `UPDATE` for when the resource was updated NOTE: For objects created prior to October 24th 2018 the list may be incomplete, but will always contain the CREATE and the last change (if the object has been changed after creation). ## Rate limiting in each response header: Rate limiting is performed on the API calls for an employee for each API consumer. Status regarding the rate limit is returned as headers: - `X-Rate-Limit-Limit` - The number of allowed requests in the current period. - `X-Rate-Limit-Remaining` - The number of remaining requests. - `X-Rate-Limit-Reset` - The number of seconds left in the current period. Once the rate limit is hit, all requests will return HTTP status code `429` for the remainder of the current period. ## Response envelope: ``` { "fullResultSize": ###, "from": ###, // Paging starting from "count": ###, // Paging count "versionDigest": "Hash of full result", "values": [...list of objects...] } { "value": {...single object...} } ``` ## WebHook envelope: ``` { "subscriptionId": ###, "event": "object.verb", // As listed from /v2/event/ "id": ###, // Object id "value": {... single object, null if object.deleted ...} } ``` ## Error/warning envelope: ``` { "status": ###, // HTTP status code "code": #####, // internal status code of event "message": "Basic feedback message in your language", "link": "Link to doc", "developerMessage": "More technical message", "validationMessages": [ // Will be null if Error { "field": "Name of field", "message": "Validation failure information" } ], "requestId": "UUID used in any logs" } ``` ## Status codes / Error codes: - **200 OK** - **201 Created** - From POSTs that create something new. - **204 No Content** - When there is no answer, ex: "/:anAction" or DELETE. - **400 Bad request** - - **4000** Bad Request Exception - **11000** Illegal Filter Exception - **12000** Path Param Exception - **24000** Cryptography Exception - **401 Unauthorized** - When authentication is required and has failed or has not yet been provided - **3000** Authentication Exception - **9000** Security Exception - **403 Forbidden** - When AuthorisationManager says no. - **404 Not Found** - For content/IDs that does not exist. - **6000** Not Found Exception - **409 Conflict** - Such as an edit conflict between multiple simultaneous updates - **7000** Object Exists Exception - **8000** Revision Exception - **10000** Locked Exception - **14000** Duplicate entry - **422 Bad Request** - For Required fields or things like malformed payload. - **15000** Value Validation Exception - **16000** Mapping Exception - **17000** Sorting Exception - **18000** Validation Exception - **21000** Param Exception - **22000** Invalid JSON Exception - **23000** Result Set Too Large Exception - **429 Too Many Requests** - Request rate limit hit - **500 Internal Error** - Unexpected condition was encountered and no more specific message is suitable - **1000** Exception

No description provided.

No description provided.

No description provided.

No description provided.