Projects tagged ‘haxe’ and ‘php’

Templo is the advanced template system for haXe. It consists of one small haXe loader, and one commandline tool temploc which is capable of compiling a .mtt template file either to Neko or PHP. ... [More] temploc is written in NekoML because of its parser facilities. [Less]

A unit testing framework for haXe.

A standard way of doing asynchronous (and synchronous) unit tests in haXe.

HXMPP is a implementation of the XMPP protocol in the haXe programming language for creating jabber clients and components.

Hxnova is recreation of the 4X game "Stars!" using the haXe language. It has more of a client-server approach than the original and it's much more cross-platform with the client done in flash and the backend compiled to either php or neko.

OverviewHaxle is a Signal and Slots Framework for haXe. Signal and slots frameworks are synchronous event handling systems. They work by 'linking' a given object method call (called a signal ... [More] function) to another arbitrary (slot) object method. The second object method receives all the arguments from the first object, whenever and wherever it is called in the code. Some benefits of signal/slots over conventional Event systems are: They need very little added syntax/boilerplate code They can control if slot functions happen before or after a signal function They can control the order in which slot functions are called They can modify arguments being passed between signal and slot functions They can set multiple signal declarations for the respective signal object function, and each signal in turn can be received by multiple slot objects. The main negatives are: The haXe implementation must use strong references. If objects are connected with Haxle, then they must be disconnected before the slot object can be deleted completely. There is no type checking for the linked functions. It is up to the developer to make sure that the types match for the two linked functions. In this implementation, the signal call is a bit clunky. You must specify three parameters (the current object, the current object's function, and any arguments you want to forward on), and call it from the function you want to treat as a signal: Haxle.signal(this, func1, array_of_args)(Where this is the current object, func1 is the current method, array of args is the arguments passed to the method). Unfortunately, due to runtime constraints on the different platforms, these parameters cannot be reliably extracted to use as defaults. They must be explicitly declared for each signal call. Other DetailsThis class tries to impose a minimal burden on implementation, as well as maximum flexibility in signaling methods. It works by adding an additional field (haxle_slots) at run time to any signaling class instance. The slot field is essentially a Hash of Lists (of method calls). This slot field contains a list of further object methods that should be triggered. To signal an event, a single static function call is made: Haxle.signal(this, func1, arr_values) (where this is the current object, func1 is the method, and arr_values are the arguments given to func1). The Haxle class reads in the parameters in the arguments and looks up the method name entry in the haxle_slots field. If it exists, it will call each function it finds with the arguments from arr_values (an array of values). Without a slot object method registered to the signal, nothing will happen. One must be specified explicitly using a static call. For example, say it's necessary to connect a signal function (func1) on an object (obj1) to another signal function (func2) on another object (obj2). First, you would insert a signal call from within func1 (as detailed above). Then you would connect these two functions together with: Haxle.connect(obj1, 'func1', obj2, 'func2') Somewhere in your main loop. Now, any functions called on obj1.func1() get passed on to obj2.func2() If you want to disconnect them, then you can call: Haxle.disconnect(obj1, 'func1', obj2, 'func2') Check the Demo.hx file in the source tree for a very simple example. Platform Specific IssuesSome platforms (Flash9+) do not automatically enable dynamic classes, and will throw errors at runtime if Haxle tries to access/create its haxle_slot field. To get around this, you can "implement dynamic" for your signaling class, which should enable class fields to be rewritten. Alternatively, you could also "implement HaxleStatic", and add the required slot field to your class definition explicitly. [Less]

The poko framework is a request based system. It is designed to allow the user to create pages / a site in an unrestricted way. It features integrated templating, database connectivity, haxe js ... [More] linking and some useful tools such as form building (with validation) and image processing. The poko CMS is a flexible data/page management tool which allows you to manage most relational databases setups. It allows you to enter metadata about your database which is used to display a fast and powerful CMS for your users. It features advanced features such as many-to-many and linked database tables. It can be used to make anything from a simple list of groceries to a complete product or gallery system. Both currently support PHP as a target but should soon support Neko as well. [Less]

The idea is to create a simple "quick-to-go" MVC web-framework for the HaXe language, which is then compiled into PHP-files (and later perhaps Neko too). It is inspired by Rails in the ... [More] MVC-file-structure, by ActiveRecord in the database-structure, and by "Convention over Configuration". So, what's the point in this ? 1) Ruby on Rails is cool, but there are few hosting-alternatives, and those that exist are probably very expensive. Unless you're able to host the web-app yourself of course. 2) PHP-hosting is cheap... Apache with mod_php is default with many low budget web-hotels. (And even though you can host your rails app on a Tomcat-server with JRuby, PHP-hosting is still cheaper, and much more lightweight). 3) haXe is an incredibly cool object-oriented, functional, type-inferred, statically and dynamically typed language, that can also compile to bytecode for the Adobe Flash VM, as well as to Javascript and to Neko bytecode for the very fast Neko VM (desktop or mod_neko for Apache). Meaning: The algorithms you write in haXe can be directly reused both in your server-side PHP or Neko and in your client-side Javascript or Flash-apps... and in your desktop Neko-apps... [Less]

A repository of wrappers which allow haXe to access php's native libraries.

The goal of this project is to offer a way to build excel files from all haXe platforms.