snprintf() may not be C89, but fgets() sure is.
Building a new Windows 3.1 app in 2019: A Slack Client
21–30 of 248 posts
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#22Aaw cheating with https. I wonder if an embeddable library like BearSSL would be hard to get working.
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#23This presents c89 as the most antiquated thing in the world, but VS didn't support mixed declarations and code in a .c file until 2015. There is still a lot of code out there that avoids this to be able to work with MS's compilers.
[deleted]
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#24I built a Win 3.1 app during a company hackathon just for fun. Here, I detail learnings and process for how a new old app can be created with the aid of modern tools and hindsight of old technologies. And perhaps what lessons can it offer us today. Without the benefit of modern libraries and languages, I had to read up and take care of many low level details, socket programming, HTTP, JSON parsing, UI design in code…
I expected to be compiled in some kind of VM, not on an actual computer with Windows 3.11 :-).
I feel "old-style" documentation is much better than we have now. My most productive _python_ only work times were when I had only the python .hlp file and a _physical_ paper book.
What are your impressions?
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#25Related: winevdm makes running 16-bit apps on 64-bit Windows possible: https://github.com/otya128/winevdm
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#26Nice, Would have been a lot using with Visual Basic 4, but I guess easy wasn't the point.
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#27This is a lot of work to avoid using that WYSIWYG editor.
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#28I built a Win 3.1 app during a company hackathon just for fun. Here, I detail learnings and process for how a new old app can be created with the aid of modern tools and hindsight of old technologies. And perhaps what lessons can it offer us today. Without the benefit of modern libraries and languages, I had to read up and take care of many low level details, socket programming, HTTP, JSON parsing, UI design in code…
Prior to online search engines there were similar offline resources such as the MSDN CDs.
[deleted]
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#29I built a Win 3.1 app during a company hackathon just for fun. Here, I detail learnings and process for how a new old app can be created with the aid of modern tools and hindsight of old technologies. And perhaps what lessons can it offer us today. Without the benefit of modern libraries and languages, I had to read up and take care of many low level details, socket programming, HTTP, JSON parsing, UI design in code…
If you happen to end up in those environments again, I would appreciate it if you take a look at my prototype web-based message board.
It's designed for compatibility, and I've tested a lot of Netscapes and IE4, but nothing on Win311 yet.
If you want to leave a comment, you can do so right on the message board. It should work, more likely with JS off.
Re: Building a new Windows 3.1 app in 2019: A Slack Client
#30Earlier quoted context omitted.
Prior to online search engines there were similar offline resources such as the MSDN CDs.
Agreed. But such CDs are tough to locate today.
Borland's compilers had the best documentation. They included a much of the MSDN API reference in their built-in help files.