Universal web component to create arbitrary split layouts
No description provided.
Split a string on the first occurance of a given separator
Easy way to split a string on a given character unless it's quoted or escaped.
Universal web component to create arbitrary split layouts
Transform a string between `camelCase`, `PascalCase`, `Capital Case`, `snake_case`, `kebab-case`, `CONSTANT_CASE` and others
split a Text Stream into a Line Stream, using Stream 3
split a Text Stream into a Line Stream
Split a LineString by another GeoJSON Feature.
Split a string into an array based on where an ansi code is present
Split Cypress specs across parallel CI machines for speed
Split string by any separator excluding brackets, quotes and escaped characters
Split JavaScript SDK common components
Simple module to split a single certificate authority chain file (aka: bundle, ca-bundle, ca-chain, etc.) into an array, as expected by the node.js tls api.
React split-pane component with hooks and TypeScript
React component for Split.js
React split-pane component
TypeScript definitions for split2
Split text into sentences with Sentence Boundary Detection (SBD).
Manipulate strings according to the word parsing rules of the UNIX Bourne shell.
Split lines into an array of lines
Turn a readable stream into multiple readable streamx streams
Cross browser String#split implementation
Angular UI library to split views and allow dragging to resize areas using CSS grid layout.
Built on top of Gosu, an engine for making 2-D games. Gosu provides the means to handle the graphics, sound, and keyboard/mouse events. It doesn't provide any sort of client/server network architecture for multiplayer games, nor a system for tracking objects in game-space. This gem aims to fill that gap. Originally I tried using Chipmunk as the physics engine, but its outcomes were too unpredictable for the client to anticipate the server. It was also hard to constrain in the ways I wanted. So I elected to build something integer-based. In the short term, I'm throwing anything into this gem that interests me. There are reusable elements (GameSpace, Entity, ServerPort), and game-specific elements (particular Entity subclasses with custom behaviors). Longer term, I could see splitting it into two gems. This gem, game_2d, would retain the reusable platform classes. The other classes would move into a new gem specific to the game I'm developing, as a sort of reference implementation.
Treste is a great tool for rapid prototyping projects. I use it in loads of my projects. There are a couple of things that kind of tick me off though; Trestle resources tend to become large files in the app/admin folder due to the way they are written. I find it hard to read/maintain them as a big file, so I split them up into smaller files and created a generator to ensure that they always follow a standard. Another pet peeve is the menu handling. Handling menu itmes in each resource quickly becomes a nightmare. Ordering them requires a lot of manual work. To keep things simpler, inspired by the work from the crowd at WinterCMS, I created a menu.yml file that is used to manage the menu. I also created a helper that simplifies the placing of the menu.
<p>Sass or the much better approach of scss is really helpful and a big silver bullet for my css structuring in ruby projects.</p> \ <p>Standard sass command works for whole directories or single files only. In general it gets the jobs we want done, but in practical usage i think the sass command tool is a little bit unconvinient. A common scenario for me is, \ that you have whole bunch of sass files, which you want to compile to a single compressed output file. But if you have splitted your sass files in component based modules and you want to watch the complete folder you have to care for dependency handling in each file, because each file will be compiled for its own.</p> \ <pre># compiling a complete folder with scss ~ $ sass css/scss:css/compiled</pre> \ <p>So converting the whole folder is not what i want, because i don\'t want to import for example my color.sass config file in each module again. Compiling a single file seems to be the better solution, and it works in general, as expected, but the devil is in the detail. </p> <pre># compiling a single file where the other files are imported. ~ $ sass css/scss/main.scss:css/compiled/main.css</pre> \ <p>If we change a file with impact to our main.sass file, the --watch handle will not get it, because it observes only the timestamp of the given main.sass.</p> <p>Here is it, where mindful_sass tries to help out. You use it according to the single file variant of sass, but it tries to observe the whole folder the given sass file is placed. If a timestamp of file in the sass folder or its children changes it will compile the specified main.sass again.</p> \ <p>This gem is not aimed to replace anything in the sass universe. It is only a wrapper to avoid the described unconvinience, and i hope that it gets useless as fast as possible, because the sass development gets this feature done for themselves.</p> \ <p>Thanks anyway to the sass developer team.</p>
Send SMS messages using the CellForce API
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.