Tiko - beta tests

[Paul Squires]

Hi everyone,

I know that some of you try the latest Tiko versions via the github "development" branch. I can inform you that the branch now contains the latest most feature complete version. I do not intend to add any more major features, so the work that remains is testing and tweaking the program before the new version is released.

https://github.com/PaulSquires/tiko/tree/development

You just need to "Download ZIP" and extract to your hard drive preferably to a location without spaces in the folder names.

DO NOT INSTALL THIS OVER YOUR EXISTING TIKO INSTALLATION

NOTE: It is a large download because it contains the full Help Centre html files, plus Tiko help html files, plus FBC toolchain. The actual Tiko Editor and DLL's are pretty small in comparison.

It is best if you unzip the program into a folder path that does not contain any spaces.

Please post here any major issues that you find so that I can polish things up before Tiko goes out for general release.

Thanks

[Paul Squires]

No major reports in the 3 days that this beta has been active.
I am taking that as a positive sign.   

@José Roca if you have tried this beta then I would be interested to know if the dialog and font sizes are okay on your computer/laptop. This beta's dialogs and fonts are larger than in the most recent released version. I remember that you had trouble with the long height of top menus a version or two ago, so I expect that screen real estate is important for you.

[hajubu]

Hi Paul,

Thanks for beta-Test phase - works fine -and here my remarks

a) Screen display on old Laptop 1366x768 :full sized windows: settings pop-up uses app.80% , Fonts resized to 10

b) Big 27inch  - need only to be resized à gusto : visual acuity : sizing and local position

c) Observing a "crash" ::
   Starting the Tiko out-of-the box , loading a test file and try to compile:
   ==> error ( warning  pop-up --> cannot not find compiler path
          Then it stops like a "crash" without further option for adapting new settings-
         (... logically this might correct, but new user not knowing the background may be scared.)
   
    Background : out-of-the-box  path setting may be (are) not known and may be different from mine .
   Tiko ought to be able to find it's way i.e.  "default path" in the "Toolchains" below  the own path.
 
P.S.     My ideas are  ::
 ::@(b) :: Output windows for Big Screen :: option for display in a "side panel"
 ::@(c) ::  an stop-over on the settings page for that choice.

b.r. (Hajubu) Hans

[Paul Squires]

Excellent, thanks Hans, appreciate it 

[hajubu]

Hi, just tried the new "UString" with fbc-win (1.20?) under the Toolchains within Tiko-beta.

How can we add the additional compiler with the help of the Settings options (Ctrl + ,).
I do know to add them manually in the settings.ini ( that worked).

Testing this with  Tiko132 - it does offer to set the alternatives with the options (Shift + F7) as it find the new folder under the "Toolchains" by itself.

It would be a great support you could check the possibilities.

Thanks Hans (Hajubu)

[Paul Squires]

Hi Hans,

I tried doing so myself and the new toolchain did not show up under the list of available toolchains. Turns out there was a bug in the new PsListTree control that scrolled the first item off the top of the list (which happened to be that new toolchain). it's fixed now but not in the development branch because I am doing other major work off a feature sub-branch from development that I don't want to disturb.

To make things easier for you, I have attached the new tiko.exe with the fix included.

Just add the whole \fbc-win folder from the USTRING repo to the \toolchains folder off of Tiko. I renamed my new toolchain to fbc-win-USTRING so that I would know for sure what that toolchain does.
 

[hajubu]

thanks , Paul

I'm trying a little the USTRING, but I'm struggling withe visualization.
The character used in the showcase "ustring_usage_test_owl.bas" U+1D11E is not visible in TIKO.
The emoji OWL can be visualized as it show below.

I added/changes from the Musical Clef values to the values for OWL. )inclusive for the surrogate pair (hi,lo)
All 146 test running fine for both , but not the visibility for the clef.

Also the compiler log files do not show the symbol, which may by nature of the fbc.
Your TODO/NOTES TAB Panels show the OWL with the emoji for the black & white symbols.
The Musical Clef sees , do not have an equivilant (?).

b.r. Hans

Code Select Expand

'#define ASTRAL wchr(&h1D11E)      ''  surrogates( hi:0xD834, lo:0xDD1E ) i.e. |𝄞|   U+1D11E MUSICAL SYMBOL G CLEF)
'#define ASTRAL wchr(&h1F989)       '' surrogates ( hi:0xD83E, lo:0xDD89 ) i.e. |🦉| U+1F989 OWL



[Paul Squires]

The OWL produces the following error output:

USTRING usage showcase

FAIL m[1] is the HIGH surrogate got= 55358 want= 55348
FAIL m[2] is the LOW surrogate got= 56713 want= 56606
FAIL units recombine to U+1D11E got= 129417 want= 119070

 142 checks, 3 failed

I'll post a fix/explanation as soon as I can.

[Paul Squires]

The problem is not the compiler, but rather the test code itself. The #DEFINE set at the top of the code has hardcoded values later in the test suite based on that value. Changing that value from a clef to an owl did not (obviously) change the hardcoded HI/LO values later in the test.

Use the attached test code file (in the zip) until I can update the Github repository.

[hajubu]

Thanks, Paul.

Yes , I had edited the "OWL" for all the necessary entries  manually.
therefore the results are the same , as what you did with the adapted defines and surrogates

Therefore my observation , said before, can be also confirmed with your edition.
a) The CLef-symbols IS NOT visualized in TIKO Editor : OWL is Visible as it should
b) FBC log text does not display the UNICODE symbols (by nature).
c) TODO/NOTES show a equivalent  of the OWL in Black & White only

b.r. Hans

P.S: I'll try to understand the reason behind - then I'll will be back.

[José Roca]

@José Roca if you have tried this beta then I would be interested to know if the dialog and font sizes are okay on your computer/laptop.

No. I guess there are "Ok" and "Cancel" buttons, but they aren't visible.

[Paul Squires]

Thanks José,

As I feared, the larger font and spacing was too much. The OK, CANCEL don't fit on the dialog based on your display.

[José Roca]

It is not a problem of the size of the font, but of the space between lines. Like writing with Word using 1.5 between lines. The same problem that happened with the menus in an early version.

[Paul Squires]

It is not a problem of the size of the font, but of the space between lines. Like writing with Word using 1.5 between lines. The same problem that happened with the menus in an early version.

Yes, I kind of figured it would result in the same issue as the top menu problem we dealt with. I'll get it all fixed up.

[José Roca]

Be aware that HD monitors are wide, but not very tall.