LiteXL for AmigaOS 4 released - Software News - News

Software News : LiteXL for AmigaOS 4 released

Posted by walkero on 2021/12/29 14:20:00 (1706 reads) News by the same author

The first public version of LiteXL editor just released. This is a lightweight text editor written in Lua and SDL, with features like Syntax Highlight, custom plugins, color themes etc. This is the first port based on the v1.16.12 source code of the program.

Lite XL is derived from lite. It is a lightweight text editor written mostly in Lua — it aims to provide something practical, pretty, small and fast easy to modify and extend, or to use without doing either.

The aim of Lite XL compared to lite is to be more user friendly, improve the quality of font rendering, and reduce CPU usage.

LiteXL for AmigaOS 4 is still experimental and there are some known issues, but it is quite usable. It is recommended to use it on a fast AmigaOne, although it was tested on microAmiga1 and works pretty good, but slow.

Please, read the enclosed README_OS4.md file before run it.

You can download the firsts public version from https://git.walkero.gr/walkero/lite-xl/releases

The comments are owned by the author. We aren't responsible for their content.

Author	Thread
kas1e	Published: 2021/12/29 15:04 Updated: 2021/12/29 15:04
Home away from home Joined: 09/11/2007 From: Russia Comments: 9130	liteXL Wow, it runs! More of it work pretty fine. The only 2 things i miss right from the start: clicking on an open file gadget didn't bring us ASL requester. And the scrollbar is pretty "tiny" and almost invisbly. if those parts can be replaced on reaction/mui ones that will be very nice! But app is good!

root	Published: 2021/12/30 13:13 Updated: 2021/12/30 13:13
Just popping in Joined: 12/17/2008 From: Berlin, Germany Comments: 29	Re: liteXL imagodespira has do some little improvements for Lite XL https://os4welt.de/viewtopic.php?p=43162#p43162 `Path: LiteXL/data/core/style.lua Line 6: style.scrollbar_size = common.round(4 * SCALE)` BTW NICE PORT!

PEB	Published: 2021/12/30 22:04 Updated: 2021/12/30 22:04
Not too shy to talk Joined: 11/29/2006 From: Comments: 474	Thanks for the Port! Thanks for bringing OS4 a new editor for us to play with. It works pretty well for an early release. I think CodeBench provides the most complete, feature-rich editor for coding, and it basically satisfies all my wants. However, your Lite XL editor does have one nice feature that is missing in CodeBench, namely, UTF-8 support. Ever since Hollywood added UTF-8 support, I've been wanting an editor on Amiga that would also support it. I'm sure I'll always use CodeBench for big projects, but Lite XL (if it matures a bit more) would be a really nice alternative for small projects.

redfox	Published: 2021/12/31 5:07 Updated: 2021/12/31 5:07
Quite a regular Joined: 03/15/2008 From: Canada Comments: 555	Re: LiteXL for AmigaOS 4 released Thanks walkero.

walkero	Published: 2021/12/31 12:25 Updated: 2021/12/31 12:25
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	v1.16.12.4 released Thank you guys for testing LiteXL. I am glad it works for you so well. A new version is released with a fix on the Gfx memory leak. You can download it at https://git.walkero.gr/walkero/lite-xl/releases/tag/v1.16.12.4 @PEB LiteXL is not intended to be an alternative to Codebench in any way. Codebench is one of the best IDEs that are available in our OS. I wish we will see a new release soon with bug fixes and faster scrolling.

TSK	Published: 2021/12/31 18:20 Updated: 2021/12/31 18:20
Just can't stay away Joined: 02/23/2007 From: Finland, the land of Santa, sauna, sisu and salmiakki Comments: 1210	Re: v1.16.12.4 released UTF8 support somebody said. I couldn't enter any scandinavian characters at all (a Ducky keyboard).

