JavaScript SDK for Agora RTM
Socket.io extension for invoking and emitting with callback
JavaScript SDK for Agora RTM
React Native around the Agora RTM SDKs for Android and iOS agora
A wrapper for Agora RTM Web SDK to use with react/reactjs
Apxor RTM Plugin
RTM CLI
`rtm-provider` 通过 `agora-rtm` 为 `@netless/forge-room` 提供实时消息服务。
React Native wrapper for Apxor RTM plugin
JavaScript SDK for anyRTC RTM
TypeScript toolchain for RTM/Minecraft 1.7.10 scripting
dingRTC RTM web端 sdk
JavaScript SDK for Agora RTM
Apxor RTM UI Plugin
Official library for using the Slack Platform's Real Time Messaging API
Client for rtm-api
RTM CLI
RTM Publisher for React Native
bootstrap a RTM CMS project
TypeScript definitions for sarif-external-property-file-2.1.0-rtm.0.
RTM client for BearyChat
JavaScript SDK for Agora RTM
JavaScript SDK for Satori RTM
a node.js API using Slack their RTM API
Intel's Transactional Synchronization
Rust Type Mapper (RTM) crate rtm-csv.
Provides intrinsics for Rust to use Intel's TSX RTM, a hardware transactional memory extension for some Skylake CPUs.
Rust Type Mapper (RTM) crate rtm-attributes.
Rust Type Mapper (RTM) crate rtm-cli.
Rust Type Mapper (RTM) crate rtm-examples.
Rust Type Mapper (RTM) crate rtm-macros.
Rust Type Mapper (RTM) crate rtm-schema.
Rust Type Mapper (RTM) crate rtm-sql.
Rust Type Mapper (RTM) crate rtm-tests.
Rust Type Mapper (RTM) crate rtm-json.
Rust Type Mapper (RTM) crate rtm-yaml.
==== Ruby Topic Maps (RTM) RTM is a Topic Maps engine written in Ruby. See http://rtm.topicmapslab.de/ for instructions. Several backends and extensions are available as separate gems. ==== Overview From a developer's perspective, RTM is a schema-less database management system. The Topic Maps standard (described below) on which RTM is based provides a way of creating a self-describing schema just by using it. ==== Quickstart require 'rtm' connection = RTM.connect # uses the default Ontopia in-memory backend topic_map = connection.create "http://example.org/my_topic_map/" some_topic = topicmap.get!("identifier_of_the_topic") some_topic["-"] = "default name for the topic" topic_map.to_xtm("my_xtm_file.xtm") ==== Topic Maps Topic Maps is an international industry standard (ISO13250) for interchangeably representing information about the structure of information resources used to define topics, and the relationships between topics. A set of one or more interrelated documents that employs the notation defined by this International Standard is called a topic map. A topic map defines a multidimensional topic space - a space in which the locations are topics, and in which the distances between topics are measurable in terms of the number of intervening topics which must be visited in order to get from one topic to another, and the kinds of relationships that define the path from one topic to another, if any, through the intervening topics, if any. In addition, information objects can have properties, as well as values for those properties, assigned to them. The Topic Maps Data Model which is used in this implementation can be found on http://www.isotopicmaps.org/sam/sam-model/. ==== Backends * rtm-ontopia: JRuby only, recommended, uses Ontopia: http://code.google.com/p/ontopia/ * rtm-tinytim: JRuby only, uses TinyTiM: http://tinytim.sourceforge.net/ * rtm-activerecord: uses a custom ActiveRecord schema ==== Extensions * rtm-tmql: Adds support for the Topic Maps Query Language (TMQL), http://isotopicmaps.org/tmql/ * rtm-tmcl: Adds support for the Topic Maps Constraint Language (TMCL), http://isotopicmaps.org/tmcl/ ==== License Copyright 2009 Topic Maps Lab, University of Leipzig. Apache License, Version 2.0
Ruby Topic Maps is a Topic Maps engine written in Ruby. This backend engine uses any Java TMAPI 2.0 compatible backend. See http://www.tmapi.org/2.0/. You can provide your own TMAPI 2.0 compatible implementation or use one of the existing ones: * rtm-ontopia * rtm-tinytim * rtm-sesametm
The Ontopia backend for Ruby Topic Maps. See http://code.google.com/p/ontopia/ for more information about Ontopia.
The TinyTiM backend for Ruby Topic Maps. See http://tinytim.sourceforge.net/ for more information about TinyTiM.
Ruby Topic Maps is a Topic Maps engine written in Ruby. This is the backend engine which holds all data in ActiveRecord objects. It's available on all ruby platforms but currently does not pass all specs.
The TMQL query engine for Ruby Topic Maps. See http://tmql4j.topicmapslab.de/ for more information about TMQL and TMQL4J.
parse and inspect RTM's estimate time
The SesameTM backend for Ruby Topic Maps. See http://code.google.com/p/sesametm for more information about SesameTM.
The TMCL Validator for Ruby Topic Maps.
==== Topic Maps for Rails (rtm-rails) RTM-Rails is the Rails-Adapter for Ruby Topic Maps. It allows simple configuration of topicmaps in config/topicmaps.yml. ==== Overview From a developer's perspective, RTM is a schema-less database management system. The Topic Maps standard (described below) on which RTM is based provides a way of creating a self-describing schema just by using it. You can use RTM as a complement data storage to ActiveRecord in your Rails apps. ==== Quickstart - existing Rails project jruby script/generate topicmaps Run the command above after installing rtm-rails. This will create * a minimal default configuration: config/topicmaps.yml and * a file with more examples and explanations config/topicmaps.example.yml * a file README.topicmaps.txt which contains more information how to use it and where to find more information * an initializer to load the topicmaps at startup * a rake task to migrate the topic maps backends in your rails application. ==== Quickstart - new Rails project For a new Rails application these are the complete initial steps: jruby -S rails my_topicmaps_app cd my_topicmaps_app jruby -S script/generate jdbc jruby -S script/generate topicmaps # The following lines are necessary because Rails does not have a template # for the H2 database and Ontopia does not support the Rails default SQLite3. sed -e "s/sqlite3/h2/" config/database.yml > config/database.yml.h2 mv config/database.yml.h2 config/database.yml # Prepare the database and then check if all is OK jruby -S rake topicmaps:migrate_backends jruby -S rake topicmaps:check ==== Usage inside the application When everything is fine, let's create our first topic: jruby -S script/console TM[:example].get!("http://example.org/my/first/topic") # and save the topic map TM[:example].commit Access the configured topic maps anywhere in your application like this: TM[:example] To retrieve all topics, you can do TM[:example].topics To retrieve a specific topic by its subject identifier: TM[:example].get("http://example.org/my/topic") Commit the changes to the database permanently: TM[:example].commit ... or abort the transaction: TM[:example].abort More information can be found on http://rtm.topicmapslab.de/ ==== Minimal configuration default: topicmaps: example: http://rtm.topicmapslab.de/example1/ The minimal configuration creates a single topic map, named :example with the locator given. This topic map will be persisted in the same database as your ActiveRecord connection if not specified otherwise. The default backend is OntopiaRDBMS (from the rtm-ontopia gem). A more complete configuration can be found in config/topicmaps.example.yml after running "jruby script/generate topicmaps". It also includes how to specifiy multiple connections to different data stores and so on. ==== Topic Maps Topic Maps is an international industry standard (ISO13250) for interchangeably representing information about the structure of information resources used to define topics, and the relationships between topics. A set of one or more interrelated documents that employs the notation defined by this International Standard is called a topic map. A topic map defines a multidimensional topic space - a space in which the locations are topics, and in which the distances between topics are measurable in terms of the number of intervening topics which must be visited in order to get from one topic to another, and the kinds of relationships that define the path from one topic to another, if any, through the intervening topics, if any. In addition, information objects can have properties, as well as values for those properties, assigned to them. The Topic Maps Data Model which is used in this implementation can be found on http://www.isotopicmaps.org/sam/sam-model/. ==== License Copyright 2009 Topic Maps Lab, University of Leipzig. Apache License, Version 2.0
Fork from Rufus RTM gem
Shell for rememberthemilk.com.
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.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.