November 2007 - jbosstools-commits

JBoss Tools SVN: r4990 - trunk/hibernatetools/docs/resources/support.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-11-20 11:57:57 -0500 (Tue, 20 Nov 2007) New Revision: 4990 Removed: trunk/hibernatetools/docs/resources/support/docbook-xsl/ Log: the folder should be replace to a more up-to-date and less in size one

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4989 - trunk/jsf/docs/resources/support.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-11-20 11:31:20 -0500 (Tue, 20 Nov 2007) New Revision: 4989 Removed: trunk/jsf/docs/resources/support/docbook-xsl/ Log: the folder will be replace to more up-to-date and less in size one

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4988 - trunk/jsf/docs/resources/styles/en.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-11-20 11:30:10 -0500 (Tue, 20 Nov 2007) New Revision: 4988 Modified: trunk/jsf/docs/resources/styles/en/html.xsl trunk/jsf/docs/resources/styles/en/html_chunk.xsl Log: http://jira.jboss.com/jira/browse/RHDS-310 docbook resources will be taken now from local folder Modified: trunk/jsf/docs/resources/styles/en/html.xsl =================================================================== --- trunk/jsf/docs/resources/styles/en/html.xsl 2007-11-20 16:29:12 UTC (rev 4987) +++ trunk/jsf/docs/resources/styles/en/html.xsl 2007-11-20 16:30:10 UTC (rev 4988) @@ -15,7 +15,7 @@ --> <!DOCTYPE xsl:stylesheet [ - <!ENTITY db_xsl_path "../support/docbook-xsl"> + <!ENTITY db_xsl_path "../../support/docbook-xsl"> ]> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" @@ -23,7 +23,7 @@ xmlns="http://www.w3.org/TR/xhtml1/transitional" exclude-result-prefixes="#default"> -<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl"/> +<xsl:import href="&db_xsl_path;/html/docbook.xsl"/> <xsl:include href="./collapsing-navigation.xsl"></xsl:include> <xsl:include href="./highlight.xsl"></xsl:include> Modified: trunk/jsf/docs/resources/styles/en/html_chunk.xsl =================================================================== --- trunk/jsf/docs/resources/styles/en/html_chunk.xsl 2007-11-20 16:29:12 UTC (rev 4987) +++ trunk/jsf/docs/resources/styles/en/html_chunk.xsl 2007-11-20 16:30:10 UTC (rev 4988) @@ -23,10 +23,8 @@ xmlns="http://www.w3.org/TR/xhtml1/transitional" exclude-result-prefixes="#default"> - +<xsl:import href="&db_xsl_path;/html/chunk.xsl"/> -<xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl"/> - <xsl:include href="./collapsing-navigation.xsl"></xsl:include> <xsl:include href="./highlight.xsl"></xsl:include>

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4987 - trunk/jsf/docs/userguide/en/modules.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-11-20 11:29:12 -0500 (Tue, 20 Nov 2007) New Revision: 4987 Added: trunk/jsf/docs/userguide/en/modules/editors.xml trunk/jsf/docs/userguide/en/modules/jboss_tools.xml Log: chapters on editors are placed into one chapter name of the guide is changed, as it is mostly of RHDS and not JBossTools http://jira.jboss.com/jira/browse/RHDS-175 Added: trunk/jsf/docs/userguide/en/modules/editors.xml =================================================================== --- trunk/jsf/docs/userguide/en/modules/editors.xml (rev 0) +++ trunk/jsf/docs/userguide/en/modules/editors.xml 2007-11-20 16:29:12 UTC (rev 4987) @@ -0,0 +1,1617 @@ +<?xml version='1.0' encoding='UTF-8'?> + <chapter id="rhds_editors" xreflabel="rhds_editors"> + <?dbhtml filename="rhds_editors"?> + <chapterinfo> + <keywordset> + <keyword>Red Hat Developer Studio</keyword> + <keyword>RHDS</keyword> + <keyword>Editor</keyword> + </keywordset> + </chapterinfo> + + <title>RHDS Editors</title> + +<para>RHDS is supplied with a huge range of various editors for different file types.</para> + +<section id="editors_features"> + <?dbhtml filename="editors_features.html"?> +<title>Editors Features</title> +<para>Red Hat Developer Studio has powerful editor features that help you easily navigate within your application and make use of content and code assist no matter what project file (jsp, xhtml, xml, css, etc.) you are working on.</para> + +<section id="OpenOnSelection4Hyperlinknavigation"> +<?dbhtml filename="OpenOnSelection(Hyperlinknavigation)"?> +<title>OpenOn</title> + +<para><property>OpenOn</property> let's you easily navigate through your project without using the Package Explorer view (project tree). With OpenOn, you can simply click on a reference to another file and that file will be opened.</para> + +<para>OpenOn is available for the following files:</para> +<itemizedlist> +<listitem><para>XML files</para></listitem> +<listitem><para>JSP/XHTML Pages</para></listitem> + <listitem><para>Java files</para></listitem> +</itemizedlist> +<section id="XMLFiles232"> +<?dbhtml filename="XMLFiles"?> +<title>XML Files</title> + +<para>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 have the mouse cursor over the name of the file you want + to open, click and the file will open in its own editor. In this example the managed bean NameBean will + open.</para> +<figure> +<title>NameBean Managed Bean</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_1.png"/> + </imageobject> +</mediaobject> +</figure> +<para>This is the result of using OpenOn</para> +<figure> +<title>NameBean Java Class</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_2.png"/> + </imageobject> +</mediaobject> +</figure> +<para>You can also try OpenOn with defined attributes.</para> +<figure> +<title>OpenOn With Defined Attributes</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_3.png"/> + </imageobject> +</mediaobject> +</figure> +<para>You can also open any JSP pages.</para> +<figure> +<title>JSP Page OpenOn</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_4.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="JSPPages223"> +<?dbhtml filename="GettingStartedwithRHDS.html"?> +<title>JSP Pages</title> + +<para><property>OpenOn</property> is also very useful in JSP pages. It will allow you to quickly jump to the reference + instead of having to hunt around in the project structure.</para> + +<para>You can easily open the imported property files.</para> +<figure> +<title>OpenOn With Imported Property Files</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_5.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Use OpenOn to open a CSS file used with a JSP page:</para> +<figure> +<title>OpenOn With CSS File</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_6.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Open managed beans:</para> +<figure> +<title>OpenOn With Maneaged Beans</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_7.png"/> + </imageobject> +</mediaobject> +</figure> +<para>For JSP files in a JSF project, you can also easily open the navigation rules by applying <property>OpenOn</property> to the JSF tag for the navigation outcome:</para> +<figure> +<title>OpenOn With JSF Tag</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_8.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> + +<section id="CodeAssistAndDynamicCodeAssist42BasedOnProjectData"> +<?dbhtml filename="CodeAssistAndDynamicCodeAssist(BasedOnProjectData).html"?> +<title>Code Assist and Dynamic Code Assist (based on project data)</title> +<section id="ContentAssistFeatures321"> +<?dbhtml filename="ContentAssistFeatures"?> +<title>Content Assist Features</title> +<section id="ContentAssist374"> +<?dbhtml filename="ContentAssist.html"?> +<title>Content Assist</title> +<para><property>Content assist</property> is available when working with</para> + +<itemizedlist> +<listitem><para>Seam project files</para></listitem> +<listitem><para>JSF project files</para></listitem> +<listitem><para>Struts project files</para></listitem> +<listitem><para>JSP files</para></listitem> +</itemizedlist> +</section> +<section id="JSFProjectFiles3087"> +<?dbhtml filename="JSFProjectFiles.html"?> +<title>JSF Project Files</title> + + <para>When working with JSF project in Red Hat Developer Studio, you can use various <property>Content Assist features</property> while developing:</para> +<itemizedlist> +<listitem><para>Content Assist for XML, JSP and JSF configuration files</para></listitem> +<listitem><para>Content Assist based on project data</para></listitem> +<listitem><para>Content Assist with graphical JSF editor</para></listitem> +</itemizedlist> +<section id="ContentAssistForXMLJSPAndJSFConfigurationFiles865"> +<?dbhtml filename="ContentAssistForXMLJSPAndJSFConfigurationFiles.html"?> +<title>Content Assist for XML, JSP and JSF configuration files</title> + +<para>At any point when working with any XML, JSP and JSF configuration files Content Assist is available to help you. Simply type <emphasis><property>Ctrl-Space</property></emphasis> to see what is available.</para> + +<para>Content Assist for JSF configuration file:</para> +<figure> +<title>Content Assist in JSF Configuration File</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_9.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Content Assist for JSF JSP file:</para> +<figure> +<title>Content Assist in JSP File</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_10.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Content Assist for other JSF XML project files (web.xml shown):</para> +<figure> +<title>Content Assist in web.xml File</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_11.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="ContentAssistBasedOnProjectData86"> +<?dbhtml filename="ContentAssistBasedOnProjectData.html"?> +<title>Content Assist Based on Project Data</title> + +<para>Red Hat Developer Studio takes Content Assist to the 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:</para> +<itemizedlist> +<listitem><para>Values from Property files</para></listitem> +<listitem><para><emphasis role="italic"><property>"Managed beans"</property></emphasis> attributes and methods</para></listitem> +<listitem><para>Navigation Rule Outcomes</para></listitem> + <listitem><para>JSF variables (context, request etc...)</para></listitem> +</itemizedlist> +<para>The first screenshot shows how to insert message from a Properties files. You simply put the cursor + inside the <emphasis role="italic"><property>"value"</property></emphasis> attribute and press <emphasis><property>Ctrl-Space</property></emphasis>. Red Hat Developer Studio will scan your project and show a list of possible values to insert.</para> +<figure> +<title>Inserting Message</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_12.png"/> + </imageobject> +</mediaobject> +</figure> +<para>In the following screen shot we are inserting a <emphasis role="italic"><property>"Managed bean"</property></emphasis> attribute value. Again, by simply clicking <emphasis><property>Ctrl-Space</property></emphasis>, Red Hat Developer Studio will show a list of all possible values that you can insert:</para> + +<para>Once you select a Managed bean, it will show you a list of all available attributes for the selected Managed bean (userBean).</para> +<figure> +<title>Attributes List</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_13.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Code Assist based on project data will also prompt you for navigation rules that exist in your JSF + configuration file.</para> +<figure> +<title>Code Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_14.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="ContentAssistWithinJSFGraphicalEditor44"> +<?dbhtml filename="ContentAssistWithinJSFGraphicalEditor.html"?> +<title>Content Assist within Tree JSF Editor</title> + +<para>Red Hat Developer Studio also provides Content Assist when working within the Tree JSF +configuration editor. Just click <emphasis><property>Ctrl-Space</property></emphasis>.</para> +<figure> +<title>Content Assist in Tree JSF Configuration Editor</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_15.png"/> + </imageobject> +</mediaobject> +</figure> +<para>If a field contains right class name and you click a link near the field you will come to the file with this class otherwise a new Java Class dialog will be shown:</para> +<figure> +<title>New Java Class</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_16.png"/> + </imageobject> +</mediaobject> +</figure> +<para>If you entered an incorrect name in the field error markers will be shown for field labels and tree items:</para> +<figure> +<title>Error Markers</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_17.png"/> + </imageobject> +</mediaobject> +</figure> +<itemizedlist> +<listitem><para>To add a new property to a managed bean expand <emphasis><property>Managed Beans</property></emphasis> and select <emphasis role="bold"><property><name_of_bean></property></emphasis></para></listitem> +<listitem><para>Click <emphasis><property>Add</property></emphasis> button in the Properties panel</para></listitem> +<listitem><para>In the dialog Add Property define a new property. From here also you can generate setters and getters methods:</para></listitem> +</itemizedlist> +<figure> +<title>Create New Property</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_18.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Here you can also add an additional navigation rule to the faces-config.xml file.</para> +<itemizedlist> +<listitem><para>Select <emphasis><property>Navigation Rules</property></emphasis></para></listitem> +<listitem><para>Click <emphasis><property>Add</property></emphasis> button</para></listitem> +<listitem><para>In the dialog <emphasis><property>Add Rule</property></emphasis> define a view and give a name to the rule. Click Finish:</para></listitem> +</itemizedlist> +<figure> +<title>Add New Navigation Rule</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_19.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> + +<section id="StrutsProjectFile46s3"> +<?dbhtml filename="StrutsProjectFiles.html"?> +<title>Struts Project Files</title> +<section id="ContentAssistForStrutsConfigurationFile75"> +<?dbhtml filename="ContentAssistForStrutsConfigurationFile.html"?> +<title>Content Assist for Struts Configuration File</title> +<figure> +<title>Struts Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_20.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="ContentAssistForStrutsJSPFile07"> +<?dbhtml filename="ContentAssistForStrutsJSPFile.html"?> +<title>Content Assist for Struts JSP File</title> +<figure> +<title>Struts JSP Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_21.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> +<section id="JSPPages434"> +<?dbhtml filename="JSPPages.html"?> +<title>JSP Pages</title> +<section id="ContentAssistForJSFTags96"> +<?dbhtml filename="ContentAssistForJSFTags.html"?> +<title>Content Assist for JSF Tags</title> +<para>RHDS provides full code completion for JSF tags:</para> + +<figure> +<title>JSF Tags Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_22.png"/> + </imageobject> +</mediaobject> +</figure> +<para>When the tag is selected the required attributes, if there any, are already inserted and the cursor is located to the first attribute. As this point you can ask for attribute proposals.</para> +<figure> +<title>Attributes Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_23.png"/> + </imageobject> +</mediaobject> +</figure> + +</section> +<section id="ContentAssistForJSTLTags6332"> +<?dbhtml filename="ContentAssistForJSTLTags.html"?> +<title>Content Assist for JSTL Tags</title> +<figure> +<title>JSTL Tags Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_24.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="ContentAssistForHTMLTags7454"> +<?dbhtml filename="ContentAssistForHTMLTags.html"?> +<title>Content Assist for HTML Tags</title> +<para>Content assist for HTML tags has the same mechanism as for JSF tags:</para> +<figure> +<title>HTML Tags Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_25.png"/> + </imageobject> +</mediaobject> +</figure> +<para>You can use as well attributes proposals for HTML tags:</para> +<figure> +<title>HTML Tags Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_26.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="ContentAssistForJavaScriptTags67433"> +<?dbhtml filename="ContentAssistForJavaScriptTags.html"?> +<title>Content Assist for JavaScript Tags</title> +<figure> +<title>JavaScript Tags Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_27.png"/> + </imageobject> +</mediaobject> +</figure> +</section> + +<section id="ContentAssistWithinConfigurationEditor743"> +<?dbhtml filename="ContentAssistWithinConfigurationEditor.html"?> +<title>Content Assist within JSF Configuration Editor</title> +<figure> +<title>Content Assist in JSF Configuration Editor</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_28.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> +<section id="ContentAssistForRF"> +<?dbhtml filename="ContentAssistForRF.html"?> +<title>Content Assist for Rich Faces components</title> +<para>RHDS indeed provides code completion for Rich Faces framework components. All you have to do is to install Rich Faces libraries into your project. See <ulink url="http://labs.jboss.com/file-access/default/members/jbossrichfaces/freezone...">here</ulink> how to install.</para> +<figure> +<title>Content Assist for Rich Faces Components</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_29.png"/> + </imageobject> +</mediaobject> +</figure> +<itemizedlist> + <listitem><para>To insert a Rich Faces component on a page expand <emphasis><property>JBoss Rich Faces</property></emphasis> group on the palette</para></listitem> + <listitem><para>Click on some component</para></listitem> + <listitem><para>Put the needed attributes in the <emphasis><property>Insert Tag</property></emphasis> dialog and click <emphasis><property>Finish</property></emphasis> button + <figure> +<title>Insert Tag</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_30.png"/> + </imageobject> +</mediaobject> +</figure> + </para></listitem> + </itemizedlist> + <para>The Rich Faces tag will be inserted on your page displayed in source and visual modes: </para> + <figure> +<title>Rich Faces Component</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_31.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> + +<section id="AddingDynamicCodeAssistToCustomComponents8745"> +<?dbhtml filename="AddingDynamicCodeAssistToCustomComponentsThatWereAddedToJBossToolsPalette.html"?> +<title>Adding dynamic code assist to custom components that were added to JBoss Tools Palette</title> +<para>Here is what you need to do to add project based code assist to a custom component added in +Red Hat Developer Studio:</para> +<orderedlist> + <listitem><para>Create a new xml file in <emphasis><property><RHDS_home>rhds/eclipse/plugins/org.jboss.tools.common.kb_***/schemas/tld/</property></emphasis>. For example call it JeniaFaces.xml. The file should be written according to <emphasis><property><RHDS_home>/rhds/eclipse/plugins/org.jboss.tools.common.kb/kb.jar/org/jboss/tools/common/kb/kb-schema_1.0.dtd</property></emphasis></para></listitem> +</orderedlist> + <para>Here is how you set what is available for code assist:</para> +<itemizedlist> +<listitem><para>Adds code assist for JSF pre-defined objects, such as value=<emphasis role="italic"><property>"#{param}"</property></emphasis>:</para></listitem> +</itemizedlist> +<programlisting role="XML"><![CDATA[<AttributeType ...> + <proposal type="jsfVariables"/> +</AttributeType> +]]></programlisting> + <itemizedlist> +<listitem><para>Adds bundle resource (property file) <property>code assist</property>:</para></listitem> + </itemizedlist> +<programlisting role="XML"><![CDATA[<AttributeType ...> + <proposal type="bundleProperty"/> +</AttributeType> +]]></programlisting> + <itemizedlist> +<listitem><para>Adds managed bean property <property>code assist</property>:</para></listitem> + </itemizedlist> +<programlisting role="XML"><![CDATA[<AttributeType ...> + <proposal type="beanProperty"/> +</AttributeType> +]]></programlisting> + <itemizedlist> +<listitem><para>Adds managed bean property but with a specified type:</para></listitem> + </itemizedlist> +<programlisting role="XML"><![CDATA[<AttributeType ...> + <proposal type="beanProperty"> + <param name="type" value="java.lang.Boolean"/> + </proposal> +</AttributeType> +]]></programlisting> + <itemizedlist> +<listitem><para>Adds managed bean method with a signature:</para></listitem> + </itemizedlist> +<programlisting role="XML"><![CDATA[<AttributeType ...> + <proposal type="beanMethodBySignature"> + <param name="paramType" value="javax.faces.context.FacesContext"/> + <param name="paramType" value="javax.faces.component.UIComponent"/> + <param name="paramType" value="java.lang.Object"/> + <param name="returnType" value="void"/> + </proposal> +</AttributeType> +]]></programlisting> + <orderedlist continuation="continues"> + <listitem><para>Add information on your xml file in <emphasis><property><RHDS_home>/rhds/eclipse/plugins/org.jboss.common.kb_***/plugin.xml</property></emphasis></para></listitem> + </orderedlist> + <programlisting role="XML"><![CDATA[ + <tld + jsf="true" + name="Jenia Faces" + schema-location="schemas/tld/myJSF.xml" + uri="http://www.jenia.org/jsf/dataTools"/>]]> + </programlisting> +<orderedlist continuation="continues"> +<listitem><para>Restart Eclipse. You should now have code assist for the component.</para></listitem> + </orderedlist> +</section> +</section> +<section id="FullControlOverSourceFiles-SynchronizedSourcAndVisualEditing74"> +<?dbhtml filename="FullControlOverSourceFiles-SynchronizedSourcAndVisualEditing.html"?> +<title>Full Control over Source Files - Synchronized Source and Visual Editing</title> + +<para>Red Hat Developer Studio offers the flexibility to edit any files in either source or extra visual + modes at the same time.</para> + +<para>The project is yours and so is the source. Red Hat Developer Studio provides you many different + graphical editors to speed your application development. At the same time, you always have full control + over all project source files. Any changes you make in the source view, will immediately appear in + the graphical view.</para> + +<para>The JSF configuration file editor has three views: Diagram, Tree and Source. All views are +synchronized, you can edit the file in any view.</para> +<figure> +<title>Diagram View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_32.png"/> + </imageobject> +</mediaobject> +</figure> +<figure> +<title>Tree View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_33.png"/> + </imageobject> +</mediaobject> +</figure> + +<figure> +<title>Source View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_34.png"/> + </imageobject> +</mediaobject> +</figure> +<para>The same applies to all other Red Hat Developer Studio editors.</para> + +<para>Web XML editor is shown. Web XML editor has a graphical view (Tree) and source (Source).</para> + +<figure> +<title>Tree View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_35.png"/> + </imageobject> +</mediaobject> +</figure> +<figure> +<title>Source View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_36.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Red Hat Developer Studio TLD file editor shown in Tree view. At any point you can edit the source by going + switching to Source view.</para> +<figure> +<title>Tree Editor</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_37.png"/> + </imageobject> +</mediaobject> +</figure> +<figure> +<title>Source Editor</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_38.png"/> + </imageobject> +</mediaobject> +</figure> +<para>The Struts configuration file editor has three views: Diagram, Tree and Source. All views are synchronized, + you can edit the file in any view.</para> +<figure> +<title>Struts Diagram View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_39.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Source view. Any changes here will immediately appear in all other views.</para> +<figure> +<title>Struts Source View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/editors_features/editors_features_40.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> + + +<section id="visual_page"> +<?dbhtml filename="visual_page.html"?> +<title>Visual Page Editor</title> +<para>Red Hat Developer Studio comes with a powerful and customizable <property>Visual Page Editor</property> (VPE). You can use the Visual Page Editor to develop an application using any technology: JSF, Struts, JSP, HTML and others.</para> + +<section id="visual_tabs"> +<?dbhtml filename="visual_tabs.html"?> + +<para>Current VPE version has four tabs: Visual/Source, Visual, Source and Preview.</para> +<para>Split screen design with instant synchronization between source and visual views:</para> +<figure> +<title>Visual/Source View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_1.png" /> + </imageobject> +</mediaobject> +</figure> + +<para>You can also switch to pure Visual design:</para> +<figure> +<title>Visual View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_2.png" /> + </imageobject> +</mediaobject> +</figure> + +<para>Or work just in Source view. Note that selection bar is now available not only in Visual mode but also in Source one:</para> +<figure> +<title>Source View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_3.png" /> + </imageobject> +</mediaobject> +</figure> +<para>No matter what view you select, you get full integration with Properties and Outline views:</para> +<figure> +<title>Properties And Outline Views</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_4.png" /> + </imageobject> +</mediaobject> +</figure> +<para>Preview mode is read-only, it only shows how the page will look like in a browser.</para> +<figure> +<title>Preview Mode</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_5.png" /> + </imageobject> +</mediaobject> +</figure> +<para>Use the graphical toolbar to add inline styling to any tag.</para> +<figure> +<title>Graphical Toolbar</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_6.png" /> + </imageobject> +</mediaobject> +</figure> +<para>With just a click or drag-and-drop insert any tags from the palette on to the page you are editing.</para> +<figure> +<title>Inserting Tags From Palette</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_7.png" /> + </imageobject> +</mediaobject> +</figure> + +<section id="AdvancedSettings954"> +<?dbhtml filename="AdvancedSettings.html"?> +<title>Advanced Settings</title> + + <para>There are three buttons on the <property>Visual Page Editor</property> left side:</para> + + <figure> + <title>Visual Page Editor Buttons</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_8.png" /> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem><para>Preferences</para></listitem> + </itemizedlist> + <para>Provides quick access to Visual Page Editor preferences.</para> + <figure> + <title>Visual Page Editor Preferences Window</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_9.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem><para>Refresh</para></listitem> + </itemizedlist> + <para>Refresh displaying information with this button.</para> + + <itemizedlist> + <listitem><para>Page Design Options</para></listitem> + </itemizedlist> +<para>This button leads to page design options.</para> + <figure> + <title>Page Design Options</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_10.png" /> + </imageobject> + </mediaobject> + </figure> +<para>This dialog let's you set resources which are usually only resolved in runtime. To set a stylesheet, + click <emphasis><property>Add</property></emphasis> (for CSS File Path section) and add your stylesheet. It works when CSS is defined on your page in the following way:</para> + +<para>Code:</para> + <programlisting role="XML"><![CDATA[<link rel="stylesheet" type="text/css" href="#{facesContext.externalContext.requestContextPath}/style.css"/> +]]></programlisting> + +<para>This will work fine in runtime, but the Visual Page Editor doesn't know what requestContextPath in design time is.</para> + +<para>The next section (URI), let's you add URI taglibs if you are using includes so that the editor knows + where to find the tag libraries.</para> + +<para>The first two sections let you define actual runtime folders. Here is an example.</para> + +<para>Let's say you have the following project structure:</para> + +<programlisting role="XML"><![CDATA[WebContent/ + pages/ + img/ + a.gif + header.jsp + main.jsp +]]></programlisting> +<para>header.jsp content:</para> +<programlisting role="XML"><![CDATA[My Header +<img src="img/a.gif"/> +]]></programlisting> +<para>main.jsp:</para> +<programlisting role="XML"><![CDATA[<jsp:include page="pages/header.jsp" /> +]]></programlisting> +<para> + When you open <emphasis><property>main.jsp</property></emphasis> in Visual Page Editor, it will not be able to resolve the image from the header, + however, it will work fine in runtime. To fix this in design time, click the <emphasis><property>Page Design Options</property></emphasis> button and + set <emphasis><property>Actual Run-Time Relative</property></emphasis> Folder to <emphasis><property><project>WebContent > pages</property></emphasis> and you will see the image appear.</para> +<para></para> + <itemizedlist> + <listitem><para>Hide Selection bar</para></listitem> + </itemizedlist> +<para> By clicking on the component in Visual view or selecting a code snippet in Source mode you can see the tags tree. If you want to hide the selection bar, use the "Hide Selection Bar" button on the lower right side.</para> + + <figure> + <title>Selection Bar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/visual_page/visual_page_11.png"/> + </imageobject> + </mediaobject> + </figure> + </section> +</section> + +<section id="SetupnotesforLinu895x"> +<?dbhtml filename="SetupNotesforLinux.html"?> +<title>Setup notes for Linux</title> +<section id="HowToStartTheVisualPageEditorUnderLinux85"> +<?dbhtml filename="HowToStartTheVisualPageEditorUnderLinux.html"?> +<title>How to Start the Visual Page Editor under Linux</title> + +<para>Linux users may need to do the following to get the Visual Editor to work correctly on their machines.</para> + <itemizedlist> +<listitem><para>On Fedora or Red Hat Enterprise Linux distributions, install the compat-libstdc++-33.i386 and libXp packages:</para></listitem> +</itemizedlist> +<programlisting role="JAVA"><![CDATA[yum install compat-libstdc++-33 libXp +]]></programlisting> + +<itemizedlist> +<listitem><para>On other rpm-based distributions download libXp.i386 package from <ulink url="http://rpm.pbone.net/index.php3/stat/4/idpl/3418392/com/libXp-1.0.0-8.i38...">here</ulink> +</para></listitem> +<listitem><para>And install it on your machine:</para></listitem> +</itemizedlist> +<programlisting role="JAVA"><![CDATA[rpm -U libXp-1.0.0-8.i386 +]]></programlisting> + +<itemizedlist> +<listitem><para>Open the RHDS perspective. If you see the Help view open, close it and restart RHDS +</para></listitem> +</itemizedlist> +</section> + +  +</section> + +<section id="JSPsyntaxvalidation84"> +<?dbhtml filename="JSPsyntaxValidation.html"?> +<title>JSP syntax validation</title> +<para>When working in JBoss Tools JSP editor you are constantly provided with feedback and +contextual error checking as you type.</para> +</section> + +  + +<section id="HTML401Suppor421t"> +<?dbhtml filename="HTML4.01Support.html"?> +<title>HTML 4.01 Support</title> +</section> + +<section id="JSP2.0JSTL1.0And1.1Suppor52t"> +<?dbhtml filename="JSP2.0JSTL1.0And1.1Support.html"?> +<title>JSP 2.0, JSTL 1.0/1.1 support</title> +</section> + +<section id="PageEditorWithPreview53"> +<?dbhtml filename="PageEditorWithPreview.html"?> +<title>JSP Page Preview</title> + +<para>Red Hat Developer Studio comes with JSP design-time preview features. When designing JSP pages you + can easily preview how they will look during runtime. You can even attach your stylesheet to the preview.</para> + +<para>JSP preview is available for:</para> + +<itemizedlist> +<listitem><para>Struts Pages</para></listitem> +<listitem><para>JSF Pages</para></listitem> +</itemizedlist> + +<para>The preview features are available with <link linkend="VisualPageEditor">Visual Page Editor</link>.</para> +</section> +</section> + +<section id="more_editors"> + <?dbhtml filename="more_editors.html"?> +<title>More Editors</title> +<para>Besides Visual Page Editor RHDS provides editors for editing project files of any types: properties, TLD, web.xml, tiles, and so on.</para> +<section id="GraphicalPropertiesEditor"> +<?dbhtml filename="GraphicalPropertiesEditor.html"?> +<title>Graphical Properties Editor</title> + + <para><property>The Properties editor</property> allows you to work in two different modes and also supports unicode characters.</para> + + <para>To create a new properties file, in the Package Explorer view, select<emphasis><property> New > Properties File</property></emphasis> from the right-click context menu on the folder where you want to create the file.</para> +<figure> +<title>Selecting Properties File</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_1.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can edit the file using a table-oriented "Properties" viewer:</para> + +<figure> +<title>"Properties" Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_2.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also use a Source viewer for editing the file:</para> +<figure> +<title>Source Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_3.png"/> + </imageobject> +</mediaobject> +</figure> +</section> + +<section id="GraphicalTLDEditor"> +<?dbhtml filename="GraphicalTLDEditor.html"?> +<title>Graphical TLD Editor</title> + + <para><property>The TLD editor</property> comes with same features you will find in all other Red Hat Developer Studio editors:</para> + +<itemizedlist> +<listitem><para>Graphical and source edit modes</para></listitem> +<listitem><para>Validation and error checking</para></listitem> +</itemizedlist> +<section id="TreeView2"> +<?dbhtml filename="TreeView.html"?> +<title>Tree view</title> + +<figure> +<title>Tree View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_4.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="SourceView1"> +<?dbhtml filename="SourceView.html"?> +<title>Source view</title> + +<para>You can easily switch from Tree to Source by selecting the Source tab at the bottom of the editor.</para> + +<figure> +<title>Source View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_5.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can easily add a <property>new tag</property>:</para> + +<figure> +<title>Adding a New Tag</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_6.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also easily add a <property>new attribute</property> to an existing tag:</para> +<figure> +<title>Adding a New Attribute</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_7.png"/> + </imageobject> +</mediaobject> +</figure> +<para>Content assist is available when editing the file using the Source viewer:</para> + +<figure> +<title>Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_8.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>In the Source viewer, if at any point a tag is incorrect or incomplete, an error will be indicated +next to the line and also in the Problems view below.</para> + +<figure> +<title>Error Reporting</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_9.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> + + +<section id="GraphicalWebApplicationFile(web.xml)Editor"> +<?dbhtml filename="GraphicalWebApplicationFile(web.xml)Editor.html"?> +<title>Graphical Web Application File (web.xml) Editor</title> + +<para>The Web Application File editor comes with the same features you will find in all other +Red Hat Developer Studio editors:</para> + +<itemizedlist> +<listitem><para>Graphical and source edit modes</para></listitem> +<listitem><para>Validation and error checking</para></listitem> +</itemizedlist> +<section id="TreeView1"> +<title>Tree View</title> + +<figure> +<title>Tree View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_10.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can add any new elements right in the <property>Tree viewer</property>:</para> + +<figure> +<title>Adding New Elements</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_11.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="SourceView2"> +<?dbhtml filename="SourceView.html"?> +<title>Source View</title> + +<para>Switch to the <property>Source viewer </property>to edit the web.xml file by hand at any time:</para> + +<figure> +<title>Source View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_12.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="ContentAssist"> +<?dbhtml filename="ContentAssist.html"?> +<title>Content Assist</title> + +<para>Content assist is available in the Source viewer. Simply click <emphasis><property>CTRL-Space</property></emphasis> anywhere in the file.</para> + +<figure> +<title>Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_13.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="ErrorCheckingAndValidation"> +<?dbhtml filename="ErrorCheckingAndValidation.html"?> +<title>Errors Checking and Validation</title> + +<para>If errors occur anywhere in the file, small red dots will appear next to the lines where the errors + occurred. Also, note that the file is marked by a small x in the Package Explorer view.</para> + +<figure> +<title>Errors Reporting</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_14.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> +<section id="GraphicalTilesFilesEditor"> +<?dbhtml filename="GraphicalTilesFilesEditor.html"?> +<title>Graphical Tiles Files Editor</title> +<section id="GraphicalEditorForTilesFiles"> +<?dbhtml filename="GraphicalEditorForTilesFiles.html"?> +<title>Graphical Editor For Tiles Files</title> +<para>The Tiles configuration file editor has three main viewers (modes): Tree (shown), Diagram and Source. The modes can be selected via the tabs at the bottom of the editor. Any changes made in one mode are immediately visible when you switch to any other mode.</para> + +<para>When working in Source view, you always have all following features available:</para> + +<itemizedlist> +<listitem><para>Content Assist</para></listitem> +<listitem><para>Open On Selection</para></listitem> +</itemizedlist> +</section> +<section id="CreateNewTilesFile"> +<?dbhtml filename="GraphicalTilesFilesEditor.html"?> +<title>Create New Tiles File</title> + +<para>To create a new Tiles files, right click any folder and select <emphasis><property>New > Tiles Files</property></emphasis>:</para> + +<figure> +<title>Creating New Tiles File</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_15.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="TreeView3"> +<?dbhtml filename="TreeView.html"?> +<title>Tree View</title> + +<para>In the Tree mode, the different elements of the Tiles file are organized into functional categories +on the left-hand side and a form for editing the properties of currently selected items on the right-hand + side.</para> + +<figure> +<title>Tree View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_16.png"/> + </imageobject> +</mediaobject> +</figure> +<para>To edit the file, simply right click any node and select among the available actions:</para> + +<figure> +<title>Editing in Tiles Editor</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_17.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="DiagramView"> +<?dbhtml filename="TreeView.html"?> +<title>Diagram View</title> + +<para>The Diagram mode is shown below:</para> +<figure> +<title>Diagram View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_18.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>To create new definition, simply right click anywhere in the diagram:</para> +<figure> +<title>Creating New Definition</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_19.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also use the Diagram toolbar to make editing easier:</para> + +<figure> +<title>Diagram Toolbar</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_20.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="Source"> +<?dbhtml filename="TreeView.html"?> +<title>Source</title> + + <para>The Tiles editor also comes with a <property>Source view</property> that gives you full control over the source. +Any changes here will immediately appear in when you switch to any of the other viewers.</para> +<figure> +<title>Source View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_21.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>Content assist is available in the Source mode.</para> + +<figure> +<title>Content Assist</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_22.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>Any errors are immediately reported as shown below:</para> +<figure> +<title>Error Reporting</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_23.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also use the Outline view together with the editor's Source mode. Selecting any node in the Outline view will jump to that place in the source:</para> + +<figure> +<title>Outline View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_24.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +</section> + + + +<section id="GraphicalEditorForStrutsValidationFiles"> +<?dbhtml filename="GraphicalStrutsValidationFilesEditor.html"?> +<title>Graphical Editor for Struts Validation Files</title> +<para>Red Hat Developer Studio comes with a visual validation editor. To create a new validation file, +right click any folder and select <emphasis><property>File > Validation File</property></emphasis> from the context menu.</para> + +<figure> +<title>Creating Validation File</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_25.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>The validation editor works through a number of viewers.</para> + +<para>The Formsets viewer shows forms and their elements for which to define validation rules:</para> + +<figure> +<title>Formsets Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_26.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>The Constants viewer lets you set constant values for your validation rules:</para> + +<figure> +<title>Constants viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_27.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>The validation file also can be viewed in a Tree viewer:</para> + +<figure> +<title>Tree Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_28.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>At any point you have full control over the source by switching to the Source viewer. Any editing +in this viewer will immediately be available in the other viewers of this editor.</para> + +<figure> +<title>Source Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_29.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also open your own custom or Struts-standard validation-rules.xml file.</para> + +<para>The Validators viewer shows the validation rules for a selected validator. You can of course add your + own rules.</para> + +<figure> +<title>Validation Rules</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_30.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>Here are the validation rules shown in the Source viewer.</para> + +<figure> +<title>Validation Rules in Source Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_31.png"/> + </imageobject> +</mediaobject> +</figure> +</section> +<section id="SpringIDE"> +<?dbhtml filename="SpringIDE.html"?> +<title>Spring IDE</title> + <para>Red Hat Developer Studio bundles a <property>Spring Framework editor</property> from <ulink url="http://springide.org/project">Spring IDE for Eclipse</ulink>. Visit this site for the latest versions and documentation.</para> + + <para>You can add a <property>Spring Project nature</property> to an existing project by right-clicking on the project and + selecting from the context menu:</para> + +<figure> + <title>Adding Spring Project Nature</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_32.png"/> + </imageobject> + </mediaobject> + </figure> + + + <para>Once the nature is added, you will see a small <property>"S"</property> decorating a Spring project in the Package Explorer + view. To remove the nature, right click the project and select <emphasis><property>Remove Spring Project Nature</property></emphasis>:</para> + +<figure> + <title>Project with Spring Nature</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_33.png"/> + </imageobject> + </mediaobject> + </figure> + +<para>After creating a Spring configuration file with bean definitions:</para> + +<figure> + <title>Spring Configuration File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_34.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Select Spring Beans project with <emphasis><property>Project > Properties > Spring > Beans Support</property></emphasis> from the menu bar:</para> + +<figure> + <title>Spring Beans</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_35.png"/> + </imageobject> + </mediaobject> + </figure> + +<para> Now you can add the Spring bean configuration files to your project by clicking on <emphasis><property>Add</property></emphasis> button:</para> + +<figure> + <title>Adding Configuration Files</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_36.png"/> + </imageobject> + </mediaobject> +</figure> + +<para>Once you add this file, the file will be marked by an "S" to indicate a Spring bean file:</para> + +<figure> + <title>Spring Bean File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_37.png"/> + </imageobject> + </mediaobject> +</figure> + + <para>To activate the Spring Beans view, select <emphasis><property>Window > Show View... > Other</property></emphasis> and then <emphasis><property>Spring Explorer> Spring Beans</property></emphasis> from the + menu bar:</para> + +<figure> + <title>Selecting Spring Beans View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_38.png"/> + </imageobject> + </mediaobject> + </figure> + +<para>The Spring Beans view shows a read-only outline view of the Spring bean configuration file:</para> + +<figure> + <title>Spring Beans View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_39.png"/> + </imageobject> + </mediaobject> +</figure> + +<para>Using a context menu, you can select a graph view of the Spring configuration file's referenced + beans:</para> + +<figure> + <title>Graph View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_40.png"/> + </imageobject> + </mediaobject> +</figure> +</section> + +<section id="CSSEditor"> +<?dbhtml filename="CSSEditor.html"?> +<title>CSS Editor</title> + + <para>The <property>CSS editor</property> comes with the same features you will find in all other Red Hat Developer Studio editors.</para> + +<itemizedlist> +<listitem><para>Content assist</para></listitem> +<listitem><para>Validation and error checking</para></listitem> +</itemizedlist> + +<para>With the CSS (Cascading Style Sheet) editor, you can take advantage of code prompting:</para> + +<figure> +<title>CSS Editor</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_41.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also use the Outline view next to the editor to navigate through the CSS file:</para> + +<figure> +<title>Outline View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_42.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>And you can also use the Properties view next to the editor to edit existing stylesheet +declaration properties:</para> + +<figure> +<title>Properties View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_43.png"/> + </imageobject> +</mediaobject> +</figure> + +</section> +<section id="JavaScriptEditor"> +<?dbhtml filename="JavaScriptEditor.html"?> +<title>JavaScript Editor</title> + + <para>The <property>JavaScript editor</property> includes a Preview viewer and a Source viewer. In the Source viewer, you can use code assist:</para> + +<figure> +<title>JavaScript Editor</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_44.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also use the Source viewer with the Outline view to navigate around the file:</para> + +<figure> +<title>Source Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_45.png"/> + </imageobject> +</mediaobject> +</figure> + +</section> +<section id="ImageViewer"> +<?dbhtml filename="ImageViewer.html"?> +<title>Image Viewer</title> +<para>This simple image viewer allows you to view GIF and JPEG files individually in a separate window:</para> + +<figure> +<title>Image Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_46.png"/> + </imageobject> +</mediaobject> +</figure> + +</section> +<section id="XSDEditor"> +<?dbhtml filename="XSDEditor.html"?> +<title>XSD Editor</title> + + <para>Red Hat Developer Studio comes with an <property>XSD Editor</property> for XML Schema files. This editor comes from the Web Tools Project (WTP) (see <ulink url="http://www.eclipse.org/webtools/testtutorials/gettingstarted/GettingStart...">WTP Getting Started</ulink>).</para> + + <para>To create a new XSD file, right-click a folder in the Package Explorer view, select <emphasis><property>New > Other...</property></emphasis> from the context menu and then select <emphasis><property>XML > XML Schema</property></emphasis> in the dialog box.</para> + +<figure> +<title>Creating New XSD file</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_47.png"/> + </imageobject> +</mediaobject> +</figure> + + <para>The XSD Editor includes two viewers for working on the file, a Design viewer and a Source viewer:</para> + +<figure> +<title>Source Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_48.png"/> + </imageobject> +</mediaobject> +</figure> + + <para>In the Design viewer, you can drill down on an element by double-clicking on it:</para> + +<figure> + <title>Design Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_49.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>Various edit options are available when you right-click an element in the diagram:</para> + +<figure> +<title>Edit Options</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_50.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also use the Properties view to edit a selected element:</para> + +<figure> +<title>Properties View</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_51.png"/> + </imageobject> +</mediaobject> +</figure> + +<para>You can also use a Source viewer for the file. In this viewer, along with direct editing of the + source code, you can also edit the file by using the Properties view on the right:</para> + +<figure> +<title>Source Viewer</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_52.png"/> + </imageobject> +</mediaobject> +</figure> + +</section> +<section id="SupportforXMLSchema"> +<?dbhtml filename="SupportforXMLSchema.html"?> +<title>Support for XML Schema</title> + +<para>Red Hat Developer Studio fully supports XML files based on schemas as well as DTDs:</para> +<figure> +<title>XML File</title> +<mediaobject> + <imageobject> + <imagedata fileref="images/more_editors/more_editors_53.png"/> + </imageobject> +</mediaobject> +</figure> + +</section> +</section> + +</chapter> \ No newline at end of file Added: trunk/jsf/docs/userguide/en/modules/jboss_tools.xml =================================================================== --- trunk/jsf/docs/userguide/en/modules/jboss_tools.xml (rev 0) +++ trunk/jsf/docs/userguide/en/modules/jboss_tools.xml 2007-11-20 16:29:12 UTC (rev 4987) @@ -0,0 +1,36 @@ +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="jboss_tools" xreflabel="jboss_tools"> + <?dbhtml filename="jboss_tools.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Eclipse</keyword> + <keyword>Java</keyword> + <keyword>Tomcat</keyword> + </keywordset> + </chapterinfo> + <title>JBoss Tools</title> +<para>JBoss Tools is an umbrella project for the JBoss developed plugins that will make it into Red Hat Developer Studio. It includes the following Eclipse modules:</para> +<itemizedlist> + <listitem><para><emphasis><property>Seam Tools</property></emphasis> Will include support for seam-gen, RichFaces VE integration, Seam related code completion and refactoring and more.</para> + <para>To read more on Seam, see <ulink url="http://docs.jboss.com/seam/2.0.0.GA/reference/en/html/index.html">Seam Reference Guide </ulink> or <ulink url="http://www.redhat.com/developers/rhds/Getting_Started/GetStartSeamGen.html">Getting Started Guide</ulink></para></listitem> +  + + <listitem><para><emphasis><property>RichFaces Support</property></emphasis>. <para>Rich Faces is an open source framework that adds Ajax capability into existing JSF applications without resorting to JavaScript.</para> + <para>To read more on RF, see<ulink url="http://labs.jboss.com/jbossrichfaces/docs/index.html"> RF Developer Guide</ulink></para></listitem> + + <listitem><para><emphasis><property>Hibernate Tools</property></emphasis>Supporting mapping files, annotations and JPA with reverse engineering, code completion, project wizards, refactoring, interactive HQL/JPA-QL/Criteria execution and more.In short a merger of Hibernate Tools and Exadel ORM features.</para> + <para>To read more on Hibernate Tools, see <ulink url="http://www.hibernate.org/hib_docs/tools/reference/en/html/">Hibernate Tools Reference Guide</ulink></para></listitem> + + <listitem><para><emphasis><property>JBoss AS Tools</property></emphasis> Easy start, stop and debug of JBoss AS 4+ servers from within Eclipse. Will also include features for efficient packaging and deployment of any type of Eclipse project.</para></listitem> +  + + <listitem><para><emphasis><property>Drools IDE</property></emphasis>Rules file editing, Rete View, working memory debugging/inspection and more.</para></listitem> +  + + <listitem><para><emphasis><property>JBPM Tools</property></emphasis>JBPM workflow editing, deployment and more.</para></listitem> +  + + </itemizedlist> + +</chapter>

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4986 - in trunk/jsf/docs/userguide/en: modules and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-11-20 11:26:02 -0500 (Tue, 20 Nov 2007) New Revision: 4986 Removed: trunk/jsf/docs/userguide/en/modules/visual_page.xml Modified: trunk/jsf/docs/userguide/en/master.xml trunk/jsf/docs/userguide/en/modules/jsf_support.xml trunk/jsf/docs/userguide/en/modules/roadmap.xml Log: chapters on editors are placed into one chapter name of the guide is changed, as it is mostly of RHDS and not JBossTools http://jira.jboss.com/jira/browse/RHDS-175 Modified: trunk/jsf/docs/userguide/en/master.xml =================================================================== --- trunk/jsf/docs/userguide/en/master.xml 2007-11-20 16:08:24 UTC (rev 4985) +++ trunk/jsf/docs/userguide/en/master.xml 2007-11-20 16:26:02 UTC (rev 4986) @@ -2,39 +2,27 @@ <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" "../../resources/support/docbook-dtd/docbookx.dtd" -[<!ENTITY rhds SYSTEM "modules/rhds.xml"> +[ +<!ENTITY rhds SYSTEM "modules/rhds.xml"> <!ENTITY roadmap SYSTEM "modules/roadmap.xml"> <!ENTITY jsf_support SYSTEM "modules/jsf_support.xml"> <!ENTITY struts SYSTEM "modules/struts.xml"> - - - - - - <!ENTITY palette SYSTEM "modules/palette.xml"> - <!ENTITY web_projects SYSTEM "modules/web_projects.xml"> +<!ENTITY editors SYSTEM "modules/editors.xml"> +<!ENTITY verif_valid SYSTEM "modules/verif_valid.xml"> + - -<!ENTITY visual_page SYSTEM "modules/visual_page.xml"> <!ENTITY verif_valid SYSTEM "modules/verif_valid.xml"> -<!ENTITY editors_features SYSTEM "modules/editors_features.xml"> - -<!ENTITY verif_valid SYSTEM "modules/verif_valid.xml"> - -<!ENTITY visual_page SYSTEM "modules/visual_page.xml"> - -<!ENTITY more_editors SYSTEM "modules/more_editors.xml"> + <!ENTITY preferences SYSTEM "modules/preferences.xml"> -<!ENTITY faq SYSTEM "modules/faq.xml"> + ]> <book> <bookinfo> - <title>JBoss JSF and Struts Tools</title> -  + <title>RHDS Reference Guide</title> <copyright> <year>2007</year> <holder>Red Hat</holder> @@ -45,30 +33,15 @@ </bookinfo> <toc/> - - &rhds; - &roadmap; + &rhds; + &roadmap; &jsf_support; &struts; -  - -  - -  - &palette; - &web_projects; - - -  - &verif_valid; - &editors_features; - &visual_page; - &more_editors; + + &editors; + &preferences; - &faq; - </book> Modified: trunk/jsf/docs/userguide/en/modules/jsf_support.xml =================================================================== --- trunk/jsf/docs/userguide/en/modules/jsf_support.xml 2007-11-20 16:08:24 UTC (rev 4985) +++ trunk/jsf/docs/userguide/en/modules/jsf_support.xml 2007-11-20 16:26:02 UTC (rev 4986) @@ -92,6 +92,14 @@ </mediaobject> </figure> <para>The JBoss Tools Palette comes with the Facelets components ready to use. A useful tip appears when you hover the mouse cursor over the tag:</para> + + <figure> <title>Facelets Components</title> <mediaobject> Modified: trunk/jsf/docs/userguide/en/modules/roadmap.xml =================================================================== --- trunk/jsf/docs/userguide/en/modules/roadmap.xml 2007-11-20 16:08:24 UTC (rev 4985) +++ trunk/jsf/docs/userguide/en/modules/roadmap.xml 2007-11-20 16:26:02 UTC (rev 4986) @@ -2,31 +2,45 @@ <chapter id="roadmap" xreflabel="roadmap"> <?dbhtml filename="roadmap.html"?> <title>Roadmap to Learn Red Hat Developer Studio</title> - <para><property>Red Hat Developer Studio</property> is an advanced enterprise-level Web application development environment for - leveraging open source, J2EE and AJAX technologies within the Eclipse environment.</para> - <para>The extensive collection of specialized wizards, - editors and views in Red Hat Developer Studio is constantly - expanding to meet the needs of enterprise developers to keep pace - with rapidly changing business environments. Red Hat Developer - Studio is packed with powerful features, including a WYSIWYG Visual - Page Editor for JSP files and also comprehensive support for Hibernate Object/Relational Mapping covering - reverse-engineering and meet-in-the-middle approaches.</para> -<para>One of the most essential elements of <property>Red Hat Developer Studio</property> is <property>Seam framework</property>. -Seam provides a single programming model for developers to use underlying frameworks such as JSF, EJB3, JMS, Web Services, jBPM, JBoss Rules, Ajax4jsf, RichFaces, Facelets, Spring, iText, Quartz, TestNG, etc., via simple annotated POJOs (Plain Old Java Objects).</para> - <section id="RedHatDeveloperStudio"> - <?dbhtml filename="GettingStartedwithRHDS.html"?> - <title>Red Hat Developer Studio</title> - - <para>Red Hat Developer Studio includes a versatile WYSIWYG Visual Page Editor for JSP files. You have a possibility to visually design HTML/XHTML/JSP/JSF pages with drag and drop or see visual changes as you edit markup:</para> - <figure> + <para><property>Red Hat Developer Studio</property> is an advanced enterprise-level Web application development environment for + leveraging open source, J2EE and AJAX technologies within the Eclipse environment. The extensive collection of specialized wizards, editors and views in Red Hat Developer Studio is constantly expanding to meet the needs of enterprise developers to keep pace with rapidly changing business environments. Red Hat Developer Studio is packed with lot's of powerful features:</para> + + <figure> <title>Red Hat Developer Studio Overview</title> <mediaobject> <imageobject> <imagedata fileref="images/roadmap/roadmap_1.png"/> </imageobject> </mediaobject> - </figure> - <para>Here is the table of main features of <property>Red Hat Developer Studio</property>:</para> +</figure> + +<itemizedlist> +<listitem><para><property>Seam framework</property> Seam provides a single programming model for developers to use underlying frameworks such as JSF, EJB3, JMS, Web Services, jBPM, JBoss Rules, Ajax4jsf, RichFaces, Facelets, Spring, iText, Quartz, TestNG, etc., via simple annotated POJOs (Plain Old Java Objects).</para> +<para>To read more on Seam, see <ulink url="http://docs.jboss.com/seam/2.0.0.GA/reference/en/html/index.html">Seam Reference Guide </ulink> or <ulink url="http://www.redhat.com/developers/rhds/Getting_Started/GetStartSeamGen.html">Getting Started Guide</ulink></para></listitem> + + +<listitem><para><property>Hibernate Tools</property> Supporting mapping files, annotations and JPA with reverse engineering, code completion, project wizards, refactoring, interactive HQL/JPA-QL/Criteria execution and more. In short a merger of Hibernate Tools and Exadel ORM features.</para> +<para>To read more on Hibernate Tools, see <ulink url="http://www.hibernate.org/hib_docs/tools/reference/en/html/">Hibernate Tools Reference Guide</ulink></para></listitem> + +<listitem><para><property>RichFaces Support</property>. Rich Faces is an open source framework that adds Ajax capability into existing JSF applications without resorting to JavaScript.</para> +<para>To read more on RF, see<ulink url="http://labs.jboss.com/jbossrichfaces/docs/index.html"> RF Developer Guide</ulink></para></listitem> + +<listitem><para><emphasis><property>JBoss AS Tools</property></emphasis> Easy start, stop and debug of JBoss AS 4+ servers from within Eclipse. It also includes features for efficient packaging and deployment of any type of Eclipse project.</para></listitem> + + +<listitem><para><property>JBPM Tools</property> JBPM workflow editing, deployment and more.</para></listitem> + + +<listitem><para><property>WYSIWYG Visual Page Editor </property> gives a possibility to visually design HTML/XHTML/JSP/JSF pages with drag and drop or see visual changes as you edit markup.</para></listitem> + + + +<listitem> And lot's of other useful functionality described further in this guide</listitem> + +</itemizedlist> + + +  + + <para>Red Hat Developer Studio, also has a steady schedule of updates, continues to build on and significantly improve its role as a unique environment that radically simplifies and accelerates application development cycles.</para> + </chapter> Deleted: trunk/jsf/docs/userguide/en/modules/visual_page.xml =================================================================== --- trunk/jsf/docs/userguide/en/modules/visual_page.xml 2007-11-20 16:08:24 UTC (rev 4985) +++ trunk/jsf/docs/userguide/en/modules/visual_page.xml 2007-11-20 16:26:02 UTC (rev 4986) @@ -1,290 +0,0 @@ -<?xml version='1.0' encoding='UTF-8'?> -<chapter id="visual_page" xreflabel="visual_page"> - <?dbhtml filename="visual_page.html"?> - <chapterinfo> - <keywordset> - <keyword>Red Hat Developer Studio</keyword> - <keyword>RHDS</keyword> - <keyword>Visual Page Editor</keyword> - </keywordset> - </chapterinfo> -<title>Visual Page Editor</title> -<para>Red Hat Developer Studio comes with a powerful and customizable <property>Visual Page Editor</property> (VPE). You can use the Visual Page Editor to develop an application using any technology: JSF, Struts, JSP, HTML and others.</para> -<section id="VisualPageEditor174"> -<?dbhtml filename="VisualPageEditor.html"?> -<title>Visual Page Editor</title> - -<para>Now VPE has four tabs: Visual/Source, Visual, Source and Preview.</para> -<para>Split screen design with instant synchronization between source and visual views:</para> - -<figure> -<title>Visual/Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_1.png" /> - </imageobject> -</mediaobject> -</figure> - -<para>You can also switch to pure Visual design:</para> -<figure> -<title>Visual View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_2.png" /> - </imageobject> -</mediaobject> -</figure> - -<para>Or work just in Source view. Note that selection bar is now available not only in Visual mode but also in Source one:</para> -<figure> -<title>Source View</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_3.png" /> - </imageobject> -</mediaobject> -</figure> -<para>No matter what view you select, you get full integration with Properties and Outline views:</para> -<figure> -<title>Properties And Outline Views</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_4.png" /> - </imageobject> -</mediaobject> -</figure> -<para>Preview mode is read-only, it only shows how the page will look like in a browser.</para> -<figure> -<title>Preview Mode</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_5.png" /> - </imageobject> -</mediaobject> -</figure> -<para>Use the graphical toolbar to add inline styling to any tag.</para> -<figure> -<title>Graphical Toolbar</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_6.png" /> - </imageobject> -</mediaobject> -</figure> -<para>With just a click or drag-and-drop insert any tags from the palette on to the page you are editing.</para> -<figure> -<title>Inserting Tags From Palette</title> -<mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_7.png" /> - </imageobject> -</mediaobject> -</figure> - -<section id="AdvancedSettings954"> -<?dbhtml filename="AdvancedSettings.html"?> -<title>Advanced Settings</title> - - <para>There are three buttons on the <property>Visual Page Editor</property> left side:</para> - - <figure> - <title>Visual Page Editor Buttons</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_8.png" /> - </imageobject> - </mediaobject> - </figure> - - <itemizedlist> - <listitem><para>Preferences</para></listitem> - </itemizedlist> - <para>Provides quick access to Visual Page Editor preferences.</para> - <figure> - <title>Visual Page Editor Preferences Window</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_9.png" /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem><para>Refresh</para></listitem> - </itemizedlist> - <para>Refresh displaying information with this button.</para> - - <itemizedlist> - <listitem><para>Page Design Options</para></listitem> - </itemizedlist> -<para>This button leads to page design options.</para> - <figure> - <title>Page Design Options</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_10.png" /> - </imageobject> - </mediaobject> - </figure> -<para>This dialog let's you set resources which are usually only resolved in runtime. To set a stylesheet, - click <emphasis><property>Add</property></emphasis> (for CSS File Path section) and add your stylesheet. It works when CSS is defined on your page in the following way:</para> - -<para>Code:</para> - <programlisting role="XML"><![CDATA[<link rel="stylesheet" type="text/css" href="#{facesContext.externalContext.requestContextPath}/style.css"/> -]]></programlisting> - -<para>This will work fine in runtime, but the Visual Page Editor doesn't know what requestContextPath in design time is.</para> - -<para>The next section (URI), let's you add URI taglibs if you are using includes so that the editor knows - where to find the tag libraries.</para> - -<para>The first two sections let you define actual runtime folders. Here is an example.</para> - -<para>Let's say you have the following project structure:</para> - -<programlisting role="XML"><![CDATA[WebContent/ - pages/ - img/ - a.gif - header.jsp - main.jsp -]]></programlisting> -<para>header.jsp content:</para> -<programlisting role="XML"><![CDATA[My Header -<img src="img/a.gif"/> -]]></programlisting> -<para>main.jsp:</para> -<programlisting role="XML"><![CDATA[<jsp:include page="pages/header.jsp" /> -]]></programlisting> -<para> - When you open <emphasis><property>main.jsp</property></emphasis> in Visual Page Editor, it will not be able to resolve the image from the header, - however, it will work fine in runtime. To fix this in design time, click the <emphasis><property>Page Design Options</property></emphasis> button and - set <emphasis><property>Actual Run-Time Relative</property></emphasis> Folder to <emphasis><property><project>WebContent > pages</property></emphasis> and you will see the image appear.</para> -<para></para> - <itemizedlist> - <listitem><para>Hide Selection bar</para></listitem> - </itemizedlist> -<para> By clicking on the component in Visual view or selecting a code snippet in Source mode you can see the tags tree. If you want to hide the selection bar, use the "Hide Selection Bar" button on the lower right side.</para> - - <figure> - <title>Selection Bar</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/visual_page/visual_page_11.png"/> - </imageobject> - </mediaobject> - </figure> - -</section> -</section> - -<section id="SetupnotesforLinu895x"> -<?dbhtml filename="SetupNotesforLinux.html"?> -<title>Setup notes for Linux</title> -<section id="HowToStartTheVisualPageEditorUnderLinux85"> -<?dbhtml filename="HowToStartTheVisualPageEditorUnderLinux.html"?> -<title>How to Start the Visual Page Editor under Linux</title> - -<para>Linux users may need to do the following to get the Visual Editor to work correctly on their machines.</para> - <itemizedlist> -<listitem><para>On Fedora or Red Hat Enterprise Linux distributions, install the compat-libstdc++-33.i386 and libXp packages:</para></listitem> -</itemizedlist> -<programlisting role="JAVA"><![CDATA[yum install compat-libstdc++-33 libXp -]]></programlisting> - -<itemizedlist> -<listitem><para>On other rpm-based distributions download libXp.i386 package from <ulink url="http://rpm.pbone.net/index.php3/stat/4/idpl/3418392/com/libXp-1.0.0-8.i38...">here</ulink> -</para></listitem> -<listitem><para>And install it on your machine:</para></listitem> -</itemizedlist> -<programlisting role="JAVA"><![CDATA[rpm -U libXp-1.0.0-8.i386 -]]></programlisting> - -<itemizedlist> -<listitem><para>Open the RHDS perspective. If you see the Help view open, close it and restart RHDS -</para></listitem> -</itemizedlist> -</section> - -  -</section> - -<section id="JSPsyntaxvalidation84"> -<?dbhtml filename="JSPsyntaxValidation.html"?> -<title>JSP syntax validation</title> -<para>When working in JBoss Tools JSP editor you are constantly provided with feedback and -contextual error checking as you type.</para> -</section> - -  - -<section id="HTML401Suppor421t"> -<?dbhtml filename="HTML4.01Support.html"?> -<title>HTML 4.01 Support</title> -</section> - -<section id="JSP2.0JSTL1.0And1.1Suppor52t"> -<?dbhtml filename="JSP2.0JSTL1.0And1.1Support.html"?> -<title>JSP 2.0, JSTL 1.0/1.1 support</title> -</section> - -<section id="PageEditorWithPreview53"> -<?dbhtml filename="PageEditorWithPreview.html"?> -<title>JSP Page Preview</title> - -<para>Red Hat Developer Studio comes with JSP design-time preview features. When designing JSP pages you - can easily preview how they will look during runtime. You can even attach your stylesheet to the preview.</para> - -<para>JSP preview is available for:</para> - -<itemizedlist> -<listitem><para>Struts Pages</para></listitem> -<listitem><para>JSF Pages</para></listitem> -</itemizedlist> - -<para>The preview features are available with <link linkend="VisualPageEditor">Visual Page Editor</link>.</para> -</section> - -</chapter> \ No newline at end of file

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4984 - trunk/hibernatetools/docs/resources/support.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2007-11-20 11:04:25 -0500 (Tue, 20 Nov 2007) New Revision: 4984 Removed: trunk/hibernatetools/docs/resources/support/docbook-xsl/ Log: new resources folder that is smaller in size will be commited

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4983 - in trunk/seam/docs/reference/en: modules and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: afedosik Date: 2007-11-20 09:12:23 -0500 (Tue, 20 Nov 2007) New Revision: 4983 Added: trunk/seam/docs/reference/en/images/directory_structure/directory_structure1.png trunk/seam/docs/reference/en/images/directory_structure/directory_structure2.png Modified: trunk/seam/docs/reference/en/modules/creating_new_seam.xml trunk/seam/docs/reference/en/modules/directory_structure.xml trunk/seam/docs/reference/en/modules/generate_entities.xml trunk/seam/docs/reference/en/modules/seam_wizards.xml Log: http://jira.jboss.com/jira/browse/RHDS-289 directory structure info with screens is added Added: trunk/seam/docs/reference/en/images/directory_structure/directory_structure1.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/directory_structure/directory_structure1.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Added: trunk/seam/docs/reference/en/images/directory_structure/directory_structure2.png =================================================================== (Binary files differ) Property changes on: trunk/seam/docs/reference/en/images/directory_structure/directory_structure2.png ___________________________________________________________________ Name: svn:mime-type + application/octet-stream Modified: trunk/seam/docs/reference/en/modules/creating_new_seam.xml =================================================================== --- trunk/seam/docs/reference/en/modules/creating_new_seam.xml 2007-11-20 13:58:40 UTC (rev 4982) +++ trunk/seam/docs/reference/en/modules/creating_new_seam.xml 2007-11-20 14:12:23 UTC (rev 4983) @@ -16,7 +16,9 @@ <title>Create standalone Seam Web Project</title> <para>You are able to enter a name and a location directory for your new project. Next wizard's sections allows you create runtime and server instances in order - to get started creating, running, and debugging J2EE applications.</para> + to get started creating, running, and debugging J2EE applications.</para> + <para>Seam Web Project wizard has an option for selecting the actual Server (not just WTP runtime) that will be used for the project. This allow the wizard to correctly + identify where the needed datasource and driver libraries need to go.</para> <figure> <title>New Seam Project Wizard</title> Modified: trunk/seam/docs/reference/en/modules/directory_structure.xml =================================================================== --- trunk/seam/docs/reference/en/modules/directory_structure.xml 2007-11-20 13:58:40 UTC (rev 4982) +++ trunk/seam/docs/reference/en/modules/directory_structure.xml 2007-11-20 14:12:23 UTC (rev 4983) @@ -12,13 +12,53 @@ <title>Directory Structure of the Generated Project</title> <para>In this chapter we describe where the Seam wizard put the generated files for both EAR and WAR deployments.</para> - - <section id="EAR"> + <para>The Seam Project wizard generates projects like Eclipse WTP style in order to utilize Eclipse WTP features and to have a correct classpath. To be more precise it generates + one project per artifact.</para> + + <section id="WAR"> + <title>WAR Deployment</title> + + <para>The project layout for WAR projects is:</para> + + <figure> + <title>Project Layout for WAR projects</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/directory_structure/directory_structure1.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>WAR projects are generated to enable Seam 1.2.1 war hotdeploy feature. Classes put into <emphasis><property>src/action</property></emphasis> will be + deployed to <emphasis><property>WEB-INF/dev</property></emphasis> from which Seam 1.2.1 automatically will perform hotdeploy of new components.</para> + <note> + <title>Note:</title> + <para>Because of Eclipse WTP limits the hot deployed classes also existen in <emphasis><property>WEB-INF/classes</property></emphasis>, + but since Seam gives <emphasis><property>WEB-INF/dev</property></emphasis> precedence it will work.</para> + </note> + + <para>Furthermore the Seam Project wizard generates a test project that is setup to run TestNG directly against the proper libraries and server runtime libraries. + When the TestNG plugin is installed you can just run your tests via <emphasis><property>Run As > TestNG Test</property>.</emphasis></para> + + + + </section> + + <section id="EAR"> <title>EAR Deployment</title> + <para>The project layout for EAR projects is:</para> + + <figure> + <title>Project Layout for WAR projects</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/directory_structure/directory_structure2.png"/> + </imageobject> + </mediaobject> + </figure> + + </section> + - <section id="WAR"> - <title>WAR Deployment</title> - </section> - </chapter> Modified: trunk/seam/docs/reference/en/modules/generate_entities.xml =================================================================== --- trunk/seam/docs/reference/en/modules/generate_entities.xml 2007-11-20 13:58:40 UTC (rev 4982) +++ trunk/seam/docs/reference/en/modules/generate_entities.xml 2007-11-20 14:12:23 UTC (rev 4983) @@ -11,4 +11,7 @@ <title>Seam Generate Entities</title> + <para>Generate Entities is available directly from within Eclipse using Hibernate Tools plugin for the standard seam-gen generation.</para> + <para>Generate Entities generates a set of CRUD Seam components and web pages based on existing tables in a database or on existing entities in your application.</para> + </chapter> Modified: trunk/seam/docs/reference/en/modules/seam_wizards.xml =================================================================== --- trunk/seam/docs/reference/en/modules/seam_wizards.xml 2007-11-20 13:58:40 UTC (rev 4982) +++ trunk/seam/docs/reference/en/modules/seam_wizards.xml 2007-11-20 14:12:23 UTC (rev 4983) @@ -11,7 +11,20 @@ <title>Seam Wizards</title> + <para>All the Seam component generations options known from Seam-gen are available as wizards (with sensible auto-defaulting) + for creating various common Seam components:</para> + + <itemizedlist> + <listitem><para>Seam Action</para></listitem> + <listitem><para>Seam Form</para></listitem> + <listitem><para>Seam Entity</para></listitem> + <listitem><para>Seam Conversation</para></listitem> + </itemizedlist> + + <para>The wizards creates multiple resources and placed in the apropriate folders dependent on your project structure (WAR or EAR)</para> + <section id="seam_action"> + <title>New Seam Action</title> </section>

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4982 - trunk/jst/plugins/org.jboss.tools.jst.web.tiles.