PEB	Published: 2021/12/31 23:42 Updated: 2021/12/31 23:42
Not too shy to talk Joined: 11/29/2006 From: Comments: 474	Re: v1.16.12.4 released When resizing the window I get this message: Quote: assertion "w_pixels % w_points == 0 && h_pixels % h_points == 0 && w_pixels / w_points == h_pixels / h_points" failed: file "src/renwindow.c", line 12 (Sometimes it crashes after displaying that message, and sometimes it doesn't.)

walkero	Published: 2022/1/1 14:18 Updated: 2022/1/1 14:18
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: v1.16.12.4 released @PEB On which computer this is happening? I know this is the case with Tabor and possible it's an issue with the lack of FPU and Lua.

PEB	Published: 2022/1/1 18:07 Updated: 2022/1/1 18:07
Not too shy to talk Joined: 11/29/2006 From: Comments: 474	Re: v1.16.12.4 released SAM460

virgola	Published: 2022/1/1 18:19 Updated: 2022/1/1 18:19
Just popping in Joined: 02/01/2007 From: Bergamo, Italy Comments: 122	Re: v1.16.12.4 released Same here, I must reboot every time I resize the window. I use a Sam460ex with OS 4.1 Final Release Update 2 and Enhancer 2.1 with a Radeon HD 6670.

walkero	Published: 2022/1/2 13:07 Updated: 2022/1/2 13:07
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: v1.16.12.4 released Thank you guys. It will be the next thing to take a look and try to fix. I think I know why this is happening.

walkero	Published: 2022/1/2 19:09 Updated: 2022/1/2 19:09
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: v1.16.12.4 released Just to let you all know, all the known issues I have so far are available at https://git.walkero.gr/walkero/lite-xl/issues These are the ones that I am going to work on. If you have anything that I forgot to include, please contact me.

walkero	Published: 2022/1/2 19:41 Updated: 2022/1/2 19:41
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: v1.16.12.4 released @PEB Can you please check if you have at GUI Prefs the "Resize with window contents" checked? Does it happening if you uncheck it?

virgola	Published: 2022/1/2 23:18 Updated: 2022/1/2 23:18
Just popping in Joined: 02/01/2007 From: Bergamo, Italy Comments: 122	Re: v1.16.12.4 released Disabling "Resize with window contents" allows me to resize the window just fine. After re-enabling it, the system continue to crash.

walkero	Published: 2022/1/2 23:26 Updated: 2022/1/2 23:26
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: v1.16.12.4 released @virgola Thank you so much for your comment. I have a fixed version ready. I will release it as soon as possible.

PEB	Published: 2022/1/3 0:09 Updated: 2022/1/3 0:09
Not too shy to talk Joined: 11/29/2006 From: Comments: 474	Re: v1.16.12.4 released Same here. (Disabling "Resize with window contents" gets rid of the error.)

walkero	Published: 2022/1/3 1:07 Updated: 2022/1/3 1:07
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: v1.16.12.4 released I just released v1.16.12.5 with a fix for the resize and two other bugs. Check this out at https://git.walkero.gr/walkero/lite-xl/releases/tag/v1.16.12.5 and please tell me if it works fine even with "Resize with contents" enabled. Thank you guys for your help and for the testing.

PEB	Published: 2022/1/3 7:09 Updated: 2022/1/3 7:09
Not too shy to talk Joined: 11/29/2006 From: Comments: 474	Re: v1.16.12.4 released I'm getting this error now: Quote: Error: Work:LiteXL/data/core/init.lua:862: bad argument #2 to 'format' (string expected, got nil) stack traceback: [C]: in function 'format' Work:LiteXL/data/core/init.lua:862: in function (...tail calls...) Work:LiteXL/data/core/init.lua:540: in function 'init' [string "local core..."]:11: in function [C]: in function 'xpcall' [string "local core..."]:2: in main chunk

mdr	Published: 2022/1/3 9:46 Updated: 2022/1/3 11:16
Just popping in Joined: 03/19/2019 From: United Kingdom Comments: 21	Re: v1.16.12.4 released Same here. X5000, OS 4.1FE Update 2. Update: Previous version works fine though. Also wanted to say a massive thanks for your work on this, I've been following your progress and it's an awesome addition to my OS4 development environment. Been giving it a try with my setcmd project as I port it to 68k, and I'm really enjoying using it even in this early state. Fantastic work!

walkero	Published: 2022/1/3 13:05 Updated: 2022/1/3 13:05
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: v1.16.12.5 released Sorry to hear that. Have you replaced all the files with tha new ones, even the data folder? Have you tried to delete/rename the .config folder before you start LiteXL, so that a new one is created? I am trying to reproduce it here on any machine and I can't really get that error.

kas1e	Published: 2022/1/3 13:39 Updated: 2022/1/3 13:41
Home away from home Joined: 09/11/2007 From: Russia Comments: 9130	problem @George Same for me on x5000. just downloaded v1.16.12.5, unpacked to ram, and db-cliсk by mouse, and has that: "An internal error occurred in a critical part of the application. Plrease verefy the file "error.txt" n the idrectory RAM Dis:iteXL/.confg/lte-xl" and then in the shell the same error as for others ps. That bug with comments on amigans.net is still here: for first it's an unformatted mess, then need to press edit, and choose "Auto wrap lines", and only then formattng are fine.

walkero	Published: 2022/1/3 15:01 Updated: 2022/1/3 15:03
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: problem Ok... managed to reproduce it when I extracted the app at Ram disk. Wait for a fix as soon as possible. Thank you guys for the report... issue created at https://git.walkero.gr/walkero/lite-xl/issues/13

walkero	Published: 2022/1/4 13:12 Updated: 2022/1/4 13:12
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: problem A new version that fixes that issue is released at https://git.walkero.gr/walkero/lite-xl/releases/tag/v1.16.12.6 Thank you all for testing LiteXL.

kas1e	Published: 2022/1/4 19:28 Updated: 2022/1/4 19:28
Home away from home Joined: 09/11/2007 From: Russia Comments: 9130	test @george Yeah works now. Through noted now that scrolling is pretty slow. if I open README.md grab the scrollbar and try to move the page then it really slow and unresponsive :( Even pure move by mouse wheel takes 100% CPU loading.

kas1e	Published: 2022/1/4 19:30 Updated: 2022/1/4 19:30
Home away from home Joined: 09/11/2007 From: Russia Comments: 9130	compostng @george is it SDL2? So compositing in use already?

walkero	Published: 2022/1/4 20:48 Updated: 2022/1/4 20:48
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: compostng @kas1e Yeah, it is SDL2. I get the CPU to 100% on my system as well, but I wouldn't say that it is unresponsive. It depends of course what else are you running at the same time.

PEB	Published: 2022/1/4 21:49 Updated: 2022/1/4 21:49
Not too shy to talk Joined: 11/29/2006 From: Comments: 474	Re: scrolling speed Would using Warp3DNova be an option to speed things up?

virgola	Published: 2022/1/4 22:33 Updated: 2022/1/4 22:33
Just popping in Joined: 02/01/2007 From: Bergamo, Italy Comments: 122	Re: problem You did it, the windows of LiteXL can now be resized correctly with v1.16.12.6 Thank you! The editor on my Sam460ex seems to be quite heavy to manage, a bit sluggish and slow, sometimes it freezes for a split second (e.g. when selected chunk of text with the mouse), but it works.

khayoz	Published: 2022/1/4 23:14 Updated: 2022/1/4 23:14
Not too shy to talk Joined: 01/10/2007 From: Stockholm Sweden Comments: 444	Re: v1.16.12.4 released @walkero Thank you for this, it looks great!

Capehill	Published: 2022/1/5 8:27 Updated: 2022/1/5 8:42
Just can't stay away Joined: 07/14/2007 From: Lothric Comments: 1732	Re: compostng @walkero 1) Could you try to request VSYNC when calling SDL_CreateRenderer: https://wiki.libsdl.org/SDL_RendererFlags It should be also possible to set VSYNC with: setenv SDL_RENDER_VSYNC 1 # Enable setenv SDL_RENDER_VSYNC 0 # Disable and then (re)start the app. 2) Is liblua build compiled with -O2/3?

walkero	Published: 2022/1/5 11:54 Updated: 2022/1/5 11:54
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: compostng @all Thank you for your kind words. Remember, this is my first port of an application that uses SDL. I am sure there are ways to optimize it. This is a learning journey for me as well. So, if you have any recommendations, feel free to tell me so. @capehill Quote: Could you try to request VSYNC when calling SDL_CreateRenderer I will try it and see if it makes any difference. Quote: 2) Is liblua build compiled with -O2/3? I have to check this out as well. I am not sure, to be honest. Good point.

walkero	Published: 2022/1/5 12:42 Updated: 2022/1/5 12:42
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: compostng @capehill Quote: 1) Could you try to request VSYNC when calling SDL_CreateRenderer: https://wiki.libsdl.org/SDL_RendererFlags I tried both SDL_RENDERER_ACCELERATED and SDL_RENDERER_PRESENTVSYNC and for sure it works better, without the CPU reaching 100%. I need to test how it works on my A1222 and microAmiga1 and see if it fails or not. If I am not wrong both of them are able to be set in ENV variables, right? In case someone would to test it on his system. At https://wiki.libsdl.org/SDL_RendererFlags there is the following mention Quote: Note that providing no flags gives priority to available SDL_RENDERER_ACCELERATED renderers. Is this the case with the AmigaOS 4 version or not? Quote: 2) Is liblua build compiled with -O2/3? It is compiled with -O2. I will compile it again with -O3 and see if it makes any difference.

