[
https://jira.jboss.org/jira/browse/JBIDE-2648?page=com.atlassian.jira.plu...
]
Yura Zhishko commented on JBIDE-2648:
-------------------------------------
No, we use the same classes for both dialog's but some functionality is defference.
We've made a next decisions:
1) Preview field says "Double click to edit" and that works but it is very hard
to get it to loose focus again - how are users expected to do this ?
Decision: We'll make a next message "Double click to edit. To save changes press
Enter button". After editing user presses Enter button and looses focus.
2) What is the Preview tab for ? It says "CSS file to edit will be displayed
here" ?
Decision: Preview tab is for observing of chosen CSS file content. This tab will be hidden
if no CSS file has been chosen. For style dialog this tab will be always hidden.
3) Where is the file to edit/class fields which are present when you do Ctrl+N ?
Decision: Such file will appear in fields if you use Ctrl+N only on active CSS file or on
the CSS file from tree of projects
4) I get the following trace when clicking the Preview tab:
That was fixed
5) The propertysheet is using some weird Courier font for the top level elements - why ?
---
--- What would you like to see, Max? Do you propose to use the same font as for the low
levels?
6) I cannot find any way to edit or select external css styles for a field (related to
3)----
--- Do you mean that user should be able to select external CSS files from any project of
existing workspace or from all hard disk space?
UI Suggestions for css editor
-----------------------------
Key: JBIDE-2648
URL:
https://jira.jboss.org/jira/browse/JBIDE-2648
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor Templates
Affects Versions: 3.0.0.alpha
Reporter: Max Rydahl Andersen
Assignee: Igor Zhukov
Fix For: 3.0.0.cr1
Attachments: cssstyle_editor.png
Some simple improvements suggestions:
1) Allow users to type in their own text to preview (or at least try and grab the text
used within the element we are styling from)
2) Show what the textual CSS styling result will be (on a seperate tab?)
3) Add a splitpane to allow adjustment of the rendered preview
4) If the quick edit is intended to be what most people would like to do most often then
it should be the first tab or at least the tab it opens up on by default
--
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