Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Dave Yeo

Pages: 1 [2] 3 4 ... 356
16
Web applications / Re: Dooble releases, Qt5 builds
« on: April 10, 2025, 04:38:31 pm »
Hi Remy, both the "suppr" key problem and the shared memory problem will be QtWebEngine or other Qt lib based, probably QtWebEngine. Unluckily the webengine, basically Chromium, is huge and I don't know my way around it. Very hard to compile too.
With Dooble, both Qt5 and Qt6 are built from the exactly the same source code.

17
Web applications / Re: Dooble releases, Qt5 builds
« on: April 08, 2025, 04:29:57 pm »
The lates version from April 7th seems to be back to normal speed like the version from Feb 28.
Mike

Good to hear. Note that I've just been building the upstream changes.

18
Web applications / Re: Dooble releases, Qt5 builds
« on: April 07, 2025, 11:20:07 pm »
ftp://dry@ftp.os2voice.org/tmp/dooble-2025-04-06-Qt5.zip has some fixes.

Both recent builts (2025-04-05 and 20205-04-06) are defenitely slower than 2025-02-28 version on my TP X250.
I downgraded back to 2025-02-28 and now it is working smooth again.
Mike

Interesting. I also found it a bit slow but blamed my internet connection. Latest fixes from upstream seem to help. Some NLS fixes too, see release notes. ftp://dry@ftp.os2voice.org/tmp/dooble-2025-04-07-Qt5.zip
BTW, I deleted 2025-04-05 as it was broken with fixes applied to the latest by upstream.

19
Internet / Re: Dooble releases-Qt6
« on: April 07, 2025, 11:17:03 pm »
Latest fixes from upstream, mostly NLS related, see release notes. ftp://dry@ftp.os2voice.org/tmp/dooble-2025-04-07-Qt6.zip

20
Internet / Re: Dooble releases-Qt6
« on: April 06, 2025, 10:01:19 pm »
Seems to zero out the settings path right before creating the application and then figuring out the settings location and creating or loading the settings. I have a hard time following the logic

21
Internet / Re: Dooble releases-Qt6
« on: April 06, 2025, 08:15:32 pm »
Yea, I think the dooble_settings.db in root is a timing issue, created too early and in root then uses the one in %HOME%
Seems the dictionary environment variable has changed to QTWEBENGINE_DICTIONARIES_PATH. Has to be an absolute path and likely needs / as a directory separator. Mine is, QTWEBENGINE_DICTIONARIES_PATH=L:/qt6-6.2.x/bin/qtwebengine_dictionaries

23
Internet / Re: Dooble releases-Qt6
« on: April 06, 2025, 07:10:31 pm »
New release with fixes for the above, ftp://dry@ftp.os2voice.org/tmp/dooble-2025-04-06-Qt6.zip

24
Internet / Re: Dooble releases-Qt6
« on: April 06, 2025, 06:21:32 pm »
There's another issue. Running "dooble 2>&1 | tee dooble.log" I see,
Code: [Select]
[7699:1:0406/090046.608000:ERROR:system_network_context_manager.cpp(299)] Cannot
 use V8 Proxy resolver in single process mode.
[7699:1:0406/090046.634000:ERROR:system_network_context_manager.cpp(299)] Cannot
 use V8 Proxy resolver in single process mode.
script_state.h
isolate_ is not broken
script_state2.h
script_state.h
isolate_ is not broken
...
Code: [Select]
Release of profile requested but WebEnginePage still not deleted. Expect troubles !
script_state.h
isolate_ is not broken
script_state2.h

With the script_state stuff repeated a lot, like a 7MB log after a couple of sites.
Going to multi-process mode does get rid of the 7699:1:0406/090046.608000:ERROR:
Looking at https://github.com/textbrowser/dooble/issues/249 someone else also has the Release of profile warning, also where he gets,
Quote
.org.chromium.Chromium.xxxxx in my ~/.dooble/WebEnginePersistentStorage folder
I get them in %TMP%

