The first test module publish
The Repodog cli publish module.
zxz first test publish module
AMQP Subscribe/Publish Module with Persistence
'test npm publish module'
publish module tester
publish module
test publish module to npm
Subscribe/Publish module with amqp
Node.js native addon binary install tool
just a demo for publish module
test publish module
Adexe Created Npm Publish store to check for the client purpose Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
Adexe Created Npm Publish store to check for the client purpose Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris
Unicode property alias mappings in JavaScript format for property names that are supported in ECMAScript RegExp property escapes.
Visual Studio Code extension package signing and verification module
A wrapper for the jackrabbit publish module
a publish module
learn npm publish module
Cross platform updater for electron applications
The Wasm package for prisma-fmt
mirror of postcss-calc-ast-parser, bundled and exposed as ES module
publish module
to publish module
Page editing/publishing module for aerogel CMS
A simple mix-inable module to provide Publisher/Consumer style event handling
A botbase module for matching a speech keyword which then triggers a general RSC job or publishes an SPS message etc.
A module which enables objects to publish multiple events, which other objects can subscribe to See http://github.com/davybrion/EventPublisher for more information.
publisher is a module for extending a class with event subscription and firing capabilities. This is helpful for implementing objects that participate in the Observer design pattern.
A ruby client for publishing messages to your http pub/sub service provided by the nginx-push-stream-module
iOS application modulize into pods, improvement for develop modules. CMD: 1.git-flow 2.auto publish code 3.auto push repo 4.auto rewrite podfile 5.sync other branch commit 6.binary static libary
This gem exists solely to reserve the `SSR` module namespace on RubyGems.org, preventing others from publishing a potentially misleading or malicious gem under this name.
* http://rubysideshow.rubyforge.org/irb_callbacks == DESCRIPTION: This gem adds callbacks to irb, intended for you to override at your discretion. == FEATURES: irb's control flow looks like this: loop: * prompt * eval * output This gem adds three callbacks to each phase. module IRB: * self.before_prompt * self.around_prompt (call yield) * self.after_prompt * self.before_eval * self.around_eval (call yield) * self.after_eval * self.before_output * self.around_output (call yield) * self.after_output == SYNOPSIS: # Here's my ~/.irbrc file (which is run at irb startup) require 'rubygems' require 'irb_callbacks' require 'benchmark' # This little snippet will time each command run via the console. module IRB def self.around_eval(&block) @timing = Benchmark.realtime do block.call end end def self.after_output puts "=> #{'%.3f' % @timing} seconds" end end # And a sample irb session: $ irb irb(main):001:0> 1_000_000.times { |x| x + 1 } => 1000000 => 0.330 seconds == CAVEATS: The three around_* callbacks all require you to call the block that's passed in. If you don't do it, undefined behavior may occur. == INSTALL: * sudo gem install irb_callbacks == LICENSE: (The MIT License) Copyright (c) 2008 Mike Judge 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.
ROS Ruby Client: rosruby ======= [ROS](http://ros.org) is Robot Operating System developed by [Willow Garage](http://www.willowgarage.com/) and open source communities. This project supports ruby ROS client. You can program robots by ruby, very easily. **Homepage**: http://otl.github.com/rosruby **Git**: http://github.com/OTL/rosruby **Author**: Takashi Ogura **Copyright**: 2012 **License**: new BSD License **Latest Version**: 0.2.0 Requirements ---------- - ruby (1.8.x/1.9.x) - ROS (electric/fuerte) - ROS requires python2.7 or more libraries Let's start --------------- Install ROS and ruby first. ROS document is [http://ros.org/wiki/ROS/Installation](http://ros.org/wiki/ROS/Installation) . You can install ruby by apt. ```bash $ sudo apt-get install ruby ``` Download rosruby into your ROS_PACKAGE_PATH. ````bash $ git clone git://github.com/OTL/rosruby.git ``` please add RUBYLIB environment variable, like below (if you are using bash). ```bash $ echo "export RUBYLIB=`rospack find rosruby`/lib" >> ~/.bashrc $ source ~/.bashrc ``` To use with precompiled electric release ----------------------- If you are using precompiled ROS distro, use the msg/srv generation script (rosruby_genmsg.py) If you are using ROS from source, it requires just recompile the msg/srv packages by rosmake rosruby. ```bash $ rosrun rosruby rosruby_genmsg.py ``` This converts msg/srv to .rb which is needed by sample programs. If you want to make other packages, add package names for args. For example, ```bash $ rosrun rosruby rosruby_genmsg.py geometry_msgs nav_msgs ``` Sample Source -------------- ## Subscriber ```ruby #!/usr/bin/env ruby require 'ros' require 'std_msgs/String' node = ROS::Node.new('/rosruby/sample_subscriber') node.subscribe('/chatter', Std_msgs::String) do |msg| puts "message come! = \'#{msg.data}\'" end while node.ok? node.spin_once sleep(1) end ``` ## Publisher ```ruby #!/usr/bin/env ruby require 'ros' require 'std_msgs/String' node = ROS::Node.new('/rosruby/sample_publisher') publisher = node.advertise('/chatter', Std_msgs::String) msg = Std_msgs::String.new i = 0 while node.ok? msg.data = "Hello, rosruby!: #{i}" publisher.publish(msg) sleep(1.0) i += 1 end ``` Note ---------------- Ruby requires 'Start with Capital letter' for class or module names. So please use **S**td_msgs::String class instead of **s**td_msgs::String. Try Publish and Subscribe ---------------------- You needs three terminal as it is often for ROS users. Then you run roscore if is not running. ```bash $ roscore ``` run publisher sample ```bash $ rosrun rosruby sample_publisher.rb ``` run subscription sample ```bash $ rosrun rosruby sample_subscriber.rb ``` you can check publication by using rostopic. ```bash $ rostopic list $ rostopic echo /chatter ``` Try Service? ---------------------- ```bash $ rosrun rosruby add_two_ints_server.rb ``` run client with args ('a' and 'b' for roscpp_tutorials/TwoInts) ```bash $ rosrun rosruby add_two_ints_client.rb 10 20 ``` and more... ---------------------- You need more tools for testing, generating documentations. ```bash $ sudo apt-get install rake gem $ sudo gem install yard redcarpet simplecov ``` do all tests ------------------------- run roscore if is not running. ```bash $ roscore ``` and run the unit tests. ```bash $ roscd rosruby $ rake test ``` documents -------------------------- you can generate API documents using yard. Document generation needs yard and redcarpet. You can install these by gem command like this. ```bash $ gem install yard redcarpet ``` Then try to generate documentds. ```bash $ rake yard ``` You can access to the generated documents from [here](http://otl.github.com/rosruby/doc/).
==== subj3ct - The DNS for the Semantic Web This is a Ruby adapter for the subj3ct.com webservice. Subj3ct is an infrastructure technology for Web 3.0 applications. These are applications that are organised around subjects and semantics rather than documents and links. Subj3ct provides the technology and services to enable Web 3.0 applications to define and exchange subject definitions. Or in other words: Subj3ct.com is for the Semantic Web what DNS is for the internet. ==== Installing Install the gem: gem install subj3ct ==== Usage Query a specific subject - to be specific: its subject identity record - using it's identifier: Subj3ct.identifier("http://www.topicmapslab.de/publications/TMRA_2009_subj3ct_a_subject_identity_resolution_service") See the README or the github page for more examples. ==== Subj3ct vs. Subject The official name is "Subj3ct", however in this API, you can also use "Subject" which may be easier to remember or to type for normal, n0n-1337 people. It should work for the gem, for the require and for the main module. ==== Contribute! Subj3ct is a young and ambitious service. It's free, will stay free and needs your help. Contribute to this library! Create bindings for other languages! Publish your data as linked data to the web and register it with subj3ct.com. ==== Note on Patches/Pull Requests * Fork the project on http://github.bb/subj3ct * Make your feature addition or bug fix. * Add tests for it. This is important so I don't break it in a future version unintentionally. * Commit, do not mess with rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull) * Send me a pull request. Bonus points for topic branches. ==== Copyright Copyright (c) 2010 Benjamin Bock, Topic Maps Lab. See LICENSE for details.
Narwhal ======= A general purpose JavaScript platform ------------------------------------- Narwhal is a cross-platform, multi-interpreter, general purpose JavaScript platform. It aims to provide a solid foundation for building JavaScript applications, primarily outside the web browser. Narwhal includes a package manager, module system, and standard library for multiple JavaScript interpreters. Currently Narwhal's [Rhino](http://www.mozilla.org/rhino/) support is the most complete, but [other engines](engines.html) are available too. Narwhal's standard library conforms to the [CommonJS standard](http://wiki.commonjs.org). It is designed to work with multiple JavaScript interpreters, and to be easy to add support for new interpreters. Wherever possible, it is implemented in pure JavaScript to maximize reuse of code among engines. Combined with [Jack](http://jackjs.org/), a [Rack](http://rack.rubyforge.org/)-like [JSGI](http://jackjs.org/jsgi-spec.html) compatible library, Narwhal provides a platform for creating server-side JavaScript web applications and frameworks such as [Nitro](http://www.nitrojs.org/). ### Homepage: * [http://narwhaljs.org/](http://narwhaljs.org/) ### Source & Download: * [http://github.com/tlrobinson/narwhal/](http://github.com/tlrobinson/narwhal/) ### Mailing list: * [http://groups.google.com/group/narwhaljs](http://groups.google.com/group/narwhaljs) ### IRC: * [\#narwhal on irc.freenode.net](http://webchat.freenode.net/?channels=narwhal) Documentation ------------- * [Quick Start](quick-start.html) * [Packages](packages.html) * [How to Install Packages](packages.html) * [How to Build Packages](packages-howto.html) * [Modules](modules.html) * [Virtual Environments / Seas](sea.html) * [How to Build Engines](engines.html) * [How Narwhal Works](narwhal.html) Contributors ------------ * [Tom Robinson](http://tlrobinson.net/) * [Kris Kowal](http://askawizard.blogspot.com/) * [George Moschovitis](http://blog.gmosx.com/) * [Kevin Dangoor](http://www.blueskyonmars.com/) * Hannes Wallnöfer * Sébastien Pierre * Irakli Gozalishvili * [Christoph Dorn](http://www.christophdorn.com/) * Zach Carter * Nathan L. Smith * Jan Varwig * Mark Porter * [Isaac Z. Schlueter](http://blog.izs.me/) * [Kris Zyp](http://www.sitepen.com/blog/author/kzyp/) * [Nathan Stott](http://nathan.whiteboard-it.com/) * [Toby Ho](http://tobyho.com) License ------- Copyright (c) 2009, 280 North Inc. <[280north.com](http://280north.com/)\> 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 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.
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.