Kexi/Plugins/Macros: Difference between revisions

Revision as of 22:13, 17 May 2023

{{Macros (the MSA style) are not implemented in KEXI. We're not even sure that Macros Kexi but we know what we want. See external discussions like [1]}}

For a quick introduction to macros see this article for MS Access.

Below is a dump from the old wiki's Macros page.

Generic Macro framework for KEXI
planning started: may 2005, js
planning extended: since jule 2005, sebsauer
development started: october 2005

Definition

Do not confuse Macros with scripts. Macros are simple tasks/actions/commands set up into sequences for later execution. So, they are kind of abstract containers for more specific functionality and useful for automating different tasks.

Macro is a program being dependent on "host" application; Macro has no assigned its own process identifier and private memory area. Script can have all of that. Please read the definition of macros as well.

@@ Line 1: / Line 1: @@
-'''Macros''' are not implemented in Kexi but we know what we want.
+{{'''Macros''' (the MSA style) are not implemented in KEXI. We're not even sure that Macros Kexi but we know what we want. See external discussions like [https://accessdatabasetutorial.com/microsoft-access-databases-pros-cons-access-macros/]}}
 For a quick introduction to macros see this article for [http://msdn.microsoft.com/en-us/library/office/gg435977%28v=office.14%29.aspx MS Access].
-For now see the old page: [http://www.kexi-project.org/wiki/wikiview/index.php@Macros.html] (TODO: migrate it here)
+Below is a dump from the old wiki's Macros page.
-Volunteers needed!
+ Generic Macro framework for KEXI
+ planning started: may 2005, js
+ planning extended: since jule 2005, sebsauer
+ development started: october 2005
+== Definition ==
+'''Do not confuse Macros with scripts'''. Macros are simple tasks/actions/commands set up into sequences for later execution. So, they are kind of abstract containers for more specific functionality and useful for automating different tasks.
+Macro is a program being dependent on "host" application; Macro has no assigned its own process identifier and private memory area. Script can have all of that. Please read the [http://en.wikipedia.org/wiki/Macro definition of macros] as well.
+See also:
+*[[/Discussions/]]
+*[https://web.archive.org/web/20060906113836/http://www.is.tcu.edu/userservices/tcuuser/0495/nltr0495accesstip.html Automating Tasks in Microsoft Access]
+*[https://web.archive.org/web/20220518185112/http://www.utteraccess.com/forums/access/access3213248.html Description of what is Macro in MSA]
+*[https://web.archive.org/web/20041215111332/http://www.saicomsystems.com/AccessPearls/mac-01.asp Example Tutorial of using Macro in MSA]
+*[https://web.archive.org/web/20150529085525/http://blogs.msdn.com/b/thirdoffive/archive/2006/04/18/561495.aspx Embedded MSA Macros]