From jbosstools-commits at lists.jboss.org Tue Mar 16 12:34:19 2010 Content-Type: multipart/mixed; boundary="===============5879620756762108559==" MIME-Version: 1.0 From: jbosstools-commits at lists.jboss.org To: jbosstools-commits at lists.jboss.org Subject: [jbosstools-commits] JBoss Tools SVN: r20846 - trunk/jsf/docs/userguide/en-US. Date: Tue, 16 Mar 2010 12:34:19 -0400 Message-ID: <201003161634.o2GGYJl9001799@svn01.web.mwc.hst.phx2.redhat.com> --===============5879620756762108559== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: abogachuk Date: 2010-03-16 12:34:18 -0400 (Tue, 16 Mar 2010) New Revision: 20846 Modified: trunk/jsf/docs/userguide/en-US/editors.xml Log: https://jira.jboss.org/jira/browse/JBDS-1127 https://jira.jboss.org/jira/browse/JBDS-1132 Modified: trunk/jsf/docs/userguide/en-US/editors.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/jsf/docs/userguide/en-US/editors.xml 2010-03-16 16:06:57 UTC (rev= 20845) +++ trunk/jsf/docs/userguide/en-US/editors.xml 2010-03-16 16:34:18 UTC (rev= 20846) @@ -8,14 +8,10 @@ Editor - Editors In the JSF Tools Reference Guide and Struts Tools Reference Guid= e you had possibility to - read about Graphical Editor for JSF - and Struts configuration - files, Graphical Editor for - Tiles Files, Graphical Editor for - Struts Validation Files. All these editors have OpenOn and @@ -24,39 +20,35 @@ to know a Visual Page Editor = for combined visual and source editing of Web pages and many other editors for different types of files. -
- Editors Features - JBoss Developer Studio has powerful edi= tor features that help you easily navigate - within your application and make use of content and code assis= t no matter what project - file (.jsp, .xhtml, .xml, .css, etc.) you are working on. - The mentioned features are the following: - = - - - OpenOn<= /link> - - - Content Assist - - - Synchronized Source and Visual Editing - - - = + JBoss Developer Studio has powerful edi= tor features that help you + easily navigate within your application and make use of conten= t and code assist no + matter what project file (.jsp, .x= html, .xml, .css, etc.) you are wo= rking on. + The mentioned features are the following: + + + OpenOn + + + Content + Assist + + + Synchronized Source and Visual Editing + +
- OpenOn - - OpenOn lets you easily link directly from one resource to - another in your project without using the Packag= e Explorer view (project tree). With + OpenOn lets you easily link directly from one resource t= o another in your project + without using the Package Explorer vi= ew (project tree). With OpenOn, you can simply use F3 or Ctrl+Click on a reference to another file and the file wi= ll be opened. - OpenOn is available for: @@ -73,163 +65,157 @@ Java files - CSS classes + + CSS classes + - Paths to f= iles set using EL variable + + Paths to files= set using EL + variable + - =
- XML Files - - Press and hold down the Ctrl key. As you move the mouse cursor over different - file references in the file, they display an underline= . When you hover the name - of the file you want to open, click and the file will = open in its own editor. - = - Use the OpenOn functionality for the next entries= defined in XML file: - = - - - Managed beans - In this example the managed bean "User" will open. - = -
- Opening a Managed Bean - - - - - -
- = - This is the result of using OpenOn. - = -
- Opened Managed Bean - - - - - -
- - = - - Beans properties -
- OpenOn for the Bean Property - - - - - -
- - = - - JSP file references -
- OpenOn for JSP Page - - - - - -
- - + Press and hold down the Ctrl key. As + you move the mouse cursor over different file referenc= es in the file, they + display an underline. When you hover the name of the f= ile you want to open, + click and the file will open in its own editor. + Use the OpenOn functionality for the next entries de= fined in XML file: + + + Managed beans + In this example the managed bean <= property + >"User" will open. +
+ Opening a Managed Bean + + + + + +
+ This is the result of using OpenOn. +
+ Opened Managed Bean + + + + + +
+ + + Beans properties +
+ OpenOn for the Bean Property + + + + + +
+ + + JSP file references +
+ OpenOn for JSP Page + + + + + +
+ +
- =
- JSP/XHTML Pages - - OpenOn is also available in JSP and XHTML pages edit= ed in the Visual Page Editor. It will allow - you to quickly jump to the reference instead of having= to hunt around in the - project structure. - - = - You can use OpenOn for the following JSP/XHTML file ent= ries: - = - - - Imported property files -
- OpenOn for Property File Imported to the JSP Page</= title> - <mediaobject> - <imageobject> - <imagedata fileref=3D"images/editors_features/editors_fe= atures_5.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - = - <listitem> - <para>CSS files used in a JSP/XHTML page</para> - <figure> - <title>OpenOn With CSS File - - - - - -
- - = - - Managed beans and their properties -
- OpenOn With Managed Beans - - - - - -
- - = - - Navigation rules in JSP files - = - For JSP files in a JSF project, you can easily open t= he navigation rules - by applying OpenOn to the JSF tag for= the navigation - outcome: - = -
- OpenOn with JSF Tag - - - - - -
- - = - - Custom Facelets tag libraries in XHTML pages = = - For details, see "OpenOn for Custom Facelets Tag Libraries" - later in this guide. - - = - - Custom JJSF 2.0 components = -
- OpenOn with JSF 2.0 Component - - - - - -
= - - + OpenOn is also available in JSP and XHTML pages edit= ed in the Visual + Page Editor. It will allow you to quick= ly jump to the reference + instead of having to hunt around in the project struct= ure. + You can use OpenOn for the following JSP/XHTML file = entries: + + + Imported property files +
+ OpenOn for Property File Imported to th= e JSP Page + + + + + +
+ + + CSS files used in a JSP/XHTML page +
+ OpenOn With CSS File + + + + + +
+ + + Managed beans and their properties +
+ OpenOn With Managed Beans + + + + + +
+ + + Navigation rules in JSP files + For JSP files in a JSF project, you can easi= ly open the navigation + rules by applying OpenOn = to the JSF tag for the + navigation outcome: +
+ OpenOn with JSF Tag + + + + + +
+ + + Custom Facelets tag libraries in XHTML pages= + For details, see "OpenOn + for Custom Facelets Tag Libraries" later in this + guide. + + + Custom JSF 2.0 components +
+ OpenOn with JSF 2.0 Component + + + + + +
+ +
- =
CSS Classes - You can quickly navigate through CSS classes using Op= enOn + You can quickly navigate through CSS classes using O= penOn
OpenOn With CSS Class @@ -238,8 +224,7 @@
- = - OpenOn is also implemented for css classes added by = a complex link. = + OpenOn is also implemented for css classes added by = a complex link.
OpenOn With CSS Class added by a complex link</= title> <mediaobject> @@ -249,34 +234,26 @@ </mediaobject> </figure> </section> - = <section id=3D"openonelvariables"> <title>OpenOn for EL variables OpenOn can be used for paths to files set with EL va= riable. -
- OpenOn for paths to files set with EL variable</ti= tle> - <mediaobject> - <imageobject> - <imagedata fileref=3D"images/editors_features/edit= ors_features_openon_el.png"/> - </imageobject> - </mediaobject> - </figure> - = + <figure> + <title>OpenOn for paths to files set with EL variable<= /title> + <mediaobject> + <imageobject> + <imagedata + fileref=3D"images/editors_features/editors= _features_openon_el.png"/> + </imageobject> + </mediaobject> + </figure> </section> - = </section> - <section id=3D"CodeAssistAndDynamicCodeAssist42BasedOnProjectData"> - <title>Content Assist Content assist is available when wo= rking with - - - Seam project files - - + Seam project files @@ -293,123 +270,121 @@ JSP files - - - XHTML files - - - RichFaces com= ponents + XHTML= files - ESB XML files + RichFaces com= ponents + ESB XML files + + Insert= Tag Wizard - Notice, that code completion for EL variables has icons = illustrating what they are - from. The most of this icons are described in the table below.= + from. The most of this icons are described in the table be= low. Content assist icons - + - Icon - Type - Context + Icon + Type + Context - - - - - - - - - - Enumeration = = - - - - Used to show items which exist in the= predefined set of equivalent proposals. - - - - - - + + + - Seam Proposal + Enumeration - Used to show Seam Context variables,= its properties and methods. = - = - - = + Used to show items which exist in th= e predefined set of + equivalent proposals. + - - - + + + - JSF EL - + Seam Proposal - Used to show Managed Beans, Managed = Bean Properties, Managed Bean Methods, Constants, Resource Bundles, Resourc= e Bundle Properties. = - = - = - + Used to show Seam Context variables,= its properties and + methods. - = - - - + + + - JSF Action - = - + JSF EL - Used to show navigation rules defin= ed in the faces-config.xml . - = + Used to show Managed Beans, Managed = Bean Properties, Managed + Bean Methods, Constants, Resource Bund= les, Resource Bundle + Properties. + + + + + + + + + + JSF Action + + + Used to show navigation rules define= d in the faces-config.xml . + - - - + + + @@ -417,36 +392,30 @@ Used to show Messages Reso= urces items. - = - = - - - + + + - Resource path - + Resource path Used to show paths which are accessi= ble from the cursor place. - = - = - = - =
-
JSF Content Assist @@ -455,7 +424,6 @@
-
Seam Content Assist @@ -464,23 +432,19 @@
- Also, as you can see, the ranking and sorting are availa= ble in EL code completions. -
- JSF Project Files - When working with JSF project in JBoss Developer Stu= dio, you can use various Content Assist features while= developing: - Content Assist for XML, XHTML, JSP and JSF = configuration files - = + Content Assist for XML, XHTML, JSP and JSF c= onfiguration files + Content Assist for Composite Components - = + Content Assist based on project data @@ -488,16 +452,12 @@ Content Assist with graphical JSF editor - =
- Content Assist for XML, JSP and JSF configurati= on files - At any point when working with any XML, JSP and = JSF configuration files Content Assist is available to help you. Simply ty= pe Ctrl-Space to see what is available. - Content Assist for JSF configuration file:
Content Assist in JSF Configuration File</t= itle> @@ -528,29 +488,26 @@ </imageobject> </mediaobject> </figure> - </section> = - = + </section> <section id=3D"ContentAssistforCompositeComponents"> <title>Content Assist for Composite Components - Content assist functionality is also available f= or composite components. On the screen is shown content assist for a compos= ite component file "tag.xhtml" within a JSF= 1.2 project with facelets - = + Content assist functionality is also available f= or composite components. + On the screen is shown content assist for a compos= ite component file + "tag.xhtml" wit= hin a JSF 1.2 project with + facelets
Content Assist for Composite Components</ti= tle> <mediaobject> <imageobject> - <imagedata fileref=3D"images/editors_featu= res/editors_features_ca_composite_component.png" + <imagedata + fileref=3D"images/editors_features/edi= tors_features_ca_composite_component.png" scale=3D"85"/> </imageobject> </mediaobject> </figure> - </section> = - = - = - = + </section> <section id=3D"ContentAssistBasedOnProjectData86"> - <title>Content Assist Based on Project Data - JBoss Developer Studio takes Content Assist to t= he next level. Studio will constantly scan your project and you will be able = to insert code into the JSP page from your project that includes: @@ -590,11 +547,9 @@
In the following screenshot we are inserting a <= emphasis role=3D"italic"> "Managed bean" - attribute value. Again, by simply clic= king - Ctrl-Space,= JBoss - Developer Studio will show a list of all possible = values that you can - insert. - + attribute value. Again, by simply clic= king Ctrl-Space, JBoss D= eveloper Studio will show + a list of all possible values that you can insert.= Once you select a Managed bean, it will show you= a list of all available attributes for the selected Managed bean (userBean= ).
@@ -617,35 +572,32 @@
- = - Code Assist can also provide you with access to = the beans located in jar archives. - = + Code Assist can also provide you with access to = the beans located in jar + archives.
- Code Assist: accessing beans in jar archives</t= itle> - <mediaobject> - <imageobject> - <imagedata fileref=3D"images/editors_features/= editors_features_14_a.png" - /> - </imageobject> - </mediaobject> + <title>Code Assist: accessing beans in jar archive= s + + + + +
- Moreover Code Assist is abl= e to define Resource Bundles on template page and give= s the proposals on the client page. + Moreover Code Assist is abl= e to define Resource Bundles on template page = and gives the proposals on + the client page.
Code Assist: Message Bundles proposals from= template page - + - =
- = - =
- Content Assist within Tree JSF Editor - JBoss Developer Studio also provides Content Ass= ist when working within the Tree JSF configuration editor. Just click Ctrl-Space. @@ -658,7 +610,6 @@
-
-
Struts Project Files Content Assist features are available when you work = with Struts projects. - -
- - Content Assist for Struts Configuration File</t= itle> - <para>Content Assist helps you in Struts Configuration= file.</para> - <figure> <title>Struts Content Assist @@ -769,11 +713,8 @@
- Content Assist for Struts JSP File - Using Code Assist in Struts JSP file is shown be= low. -
Struts JSP Content Assist @@ -786,15 +727,10 @@
- JSP Pages - -
- Content Assist for JSF Tags JBDS provides full code completion for JSF tags:= -
JSF Tags Content Assist @@ -816,10 +752,8 @@
-
- Content Assist for JSTL Tags
JSTL Tags Content Assist @@ -832,7 +766,6 @@
- Content Assist for HTML Tags Content assist for HTML tags has the same mechan= ism as for JSF tags: @@ -857,7 +790,6 @@
- Content Assist for JavaScript Tags
JavaScript Tags Content Assist @@ -870,26 +802,27 @@
- -
- Content Assist for XHTML Pages - = - The code completion for the Seam components in a Seam proj= ect shows the proposals marked with Seam icon. -
- Content Assist for Seam Components in the XHTML Page</ti= tle> - <mediaobject> - <imageobject> - <imagedata fileref=3D"images/visual_page/contentAssistXHTMLpa= ges1.png"/> - </imageobject> - </mediaobject> - </figure> - = - <para>If XHTML file uses custom Facelets components, the Content= Assist should also be available for them. For details, see - <link linkend=3D"contentAssistForCustomFacelets">"Content = Assist for Custom Facelets Components"</link> later in this guide.</pa= ra> - </section> + <section id=3D"ContentAssistForXHTMLPages"> + <title>Content Assist for XHTML Pages + The code completion for the Seam components in a Sea= m project shows the + proposals marked with Seam icon. +
+ Content Assist for Seam Components in the XHTML= Page + + + + + +
+ If XHTML file uses custom Facelets components, the C= ontent Assist should also + be available for them. For details, see "C= ontent Assist for Custom + Facelets Components" later in this gui= de. +
Content Assist for Insert Tag Wizard - Content Assist is also available for any attribute v= alue of Insert Tag wizard. + Content Assist is also available for any attribute v= alue of Insert + Tag wizard.
Content Assist for Insert Tag Wizard @@ -898,11 +831,8 @@
- =
- =
- Adding dynamic code assist to custom components tha= t were added to JBoss Tools Palette Here is what you need to do to add project based cod= e assist to a custom @@ -922,8 +852,7 @@ Adds code assist for JSF pre-defined objects= , such as - value=3D"#{param}" - : + value=3D"#{param}" = : @@ -987,15 +916,16 @@ uri=3D"http://www.jenia.org/jsf/dataTools"/>]]> - Restart Eclipse. You should now have code as= sist for the component. - From JBoss Developer Studio 3.0.0.M1 you should not do any of the steps described = - before,dynamic code assist to custom components is added a= utomatically. - If you open projects that were created in older stud= io versions such message could appear: + From JBoss Developer Studio 3.0.0.M1 you should not do + any of the steps described before,dynamic code assist = to custom components is + added automatically. + If you open projects that were created in older stud= io versions such message + could appear:
Missing Natures Message @@ -1004,28 +934,33 @@
- It shows that some features of content assist includ= ing this one probably will not work. - To fix this problem and turn off the message box execu= te the following steps: + It shows that some features of content assist includ= ing this one probably will + not work. To fix this problem and turn off the message= box execute the following + steps: - Right click the project in Package Exp= lorer. - Select Configure -> Add JSF = Capabilities from the context menu. - Configure your project using Add JSF C= apabilities wizard and press Finish + + Right click the project in Package Explorer.= + + + Select Configure -> Add JSF Capabi= lities from the + context menu. + + + Configure your project using Add JSF Capabil= ities wizard and press + Finish +
- Synchronized Source and Visual Editing - JBoss Developer Studio offers the f= lexibility to edit any files in either source or extra visual modes at the same t= ime. - The project is yours and so is the source. JBo= ss Developer Studio provides you many different graphica= l editors to speed your application development. At the same time, you always have= a full control over all project source files. Any changes you make in the source v= iew immediately appear in the graphical view. - The JSF configuration file editor has three views: Diagram, Tree and Source. All views are synchronized, you can edit the file in any view. @@ -1038,13 +973,10 @@ - The same is relevant to all other JBoss Develo= per Studio editors. - Web XML editor is shown. Web XML editor has a graphical = view (Tree) and source (Source). -
Two Views are Synchronized @@ -1054,7 +986,6 @@
- JBoss Developer Studio TLD file edi= tor is shown in Tree view. At any point you can edit the source by switching to Sourc= e view.
@@ -1066,29 +997,31 @@
-
- Visual Page Editor - JBoss Developer Studio comes with a pow= erful and customizable Visual Page Editor (VPE). You can use= the Visual Page Editor to - develop an application using any technology: JSF, Struts, JSP,= HTML and others. Double-click on the necessary file in the Package Explore= r view to open it in the Visual Editor or just drag-and-drop it into perspe= ctive (the drag-and-drop feature can be also applied to JSP, XHTML or HTML = files created locally). - - As a new JSF 2.0 specification has been released, support of = new features is now implemented in the Visual Page Editor. - The JSF 2.0 tags like <h:body>, = <h:head>, <h:outputscript>, <h:outputstyle> - are supported in the editor as well as the composite components an= d the resource handling from the expression language. (See the fo= llowing link on how to use composite components and = - following blog post on how to handle the resources form the EL). - - = - Current VPE version has three tabs: Visual/Source, - Source and Preview. To switch between the - views you can use tabs at the bottom of the VPE or the shortcu= ts + develop an application using any technology: JSF, Struts, JSP,= HTML and others. + Double-click on the necessary file in the Package Explorer vie= w to open it in the Visual + Editor or just drag-and-drop it into perspective (the drag-and= -drop feature can be also + applied to JSP, XHTML or HTML files created locally). + As a new JSF 2.0 specification has been released, support of= new features is now + implemented in the Visual Page Editor. Th= e JSF 2.0 tags like + <h:body>, <h:head>= , <h:outputscript>, <h:outputst= yle> are + supported in the editor as well as the composite components an= d the resource handling + from the expression language. (See the following + link on how to use composite components and following blog + post on how to handle the resources form the EL). = + Current VPE version has three tabs: Visual/Source<= /property>, Source and Preview. To sw= itch between the views you + can use tabs at the bottom of the VPE or the shortcuts Ctrl + PageUp/Ctrl + PageDown . -
Visual Page Editor @@ -1097,10 +1030,8 @@
-
Visual/Source View - Using the Visual/Source view you ca= n edit your pages in the Source and Visual modes simultaneously having an instant s= ynchronization between them: @@ -1112,11 +1043,9 @@ - The view is designed in the form of a split pane with to= ggle buttons for quickly moving between Source, Visual or Source/Visual modes as sh= own on the figure above. - One more way to toggle between the various states of the= split pane is using the shortcuts Shift + F6 @@ -1128,7 +1057,6 @@ When editing large documents hiding the Visual part = will speed up the editing. - It should be pointed out that, no matter in what mode yo= u are working, you get a full integration with Properties and = Outline views: @@ -1140,12 +1068,16 @@ - - - The Outline view displays a specific outline of a struct= ured file that is currently open in the editor area, and lists its structur= al elements. Right-click on the elements will open additional options that = allow adding other specific elements in necessary positions. - The Properties view shows property names and their value= s for a selected item. The values are editable, just select any and click o= n the button that appeared to choose a new value. Key combination Ctrl+Z will return the previous value, Ctrl+Y will return the new value again. The Properties view has additional opt= ions and can be set up to display categories and advanced properties. - - + The Outline view displays a specific outline of a struct= ured file that is + currently open in the editor area, and lists its structura= l elements. Right-click on + the elements will open additional options that allow addin= g other specific elements + in necessary positions. + The Properties view shows property names and their value= s for a selected item. The + values are editable, just select any and click on the butt= on that appeared to choose + a new value. Key combination Ctrl+Z w= ill return the previous + value, Ctrl+Y will return the new val= ue again. The Properties + view has additional options and can be set up to display c= ategories and advanced + properties. It's also possible to use the JBoss Tools Palette to insert any tag from the list of tag = libraries to the page you are editing with just a click or drag-and-drop. @@ -1160,10 +1092,9 @@ You can insert a tag/component from the palette into ei= ther the Source or the Visual part by calling a context menu and selecting Insert around, Insert before,= Insert - after or Replace With,= pointing to - From Palette, picking the type of= the tag and finally - choosing the tag you want to insert. - + after or Replace With,= pointing to From Palette, picking the type of the tag = and finally choosing the + tag you want to insert. The image below illustrates how you can insert a tag int= o the Source part.
Inserting a tag into the Source part @@ -1173,9 +1104,7 @@
- And this is how a tag is inserted using a context menu i= n the Visual part. -
Inserting a tag into the Visual part @@ -1184,10 +1113,10 @@
- = - Visual Page Editor also displays custom tags correctly i= f they are configured properly. - The picture below shows an example how custom tags "pagination" and = "echo" will be displayed in VPE. - + Visual Page Editor also displays custom tags correctly i= f they are configured + properly. The picture below shows an example how custom ta= gs "pagination" and = "echo" will be di= splayed in VPE.
Custom Tags in the VPE @@ -1196,21 +1125,19 @@
- - The listings of the custom tags implementations will help = to clear how VPE works. - - = - - echo.xhtml: = - The listings of the custom tags implementations will he= lp to clear how VPE works. + + + echo.xhtml: + #{msg} -]]> = - = - paginator.xhtml: - = - + + + paginator.xhtml: + @@ -1239,11 +1166,10 @@ ]]> - - - - If your custom tags aren't configured correctly your = Visual mode will look like this: = - + + + If your custom tags aren't configured correctly yo= ur Visual mode will look + like this:
Wrong configured Custom Tags in the VPE @@ -1252,26 +1178,22 @@
- =
Commenting out Code - VPE supports possibility to add= comments in files you are working with (JSP, XHTML, etc.): - - HTML comments (<!-- -->) = which are output to the client + HTML comments (<!-- -->) = which are output to the + client - JSP comments ( - <%-- --%> + JSP comments ( <%-- --%> ) which are not output to the client as= part of the JSP page output
-
Using Code Folding @@ -1288,7 +1210,6 @@ ) will appear on the left margin = of the editor next to each opening block tag. -
Enabled Code Folding @@ -1297,9 +1218,7 @@
- Click the minus sign to collapse a block tag. - When the minus sing is clicked on the appropriate ta= g collapses and a plus sing ( @@ -1311,7 +1230,6 @@ ) appears after opening and closi= ng tags. -
Collapsed Code @@ -1320,54 +1238,44 @@
-
-
- JSP Syntax Validation When working in JBoss Tools JSP editor you are const= antly provided with feedback and contextual error checking as you type.
-
Support for custom TagLibs and Taglib versions</tit= le> - <para>VPE templates support custom tag libs, e.g. Seam M= ail facelet taglib, RichFaces taglibs or any other created by you.</para> - - <para>VPE templates also provide a support for various ve= rsions of tag libraries. It means that the - <property>VPE</property> takes control over those = components which have - different parameters or preview according to the frame= work version (like seam - 1.2 and seam 2.0, or JSF 1.1 and JSF 1.2).</para> - - <para>For example, <code> - <s:decorate> - </code> element in seam has different parameters in ve= rsions 1.2 and 2.0 as - well as = - <code><h:outputLink></code> - JSF element has different preview in versions 1.1 and= 1.2.</para> + <para>VPE templates support custom tag libs, e.g. Seam Mai= l facelet taglib, + RichFaces taglibs or any other created by you.</para> + <para>VPE templates also provide a support for various ver= sions of tag libraries. It + means that the <property>VPE</property> takes control = over those components + which have different parameters or preview according t= o the framework version + (like seam 1.2 and seam 2.0, or JSF 1.1 and JSF 1.2).<= /para> + <para>For example, <code> <s:decorate> + </code> element in seam has different parameters in ve= rsions 1.2 and 2.0 as well + as <code><h:outputLink></code> JSF element has d= ifferent preview in + versions 1.1 and 1.2.</para> </section> </section> - = <section id=3D"pages_styling"> <title>Pages Styling - Most web pages use the cascading style sheets (CSS) to c= ontrol the way they look. - With Visual Page Editor you can easil= y stylise your pages. In - this section we are going to introduce you to a powerful m= echanism that - VPE provides for a complete control o= ver pages styling. More helpful information on wok with CSS files can be fo= und in CSS Perspective chapter - + With Visual Page Editor you can easil= y stylize your pages. In + this section we are going to introduce you to a powerful m= echanism that VPE provides for a complete control over p= ages styling. More helpful + information on work with CSS files can be found in CSS Perspective chapter +
Inline Style Editing - In the Visual part of the VPE t= here is a graphical toolbar, use it to add inline styling to JSF and Strut= s tags on your page. The - toolbar can be hidden with the help of the special but= ton ( = - - - - - ) on the VPE toolbar. - + toolbar can be hidden with the help of the special but= ton ( + + + + ) on the VPE toolbar.
Text Formatting @@ -1376,13 +1284,11 @@
- - For editing inline styles for DOM elements VPE = - provides the CSS Dialog. It can b= e called from + For editing inline styles for DOM elements VPE provides + the CSS Dialog. It can be called = from style line in the Properties view for a currently selected element. -
Call the CSS Dialog @@ -1391,12 +1297,11 @@
- - CSS Style Dialog has several tabs where css - properties for text, background, borders and others ca= n be specified. A simple - preview which is generated at the top of the CSS Style Dialog - allows you to see the changes before you apply them. - + CSS Style Dialog has several tabs where + css properties for text, background, borders and other= s can be specified. A + simple preview which is generated at the top of the CSS Style + Dialog allows you to see the changes be= fore you apply + them.
CSS Style Dialog @@ -1406,7 +1311,6 @@
-
External Stylesheets The pages you are working with in VPE can use external @@ -1417,7 +1321,6 @@ button next to styleClass field in Properties view. -
Calling the Edit Style Class Dialog @@ -1426,7 +1329,6 @@
- It'll pick up the Edit Style Class Di= alog which looks like on the figure below:
@@ -1437,38 +1339,40 @@
- = - Choose a style class from the variants provided and = click on the Ok button to apply the changes. - = + Choose a style class from the variants provided and = click on the Ok button to apply the changes. To open a CSS dialog based on the active CSS file cl= ick on - - - - in the top panel or use hot-keys (Shift+Ctrl+C). - = - To create a new CSS class for the file click on the = Add CSS Class button, write its name in the field appe= ared and click on the Ok button: - = -
- Add CSS Class - - - - - -
- = - Then you can configure style settings switching b= etween the tabs: + + + + in the top panel or use hot-keys = (Shift+Ctrl+C). + To create a new CSS class for the file click on the = Add CSS + Class button, write its name in the fie= ld appeared and click on + the Ok button: +
+ Add CSS Class + + + + + +
+ Then you can configure style settings switching betw= een the tabs: Text/Font, Background, Boxes, - Property Sheet. Th= e list of already existing classes with names beginning with the symbols pr= inted will be displayed on standard "Ctrl+Space" key combination. To add ex= isting styling to - the chosen element just point to the - necessary one. Each time you select any class it is di= splayed in the Preview tab. Click on the Apply button will apply the changes without closing the window. - -
+ Property Sheet. Th= e list of already existing + classes with names beginning with the symbols printed = will be displayed on + standard "Ctrl+Space" key combination. To add existing= styling to the chosen + element just point to the necessary one. Each time you= select any class it is + displayed in the Preview tab. Click on the <= property + >Apply button will apply the= changes without closing + the window. +
Style Class Selection @@ -1476,15 +1380,10 @@
- - - = - The Edited properties tab gives a preview of the properties whic= h are set for the existing style class. You can easily modify them with the help = of this wizard. -
Edited Properties @@ -1493,9 +1392,8 @@
- = - If the style class isn't chosen, the tab doesn&= apos;t show any properties. - = + If the style class isn't chosen, the tab doesn&= apos;t show any + properties.
Edited Properties when the style class isn't ch= osen @@ -1504,11 +1402,10 @@
- = The Preview tab - is for observing the content of the chosen= CSS file. This tab is hidden if no CSS file is chosen. - + is for observing the content of the chosen= CSS file. This tab is + hidden if no CSS file is chosen.
Preview Tab @@ -1517,11 +1414,10 @@
- - At the top of the CSS Class Dialog - you can see a preview box which visualizes the result.= To edit the preview you should double click in the box. To leave the focus= , use + At the top of the CSS Class Dialog you can see a preview + box which visualizes the result. To edit the preview y= ou should double click in + the box. To leave the focus, use Ctrl + Tab. - =
Editing the Preview @@ -1530,11 +1426,9 @@
- The dialog for creating a new CSS class, which is ca= lled from New > Other... > JBoss Tools Web > CSS C= lass, looks this way: -
New CSS Class Dialog @@ -1543,7 +1437,8 @@
- Click on the Browse button to open = a dialog to select the CSS file to create a CSS class for: + Click on the Browse button to o= pen a dialog to select the + CSS file to create a CSS class for:
CSS File Selection @@ -1552,22 +1447,17 @@
- Choose the necessary CSS file and click on the Ok button. - = - = + Choose the necessary CSS file and click on the Ok + button.
-
Templating - The VPE also makes it possible to create templates for u= nknown tags. - To call the Template dialog for a t= ag, right-click on it in Visual mode and select Setup Template for <tag name> option. -
Calling Template Dialog @@ -1576,10 +1466,8 @@
- Here is what the Templa= te dialog looks like. -
Template Dialog @@ -1588,14 +1476,12 @@
- Tag for Display field in the Template dialog requires specifying a type of tag. It can be SPAN, DIV, TABLE or any other html = element. Check Children , if you want to mark a tag as a child element.= - The Value field is for setting a tag value. @@ -1604,11 +1490,9 @@ field, you can fill it out manually or make us= e of the button next to the field to bring the CSS Di= alog for editing styles. - You can observe all defined templates in the VPE Preferences on the Templates tab which you can = quickly access by pressing Preferences butt= on. -
Templates Tab of the VPE Preferences Page @@ -1617,110 +1501,83 @@
- - Here it's possible to edit or remove any listed in = the table - template. - + Here it's possible to edit or remove any listed in = the table template.
-
- VPE Toolbar - = The Visual Page Editor toolbar includes the next buttons= : - = - - Preference= s - ( - - - - - - ) - - = - Refresh - ( - - - - - - ) - - = - Pa= ge Design Options - ( = - - - - - - ) - - - = - - the button to swi= tch the current Visual/Source layout - ( = - - - - - ) - - = - - Show border for unk= nown tags - ( = - - - - - ) - - = - - Show non-vi= sual tags - ( = - - - - - ) - - = - - Show selecti= on bar - ( = - - - - - ) - - = - - Show text formatting= bar - ( = - - - - - ) - - = - - Show bundle's messages as EL expressions ( = - - - - - ) - - - = + + + Preferences ( + + + + ) + + + Refresh ( <= inlinemediaobject> + + + + ) + + + Page D= esign Options ( + + + + + ) + + + the button t= o switch the current + Visual/Source layout ( + + + + ) + + + Show border fo= r unknown tags ( + + + + + ) + + + Show n= on-visual tags ( + + + + + ) + + + Show se= lection bar ( + + + + + ) + + + Show text forma= tting bar ( + + + + + ) + + + Show bundle's messages as EL expressions ( + + + + ) + +
Buttons on the VPE Toolbar @@ -1729,517 +1586,456 @@
- -
- Preferences - = - The - Preferences - button - ( - - - - - - ) - provides a quick access to the Visual Page - Editor preferences. - = -
- Visual Page Editor Preferences Window - - - - - -
- = - This page provides a number of options associated with the editor = representation. = - The more detailed description on each one you can find in the "JBoss Tools Preferences" chapter = - under Visual Page Editor. -
- = -
- Refresh - = - Clicking on the - Refresh - button = - ( - - - - - - ) = - refreshes the displayed information. -
- = -
- Page Design Options - = - The - Page Design Options - button = - ( = - - - - - - ) = - leads to a window which helps you specify necessary - references of the resources. It is represented by a window with 4 ta= bs. The - first one, - Actual Run-Time folders, - is used to replace absolute and relative path values when - generating a preview: -
- Page Design Options: Actual Run-Time folders - - - - - -
- = - = - The second tab, - Included CSS files - , is used to add CSS files to be linked by Visual Page Edi= tor - when generating a preview: - = -
- Page Design Options: Included CSS files - - - - - -
- = - The third one, - Included tag libs, can be used to ad= d Taglibs that can be used by the editor for - getting appropriate templates to generate a preview: - = -
- Page Design Options: Included tag libs - - - - - -
- = - And finally, the - Substituted El expressions - tab is used to add El expressions that will be substitute= d by - the editor when generating a preview: - = -
- Page Design Options: Substituted El expressions - - - - - -
- = - = - The first two tabs of the window let you define actual runtime = folders. - The example below will help you understand how this can be done. - = - Suppose you have the following project structure: - = - + Preferences + The + Preferences + button ( + + + + ) provides a quick access to the = Visual Page + Editor preferences. +
+ Visual Page Editor Preferences Window + + + + + +
+ This page provides a number of options associated wi= th the editor + representation. The more detailed description on each = one you can find in the + "JBoss Tools Preferences" chapter under Visual Page Editor. +
+
+ Refresh + Clicking on the + Refresh + button ( + + + + ) refreshes the displayed informa= tion. +
+
+ Page Design Options + The + Page Design Options + button ( + + + + ) leads to a window which helps y= ou specify necessary + references of the resources. It is represented by a wi= ndow with 4 tabs. The + first one, + Actual Run-Time folders, is used to replace + absolute and relative path values when generating a pr= eview: +
+ Page Design Options: Actual Run-Time folders</t= itle> + <mediaobject> + <imageobject> + <imagedata fileref=3D"images/visual_page/visua= l_page_10.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The second tab, <emphasis> + <property>Included CSS files</property> + </emphasis>, is used to add CSS files to be linked by = Visual Page Editor when + generating a preview:</para> + <figure> + <title>Page Design Options: Included CSS files + + + + + +
+ The third one, + Included tag libs,= can be used to add + Taglibs that can be used by the editor for getting app= ropriate templates to + generate a preview: +
+ Page Design Options: Included tag libs + + + + + +
+ And finally, the + Substituted El expressions + tab is used to add El expressions that wil= l be substituted by the + editor when generating a preview: +
+ Page Design Options: Substituted El expressions= + + + + + +
+ The first two tabs of the window let you define actu= al runtime folders. The + example below will help you understand how this can be= done. + Suppose you have the following project structure: + - = - The content of the - header.jsp - is: - The content of the + header.jsp + is: + ]]> - and - main.jsp - content is: - + and + main.jsp + content is: + ]]> - When you open - main.jsp - in Visual Page Editor, it will not b= e able - to resolve the image from the header, however, it will work fine in = runtime. - To fix this in design time, click the - Page Design Options - button and set - Actual Run-Time Relative Folder - to 'projectName > WebContent > - pages' and you will see the image appeared. - - = - Let' consider an example for other tabs. For instance, the - definition of your CSS on the page is the next: - = - When you open + main.jsp + in Visual Page Editor= , it will not be able to + resolve the image from the header, however, it will wo= rk fine in runtime. To fix + this in design time, click the + Page Design Options + button and set + Actual Run-Time Relative Folder + to 'projectName > WebCon= tent > + pages' and you will see the image = appeared. + + Let' consider an example for other tabs. For in= stance, the definition of + your CSS on the page is the next: + ]]> - = - This will work fine in runtime, but the Visual Page - Editor doesn't know what - requestContextPath in design time is. In order = to - see the necessary styles applied in design time your should add a pa= th to - your stylesheet in the CSS File Path section. - = - The next URI section lets you add URI tagl= ibs so that - the editor knows where to find the tag libraries. - = - And the last Substituted EL expressions se= ction is - provided to specify the values for specific EL variables. It can be = useful - for a preview generation. - As an example look at the figure below: -
- EL Expression - - - - - -
- = - Here bath in Source and Visual modes you see the EL expression - #{user.name}. When you switch to Prev= iew - view, you'll also see this expression. Now press - Page Design Options - button and set the value for the - "user.name" as - World. - = -
- Setting the Value for the EL Expression - - - - - -
- = - As a result in Visual mode and Preview view the word - World - is displayed. -
- The EL Expression Value - - - - - -
-
- -
- Visual/Source Editors splitting buttons - = - The - Visual/Source Editors splitting buttons - provide the possibility to choose one of the four possible layouts = for the Visual/Source Editor. - - = - = - The available layouts and corresponding buttons are as follows: - - Vertical Source on top( - - - - ) - Vertical Visual on top ( - - - - ) - Horizontal Source to the left ( - - - - ) - Horizontal Visual to the left ( - - - - ) - = - -
- Visual Page Editor Before Layout Changing - - - - - -
- Note, at the current view there is only - one button, that proposes the poss= ibility to change it in order the Source and the View are moved - in a clockwise direction. = -
- Visual Page Editor After Layout Changing - - - - - -
- -
- = -
- Show Border for Unknown Tags - = - The option is a self explanatory, i. e. if you want unknown tag= s to be wrapped in a border in the VPE visual part, just press the = - - Show border for unknown tags button - ( = - - - - - ) on the toolbar. -
- = -
- Show Non-visual Tags - = - Visual Page Editor provides the option for= displaying - non-visual tags in Visual mode of the editor. To enable it select th= e - Show non-visual tags button ( = - - - - - ) on the VPE toolbar. - = - On the figure you can see non-visual elements with gray dashed = borders. - = -
- Non-visual Tag in the VPE - - - - - -
- = - You can also switch on this option in the VPE preferences, hav= ing clicked on the Preferences - button - ( - - - - ). -
- = -
- Show Selection Bar - = - You can find useful one more functionality provided by VPE= . At the bottom of the - Visual/Source view there is a Se= lection Tag - Bar. It's updated automatically allowing to see tag= s tree for a current component selected in - Visual or Source mode, also it allows to select tags back and f= orward. - = -
- Selection Tag Bar - - - - - -
- = - If you want to hide the Selection Tag Bar, use - the - Show Selection Bar button ( = - - - - - ) on the VPE toolbar. -
+ This will work fine in runtime, but the Vi= sual Page + Editor doesn't know what + requestContextPath in design = time is. In order to see + the necessary styles applied in design time your shoul= d add a path to your + stylesheet in the CSS File Path s= ection. + The next URI section lets you a= dd URI taglibs so that the + editor knows where to find the tag libraries. + And the last Substituted EL expressions section is + provided to specify the values for specific EL variabl= es. It can be useful for a + preview generation. + As an example look at the figure below: +
+ EL Expression + + + + + +
+ Here bath in Source and Visual modes you see the EL = expression + #{user.name}. When you switch= to Preview + view, you'll also see this express= ion. Now press + Page Design Options + button and set the value for the + "user.name" as World. +
+ Setting the Value for the EL Expression + + + + + +
+ As a result in Visual mode and Preview view the word= + World + is displayed. +
+ The EL Expression Value + + + + + +
+
+
+ Visual/Source Editors splitting buttons + The + Visual/Source Editors splitting buttons<= /property> + provide the possibility to choose one of the four poss= ible layouts for the + Visual/Source Editor. + The available layouts and corresponding buttons are = as follows: + + Vertical Source on top( + + + + ) + + + Vertical Visual on top ( + + + + ) + + + Horizontal Source to the left ( + + + + ) + + + Horizontal Visual to the left ( + + + + ) + +
+ Visual Page Editor Before Layout Changing <= /title> + <mediaobject> + <imageobject> + <imagedata fileref=3D"images/visual_page/v= isual_page_24.png"/> + </imageobject> + </mediaobject> + </figure> Note, at the current view there is only <emp= hasis> + <property> one</property></emphasis> button, that = proposes the possibility + to change it in order the Source and the View are move= d <emphasis> + <property>in a clockwise direction</property></emp= hasis>. <figure> + <title>Visual Page Editor After Layout Changing </= title> + <mediaobject> + <imageobject> + <imagedata fileref=3D"images/visual_page/v= isual_page_25.png"/> + </imageobject> + </mediaobject> + </figure></para> + </section> + <section id=3D"vpe_show_border"> + <title>Show Border for Unknown Tags + The option is a self explanatory, i. e. if you want = unknown tags to be wrapped + in a border in the VPE visual part, just press the + Show border for unknown tags<= /emphasis> button ( + + + + + ) on the toolbar. +
+
+ Show Non-visual Tags + Visual Page Editor provides the= option for displaying + non-visual tags in Visual mode of the editor. To enabl= e it select the + Show non-visual tags button ( + + + + + ) on the VPE toolbar. + On the figure you can see non-visual elements with g= ray dashed borders. +
+ Non-visual Tag in the VPE + + + + + +
+ You can also switch on this option in the VPE prefer= ences, having clicked on + the Preferences + button ( + + + + ). +
+
+ Show Selection Bar + You can find useful one more functionality provided = by VPE. At the bottom of + the Visual/Source view there is a= Selection Tag + Bar. It's updated automatically allowin= g to see tags tree for a + current component selected in Visual or Source mode, a= lso it allows to select + tags back and forward. +
+ Selection Tag Bar + + + + + +
+ If you want to hide the Selection Tag Bar<= /property>, use the + + Show Selection Bar= button ( + + + + + ) on the VPE toolbar. +
- = -
- Page Preview - = - VPE comes with design-time preview featur= e which is available - for: - = - - - Struts Pages - - - JSF Pages - - +
+ Page Preview + VPE comes with design-time preview = feature which is available + for: + + + Struts Pages + + + JSF Pages + + Seam Pages - = - Preview view is read-only, it shows how t= he page will look - like in a browser. -
- Preview View - - - - - -
- = - -
- = -
- Support for Custom Facelets Components - = - Visual Page Editor (starting from 3.0.0.M3 v= ersion of JBoss Tools) supports - custom Facelets tag libraries both declared in the web.xml file = - (for details, see = - Creating a component) and packed into the JAR file. - = - - Tip: - In case of Facelets tag library packed in .jar, remember to put *.taglib.xml in right place: - [filename].jar/META-INF/*.taglib.xml - - = - Visual Page Editor recognizes the tags from = the custom Facelets tag library and correctly - renders them both in source and visual view of the editor. - = -
- Custom Facelets Tags in the VPE - - - - - -
- = - While editing an XHTML file that uses a custom Facelets components - you can always make use of the following editor's features: - = - - - Content Assist= for Custom Facelets Components - - - OpenOn for Custom Fac= elets Components - - - = -
- Content Assist for Custom Facelets Components - Call the content assist as usual by using Ct= rl+Space - when typing a tag. As proposals you should see custom Facelets tags d= efined in your Facelets tag library. - = -
- Content Assist for Custom Facelets Tags - - - - - -
-
- = -
- OpenOn for Custom Facelets Components - = - While developing using Facelets you can make use of: - - OpenOn in XHTML Files= That Use Custom Facelets Components - OpenO= n in Custom Facelets Tag File (*.taglib.xml) - - = -
- OpenOn in XHTML Files That Use Custom Facelets Components</tit= le> - <para>OpenOn functionality in XHTML files is available in two views o= f the <property>Visual Page Editor</property>:</para> - = - <orderedlist> - <listitem> - <para>Source view</para> - = - <para><emphasis><property>Ctrl+Click</property></emphasis> on the n= amespace will open the Facelets tag file - in a separate window.</para> - = - <figure> - <title>Opening a Custom Facelets Tag File - - - - - - - = - Ctrl+Click on any c= ustom Facelets tag declared on the page will do the same. - The selected tag will be highlighted in the opened file. - = -
- Opening a Custom Facelets Tag File - - - - - -
- - = - - Visual view - = - In the visual view of the VPE, double-cl= ick a custom component and the Facelets tag file = - (*.taglib.xml) where it is declared will be ope= ned. - - -
- = -
- OpenOn in Custom Facelets Tag File (<literal>*.taglib.xml</lit= eral>) - = - Ctrl+Click on the pat= h to source of the Facelets tag will - open the component in its own editor. -
- Opening a Custom Facelets Component - - - - - -
-
- -
-
- = -
- +
+
+ Support for Custom Facelets Components + Visual Page Editor (starting from 3= .0.0.M3 version of + JBoss Tools) supports custom Face= lets tag libraries both + declared in the web.xml file (for detai= ls, see Creating + a component) and packed into the JAR file. + + Tip: + In case of Facelets tag library packed in .= jar, remember to + put *.taglib.xml in right place: [filename].jar/META-INF/*.taglib.xml + + Visual Page Editor recognizes the t= ags from the custom + Facelets tag library and correctly renders them both in so= urce and visual view of + the editor. +
+ Custom Facelets Tags in the VPE + + + + + +
+ While editing an XHTML file that uses a custom Facelets = components you can always + make use of the following editor's features: + + + Content Assist for Custom + Facelets Components + + + OpenOn= for Custom Facelets + Components + + +
+ Content Assist for Custom Facelets Components</titl= e> + <para>Call the content assist as usual by using <emphasis>= <property + >Ctrl+Space</property></emphasis> when typing = a tag. As proposals you + should see custom Facelets tags defined in your Facele= ts tag library.</para> + <figure> + <title>Content Assist for Custom Facelets Tags + + + + + + +
+
+ OpenOn for Custom Facelets Components + While developing using Facelets you can make use of:= + + + OpenOn in XH= TML Files That Use Custom + Facelets Components + + + OpenOn in Custom + Facelets Tag File (*.taglib.xml) + + +
+ OpenOn in XHTML Files That Use Custom Facelets = Components + OpenOn functionality in XHTML files is available= in two views of the + Visual Page Editor: + + + Source view + Ctrl+Click on the + namespace will open the Facelets tag file = in a separate + window. +
+ Opening a Custom Facelets Tag File<= /title> + <mediaobject> + <imageobject> + <imagedata fileref=3D"images/visua= l_page/customFacelets3.png" + /> + </imageobject> + </mediaobject> + </figure> + <para><emphasis><property>Ctrl+Click</property= ></emphasis> on any custom + Facelets tag declared on the page will do = the same. The selected tag + will be highlighted in the opened file.</p= ara> + <figure> + <title>Opening a Custom Facelets Tag File<= /title> + <mediaobject> + <imageobject> + <imagedata fileref=3D"images/visua= l_page/customFacelets4.png" + /> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Visual view</para> + <para>In the visual view of the <property>VPE<= /property>, double-click a + custom component and the Facelets tag file= (<literal + >*.taglib.xml</literal>) where it is d= eclared will be + opened.</para> + </listitem> + </orderedlist> + </section> + <section id=3D"openOnInCustomFaceletsTaglibs"> + <title>OpenOn in Custom Facelets Tag File (<literal + >*.taglib.xml</literal>) + Ctrl+Click on the path to source + of the Facelets tag will open the component in its= own editor. +
+ Opening a Custom Facelets Component + + + + + +
+
+
+
+
Setup notes for Linux - - Linux users who are going to use earlier then JBoss Tool= s 3.1.0.M4 versions may need to do the following to get the Visua= l Page - Editor to work correctly on their machines. - = - + Linux users who are going to use earlier then JBoss Tool= s 3.1.0.M4 versions may + need to do the following to get the Visual Page = Editor to work + correctly on their machines. The Visual Page Editor requires the library libstdc++.s= o.5. This library is - contained in the compat-libstdc++-33.i386 package. = - = - Note - Starting from JBoss Tools 3.1.0.M4 the libstdc++.so= .5 library isn't required. - + contained in the compat-libstdc++-33.i386 package. + + Note + Starting from JBoss Tools 3.1.0.M4 the libstdc++.so= .5 library isn't + required. + To install this package on Fedora Core or Red Ha= t Enterprise Linux run the @@ -2247,47 +2043,45 @@ - - On any other rpm based distributions download li= bstdc++.so.5 and run the following command: - - On Debian based distributives run the following = command: - - In case you have the library installed and you still ha= ve issue with starting the visual page editor then close all browser views/editors an= d leave one visual page editor open and restart eclipse. This should force a load = of the right XULRunner viewer. - If it doesn't help and you use Fedora Core Linux and Ec= lipse Version: 3.4.1,the issue can be produced because libswt-xulrunner-gtk= -3449.so file doesn't present - in eclipse-swt-3.4.1-5.fc10.x86_64.rpm/eclipse/plugins/org= .eclipse.swt.gtk.linux.x86_64_3.4.1.v3449c.jar.To add this file to eclipse = you should: = - + If it doesn't help and you use Fedora Core Linux and Ec= lipse Version: 3.4.1,the + issue can be produced because libswt-xulrunner-gtk-3449.so= file doesn't present in + eclipse-swt-3.4.1-5.fc10.x86_64.rpm/eclipse/plugins/org.ec= lipse.swt.gtk.linux.x86_64_3.4.1.v3449c.jar.To + add this file to eclipse you should: - Decompress eclipse/plugins/org.eclipse.swt.gtk.l= inux.x86_3.4.1.v3449c.jar form eclipse-SDK-3.4.1-linux-gtk-x86_64.tar.gz - = + Decompress eclipse/plugins/org.eclipse.swt.gtk.l= inux.x86_3.4.1.v3449c.jar + form eclipse-SDK-3.4.1-linux-gtk-x86_64.tar.gz + - Copy libswt-xulrunner-gtk-3449.so file to your Fedora Eclipse location. - = - = + Copy libswt-xulrunner-gtk-3449.so file to your Fedora + Eclipse location. + - Open the file eclipse.ini,which can be found in = your Fedora Eclipse location and add the following line: + Open the file eclipse.ini,which can be found in = your Fedora Eclipse + location and add the following line: ,where /usr/lib/eclipse is the path= to your eclipse folder. - = +]]> + ,where /usr/lib/eclipse is the path= to your eclipse + folder. +
- -
-
- More Editors - Besides Visual Page Editor JBDS is supplied with a huge rang= e of various editors for different file types: properties, TLD, web.xml, tiles, and so = on.
- Graphical Properties Editor - The Properties editor allows you to= work in two different modes and also supports unicode characters. - To create a new properties file, in the Package Explorer= view, select New > Properties File from the right-click context menu on the folde= r where you want to create @@ -2355,10 +2142,7 @@ - - You can edit the file using a table-oriented "Prope= rties" - viewer: - + You can edit the file using a table-oriented "Prope= rties" viewer:
"Properties" Viewer @@ -2367,7 +2151,6 @@
- You can also use a Source viewer for editing the file:
Source Viewer @@ -2378,14 +2161,10 @@
-
- Graphical TLD Editor - The TLD editor comes with same feat= ures you will find in all other JBoss Developer Studio editors: - Graphical and source edit modes @@ -2395,9 +2174,7 @@
- Tree view -
Tree View @@ -2408,12 +2185,9 @@
- Source view - You can easily switch from Tree to Source by selecti= ng the Source tab at the bottom of the editor. -
Source View @@ -2422,9 +2196,7 @@
- You can easily add a new tag: -
Adding a New TLD Tag @@ -2433,7 +2205,6 @@
- You can also easily add a new attribute to an existing tag:
@@ -2446,7 +2217,6 @@
Content assist is available when editing the file us= ing the Source viewer: -
TLD Content Assist @@ -2455,11 +2225,9 @@
- In the Source viewer, if at any point a tag is incor= rect or incomplete, an error will be indicated next to the line and also in t= he Problems view below. -
Error Reporting @@ -2470,19 +2238,15 @@
- -
- Graphical Web Application File (web.xml) Editor - - The deployment descriptor - web.xml file is intended for des= cribing the servlets, container-managed = - security constraints and various deployment properties specific = for your Web Application. - = - To edit the deployment descriptor JBoss Developer= Studio provides its own = - web.xml editor that comes with the same fea= tures you will find in all other JBDS editors: - + The deployment descriptor + web.xml file is intend= ed for describing the + servlets, container-managed security constraints and vario= us deployment properties + specific for your Web Application. + To edit the deployment descriptor JBoss Develo= per Studio + provides its own web.xml editor that = comes with the same + features you will find in all other JBDS editors: Graphical and source edit modes @@ -2493,12 +2257,12 @@
Tree View - - Switch to the Tree view if you wan= t to edit - web.xml in a graphical mode. = - All elements that - web.xml could include are l= ocated in the left area of the editor in a tree format. = - Click a node on the left to display and edit its properties = that will appear in the right-hand area. + Switch to the Tree view if you = want to edit + web.xml in a graph= ical mode. All elements + that + web.xml could incl= ude are located in the + left area of the editor in a tree format. Click a node= on the left to display + and edit its properties that will appear in the right-= hand area.
Tree View for editing web.xml in a graphical mo= de @@ -2507,10 +2271,8 @@
- You can add any new elements right in the = Tree viewer: -
Adding New Elements in Web XML Editor @@ -2521,12 +2283,9 @@
- Source View - Switch to the Source viewer to = edit the web.xml file by hand at any time: -
Web XML Source View @@ -2537,13 +2296,10 @@
- Content Assist - Content assist is available in the Source viewer. Si= mply click CTRL-Space anywhere in the file. -
Web XML Content Assist @@ -2555,13 +2311,10 @@
- Errors Checking and Validation - If errors occur anywhere in the file, small red dots= will appear next to the lines where the errors occurred. Also, note that the f= ile is marked by a small x in the Package Explorer view. -
Errors Reporting @@ -2572,14 +2325,10 @@
-
- CSS Editor - The CSS editor comes with the same = features you will find in all other JBoss Developer Studio editors. - Content assist @@ -2588,10 +2337,8 @@ Validation and error checking - With the CSS (Cascading Style Sheet) editor, you can tak= e advantage of code prompting: -
CSS Editor @@ -2600,7 +2347,6 @@
- - And you can also use the Properties view next to the edi= tor to edit existing stylesheet declaration properties: -
Properties View in CSS Editor @@ -2625,17 +2369,14 @@
- - To make you work on CSS files more comfortable, CSS pers= pective is available, read more about it in CSS Editing Perspective chapter = + To make you work on CSS files more comfortable, CSS pers= pective is available, read + more about it in CSS Edi= ting Perspective + chapter
- = - JavaScript Editor - The JavaScript editor includes a Pr= eview viewer and a Source viewer. In the Source viewer, you can use code assist: -
JavaScript Editor @@ -2644,10 +2385,8 @@
- You can also use the Source viewer with the Outline view= to navigate around the file: -
Source Viewer in JavaScript Editor @@ -2656,7 +2395,6 @@
-
- XSD Editor - JBoss Developer Studio comes with an XSD Edito= r for XML Schema files. This editor comes from the Web Tools Project= (WTP) (see WTP Getting Started). - To create a new XSD file, right-click a folder in the Pa= ckage Explorer view, select New > Other... from the context menu and then select XML > XML Schema in the dialog box. -
Creating New XSD file @@ -2698,10 +2432,8 @@
- The XSD Editor includes two viewers for working on the f= ile, a Design viewer and a Source viewer: -
Source Viewer in XSD Editor @@ -2710,10 +2442,8 @@
- In the Design viewer, you can drill down on an element b= y double-clicking on it: -
Design Viewer in XSD Editor @@ -2722,10 +2452,8 @@
- Various edit options are available when you right-click = an element in the diagram: -
Edit Options in XSD Editor Context Menu. @@ -2734,9 +2462,7 @@
- You can also use the Properties view to edit a selected = element: -
Properties View in XSD Editor @@ -2745,25 +2471,21 @@
- You can also use a Source viewer for the file. In this v= iewer, along with direct editing of the source code, you can also edit the file by = using the Properties view on the right: -
- Using Source Viewer and Properties View together fo= r source code editing + Using Source Viewer and Properties View together fo= r source code + editing
-
- Support for XML Schema - JBoss Developer Studio fully supports XML files based on= schemas as well as DTDs:
@@ -2774,8 +2496,6 @@
-
- --===============5879620756762108559==--