Cool! Just be aware that GWEN is a Construct Classic plugin, not a Construct 2 plugin. If you need a refund just let me know.

Looks like I ran into some trouble with this. It's the default example cap untampered with other than changing the font from Times to Verdana, although it didn't appear right to begin with.

Am I overlooking something? The widgets appear either clipped in a wrong way or straight out missing and many text elements have very unfitting colors.

That is GWEN when it can't find a skin to use. I figured using the default skin would be better than not showing anything or crashing. The default skin is ugly. Make sure your skin property is pointing at a valid skin, and remember that Construct points to various places when using relative paths. (AppData, and the directory your cap is in)

Colonel: Disabling the resizing of something screws up something along the borders. This is actually a known problem in GWEN itself, rather than the plugin. I noticed it during my testing, but I'm still waiting on Garry to figure out the problem. (He might have already fixed it, I haven't recompiled GWEN in a bit.) Apparently he knows what is causing it though, so a fix should be imminent. Like I said, GWEN is a library intended for use in the Source Engine (Garry's Mod), and my plugin is a wrapper around it that makes it easier to use, while showing it how to render within Construct.

EDIT: Colonel I checked his SVN and it seems that there was a fix for this. I will fold it into the next update. Apologies.

Tonight I'm dropping the price by half.

I've been getting a lot of views, showing me that there is interest, but so far only one purchase over the course of a week, and while the profit would be nice, seeing my plugin proliferate and actually being used would be much nicer for me as a developer. This will, however, be the only price drop.

EDIT: I have updated the price.

Is this the new version of that xml reader?

No this is GWEN.

I tested the demo before release, and tested it once again just now after clearing out all my plugins to default state. Are you sure you installed it correctly?

Do you have more than one instance of Construct installed? If so are you sure you both extracted to Construct RC2's directory, and that you are opening the example CAP in Construct RC2?

EDIT: Oh okay great! I hope you enjoy it.

I have a few errands to run, but I will make an inventory example tonight, and I'll make that my first video. The basic process is you make an inventory panel, then you create an inventory object as a child. You set the size of each square on the inventory, then you set image panel objects as children on the inventory object. They will automatically snap to a grid when parented to an inventory object. They will also never overlap each other. They fire a condition if you try to drop an object on another object.

There's an expression on the inventory object that will let you see if the inventory has any space, and another expression that tells you where the first available space is.

Each object in the inventory is an image panel. Image panels are kind of like sprites but instead of Construct handling them, GWEN handles them. They are GUI objects that can be docked and so forth. They have a load from external image action, and more importantly, a set UV action. Set UV means you can load a giant image with all your inventory object art on it, like this, and then make image panels with that image. Set UV will let you select which object you want the image to represent. This saves a lot of memory in the long run. Like I said, I created each widget thinking about long term implications.

Another example of that is that each and every widget has a "set data" action and a "get data" expression. "Data" can be anything you want, a string, integer, float, whatever. The cool thing is that you can use set data on all of the image panels to set statistics for the object that it represents. (It's name, damage, etc.) Set and Get Data are found in the common widget options, since they affect all widgets.

I will have the example cap and Youtube video for all this functionality ready tonight.

The full post is available in the completed addons forum here - this thread will be closed shortly.

<center><img src="http://dl.dropbox.com/u/1032313/256.png" border="0">

<font size="4">GUI system aimed at games</font>

</center>

What is GWEN?

GWEN is a collection of easy to use widgets for use in easily designing graphical user interfaces for either games or applications. It can be fully skinned, it performs well, and it has many more options than the vanilla alternatives.

Why do I need GWEN over Construct's normal interface options?

Construct offers a lot of objects designed to help you make a game, but it doesn't quite cut it for many situations. Many of the objects, like list boxes, or edit boxes, or combo boxes, cannot be hidden or destroyed in Construct. They all look exactly the same, because they are based on the Windows API, and for the same reason, they all behave exactly the same and have the same bugs.

A quick example of this - make a list box in vanilla Construct. Now try to hide it, or make it transparent. Your only option is to move it off screen, which is not an ideal solution. GWEN uses Construct's innate rendering capabilities, not Windows. It is much more flexible because of this.

GWEN's widgets are all created at runtime directly on the event sheet, where they can be organized into groups and collapsed. This means they won't be cluttering up your layout in the editor. You can have hundreds of buttons and still easily navigate around in your layout. This doesn't mean GWEN is difficult to use - I have designed GWEN to be as easy to use as possible. You can crank out a professional interface in minutes.

Tired of counting pixels and calculating percentages? GWEN can do all the measuring for you, meaning absolute coordinates aren't necessary - widgets can be docked, ordered, and aligned based on relative positions rather than absolute coordinates, taking a lot of math off your shoulders and giving you flexibility. This means that if a window is resized, or a resolution is changed, it's no longer your problem. You don't have to shuffle the interface around, GWEN will do that for you.

Lastly, GWEN has a lot more interface widgets than Construct. Some examples are context menus, toolbar ribbons, tree lists, rpg inventory screens, and tooltips. There's more, but listing them all would take up half the page, instead, just check out the free demo!

These are only a few of the many benefits, but it gives you an idea of how massive GWEN is and how much it can help you. I personally use it in my current projects.

I need video evidence.

I currently have two good videos, I'm working on many more.

Teaser Two

I would like to try GWEN for free.

There is a free demo available, it is not time limited, and it is just as powerful as the full version, but it has a DEMO watermark on it. This should let you play with the plugin as long as you like without purchasing it. It comes with a fully commented example cap.

Download the GWEN Demo HERE!

This is pretty awesome! Where do I get the full version?

The full version of GWEN is $9.99.

Buy GWEN HERE!

What's the license look like?

Basically, you can release whatever you want with the demo version. With the retail ($9.99) version, you can release independent games. I classify independent as free games, or games that gross under $3500 income. If you get lucky enough to make it to that point, I'll ask for $90 for the super duper commercial unlimited license. I don't have the legal power to enforce this license, but I struggle to make enough cash to eat, and I work at Walmart every night, so shame on you.

GridTree and Noise were free, why are you charging for GWEN?

GWEN's complexity, enormity, usefulness, and sheer awesomeness put it leagues ahead of my previous plugins. I released those with an optional donation option, and it didn't work out so well. GWEN took a long time to develop, and I put a lot of care into it. My financial situation isn't so great - I work at Walmart every night and develop in my spare time, so I am inclined to sell it. I apologize for the inconvenience, but trust me - it'll be worth your while, and I will support the plugin post release until it's as bug free as I can make it. All future updates will be free.

I'm confused!

Luckily for you, I am working on an array of Youtube videos outlining every aspect of GWEN from how to install it to how docking a widget works. Unfortunately, they aren't quite ready yet! This space is reserved for links to them as I complete them.

I found a bug.

These are the currently known issues:

• GWEN looks weird, ugly, or different from the screenshots. - If GWEN cannot find a valid skin, it will default to using basic colors. Make sure that you have your skin property pointing at a valid skin.
• Button behaves oddly when mode is not set. - Known issue.
• Property List incomplete - Working on this.

Did you find something that isn't on this list? It's much easier to get my attention via private message, so PM me the details, and I'll fold a fix into the next update. Thanks for your help!

http://dl.dropbox.com/u/1032313/GWEN_DEMO.zip

Here's the demo, working on a proper release thread as we speak, but this will let you guys play.

Tonight I will release a free demo so anybody on the fence can see GWEN in action.

http://screencast.com/t/E0sLG0WKH

That seems to be what you want. It makes all the conditions fire as expected on this end. Despite buttons being pressable by default, forcing the mode makes the conditions work. I'll fix this in the first patch. Thanks for the report.

Alrighty, I have released GWEN. After a few weeks of implementing feature requests, fixing a few known issues, and fixing issues that people find, I will release an update to it. Please keep that in mind. All the legal stuff is written in ENGLISH in the readme, not legalese. Also keep in mind that you will need a skin file for GWEN in the same directory as your CAP. A default skin is provided in the zip file.

GWEN makes beautiful, powerful interfaces. I've already used it in a few personal projects. You won't regret your purchase. For more in depth information on GWEN, read its project page here: http://code.google.com/p/gwen/

Benefits of using GWEN over Construct UI elements: GWEN uses CONSTRUCT to render itself, not Windows, meaning it is much more flexible. All of GWEN's interface elements are created, modified, and maintained in the event sheet - meaning instead of cluttering up your layout, they can be organized into groups and minimized. GWEN can do all the measuring for you, meaning absolute coordinates aren't necessary - elements can be docked, ordered, and aligned based on relative positions rather than absolute coordinates, taking a lot of math off your shoulders and giving you flexibility, and meaning that changes at runtime (whether the user resizes something or the resolution changes) are reacted to instantaneously and smoothly. GWEN has a lot more interface options than Construct. Context Menus, toolbar ribbons, tree lists, inventory screens, etc. These are only a few of the many benefits, but they are the ones I like the most.

Video Two! (Shows off a lot more widgets than video one. The program in this video was made fairly quickly with GWEN, despite the complexity.)

I will be recording and releasing Youtube videos outlining (in great depth) how to use each widget in the coming days/weeks. I will also create a proper release thread in the completed addons forum. However, for now:

Buy GWEN!