Messages

1

Programming / Re: Qt6 Application Testing

« on: Today at 07:14:54 am »

Remy's cmd seems to work fairly well, on the 2nd try youtube works as expected for a while then the UI gets kind of stuck needing to close Dooble.

2

Programming / Re: Qt6 Application Testing

« on: Today at 02:32:57 am »

Might be an idea to try rebuilding FFmpeg with --disable-avx --disable-avx2 --disable-avx512 --disable-avx512icl.
I find the newer GCC's are way to quick to enable AVX, though if targetting old CPU's, it shouldn't be a problem.

3

Programming / Re: Qt6 Application Testing

« on: September 06, 2024, 07:41:16 am »

Are you running out of memory on these builds? When I built the Qt5 webengine, I had to periodically reboot to defrag the memory.
Even with Mozilla, just building SeaMonkey to test a patch and got,

Code: [Select]

25:53.50 cc1plus.exe: out of memory allocating 65536 bytes after a total of 0 bytes
With a popup with a sys0147 which blocked until I allowed it to kill the program (cc1plus.exe I think)

Code: [Select]

SYS0147: Not enough resources are available to process this command.
The process for which this pop-up is displayed will end.

EXPLANATION: All available memory is in use.  If segment swapping is
active, the swap file may be full.

ACTION: Do one of the following and retry the command:
o  Reduce the number of running programs.
o  Reduce the value of the BUFFERS=, TRACEBUF=, DISKCACHE=, THREADS=,
   RMSIZE=, or DEVICE=VDISK.SYS statement in the CONFIG.SYS file and
   restart the system.
o  Remove unwanted files from the swap file disk and restart the system.
o  Install additional memory on your system.
o  Contact the supplier of the application.

An error with its roots in 16bit land.

Now the VIO window I was building in is frozen so have to reboot eventually to continue on.

4

Setup & Installation / Re: How to get rid of the second boot menue?

« on: September 04, 2024, 10:09:00 pm »

Add the drive letter as an option? My rEFInd menu entry for AOS 5.1 on drive M:

Code: [Select]

# This is an entry for ArcaOS 5.1 in UEFI mode
menuentry ArcaOS-5.1 {
    icon \EFI\refind\icons\os_aos.png
    loader \EFI\OS2\OS2LDR.EFI
    options "M:"
}



5

General Discussion / Re: Re: Do we still need a 64-bit version of OS/2? And a possible roadmap provided ...

« on: September 02, 2024, 07:11:43 pm »

You might want to test with only one cpu enabled. Add /MAXCPU=1 to the PSD=ACPI.PSD line in config.sys.
As for LibreOffice, one of the first things they did when they forked from OpenOffice was remove the OS/2 stuff and since then so much development has happened that re-adding it would be very hard. Even building OpenOffice is next to impossible without the right environment which I understand only one person has.

6

Programming / Re: Qt6 Application Testing

« on: September 01, 2024, 06:07:59 am »

Can't you do things like win32|os2 to follow that path on win32 or os2?

I was wondering the same, will test.

And yes, that works fine.

7

Programming / Re: Qt6 Application Testing

« on: September 01, 2024, 03:03:53 am »

Can't you do things like win32|os2 to follow that path on win32 or os2?

I was wondering the same, will test.

8

General Discussion / Re: Re: Do we still need a 64-bit version of OS/2? And a possible roadmap provided ...

« on: August 31, 2024, 07:10:55 pm »

The MDOS(WinOS2) subsystem in OS/2 is not an emulator, but actual PC-DOS 5 running in ring2. Not quite bare metal but closer then most user programs that run in ring3. You can actually load and run most DOS device drivers with some such as disk, mouse and keyboard getting trapped by the kernel and replaced by the OS/2 driver. So DOS programs can run on HPFS and JFS but you can't easily do something like supporting long file names.
The hardware itself has changed enough that DOS applications just don't run as well as they used to do.

9

Programming / Re: Qt6 Application Testing

« on: August 30, 2024, 08:38:35 am »

