An adapter-based ORM for ThinkJS 3.x
Abstract adapter for ThinkJS 3.x
Mysql adapter for ThinkJS 3.x
SQLite adapter for ThinkJS 3.x
Mysql adapter for ThinkJS 3.x
PostgreSQL adapter for ThinkJS 3.x
Inline directive parsing for Eliza agents (@think, @model, @verbose, etc.)
Oracle adapter for ThinkJS 3.x
think-model-pro
Real-time web search, reasoning, and research through Perplexity's API
No description provided.
Local-first memory for your AI brain — a nervous system that turns engrams into curated, persistent memories in a folder you control. Bundles `think serve` for piping external events (GitHub, Linear, …) into memory.
for adding, subtracting, and indexing discontinuous ranges of numbers
An HTTP proxy written with Node.js (think Squid)
Remap sequential sourcemaps through transformations to point at the original source code
Opinionated chat agent with agentic loop, stream resumption, client tools, and extensions
Rails UJS for the react-rails gem
Oboe.js reads json, giving you the objects as they are found without waiting for the stream to finish
A Node.js fetch shim using built-in Request, Response, and Headers (but without native fetch)
A tiny neural network for natural language detection.
ProseMirror's document model
Make Claude Code, Codex, and Gemini work properly in your Replit shell.
Remap sequential sourcemaps through transformations to point at the original source code
Tests whether one path is inside another path
Tuile is a small TUI framework built on top of the TTY toolkit. It models the terminal as a tree of components (windows, lists, text fields, popups) with an invalidation-based repaint model and a single-threaded event queue, so apps don't have to think about locking. The name is French for "roof tile" — a small piece that composes into a larger whole.
Create APIs in a fast and dynamic way, without the need to develop everything from scratch. You just need to create your models and let APIcasso do the rest for you. It is the perfect candidate to make your project development go faster or for legacy Rails projects that do not have an API. If you think it through, JSON API development can get boring and time consuming. Every time you use almost the same route structure, pointing to the same controller actions, with the same ordering, filtering and pagination features. APIcasso is intended to be used to speed-up development, acting as a full-fledged CRUD JSON API into all your models. It is a route-based abstraction that lets you create, read, list, update or delete any ActiveRecord object in your application. This makes it possible to make CRUD-only applications just by creating functional Rails' models. Access to your application's resources is managed by a .scope JSON object per API key. It uses that permission scope to restrict and extend access.
Sem4r is a library to access google adwords api. It will works with ruby 1.9 and ruby 1.8 without soap4r. It uses a high level model instead of a low level api. You think about clients, campaigns, keywords and not about operations, operands, selectors, service calls. This is a ALPHA version.rb don't use in production. If you are interested in this project let me now: install it and update periodically, so the gemcutter download counter go up. Or subscribe to my feed at sem4r.com. Or watch the project on github. Or simply drop me a line in email. However I will know there is someone out of here.
Zz structures are an interesting way of representing relations invented by Ted Nelson, whose domain model I provide in a gem Yzz. In this gem, YNelson, I combine Yzz with the universal Petri net provided by YPetri (another gem I wrote) to obtain a hybrid data structure that formalizes and generelizes a spreadsheet. Because let us note spreadsheets (as I have seen them) can be considered Petri nets of a kind, with cell functions acting as Petri net transitions. At the same time, spreadsheets are globally orthogonal structures with 3 typical dimensions (rows, columns and sheets). By using zz structures, the globally orthogonal spreadsheet is generalized as a locally orthogonal zz structure, with relations represented as zz dimensions, thus generalizing and formalizing a spreadsheet. The catch is that I have not yet finished the thinking process regarding what everything should be a zz object: Places (cells) and transitions definitely yes, but how about nets and dimensions? Should YNelson go as far as making namespaces into zz objects? The reason why these questions are hard to answer is because Ted Nelson himself, while providing interfaces guidelines (zz structure views, cursors...) did not comment on these questions. While being a (textual) DSL, YNelson aims to provide convenience on par with actual spreadsheet apps. Unlike YPetri, YNelson also aims to be able to specify more than one Petri net node per command, but this is still under development. See the user guide and the documentation for the details. YNelson documentation is available online, but due to formatting issues, you may prefer to generate the documentation on your own by running rdoc in the gem directory. 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.
I believe that some of developers faced a situation when you can't convince your customer | project manager | team lead | teammates to use any of existing business logic handler, as they think it: - has no value for business - is hard to integrate - needs to be learned be developers - is no guarantee that this gem will be well maintained in the future - is developed by no name author But you still want to make your controllers and models as thin as possible. If such situation is familiar for you then this gem is for you. This is a one file gem, just copy `Service` class from `lib/simple_logic_step.rb` to your project and specs for it from `spec/simple_logic_step/logic_step_spec.rb`.
Contentful API wrapper library exposing an ActiveRecord-like interface
# BELGIAN 2050 CALCULATOR TOOL A C version and ruby wrapper for the Belgian 2050 calcualtor ## GOTCHAS Some versions have a special formula in 2050!B2 that the translator doesn't recognise. Just write 2050 in that cell and recompile. Some tests fail for columns AN and AM on OUTPUT. I think this is due to rounding differences between excel and C. ## DEPENDENCIES 1. ruby 1.9.2 (including development headers) 2. basic c development headers This has ONLY been tested on OSX and on Ubuntu 64 bit EC2 ami. Grateful for reports from other platforms. In the util folder there is an example script that creates a new EC2 EMI, installs all the dependencies and then compiles the gem. It may be useful if you are trying to figure out the complete set of dependencies. ## INSTALLATION Note that this compiles the underlying c code, which might take 10-20 minutes or so gem install belgium_2050_model ## UPDATING TO NEWER VERSIONS OF EXCEL MODEL First of all, you need to be working on the github version of the code, not the rubygem: git clone http://github.com/decc/belgium_2050_model Then put the new spreadsheet in spreadsheet/2050Model.xlsx Then, from the top directory of the gem: bundle bundle exec rake The next step is to check whether lib/belgium_2050_model/belgium_2050_model_result.rb and lib/belgium_2050_model/model_structure.rb need to be altered so that they pick up the correct places in the underlying excel. The final stage is to build and install the new gem: gem build belgium_2050_model.gemspec gem install belgium_2050_model-<version>.gem ... where <version> is the version number of the gem file that was created in the folder. Now follow the instructions in the twenty-fifty server directory in order to ensure that it is using this new version of the 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.