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 11, 2025, 04:44:23 pm »
Code: [Select]
highmem -u \qt6-6.2.x\lib\*.dllShould undo the marking. Shouldn't need to reboot either if nothing is using the DLL's.
Perhaps jsut try marking Qt6WebEn.dll at first.

17
Web applications / Re: Dooble releases, Qt5 builds
« on: April 10, 2025, 11:34:09 pm »
Hi Matt, the simplest way is to start out with one of the RPM builds such as ftp://dry@ftp.os2voice.org/rpm/dooble-2024.11.23-1.oc00.pentium4.rpm and then replace dooble.exe with the one in the zip file. You can use ANPM to install the RPM. Manage-->Yum Tools-->Install Package from File.
What FTP client are you using? With SeaMonkey or Firefox, the URL should work, when it asks for a password, enter your email.
For other FTP clients, you may have to go to ftp.os2voice.org. log in as dry and enter your email address as password, then navigate to the right directory. How you log in will vary on client. Anonymous log in will take you to the regular os2voice ftp site.
Sorry for no recent RPM builds, something broke here and I haven't chased it down.

18
You need to set some environment parameters. Run emxomfld with no parameters to see,
Code: [Select]
Environment variables:
  EMXOMFLD_TYPE:
    The type of linker we're using. Values: WLINK, VAC365, VAC308, LINK386.
        WLINK    wlink.exe from Open Watcom v1.5 or later.
        VAC365   ilink.exe from IBM C and C++ Compilers for OS/2 v3.6 or later.
        VAC308   ilink.exe from Visual Age for C++ v3.08.
        LINK386  link386 form OS/2 install or DDK.
  EMXOMFLD_LINKER:
    Name of the linker to use and optionally extra parameters. Spaces in the
    linker name or path is not supported. Quotes are not supported either.
The default values for these two variables are VAC365 and ilink.exe.
  EMXOMFLD_RC_TYPE:
    The type of resource compiler we're using. Values: RC,WRC.
        RC       rc.exe as shipped with OS/2 or found in the Toolkit
        WRC      wrc.exe from Open Watcom v1.6 or later.
  EMXOMFLD_RC:
    Name of the resource compiler to use and optionally extra parameters.
    Spaces or quotes in the name or path are not supported.
The default values for these two variables are RC and rc.exe.

So, I use something like,
Code: [Select]
set EMXOMFLD_TYPE=WLINK
set EMXOMFLD_LINKER=wl.exe

Might need the full path to wl.exe

19
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: April 10, 2025, 04:49:23 pm »
About the email client. We actually have a bug that breaks Oauth2, which causes the login problems. Often, like I do with Gmail you can use an app password. Not sure about Yahoo, but even following the SeaMonkey list, outlook is weird, slightly different way of doing Oauth2 and various servers where only some work.
May be app passwords available for both.
Here's the instructions for Gmail, https://support.google.com/mail/answer/185833?hl=en

As for LibreOffice, one of the first things they did when they forked from OpenOffice was rip out all the OS/2 code and since a lot of development has happened there. It would be a huge job and we don't really have anyone working on OpenOffice. Would be nice if OpenOffice was back porting some of the stuff from LibreOffice but there's no volunteers.

20
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.

21
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.

22
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.

23
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

24
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

25
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

27
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

28
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%

29
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

30
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.

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