12/20/2023 0 Comments Baseelements xml error![]() ![]() We knew that the latest beta of 14 was slower, quite a bit slower. Our base line for speed testing was importing our sample files ( BaseElements itself ) into the current BE 4. This makes it really time consuming to debug and test any change. This is a complex, difficult process – XSLT is handled differently in the plugin, vs the command line, vs the import, vs the debugger tools. We’ve spent a lot of time re-factoring our XSLT to shift a lot of the complexity there instead of the import. ![]() If you want fast imports, remove all your unnecessary auto enters, lookups, stored calculations and indexes. And to do that meant putting a lot of these calculations into the XSLT so that the import was as simple as possible, and therefore as fast as possible. The solution was to go back and re-think the whole way alerts are generated across all the elements, but especially the large ones ( objects, steps, calculations ). You never set out to design a slow solution, and you never deliberately make a change that is going make things slow, but occasionally you add a great feature that has a cost you didn’t plan for. At some point in the last few betas our alerts auto enter calculation was doing a sum of a related field, which itself was un-stored, and that will never be fast. And what we ended up with was a solution for layout objects that was way too complex than it should be to get the job done. So we’ve added some extra items and included more detail for others, plus combined things into a single location.Īnd as every developer knows, when you add to a solution iteratively over a long period, all your changes add up. In order to better track the myriad of issues that can crop up, and be better able to handle errors, warnings, performance issues and unreferenced items, we’ve been consolidating them into a single alert. What’s mostly got us stuck is some changes to the Alerts that we introduced with the new 14 re-design. We haven’t sat still but development has been slower while we’ve worked on client work, RefreshFM updates, RESTfm updates and additions and bug fixes to the Plugin. We still use BE every day ourselves, and even use BE to develop BE and couldn’t live with out it, much like a lot of you. ![]() So to answer all the big questions : Are you still working on it?Ībsolutely. Rest assured we’re still working on it, and things are progressing.Īnd FileMaker 15 is out today, and happens to coincide with me finishing up a big set of changes to BE, so an opportune time to post an update. If base type's content model always appears first, application code written to process the base type will also work correctly on the derived types.It’s been a while since the last BaseElements update, and I’ve had a few emails asking me what’s going on. This is designed for compatibility consideration. Long answer: In extension, base type's content model will appear first. For your problem, one workaround is to define a named model group containing "firstname" and "lastname" elements, and reuse it in both "personinfo" and "fullpersoninfo": If base type's content model always appears first, application code written to process the base type will also work correctly on the derived types. Here's what I have now: joe smith 1 main st Anytown USA įor this xsd schema: Here's what I want: 1 main st Anytown USA joe smith Without changing my inheritance hierarchy (the "firstname" and "lastname" are in the base), can I get "address", "city", "country" to be at the beginning of the sequence of elements? xsd schema with an "extension" of fullpersoninfo based on personinfo.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |