A modern take on building reusable components and maintainable applications
An Ext style Famous framework
Infinite Scroll implementation for famous framework
Simple, yet effective, vanilla JavaScript form validation plugin. Validatinator is based off of one of PHP's most famous framework, Laravel. Using Validatinator is as easy as instantiating a Validatinator object, calling the passes or fails methods and i
Important: this is an internal API. Expect breaking changes.
Modern and scalable routing for React applications
FaaS (Function as a service) framework for writing portable Node.js functions
The log/tasks/spinners portion of Ionic CLI Framework
[](https://serverless.com)
base library for oclif CLIs
Simple, yet effective, vanilla JavaScript form validation plugin. Validatinator is based off of one of PHP's most famous framework, Laravel. Using Validatinator is as easy as instantiating a Validatinator object, calling the passes or fails methods and i
Modern and scalable routing for React applications
Modern and scalable routing for React applications
Next generation testing framework powered by Vite
Modern and scalable routing for React applications
Modern and scalable routing for React applications
Simple JavaScript testing framework for browsers and node.js
Modern and scalable routing for React applications
The Serverless Dashboard plugin
camelCase, kebab-case, PascalCase... a simple integration with nano package size. (SMALL footprint!)
Helps to create your own Protocol Buffers code generators.
Elastic UI Component Library
Modern and scalable routing for Web applications
LangGraph
Reactive is a desktop application framework that gives everything needed to create database-backed applications according to the Model-View-Control pattern of separation. Reactive is highly inspired and also uses code of Rails, the famous Web-Framework for ruby. In Reactive, the model is handled by what's called an object-relational mapping layer. Reactive doesn't impose any ORM, you may choose the one you like but Reactive defaults to Active Record. This means it has baked in support for it, without forcing you to use it. The view part is independant of Reactive, this means that the application has to choose a view provider and feed it into Reactive. This leads to complete freedom for the GUI part. View providers are packaged as gems, so that it is easy for the developer to choose and install them. Look for reactive_view_* to discover some view providers (at this early alpha stage, only reactive_view_wx is available) The controller is part of Reactive and is loosely coupled to the view. Simple convention set up the link.
= The Owasp ESAPI Ruby project == Introduction The Owasp ESAPI Ruby is a port for outstanding release quality Owasp ESAPI project to the Ruby programming language. Ruby is now a famous programming language due to its Rails framework developed by David Heinemeier Hansson (http://twitter.com/dhh) that simplify the creation of a web application using a convention over configuration approach to simplify programmers' life. Despite Rails diffusion, there are a lot of Web framework out there that allow people to write web apps in Ruby (merb, sinatra, vintage) [http://accidentaltechnologist.com/ruby/10-alternative-ruby-web-frameworks/]. Owasp Esapi Ruby wants to bring all Ruby deevelopers a gem full of Secure APIs they can use whatever the framework they choose. == Why supporting only Ruby 1.9.2 and beyond? The OWASP Esapi Ruby gem will require at least version 1.9.2 of Ruby interpreter to make sure to have full advantages of the newer language APIs. In particular version 1.9.2 introduces radical changes in the following areas: === Regular expression engine (to be written) === UTF-8 support Unicode support in 1.9.2 is much better and provides better support for character set encoding/decoding * All strings have an additional chunk of info attached: Encoding * String#size takes encoding into account – returns the encoded character count * You can get the raw datasize * Indexed access is by encoded data – characters, not bytes * You can change encoding by force but it doesn’t convert the data === Dates and Time From "Programming Ruby 1.9" "As of Ruby 1.9.2, the range of dates that can be represented is no longer limited by the under- lying operating system’s time representation (so there’s no year 2038 problem). As a result, the year passed to the methods gm, local, new, mktime, and utc must now include the century—a year of 90 now represents 90 and not 1990." == Roadmap Please see ChangeLog file. == Note on Patches/Pull Requests * Fork the project. * Create documentation with rake yard task * 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) 2011 the OWASP Foundation. See LICENSE for details.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.