Pages containing 'Fileman'
One of the characteristics of the final stage of packaging a new version for a VISTA application is that we must paradoxically freeze development without freezing development.
We must freeze development because the distribution sent to the world has to be a specific, tested version of the software. Getting to that point requires constraining development toward satisfying the results of testing, not introducing new disruption late in the packaging process, when there won't be sufficient time to test it. In this pro-testing era, most people get this issue pretty well.
To say that File Manager is VISTA's database management system is a gross understatement, so gross that it is more misleading than helpful.
Traditional database systems run side by side with the applications, offering data-related services (like creating, reading, updating, and deleting records - the services with the unattractive acronym CRUD - along with many, many other such services). In other words, most DBMSes have a peer-to-peer relationship with the applications that use them to manage their data.
One of the two top strategic goals for FLAP Phase One (which ran from October 2012 through March 2013) was code convergence, to create a shared, common Fileman codebase that all VISTA dialects could run, to maximize our ability to exchange data and software with one another, to ensure that innovations anywhere became innovations everywhere as quickly as possible, and to reduce the amount of reinventing the wheel we had to do.
The main VISTA dialects we aimed at converging for Phase One were:
1) VA VISTA
2) IHS RPMS
3) WorldVistA EHR
4) vxVistA, and
FLAP Phase Two began yesterday - Sunday, 23 November 2014 - with the launching of a Preparatory stage.
In its 1.1 release, FMQL will move its JSON format over to JSON-LD. This form of JSON provides a straightforward JSON with rigorous semantics, something key for VistA data with its large and powerful data model.