[JBoss JIRA] (JBIDE-18070) New JPA field wizard: content assist for field type is not available
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18070?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18070:
---------------------------------------------
it seem to work sometimes and others not.
Also one have to type in the *full* package name to get completion for classes inside the current package or project.
I think this needs a much improved overhaul - better to push after cr1/ga. wdyt [~gastaldi]
> New JPA field wizard: content assist for field type is not available
> --------------------------------------------------------------------
>
> Key: JBIDE-18070
> URL: https://issues.jboss.org/browse/JBIDE-18070
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> In the "JPA: New Field" wizard, there's a lightbulb before the "Field Type" textfield, which would indicate that content assist is available (which would avoid having to click on the {{Browse...}} button), but nothing appears when doing the Ctrl+space (or Cmd+Space) key.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18183) Enhancement to custom jmx provider UI
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18183?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18183:
----------------------------------------
Assignee: Rob Stryker
> Enhancement to custom jmx provider UI
> -------------------------------------
>
> Key: JBIDE-18183
> URL: https://issues.jboss.org/browse/JBIDE-18183
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx
> Affects Versions: 4.2.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> Currently, each JMX provider has a UI mapped to it, and the UI assumes only 1 icon for each provider.
> Fuse Tools has several server types that behave identically, but require different icons. This could be worked around by declaring 4 or 5 different providers, and accompanying xml indicating different icons, but this is a lot of overhead and would make the code much more complex.
> A simpler solution is to allow an image provider to be part of the extension point. The image provider could then pull the Image from the server type ui (declared in wtp's api). This would also instantiate fewer images by re-using those already instantiated for wtp.server.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months