The FreeBASIC GUI Compiler

[adosorken]

Once the QBXL compo is over, I'll be back at work on regular projects. For now though, I'm crammin' at an RPG for this compo, and now I gotta get back to work on it if I ever expect to finish it in time. Cya tomorrow, hehehe.

[ShadowWolf]

will it be possible to creat our own controll's like in VB?

[adosorken]

Dunno yet. Even in the ease of VB, that's a pretty advanced topic. So it remains to be seen. I'm going to say no initially (as in it won't have the capability at first, other issues are more important), but as the project matures, it may very well become an option.

[ShadowWolf]

an easy way to do it would be to use a dll's then some sort of script system i.e.

have the code for how the controll will work compiled into a dll
then a script of some sort for how the GUI IDE will handle it code generation.

then have all that packed togather in one file like a faked OCX
i.e. DLL and import lib .A , script , and then resource stuff like bitmaps ect.

i.e. so when the user add's the controll to his/her projected the GUI ide reads the ocx use the script to set up code generation and the resource for the bitmaps and stuff if used then at compile time unpacks the DLL and import lib and links.

[MystikShadows]

Dunno yet. Even in the ease of VB, that's a pretty advanced topic. So it remains to be seen. I'm going to say no initially (as in it won't have the capability at first, other issues are more important), but as the project matures, it may very well become an option.

Well, VB's control create is quite limited, as in it's really just combining more than one control (which all have the same events) into a container (parent) object. I say once you have all the controls working, adding a container type to contain these controls that spit out just the events that you want users of the control to control and you're all set. :-). The rest is/should be exactly the same as a control like any other you'd typically create as a base control.

[Anonymous]

o.o _awesome_. any idea yet as to a beta release date?

[adosorken]

Update: work on the property palette is being done as we speak, which gives this sucka authentic VB-like editing of control properties. It's not going to be identical, but it's very very similar. However, as a trade-off, the properties are expanded over their VB6 counterparts; standard controls now have more options and switches to give them new functionality that in VB6 you had to use raw API calls to accomplish (half-sunk and fully-sunk border styles on labels, for example...VB6 only offers fully-sunk). Almost all common controls are available directly from the IDE without need to include bulky additional OCX files. Controls based on DLL files will be supported natively (like scilexer.dll, for example), but I'm still researching the possibilities with actual OCX files. Probably gonna require some pretty severe OLEAUT R&D.

Expect a working demo version in April.

[adosorken]

Code:

Set ChildForm = New Form

This does not work. VB says "Invalid use of New keyword".