emporiumgugl.blogg.se - Best slack client windows

#Best slack client windows full
#Best slack client windows windows 10
#Best slack client windows software
#Best slack client windows code
#Best slack client windows windows

If you are going to program for Windows (3.1), buy this book. I purchased this book Programming Windows 3.1 by Charles Petzold from Amazon. Basically Windows 3.1, its API documentation and problems can’t be Googled easily, one has to rely on a more traditional method like books! Reference Book Typically, programmers will rely quite heavily on Google and Stackoverflow.Īlas, Win 3.1 only came during the dawn of the internet era and Google cannot help if relevant websites do not even exist.

#Best slack client windows software

API DocumentationĪPI documentation and usage examples are very important when it comes to software development. I had to wade through many issues which I detail the following key ones.

That’s many orders of magnitude smaller then the modern Slack app on the App store :P Let’s get down to the coding businessĬoding an ancient app presents some very unique challenges not seen when using modern toolchains and programming languages. That’s actually the first time I saw the network drive icon in File Manager. With Win 2K VM configured to use a bridged network and thus the same subnet, my native WFW 3.11 system can access the SMB share folder of the Win 2K VM as seen above. I can do intermediate testing on Win 2K since it can run 16-bit apps. VC++ 1.52 will access the source files using a mapped drive on SMB share and do the compilation.

#Best slack client windows code

Primary development is done on the Mac with Visual Studio Code editor with the files residing on the Mac file system.

#Best slack client windows windows 10

Windows 10 and Mac cannot directly talk to the ancient SMB protocol used by WFW 3.11. We need to occasionally test our app on the actual ancient hardware with WFW 3.11 during development.Īlso, we can’t write our code directly on the Windows 2000 VM as it has limited software support for modern IDEs like Visual Studio Code not to mention security issues. Testing a 16-bit program on a 32-bit OS VM is not a very realistic scenario as VMs can be too perfect.

Compatible with both Windows 10/Mac and Windows 3.1 SMB file sharing.

Lightest resource usage with smallest disk footprint.

No product activation unlike its successor Windows XP.

#Best slack client windows full

Oldest Windows OS with full Virtualbox support of drivers, network and bidirectional clipboard.

So I had to take the Virtual Machine option using Windows 2000 with the following considerations in mind. Theoretically it should run even on Windows 10 32-bit but I did not have such a native setup lying around. VC++ 1.52 is itself a 16-bit program so it can only be run on 32-bit Windows. This is the last VC++ compiler from Microsoft that can target for WFW 3.11. Everything has to revolve around it and this project is no exception.įor this, we have the Visual C++ 1.52. The most important aspect of developing an app is the compiler toolchain. Windows 3.1 also largely consumes 16-bit apps which is the tail-end of that era before Windows 95 came in. Nevertheless, as you will see, the effort to put in to write such an app is still herculean in its own right.

Therefore, if one wants to write an app using Windows OS standard APIs, WFW 3.11 is the oldest one can go back without putting in even more exponential effort. Or to be more precise, why Windows For Workgroups (WFW) 3.11? There is a special reason for this, WFW 3.11 released in 1993 is the first Windows OS for consumers to have network installable TCP/IP support. If you are too lazy to continue reading and want to dive into code, here is the repository on Github. On the right is my Mac with the Slack client for verification. Left is my Thinkpad 390e running Windows 3.1. This blog post is a few months late as I needed time to clean up the code and write the documentation.ĭon’t forget to checkout out Part 2 of the game app with Hui Jing too! The App And perhaps what lessons can it offer us today. We would develop a small game for Win 3.1 with great help from the knowledge gained from this first project.įor Part 1, I shall detail the learnings and process for how a new old app can be created with the aid of modern tools and hindsight of old technologies. After all, Slack clients exist for most platforms but I’m certain one does not exist for Windows 3.1.Ī few months later in Dec 2019, I would join the Super Silly Hackathon for the second time with fellow retrocomputing enthusiast Hui Jing. My colleague Subhransu and I worked on a whacky idea of writing a brand-new Windows 3.1 app which was an OS released almost 30 years ago. In October 2019, my company SP Digital held an internal hackathon.