Capehill	Published: 2022/1/5 13:23 Updated: 2022/1/5 13:23
Just can't stay away Joined: 07/14/2007 From: Lothric Comments: 1732	Re: compostng @walkero User may try to override the default renderer by: setenv SDL_RENDER_DRIVER "software" ; Might be good for WinUAE, no need for CompositePatch setenv SDL_RENDER_DRIVER "compositing" setenv SDL_RENDER_DRIVER "opengl" setenv SDL_RENDER_DRIVER "opengles2" So technically one can try Warp3DNova by choosing "opengles2". But I don't think it matters. Texture upload from RAM to VRAM will be done by the CPU in anyway when there is no DMA support. How about X1000 users, don't they have the DMA? Quote: Is this the case with the AmigaOS 4 version or not? Yes, it should be. I think compositing comes first.

walkero	Published: 2022/1/5 13:46 Updated: 2022/1/5 13:46
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: compostng @capehill In your opinion, it is safe to leave SDL_RENDERER_ACCELERATED there? Do you believe there are going to be issues with any kind of hardware? If I get it right, and please correct me, that's the default anyway, so it wouldn't make any serious problems, right?

Capehill	Published: 2022/1/5 15:56 Updated: 2022/1/5 15:56
Just can't stay away Joined: 07/14/2007 From: Lothric Comments: 1732	Re: compostng Quote: In your opinion, it is safe to leave SDL_RENDERER_ACCELERATED there? Do you believe there are going to be issues with any kind of hardware? Should be safe but also unnecessary. I think WinUAE users will get a blank window if they don't run PatchCompositeTags, or force SW rendering using setenv, but that's normal. By the way, here is the logic: https://github.com/AmigaPorts/SDL/blob ... /render/SDL_render.c#L819 If there is no hint then flag match is used.

walkero	Published: 2022/1/5 16:23 Updated: 2022/1/5 16:23
Site Builder Joined: 12/02/2006 From: Athens/Dublin Comments: 1836	Re: compostng What I do not know is, if I set the flag as SDL_RENDERER_ACCELERATED \| SDL_RENDERER_PRESENTVSYNC, is it possible to override them from ENV variables, if necessary? Or should I leave it as it is and if someone would like to enable VSync to do it using ENV variables? Sorry if I ask the same things again and again, but I am not familiar with SDL

Capehill	Published: 2022/1/5 17:42 Updated: 2022/1/5 17:42
Just can't stay away Joined: 07/14/2007 From: Lothric Comments: 1732	Re: compostng @walkero Yes, overriding both VSYNC and render driver should be still possible because these are checked before trying to match the flags. You can test it, try requesting SDL_RENDERER_ACCELERATED \| SDL_RENDERER_PRESENTVSYNC from code but then force VSYNC off with: setenv SDL_RENDER_VSYNC 0 Perhaps you can notice difference in the CPU load?