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
{{ message }}
This repository has been archived by the owner on Feb 22, 2019. It is now read-only.
This route shall provide generic rendering of EObject/CDOObject on GET request - attributes in a table, references as AJAX-loaded tabs. PUT/POST shall take information from request parameters. They shall recognize dot and array notation e.g. myprop.supprop[3].
The route shall support adding new elements to references (if permissions allow). Route implementation shall scan for all available concrete EClass'es in the package registry which are compatible with the reference element type. If more than one available then user shall be presented with a tree dialog to choose element type to be created.
It shall also support modification or replacement of existing elements (including 0..1 cardinality) and modification of the object itself.
The route shall rely on jQuery/jQuery UI for server communications and tabs rendering. jWizard JQuery UI plugin may be used for element creation wizards (step 1 - select type, step 2 - fill out form and submit).
JET can be used for server-side templates. Rendering shall be fine-grained allowing to customize how individual structural features are rendered. It can be done in two complementary ways:
a) Using extensions/services approach similar to the routes. b) Using context renderer (which may fall-back to a). The context render may be client device and principal-specific, i.e. it will allow to configure different appearance for different users and clients.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This route shall provide generic rendering of EObject/CDOObject on GET request - attributes in a table, references as AJAX-loaded tabs. PUT/POST shall take information from request parameters. They shall recognize dot and array notation e.g. myprop.supprop[3].
The route shall support adding new elements to references (if permissions allow). Route implementation shall scan for all available concrete EClass'es in the package registry which are compatible with the reference element type. If more than one available then user shall be presented with a tree dialog to choose element type to be created.
It shall also support modification or replacement of existing elements (including 0..1 cardinality) and modification of the object itself.
The route shall rely on jQuery/jQuery UI for server communications and tabs rendering. jWizard JQuery UI plugin may be used for element creation wizards (step 1 - select type, step 2 - fill out form and submit).
JET can be used for server-side templates. Rendering shall be fine-grained allowing to customize how individual structural features are rendered. It can be done in two complementary ways:
a) Using extensions/services approach similar to the routes. b) Using context renderer (which may fall-back to a). The context render may be client device and principal-specific, i.e. it will allow to configure different appearance for different users and clients.
The text was updated successfully, but these errors were encountered: