Built something? We create video reels & spotlights for GitHub projects.Promote your project →
Home / Developers / tomhat
Developer Profile

tomhat

Discovered public repositories for tomhat in the GitHub catalog.

↗

tomhat/elFinder

Open-source file manager for web, written in JavaScript using jQuery and jQuery UI

↗

tomhat/elRTE

Open-source WYSIWYG HTML-editor written in JavaScript using jQuery UI

↗

tomhat/flight

A lightweight, component-based JavaScript framework

↗

tomhat/WordPress

WordPress, Git-ified. Synced via SVN every 15 minutes, including branches and tags! This repository is just a mirror of the WordPress subversion repository. Please do not send pull requests. Submit patches tohttp://core.trac.wordpress.org/ instead.

↗

tomhat/evercookie

evercookie is a javascript API available that produces extremely persistent cookies in a browser. Its goal is to identify a client even after they've removed standard cookies, Flash cookies (Local Shared Objects or LSOs), and others.

↗

tomhat/Posql

Posql is a tiny text-base database engine (DBMS) written by pure PHP that does not need any additional extension library, it is designed compatible with SQL-92, and only uses all-in-one file as database.

↗

tomhat/ActiveDocument

ActiveDocument is an open source Ruby connector for MarkLogic server, although at a later date it could potentially expanded to work with other XML databases. The goal of ActiveDocument is to make it as easy for developers to work with MarkLogic as ActiveRecord makes it for them to work with an RDBMS. The intent is to make them write as little XQuery as possible. If they can get 80% of their tasks done without having to write any XQuery that should increase adoption. Performance is less of a consideration as developers will have the ability to write their own potentially more performant XQuery later on in the development cycle. Also, the here goal is NOT to make ActiveDocument just an invocation of stored procedures. In fact, I'm imagining that about 80% of the calls from Ruby to MarkLogic will be XQuery that I am dynamically generating. This also is very much what ActiveRecord does where they have a SQL calculus engine that dynamically generate SQL. Again, like ActiveRecord I will give you the ability to call XQuery stored on the server, similar to invoking Stored Procedures. This will be something developers would use to access the 20% or so of functionality that they can't get through the dynamically generated SQL. A final goal is to make this a very flexible system. It should be flexible enough to support another transport mechanism beyond HTTP if such is ever required. It should also support a different XQuery generator which could potentially allow this to support additional XML databases.

FOR MAINTAINERS

Built something? Put it in front of millions of developers.

We make a short reel about your project and post it across YouTube, Instagram, Threads, and X. Send a link, we do the rest.