Loading...
Logo
Processing Forum
This tool provides a visual form editor that enables the rapid development of user interfaces that use the G4P (GUI for Processing) library, including multiple windows.

Although the tool is both powerful and feature rich it is easy to use.

The website has links for downloading, installation instructions and a number of video tutorials that demonstrate the tool and its use.

[EDIT - due to change in website organisation]
If you just want to view the introductory video first - click here

Replies(15)

really nice,thank you,have to try it out
The property grid video blacks out halfway (ironically, exactly at the moment you say "and you can see"). Maybe my browser didn't cache it properly.

That aside, looks great! I think I'll be using this in future projects.
Awesome Job Peter!!!
Very cool. Seems to work pretty well.  Thanks man!
Great work !!
working under Ubuntu 10.04 too. Processing 1.5.
Thanks for sharing.
Thanks for all the positive comments.

@algo_maccione - thanks for testing it on a Linux machine as I don't have access to one.

@jeff_g - thanks for the testing of G4P when I was first developing it; without your support and interest I would probably never have developed as far as I have.

Just to let you know I am working on the next release of this tool.

Some of the features of G4P are not accessable in the tool and this is what I am working on. For instance GButton can have an icon as well as text and I have the added the functionality to specify the icon image file and to set the icon/text alignment on the button face.

The next thing I want to do is GImageButton and change the GTimer property list to reflect recent changes in this control. Once these are done I will release another version of the tool.

For the version after that I hope to include GCombobox (drop down list) - I have left this to last because I suspect it is the least used control in G4P.

If anyone have any suggestions I will be interested in hearing them.
Thank you for this. Saved me a bunch of time.
I have a simple request/suggestion.
Is it possible to have a build in theme/style maker, which will export code to the customGUI function? Or the possibility to load afile (eg XML) with style properties?
Thank you for your hard work
When I created G4P I used the idea of 'colour themes' so that all the controls had a similar look and feel to them and in the tool it is possible to select one of the pre-defined colur schemes (select SKETCH in the tree view and look in the property grid), also it is possible to add your own colour scheme .
is it possible to have a build in theme/style maker, which will export code to the customGUI function?
The customGUI function is just a place holder where the user can define properties for the controls created in the tool but not accessible in the property grid. As I add functionality to the tool the need for this will diminish.
Or the possibility to load afile (eg XML) with style properties?
At the moment designs created with the tool are saved using 'object serialisation' - this is not ideal because later versions of the tool will not always work with designs created with earlier versions. XML is the obvious solution to this problem BUT it would require an XML scheme to be devised to match G4P and the programming effort to save/load the designs as XML is very significant.

When creating the tool I considered both object serialisation and XML - I went for the first option for 2 reasons.
1) Object serialisation is easier to implement, but more importantly
2) I envisioned that the tool being used a few times when developing the sketch but then once the sketch is finished the tool will become redundant (for that sketch).

I have not completely abandoned the idea of XML but once the tool matures the problem of versioning and the need to use XML becomes less.

Thanks for your input
I'll agree with everyone else that this is a great tool! I had a quick question if you don't mind. I've created a GUI using the builder and am trying to export the sketch as an application. I've placed all image and font files used in the sketch in the application.windows64 folder, but the application still doesn't do anything when I run it. Are there any additional steps that I need to take because I used the GUI Builder to produce this sketch? Thanks again!

 I've placed all image and font files used in the sketch in the application.windows64 folder,

I suspect that this will not work because this folder is not on the search path for Processing.

I am assuming that the sketch actual works / runs in the Processing IDE. If it doesn't then your application export will not work.

Inside the sketch folder create another folder called data and in this folder place all the image and fonts files that your sketch uses. Now make sure your sketch works in Processing. If this is OK then export as application. It should create an application with all the the necessary files (images, sounds, fonts, libraries etc) included.

Are there any additional steps that I need to take because I used the GUI Builder to produce this sketch?
No - GUI Builder has absolutely no effect on exporting the sketch as an application or applet.

Does it work for android mode? I'm having problems when I try to download a sketch made with g4p gui builder. This is parte of the debug message:
BUILD FAILED
C:\Android-sdk\tools\ant\build.xml:713: The following error occurred while executing this line:
C:\Android-sdk\tools\ant\build.xml:727: Compile failed; see the compiler error output for details.

Total time: 13 seconds
 
and it highlights this line:
G4P.setCursor(ARROW)   
You asked this question in another topic you posted just yesterday - I responded in that thread but and it appears you have not read my answer!

READ my response and then post any further questions should be in the other topic ( not this one).

quarks your video is down.
This topic is a year old and I have completely revamped the website so the link is no longer valid. I have edited the link above to point to the introductory video. Note the videos were created using the first release of this tool and the current version is far superior.
looks cool and easy.
Wouldn't hurt if your default button style looked a bit better.