PureGUI

Developed or developing a new product in PureBasic? Tell the world about it.
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by Franco.

In a few weeks, depends on a better build-in PureBasic 'Events' implementation (hopefully coming with 3v1)
and some other stuff (like easiely creating PB libs with PB - still waiting for since 2v4...)
I will release the first public version of PureGUI.

Then you can use your Gadgets like:

Gadget1=PG_CreateButtonGadget(Window1,320, 10, 100, 25,"Button","Gadget 1 ToolTip",?FunctionGadget1)

The name of the Gadgets can change...
If you want, you (every registred user of PureBasic and Fred ) can make suggestions how to name the gadgets.
But remember, I don't want to interfere with the 'normal' PureBasic Gadgets names.

My First thought was to use the same 'gadget names' with an additional 'PG_' in front.
But as you can see I like also a 'CreateButtonGadget' syntax.

Now would be the time to tell me what you think...

'?FunctionGadget1' is the function called by pressed Left-Mouse-Button on the gadget...

Gadget Numbers are not needed anymore.
You don't have to create a event loop and catch the event for every gadget - all is automatically set.

If you need to use API calls and you need a gadget handle you can use the command:

GadgetHWND = GetGadgetID(Gadget1)

because the value returned (Gadget1) is the GadgetNumber. (Remember: a PureBasic Gadget returns the Handle/ID)
AFAIK Handles are Windows specific and not used in Linux or Amiga.

If you use StringGadgets - simply press 'Enter' after typing your string in, and the function behind this gadget
is called (in this way you can change a value of a variable or something like that) without pressing any other Gadgets.
ComboBox works the way it should (I hope... - for now win API used)
And more...

It would be nice to hear how many users are interested in something like that (Hi Fangles, I know you are...)


PureGUI code looks like:

Code: Select all

;start the PureGUI code
 
PureGUIApplication()
 
