]
Maxim Areshkau commented on JBIDE-675:
--------------------------------------
I have applied in my local working copy a xpcom proxy mehanizm where I founded
modification of DOM.
It's add following benefits:
1) It's helps us to modify DOM in non ui JOB without interrupting user input.
2) Also it's allow us to queue modifications event and in case when user modify some
node several times, we applying only last modification.Without it's we apply all
modifications.
problems:
If in VPE will be some place where DOM will be modified without proxy it's crashes a
eclipse(I can't founded such places now), but we should check all carefully.
If it's suits for us, i can commit my changes.
Also I have tried to apply a delay before update visual preview, it's doesn't
helped.
Large JSF file are too slow to handle, making editor useless for
them
---------------------------------------------------------------------
Key: JBIDE-675
URL:
http://jira.jboss.com/jira/browse/JBIDE-675
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, Visual Page Editor
Affects Versions: ExadelStudioPro4
Environment: Eclipse 3.2.2
Exadel Studio 4.0.4
Kubuntu Feisty Fawn
1G RAM
CPU Intel(R) Pentium(R) 4 CPU 2.80GHz, HyperThreading activated
Reporter: David Delbecq
Assigned To: Maxim Areshkau
Priority: Critical
Fix For: 2.1
Attachments: .classpath, copy_dump.txt, edit_dump1.txt, edit_dump2.txt,
editStructure.txt, JBIDE-675.tar.gz, loading_dump.txt, profiling.tar.gz,
stacktraces-rhd2b1.log.gz, tree.txt
Post to JIRA, following recommandatiopn here:
http://jboss.com/index.html?module=bb&op=viewtopic&t=115447
When editing JSF files That contains quite a lot of include, it take commonly up to 20
seconds for one character i type to get it's way to the screen. I can even see, after
10 seconds, the cursor goes on step right, and after a new 10 second the character appear
in front of the cursor. This make it impossible to use JSF editor from exadel to edit such
file, i have to ressort to plain xml editor without completion for facelets tags.
I will be posting attachement containing description of files involved (sorry, no file
content).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: