Tiko Editor (with full FreeBasic Compiler) (v1.1.1 Updated 2025.07.07)

[PaulSquires]

We seem to be discussing two separate things at the same time (1) How to compile the Tiko Editor itself, and (2) How to create a new Project.

(1) Compile the Tiko Editor:
- You need to "Project / Open Project" and select the tiko.tiko project file.
- Earlier post you said that when you compile the tiko.exe it will not compile because it is trying to overwrite an already running tiko.exe instance. You need to do this:
- Select "Project / Project Options" and remove this "Other Options (64 bit Compiler)" "-x ..\tiko.exe"
- Now when you compile, the resulting tiko.exe will be placed in the /src folder, rather than the same folder as the existing tiko.exe.
- You can now exit the Tiko editor and copy the new tiko.exe from the /src folder to the parent folder overwriting your existing exe.

(2) Creating a New Project
- You do not need to manually edit project files. The editor automatically generates this file.
- Seems like you were trying to shoehorn the existing Tiko source files into a New Project. You can certainly do that but it makes little sense given that the tiko.tiko project already exists and you simply need to Open that project file rather than create a new one from scratch.
- However, if you decided to continue down the New Project route with the tiko source files, you would need to (1) create your new project (as you had already done); then (2) use "Project / Add files to project" to select all of the files in the /src folder (basically all of the *.inc, *.bi, *.rc files). (3) The selected files will load into the Project Explorer under the different categories: Main, Resource, Header, Normal. You should now be able to compile the Main file.

...but like I said earlier, the approach as outlined in #1 above is the path you should take.

[adeyblue]

There is not one word that you have mentioned above about projects covered in 'Tiko Editor Help'. Until that happens, nobody will get involved in Tiko projects. Perhaps adeyblue and his like, but there are very few of them.

Hey, I'm only here to occasionally post dubious music*, be a big meany to wet blankets and derail threads.

Apart from the time I jury rigged exceptions into the compiler, 670 lines is about the biggest FB thing I've ever written. No need for IDEs at that scale. Bog standard Notepad and command line.


* Seriously, who knew New Kids on the Block were still releasing new music and that they'd made the best pop song of the last few years. Features bonus Rick Astley waterboarding. The En Vogue bit is entireley pointless though, I will admit. If you get Talking Pictures TV in the depths of your TV EPG, watch The Heritage Chart Show. New music from artists you thought had long gone away, with videos made on a budget of about a fiver. It's brilliant/terrible

[PaulSquires]

Version 1.1.1 release: https://github.com/PaulSquires/tiko/release

