This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
experimental_features [2023/02/27 19:08] yves [Pre-set annotations] |
experimental_features [2023/02/28 17:02] (current) yves [Artificial intelligence (AI)] |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| ==== Conferencing ==== | ==== Conferencing ==== | ||
| + | |||
| + | Experienced digital pathology users are aware that slide sharing through standard video conferencing tools like Zoom or WebEx is far from ideal. | ||
| + | |||
| + | PMA.studio can interface with both [[https://www.pathomation.com/pma.core|PMA.core]] and [[https://www.pathomation.com/pma.live/|PMA.live]] to provide a better way to share slide-centric discussions. | ||
| + | |||
| + | Admittedly, we got into a bit of feature creep when designing this one, and it's not quite finished yet for prime time. Experimentally, though, it's a great resource already for team discussions, and we already hear from several customers that were pretty excited playing around with initial implementations. | ||
| + | |||
| + | {{:ri_experimental_conferencing.png?|}} | ||
| + | |||
| + | So, rather than putting this one in the freezer, we're simply allowing you to enable it when you want to and play around with it. Then, let us know if this is (already) useful to you, and what edge conditions you'd like to have more control over. | ||
| ==== Artificial intelligence (AI) ==== | ==== Artificial intelligence (AI) ==== | ||
| + | |||
| + | There's no question that everything artificial intelligence is smoking hot right now. All the big guys are doing it, so [[https://realdata.pathomation.com/quod-ai|why shouldn't we]]? | ||
| + | |||
| + | Summarizing the above blog article; Pathomation doesn't want to come out with its own AI software, but it does want to offer a mechanism that allows data from different AI providers to come together in a single uniform interface. | ||
| + | |||
| + | This is where the [[https://realdata.pathomation.com/custom-panels-and-functionality-in-pma-studio/|custom panels]] come into play. | ||
| + | |||
| + | {{::ri_experimental_ai.png?|}} | ||
| + | |||
| + | PMA.studio comes with an optional AI ribbon tab that repeats relevant annotation capabilities from the [[ribbon_tabs#annotations_tab|annotation tab]], and provides interfaces to a number of well-known AI providers already. | ||
| + | |||
| + | But better yet: the interfaces that we offer this way are implemented through custom panels (following the "[[https://en.wikipedia.org/wiki/Eating_your_own_dog_food|take your own medicine]]" principle). The code behind these is currently written in PHP, and can be used for study and to build your own interface to your own AI providers (or further extend the ones we offer (limited) support for already ourselves. | ||
| ==== Persistent user features ==== | ==== Persistent user features ==== | ||
| + | |||
| + | While the panels and ribbon tabs in PMA.studio are fully configurable, they have a major flaw: in their current implementation they're only configurable at the application level. | ||
| + | |||
| + | Furthermore, a user must have PMA.core administrator-level access to be able to modify either configuration. This last one is actually not a bad thing, considering: | ||
| + | |||
| + | * Both panel and ribbon configurations require knowledge of XML, and | ||
| + | * Changes in the configuration will affect *all* users of said PMA.studio instance | ||
| + | |||
| + | The solution is to have a basic configuration that applies to all users, and in addition allow users to define their own interfaces as they see fit. Other applications like Microsoft Office 365 have had this feature for a while now, of course, but then again, Office users historically only had to worry about their own configuration on their own computer. In our case, we need to thread a bit more carefully. | ||
| + | |||
| + | The key word is "user persistence". | ||
| + | |||
| + | We've started with making some basic features persistent: end-user settings like "auto-save annotations" and others, all accessible from the Edit settings from the application's [[context_menu|context-menu]]. | ||
| + | |||
| + | In future releases of PMA.studio you can expect to see a lot more persistance. | ||
| ==== See also ==== | ==== See also ==== | ||