HaxeUI Version 2 Preview

Hi All,

Just thought I would share current progress of HaxeUI version 2… There are some previews availble here: http://www.haxeui.org/v2

Cheers!
Ian

6 Likes

Forgot to add, heres the facebook page and twitter account (i tend to post more updates there rather than spam here!) :slight_smile:

Facebook: https://www.facebook.com/haxeui
Twitter: https://twitter.com/IanHarrigan1982

Cheers,
Ian

1 Like

Hi, how do we use haxeui to code in haxe language?

The links above are for version 2, which is currently in development, there is however, a version 1, here are some links here that might help:

http://haxeui.org/getting_started.jsp
http://haxeui.org/wiki/en/Home
http://haxeui.org/try.jsp

Its worth mentioning that version 2 is alot simpler (no “Roots” for example - just add directly to stage, new style and layout engine, simpler class hierarchy, etc, etc). In order to “future proof” yourself if you are using version 1 i would advise using xml layouts and build controllers as much as possible):

http://haxeui.org/wiki/en/XML_Based_UIs
http://haxeui.org/wiki/en/Using_Controllers

Cheers,
Ian

Cool work, Ian! :smiley:
Will you adept the visual builder plugin for FlashDevelop?

1 Like

Yup, certainly. Going to move pretty much everything over to version 2 once it has at least the same functionality as version 1. :slight_smile:

1 Like

Hi Ian.

I’m starting a new project in my company and I want to know when it is possible to play with version 2. Do you have any roadmap?

Thanks in advance and good work.

Hi,

Its quite hard to to tell to be honest. There is still a load left to do, the base framework is pretty stable, and the openfl backend works well. The main problem is there is no where near the components that version 1 has, and i dont really want to release it until it has the same funcitonality as version 1 (at least). This means there is still a fair amount of work to do. At the moment there is only:

  • Buttons
  • Labels
  • Checkboxes
  • Optionboxes
  • Text inputs
  • Progressbars
  • Scrollbars
  • Sliders
  • Images
  • HBoxes
  • VBoxes
  • ScrollViews

Seems like a lot, but its missing (that v1 has):

  • Accordions
  • Calendars
  • Continuos Layouts
  • Grid Layout
  • Splitters
  • Lists (and item renderers)
  • Sprite Container
  • Tabs
  • Popups
  • Drop downs
  • Menus
  • Seperators
  • Links

Plus loads of stuff like build macros for controllers etc, etc. Basically all the hard stuff left to do! :slight_smile:

I migh release the openfl before I get all the other backends working perfectly though, but at the same time, i dont want to rush and release it until its basically ready.

My advice for the new project, as i mentioned above, would be to use version 1, but try to use the including build macros and xml layouts as much as possible, that way migration to v2 should be fairly painless.

Hope that helps somewhat!

Cheers,
Ian

1 Like

So HaxeUI will be a gui development program like visual basic and/or Flash Professional, where we see the components we layout? That would be great! :smile:

Is there anyway that HaxeUI will support an advance source code editing that support functionality similar to visual basic source code view and IntelliJ? (Code hinting, code completion and so on…)

Well, HaxeUI is just a framework. You can add GUI elements either by raw code, like:

var vbox = new VBox();
vbox.addChild(new Button());
vbox.addChild(new Button());
vbox.addChild(new Button());

Etc. You can also create UIs using XML, ie:

<vbox>
    <button />
    <button />
    <button />
</vbox>

So its just a framework basically, what you do with it, is of course, totally up to you. There are some build tools i have for version 1, like:

https://github.com/ianharrigan/HaxeUILayoutPreview.
https://github.com/ianharrigan/haxeui-builder

These will be moved over to version 2 also when its gets released. You can build editors to a degree with version 1 (again, all of these projects will be moved over to v2 at some point):



Most of the components in version 1 can be viewed here: http://haxeui.org/showcase.jsp (You might want to change the theme in the top right corner to gradient for best effect).

Cheers,
Ian

Cool. Thanks!

Maybe it can be a good idea a preview release (with the risk of API changes) with the core functionality (when it is ready) without all components implemented. It could be helpful to test it by other people (me included) and you will have feedback. I don’t know if it is in your plans.

Yeah, its something that ive been toying with, but certainly before that happens it still needs a bit of work. What im mainly concerned about is getting code reviews on essentially unfinished source and having to micro manage things like that. It sort of happened with version 1, and as a result there were some design mistakes that made their way in.

Ill certainly keep it in mind though! :slight_smile:

:slight_smile:

Hey, .NET Framework 5 is now open source, and somebody had now been able to include for compile in haxe, maybe we can learn something there? :smile:

Quick update, added quite a few things, but most recent is 9-slice and custom fonts, when mixed together you can get pretty nice results for custom buttons (all via css of course): http://haxeui.org/v2/

xml is just:

<button text="Custom Button" styleNames="custom-button custom-button-spooky"/>

and css to get the button is:

.custom-button {
	background-image: "haxeui-core/styles/default/temp/button_test.png";
	background-image-clip: 0px 0px 32px 82px;
	background-image-slice: 10px 10px 22px 72px;
	border: none;
	background-color: white;
	color: #515F6A !important;
}

.custom-button:hover {
	background-image: "haxeui-core/styles/default/temp/button_test.png";
	background-image-clip: 0px 90px 32px 172px;
	background-image-slice: 10px 10px 22px 72px;
	border: none;
	color: #515F6A !important;
}

.custom-button:down {
	background-image: "haxeui-core/styles/default/temp/button_test.png";
	background-image-clip: 0px 179px 32px 261px;
	background-image-slice: 10px 10px 22px 72px;
	border: none;
	color: #515F6A !important;
}

.custom-button-spooky {
	padding-top: 20px;
	font-name: "fonts/Something Strange.ttf";
	font-size:32;
}

.custom-button-spooky .label {
	padding-top: 5px;
}