Cmake install is used to package things. I'll take a look at the scripts - it's possible there are different install paths depending on platform...

Good point, I simply replaced win32 with os2 as a quick hack.
Looking at dooble.pro (basically at the beginning), the main differences seem to be between libexec and libexec/qt6 or in the case of win32, being on the PATH depending on platform. Seems no support for building them on Qt5.

10

Internet / Re: Dooble releases-Qt6

« on: August 30, 2024, 07:07:24 am »

Hi Pete, Hunspell uses the myspell dictionaries and I believe most have hunspell installed, Firefox and Thunderbird require it, SeaMonkey I accidentally used the intree version and then decided to leave it that way.
Anyways the ones I posted are likely more up to date and already converted.

11

Programming / Re: Qt6 Application Testing

« on: August 30, 2024, 06:20:28 am »

Hi Paul, I fixed dooble.pro to process the dictionary files, make failed as it expected qwebengine_convert_dict to be in qt6-6.2.x\libexec instead of bin. I notice that Qt5 puts it in @unixroot/usr/lib/qt5/bin along with a lot of other Qt5 exe's.
Is that how your build left it or are you manually installing?

12

Internet / Re: Dooble releases-Qt6

« on: August 30, 2024, 12:29:55 am »

They're the same as the Qt5 dictionaries. To get the ones Paul pointed to means doing a git clone. Easier to get the ones in @unixroot\usr\share\myspell. Either way they need to be converted with qwebengine_convert_dict.exe, either the one in @unixroot\usr\lib\qt5\bin or x:\qt6-6.2.x\bin. See my previous post.
I'd post the dictionaries directory, but zipped it is 35MB's. If you need an individual one, ask.
Actually here's my dictionaries, various en, now removed
Edit: figured out how to automatically create the dictionaries during build, so here's the ones I think we would like to have.

13

Internet / Re: Dooble releases-Qt6

« on: August 29, 2024, 07:34:05 am »

Here's the commit that broke finding the dictionaries when installed as qtwebengine_dictionaries as a child directory under the directory where the dooble binary resides.
I can't quickly see the problem, have to sleep on it. I do notice that dooble.sh, the Linux wrapper script has  various export QTWEBENGINE_DICTIONARIES_PATH= added. Perhaps we should just do similar rather then getting further from upstream by reverting this commit or otherwise changing things.

Code: [Select]

From 02958934b6771efdebbb9dfdc8d77e3d7018c2c2 Mon Sep 17 00:00:00 2001
From: textbrowser <textbrowser@gmail.com>
Date: Fri, 26 Apr 2024 18:35:35 -0400
Subject: [PATCH] Improved error messages.

---
 Source/dooble_settings.cc | 22 ++++++++++++++--------
 dooble.sh                 |  4 ++++
 2 files changed, 18 insertions(+), 8 deletions(-)

diff --git a/Source/dooble_settings.cc b/Source/dooble_settings.cc
index a84e9f76..0ff17f49 100644
--- a/Source/dooble_settings.cc
+++ b/Source/dooble_settings.cc
@@ -2304,21 +2304,22 @@ void dooble_settings::show_panel(dooble_settings::Panels panel)
 
 void dooble_settings::show_qtwebengine_dictionaries_warning_label(void)
 {
-  m_ui.qtwebengine_dictionaries_warning_label->setText
-    (tr("<b>Warning!</b> "
- "The directory qtwebengine_dictionaries cannot be accessed. "
- "Dooble searched QTWEBENGINE_DICTIONARIES_PATH and the relative "
- "qtwebengine_dictionaries directories. "
- "Please read %1, line %2.").arg(__FILE__).arg(__LINE__));
   m_ui.qtwebengine_dictionaries_warning_label->setVisible(false);
 
   auto bytes(qgetenv("QTWEBENGINE_DICTIONARIES_PATH"));
 
   if(bytes.trimmed().isEmpty())
     {
-      bytes = "qtwebengine_dictionaries";
+      auto directory
+ (QDir::currentPath() + QDir::separator() + "qtwebengine_dictionaries");
 
-      if(!QFileInfo(bytes).isReadable())
+      m_ui.qtwebengine_dictionaries_warning_label->setText
+ (tr("<b>Warning!</b> "
+     "The directory qtwebengine_dictionaries cannot be accessed. "
+     "Dooble searched %1. Please read %2, line %3.").
+ arg(directory).arg(__FILE__).arg(__LINE__));
+
+      if(!QFileInfo(directory).isReadable())
  {
    m_ui.qtwebengine_dictionaries_warning_label->setVisible(true);
    return;
@@ -2326,6 +2327,11 @@ void dooble_settings::show_qtwebengine_dictionaries_warning_label(void)
     }
   else if(!QFileInfo(bytes).isReadable())
     {
+      m_ui.qtwebengine_dictionaries_warning_label->setText
+ (tr("<b>Warning!</b> "
+     "The directory qtwebengine_dictionaries cannot be accessed. "
+     "Dooble searched %1. Please read %2, line %3.").
+ arg(bytes.constData()).arg(__FILE__).arg(__LINE__));
       m_ui.qtwebengine_dictionaries_warning_label->setVisible(true);
       return;
     }
diff --git a/dooble.sh b/dooble.sh
index dd7f8d02..ac5d06a8 100755
--- a/dooble.sh
+++ b/dooble.sh
@@ -28,6 +28,7 @@ export QT_X11_NO_MITSHM=1
 if [ -r ./Dooble ] && [ -x ./Dooble ]
 then
     echo "Launching a local Dooble."
+    export QTWEBENGINE_DICTIONARIES_PATH=qtwebengine_dictionaries
 
     if [ -r ./Lib ]
     then
@@ -46,6 +47,7 @@ then
     echo "Launching an official Dooble."
     export DOOBLE_TRANSLATIONS_PATH=/opt/dooble/Translations
     export LD_LIBRARY_PATH=/opt/dooble/Lib
+    export QTWEBENGINE_DICTIONARIES_PATH=/opt/dooble/qtwebengine_dictionaries
     export QT_PLUGIN_PATH=/opt/dooble/plugins
     cd /opt/dooble && exec ./Dooble "$@"
     exit $?
@@ -54,6 +56,8 @@ then
     echo "Launching an official Dooble."
     export DOOBLE_TRANSLATIONS_PATH=/usr/local/dooble/Translations
     export LD_LIBRARY_PATH=/usr/local/dooble/Lib
+    export QTWEBENGINE_DICTIONARIES_PATH=/usr/local/dooble/\
+    qtwebengine_dictionaries
     export QT_PLUGIN_PATH=/usr/local/dooble/plugins
     cd /usr/local/dooble && exec ./Dooble "$@"
     exit $?
--
2.30.2


14

Applications / Re: Any way to increase mouse tracking speed other than the regular System applet?

« on: August 29, 2024, 01:45:36 am »

Try using AMouse, there's an older version on Hobbesarchive which says it runs on Warp. http://hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/system/drivers/mouse/Amouse_2-80.wpi.

15

Internet / Re: Dooble releases-Qt6

« on: August 28, 2024, 05:57:13 pm »

About UA (User Agent) detection. A lot of sites seem to have crappy UA detection. Ideally they shouldn't even care about the UA, rather detecting browser features and adjusting the page or rejecting the browser based on the detection.
Instead they seem to detect the browser, compare to a list and fail when a browser or Operating System appears that is not in the list. I monitor the SeaMonkey newsgroup and UA's often come up. Which version of Firefox to advertise in SeaMonkey's UA, whether to mention Firefox are common topics. They've even added, in about:settings, the capability to vary the UA depending on site.
I still use SeaMonkey mostly and have the UA switcher extension installed. There are sites where I actually use the Dooble UA string to get the page to display the page.
Basically, using uncommon browsers breaks the UA detection on too many pages, so have to change the UA