by jbosstools-commits＠lists.jboss.org

Author: scabanovich Date: 2007-11-20 08:58:40 -0500 (Tue, 20 Nov 2007) New Revision: 4982 Modified: trunk/jst/plugins/org.jboss.tools.jst.web.tiles/build.properties Log: JBIDE-1340 Modified: trunk/jst/plugins/org.jboss.tools.jst.web.tiles/build.properties =================================================================== --- trunk/jst/plugins/org.jboss.tools.jst.web.tiles/build.properties 2007-11-19 20:57:18 UTC (rev 4981) +++ trunk/jst/plugins/org.jboss.tools.jst.web.tiles/build.properties 2007-11-20 13:58:40 UTC (rev 4982) @@ -7,5 +7,6 @@ bin.includes = web-tiles.jar,\ plugin.xml,\ plugin.properties,\ + dtds/,\ META-INF/,\ about.html

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4981 - trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet.

by jbosstools-commits＠lists.jboss.org

Author: dgolovin Date: 2007-11-19 15:57:18 -0500 (Mon, 19 Nov 2007) New Revision: 4981 Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ISeamFacetDataModelProperties.java Log: http://jira.jboss.org/jira/browse/JBIDE-1328 properties that are used as Seam Webg Project Preferencesnames are documented Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ISeamFacetDataModelProperties.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ISeamFacetDataModelProperties.java 2007-11-19 20:50:40 UTC (rev 4980) +++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ISeamFacetDataModelProperties.java 2007-11-19 20:57:18 UTC (rev 4981) @@ -33,51 +33,55 @@ // Seam Preferences names constants /** - * + * Package name used session objects: actions, forms, conversations, beans + * web pages backing beans */ public static final String SESION_BEAN_PACKAGE_NAME = "action.package"; //$NON-NLS-1$ /** - * + * Package name for Entity Beans classes */ public static final String ENTITY_BEAN_PACKAGE_NAME = "model.package"; //$NON-NLS-1$ /** - * + * Connection profile name */ public static final String SEAM_CONNECTION_PROFILE = "seam.project.connection.profile"; //$NON-NLS-1$ /** - * + * Selected deployment type */ public static final String JBOSS_AS_DEPLOY_AS = "seam.project.deployment.type"; //$NON-NLS-1$ /** - * + * Test project name that was created for Seam Web Project */ public static final String SEAM_TEST_PROJECT = "seam.test.project"; //$NON-NLS-1$ /** - * + * Seam runtime name that should be used to create seam artifacts: + * forms, actions, conversations and entities */ public static final String SEAM_RUNTIME_NAME = "seam.runtime.name"; //$NON-NLS-1$ /** - * + * Package where tests for seam artifacts should be placed inside the + * test project */ public static final String TEST_CASES_PACKAGE_NAME = "test.package"; //$NON-NLS-1$ /** - * + * Ejb project name created fro Seam Web Project in EAR deployment configuration */ public static final String SEAM_EJB_PROJECT = "seam.ejb.project"; //$NON-NLS-1$ /** - * + * Ear project name created for Seam Web Project in EAR deployment configuration */ public static final String SEAM_EAR_PROJECT = "seam.ear.project"; //$NON-NLS-1$ - // Seam Facest Wizard Page parameters constants + + // Seam Facet Wizard Page parameters constants public static final String SEAM_PROJECT_NAME = "project.name"; //$NON-NLS-1$

