View source

From HippoHX

You do not have permission to do that, for the following reason:
This page has been locked to prevent editing.
You can view and copy the source of this page:
==How this works?==

We are just a layer on top of [http://haxe.org/com/libs/swhx ScreenweaverHX]. We are powered and limited at the same time by SWHX.

All our work is based on it so first thing we want to do is shout a '''HUGE THANKS''' to '''Nicolas Cannasse''' and '''Edwin van Rijkom''', authors of SWHX, without them we could do nothing. Also to all [http://haxe.org haXe] contributors, of course.

==So, what will you do?==

We aim to provide:

*A common API for commmon simple tasks such as file manipulation, accessing system information, etc. This is [http://code.google.com/p/hippohx/source/browse/trunk/src/server/com/hippohx/ what we have so far].
** Backend side, a SWHX application class that instantiates several classes that expose the available API.
** Matching API on the client with AS2, AS3 and haXe versions.
*A command-line tool that will get an xml-based config file and will output executables for Win, Mac or both. If SWHX ever supports Linux we will be more than happy to support it too, of course.
*A GUI on top of that tool to make things simpler for non-experienced users.

The code is released under A BSD license and we are hosting it right now in Google Code: [http://hippohx.googlecode.com/ HippoHX]

==Why not keep using "Screenweaver" as project name?==

We would have love to, but it turned out difficult. We've tried contacting Edwin van Rijkom several times because, as far as we know, he is the owner of the project. We haven't heard from him so far, so we decided to go for a new project name.

We hope this doesn't bother anyone, we totally respect and give credit to Edwin's work. Actually, we would LOVE to have him on board or be on board with him, whatever you prefer. We just haven't heard back from him and we cannot wait anymore. We hope he's doing well!

You can read [[Why HippoHX name| why we chose HippoHX as the new name]].

==Why are you using your own Api class for the haXe <-> Flash communication?==

Despite [http://lists.motion-twin.com/pipermail/haxe/2008-March/015399.html my attempts] to make work the backend to multiple frontend communication, I couldn't make it happen, mostly because of scope issues. However, I'm not saying it's not possible, I'm saying *I* couldn't make it work :)

So, we're using a slightly modified version that you can check out [http://hippohx.googlecode.com/svn/trunk/src/client/as3/com/hippohx/Api.as here]. If anyone can send me a working example with the official one, I'm all ears.

==Why are you redistributing Neko and SWHX binaries?==

Well, a couple of reasons:

*We want to make this tool as easy as possible for non-advanced users, a single installation and done. 
*Also we want some stability and control. Although haXe is quite stable, is still in development (see the [http://lists.motion-twin.com/pipermail/haxe/2008-March/015474.html discussion about haXe 2.0] for example) and same applies to SWHX and Neko. We want to test their new versions with our APIs before updating our tool.

Ok, but can't you download specific versions when installing? Ummm... probably, but it seems easier adding them to our repository.

If anyone is against this or we are not honouring haXe, Neko or SWHX license, PLEASE contact us!

Also, if you're and advanced user, you can still update yourself Neko and SWHX binaries in the [http://code.google.com/p/hippohx/source/browse/trunk/src/tools/templates/ template folder]. Use at your own risk!

==Why use HippoHX when I can use SWHX itself?==

To use SWHX you need to at least learn the very basics of haXe and SWHX itself. We think this isn't any big deal (we've done it!) but for some people it really is. Using HippoHX you don't need to learn anything about haXe, just use the ActionScript APIs and the GUI when ready. Same as old Screenweaver used to do.

We hope HippoHX will lower the barrier for Flash developers so they can start using SWHX easily. Hopefully some of them will also engage with the haXe ecosystem bringing benefits both projects.

Even if you are an advanced haXe developer, using HippoHX might help you avoiding you to rewrite your haXe backend for the common tasks that [http://hippohx.googlecode.com/svn/trunk/src/server/com/hippohx/ HippoHX's API] already covers.
Return to FAQ.
Retrieved from "http://wiki.hippohx.com/FAQ"
View source

From HippoHX

Views

Personal tools

Navigation

Search

Toolbox
