garlic3 / Blog: Recent posts

Easy entry of data; The fields for the explanation of the database fields that you created react on enter or return button to save the text.
Also when you click on the old value, it will be copied in the field new value, and cursor is set there.

new in Examples : DistributedButtons

Made as test for an application with a touchscreen.

How to distribute buttons all over the screen? Use of VBox with HBoxes:

Given number of buttons / row
Given total number of buttons to display

Quit button.

• Fixed source code name discrepantion between screens and source.
• Fixed source code calling procedures syntax errors
• Reset the current filename choice (also in settings)

So, current state:
- a little bit usable to generate settings/config screen code and form code.
- quite usable to view a gambas3 config file (except you cannot "choose" the file, but have to give the name (what is usually just the project name, that's probably ok).
- nice to quickly create a settings file with some documentation in it :-)... read more

0.8, 0.9:
Main screen: tab added to load an existing settings file to view.
Main screen: tab added to load an existing settings file to edit and save.
So now you can choose in a file-open style the settings file you want to view. If you need to edit it, you can do so in the next edit tab.

Caution: direct editing these files (and making small syntax errors in it) might prevent an app from starting, and/or keep it from functioning in a normal way, and make it crash if it uses the corrupted settings somewhere.

Le Portel combines the steps 3.1.37 -.38 -.39 -.40
Mainly completing the creation of getters/setters code from class properties code.
The form is called External because the features have nothing to do with the database, and also work without database connection.

3.1.37 : This offline use is now anticipated on at startup.
3.1.38 : Getters and setters code can now be done separate or combined
3.1.39 : MCode sets comments and Error feedback
3.1.40 :
- Option to prepare some validation code in setter (MCode/FExternal)
- The created sourcecode for getters and/or setters is selected and copied to clipboard.

Form External lets you paste declarations from a class, and create code for getters and setters when method is private (setter if not const).
Select in grid what declarations to work on. Somewhat limited to most used types.
Has nothing to do with the database, but does approximately the same as for the fields of the dbtable.

New in Templates: a library to (compile in ~/.local/share/gambas3/lib/vendor) properties, Librarie, Add..)
- get Error formated with errorcount, date/time stamp
- log error to textfile
Class CError provides setError, LogToFile, getPreviousError, getVersion

Finds source directory now :-)
Improved source text compilation to .txt with index and better titles
(e.g. for import in 2 column small text template in Open/LibreOffice document to print)

3.1.27 FKeyValue: gets fixed value "keyval" in datatype field, gets origin selected from combobox. Create new works now.
This is a small trick to store some values in the configuration table; e.g. you need a limited list of colors as a choice somewhere;
_dd_helpdata records can be made with datatype="keyval" and origin= "myappcolor" (to select all records for the colors) and name as description for the user, and defaultval with the value to use to produce the color.... read more

3.1.25
Fixed bugs:
use of {} with code generation of parameters in SQL statement.
3.1.45
crash on no keyval

** 3.1.23**
Add the possibility to add/edit keys - values in dd_helpdata table with datatype "keyval", Form FKeyValue
Logo added
Bug fixed: db not selected
Bug fixed INC in MCode

With one press of a button (well, rather one choice from the menu), you create the structure of a dd table in the selected database. There you can store the explanation of the fields used, example text, and default value (as text). You can use these from your application on the moment you have to make an edit form for the data; you can retrieve the explanation for a mouseover Help text, you can fill the default, and you can provide examples to the user.
From the DbInfoCode application, you can fill values in this "dd" table, even before your application is ready to the point that you need it there (e.g. no edit form yet). So this "metadata" can still change without impact on your app, or even better, as result of the evolution of your app.
Once the "dd" table created, you get the existing dd data about a field on the moment that you select a fieldname (after database selection, table selection of course).
Pre-release, bug fixes follow from feedback on this feature.

I must confess that the postgresql integration is not yet there, made a start though, help welcome.
Multiple dataset with drop-down box seems to work somewhat, might need bugfixes.
What works for me is that I can switch between two datasets on my laptop (both locahost, one is mysql other is postgresql - but see note above on the use).
Purpose of this change is switching is between development on localhost an production on remote host.
All settings kept in regular gambas settings file.... read more

Just converted the Gambas2 version of/to ProbableCause (3.0.1).
Also improved a bit. Can check my Gambas3 projects for unused variables, procedures etc with tables on screen or a report on screen or sent to kwrite.

When I noticed I couldn't run DBinfocode for Gambas2 anymore, it was time to convert it to Gambas3.

The first part is somewhat finished:

• Connect to a database (login password are saved for easy re-connection)
• see the existing databases and tables (depending on your rights of course)
• Use kind of template with standarised id and update metadata fields to create a new initialised table.
• Not only create an initialisation for the table, but also give extra fields at creation.... read more

I missed the WaveGenerator example in recent Gambas3 versions, so I made my own based on it.
What it does: use sliders to adapt sound volume and frequency, use radiobuttons to choose waveform or noise.
Actually a 0.0.1 version, but for gambas 3, that's why 3.x

0.0.5
- first version of default settings file that can be used with the generated code; has somewhat 10 fields now.

0.0.4
- Menu added
- FLoadText to load and show readonly text files like About/ Changes.txt / etc
- Help added with 2 screenshots
- Table grows with input now (instead of being limited to 20)
- group-key value is copied for easy entry if same value.

The tool can read the table from the saved file now.
This means you can fill the table, save the table, generate code from it, use that code in your project.
After a while you might need more settings. You start the settings tool, load the saved table, add the needed settings, and generate the code again.

have fun.
(+ feedback welcome of course)

0.0.2
- save the table data in a file.
(later: load from..)

0.0.1
- enter settings in a table on screen.
- generate code of it in a tab with textfield.
- write the text as file to a choosen directory
This gives you code to use in your gambas project
(given you make the right form, planning to make template later on. It has to contain txlbSettings1, 2 ... and txbxSettings1, 2 ... )
- the code can save each setting, load all settings, and init the textlabels.... read more

Garlic3 started to keep code for Gambas3 apart from Gambas2 code in original garlic project.

New Gambas3 project will end up here. Gambas2 projects from garlic might be "translated" to gambas3, but not for sure...

We start with a tool to generate gambas source code for the FSettings that you might need in almost any application: a form with all the application-settings that you want to store locally.
You make a form with text asking for a certain setting in a field, accompanied from a button to save it.... read more