You may know Xojo Cloud as an easy way to deploy Web 1 and 2 applications to the web.

Replace(Path as string, NewValue as Variant) as JSONMBS.

Query(Path as string, Options as Integer = 0) as JSONMBS.

If you know XML queries, you may like the JSON queries: We like to add great new features like JSON Path Queries, Search & Replace and flatten & unflatten. You can choose whatever name you prefer since they are all connected to the same methods internally. That is why we get both Value() and ValueAt(). That means we have to copy the JSONItem public interface in both API 1 and API 2. Since you may use JSONItem, we need to be compatible, so you can easily switch to our class. Performance should be in general the same and exact results depend on what operations are used in the benchmark code. In other cases we can be more efficient and avoid calls and do things quicker. Since we have to go through the Plugin SDK interface, we are slower in some cases due to that extra layer. We need to keep performance at great levels, especially when JSONItem caught up in Xoxo 2021 Release 1. And we need to do same behaviors as much as possible. To make a compelling offer to our clients for using this class, it has include a few key things:Īlthough we swap the underlaying library, we have to keep the same interface so existing code using JSONMBS continues to work. Time for a rewrite and over the last months, we got that on the way. Our MBS JSON class called JSONMBS got a bit aged in the last years.

We also got functions like IsInt64, IsUInt64, IsInt32 and IsUInt32 which check for IsNumber and the range. So if a floating point number is stored internally as string, you may see kTypeString for it, but IsNumber returns true as it's a string we use to hold a number and output it as number. Our IsNumber function handles this correctly. If you store 1.2345 as currency into JSON with our plugin, it will stay 1.2345 and not convert internally to a double and get output as 1.2344999999999999307. We preserve numbers in exact representation. You can inspect the exception for it's message property to see an error message. So checking handle for 0 and checking ParseError property is gone. We now raise exceptions for all bad operations. The byte string is for handling MemoryBlocks in JSON, which can encoded as Hex, Base64 or Base64URL as needed. Error, True, False and Number types are gone and we got new things like Boolean, ByteString, Int64, Single, Double and UInt64. We got new kType* constants for new node types. The new class is better in many ways, like interface compatible to JSONItem class, adds new Query, Search and Replace methods as well as handling errors better. If you used our older JSONMBS class and now move to 23.5 version of MBS Xojo Plugins, you may notice a few changes.

Xojo plugins