2nd part.

4th.

Who download only some parts of the file? probably  the boots that are constantly tracking the WWW.

----

Ok, once with QUIGS downloaded and installed, you must open the SETTINGS.TXT file to adapt the program to your monitor resolution. Also, it must be run on a freshly loaded WIN session, because if not, it will refuse to work annoyingly.

Now I will give a brief description of what is it and what not.

It is an environment, not only an editor for a language, it brings a lot of tools to create the app. Once you start using it understand the titanic task of creating it, while doing it so easy to the user.

Sadly, it has ONE BIG DRAWBACK: still there is no manual of use.... although it is very intuitive to use. Other minor drawback is that it has still a number of bugs, but it is very usable. For example, the use of Copy/Paste is very limited and the lenght of the lines has not been defined.

But first some hints about the target of QUIGS -----> SymbOS.

SymbOS is a "modern" multi-task WIMP,(Windows, Icons, Mouse, Pointer) operative system on a Z80 architecture computer, you all know that, but internally it manages cleverly and very fast a lot of "complex" things to show us a face that seem very similar to a WIN98 OS. Like EXOS, it manages automatically the pagination system, but instead, all SymbOS apps are made of relocatable code, something that EXOS can do but is not so easy to achieve. Don't fear, QUIGS will do that task for us....

Also, SymbOS is not a whole thing, it is made of a multitude of "events", like open/close a window, click a button, pull a menu, etc. QUIGS necessarily has to be based on these elements so, every time we launch the environment we  are presented with the first event, the bigger of all, Main:

[ Guests cannot view attachments ]

If you click on the Form label you will see appearing something like this instead of the code:

[ Guests cannot view attachments ]

And, if you click on the middle of the "form", some options will emerge at the right side of the screen:

[ Guests cannot view attachments ]

The "forms" can be accumulated, is for it that QUIGS has the "Control Form" selector under the design grid, to edit the forms one by one.

Like with the Main event, here we have a main Form that will be the first frontend to be seen when the program will be opened.

At the left of  "Control Form" we have the "Add Control" selector. As you can see all reminds to a paint program, but the fact is that it is real programming....

The options that have appeared at the right of the screen are the attributes of the selected form. And under them you can see where the events that control the form will be created.

Being the events of the Main form, we have to be careful with them.

If you click on new "Form1.Open.Event" or "Form1.Close.Event", you will see immediately how the event is added to the Code list. Open will serve as the initialisation of the program, and Close will be the place where the computer resources are liberated, just like you do on other languages. Logically, the Open code will be executed just at the launching of the program, and the Close code when the  X in a square at the top most right corner of the main form is clicked or other ways implemented to close the program.

All variables declared at the start of the code are shared by all the events, so better select well the names. Also, the order of the events is not important, and their effect can be simulated, for example, an action on some code can call the execution of "Form1.Close.Event", what will automatically close the program without need to clicking the X...

On Form1 I displayed an Enterpress logo and a text below it.
However, compile failed. When you start the .exe file, the cursor bounces in SymbOS
Or I went very far and missed important things (which you haven't written down yet)

I am going to return to this thread. I feel that if I don't do it now it will remain unfinished forever.....

-------

Be careful from now on, because some of the  actions on the environment still don't work properly and can hang it.... but we can save the project every time that some thing is well done, or even use several names for the phases we achieve in your work.

Ok, now that we have the empty main form(the front-end of our future application), and defined its characteristics on the left side of the screen, we can begin to add controls(events) to it.

[ Guests cannot view attachments ]

They are used like the tools on a paint program. Put the mouse pointer over the symbols and a brief description will surface. Select one of them and paste it on the work area inside Form1. A lot of controls will appear on the right side of the screen instead of the ones for Form1. There we can modify parameters of the pasted control, even we can erase it. There are dimensions and position, colours and the usual navigation buttons. The last setting is to add the control to the text of the program. The environment proposes us a name, but we can put there what we want.

In the case of text boxes, usually it appears an input line where we can write the default text we want they to show at start.

Always will be one of the controls or forms highlighted on the work area, to show to which event the settings shown correspond. It is not necessary that all objects shown on the form have a function. For example, if we need to put a warning text on some part, it will not interact with the other events, so we don't need to add it unnecessarily to the text code.

Let´s see an example:

[ Guests cannot view attachments ]

This is the code:

// Quigs 1.01 Application for Symbos
// Name:
// Coder:
// Date / Version:

// Declare variables
Var position:Int=1

// End declares

Function Main:Void()
 // Main loop
 
EndF

Function Button1.Event:Void()
 If position=0 Then
 position=1
 Button1.Text.Set("")
 Button1.Refresh
 Button2.Text.Set("click here")
 Button2.Refresh
 EndIf
EndF
Function Button2.Event:Void()
 If position=1 Then
 position=0
 Button2.Text.Set("")
 Button2.Refresh
 Button1.Text.Set("click here")
 Button1.Refresh
 EndIf
EndF

I only have defined 2 buttons, and declared them as events on the text code.

As you can see, the code is controlled by only one variable, position.

The code on every button is only executed after a click on it.

The function XXXXX.Text.set("yyyyy"), where XXXXX is the name of an event, is used to change the text on the buttons, and XXXXX.Refresh is used to effectively write the text.