MainWindow1=PG_OpenWindow(200, 200, 320,240,#PB_Window_SystemMenu|#PB_Window_SizeGadget,"PureGUI Window")
 
Menu1=PG_CreateMenu()
  PG_AddMenuTitle("Project")
    MenuItem1=PG_AddMenuItem("New",?FunctionMenu1)
    MenuItem2=PG_AddMenuItem("Open",?FunctionMenu2)
    MenuItem3=PG_AddMenuItem("Save",?FunctionMenu3)
PG_AttachMenu(MainWindow1,Menu1)
 
ToolBar1=PG_CreateToolBar()
  ToolBarButton1=PG_AddToolBarStandardButton(#PB_ToolBarIcon_New,"ToolBarButton 1 ToolTip",?FunctionButton1)
  ToolBarButton2=PG_AddToolBarStandardButton(#PB_ToolBarIcon_Open,"ToolBarButton 2 ToolTip",?FunctionButton2)
  ToolBarButton3=PG_AddToolBarStandardButton(#PB_ToolBarIcon_Save,"ToolBarButton 3 ToolTip",?FunctionButton3)
  ToolBarButton4=PG_AddToolBarStandardButton(#PB_ToolBarIcon_Print,"ToolBarButton 4 ToolTip",?FunctionButton4)
  ToolBarButton5=PG_AddToolBarStandardButton(#PB_ToolBarIcon_Find,"ToolBarButton 5 ToolTip",?FunctionButton5)
PG_AttachToolBar(MainWindow1,ToolBar1)
 
Gadget1=PG_CreateButtonGadget(MainWindow1,20, 100, 100, 25,"Button","Button 1 ToolTip",?FunctionGadget1)
 
PG_RunApplication()
 
End
 
IncludeFile "Functions.pbi"
 
;end the PureGUI code

In the IncludeFile Functions.pbi are all functions needed (as Subroutines).
It looks like:

Code: Select all

;start Functions.pbi
FunctionButton1:
  XIncludeFile "FunctionButton1.pbi"
Return
 
FunctionButton2:
  XIncludeFile "FunctionButton2.pbi"
Return
 
FunctionButton3:
  XIncludeFile "FunctionButton3.pbi"
Return
 
FunctionButton4:
  XIncludeFile "FunctionButton4.pbi"
Return
 
FunctionButton5:
  XIncludeFile "FunctionButton5.pbi"
Return
 
FunctionGadget1:
  XIncludeFile "FunctionGadget1.pbi"
Return
 
FunctionMenu1:
  XIncludeFile "FunctionMenu1.pbi"
Return
 
FunctionMenu2:
  XIncludeFile "FunctionMenu2.pbi"
Return
 
FunctionMenu3:
  XIncludeFile "FunctionMenu3.pbi"
Return
 
; this is the very end my friend...
Every Gadget has his own Subroutine and IncludeFile (like XIncludeFile "FunctionButton1.pbi").

That's because I like to have my code reusable and the possibility to make a neat 'Visual IDE' called 'PureGUIDE'.
In PureGUIDE you draw a Gadget and when you press the right mouse button on it you get the possibility to enter
your code that will be executed.

Yes, it is a modular way to code and some of you don't like the IncludeFile stuff.

But it is the easiest way to write/delete/change gadget-function-code without messing up the main-code.

If there is no interest for such a GUI-Class in PureBasic let me know. (or if you think it is useless...)

Anyway tell me what you think...


Have a nice day...
Franco

Sometimes you have to go a lonely way to accomplish genius things.
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by Andre.

I like your idea. It seems especially useful for user-definable GUI's, where the programmer can offer all possible functions and the user (via definable GUI layout files) can define the look and feel. Makes skinned Gui's easier


Regards
André

*** German PureBasic Support ***
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by Fangbeast.
It would be nice to hear how many users are interested in something like that (Hi Fangles, I know you are...)
hahaha, you caught me watching again :):)

Fangles
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by tinman.
I will release the first public version of PureGUI.
Cool, looking forward to it :)
Now would be the time to tell me what you think...
That would probably be easier for people to remember (same command names, only with PG_ in front). I think ButtonGadget seems to imply that you are creating a gadget - when you need to change things, the commands would be named Set....

because the value returned (Gadget1) is the GadgetNumber. (Remember: a PureBasic Gadget returns the Handle/ID)
AFAIK Handles are Windows specific and not used in Linux or Amiga.
Obviously you can get pointers to the gadgets on the Amiga, and most likely Linux too. It would be *very* cool if you could get this to be cross platform. There is absolutely nothing like this (well, the PureGUIDE) on the Amiga at all AFAIK.
If you use StringGadgets - simply press 'Enter' after typing your string in, and the function behind this gadget is called (in this way you can change a value of a variable or something like that) without pressing any other Gadgets.
How easy/possible is it to add functions for different events other than the default one? I guess this comes down to what kinds of events PureBasic gives you. I use C+ Builder and it is sometimes useful to be able to assign a function to the event when you double click on a gadget instead of single clicking as you would normally.
It would be nice to hear how many users are interested in something like that
I am :)

Code: Select all

PG_RunApplication()
 
End
How do you control when your application quits?

Thanks. And keep up the good work, I think a lot of people would be interested in this.


--
It's not minimalist - I'm increasing efficiency by reducing input effort.
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by Stan.
...
Now would be the time to tell me what you think
...
It would be nice to hear how many users are interested in something like that (Hi Fangles, I know you are...)
...
Anyway tell me what you think...

Have a nice day...
Franco

Sometimes you have to go a lonely way to accomplish genius things.
This will be GREAT (and modularity is also a plus)

I would be interested (don't think I am alone) ...

Best wishes.

Stan



Since I attended an MS course, my programs no longer have bugs ... just hidden "features" !! [ PB. registered user ]
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by naw.

Aha! Now I see why you had (some) interest in my INI File GUI comment.

This looks great - when released, I will abandon my INI files for ever :wink:
Can you use Procedures instead of labels? - or both even...

I really think this would be an enormous bonus for PB (assuming it works :wink:, it should be part of the standard distro)

How about these syntax compromises:

Using Labels:
~~~~~~~~~~~~

Button1=PG_CreateGadget(#ButtonGadget,Window1,320,10,100,25,"Button","ToolTip",?Button1Label)

Using Procedures:
~~~~~~~~~~~~~~~~

Button1=PG_CreateGadget(#Button,Window1,320,10,100,25,"Button","ToolTip",MyProc1(),MyProc2(),MyProc3(),MyProc4(),MyProc5())

- the last 5 params identify different Procedures for left & right buttons, double click, drag and drop

Or better still:
~~~~~~~~~~~~~~~
PG_Gadget("Button1")=PG_CreateGadget(#Button,Window1,320,10,100,25,"Button","ToolTip",MyProcedure(PG_ButtonAction,PG_GadgetValue$,PG_GadgetIndex))

- PG_ButtonAction = left/right/dbl click/drag/drop
PG_GadgetValue$ = The label on a button or the value of a text/combo/tree
PG_GadgetIndex = The Index # of combo/tree/list ... or 0 for a string

I really like this syntax - very compact and still descriptive
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by Franco.
Obviously you can get pointers to the gadgets on the Amiga, and most likely Linux too. It would be *very* cool if you could get this to be cross platform. There is absolutely nothing like this (well, the PureGUIDE) on the Amiga at all AFAIK.
Well, sorry but I have really no Amiga background. Sorry for that.
A view month ago I played with AmigaUE (hope the name is right) but I didn't like what I saw - very low screen resolution, and nothing that I was able to start.
Yes, I found somewhere on the net a 'StartKick' file and I figured out what to do, but I suppose only people that worked for years with Amiga really know what I'm missing here.
For now I'm stucked with Windows and I like Linux (except for X/KDE/GNOME and the hole 'dependencies' crap - I hope Bill Hayden goes along with his work to port the AtheOS GUI (like BeOS) to the Linux kernel and brings an application installer with it - but this is another story...).
How easy/possible is it to add functions for different events other than the default one? I guess this comes down to what kinds of events PureBasic gives you. I use C+ Builder and it is sometimes useful to be able to assign a function to the event when you double click on a gadget instead of single clicking as you would normally.
Well this is very easy and already working, but I don't want to confuse the users a lot at the beginning. I want to start without implementing all possibilities - could be too confusing.

Code: Select all

PG_RunApplication()
 
End
How do you control when your application quits?
Well PG_RunApplication() is at this time a combination of 'PureBasic-Event Stuff' and 'WindowCallback-API Stuff' combined with other things to get the Event action done. Only with this combination it works properly (at this time...).

But I really don't like it, because if the coder has a second WindowCallback routine it will disable a part of PureGUI's Event functions and this is very, very bad.
That's why I'm waiting for better working Event stuff in PureBasic - hope Fred get this things done - otherwise NO WindowCallback routine allowed in PureGUI code


Have a nice day...
Franco

Sometimes you have to go a lonely way to accomplish genius things.

Edited by - Franco on 30 April 2002 17:29:45
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by Franco.
Aha! Now I see why you had (some) interest in my INI File GUI comment.

But I don't use ini files to store the positions of the gadgets.
Don't know if there are a lot of users that want such a thing.
Skinnable GUI is only nice if you could change the look of Buttons not only the position.
But I never saw such a program that was lean. Every skinnable application is bloated and I like it small, fast and simple.
For now, only the application programmer can change the position of the gadgets...
Can you use Procedures instead of labels? - or both even...
Yes, you can call Procedures instead of Labels without problems.

Well actually my first steps creating PureGUI was to call Procedures.

BUT after chatting with Paul (hi Paul ) I'm convinced that Subroutines have a lot more advantages as Procedures:
1.) Every created variable is available without the shared/global stuff.
2.) Because of the modularity of PureGUI you can even put a procedure in a subroutine.
You can't code a Procedure inside a Procedure.
So if you want to code a Procedure in a Gadget Event Subroutine you can do it!
And if you have a procedure in a subroutine you can 'declare' it, and all
procedures will work properly.
(for this there will be a OnStart subroutine to put all 'declare' stuff in it.)
3.) Maybe calling Subroutines are a little bit faster than calling Procedures.
I really think this would be an enormous bonus for PB (assuming it works :wink:, it should be part of the standard distro)
Well I don't know about this... maybe, but this is Fred's decision.
(maybe he is coding such a thing too... and my code will be obsolete - I don't know)

For now let's start quite and smooth first...
How about these syntax compromises:

Using Labels:
~~~~~~~~~~~~

Button1=PG_CreateGadget(#ButtonGadget,Window1,320,10,100,25,"Button","ToolTip",?Button1Label)

You got me again

I played around with such a style but I don't know if this:
Button1=PG_CreateGadget(#ButtonGadget,Window1,320,10,100,25,"Button","ToolTip",?Button1Label)
is better than:
Button1=PG_ButtonGadget(Window1,320,10,100,25,"Button","ToolTip",?Button1Label)

That's a good point to be discussed with more users...
Using Procedures:
~~~~~~~~~~~~~~~~

Button1=PG_CreateGadget(#Button,Window1,320,10,100,25,"Button","ToolTip",MyProc1(),MyProc2(),MyProc3(),MyProc4(),MyProc5())

- the last 5 params identify different Procedures for left & right buttons, double click, drag and drop

Or better still:
~~~~~~~~~~~~~~~
PG_Gadget("Button1")=PG_CreateGadget(#Button,Window1,320,10,100,25,"Button","ToolTip",MyProcedure(PG_ButtonAction,PG_GadgetValue$,PG_GadgetIndex))

- PG_ButtonAction = left/right/dbl click/drag/drop
PG_GadgetValue$ = The label on a button or the value of a text/combo/tree
PG_GadgetIndex = The Index # of combo/tree/list ... or 0 for a string

I really like this syntax - very compact and still descriptive
Autsch, you got me again and again

Right Mouse Button is already working properly (I need it for PureGUIDE), but my intension was to start without it... thought that maybe nobody than me needs it.

The other stuff 'dbl click/drag/drop' is not planned yet. This is not an easy task.
And I don't want to bloat the applications while using PureGUI.


Have a nice day...
Franco

Sometimes you have to go a lonely way to accomplish genius things.
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by tinman.
Linux too. It would be *very* cool if you could get this to be cross platform. There is absolutely nothing like this (well, the PureGUIDE) on the Amiga at all AFAIK.
Well, sorry but I have really no Amiga background. Sorry for that.
A view month ago I played with AmigaUE (hope the name is right) but I didn't like what I saw - very low screen resolution, and nothing that I was able to start.
UAE? Yeah, if you are new to Amigas then you are unlikely to know what software you need to get it all set up properly. It is probably even worse if you are only downloading stuff and not buying a package which has it all ready for you (e.g. Amiga Forever).

No problem though - it would have been nice to have PureGUIDE on Amiga, but it is unlikely I will be running the program I am coding on an Amiga for some time anyway.
How easy/possible is it to add functions for different events other than the
Well this is very easy and already working, but I don't want to confuse the users a lot at the beginning. I want to start without implementing all possibilities - could be too confusing.
Bah, burn the beginners! :wink:
I guess you have been coding this as a library? Maybe you could use the new variable arguments feature of PB, and then only mention the simple set of parameters. Maybe have a separate advanced programmers section which mentions all the extra parameters?
How do you control when your application quits?
Well PG_RunApplication() is at this time a combination of 'PureBasic-Event Stuff' and 'WindowCallback-API Stuff' combined with other things to get the Event action done. Only with this combination it works properly (at this time...).
I probably should have asked this too, but is it possible to quit your application from your own code? Not just rely on what PureGUI thinks is best (i.e. all windows get closed, PureGUI quits the application). Unless I misunderstood you, and you have not done that stuff yet?
But I really don't like it, because if the coder has a second WindowCallback routine it will disable a part of PureGUI's Event functions and this is very, very bad.
I can imagine :)


--
It's not minimalist - I'm increasing efficiency by reducing input effort.
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by marlo.

Hi all, im a beginner on PB,i use some tools in the past,most of them visual authoring tools. Purebasic is an excellent tool,fast and create extremely small exes, maybe one of more small that i see on my 41 years.If PB can be used in a visual way, PB become, maybe one of the most popular programming tool, imho.The thing is how implement that visual way of programming in PB. I see the Visual IDE, but only help us on windows and controls.I wait for PureGUI!!

south south america
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by naw.
Hi all, im a beginner on PB,i use some tools in the past,most of them visual authoring tools. Purebasic is an excellent tool,fast and create extremely small exes, maybe one of more small that i see on my 41 years.If PB can be used in a visual way, PB become, maybe one of the most popular programming tool, imho.The thing is how implement that visual way of programming in PB. I see the Visual IDE, but only help us on windows and controls.I wait for PureGUI!!

south south america
I think this is a different topic for this thread...

I hope PB maintains a Text Editor interface as the default - I hate all this MS *Visual* stuff - but I understand other people do like it. As an alternative way of programming, fine. But I suspect that the flexibility of PB would be compromised and the code would bloat.

I seem to recall reading that Fred is writing a new PB editor in PB...
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by naw.
Yes, you can call Procedures instead of Labels without problems.
Well actually my first steps creating PureGUI was to call Procedures.
BUT after chatting with Paul (hi Paul ) I'm convinced that Subroutines have a lot more advantages as Procedures:
1.) Every created variable is available without the shared/global stuff.
2.) Because of the modularity of PureGUI you can even put a procedure in a subroutine.
You can't code a Procedure inside a Procedure.
So if you want to code a Procedure in a Gadget Event Subroutine you can do it!
And if you have a procedure in a subroutine you can 'declare' it, and all
procedures will work properly.
(for this there will be a OnStart subroutine to put all 'declare' stuff in it.)
3.) Maybe calling Subroutines are a little bit faster than calling Procedures.
Labels may produce more optimised code (I dunno) but are much less maintainable than Procedures. In any event this is drawing a screen how optimised does it need to be...

The shared/global stuff lets me re-use chunks of code without worry, I wouldn't mourn the loss of labels but I couldnt code without procedures.

How about doing both:
PG_CreateGadget(#Button,Window1,320,10,100,25,"Button","ToolTip", MyProcedure(W,X,Y,Z) )
PG_CreateGadget(#Button,Window1,320,10,100,25,"Button","ToolTip", ?MyLabel )


How About these syntax alternatives:
1) PG_CreateGadget(#ButtonGadget,Window1,320,10,100,25,"Button","ToolTip",?Button1Label)
2) PG_ButtonGadget(Window1,320,10,100,25,"Button","ToolTip",?Button1Label)
3) PG_CreateGadget(#Button,Window1,320,10,100,25,"Button","ToolTip",MyProcedure(PG_ButtonAction,PG_GadgetValue$,PG_GadgetIndex))
That's a good point to be discussed with more users...
The *CreateGadget*(1 / 3) method keeps the number of *new* commands introduced into PB to 1 whereas the PG_ButtonGadget(2) method requires at least a dozen new commands - a page of documentation for each command. I think *CreateGadget* would more readily encompass new GadgetTypes.

The Procedure approach(3) would be very readable and therefore easily maintained
Right Mouse Button is already working properly (I need it for PureGUIDE), but my intension was to start without it... thought that maybe nobody than me needs it.

The other stuff 'dbl click/drag/drop' is not planned yet. This is not an easy task.
And I don't want to bloat the applications while using PureGUI.
Ok - this is a *voluntary project* so I'm just glad you're doing it [;-)].

- but you dont have to code the right/dbl/drag/drop now (or ever) - I just think this syntax:
PG_CreateGadget(#Button,Window1,320,10,100,25,"Button","ToolTip",MyProcedure(PG_ButtonAction,PG_GadgetValue$,PG_GadgetIndex))

would allow you to incorporate it in syntactically one day (perhaps) more easily.
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by PB.

> I played with AmigaUE (hope the name is right) but I didn't like what I
> saw - very low screen resolution, and nothing that I was able to start.

The Amiga is very powerful and configurable, and what you saw was just the
default install, which, in Australia, is a low-res screen of 640x256 pixels.
No different, really, to Windows 95 using a low-res default of 640x480.
Naturally you can use higher resolutions, and run everything, with no problems.
But unless you grew up with the Amiga, it's probably too much hassle to start
learning it, unless you plan on Amiga support for your PureBasic apps...

PB - Registered PureBasic Coder
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by Franco.
I guess you have been coding this as a library? Maybe you could use the new variable arguments feature of PB, and then only mention the simple set of parameters. Maybe have a separate advanced programmers section which mentions all the extra parameters?
Yes, it was intended to be a library BUT...
Like I said in the announcement, I need the possibility to generate PureBasic libs with PureBasic itself.
And the reason is: PureGUI is written in PureBasic not in asm.
I'm not a asm coder! I use a little bit of inline asm but that's it.

Hope that Fred will implement this soon - otherwise I have to alter the generated asm code of PureBasic by hand to get it work (already tested with other code and it seems to work well)

I see no negative point to code a GUI class in PureBasic itself.
PureBasic and C are quite similar in speed and there are a lot GUI classes for C written in C.
Anyway, PureGUI is only used to draw the GUI at the beginning and the GUI-Event command uses inline asm to get it done.

I probably should have asked this too, but is it possible to quit your application from your own code? Not just rely on what PureGUI thinks is best (i.e. all windows get closed, PureGUI quits the application). Unless I misunderstood you, and you have not done that stuff yet?
Well you can use all 'non GUI' related commands of PureBasic anytime.
In every part of your code you can put the 'END' command and the app quits.

You can also use PureGUI's command 'PG_CloseApplication(Title$,Text$)' where a question window appears with your title and text.

Also the 'PG_RunApplication(Title$,Text$)' will have the 2 parameters, so if you close your 'MAIN' window (and only THE MAIN window) you are able to quit your app.


Have a nice day...
Franco

Sometimes you have to go a lonely way to accomplish genius things.

Edited by - franco on 01 May 2002 17:41:57
BackupUser
PureBasic Guru
PureBasic Guru
Posts: 16777133
Joined: Tue Apr 22, 2003 7:42 pm

Post by BackupUser »

Restored from previous forum. Originally posted by Franco.
Hi all, im a beginner on PB,i use some tools in the past,most of them visual authoring tools. Purebasic is an excellent tool,fast and create extremely small exes, maybe one of more small that i see on my 41 years.If PB can be used in a visual way, PB become, maybe one of the most popular programming tool, imho.The thing is how implement that visual way of programming in PB. I see the Visual IDE, but only help us on windows and controls.I wait for PureGUI!!

south south america
Hi Marlo, welcome to the PureBasic community!

PureGUI is not a visual design tool!
PureGUI is a GUI-Class or a GUI-Wrapper or whatever you want to name it.

The advantages are that the main GUI code is really small and the hole GUI event stuff is done automatically. You only code the function behind the GUI-event - thats it.
With releasing PureGUI I want that the users of it use a modular way to code.

But like I said I'm also writing (trying too...) a visual tool coded with PureGUI.
The name of the visual IDE is 'PureGUIDE'.
In this way I can test PureGUI myself while coding a real application.
PureGUIDE should be able to write/read his code and also to export the GUI code to a new project without cracking the code. In this way the GUI code would be reusable.
This is a huge task and I'm not a profesional coder, I have to work to make my living - so the time that I can spend for it is not much.

PureGUI will come out first, and than if there are enough users that 'cry out' for a visual tool I will try get a usable amount of functions in PureGUIDE and release it - but at this time I can't say when it will be.

Lets start quite and smooth with PureGUI (sure there will be a lot of 'user wishes' after releasing it {bugs?}) and than we will see.


Have a nice day...
Franco

Sometimes you have to go a lonely way to accomplish genius things.
Post Reply