No, it says safari....
EDIT: Oh, in the right column it says safafi!

nice to hear, it looks really good!

Has this taken advantage of callbacks yet, given that Axe now has variable function calls?  All modern GUI designs these days are callback-based because it makes the programming simple and minimal.

Indeed we are. However, with this:

Dilog("Are you sure?",_LMYes,_LMNo)

That would be an example of over-doing it!

This would create a dialog with the text "Are you sure?" and when the "Yes" button is clicked, calls the label MYes and when "No" or cancel is clicked, calls the label MNo.  This is just an example implementation, but I wonder if its similar?

To fully answer this post... I know for a fact that wxWidgets does not do it this way, but it's C++, an OOP language, which Axe does not feature.... yet.

So for a better comparison, I'll use a C based toolkit which has some OOP principles implemented in the background (hint hint: something that we're aiming for!) for proper comparison.

If we look at GTK+, a very popular C GUI toolkit, we have GtkMessageDialog. (See the API here. This link points exactly to the section I refer to below.)

If you look at gtk_dialog_run(), it shows how might this be used. Let's display it here:
gint result = gtk_dialog_run (GTK_DIALOG (dialog));
switch (result)
  {
    case GTK_RESPONSE_ACCEPT:
       do_application_specific_something ();
       break;
    default:
       do_nothing_since_dialog_was_cancelled ();
       break;
  }
gtk_widget_destroy (dialog);We don't use callbacks in this case; instead, we take a result integer and compare it to another, preferably through predefined variables (in this case, GTK_RESPONSE_ACCEPT).

For those not versed in C, a pretty Python example (PyGTK) is shown below.
        dialog = gtk.MessageDialog(self, 0, gtk.MESSAGE_QUESTION,
            gtk.BUTTONS_YES_NO, "Are you sure you want to exit?")
        dialog.format_secondary_text(
           "We don't want you to lose any data.")
        response = dialog.run()
        dialog.destroy()
        if response == gtk.RESPONSE_YES:
            gtk.main_quit()
        elif response == gtk.RESPONSE_NO:
            print "Not exiting."
However, a case where callbacks may be (or rather, should be) used is when you create a window with all sorts of widgets inside.
For the sake of simplicity, I'll show PyGTK code.

**********************************
* Hello world!               [X] *
**********************************
* +--------+                     *
* | Button |                     *
* +--------+                     *
**********************************

import gtk

class PyApp(gtk.Window):

    def __init__(self):
        super(PyApp, self).__init__()
     
        self.set_title("Hello world!")
        self.set_size_request(250, 200)
        self.set_position(gtk.WIN_POS_CENTER)

        self.connect("destroy", gtk.main_quit)

        self.fixed = gtk.Fixed()
        self.add(self.fixed)
       
        button = gtk.Button("Button")
        button.set_size_request(80, 35)
        button.connect("clicked", self.on_clicked) # There's the callback! :)
 
        self.fixed.put(button, 50, 50)
     
        self.set_tooltip_text("Window widget")
        button.set_tooltip_text("Button widget")

        self.show_all()
    def on_clicked(self, widget): # This handle the event
        dialog = gtk.MessageDialog(self, 0, gtk.MESSAGE_QUESTION,
            gtk.BUTTONS_YES_NO, "Are you sure you want to exit?")
        dialog.format_secondary_text(
           "We don't want you to lose any data.")
        response = dialog.run()
        dialog.destroy()
        if response == gtk.RESPONSE_YES:
            gtk.main_quit()
        elif response == gtk.RESPONSE_NO:
            print "Not exiting."

PyApp()
gtk.main()

We, of course, can get even more complex by talking about the different ways you could handle events - GTK+ uses signals and callbacks, Qt signals and slots, wxWidgets an "event table" and regular callbacks (scroll down). Kinda crazy, eh? I think our plan is to do the "signals and callbacks" method, since it's the simplest to implement and possibly use.

---

Finally, a note to all: we follow the rule "show, don't tell" simply because we like giving surprises (who doesn't? ), but also it gives us freedom to work on it any time without any deadline pressures. And if it does die - possible, but not likely - no one can be really disappointed because we never offered any expectations in the first place.

This project is undergoing a significant rewrite - we used to do something like this:
AddButton(A,1,2)
While Z!=15
getKey->Z
If Z=1
Y+1->Y
End
. etc...
If Z=19 .or whatever ENTER is
DlgBox("Hello world!")
End

Doing it this way would make it impractical, verbose, and just a pain to make a GUI with.
Hence, we went for a complete redesign, with sophisticated planning so that you guys will enjoy the new, refined AGL once it's released!
As always, the foundation builds the house, NOT the roof nor the pretty furniture - and we're focusing on that foundation.

If you are really good at Axe, have a passion for GUI toolkits, and would like to help, come on board! We could use all the help we can get! Either reply in this topic or PM me and you'll get added in. If possible, showcase some of your previous best works (like a resume ).

A new year.... a new chance for infinite possibilities!

uh...you lost me.

Heh, I'm probably a bad explainer then

Basically, the way you build a GUI is to have a "container" to hold the "widgets", starting from the base and up.
When you want to make something interactive - say, if I click a button, I get a popup window - then you have to use a function to "connect" a signal and a callback.

Here's a possible future Axe GUI Library example: (I do not use 5 char label names here since they are very ambiguous)
.AXEGUI
InitGUI(GUIV) .Sets up the GUI system
AddWindow(GUIV, WINV, "Hello world!", 1) .Creates a "fullscreen" window
AddLabel(WINV, LBLV, "Click that button!") .Creates a label
AddButton(WINV, BTNV, "Click me!") .Creates a button

.Let's make it interactive!
Connect(BTNV, 1, _LOnClick) .Set up button so that when it's clicked, the label OnClick is called.
ShowGUI() .Show the GUI/mouse.
DestroyGUI() .Delete the GUI once done
Return .Exit

Lbl OnClick
MsgBox("Hey! What a cool MsgBox this is!") .Show a dialog box (MsgBox)
Return .Exit from subroutine


If you're still confused, please tell me and I'll try to clarify. (That may mean the current API must be complex... )