Community
Participate
Working Groups
We have two cases where we generate simple HTML5 UI fields: - command slideouts - settings We also have similar needs where at some point a client can hook in and fill in their own UI - command slideout/find replace - settings/profile page At some point we should look at both these approaches and unify the code so that the same code is generating fields in either case. Anton has done work where widgets can be used in the case where the HTML5 stuff is not mature, etc. Possibly there are common API models for inserting your own UI (not sure about this one). This might be something to look at after 0.5 once we have more experience with both of these. The Eclipse equivalent of this is JFace field editors.
Another level of potential commonality is in the specification of the types for generated fields from an API point of view. For example: A plugin can say it has a preference of a certain type, and perhaps a set of ranges, or potential values, or whatever. Likewise, a command parameter can say what type it is (currently HTML5 text types, but this is going to evolve similarly into things like toggles, etc.) Perhaps this is a different bug. The plugin case is more general, so maybe I can just watch that and adapt command parameter types accordingly. We currently don't expose the command parameter concept into plugins, it's just used internally.
(In reply to comment #1) > Another level of potential commonality is in the specification of the types for > generated fields from an API point of view. gcli has yet another way of specifying types (for console command arguments), we should extract commonality there also.
(In reply to comment #2) > (In reply to comment #1) > > Another level of potential commonality is in the specification of the types for > > generated fields from an API point of view. > > gcli has yet another way of specifying types (for console command arguments), > we should extract commonality there also. see also bug 378420
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html