25
Internet / Re: Dooble releases-Qt6
« on: April 06, 2025, 05:46:34 pm »
It's weird, I haven't had dooble_settings.db written to the root in a week or so. It seems to be the way things are initialized. Upstream changed the startup in main() which created this problem, so I reversed that patch. Now Dooble wouldn't start with this output,
Code: [Select]
QCoreApplication::arguments: Please instantiate the QApplication object first
QCoreApplication::arguments: Please instantiate the QApplication object first
QCoreApplication::applicationDirPath: Please instantiate the QApplication object first
QCoreApplication::applicationDirPath: Please instantiate the QApplication object first
QCoreApplication::applicationDirPath: Please instantiate the QApplication object first
qt.core.qobject.connect: QObject::connect(QGuiApplication, Unknown): invalid nullptr parameter

Which I fixed by undoing my reversed patch. Need to look more into the startup.
Edit: Same problem with both Qt6 and Qt5

26
Web applications / Re: Dooble releases, Qt5 builds
« on: April 06, 2025, 07:38:04 am »
I've uploaded ftp://dry@ftp.os2voice.org/tmp/dooble-2025-04-05-Qt5.zip it's sort of experimental, had to revert a change I made to avoid dooble_settings.db being written to the root of the drive that was active when dooble was launched. Something to watch for.
Fixes from upstream include fixing visited links on Qt6. See Help-->Release Notes.

27
Internet / Re: Dooble releases-Qt6
« on: April 06, 2025, 07:32:35 am »
I've uploaded ftp://dry@ftp.os2voice.org/tmp/dooble-2025-04-05-Qt6.zip it's sort of experimental, had to revert a change I made to avoid dooble_settings.db being written to the root of the drive that was active when dooble was launched. Something to watch for.
Fixes from upstream include fixing visited links on Qt6. See Help-->Release Notes.

28
Programming / Re: Brainstorm: OS/2 on a Different Kernel
« on: April 05, 2025, 02:44:39 am »
In a way ReactOS would be a better fit for a kernel then Linux. Otherwise extending WINE, which is not an emulator, might help a lot. The running OS/2 on NT does show it is possible to run our binaries on a different OS and WINE shows running Windows apps on Linux is doable. The WPS is perhaps too hard to run on Linux and maybe even NT.

On this case 2ine will be an interesting way to go, since it is like WINE but to interpret OS/2 and not Windows. But the issue with 2ine is that the developer tried to replace all possible functions with a cloned open alternative, which makes it a lot of developer work and this is why the project is incomplete (Like cloning all OS/2). What it may be interesting is to use 2ine to clone only the OS2KRNL and Driver$ only and use the IBM's OS/2 binaries for CMD, PM, SOM, WPS, to avoid cloning all OS/2, and find a way to boot the OS/2 desktop over a different kernel.

2ine could be merged into WINE. The reason I mention WINE is that we would need things like a DLL loader, a way to manage shared/private memory and various other things that Windows also does as they are cousins. Seems adapting the WINE DLL loader to load OS/2 DLL's would be simpler then writing one from scratch. Same with managing memory, seems to me that WINE must do memory management in a way similar to OS/2, which is different then Linux usually does and since much of the work has been done to load Win executables and DLL's, adapting would be easier once again then starting from scratch. File system emulation too, OS/2 and Windows expect a drive letter.

Quote
"Win-OS/2" runs virtualized / Interpreted on OS/2, right?, not emulated. It will be something like having "Warp-Linux VDM" sessions on Linux.

Regards

Yes, on X86, Win-OS2 mostly runs virtualized with parts like the mouse emulated by the OS/2 mouse system. The PowerPC OS/2 did emulate Win-OS2 and DOS.
I don't see why we'd need a Win-OS2. WINE runs most Windows binaries fine, there are also options like DOSBox-X that not only run Windows for Workgroups (3.11) but even Win9x.
Similar with DOS. We're not going to be able to run DOS on ring 2 on Linux and that is one big advantage of DOS on OS/2, can use DOS drivers and operate close to the hardware. Linux has DOSEmu and also DOSBox and such.

29
Internet / Re: otter-browser, Qt5 build
« on: March 30, 2025, 07:41:37 pm »
Hi Martin, wait a little bit while I try to update and build the latest.

Hmm, latest is crashing. Might be a while to figure out why so you might as well upload the version you packaged. Can always update later.
Actually first you should add a link to https://github.com/OtterBrowser/otter-browser where the source resides to otter-browser.txt. Guess I should fork that repository and keep better track of which commit I'm building from :)

30
Internet / Re: otter-browser, Qt5 build
« on: March 30, 2025, 07:23:35 pm »
Hi Martin, wait a little bit while I try to update and build the latest.

Pages: 1 [2] 3 4 ... 356