MWAPI Standard~ - Revision history

DavidWhitten at 00:45, 2 July 2019

2019-07-02T00:45:16Z

← Older revision		Revision as of 00:45, 2 July 2019
Line 2:		Line 2:
	------------------------------------------------------------------------		------------------------------------------------------------------------
	11. Does M/MUMPS support Microsoft Windows and other Graphic User Interfaces (GUIs)?		11. Does M/MUMPS support Microsoft Windows and other Graphic User Interfaces (GUIs)?

	== M Windowing API (MWAPI) ==		== M Windowing API (MWAPI) ==

DavidWhitten: /* "WRITE-SLASH" APPROACHES */

2019-07-02T00:43:21Z

"WRITE-SLASH" APPROACHES

← Older revision		Revision as of 00:43, 2 July 2019
Line 36:		Line 36:
	; MGM		; MGM
	: W /DBUTTON("OK",2,9)		: W /DBUTTON("OK",2,9)

			Paul Perrin said:
			as far as practical use goes I find the write-slash formatvery useful for mumps integration within the MSWindows enviroment. Enabling data from a Mumps system (maybe from a {{G\|DDP}} link to another hardware platform) to be placed on the windows clipboard for pasting into other applications is invaluable.

			I've recently been using this mechanism to allow editing of DTM code using a windows based programmers editor (tho' I'm still experimenting)

			From Memory:-

			R "Routine Name:",ROUT W !
			I ROUT="" Q
			S SOURCE=$ZRS(ROUT)
			I SOURCE="" Q
			O 40 U 40 W /WSETCLIP(SOURCE)

			; Prog can now paste code into windows editor
			; Edit source
			; Copy modified code back to clipboard

			W "Hit <space> to reload source" R *X
			I X'=$A(" ") Q

			; Request Clipped Data, Get Response Message, If not null zsave
			W /WGETCLIP
			F I=1:1:10 W /WGETMESSAGE(.X) Q:X'="" H .5
			I X="" Q
			S SOURCE=$P(X,$C(22),5)

			ZS @ROUT:SOURCE:1
			Q

			Probably the shortest program editor I've ever written :-).

DavidWhitten: /* "WRITE-SLASH" APPROACHES */

2019-07-02T00:40:23Z

"WRITE-SLASH" APPROACHES

← Older revision		Revision as of 00:40, 2 July 2019
Line 28:		Line 28:
	InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash" syntax. In DT-Windows and MGM, the windowing system is treated as a "device" with an unusually rich repertoire of device-specific commands.		InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash" syntax. In DT-Windows and MGM, the windowing system is treated as a "device" with an unusually rich repertoire of device-specific commands.

	Although DT-Windows and MGM are conceptually similar, they are incompatible with each other. They are ad-hoc language extensions. Neither seems to have set a defacto standard. Why do these products (DT-Windows and MGM) provide a nonstandard approach? The answer, in part, is that they were introduced prior to the finalization of the MWAPI standard. Why do they still exist? Because they are closer to their underlying windowing platform		Although DT-Windows and MGM are conceptually similar, they are incompatible with each other. They are ad-hoc language extensions. Neither seems to have set a defacto standard. Why do these products (DT-Windows and MGM) provide a nonstandard approach? The answer, in part, is that they were introduced prior to the finalization of the MWAPI standard. Why do they still exist? Because they are closer to their underlying windowing platform than the MWAPI, they arguably provide better performance and broader access to the GUI system's functionality.
	than the MWAPI, they arguably provide better performance and broader access to the GUI system's functionality.

	Examples from the DT-Windows manual and MGM product literature, respectively, show how an "OK" button is added to a dialog box:		Examples from the DT-Windows manual and MGM product literature, respectively, show how an "OK" button is added to a dialog box:

DavidWhitten: /* "WRITE-SLASH" APPROACHES */

2019-07-02T00:39:58Z

"WRITE-SLASH" APPROACHES

