Copies an object’s own properties to another object.
Open-source agent connectors. Copy & own.
Tree utilities which provides a full-featured extend and object-cloning facility, and various tools to deal with nested object structures.
An optimised way to copy'ing an object. A small and simple integration
Copy files && directories with webpack
Copy a descriptor from object A to object B
Robustly get an object's own property keys (strings and symbols), including non-enumerables when possible
Copy stuff into clipboard using JS with fallbacks
A blazing fast deep object copier
Copy static properties, prototype properties, and descriptors from one object to another.
Copy-to-clipboard React component
Copy properties deeply between two objects.
Merge objects using their property descriptors
A rewrite-copy optimize-query-operation actor
rollup-plugin-copy for vite with dev server support.
Copy files and folders using Rollup
Copy text to the clipboard in modern browsers (0.2 kB)
Convert a typed array to a Buffer without a copy
This is a pure-js JSON streaming parser for node.js
Lightweight copy to clipboard for the web
Really Fast Deep Clone
make a shallow copy of an object or array
Like `Object.keys()` but also includes symbols
Iterate over the own enumerable properties of an object, and return an object with properties that evaluate to true from the callback. Exit early by returning `false`. JavaScript/Node.js.
Uploads the specified file to the given server. Progress is shown via system notifications (disable with --no-progress). The final notification is clickable and opens the share URL in a web browser. The share URL is automatically copied to the system clipboard (disable with --no-clipboard).
Gemstash acts as a local RubyGems server, caching copies of gems from RubyGems.org automatically, and eventually letting you push your own private gems as well.
Klipp, Xcode templates for the rest of us.
The cute_alert_rails gives you ability to avoid routine copying javascripts or writing by your own, it helps you to add pretty alerts instead of defaults.
This project is based on the need for a system for easily create/delete files and folders in a repository. For sharing these repositories easily with other object with a flexible and complete permissions management. Each instance (users, groups, etc..) can have it own repositories (with files and folders). It can manage them easily (create, delete, edit, move, copy, etc) and sharing them with other instance.
The sandbox plugin for rubygems helps you manage your command-line tools and their dependencies. Sandboxed gems are installed in their own private rubygem repositories with all of their dependencies. This means that you don't have to have a rat's nest of gems in your global repository in order to run popular command-tools like rdoc, flog, flay, rcov, etc. gem sandbox has the following sub-commands: * install gem_name ... - install 1 or more gems * plugin gem_name plugin_name ... - install a gem and plugins for it * remove gem_name ... - uninstall 1 or more gems * help - show this output Once you install gem sandbox will output something like: Copy the following scripts to any directory in your path to use them: cp /Users/USER/.gem/sandboxes/GEM/bin/TOOL _in_your_$PATH_ Copy the scripts to a directory in your path (eg ~/bin or /usr/bin) and you're good to go.
This is a simple hello world gem copied from https://guides.rubygems.org/make-your-own-gem/. Since I've been using echoe a number of times, this time I want to be able to create a Gem without echoe so i can fix sakuric ASAP which is breaking many environemnts. This gem tries to be able to give DEB and COLORS as 'ric' without all 'ric' dependencies. Like a vanilla RIC version I can include in my stuff. Possibly depending on lolcat :).
= crucigrama Crucigrama is a library for the generation of crosswords. The gem includes as well a simple command line tool that, making use of the library, can generate and print crosswords. == Contributing to crucigrama * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it * Fork the project * Start a feature/bugfix branch * Commit and push until you are happy with your contribution * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. * Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it. == Copyright Copyright (c) 2011-2012 Pablo Baños López Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the âSoftwareâ), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED âAS ISâ, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
A Jekyll liquid tag plugin which allows includes directly from plugins' `_include` directories, with optional ability to override with files present in site includes_dir (if they exist). Normally, Jekyll's `include` tag can only search for files in the site's single configured includes directory (and that of the *theme* plugin, if it using one). That means that if a plugin wants to provide you with a template/fragment via includes, the best it can do is ask you to copy it into your own repo manually. This plugin then makes it easy to use includes that ship *with* a plugin directly *from* a plugin. And if a modified version of the file is provided in the site's own includes directory, it can intelligently use that one instead! And for plugin developers, this provides a way to ship and use includes without leaning on the user to manage the unmodified files themselves.
chef-gen-flavors is a framework for creating custom templates for the 'chef generate' command provided by ChefDK. This gem simply provides a framework; templates are provided by separate gems, which you can host privately for use within your organization or publicly for the Chef community to use. [chef-gen-flavor-base](https://github.com/jf647/chef-gen-flavor-base) is a base class that makes it easy to compose a flavor from reusable snippets of functionality, and using it is highly recommended. Using chef-gen-flavors on its own is only suitable if you already have a template which is a copy of the skeleton provided by ChefDK. At present this is focused primarily on providing templates for generation of cookbooks, as this is where most organization-specific customization takes place. Support for the other artifacts that ChefDK can generate may work, but is not the focus of early releases.
# Single File Delivery Method for Mail gem ## Summary This gem is a delivery-method plug-in for [mail](https://github.com/mikel/mail) that delivers all mail to a single file for testing. The Mail gem already provides a file delivery-method that appends a copy of each message to a file named after each message recipient, but I want them to all go to a single file so that I can monitor them from another window with `tail -f my-file`, or `cat my-named-pipe` while I hand-test the web interface from a browser. Of course this is _in addition to_ running automated tests with Rspec and Cucumber. At some point in development, I want to actually see the pages and enter my own inputs and perhaps display the mail messages in an HTML reader. ## Synopsis Mail.defaults do delivery_method SingleFileDelivery => '/tmp/my-file.txt' end
YPetri is a DSL (domain-specific language) for modelling of dynamical systems. It is biologically inspired, but concerns of biology and chemistry have been purposely separated away from it. YPetri caters solely to the two main concerns of modelling, model specification and simulation, and it excels in the first one. Dynamical systems are described under a Petri net paradigm. YPetri implements a universal Petri net abstraction that integrates discrete/continous, timed/timeless and stoichiometric/nonstoichiometric dichotomies of the extended Petri nets, and allows efficient specification of any kind of dynamical system. Like Petri nets themselves, YPetri was inspired by problems from the domain of chemistry (biochemical pathway modelling), but is not specific to it. Other gems, YChem and YCell are planned to cater to the concerns specific to chemistry and cell biochemistry. A lower-level extension of YPetri is currently under development under the name YNelson. Its usage is practically identical to YPetri, so any YPetri user can now consider using YNelson instead. YNelson covers additional concerns: it allows relations among nodes and parameters to be specified under a zz structure paradigm (developed by Ted Nelson) and it is also aimed towards providing a higher level of abstraction in Petri net specification by providing commands that create more than one Petri net node per command. YPetri documentation is avalable online, but due to formatting issues, you may prefer to generate the documentation on your own by running rdoc in the gem directory. As for the user manuals, there are currently 3 documents applicable for both YPetri and YNelson, whose master copies are stored in the YNelson source directory: 1. Introduction to YNelson and YPetri (hands-on tutorial), 2. Object model of YNelson and YPetri, 3. Introduction to Ruby for YNelson users. These manuals are written to allow beginners, including those unfamiliar with Ruby, to start working with YPetri and/or YNelson. For an example of how YPetri can be used to model complex dynamical systems, see the eukaryotic cell cycle model which I released as "cell_cycle" gem.
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.