Download the "Source code (zip)" file from the Release page (https://github.com/PaulSquires/tiko/releases), or directly via the following link:
https://github.com/PaulSquires/tiko/arc ... v1.1.1.zip

To install, simply unzip to a folder path that does not contain spaces. To uninstall, delete the folder. Tiko does not install any additional files elsewhere in your system nor does it store information in the Windows Registry.

It is safe to copy the files from this version release over your previous v1.1.0 release because the download does not contain a settings.ini or keybindings.ini file that would overwrite your existing files.

Version 1.1.1 (July 7, 2025)
- Added: Additional Build Configuration flags (-O1,2,3,s,fast and -eassert) to the flag entries in the configuration listbox.
- Added: French language translation from community member docroger.
- Changed: Substantial file management refactor. Reduce resource usage (especially font handles) by up to 400% for large projects.
- Changed: RunViaCommandWindow now defaults to false for new settings.ini.
- Changed: Silently switch to "Build and Execute" for "Quick Run" compiles on already saved source files.
- Changed: Beep only on compile errors only (no beep if only warnings).
- Changed: Pop open the Output window only if errors (no pop open if only warnings).
- Fixed: Output window minimize, restore, and close logic respecting user defined panel height.
- Fixed: Default config build description for "Win64 Static Library".
- Fixed: Saved several hFont gdi resources by using modified CWindow class.
- Fixed: Menu text and keyboard accelerator text possibly squishing into each other in the top menu.
- Fixed: Quick Run produced temporary .bat file now deleted in same manner as temp .exe file.
- Fixed: Prevent certain config file data from being hot reloaded (eg. SidePanel width and OutputPanel height).
- Fixed: Replace All not resetting displayed find count.
- Fixed: Parsing TYPE ALIAS's failed and caused incorrect parsing of remainder of the source file.
- Fixed: File/Rename would fail if trying to rename to an already existing file name.
- Fixed: Various refactoring and improvements too many to list.

[dodicat]

Thanks for fixing the quick run.
I am sure many members use it to build up and de-bug their programs .
It would be nice have an undo and redo (like fbide or the devcpp ide for example)
I see you have left a suitable gap between environment options and compile icons.
(Just a thought)

[Patrice Terrier]

Paul

I did try to compile a project, stored in another folder than Tiko (the project was dropped from the Explorer using drag & drop).

One of the Tools.bi used in my project is using
#include once "crt.bi"
#include once "inc\win\commctrl.bi"

But Tiko is unable to find the commctrl.bi what should I do to solve this?

[deltarho[1859]]

Hi Paul

I am going to have a rant.

Yesterday, you wrote a post with a section entitled 'Compile the Tiko Editor:'

Now when you compile, the resulting tiko.exe will be placed in the /src folder,

I followed your instructions and got tiko.exe in the /src folder. When I ran tiko.ece I got couldn't find certain files. You may say "Ah well, what you should have done is xyz". I don't to read what I should have done. You should have told me.

All my random number implementations have one thing in common: A 'Example Usage' section. I do not expect a reader to go through the Types looking at the procedures and parameters, if any. After running the example usage code and looking at the output, they are now an expert at the implementation without having to read its code.

I run the example usage code myself to make sure the implementation does what it is supposed to do.

If you follow your own instructions, you will find they don't work because you assume that we know how to fill in any gaps. Never ever make assumptions about a reader. Always write to the lowest common denominator. It is what I do when writing Help files. I never make assumptions about a reader's understanding of my software. They were not looking over my shoulder when I wrote it.

What I would like to see is a detailed example of creating a project step by step, missing no steps out, and tested by you to make sure the instructions actually work.

So let us see how to 'Compile the Tiko Editor:' in full.

If you do that, you may find a lot of users creating projects because as it stands a lot of users will simply give up on the idea, and you will have wasted your time developing the method.

Rant over.

[Arachnphilia]

Hello David

You are frustrated and are sharing your frustration with us.

Of course, it won't help you now if I tell you that I was able to compile the current editor after unpacking without errors.
The only thing I changed in the project settings was the entry -x ..\tiko.exe. I changed this entry to -x ..\tiko64.exe.

Since tiko.exe is already opened by me, the source code cannot otherwise be compiled and saved because tiko.exe is already open.

If I have the source code in a different directory, i.e. outside the Tiko Editor, I don't have to change anything in the project settings.

Creating a project also went smoothly.

I'm sure it's just a small thing to make it work for you too. I think you'll manage. You're an old fox.

I hope I have made myself clear.

[Arachnphilia]

Version 1.1.1 release: https://github.com/PaulSquires/tiko/release

Hi Paul
I thank you for the update.

[PaulSquires]

Yesterday, you wrote a post with a section entitled 'Compile the Tiko Editor:'

Now when you compile, the resulting tiko.exe will be placed in the /src folder,

I followed your instructions and got tiko.exe in the /src folder. When I ran tiko.ece I got couldn't find certain files. You may say "Ah well, what you should have done is xyz". I don't to read what I should have done. You should have told me.

Did you follow the very next instruction I gave (in bold below)?

- Now when you compile, the resulting tiko.exe will be placed in the /src folder, rather than the same folder as the existing tiko.exe.
- You can now exit the Tiko editor and copy the new tiko.exe from the /src folder to the parent folder overwriting your existing exe.

[Imortis]

Paul

I did try to compile a project, stored in another folder than Tiko (the project was dropped from the Explorer using drag & drop).

One of the Tools.bi used in my project is using
#include once "crt.bi"
#include once "inc\win\commctrl.bi"

But Tiko is unable to find the commctrl.bi what should I do to solve this?

Remove the "inc\" from the path. the compiler will always look in that folder unless you tell it otherwise. Having that in the patch makes it look in the path that the current source file is in and try to find a folder called "inc" there.

[PaulSquires]

What I would like to see is a detailed example of creating a project step by step, missing no steps out .....

Yes, I agree, documentation can certainly be a lot stronger and I will make sure going forward that I write it as simply as I can.
I will also break out the help documentation into multiple files so that I can have each file dedicated to a specific topic.
I loathe the Microsoft chm format so I will build on the current simple text file format.
As the editor matures I will also look at creating some tutorial videos because seeing something in use may make it more understandable than reading words on a page and trying to visualize it.

[zaphod]

Hello,

For compiling Tiko :
1 - In menu project -> OPEN PROJECT -> select file : tiko - Copy.tico
2 - Menu Project - > Project Options -> Other Options (64 bits compiler) -> change the content with :

-x ..\tikox64.exe

3 - Menu File -> Preferences -> Build Configuration -> Select : Win64 GUI Release - then F5 (build and execute)

Thats all : you have a second instance of Tiko running (wait a few second, big source to proceed).

Its very nice to study the code of the IDE, thanks Paul.

Have a nice day,
An old french user.

[srvaldez]

@zaphod

[dodicat]

The editor should accept the keyword at the cursor position and show the help for that keyword when F1 is pressed.(from the .chm file)
I know projects are popular, but I avoid them like the plague.
What's wrong with plain old source code files (singular or plural).
But of course it is only me, I don't even use code completion , If I want a character I prefer to write it myself.
So just ignore me everybody--carry on.

[deltarho[1859]]

Hi zaphod

I did 1. OK with that.

When it comes to 2. that requires editing a tiko profile.

WHAT?

@srvaldez
What did you do to comply with 2?