Future Development

Pick 'Em
Monday Night
Survivor

[TaskMaster]

Currently I am working on a form builder for ifsoGUI.  It will be simple at first, but hopefully I will have a chance to improve and fine tune it into something really useful.

Future Gadget Ideas
Splitter
Image
Image Button
Tree View
Multi-Column ListBox (maybe same as a grid).
Grid
Dual Slider - Allows a range selection.
Color Selector
Option Buttons

If you have any more ideas/suggestions, feel free to post them.

[matibee]

+1 for a color selector and a treeview, but I'm selfish and can live without the others at the moment

Also;
Menus
Window buttons (minimize & close)
Render Target

and documentation!

I'd like to see what members / funcs each control has.

I've been using ifsoGUI for less than a day and I'm very impressed so far.  Keep up the good work.

[TaskMaster]

The http://www.ifsogui.com website has docs on it.  They could be better and I will slowly improve them.

I thought about close button and min/max button for the Windows.  Should be fairly easy to implement.  I just always thought of ifsoGUI being used for a game interface, and min/max buttons just aren't seen very often on windows in a game's GUI.

I think the best thing to do for those buttons would be to just to have the gadget put them there and return events.  Let user decide what to do when they have been clicked.  Min/Max the window, or hide it, or destroy it, or what ever...

Menus, that is a good idea.  I can add that to the list of todo.

Render Target?  How would that work?

[matibee]

A Render target control would give me a canvas to draw on.  Probably nothing more than a TPixmap inside, but as a GUI gadget it would belong to a window (and be moved with it) and handle clipping to the window borders etc just like all other controls.

I guess that's similar to the Image gadget, except I want access to draw on it.

[TaskMaster]

A Render target control would give me a canvas to draw on.  Probably nothing more than a TPixmap inside, but as a GUI gadget it would belong to a window (and be moved with it) and handle clipping to the window borders etc just like all other controls.

I guess that's similar to the Image gadget, except I want access to draw on it.

Well, if there was an image gadget, it could easily be used like that, since you could always just lock it as a pixmap and draw on it.  That is a gadget that would be very easy to code.  Maybe I will make it the next one I do, as it should be fairly quick and easy to do.

And once you get the hang of ifsoGUI, you should be able to subclass the ifsoGUI_Base Gadget and make your own gadgets like an image gadget.  Maybe when I make the image gadget I will create a tutorial for making a gadget as I go.

[matibee]

Oh, thanks for the pointer to the docs 

I'd already glanced through them several times before, but once I got the mod I was locked into thinking the docs would be with it.

[TaskMaster]

Oh, thanks for the pointer to the docs  

I'd already glanced through them several times before, but once I got the mod I was locked into thinking the docs would be with it.

I like the idea of the docs being on a website like that, because then it can become a living document.  Where comments are posted which can help others and improve the docs themselves.  I know when I go tot he PHP website and look in the docs, the comments are always very helpful.  Can usually find good sample code in there as well.  I would like the ifsoGUI docs to be like that eventually.

I guess I could do the bbdocs to HTML thing and supply an HTML docs with the GUI.  I'll look into it and make it available when I can.

[Dabz]

Another BlitzMonkey in the house!

Going to have a peek at the docs!

Dabz

[TaskMaster]

The mod now includes the doc folder, which has the html version of the docs created by build docs in it.  So, now you can view them on your local pc.

I am not sure if build docs can build them without the source, so I will be including them from now on.

[Samah]

I like the idea of the docs being on a website like that, because then it can become a living document.

In that case, maybe you should set up a wiki, but limit editing to ifsogui users.

[TaskMaster]

I like the idea of the docs being on a website like that, because then it can become a living document.

In that case, maybe you should set up a wiki, but limit editing to ifsogui users.

A wiki is a possibility.

I really want to redo the docs, but just not had the time.

[Samah]

You could always create a Google Code project for user-created widgets (and perhaps some of yours, since you still need to purchase the core module).  You could add registered users as committers and anyone who wanted to contribute could check out/in code.  All the source files would be versioned so if there's a bug introduced in one of the custom widgets you could just back it out.

[Samah]

Feature request: Layout managers.
I'm tempted to write one myself actually, but if I do that I'll never finish my game!

[TaskMaster]

Feature request: Layout managers.
I'm tempted to write one myself actually, but if I do that I'll never finish my game!

This is a huge task.  I work on one every now and then, but I don't think i will have it done anytime soon.

[Samah]

Well I might have a go at writing one myself then.  Another feature that would be awesome is support for custom properties.  Java's Swing supports this.  Basically just have a string->object map in ifsoGUI_Base so that every component will inherit it.

Field customProperties:TMap = New TMap
Method SetProperty(key$,value:Object) customProperties.Insert(key,value) EndMethod
Method GetProperty:Object(key$) Return customProperties.ValueForKey(key) EndMethod

Easy.