Shortly before Todd launched ModuleFileMaker.org, I distinctly remember him advocating Let notation as a data format instead of the # functions. I was even inspired to write up some best practices for Let notation. I understand that the context of that was a little different, but I wonder if posting the # functions as a mFM module would make folks more willing to write modules with a dependency on those functions
One of the things I love about the # functions is that they are pretty just sugar on the Let Notation.
If anything, narrowing the allowable scope of # functions to Let notation would make me more comfortable with the notion of wrapping them up as a module, since they would indeed then just be sugar for the interchange format of choice.
...but I have a hard time imagining anyone deciding that it's worth it to implement the functions using anything else.
Before I worked on the JSON module, I would have said the same, but I found two issues with the current format used:
- The name in the name/value pair is not escaped, which limits the characters that can be used.
Todd, can you elaborate on the role of this core module you mentioned?I don't understand why a core module is needed rather than a separate module for each distinct feature.
--
You received this message because you are subscribed to the Google Groups "Modular FileMaker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modular-filema...@googlegroups.com.
To post to this group, send email to modular-...@googlegroups.com.
Visit this group at http://groups.google.com/group/modular-filemaker.
To view this discussion on the web visit https://groups.google.com/d/msgid/modular-filemaker/93df5098-57ec-4eba-af6e-ce056b064e3e%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
#GetLastError & # ( "section" ; "Create Invoice: commit record" )
--
You received this message because you are subscribed to the Google Groups "Modular FileMaker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modular-filema...@googlegroups.com.
To post to this group, send email to modular-...@googlegroups.com.
Visit this group at http://groups.google.com/group/modular-filemaker.
--
You received this message because you are subscribed to the Google Groups "Modular FileMaker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modular-filema...@googlegroups.com.
To post to this group, send email to modular-...@googlegroups.com.
Visit this group at http://groups.google.com/group/modular-filemaker.
To view this discussion on the web visit https://groups.google.com/d/msgid/modular-filemaker/5254b889-c2a3-4ab3-8c44-5d007c4d2aa5%40googlegroups.com.
As discussed briefly before, I think we have to be able to generate an "fmp" error, rather than only testing Get ( LastError ). As these functions are defined, it could be done with the #NewError CF, but the error text would need to be set manually. Personally, I would prefer that the "errorText" of an "fmp" error to always match the description of that error, as defined by FileMaker. That's not easy to do using this method, though.
--
You received this message because you are subscribed to the Google Groups "Modular FileMaker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to modular-filema...@googlegroups.com.
To post to this group, send email to modular-...@googlegroups.com.
Visit this group at http://groups.google.com/group/modular-filemaker.
To view this discussion on the web visit https://groups.google.com/d/msgid/modular-filemaker/51D752D4.60100%40geistinteractive.com.
On October 11, 2013 at 1:10:46 PM, Daniel Smith (dansm...@gmail.com) wrote:
FYI: I've been working on creating a set of Error functions, I'm going to use them for a while before I submit a pull request for them.Todd, were you going to submit a pull request for the #FPath function? I'd like to modify the examples in my JSON module to utilize that function for retrieving values.
FYI: I updated my error custom functions, and am trying to spark one last discussion about them before making them official: http://filemakerstandards.org/display/props/Error+Information+tracking?focusedCommentId=10649602#comment-10649602Once finalized, do you think they should be added to the #Parameters module? Or a module of their own?