← Older revision		Revision as of 00:39, 2 July 2019
Line 26:		Line 26:

	== "WRITE-SLASH" APPROACHES ==		== "WRITE-SLASH" APPROACHES ==
	InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash"		InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash" syntax. In DT-Windows and MGM, the windowing system is treated as a "device" with an unusually rich repertoire of device-specific commands.
	syntax. In DT-Windows and MGM, the windowing system is treated as a "device" with an unusually rich repertoire of device-specific commands.

	Although DT-Windows and MGM are conceptually similar, they are incompatible with each other. They are ad-hoc language extensions. Neither seems to have set a defacto standard. Why do these products (DT-Windows and MGM) provide a nonstandard approach? The answer, in part, is that they were introduced prior to the finalization of the MWAPI standard. Why do they still exist? Because they are closer to their underlying windowing platform		Although DT-Windows and MGM are conceptually similar, they are incompatible with each other. They are ad-hoc language extensions. Neither seems to have set a defacto standard. Why do these products (DT-Windows and MGM) provide a nonstandard approach? The answer, in part, is that they were introduced prior to the finalization of the MWAPI standard. Why do they still exist? Because they are closer to their underlying windowing platform

DavidWhitten at 00:39, 2 July 2019

2019-07-02T00:39:39Z

← Older revision		Revision as of 00:39, 2 July 2019
Line 1:		Line 1:
	From the FAQ: ( as documented by Daniel P.B. Smith 1995)		From the FAQ: ( as documented by Daniel P.B. Smith 1995)
	------------------------------------------------------------------------		------------------------------------------------------------------------
	11. Does M/MUMPS support Microsoft Windows and other GUIs?		11. Does M/MUMPS support Microsoft Windows and other Graphic User Interfaces (GUIs)?
			== M Windowing API (MWAPI) ==

	A 1994 addition to the M standard, the M Windowing API (MWAPI), defines an interface between the M language and windowing systems.		A 1994 addition to the M standard, the M Windowing API (MWAPI), defines an interface between the M language and windowing systems.

DavidWhitten at 00:38, 2 July 2019

2019-07-02T00:38:33Z

← Older revision		Revision as of 00:38, 2 July 2019
Line 1:		Line 1:
	From the FAQ: ( as documented by Daniel P.B. Smith 1995)		From the FAQ: ( as documented by Daniel P.B. Smith 1995)
	------------------------------------------------------------------------		------------------------------------------------------------------------
	11. Does M/MUMPS support Microsoft Windows and other ~~GUIUs~~?		11. Does M/MUMPS support Microsoft Windows and other GUIs?

	A 1994 addition to the M standard, the M Windowing API (MWAPI), defines an interface between the M language and windowing systems.		A 1994 addition to the M standard, the M Windowing API (MWAPI), defines an interface between the M language and windowing systems.
Line 19:		Line 19:
	The MWAPI is currently offered for Microsoft Windows by InterSystems and Micronetics, and for Windows NT by Digital Equipment Corporation. It is often presented as the windowing future for M technology.		The MWAPI is currently offered for Microsoft Windows by InterSystems and Micronetics, and for Windows NT by Digital Equipment Corporation. It is often presented as the windowing future for M technology.

	VISUAL-BASIC-LIKE APPROACHES		== VISUAL-BASIC-LIKE APPROACHES ==

	InterSystems' "Visual M" is a set of tools which link M with Microsoft Visual Basic, creating an integrated dual-language environment. M code can be accessed and edited from within the VB design environment, can access VB control properties, and can be triggered by VB events.		InterSystems' "Visual M" is a set of tools which link M with Microsoft Visual Basic, creating an integrated dual-language environment. M code can be accessed and edited from within the VB design environment, can access VB control properties, and can be triggered by VB events.

	Micronetics product MSM-View Builder and MSM Workstation provides a Visual-Basic-like environment entirely based on M and the MWAPI.		Micronetics product MSM-View Builder and MSM Workstation provides a Visual-Basic-like environment entirely based on M and the MWAPI.

	== "WRITE-SLASH" APPROACHES ==		== "WRITE-SLASH" APPROACHES ==

	InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash"		InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash"
	syntax. In DT-Windows and MGM, the windowing system is treated as a "device" with an unusually rich repertoire of device-specific commands.		syntax. In DT-Windows and MGM, the windowing system is treated as a "device" with an unusually rich repertoire of device-specific commands.

DavidWhitten at 00:37, 2 July 2019

2019-07-02T00:37:23Z

