When Vince Menanno suggested I revive that dormant project and turn the old search interface I had showed him into a module that could be used in other FileMaker applications, it occurred to me that using the brand new card-style windows in FileMaker 16 would allow me to continue to present a UI styled after macOS sheets, but free me from portals and relationships. Why? Because card windows, while they may feel like yet another layout object, are . . . well . . . windows. Like any window type, they have their own context, which may be different from the parent window. Also, instead of being limited to showing records in a portal, I could use a traditional FileMaker list view. Goodbye, tangles of relationships! Adios, UI limitations of portals!
One setting in which you should consider using card windows is as an occasional replacement for popovers. Each has its strengths; the following table may help you decide which one is right for a given use.
The ability to use card windows in WebDirect is a powerful feature. Card windows are a true modal window, allowing the display of context-independent information. Users can create, edit, and delete records without navigating from the parent window. Card windows can be used for things like to-do lists, navigation, or pick lists.
Overall, the support of card windows in WebDirect will make developing a unified and streamlined user experience even easier. If you have any questions or need help implementing this functionality in your FileMaker application, please feel free to contact our team.
With the introduction of FileMaker 16 for Windows, the FileMaker interface was redesigned to handle multiple windows, more akin to the Mac OS. Instead of using one application window, Windows users can now run multiple windows, each with their own menu and toolbars.
760c119bf3