-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the Application schema #437
Conversation
e0440f9
to
4ae6e31
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added in some suggested changes around typos and phrasing. Otherwise this looks really good.
Co-authored-by: Terry Thorsen <terry@chartiq.com>
Co-authored-by: Terry Thorsen <terry@chartiq.com>
Co-authored-by: Terry Thorsen <terry@chartiq.com>
Co-authored-by: Terry Thorsen <terry@chartiq.com>
Co-authored-by: Terry Thorsen <terry@chartiq.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kriswest @ggeorgievx @mattjamieson is it okay to merge this as in interrim change on the road to 2.0, even though discussions around AppD are still ongoing? I am happy to do so, if you are.
I concur. I fully expect to have a further debate on #468 early in the new year + about how to improve appD further. I've just realised I have a few small review comments pending, I'll submit those now as I think they need dealing with before we merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Several of my comments have already been dealt with however I think we should adjust the examples so that we're not dependent on external applications/domains + a changelog entry is needed.
src/app-directory/specification/examples/application/fdc3-tradingview-chart-orig.js
Outdated
Show resolved
Hide resolved
Co-authored-by: Kris West <kris@cosaic.io>
Update CHANGELOG.md
@kriswest Thank you for the feedback, Kris! I just updated the example application to FDC3 Workbench and also noted all changes inside of the changelog. Please let me know if you have any additional comments/feedback. |
module.exports = { | ||
appId: 'fdc3-workbench', | ||
name: 'FDC3 Workbench', | ||
type: 'browser', | ||
details: { | ||
url: 'https://fdc3.finos.org/toolbox/fdc3-workbench/' | ||
}, | ||
hostManifests: { | ||
Glue42: { | ||
type: 'window', | ||
icon: 'https://fdc3.finos.org/docs/assets/fdc3-logo.png', | ||
details: { | ||
height: 640, | ||
width: 560, | ||
left: 120, | ||
top: 120, | ||
mode: 'tab', | ||
allowChannels: true, | ||
loader: { | ||
enabled: true, | ||
hideOnLoad: true | ||
} | ||
}, | ||
customProperties: { | ||
folder: 'FDC3 Toolbox' | ||
} | ||
} | ||
} | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The example might as well be exhaustive so I've populated the rest of the optional fields. I've also tweaked it to be valid JSON in case someone needs to copy/paste or we want to switch the example to a JSON file in future. Finally, I've added the Finsemble config example.
@ggeorgievx will need you to run this through the test to make sure it still validates.
module.exports = { | |
appId: 'fdc3-workbench', | |
name: 'FDC3 Workbench', | |
type: 'browser', | |
details: { | |
url: 'https://fdc3.finos.org/toolbox/fdc3-workbench/' | |
}, | |
hostManifests: { | |
Glue42: { | |
type: 'window', | |
icon: 'https://fdc3.finos.org/docs/assets/fdc3-logo.png', | |
details: { | |
height: 640, | |
width: 560, | |
left: 120, | |
top: 120, | |
mode: 'tab', | |
allowChannels: true, | |
loader: { | |
enabled: true, | |
hideOnLoad: true | |
} | |
}, | |
customProperties: { | |
folder: 'FDC3 Toolbox' | |
} | |
} | |
} | |
}; | |
module.exports = { | |
"appId": "fdc3-workbench", | |
"name": "fdc3-workbench", | |
"title": "FDC3 Workbench", | |
"description": "Development and test tool for FDC3 desktop agents and apps", | |
"version": "1.0.0", | |
"tooltip": "FDC3 Workbench", | |
"icons": [ | |
{ | |
"url": "http://fdc3.finos.org/toolbox/fdc3-workbench/fdc3-icon-256.png" | |
} | |
], | |
"images": [ | |
{ | |
"url": "https://fdc3.finos.org/docs/assets/fdc3-logo.png", | |
"tooltip": "FDC3 logo" | |
} | |
], | |
"contactEmail": "fdc3@finos.org", | |
"supportEmail": "fdc3-maintainers@finos.org", | |
"publisher": "FDC3", | |
"intents": [ | |
{ | |
"name": "ViewChart", | |
"displayName": "View Chart", | |
"contexts": ["fdc3.instrument"] | |
} | |
], | |
"type": "browser", | |
"details": { | |
"url": "https://fdc3.finos.org/toolbox/fdc3-workbench/" | |
}, | |
"hostManifests": { | |
"Glue42": { | |
"type": "window", | |
"icon": "https://fdc3.finos.org/docs/assets/fdc3-logo.png", | |
"details": { | |
"height": 640, | |
"width": 560, | |
"left": 120, | |
"top": 120, | |
"mode": "tab", | |
"allowChannels": true, | |
"loader": { | |
"enabled": true, | |
"hideOnLoad": true | |
} | |
}, | |
"customProperties": { | |
"folder": "FDC3 Toolbox" | |
} | |
}, | |
"Finsemble": { | |
"window": { | |
"left": 120, | |
"top": 120, | |
"width": 800, | |
"height": 750, | |
"options": { | |
"minWidth": 75 | |
} | |
}, | |
"foreign": { | |
"components": { | |
"App Launcher": { | |
"launchableByUser": true | |
}, | |
"Toolbar": { | |
"iconURL": "http://fdc3.finos.org/toolbox/fdc3-workbench/fdc3-icon-256.png" | |
}, | |
"Window Manager": { | |
"FSBLHeader": true, | |
"persistWindowState": true | |
} | |
} | |
}, | |
"interop": { | |
"autoConnect": true | |
} | |
} | |
} | |
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although I think there will definitely be further changes, I think this PR can be merged as its an improvement on the current state.
@ggeorgievx I've suggested a change to the example that I'd appreciate you integrating (and giving a quick test) before we merge.
@kriswest Thank you, Kris! I updated the example and ran the test successfully. We should be ready to go on this one. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Resolves #314
fdc3.general.app.manifest
manifest type describing an application #314:manifestType
propertymanifest
propertytype
propertydetails
propertyhostManifests
property (a mapping from host string to host specific application manifest object or URI instead of an array)Notes:
type
property are browser and host - host would allow application providers to serve applications other than browser onesdetails
are not marked as required as they are only needed when the application type is browser. Host type applications should use thehostManifests
object for all application details.hostManifests
is a mapping from host string to host specific application manifest object or URI (added URI for better backwards compatibility as some vendors used URI manifests)