Messages

1

Programming / Re: OpenDOC - Source Code

« on: April 30, 2024, 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.

2

Programming / Re: OpenDOC - Source Code

« on: April 29, 2024, 11:16:03 pm »

Also... should someone manage to build the runtime, these could be use to test the end result :-)

https://github.com/OS2World/DEV-SAMPLES-IBM_OpenDoc

3

Programming / Re: OpenDOC - Source Code

« on: April 29, 2024, 11:04:13 pm »

I think it was in Warp 4 original install media.

Indeed. I think it was in the selective install options?

The code in there remains really interesting for concerns outside of the OpenDoc context, however:

- we get to see excellent examples of clean Workplace Shell integration C++ code:
  https://github.com/atcurtis/OpenDoc/blob/main/os2/src/docshell/OS2Shell.cpp
- ... and its IDL counterpart
  https://github.com/atcurtis/OpenDoc/blob/main/os2/src/docshell/idl/OS2Shell.idl


There's an effing full bento format implementation:
   https://github.com/atcurtis/OpenDoc/tree/main/com/src/bento


What's the value? Well, some application formats relied on Bento, just as Microsoft file formats relied on OLE/COM Structured Storage format. Can be useful to inspect the structure of old archived media files from early Avid workstations, for example (http://justsolve.archiveteam.org/wiki/OMF_Interchange) although the data won't be immediately readable without reverse engineering yet for forensics and archeology, I can definitely see value there for many multimedia applications (Avid Symphony/Media Composer, ProTools...)

4

Programming / Re: ArcaOS - Recreate a complete build environment?

« on: April 10, 2024, 12:38:24 am »

This thread is immensely useful and a great complement (or replacement) to BitWise Works wiki page on how to build qt5 (https://github.com/bitwiseworks/qt5-os2/wiki/Developers#building-qt)

Considering there's an official developer page through EDM2, perhaps the very first article should be "how to get started", with this information? Also, should anyone have a script to automate some of this yak shaving setup, it could reduce the friction that many hobbyist developers have to face when approaching OS/2 development...

5

Applications / Re: Lost / Missing Software for OS/2

« on: February 20, 2024, 12:24:34 am »

Close but no cigar:

http://web.archive.org/web/19980419082437/http://nuts.ml.org/TopBar.html

Sadly, archive.org doesn't have the zip in store. Antony is still very much active. I have a feeling he would answer back promptly if reached out.

If you're lucky, he might have the source code on a zip drive or somethin' :-)


Trying to dig his second website, topbar was long gone - http://web.archive.org/web/*/http://cyberkinetica.homeunix.net/*

Hello

I'm trying to find:

1) TopBar
By Antony T. Curtis
Last known FileName: topbr036.zip

6

Applications / Re: OS/2 - Graphic User Interface - Desktop - Personal Experiences ?

« on: December 20, 2023, 02:01:59 am »

the one thing that annoys me the most is the way outdated font rendering. there were attempt to modernize that. I understand the PM and font IFF thing might be in the way. it's the #1 visual thing for me.

otherwise  the more we extend the WPS, the more likely we are to unstabilize it. food for thoughts.

7

Setup & Installation / Re: DOS VDM: WordStar-for-DOS 7c ("WS") and Borland Quattro Pro ("QP")

« on: November 29, 2023, 12:49:48 am »

Andrew, should the migration route to OpenOffice doesn't go smoothly and you need to bring the WS files to a newer format, you might want to consider converting them to WordPerfect format first. That format is well converted iirc.

8

Programming / Re: VisualAge C++ 3.0 editor

« on: September 16, 2023, 01:08:21 pm »

LXPMs should have a backward compat command line interface. I would try renaming one instance to, say, lxpm.old and have OS2 find the other executable through the PATH as first experiment if there's no configuration setting for it...

9

General Discussion / Re: when will version 5.1 of ArcaOS be released

« on: May 24, 2023, 02:31:12 am »

Apparently, beyond the distribution woes, it _is_ ready? ... such a tease!

10

Applications / Re: SSH - take the long way home

« on: January 16, 2023, 05:58:12 am »

Yeah I remembered one of my friend using putty with odin around 2001 or so... and decided to give it a shot :-)

