[JBoss JIRA] Commented: (JBIDE-538) first time open of visual editor is slooow
by Sergey Vasilyev (JIRA)
[ http://jira.jboss.com/jira/browse/JBIDE-538?page=comments#action_12378513 ]
Sergey Vasilyev commented on JBIDE-538:
---------------------------------------
It is seemed that the eclipse takes so long time to select an editor from registered editors for such files. If first start of VE takes 1 minute the eclipse takes 50 seconds and VE takes 8-10 seconds only. The same situation is with WTP's Web Page Editor.
I have tried showing "Starting visual editor...", but there is an error in SWT, and after I had disposed the label, the place that was occupied by the label is left until resize a control. Call onResize() method doesn't help.
> first time open of visual editor is slooow
> ------------------------------------------
>
> Key: JBIDE-538
> URL: http://jira.jboss.com/jira/browse/JBIDE-538
> Project: JBoss Tools
> Issue Type: Feature Request
> Components: integration
> Affects Versions: ExadelStudioPro4
> Reporter: Max Andersen
> Assigned To: Sergey Vasilyev
> Priority: Critical
>
> First time a visual editor is opened Eclipse freezes and in the worst case it turns all white.
> I assume this is because of the first start of the mozilla engine.
> We should investigate if it wouldn't be possible to start this in the background; showing a "Starting visual editor...." in the visual part of the editor until it is ready.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month
[JBoss JIRA] Created: (JBIDE-937) Classname not being picked up from DTP (inconsistently)
by Max Andersen (JIRA)
Classname not being picked up from DTP (inconsistently)
-------------------------------------------------------
Key: JBIDE-937
URL: http://jira.jboss.com/jira/browse/JBIDE-937
Project: JBoss Tools
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.Beta3
Reporter: Max Andersen
Assigned To: Denis Golovin
Priority: Critical
Fix For: 2.0.0.Beta4
I can still sometime create a db connection that does result in the driver class not being returned by the connection.
JBIDE-689 is the same, but this was fixed by removing the first dialog with the option of 5-6 concrete types of connections and always use the JDBC profile.
The issue is not in that end, but the driver profile end; here when selecting Generic Driver it always works - but when i use a HSQL driver I*sometimes* get into the situation.
So we should:
1) allow users to choose if they want the specific connection (not always use generic)
2) validate if the profile actually have a driver class in wizard and not allow it to finish before a connection which return a driver class is found. (this will only affect those who are unlucky to bump into this issue - all the rest wont be affected)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 1 month