View source for Visual Page Designer

==Look and Feel==
#The designer canvas should sport a ‘clean’ look
##Add more space between components
##Use softer/lighter color for component boundaries. 
##Don’t highlight non-visual components.
###Show the source in a separate page
###*We can support both the split-pane design and a separate source tab. Thus we can four pages:
###**Design-Source split-pane
###**Design
###**Source
###**Preview
#Improve selection of components
##Highlight the component boundary that ‘has’ the mouse cursor
##Use a dark color to highlight the component to be selected
##Display a tool tip with just the name of the component
##Show the selected component using a dotted line with the color used to highlight the component.
##Use anchor points on the selected components only if the component can be resized
##Provide visual cues to help place the cursor before or after a component (instead of selecting the component) 
##Provide decorations on the canvas to represent hidden component(s) that can be used to select it.
##Provide a crumb trail that shows the parent-child hierarchy of the currently selected component. The crumbs are hyperlinks that help in navigating/selecting a component in the hierarchy.
##The outline view should list all the components in the current page. User can use this view to select the components.
##Provide Context-menus to aid in selection 
###Select Parent component – show the name of the parent
###Select child component, facets – display list of names of the child components, facets
###Place cursor before or after the currently selected component
==Render==
#Render both visual and non-visual tags
#Represent non-visual tags including views, forms, facets, directives, converters etc. as (rectangular) objects or appropriate decorations on the canvas
#Provide an option to render included pages and subviews in the including page. The included content is not editable
#Provide an option to show/hide components in the designer.
##Render hidden components as decorations on the canvas.
##Provide a context-menu to show/hide the component. (A selected component can have a special decoration that , when clicked, pops up a context menu with the show/hide option)
#Pluggable rendering
##Placeholder for a pluggable, extensible rendering mechanism
==Add==
#DND should follow standard UI practice
##Current behavior doesn’t require you to hold the LMB to drag the component to the canvas (find this to be a better mechanism)
#Provide visual clue of the drop target
##Facets should be included as a drop target
#Validate the drop target. Provide visual clue for invalid targets
#Support DND to add to the Outline view and the Source tab view
##*DND on Outline view might violate UI guidelines
#Provide context menus to add a filtered list of valid components
##Add before, inside, after the selected component
##Add inside supported facets
#Support context menus to add in the graphical canvas and Outline View (and Source tab?)
==Edit==
#Enhancements to the Property view
##Use standard meta-data mechanism to provide extensibility
##Invoke wizards for complex properties?
#Clean-up Context menu options 
#Improve DND support for moving selected components
#Provide mechanism to visually link related components (‘for’ attribute)
#Support in-pace editing of text for static  text, commandbutton, outputtext , outputlabel etc.
==Palette View==
#Option to configure view as a fly-out view of the designer canvas or a separate view
#Provide a filter to select the components displayed in the view
#*Filter by select libraries, component type, recently used, favorites
#*Custom filters?
==Context menus on the designer==
#Organize/re-arrange menu options in a standard and predictable manner
#Select options (copied)
##Select Parent component – show the name of the parent
##Select child component, facets – display list of names of the child components, facets
#Place cursor before or after the currently selected component
#Add options (copied)
##Show only valid components to add
##Add before, inside, after the selected component
##Add inside supported facets
##Navigate to related artifacts
###Context menu on the component to navigate to appropriate section in the application configuration resource file 
###Context menu on the component to navigate to associated Java class 
###*Managed bean class 
###*Listener class 
###*Validator class 
==Outline View==
#An option to display the ‘logical’ view that includes supported facets of a component (more generic?)
#Enable adding of components from the palette by DND on to the view
#*Currently DND is supported within the view
#Provide context menu similar to those in the designer
==Validation==
==VPD Preference Page==
#Show/Hide tool tip on the page
#Show/hide non-visual components


;[[JSF Tools Project | Back to JSF Tools Project Wiki Home]]