IUP_FB_EDITOR (simple development environment)
-
- Posts: 65
- Joined: Jul 01, 2021 7:53
Re: IUP_FB_EDITOR (simple development environment)
These keywords are for highlighting of Yabasic keywords on IUP_FB_EDITOR
https://pastebin.com/5gS6NKB2
https://pastebin.com/5gS6NKB2
-
- Posts: 65
- Joined: Jul 01, 2021 7:53
Re: IUP_FB_EDITOR (simple development environment)
From my research it seems the Scintilla keywords doesn't allowed to have $ and # on their names, one exception is when # is at beginning of the word. This is why some keywords just don't get highlighted.
Updated keywords files for QB64:
keywords0: https://pastebin.com/qxncn2NV
keywords1: https://pastebin.com/UP6rmmtM
keywords2: https://pastebin.com/tesFcvs3
keywords3: https://pastebin.com/EWt2SRB8
Updated keywords files for Yabasic:
https://pastebin.com/B6M7VgnK
Updated keywords files for QB64:
keywords0: https://pastebin.com/qxncn2NV
keywords1: https://pastebin.com/UP6rmmtM
keywords2: https://pastebin.com/tesFcvs3
keywords3: https://pastebin.com/EWt2SRB8
Updated keywords files for Yabasic:
https://pastebin.com/B6M7VgnK
-
- Posts: 65
- Joined: Jul 01, 2021 7:53
Re: IUP_FB_EDITOR (simple development environment)
Hi. Your IDE only needs libiup.so and libiup_scintilla.so. I copied them into fbnp's directory and run fbnp with this:
LD_LIBRARY_PATH=. ./fbnp
It worked. The reason for LD_LIBRARY_PATH is Linux doesn't search the current directory for libraries like Windows.
LD_LIBRARY_PATH=. ./fbnp
It worked. The reason for LD_LIBRARY_PATH is Linux doesn't search the current directory for libraries like Windows.
-
- Posts: 232
- Joined: Apr 10, 2010 11:41
- Location: Japan
- Contact:
Re: IUP_FB_EDITOR (simple development environment)
Dear VANYA;
Thanks for your continuous development of IUP_FB_EDITOR.
And thank you for adding exact Japanese translations of newly added items.
By the way, I have two questions, please let me know.
1. How to use "Convert document in the encoding on the fly"
What is this function intended to convert a file with what character code content to what character code?
I tried some files and got following errors:
Problem with conversion. Function iconv_open returned handle is invalid.
There is no way to convert to a given encoding. The editor may try to convert to 1 out of 120 possible encodings. To Begin?
2. How to set up Parser
The following is written in the help file.
> on Windows with the same settings, but with a file size of 3,500 lines, there are already brakes when moving the cursor.
Sure, it is difficult to move lines on 3,500 lines.
Please let us know which parameter should be set in which direction (larger or smaller).
Thanks for your continuous development of IUP_FB_EDITOR.
And thank you for adding exact Japanese translations of newly added items.
By the way, I have two questions, please let me know.
1. How to use "Convert document in the encoding on the fly"
What is this function intended to convert a file with what character code content to what character code?
I tried some files and got following errors:
Problem with conversion. Function iconv_open returned handle is invalid.
There is no way to convert to a given encoding. The editor may try to convert to 1 out of 120 possible encodings. To Begin?
2. How to set up Parser
The following is written in the help file.
> on Windows with the same settings, but with a file size of 3,500 lines, there are already brakes when moving the cursor.
Sure, it is difficult to move lines on 3,500 lines.
Please let us know which parameter should be set in which direction (larger or smaller).
Re: IUP_FB_EDITOR (simple development environment)
Hi Makoto WATANABE!
This function makes it possible to change the characters of 2 half of the ASCII table in the editor without saving the original file. You can mix characters of different encodings. Despite the fact that in the source code, the characters will be displayed by krakozyabram, in the final program everything will be displayed and work correctly. In this case, you do not need to use the specific winapi functions (for converting text). For example, you pasted the source code from the Internet, but the characters are displayed in krakozyabra:
In general, the more numbers in the widgets highlighted in red, the longer it takes to launch the main parser after the last keystroke. If the key was pressed before the expiration of the timer, the timer starts counting again and thus the work of the parser is postponed. The larger the number in the blue highlighted widget, the longer it takes for the mini parser to start (it always works, even if you disable the main parser) and the more time it takes to enter text and less time to run the parser. Everything is selected individually, depending on the performance of the computer and the speed of text printing.
This is a very specific feature. I don't think it is applicable on Japanese windows. The fact is that in the 90s several Russian encodings were developed (Cp866, KOI8-R, CP1251). For example, so far in the console, the encoding is Cp866, and when working with files and GUIs, it is CP1251. That is, if the file is saved in Cp866 encoding, then everything will be displayed correctly in the console, but you will not be able to use functions for working with files (open, put # ...).Makoto WATANABE wrote:1. How to use "Convert document in the encoding on the fly"
This function makes it possible to change the characters of 2 half of the ASCII table in the editor without saving the original file. You can mix characters of different encodings. Despite the fact that in the source code, the characters will be displayed by krakozyabram, in the final program everything will be displayed and work correctly. In this case, you do not need to use the specific winapi functions (for converting text). For example, you pasted the source code from the Internet, but the characters are displayed in krakozyabra:
If you have the default encoding Cp1251 and you convert to UTF-8 on the fly, you get the Russian word:привет
Browsers often distort text if the HTML page does not contain an indication of the encoding inside it.привет
Makoto WATANABE wrote:2. How to set up Parser
In general, the more numbers in the widgets highlighted in red, the longer it takes to launch the main parser after the last keystroke. If the key was pressed before the expiration of the timer, the timer starts counting again and thus the work of the parser is postponed. The larger the number in the blue highlighted widget, the longer it takes for the mini parser to start (it always works, even if you disable the main parser) and the more time it takes to enter text and less time to run the parser. Everything is selected individually, depending on the performance of the computer and the speed of text printing.
Re: IUP_FB_EDITOR (simple development environment)
Hi all!
Editor update:
1) Added poseidonOutline plugin by Kuan Xsu (thanks)
2) Changed how the help files work.
--------- a) The editor now uses * .CHM files on all operating systems.
--------- b) Search for a keyword (when pressing F1) is now done in all the help that you connect.
Editor update:
1) Added poseidonOutline plugin by Kuan Xsu (thanks)
2) Changed how the help files work.
--------- a) The editor now uses * .CHM files on all operating systems.
--------- b) Search for a keyword (when pressing F1) is now done in all the help that you connect.
Re: IUP_FB_EDITOR (simple development environment)
Update. Error fixed.
Re: IUP_FB_EDITOR (simple development environment)
Update archives:
1) A version for IUP+GTK3 (64-bit) is now available for linux
2) An attempt was made to fix the menu display problem on some Linux systems. For example, in OpenSuse, the menu bumped into the toolbar. Hopefully this is now fixed.
1) A version for IUP+GTK3 (64-bit) is now available for linux
2) An attempt was made to fix the menu display problem on some Linux systems. For example, in OpenSuse, the menu bumped into the toolbar. Hopefully this is now fixed.
Re: IUP_FB_EDITOR (simple development environment)
Update:
1) fixed bugs
2) add warning in the compile-time output window. Now, when the compilation is performed, the inscription is displayed: Wait, compilation in progress...
1) fixed bugs
2) add warning in the compile-time output window. Now, when the compilation is performed, the inscription is displayed: Wait, compilation in progress...
Re: IUP_FB_EDITOR (simple development environment)
Update, fixed bug.
Re: IUP_FB_EDITOR (simple development environment)
Update: minor improvement for find
Re: IUP_FB_EDITOR (simple development environment)
Update:
fix bug on the windows version , related with encoding.
fix bug on the windows version , related with encoding.
Re: IUP_FB_EDITOR (simple development environment)
Update:
1) Parser now reads global variables from other tabs
2) When autocompletion, type fields are no longer sorted, but displayed in natural order
2) Correction of the error related to the encoding of the project
1) Parser now reads global variables from other tabs
2) When autocompletion, type fields are no longer sorted, but displayed in natural order
2) Correction of the error related to the encoding of the project
Re: IUP_FB_EDITOR (simple development environment)
Update:
Non-critical bug fixed.
Non-critical bug fixed.
Re: IUP_FB_EDITOR (simple development environment)
Update:
1) Added highlighting for cpp,asm,rc,none
2) Disabled saving in the register for non-FB files
3) Fixed creation of files in the project that are in subfolders (now folders are created automatically based on the file name)
4) Files cpp, asm, rc, txt are automatically recognized when opened and highlighted
5) When renaming files and displaying a message, now the focus returns to the desired dialog
6) When deleting a file from the project (if it is physically no longer on the disk), CRASH occurred, now this is fixed
7) The project file could be corrupted if it was created with the ending 13+10
Fixed the error of going beyond the array in the repository of the resource files of the project
1) Added highlighting for cpp,asm,rc,none
2) Disabled saving in the register for non-FB files
3) Fixed creation of files in the project that are in subfolders (now folders are created automatically based on the file name)
4) Files cpp, asm, rc, txt are automatically recognized when opened and highlighted
5) When renaming files and displaying a message, now the focus returns to the desired dialog
6) When deleting a file from the project (if it is physically no longer on the disk), CRASH occurred, now this is fixed
7) The project file could be corrupted if it was created with the ending 13+10
Fixed the error of going beyond the array in the repository of the resource files of the project