I managed to have X11 forwarding to work. Due to the richness of today's GNOME, the experience is unbearable. Even adding compression doesn't help. Perhaps an X2Go client would do better.... seems that previously suggested xrdp a better route for remote desktop of that Unix box...

But disregarding the performance, the combo putty-on-Odin-with-X11 + Hoblink works.

11

Applications / Re: SSH - take the long way home

« on: January 16, 2023, 04:54:34 am »

I gave another shot at komh' s QPutty, and found the culprit from previous failures (on which I gave up really quickly, I must admit) - only an old subset of now-considered-insecure ciphers are available.

Back to square 1.

You know what? There's nothing like the original. Downloaded the win32 putty, 32-bit edition. After a bit of tinkering with puttygen to import my private key to putty's proprietary format (wtf, really) IT ACTUALLY WORKS.

Procedure:
- Download putty.exe
- Open an OS/2 Command Prompt
- Open putty through Odin with "pe putty.exe"

Confirmed to work:
- Window is resizeable \o/
- There are some quirks with the cursor (annoying, but I can live with them until qputty is refreshed)
- TUI apps such as Midnight Commander render just fine
- Fonts report negative font sizes for about every font except Courier New (perhaps for every bitmap except TrueType)

So here's my current compilation of the current state of things with SSH client for OS/2, existing and potential:

- Win32 Putty through ODIN - only known to work stable solution (well, it crashes on exit but I can live with that)
- Command line SSH from ANPM - give it a shot, it connects but it's not really usable.
- ZOC. doesn't work. It needs a refreshed SSL stack. Seriously, it's only useful for unencrypted
- QPutty - doesn't work with secure ciphers.
- PUTTY for Win32s - doesn't work, relies on Win32s 1.30 but open source... based on OpenWatcom infamous V2 branch - SSH for DOS - doesn't work, needs wattcp to be ported over to IBM TCP/IP for DOS
(probably easy to port to OW 1.9 and build to win32s 1.25)
- Kermit 95. Doesn't work, but it's now open source and modular. It could actually be interesting to (re-)port as it once supported OS/2.

12

Applications / Re: ssh - sshd

« on: January 10, 2023, 06:42:34 pm »

Thank you Sean for sharing your results!

13

Applications / Re: Software Wishlist for 2023

« on: January 09, 2023, 03:32:01 pm »

I'm using the 1.9 build, which iirc I downloaded from github using a link from BWW docs, but that I'm not sure anymore. I'll have to validate with my firefox download history... I agree with you on the fork, I bet their OS/2 build is broken.

Thanks for all the insights!

14

Applications / Re: HOBLink and ArcaOS

« on: January 08, 2023, 05:29:21 pm »

Successfully uninstalled previous AND successfully installed HOBLink ! I did not have a nagging screen and I have a minimized XSession running. It looks very promising!

Thank you Dave !

15

Applications / Re: Software Wishlist for 2023

« on: January 08, 2023, 03:51:22 pm »

Having the libcn in a lesser state than EMX is... well, as a developer I understand that there's so much to do and so little time, so applying YAGNI principle, if these calls were not required when the libs were leverage for a given port (say firefox), it's understandable they aren't at the same quality.

However, when it's time to port, what should be the target now? It should be libcn. But... I understand it can't be used for console apps? Nonsense.

Perhaps the priority of the development community (not putting the burden on one dev, but more in a collegial way - if we want to conquer the hill, we need a strategy) should be to give some love to that runtime while moving forward porting stuff. But where to start? Is what's missing documented at all, or is it the knowledge of a few devs?

Back to vim.  I'm using the OW version and it's pretty good. I was using it as a porting exercise, knowing that if I'd checkout the commit before the os2 support was removed, it _should_ build. It did. But as you confirmed, console appears broken in many ways. I wanted to port console apps, so unless the libcn is fixed I can't... and no problem to debug and eventually contribute to libcn, yet back to my original comments, the setup time is somewhat time-consuming and error-prone.

Still, I want to give credits to the folks at BWW who documented a lot. Now it needs to reach next level. One toolset for porting, one toolset for legacy (PM and DOS or win32s ports) and reduced friction setup for both. I'm probably oversimplifying, still I think a hobbyist purchasing ArcaOS should be able to code in less than an hour, that's not really the case right now.