← Older revision		Revision as of 00:37, 2 July 2019
Line 21:		Line 21:
	VISUAL-BASIC-LIKE APPROACHES		VISUAL-BASIC-LIKE APPROACHES

	InterSystems' "Visual M" is a set of tools which link M with Microsoft Visual Basic, creating an integrated dual-language environment. M code can be accessed and edited from within the VB design environment, can access VB		InterSystems' "Visual M" is a set of tools which link M with Microsoft Visual Basic, creating an integrated dual-language environment. M code can be accessed and edited from within the VB design environment, can access VB control properties, and can be triggered by VB events.
	control properties, and can be triggered by VB events.

	Micronetics [product ~~name????]~~ provides a Visual-Basic-like environment entirely based on M and the MWAPI.		Micronetics product MSM-View Builder and MSM Workstation provides a Visual-Basic-like environment entirely based on M and the MWAPI.

	"WRITE-SLASH" APPROACHES		== "WRITE-SLASH" APPROACHES ==

	InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash"		InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash"

DavidWhitten at 00:34, 2 July 2019

2019-07-02T00:34:53Z

← Older revision		Revision as of 00:34, 2 July 2019
Line 29:		Line 29:

	InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash"		InterSystems' "DT-Windows," MGlobal's MGM-PC (for MS-Windows) and MGM-Mac (for the Macintosh) use a feature of the M standard that allows the language to be extended for device-specific purposes by means of the "write-slash"
	syntax. In DT-Windows and MGM, the windowing system is treated as a "device" with an unusually rich repertoire of device-specific commands.		syntax. In DT-Windows and MGM, the windowing system is treated as a "device" with an unusually rich repertoire of device-specific commands.
	Although DT-Windows and MGM are conceptually similar, they are incompatible with each other. They are ad-hoc language extensions. Neither seems to have set a defacto standard. Why do these products (DT-Windows and MGM)
	provide a nonstandard approach? The answer, in part, is that they were introduced prior to the finalization of the MWAPI standard. Why do they still exist? Because they are closer to their underlying windowing platform		Although DT-Windows and MGM are conceptually similar, they are incompatible with each other. They are ad-hoc language extensions. Neither seems to have set a defacto standard. Why do these products (DT-Windows and MGM) provide a nonstandard approach? The answer, in part, is that they were introduced prior to the finalization of the MWAPI standard. Why do they still exist? Because they are closer to their underlying windowing platform
	than the MWAPI, they arguably provide better performance and broader access to the GUI system's functionality.		than the MWAPI, they arguably provide better performance and broader access to the GUI system's functionality.

	Examples from the DT-Windows manual and MGM product literature, respectively, show how an "OK" button is added to a dialog box:		Examples from the DT-Windows manual and MGM product literature, respectively, show how an "OK" button is added to a dialog box:
	; DT-Windows		; DT-Windows

DavidWhitten at 00:33, 2 July 2019

2019-07-02T00:33:52Z

← Older revision		Revision as of 00:33, 2 July 2019
Line 1:		Line 1:
	From the FAQ: ( as documented by Daniel P.B. Smith 1995)		From the FAQ: ( as documented by Daniel P.B. Smith 1995)
			------------------------------------------------------------------------
	------------------------------------------------------------------------
	11. Does M/MUMPS support Microsoft Windows and other GUIUs?		11. Does M/MUMPS support Microsoft Windows and other GUIUs?

DavidWhitten at 00:33, 2 July 2019

2019-07-02T00:33:24Z

← Older revision		Revision as of 00:33, 2 July 2019
Line 10:		Line 10:
	The M Windowing API and its commercial implementations are relatively new and have rough edges. The MWAPI has the advantage of portability and platform-independence, but has some limitations associated with the "least-common-denominator" approach.		The M Windowing API and its commercial implementations are relatively new and have rough edges. The MWAPI has the advantage of portability and platform-independence, but has some limitations associated with the "least-common-denominator" approach.

	A unique feature of the MWAPI is that this "API" does not consist of subroutine calls (except for a few incidental functions). MWAPI programming consists mainly of performing sets and kills into a "structured system		A unique feature of the MWAPI is that this "API" does not consist of subroutine calls (except for a few incidental functions). MWAPI programming consists mainly of performing sets and kills into a "structured system variable," which looks like a standard M global. For example, to set the title of a window to "M Technology Demonstration," you write
	variable," which looks like a standard M global. For example, to set the title of a window to "M Technology Demonstration," you write

	s ^$WINDOW("main","TITLE")="M Technology Demonstration"		s ^$WINDOW("main","TITLE")="M Technology Demonstration"