Skip to content
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

Add vendor agnostic default window size and position settings to the App Directory app definition format #564

Open
Tracked by #657 ...
kriswest opened this issue Jan 24, 2022 · 1 comment
Labels
app-directory enhancement New feature or request help wanted Extra attention is needed needs-pr

Comments

@kriswest
Copy link
Contributor

Enhancement Request

Most container/Desktop Agent vendors support the configuration of a default window size (in pixels) and position (in pixels or positional hints such as 'center') for applications, which can currently be specified in a host manifest. Given the common occurrence and form of these configurations, it may be advantageous to create vendor-agnostic properties for these settings within the application definition. Adherence to the values specified in any such properties should be optional but recommended (SHOULD).

Use Case:

  • Default window sizes and positions for applications are usually supported by Desktop Agents/containers, however, there is currently no vendor-agnostic way of specifying these settings in an AppD app definition.
    • Providing vendor-agnostic support for common settings saves publishers of AppD records from having to provide multiple hostManifests defining behaviour in proprietary formats.

Additional Information

Note: the Web Application Manifest specification does NOT support size and position properties, instead it defines display modes (e.g. "fullscreen", "standalone", "minimal-ui", "browser") and orientation ( "any", "natural", "landscape", "portrait", "portrait-primary", "portrait-secondary", "landscape-primary", or "landscape-secondary"). These are better suited to mobile and tablet applications than those used on a financial services desktop. Further, the form factor of a desktop container is often different to that of a desktop browser (with more applications sharing the screen at the same time), leading to different requirements for the initial display of a newly launched application.

@kriswest
Copy link
Contributor Author

App D discussion group outcome: This is likely to be a candidate for standardisation in future, but maybe best done after more AppDs have been published and there are more examples of proprietary manifests to draw on for the design.

@kriswest kriswest added this to the 2.1-candidates milestone Feb 7, 2023
@kriswest kriswest modified the milestones: 2.1-candidates, 2.2 candidates Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app-directory enhancement New feature or request help wanted Extra attention is needed needs-pr
Projects
None yet
Development

No branches or pull requests

1 participant