Another minor readme update with gui types

This commit is contained in:
sloum 2022-04-21 16:33:05 -07:00
parent cda9e9bf94
commit 3a61428145
1 changed files with 16 additions and 1 deletions

View File

@ -82,8 +82,23 @@ slope recognizes a few types, that are generally created and used dynamically:
- `(exception-mode-panic)`, will panic and halt execution when an exception is encountered (_default_)
- `(exception-mode-pass)`, will return the exception like any other value and it can be handled
- the two modes can be switched on and off at various points in the code
- `io-handle`
- represents files (in read or write mode), network connections, and string buffers
- passed by _reference_ rather than by value (unlike all other slope types)
If the _optional_ gui module is installed, the following become available:
- `gui-root`
- The application root of a gui
- Holds all windows and is used as the reference point for many gui based procedures
- Passed by _value_ like most slope types
- `gui-container`
- an organizational structure used for laying out widgets
- does not specify the type of container, just that the value is a `gui-container`
- `gui-widget`
- the interface building block of gui applications
- does not specify the type of widget, just that the value is a `gui-widget`
There is also the concept/type `IOHandle`. This type cannot be cast to another (except string, but the output will likely not be useful for much beyond debugging), nor can it be entered manually. It is returned by things like `net-conn` and `file-open-read`. It is the general concept of something that can be read from and/or written to.
### Special Forms