Future Development ideas

Future Development Ideas

Here are some exciting ideas for future development of the ACF Plugin:

Literal Arrays: Allow the use of literal arrays (e.g., {1, 2, 3}) as parameters for functions.
Enhanced Substitute Function: Improve the substitute function to support arrays in both the "from" and "to" parameters, enabling complex substitution patterns, similar to PHP.
Array Mixed Type: Introduce a mixed type array that can hold values of any data type. Such arrays could be particularly useful in representing record sets.
ImplodeToSQL Function: Implement an ImplodeToSQL function that automatically handles necessary quotations and date syntax in the merged result when working with mixed type arrays.
mySQL Connector: Develop a mySQL connector to enable direct querying or updating of mySQL databases using ACF functions. ( This is allready implemented for the Mac version in version 1.6.3 )
MSSQL Connector: Create an MSSQL connector to facilitate direct querying or updating of MSSQL databases through ACF functions.
ExecuteScript Function: Explore the possibility of adding an ExecuteScript function to launch FileMaker Scripts directly from ACF functions. While immediate execution is not feasible due to PluginAPI limitations, it could allow queuing scripts for execution after the plugin function has finished.

Here are additional ideas that could enhance the ACF Plugin's functionality and development experience:

Script Debugger: Consider implementing a script debugger for plugin functions. In debug mode during compilation, the debugger could insert "Debug NOOPS" (NOOP = NO Operation) into the code, one per line. These "NOOP <line no>" markers could trigger suspension of execution and transfer control to a debug window displaying the source code with line numbers. Developers could examine variables and set breakpoints, enabling stepping through code and other debugging tasks.
Automatic Debug Mode Activation: If the source is compiled in debug mode, a "Debug" statement could automatically activate the debug window and suspend execution.
Debug Info Generation: When compiled in debug mode, generate a separate debug info file, such as "package_name.deb." This file could include the source code as a table with line numbers and additional debugging information, eliminating the need to include this in the compiled package.

These innovative ideas hold the potential to further enhance the functionality and developer experience within the ACF Plugin.