17 years, 1 month

1
0
0 / 0

JBoss Tools SVN: r4980 - trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet.

by jbosstools-commits＠lists.jboss.org

Author: dgolovin Date: 2007-11-19 15:50:40 -0500 (Mon, 19 Nov 2007) New Revision: 4980 Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ISeamFacetDataModelProperties.java Log: http://jira.jboss.org/jira/browse/JBIDE-1328 properties that are used as Seam Webg Project Preferencesnames are documented Modified: trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ISeamFacetDataModelProperties.java =================================================================== --- trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ISeamFacetDataModelProperties.java 2007-11-19 20:35:39 UTC (rev 4979) +++ trunk/seam/plugins/org.jboss.tools.seam.core/src/org/jboss/tools/seam/internal/core/project/facet/ISeamFacetDataModelProperties.java 2007-11-19 20:50:40 UTC (rev 4980) @@ -14,24 +14,77 @@ import org.eclipse.wst.common.project.facet.core.IActionConfigFactory; /** - * Seam facet properties + * Seam facet properties collected in Seam Web Project Wizard. + * Only properties listed below are saved in Seam WebProject Preferences: + * ISeamFacetDataModelProperties.SESION_BEAN_PACKAGE_NAME, + * ISeamFacetDataModelProperties.ENTITY_BEAN_PACKAGE_NAME + * ISeamFacetDataModelProperties.SEAM_CONNECTION_PROFILE + * ISeamFacetDataModelProperties.JBOSS_AS_DEPLOY_AS + * ISeamFacetDataModelProperties.SEAM_TEST_PROJECT + * ISeamFacetDataModelProperties.SEAM_RUNTIME_NAME + * ISeamFacetDataModelProperties.TEST_CASES_PACKAGE_NAME + * ISeamFacetDataModelProperties.SEAM_EJB_PROJECT + * ISeamFacetDataModelProperties.SEAM_EAR_PROJECT * @author eskimo * */ public interface ISeamFacetDataModelProperties extends IActionConfigFactory { - public static final String SEAM_PROJECT_NAME = "project.name"; //$NON-NLS-1$ + // Seam Preferences names constants - public static final String SEAM_PROJECT_INSTANCE = "seam.project.instance"; //$NON-NLS-1$ + /** + * + */ + public static final String SESION_BEAN_PACKAGE_NAME = "action.package"; //$NON-NLS-1$ + + /** + * + */ + public static final String ENTITY_BEAN_PACKAGE_NAME = "model.package"; //$NON-NLS-1$ + /** + * + */ public static final String SEAM_CONNECTION_PROFILE = "seam.project.connection.profile"; //$NON-NLS-1$ + + /** + * + */ + public static final String JBOSS_AS_DEPLOY_AS = "seam.project.deployment.type"; //$NON-NLS-1$ + + /** + * + */ + public static final String SEAM_TEST_PROJECT = "seam.test.project"; //$NON-NLS-1$ + /** + * + */ public static final String SEAM_RUNTIME_NAME = "seam.runtime.name"; //$NON-NLS-1$ + + /** + * + */ + public static final String TEST_CASES_PACKAGE_NAME = "test.package"; //$NON-NLS-1$ + /** + * + */ + public static final String SEAM_EJB_PROJECT = "seam.ejb.project"; //$NON-NLS-1$ + + /** + * + */ + public static final String SEAM_EAR_PROJECT = "seam.ear.project"; //$NON-NLS-1$ + + // Seam Facest Wizard Page parameters constants + + public static final String SEAM_PROJECT_NAME = "project.name"; //$NON-NLS-1$ + + public static final String SEAM_PROJECT_INSTANCE = "seam.project.instance"; //$NON-NLS-1$ + public static final String JBOSS_AS_HOME = "jboss.home"; //$NON-NLS-1$ - public static final String JBOSS_AS_DEPLOY_AS = "seam.project.deployment.type"; //$NON-NLS-1$ - public static final String DB_TYPE = "database.type"; //$NON-NLS-1$ public static final String HIBERNATE_DIALECT = "hibernate.dialect"; //$NON-NLS-1$ @@ -56,18 +109,15 @@ public static final String JDBC_DRIVER_JAR_PATH = "driver.file"; //$NON-NLS-1$ - public static final String SESION_BEAN_PACKAGE_NAME = "action.package"; //$NON-NLS-1$ - + // TODO: should be moved to org.jboss.tools.seam.ui.wizard.IParameter // why is this a property when it is always derivable from sesion_bean_package_name ? public static final String SESION_BEAN_PACKAGE_PATH = "action.package.path"; //$NON-NLS-1$ - - public static final String ENTITY_BEAN_PACKAGE_NAME = "model.package"; //$NON-NLS-1$ + // TODO: should be moved to org.jboss.tools.seam.ui.wizard.IParameter // why is this a property when it is always derivable from entity_bean_package_name ? public static final String ENTITY_BEAN_PACKAGE_PATH = "model.package.path"; //$NON-NLS-1$ - - public static final String TEST_CASES_PACKAGE_NAME = "test.package"; //$NON-NLS-1$ - + + // TODO: should be moved to org.jboss.tools.seam.ui.wizard.IParameter // why is this a property when it is always derivable from test_package_path ? public static final String TEST_CASES_PACKAGE_PATH = "test.package.path"; //$NON-NLS-1$ @@ -75,12 +125,6 @@ public static final String WEB_CONTENTS_FOLDER = "seam.project.web.root.folder"; //$NON-NLS-1$ - public static final String SEAM_EJB_PROJECT = "seam.ejb.project"; //$NON-NLS-1$ - - public static final String SEAM_TEST_PROJECT = "seam.test.project"; //$NON-NLS-1$ - - public static final String SEAM_EAR_PROJECT = "seam.ear.project"; //$NON-NLS-1$ - public static final String DEPLOY_AS_WAR = "war"; //$NON-NLS-1$ public static final String DEPLOY_AS_EAR = "ear"; //$NON-NLS-1$

17 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits November 2007