You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when you call runApp() and pass in some files, you do this:
runApp(el,"viewer",{startFiles: files},"r")
Where files has type Array<FileContent>.
But I think it makes as much sense for the object that's passed to runApp to contain information about which engine to use. Instead of just an array of files, it would also provide info about how to run the app. So the structure would be something like:
typeAppSpec={engine: AppEngine,files: Array<FileContent>}// This could be loaded from JSONconstapp={engine: "r", files =[ ... ]};runApp(el,"viewer",{appSpec: app})
Unlike some of the other options engine seems inherent to the app; viewerHeight, for example, seems incidental to the app.
The text was updated successfully, but these errors were encountered:
Currently, when you call
runApp()
and pass in some files, you do this:Where
files
has typeArray<FileContent>
.But I think it makes as much sense for the object that's passed to
runApp
to contain information about which engine to use. Instead of just an array of files, it would also provide info about how to run the app. So the structure would be something like:Unlike some of the other options
engine
seems inherent to the app;viewerHeight
, for example, seems incidental to the app.The text was updated successfully, but these errors were encountered: