Native JSON Functions and # Functions

[alec gregory]

Is now a good time to start a discussion about the future of the # Functions given that native JSON functions are coming? Or is it best to wait until the official release?

[Jeremy Bante]

I've been holding my tongue for the public release.

[Alec Gregory]

Cool. Looking forward to the discussion.

--
You received this message because you are subscribed to a topic in the Google Groups "FileMaker Development Standards" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fmstandards/1XhB22XfczE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to fmstandards...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Diego D'Alessio]

we're still under NDA ... :O

On Thu, Apr 13, 2017 at 2:07 PM, Alec Gregory <alecg...@gmail.com> wrote:

Cool. Looking forward to the discussion.

On Thu, Apr 13, 2017 at 12:27 PM Jeremy Bante <jeremy...@gmail.com> wrote:

I've been holding my tongue for the public release.

On Thursday, April 13, 2017 at 5:10:19 AM UTC-7, alec gregory wrote:

Is now a good time to start a discussion about the future of the # Functions given that native JSON functions are coming? Or is it best to wait until the official release?

--
You received this message because you are subscribed to a topic in the Google Groups "FileMaker Development Standards" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fmstandards/1XhB22XfczE/unsubscribe.

To unsubscribe from this group and all its topics, send an email to fmstandards+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "FileMaker Development Standards" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fmstandards+unsubscribe@googlegroups.com.

[Jeremy Bante]

Now that FileMaker 16 has been released, here are some of my thoughts on the topic: https://github.com/jbante/FM-JSON-Types

[Gary Czychi]

Hi Jeremy,

thanks for sharing.

You say: « This will also make JSON the de facto standard format for scripts within FileMaker to pass parameters and results to each other…» Do you mean that you want/need to change the #-scripts that we are currently using to pass parameters from the FM Standards? Any enlightenment would be greatly appreciated as I am using the #-scripts in all my projects.

Thanks,

Gary

On 12.05.2017, at 09:23, Jeremy Bante <jeremy...@gmail.com> wrote:

Now that FileMaker 16 has been released, here are some of my thoughts on the topic: https://github.com/jbante/FM-JSON-Types

--
You received this message because you are subscribed to the Google Groups "FileMaker Development Standards" group.

To unsubscribe from this group and stop receiving emails from it, send an email to fmstandards...@googlegroups.com.

[Jeremy Bante]

On Friday, May 12, 2017 at 12:42:09 AM UTC-7, Gary Czychi wrote:

Do you mean that you want/need to change the #-scripts that we are currently using to pass parameters from the FM Standards? Any enlightenment would be greatly appreciated as I am using the #-scripts in all my projects.

My current personal thinking is to abandon the # functions, and the approach taken by #Assign in particular, in favor of JSON. Additionally, some of the semantics of how building JSON works in FileMaker are incompatible with how the # ( name ; value ) function is used to build Let Notation. It isn't possible to just swap out the calculations for the # functions to use JSON without modifying how they're used. (Well, it might be possible if we're really clever about it; but it would be unwise, all the same.)

[Daniel Smith]

I agree with JSON being the new standard serialization method, but please don't feel like you have to change old code to this new method. If you are starting a new project that only has to run on FM16+, you might benefit from using JSON instead of the #-functions. But even then, if you want to re-use your own code that uses the #-functions, you might want to stick to them for now, even for new projects.

Changing a core standard that all your code rely's on is not to be taken lightly.

--

You received this message because you are subscribed to the Google Groups "FileMaker Development Standards" group.

To unsubscribe from this group and stop receiving emails from it, send an email to fmstandards+unsubscribe@googlegroups.com.

[Jeremy Bante]

On Friday, May 12, 2017 at 10:11:37 AM UTC-7, dansmith65 wrote:

I agree with JSON being the new standard serialization method, but please don't feel like you have to change old code to this new method. If you are starting a new project that only has to run on FM16+, you might benefit from using JSON instead of the #-functions. But even then, if you want to re-use your own code that uses the #-functions, you might want to stick to them for now, even for new projects.

Changing a core standard that all your code rely's on is not to be taken lightly.

Agreed. 

[Ben Graham]

Agreed!

Sent from my iPhone

To unsubscribe from this group and stop receiving emails from it, send an email to fmstandards...@googlegroups.com.

[Scott Reese]

I wouldn't make it as standard until an extension change. I wouldn't want to break backwards compatibility. 

Sent from my iPhone

[Gary Czychi]

I would [make it a standard] as soon as possible, because many people already work with json, even more so as we speak.

Why not have both? Until an extension change? They could easily coexist. You could have backwards compatibility with our “Set Variable [ParametersAreOK ; Value: #Assign … // deprecated ]”  and you could also have: “… #jAssign …” and it would be up to you what you would use.

My current project already involves json and even though we are about one third into the project I’m thinking of replacing the # functions; also because not much scripting has been done yet.

It would be really cool to have the new functionality. Updated FM Standards would be very beneficial because FileMaker now again is very open and minimalist about what they provide.

Gary

[Jeremy Bante]

The new built-in JSON functions in FileMaker 16 are not supported in runtimes. That's a big deal for anyone with a business built on runtime-based products, and anyone who wants to share code with them. That's a fair-sized group.