News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

Idea for new sub-forum

Started by NoCforMe, November 19, 2023, 11:14:56 AM

Previous topic - Next topic

NoCforMe

How about a subforum here that focuses on Win32? Questions and answers about the Win32 APIs. Seems like a lot of members here (maybe the majority?) use that platform. I'm finding that a lot of my programming issues have little to do with MASM or assembly language in general and instead concern using Windows.

What do you think? I think it's a good idea, but as always am willing to be convinced otherwise.
Assembly language programming should be fun. That's why I do it.

stoo23

Well, that is certainly possible and am More than happy to create such a Sub-Forum, if there is support for it.

Where or under what Forum Section do you envisage it being created ??

jj2007

#2
The idea is valid. Today, most of the Win32 stuff appears in the Campus or in the Workshop.

What about a sub-forum of the Workshop? We could move the current Windows.inc project under the Workshop, and rename it to Windows API.

I would agree to that, provided I am allowed to show off a little bit with my dedicated IDE :greensml:


NoCforMe

Quote from: jj2007 on November 19, 2023, 12:37:42 PMI would agree to that, provided I am allowed to show off a little bit with my dedicated IDE :greensml:
By all means. Since it uses Win32, it's fair game.
Assembly language programming should be fun. That's why I do it.

NoCforMe

Quote from: jj2007 on November 19, 2023, 12:37:42 PMWhat about a sub-forum of the Workshop? We could move the current Windows.inc project under the Workshop, and rename it to Windows API.
Hmmm; not dead-set against that, but since windows.inc is a separate ongoing project (and one that I have some things to say about), how about making it a sub-sub forum, under the new Win32 one? Would that be burying it too deeply?

Where is that forum anyhow? I couldn't find it. And JJ, that link you posted is apparently to something on your D: drive.
Assembly language programming should be fun. That's why I do it.

stoo23

The Windows.inc Board is already a Sub-Board of the MASM32 Board in the 'Projects' section:
https://masm32.com/board/index.php?board=22.0

Technically there is NO issue with there being a Sub-Sub Forum per se but may perhaps be an issue (as you suggest), with it being Buried too deep ??

NB: I've 'fixed' jj's incorrect 'link'  :thumbsup:

Vortex

QuoteThe Windows.inc Board is already a Sub-Board of the MASM32 Board in the 'Projects' section:
https://masm32.com/board/index.php?board=22.0

Stewart is right, no need to move \ rename the Windows.inc project.

jj2007

The point is that the current Windows.inc board has nothing to do with a "Windows.inc project".

Have a look, it's mostly Win32 discussion. A misnamer.

stoo23

Well, perhaps the 'Content' of the Windows.inc Board, could be reviewed and the Win32 specific stuff Moved into the New Win32 Board, leaving the Windows.inc stuff IN the Windows,inc board, thereby making Both Cleaner and suitably More specific to Both !!??

If that is a suitable suggestion, then IS the current Windows.inc Board in an appropriate and suitable place in the overall Forum and (once again), Where should the New 'Win32' board be created?

Should the Two have anything to do with each other ??

jj2007

Splitting and moving is a good idea. My preferred place for the "Windows.inc project" would be the Masm64 subforum (the Masm64 SDK is in urgent need of a correct and complete Windows.inc).

The Win32 content of the current "project" should move to a Windows API subforum of the Workshop. It's not Campus stuff, and the Lab should be reserved for fast Assembly algos.

My 2cts :cool:

stoo23

OK, let me know about 'Moving' the 'Windows.inc' Sub Board, (if in fact it Should be Moved).

I will create the 'Windows API' Sub Board,.. all I need from you guys is the Desired/Suitable 'Description' for it.

NB: New 'Windows API' Sub Board created.
https://masm32.com/board/index.php?board=68.0

jj2007

Quote from: jj2007 on November 19, 2023, 09:04:46 PMThe point is that the current Windows.inc board has nothing to do with a "Windows.inc project".

Have a look, it's mostly Win32 discussion. A misnamer.

Yesterday I checked again, and to my surprise I was wrong: all posts relate to problems with the include files, so it's not a misnamer.

Fact is there are lots of posts specialised in Windows API programming. They are spread all over the place, often in the Campus and mostly in the Workshop.

Moving future posts into the new Windows API subforum is feasible, but what should be the criteria?

Pure algos without API calls are somewhat rare, and they have their place in the Laboratory.

Those with API calls are mostly found in the Workshop or, if at a basic level, in the Campus.

I'm a bit lost re the need for a separate Windows API forum and would like to see the views of other members :thup:

NoCforMe

I think it's definitely appropriate to have the (newly created) Win32 forum.

I don't think we have to agonize about which existing posts (say in the Campus but moreso the Workshop & Laboratory) to move there; we can let some sleeping dogs lie. But if some topic is obviously more about the workings of Win32 than just assembly-language programming, then you might consider moving it. (I know I have some topics there that fall in that category.)
Assembly language programming should be fun. That's why I do it.

NoCforMe

Quote from: stoo23 on November 19, 2023, 10:29:43 PM.. all I need from you guys is the Desired/Suitable 'Description' for it.

How 'bout something like this:
QuoteThis board is for questions and answers specifically about using the Windows Win32 API. This includes all elements of this interface, including GUI (graphical user interface) issues.
Or something like that ...
Assembly language programming should be fun. That's why I do it.

stoo23

QuoteThis board is for questions and answers specifically about using the Windows Win32 API. This includes all elements of this interface, including GUI (graphical user interface) issues.

Done. Thanks  :thumbsup: