Although I don’t know the specifics as to how Dynamo organises parameters in this panel, it is basically the Remote control panel as we know from Grasshopper on steroids. You can browse to a particular script and open it in the Dynamo player, without having to use the scripting canvas itself. It is like having a window of Human UI with all parameters listed, if you will. Although I have yet to give Human UI a try myself, I can foresee a Grasshopper Player being much easier to have a drag and drop UI in which all input parameters are pre-populated and with users being able to rearrange and resize input parameters (or even hide them from the panel in case it is a constant value), but this is already into the technicality of how it could work. I think that this is particularly powerful when used in Rhino.Inside. or to allow other people to work with someone else’s script.
This is how it works in Alias, where you save the script as a tool: https://www.youtube.com/watch?v=Jx531XHWFAg
And in Revit (note that this window can be fully populated with sliders and input boxes as well as other folders to browse to): https://www.youtube.com/watch?v=Nrztrqip2OE
Live linking files
This is similar to how you can link a PSD into Indesign/ Illustrator, save a new iteration and relink the contents. Or like how 3ds Max or Revit can exchange Autocad or Revit data with each other. Move a line, resave and the changes will be propagated in the host application.
Live linking files in Rhino would basically be the same — save file in external application or another Rhino session > Rhino sees that the contents of the file have changed and A) prompts to relink B) Relink automatically C) Ignore > if relinked, the contents of the newly saved file are ‘imported’ into Rhino and overwrite the previous imported data.
This is particularly powerful when working with a model from an external application Alias/ Fusion 360/ Blender, etc. and using that base model for patterning/ panelisation with Grasshopper. If you change the original file, say modify a dimension value or two and move some points around, the Grasshopper script should still be working off off the new model once saved and relinked in. So users wouldn’t have to reconfigure which surface to input into the script, etc. Or, have the contents of an urban plan change in a 2d dwg and have the extruded buildings resize with the changed footprint and so on.
E: Come to think of it, I also requested a feature similar to the History Visualiser in Alias a while ago: [History] - Feature requests: query edit & history visualiser, I guess that completes my list, or does it…?