Objects in HTML5 observe a true parent-child hierarchy-that is, a child object is always contained within a single parent object. The custom app's host also sets record locks, activates script triggers, fetches data, and manages layout and data caches. For example, key presses and mouse clicks that are handled by FileMaker Pro must be sent from FileMaker WebDirect to FileMaker Server or FileMaker Cloud. The FileMaker Server or FileMaker Cloud deployment does most of the work for the FileMaker WebDirect client. Limitations that are inherent to the web also apply to FileMaker WebDirect. Most web applications don’t have hundreds of interactive objects or large, high-resolution images because web browsers cannot render them quickly enough and can be slowed by poor network connections. Layouts should reflect standard best practices on the web.Įvery object, style, image, and interaction on a layout means more data transferred from the Database Server to the web browser, so consider carefully what to include on a layout.
Web server: Communicates with web browsers using HTTP/HTTPS and WebSocket protocols to serve your custom app as a web application.In FileMaker Server multiple-machine deployments, the WPE manages communications between the primary and secondary machines. In real time, the Web Publishing Engine (WPE) creates the user interface from your layouts to work in the web browser and processes scripts, script triggers, user clicks, and key presses. Web Publishing Engine: Translates the layouts, interactions, and data defined by your custom app into HTML5, CSS3, JavaScript, and data for the web browser and processes user interaction.It handles layouts, data, scripts, script triggers, user account authentication, record locking, and communication with all FileMaker clients. Database Server: Hosts the custom apps you share with all FileMaker clients (FileMaker Pro, Claris FileMaker Go®, and FileMaker WebDirect).In the web browser, FileMaker WebDirect runs as a client that interacts with a custom app hosted by FileMaker Server or FileMaker Cloud.įileMaker Server and FileMaker Cloud include the following components: The architecture of FileMaker WebDirect bridges two different environments: the web browser and a FileMaker custom app. Though you may need to make some changes to your custom app using FileMaker Pro, you won’t need to write any PHP, HTML, CSS, or JavaScript code. If you plan to extend an existing custom app for web users, expect to make changes to your custom app for the best possible user experience. For example, if warehouse workers only need to fulfill orders in your order management custom app, then you may only need to add invoice layouts that work well in a browser. Import or export records and container dataĭeploy a customized web application by hiding and locking the menu bar and status toolbarīuilt on advances in web technologies, FileMaker WebDirect enables your custom apps to do much of what FileMaker Pro can do, within the constraints of modern web browsers.įileMaker WebDirect works best when you are:ĭeploying FileMaker custom apps intended primarily for web browsersĮxtending existing custom apps to include remote users outside the team or organizationįor particular groups of users, you can add or modify only the layouts they need. With FileMaker WebDirect, you can:Įasily and quickly deploy a custom app to anyone with a compatible web browser without using web authoring tools or other technologies Claris FileMaker WebDirect® combines aspects of a web application and a desktop application, bringing FileMaker Pro features to your custom apps on the web.
0 kommentar(er)
