[
https://jira.jboss.org/jira/browse/JBIDE-2588?page=com.atlassian.jira.plu...
]
arne anka commented on JBIDE-2588:
----------------------------------
yes, i found taht already (though the slider's description could use a bit
elaboration, it's not clear which direction to push).
but i still find it confusing and no good design to have both on one tab and the little
triangles on bottom, too.
my point still stands: source editing and visual editzing are different things to be
addressed by different tabs.
having both active on one tab, there's not enough space for either one and
cumbersome.
how big is the chance that somebody does source editing and visual editing at the same
time and thus needs _both_ editors on one tab?
VPE on separate tab w/ lazy initialization
------------------------------------------
Key: JBIDE-2588
URL:
https://jira.jboss.org/jira/browse/JBIDE-2588
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor
Environment: debian/unstable, linux 32bit, eclipse 3.4
Reporter: arne anka
Priority: Optional
Attachments: vpe.png
the vpe should reside on a separate tab, not together with source, and it should
initialize only when openend.
rationale:
i am no big fan of visual editors but can imagine that there are situations when i might
find it useful.
so, when editing pages i do it with the source editor. having the vpe on the same tab it
occupies space, even minimized, and is confusing -- a clean separation is desirable
(source|visual|preview).
additionally, the visual editor is initialized when the source editor is opened,
regardless whether i ever use it. having the visual editor on it's own tab would allow
lazy initialization, saving resources.
re the versions: i see "Richfaces VPE Feature 2.0.0.200807200019-nightly", not
clear to me which of the numbers in the selects above fits.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira