Recent Posts

Pages: [1] 2 3 ... 10
1
Applications / Re: Nomacs Image Viewer
« Last post by roberto on Today at 08:19:22 pm »
Hi Tellie,
When you left us the qt6 version, I installed it, and put the qt6core.dll in the same folder of the nomacs.
I ran it and it worked perfectly, and I looked at a lot of photos and a lot of folders.
But, days later I wanted to open it again and it closed, seconds after opening. With an error in exceptq.
Editing the profile, I saw a mega line of a length of approximately 1600 columns, created with the qt6
They were the paths of each photo.
With the epm I left the line at about 600 characters.
I tried on the QT5 version, and it worked perfectly.
I put it back with the QT6 version, and it still works perfectly.
My conclusion : To have a correct profile in Qt6, you first have to have it created in Qt5.
Saludos
2
Programming / Re: OpenDOC - Source Code
« Last post by Lars on Today at 07:44:12 pm »
1) the Warp4 Toolkit (NOT the Warp 4.5 toolkit) came with a whole OpenDoc subdirectory, including all documentation (in HTML format)
2) there existed OpenDoc Version 1.2, multiple self-extracting installation executables. It is likely the same stuff as is contained in:
http://www.hobbesarchive.com/Home/Download?path=/Hobbes/pub/os2/dev/tools/toolkits/OpenDoc_1-2.zip
and it can also be found here:
https://www.adofai.gg/HOBBES/dev/opendoc/

I have both on CD-ROM.
3
Programming / Re: libALSA?
« Last post by Mentore on Today at 10:11:26 am »
You will have to implement the audio yourself, e.g. you could use KAI.

I was thinking about something like that. BTW the emulator works perfectly, so I'll probably upload it without sound support.
Mentore
4
Programming / Re: libALSA?
« Last post by Jochen Schäfer on Today at 09:47:08 am »
You will have to implement the audio yourself, e.g. you could use KAI.
5
Programming / libALSA?
« Last post by Mentore on Today at 09:17:40 am »
Hello all,
I finally managed in setting up some projects on OS/2 - mainly focusing on emulatio.
As it seems, I have a QL Emulator under SDL/2 working - never happened before (there was UQLX but needed X11 and I never saw a working copy).

Now for the difficult part:
I'm working on a newer release of FBZX, a ZX Spectrum emulator I already ported before. It uses libpulse, OSS or libALSA for sound - and we don't have any of them.
As UNIAUD is based on ALSA, I'm wondering how difficult it may be to port libalsa under OS/2.
Thoughts, anyone? I'm pulling it from github right now.

Mentore
6
Programming / Re: OpenDOC - Source Code
« Last post by SoundChaser on Today at 04:20:15 am »
A fair chunk of the Taligent C++ coding style ended up in the Open Class framework in VAC++4 which unfortunately is too much an esoteric environment to work with. I wonder if anyone tried to compile these modules with another compiler than IBM xlc (say MSFT cl.exe) which would have given a second life to that otherwise very interesting tech.

The book Taligent's guide to designing programs : well-mannered object-oriented design in C++ remains an excellent book.
7
Programming / Re: Any standard on exit codes?
« Last post by Dave Yeo on Today at 01:26:36 am »
The "Control Programming Guide and Reference", installed by the toolkit as cp2.inf has a detailed list of error codes, about 64K different ones including reserved.
For GCC/Libc errors, see @unixroot/usr/include/sys/errno.h
8
Programming / Any standard on exit codes?
« Last post by Alfredo Fernández Díaz on Today at 12:54:24 am »
Hi everyone,
I am writing a few tools that can report a number of different conditions, e.g. "target file does not exist," "file can't be read," "wrong file type," "parameter out of range," etc. While well-chosen error messages are the best you can give users, when tools are to be chained, it is better to pass along different numeric return codes. Now the question is, in order to cooperate most properly, every tool must know at least the error codes of the previous one, so I wondered whether we have any kind of standard or guidelines regarding this, instead of having a plethora of necessarily arbitrary values.
Thank you in advance.
9
Programming / Re: OpenDOC - Source Code
« Last post by Sean Casey on Today at 12:26:15 am »
I recall speaking with Carla Hanzlik, Sundial Systems, regarding Taligent and OpenDoc's People, Places, and Things metaphor.  Sundial Systems had a lot of time invested in Taligent and it was believed Relish version 3 would incorporate its technology.   

A variety of interconnected remote users, collaborative work spaces, data and objects disbursed throughout a network. Developers would write helper components that operate on different types of data instead of writing full applications.  OpenDoc would be the common component interchange glue.  This would eliminate monolithic applications and software suites.  Essentially, someone can assemble their own software suite using individual components that are part of the operating environment.

I believe the OpenDoc framework was developed by an alliance with Apple, IBM, and Motorola to counter Microsoft's growing dominance.  HP also had some ownership and contributed IP.  While Apple was developing their own OS utilizing OpenDoc, IBM had planned to use the framework within its Workplace OS and planned a Taligent personality module.
10
Programming / Re: OpenDOC - Source Code
« Last post by Martin Iturbide on April 29, 2024, 11:52:59 pm »
Thanks for the feedback SoundChaser.
Pages: [1] 2 3 ... 10