You can easily pop the hood, see what someone else made, and get an idea of the database’s scope in just a few minutes. It tells you the size and scale of the solution you’re analyzing, which is especially helpful if you’re dealing with a solution you didn’t build.
Human error also means that, if you check your files without BaseElements, you could overlook big problems.īaseElements counts all of your components as a total. SMTP is an optional one, so anyone who would like this functionality and would consider sponsoring us should get in touch.BaseElements is helpful because it analyzes files that would otherwise take your team a lot of time to check manually. And then I’d like to look at both XQuery and SMTP support. I’d like to add a progress dialog, just something basic with a start and an end. We already have some things we’d like to do, possibly in point releases of 2.x but possibly also in a 3.0 version. I’ve updated the Functions list with all of the new details and the Todo List page with the changes. You don’t even need to tell us you use it, but if you like it, please let us know. You don’t need to licence it, register it or pay for it.
GOYA BASEELEMENTS LICENSE FREE
Our BaseElements plugin continues to be free and open source.
GOYA BASEELEMENTS LICENSE FULL
So you can test the value of this result with multiple calls to the function and it doesn’t change until you call some other BE plugin function.Īdded BE_HTTP_DELETE and BE_HTTP_PUT, so we now have the full complement of GET, PUT, POST and DELETE, plus we added basic authentication to all of the HTTP functions.Īdded default folders to the BE_SelectFile and BE_SelectFolder functions so now you can choose what folder it will start in.Īdded a function BE_StripXMLNodes which although not useful to many people is going to be handy to us in the future for our changes to the BaseElements import process which hopefully gives us some useful optimisations we can do. There is still the option to wait for ever by using a -1 parameter, or not at all with a value of 0.Ĭhanged the way the BE_GetLastError function works, so that it doesn’t reset on successive calls. This is much better in that you no longer get stuck if your process gets stuck. Now instead of a waitForResponse option, you can specify a timeout.
This changes slightly the operation in terms of having a different second optional parameter. It’s been replace by …īE_ExecuteSystemCommand was added. If typed, or copied it will continue to work though. The function still exists, and will still work exactly as before, but no longer appears in the function list when editing a calculation.
This one will be really handy when doing remote data entry and having to sync back to a server that is outside the current timezone.īE_ExecuteShellCommand was deprecated. The new function produces url safe output and also pads the value in the same way as the web version.Īdded BE_CurrentTimeMilliseconds, BE_UTCMilliseconds, and BE_TimeZoneOffset.īE_CurrentTimeMilliseconds is effectively a copy of GetAsNumber ( Get ( CurrentTimestamp ) ) but was being added anyway with the offset coding.īE_UTCMilliseconds is just the UTC version of BE_CurrentTimeMilliseconds, but for the UTC timezone.īE_TimeZoneOffset is the difference ( in minutes ) between UTC and local time. This often results in values that don’t quite work at one end. However, you’re sending data to web services that use, for example, the php based base64 library then the character set they’re using, and the encode method is slightly different. The short explanation is that if you’re using the built in encode / decode, then it will all work fine. The difference is in the character set and details of the encode. This is as well as the existing BE_Base64_Encode. There is lots of new and changed functionality in this release. This is our first big release since version 1 and so we’ve bumped the version number to 2.0. Today we’ve made available version 2.0 of our free FileMaker plugin.
0 kommentar(er)
