I recently used Jan Stieparaere's amazing technique for getting one FileMaker client to execute a script on another client. Although Jan has published a module that uses the technique for generating PDF files from WebDirect clients, I'm interested in publishing a more generic module that one client to send a data message to another. I don't mean a message to the user. To use Jan's WebDirect solution as an example, the WebDirect client is sending a message to the robot that a PDF needs to be generated and then the robot sends a message back to the WebDirect client that the PDF is ready.
But here's the thing. I'm going to build this with custom functions. I'm sure I could do it without them, but, well, I disagree with the position that custom functions should be avoided by default. I feel they should be used by default. I understand the other point of view, it's just not mine.
I'm not trying to argue my view about custom functions. I'm only saying I plan to build this module with my custom function library as a given.
So how strict is the general rule that custom functions should be avoided? The module will be available on GitHub regardless, but should I forego submitting it to
modularfilemaker.org given the above plans?
Thanks,
Chuck