diff options
Diffstat (limited to 'docs')
568 files changed, 0 insertions, 27533 deletions
diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.cvsignore b/docs/org.eclipse.jst.jsp.ui.infopop/.cvsignore deleted file mode 100644 index c14487ceac..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -build.xml diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.project b/docs/org.eclipse.jst.jsp.ui.infopop/.project deleted file mode 100644 index 01be1bc426..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.jst.jsp.ui.infopop</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts.xml b/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts.xml deleted file mode 100644 index bac1fef208..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts.xml +++ /dev/null @@ -1,74 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> -<context id="jspf1000"> -<description>Select values for the following properties from the drop-down lists: -- <b>Character code:</b> Specifies the page directive's pageEncoding value and contentType charset. In HTML documents, this value is also used for the <META> tag's charset property. -- <b>Language:</b> Specifies the page directive's programming language. -- <b>Content Type:</b> Specifies the contentType's TYPE value for the page directive. In HTML documents, this value is also used for the <META> tag's content property. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="jspr0010"> -<description>Select this option to open the <b>Rename Resource</b> dialog, if applicable, which lets you rename the currently selected Java element and references to that element. -</description> -<topic label="Source editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing source code - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> -<context id="jspr0020"> -<description>Select this option to open the <b>Move</b> dialog, if applicable, which lets you move the currently selected Java element. For example, you can move a method from one class to another. -</description> -<topic label="Source editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing source code - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="webx0050"> -<description>This page lets you specify the line delimiter and the text encoding that will be used when you create or save a JavaServer Pages (JSP) file. - -Various development platforms use different line delimiters to indicate the start of a new line. Select the operating system that corresponds to your development or deployment platform. -<b>Note:</b> This delimiter will not automatically be added to any documents that currently exist. It will be added only to documents that you create after you select the line delimiter type and click <b>Apply</b>, or to existing files that you open and then resave after you select the line delimiter type and click <b>Apply</b>. - -The encoding attribute is used to specify the default character encoding set that is used when creating JSP files. Changing the encoding causes any new JSP files that are created from scratch to use the selected encoding. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="webx0051"> -<description>This page lets you customize the syntax highlighting that the JavaServer Pages (JSP) editor does when you are editing a file." - -The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting. - -The <b>Foreground</b> and <b>Background</b> push buttons open <b>Color</b> dialog boxes that let you specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold. - -Click the <b>Restore Default</b> push button to set the highlighting styles back to their default values. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="webx0052"> -<description>This page lets you create new and edit existing templates that will be used when you edit a JSP file. -</description> -<topic label="Adding and removing JSP templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html"/> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="xmlm1050"> -<description>Select this option to open the <b>Cleanup</b> dialog, which contains settings to update a document so that it is well-formed and formatted. Cleanup includes such activities as inserting missing tags, adding quotation marks around attribute values, node capitalization, and formatting a document. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -</contexts> diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts2.xml b/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts2.xml deleted file mode 100644 index 780835ac94..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/EditorJspContexts2.xml +++ /dev/null @@ -1,83 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> -<context id="jspsource_source_HelpId"> -<description>The JSP source page editor lets you edit a JavaServer Pages file. The editor provides many text editing features, such as content assist, user-defined templates, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -<topic label="Adding and removing JSP templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html"/> -<topic label="Making content assist work for JSP files" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html"/> -</context> - -<context id="jspf1000"> -<description>Select values for the following properties from the drop-down lists: -- <b>Character code:</b> Specifies the page directive's pageEncoding value and contentType charset. In HTML documents, this value is also used for the <META> tag's charset property. -- <b>Language:</b> Specifies the page directive's programming language. -- <b>Content Type:</b> Specifies the contentType's TYPE value for the page directive. In HTML documents, this value is also used for the <META> tag's content property. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="jspr0010"> -<description>Select this option to open the <b>Refactor Rename</b> dialog, if applicable, which lets you rename the currently selected Java element and references to that element. -</description> -<topic label="Source editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing source code - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> -<context id="jspr0020"> -<description>Select this option to open the <b>Refactor Move</b> dialog, if applicable, which lets you move the currently selected Java element. For example, you can move a method from one class to another. -</description> -<topic label="Source editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing source code - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="webx0050"> -<description>This page lets you specify the line delimiter and the text encoding that will be used when you create or save a JavaServer Pages (JSP) file. - -Various development platforms use different line delimiters to indicate the start of a new line. Select the operating system that corresponds to your development or deployment platform. -<b>Note:</b> This delimiter will not automatically be added to any documents that currently exist. It will be added only to documents that you create after you select the line delimiter type and click <b>Apply</b>, or to existing files that you open and then resave after you select the line delimiter type and click <b>Apply</b>. - -The encoding attribute is used to specify the default character encoding set that is used when creating JSP files. Changing the encoding causes any new JSP files that are created from scratch to use the selected encoding. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="webx0051"> -<description>This page lets you customize the syntax highlighting that the JavaServer Pages (JSP) editor does when you are editing a file." - -The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting. - -The <b>Foreground</b> and <b>Background</b> push buttons open <b>Color</b> dialog boxes that let you specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold. - -Click the <b>Restore Default</b> push button to set the highlighting styles back to their default values. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="webx0052"> -<description>This page lets you create new and edit existing templates that will be used when you edit a JSP file. -</description> -<topic label="Adding and removing JSP templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html"/> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="xmlm1050"> -<description>Select this option to open the <b>Cleanup</b> dialog, which contains settings to update a document so that it is well-formed and formatted. Cleanup includes such activities as inserting missing tags, adding quotation marks around attribute values, node capitalization, and formatting a document. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -</contexts> diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/JspWizContexts.xml b/docs/org.eclipse.jst.jsp.ui.infopop/JspWizContexts.xml deleted file mode 100644 index 1d085e2666..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/JspWizContexts.xml +++ /dev/null @@ -1,19 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> - <context id="jspw0010"> - <description> - Select the JSP template checkbox to create your JSP file based on a default template. You can choose to have your JSP created with HTML, XHTML, or XHTML with XML markup. If you do not select a template, your newly created JSP file will be completely blank. - </description> - </context> -</contexts> diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.jsp.ui.infopop/META-INF/MANIFEST.MF deleted file mode 100644 index a703c2c71a..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/META-INF/MANIFEST.MF +++ /dev/null @@ -1,7 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %Plugin.name -Bundle-SymbolicName: org.eclipse.jst.jsp.ui.infopop; singleton:=true -Bundle-Version: 1.0.3.qualifier -Bundle-Vendor: %Bundle-Vendor.0 -Bundle-Localization: plugin diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/about.html b/docs/org.eclipse.jst.jsp.ui.infopop/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/build.properties b/docs/org.eclipse.jst.jsp.ui.infopop/build.properties deleted file mode 100644 index 33cb6c7cea..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/build.properties +++ /dev/null @@ -1,13 +0,0 @@ -bin.includes = EditorJspContexts.xml,\ - EditorJspContexts2.xml,\ - about.html,\ - plugin.xml,\ - META-INF/,\ - META-INF/,\ - EditorJspContexts2.xml,\ - EditorJspContexts.xml,\ - about.html,\ - plugin.properties,\ - plugin.xml,\ - plugin.properties -src.includes = build.properties diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/plugin.properties b/docs/org.eclipse.jst.jsp.ui.infopop/plugin.properties deleted file mode 100644 index 138c44e033..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/plugin.properties +++ /dev/null @@ -1,7 +0,0 @@ -# NLS_MESSAGEFORMAT_VAR -# ============================================================================== -# Translation Instruction: section to be translated -# ============================================================================== -Plugin.name = JSP tools infopops - -Bundle-Vendor.0 = Eclipse.org
\ No newline at end of file diff --git a/docs/org.eclipse.jst.jsp.ui.infopop/plugin.xml b/docs/org.eclipse.jst.jsp.ui.infopop/plugin.xml deleted file mode 100644 index 3d1b116f16..0000000000 --- a/docs/org.eclipse.jst.jsp.ui.infopop/plugin.xml +++ /dev/null @@ -1,27 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.1"?> - -<!-- ================================================= --> -<!-- This is the plugin for declaring the help --> -<!-- contributions for using the tool. --> -<!-- ================================================= --> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - -<extension point="org.eclipse.help.contexts"> - <contexts file="EditorJspContexts.xml" plugin="org.eclipse.jst.jsp.ui"/> - <contexts file="EditorJspContexts2.xml" plugin="org.eclipse.jst.jsp.core"/> - <contexts file="JspWizContexts.xml" plugin="org.eclipse.jst.jsp.ui"/> -</extension> - - -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.doc.user/.cvsignore b/docs/org.eclipse.wst.doc.user/.cvsignore deleted file mode 100644 index 183c840c6f..0000000000 --- a/docs/org.eclipse.wst.doc.user/.cvsignore +++ /dev/null @@ -1,2 +0,0 @@ -build.xml -org.eclipse.wst.doc.user_1.0.0.jar diff --git a/docs/org.eclipse.wst.doc.user/.project b/docs/org.eclipse.wst.doc.user/.project deleted file mode 100644 index 94c75b9860..0000000000 --- a/docs/org.eclipse.wst.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.doc.user/META-INF/MANIFEST.MF deleted file mode 100644 index 1c3bac23fa..0000000000 --- a/docs/org.eclipse.wst.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.wst.doc.user; singleton:=true -Bundle-Version: 1.1.0.qualifier -Bundle-Vendor: %providerName -Bundle-Localization: plugin -Eclipse-LazyStart: true diff --git a/docs/org.eclipse.wst.doc.user/about.html b/docs/org.eclipse.wst.doc.user/about.html deleted file mode 100644 index 86cd081c86..0000000000 --- a/docs/org.eclipse.wst.doc.user/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -<title>About</title> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor's license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.doc.user/book.css b/docs/org.eclipse.wst.doc.user/book.css deleted file mode 100644 index 0df25533a9..0000000000 --- a/docs/org.eclipse.wst.doc.user/book.css +++ /dev/null @@ -1,203 +0,0 @@ -@import "../PRODUCT_PLUGIN/book.css"; - -P.Code { - display: block; - text-align: left; - text-indent: 0.00pt; - margin-top: 0.000000pt; - margin-bottom: 0.000000pt; - margin-right: 0.000000pt; - margin-left: 15pt; - font-size: 10.000000pt; - font-weight: medium; - font-style: Regular; - color: #4444CC; - text-decoration: none; - vertical-align: baseline; - text-transform: none; - font-family: "Courier New"; -} - -H6.CaptionFigColumn { - display: block; - text-align: left; - text-indent: 0.000000pt; - margin-top: 3.000000pt; - margin-bottom: 11.000000pt; - margin-right: 0.000000pt; - margin-left: 0.000000pt; - font-size: 9.000000pt; - font-weight: medium; - font-style: Italic; - color: #000000; - text-decoration: none; - vertical-align: baseline; - text-transform: none; - font-family: "Arial"; -} - -P.Note { - display: block; - text-align: left; - text-indent: 0pt; - margin-top: 19.500000pt; - margin-bottom: 19.500000pt; - margin-right: 0.000000pt; - margin-left: 30pt; - font-size: 11.000000pt; - font-weight: medium; - font-style: Italic; - color: #000000; - text-decoration: none; - vertical-align: baseline; - text-transform: none; - font-family: "Arial"; -} - -EM.UILabel { - font-weight: Bold; - font-style: Regular; - text-decoration: none; - vertical-align: baseline; - text-transform: none; -} - -EM.CodeName { - font-weight: Bold; - font-style: Regular; - text-decoration: none; - vertical-align: baseline; - text-transform: none; - font-family: "Courier New"; -} - -/* following font face declarations need to be removed for DBCS */ -body,h1,h2,h3,h4,h5,h6,p,table,td,caption,th,ul,ol,dl,li,dd,dt { - font-family: Arial, Helvetica, sans-serif; - color: #000000 -} - -pre { - font-family: Courier, monospace -} - -/* end font face declarations */ - /* following font size declarations should be OK for DBCS */ -body,h1,h2,h3,h4,h5,h6,p,table,td,caption,th,ul,ol,dl,li,dd,dt { - font-size: 10pt; -} - -pre { - font-size: 10pt -} - -/* end font size declarations */ -body { - background: #FFFFFF -} - -h1 { - font-size: 18pt; - margin-top: 5; - margin-bottom: 1 -} - -h2 { - font-size: 14pt; - margin-top: 25; - margin-bottom: 3 -} - -h3 { - font-size: 11pt; - margin-top: 20; - margin-bottom: 3 -} - -h4 { - font-size: 10pt; - margin-top: 20; - margin-bottom: 3; - font-style: italic -} - -p { - margin-top: 10px; - margin-bottom: 10px -} - -pre { - margin-left: 6; - font-size: 9pt -} - -a:link { - color: #0000FF -} - -a:hover { - color: #000080 -} - -a:visited { - text-decoration: underline -} - -ul { - margin-top: 0; - margin-bottom: 10 -} - -li { - margin-top: 0; - margin-bottom: 0 -} - -li p { - margin-top: 0; - margin-bottom: 0 -} - -ol { - margin-top: 0; - margin-bottom: 10 -} - -dl { - margin-top: 0; - margin-bottom: 10 -} - -dt { - margin-top: 0; - margin-bottom: 0; - font-weight: bold -} - -dd { - margin-top: 0; - margin-bottom: 0 -} - -strong { - font-weight: bold -} - -em { - font-style: italic -} - -var { - font-style: italic -} - -div.revision { - border-left-style: solid; - border-left-width: thin; - border-left-color: #7B68EE; - padding-left: 5 -} - -th { - font-weight: bold -}
\ No newline at end of file diff --git a/docs/org.eclipse.wst.doc.user/build.properties b/docs/org.eclipse.wst.doc.user/build.properties deleted file mode 100644 index 3d270e953c..0000000000 --- a/docs/org.eclipse.wst.doc.user/build.properties +++ /dev/null @@ -1,12 +0,0 @@ -bin.includes = about.html,\ - common.css,\ - commonltr.css,\ - images/,\ - META-INF/,\ - notices.html,\ - plugin.properties,\ - plugin.xml,\ - toc.xml,\ - topics/,\ - book.css,\ - commonrtl.css diff --git a/docs/org.eclipse.wst.doc.user/common.css b/docs/org.eclipse.wst.doc.user/common.css deleted file mode 100644 index 2f4f3f2f94..0000000000 --- a/docs/org.eclipse.wst.doc.user/common.css +++ /dev/null @@ -1,1197 +0,0 @@ -body { - font-family: Arial, sans-serif; - font-size: 0.8em; - background-color: #ffffff; - color: Black; - margin-right: 5em; - margin-bottom: 1em; -} - -.ibmfilepath { - font-family: monospace; - font-size: 100%; -} - -.ibmcommand { - font-weight: bold; -} - -.ibmemphasis { - font-style: italic; -} - -.mv,.pk,.pkdef,.pv { - font-family: monospace; - font-size: 100%; - padding-top: 0em; - padding-right: .3em; - padding-bottom: 0em; - padding-left: .3em; -} - -tt,samp { - font-family: monospace; - font-size: 100%; -} - -BODY.nav { - background-color: #FFFFFF; - border-right: 0.2em ridge black; - font-size: 0.95em; -} - -.base { - font-weight: normal; - font-style: normal; - font-variant: normal; - text-decoration: none; - background-color: #ffffff; -} - -TABLE { - color: black; - width: 90%; - border-collapse: collapse; - border-color: Black; - background: white; - margin-top: 0.5em; - margin-bottom: 0.5em; - margin-left: 0em; - margin-right: 0em; -} - -.tbldesc { - font-style: italic; -} - -TH { - font-weight: bold; - font-size: 0.7em; - color: black; - background-color: #dadada; - padding-top: 0.1em; - padding-bottom: 0.3em; - padding-left: 1em; - padding-right: 1em; -} - -TH.base { - font-weight: bold; - color: black; - border: 1 solid #606060; - background-color: #dcdada; - padding-top: 0.65em; - padding-bottom: 0.65em; - padding-left: 1em; - padding-right: 1em; -} - -TD { - font-size: 0.7em; - color: black; - background-color: white; - padding-top: 0.1em; - padding-bottom: 0.3em; - padding-left: 1em; - padding-right: 1em; -} - -CITE { - font-style: italic; -} - -EM { - font-style: italic; -} - -STRONG { - font-weight: bold; -} - -caption { - text-align: left; - font-style: italic; -} - -DT { - margin-top: 0.5em; - margin-bottom: 0.5em; -} - -DD { - margin-left: 1.0em; -} - -PRE,pre.cgraphic { - font-family: monospace; - font-size: 12px; - background-color: #dadada; - padding: 5px; -} - -.italic { - font-style: italic; -} - -.bold { - font-weight: bold; -} - -.underlined { - text-decoration: underline; -} - -.bold-italic,.boldItalic { - font-weight: bold; - font-style: italic; -} - -.smallCaps,.smallcaps { - text-transform: uppercase; - font-size: smaller; - font-variant: small-caps; -} - -.italic-underlined { - font-style: italic; - text-decoration: underline; -} - -.bold-underlined { - font-weight: bold; - text-decoration: underline; -} - -.bold-italic-underlined { - font-weight: bold; - font-style: italic; - text-decoration: underline; -} - -.smallcaps-underlined { - font-variant: small-caps; - text-decoration: underline; -} - -.emphasis { - font-style: italic; -} - -.inlinedef { - font-style: italic; -} - -.sidebar { - background: #cccccc; -} - -A:link { - color: #006699; - text-decoration: underline; -} - -A:visited { - color: #996699; - text-decoration: underline; -} - -A:active { - color: #006699; - text-decoration: underline; -} - -A:hover { - color: #996699;; - text-decoration: underline; -} - -a.toclink:link { - text-decoration: none; -} - -a.toclink:active { - text-decoration: none; -} - -a.toclink:visited { - text-decoration: none; -} - -a.toclink:hover { - text-decoration: underline; -} - -a.ptoclink:link { - text-decoration: none; -} - -a.ptoclink:active { - text-decoration: none; -} - -a.ptoclink:visited { - text-decoration: none; -} - -a.ptoclink:hover { - text-decoration: underline; -} - -a.indexlink:link { - text-decoration: none; -} - -a.indexlink:active { - text-decoration: none; -} - -a.indexlink:visited { - text-decoration: none; -} - -a.indexlink:hover { - text-decoration: underline; -} - -a.figurelist:link { - text-decoration: none; -} - -a.figurelist:active { - text-decoration: none; -} - -a.figurelist:visited { - text-decoration: none; -} - -a.figurelist:hover { - text-decoration: underline; -} - -a.tablelist:link { - text-decoration: none; -} - -a.tablelist:active { - text-decoration: none; -} - -a.tablelist:visited { - text-decoration: none; -} - -a.tablelist:hover { - text-decoration: underline; -} - -a.boldgreylink:link { - text-decoration: none; - color: #333333; - font-family: Verdana, Arial, sans-serif; - font-weight: bold; - font-size: 0.9em; -} - -a.boldgreylink:visited { - text-decoration: none; - color: #333333; - font-family: Verdana, Arial, sans-serif; - font-weight: bold; - font-size: 0.9em; -} - -a.boldgreylink:hover { - text-decoration: underline; - color: #333333; - font-family: Verdana, Arial, sans-serif; - font-weight: bold; - font-size: 0.9em; -} - -.runningheader { - font-family: Verdana, Arial, sans-serif; - font-size: 0.7em; -} - -.runningfooter { - font-family: Verdana, Arial, sans-serif; - font-size: 0.7em; -} - -.runningfooter a:link { - font-weight: bold; - color: #000000; - text-decoration: none; -} - -.runningfooter a:active { - font-weight: bold; - color: #000000; - text-decoration: none; -} - -.runningfooter a:visited { - font-weight: bold; - color: #000000; - text-decoration: none; -} - -.runningfooter a:hover { - font-weight: bold; - color: #000000; - text-decoration: underline; -} - -#breadcrumb,.breadcrumb,span.breadcrumbs { - font-size: 0.75em; -} - -.fastpath { - margin-top: 1em; - margin-bottom: 1em; -} - -.fastpathtitle { - font-weight: bold; -} - -.toc { - font-size: small; -} - -.nested0 { - margin-top: 0em; -} - -.p { - margin-top: 1em; -} - -span.figcap { - font-style: italic; -} - -span.figdesc { - font-style: italic; -} - -div.figbox { - -} - -div.figrules { - -} - -div.fignone { - -} - -.fignone { - -} - -.figborder { - -} - -.figsides { - -} - -.figtop { - -} - -.figbottom { - -} - -.figtopbot { - -} - -.parentlink { - -} - -.prevlink { - -} - -.nextlink { - -} - -.relconceptshd { - -} - -.reltaskshd { - -} - -.relrefhd { - -} - -.synnone { - -} - -.synborder { - -} - -.synsides { - -} - -.syntop { - -} - -.synbottom { - -} - -.syntopbot { - -} - -.skip { - margin-top: 1em; -} - -.skipspace { - margin-top: 1em; - margin-bottom: 1em; -} - -.ulchildlink { - margin-top: 1em; - margin-bottom: 1em; -} - -.olchildlink { - margin-top: 1em; - margin-bottom: 1em; -} - -ul,ol { - margin-top: 0.1em; - padding-top: 0.1em; -} - -ul.simple { - list-style-type: none; -} - -ul.indexlist { - list-style-type: none; -} - -OL LI { - margin-top: 0.0em; - margin-bottom: 0.0em; - margin-left: 0.0em; -} - -UL LI { - margin-top: 0.0em; - margin-bottom: 0.0em; - margin-left: 0.0em; -} - -OL LI DIV P { - list-style-type: decimal; - margin-top: 0.2em; - margin-bottom: 0.2em; -} - -UL LI DIV P { - list-style-type: disc; - margin-top: 0.2em; - margin-bottom: 0.2em; -} - -* [compact="yes"]>li { - margin-top: 0 em; -} - -* [compact="no"]>li { - margin-top: 0.5em; -} - -hr { - margin-bottom: 0em; - margin-top: 0em; - padding-top: 0em; - padding-bottom: 0em; - width: 90%; - color: #cccccc; - text-align: center; -} - -H1,.title,.pagetitle,.topictitle1 { - font-size: 1.5em; - font-style: normal; - font-weight: bold; - margin-bottom: 0.5em; - word-spacing: 0.1em; -} - -H2,.subtitle,.pagesubtitle,.topictitle2 { - font-size: 1.25em; - font-style: normal; - font-weight: bold; - margin-bottom: 0.0em; - padding-bottom: 0.0em; -} - -H3,.boldtitle,.topictitle3 { - font-size: 1.0em; - font-style: normal; - font-weight: bold; - margin-bottom: 0.2em; - padding-bottom: 0.1em; -} - -H4,.topictitle4 { - font-size: 0.9em; - font-style: normal; - font-weight: bold; - margin-bottom: 0.1em; - padding-bottom: 0.1em; -} - -h5,.topictitle5 { - font-size: 0.8em; - font-style: normal; - font-weight: bold; - margin-bottom: 0em; - padding-bottom: 0em; -} - -h6,.topictitle6 { - font-size: 0.7em; - font-style: normal; - font-weight: bold; - margin-bottom: 0em; - padding-bottom: 0em; -} - -div.headtitle { - font-size: 1em; - font-weight: bold; - margin-left: 0em; -} - -div.head0 { - font-size: 0.9em; - font-weight: bold; - margin-left: 0em; - margin-top: 0.5em; -} - -div.head1 { - font-size: 0.8em; - font-weight: bold; - margin-left: 1em; - padding-top: 0.5em; -} - -div.head2 { - font-size: 0.7em; - font-weight: normal; - margin-left: 2em; -} - -div.head3 { - font-size: 0.7em; - font-weight: normal; - margin-left: 3em; -} - -div.head4 { - font-size: 0.7em; - font-weight: normal; - margin-left: 4em; -} - -div.head5 { - font-size: 0.7em; - font-weight: normal; - margin-left: 5em; -} - -div.head6 { - font-size: 0.7em; - font-weight: normal; - margin-left: 6em; -} - -div.head7 { - font-size: 0.7em; - font-weight: normal; - margin-left: 7em; -} - -div.head8 { - font-size: 0.7em; - font-weight: normal; - margin-left: 8em; -} - -div.head9 { - font-size: 0.7em; - font-weight: normal; - margin-left: 9em; -} - -.tip { - margin-top: 1em; - margin-bottom: 1em; -} - -.tiptitle { - font-weight: bold; -} - -.firstcol { - font-weight: bold; -} - -.ptocH1 { - font-size: x-small; -} - -.ptocH2 { - font-size: x-small; -} - -.stitle { - font-style: italic; - text-decoration: underline; -} - -.nte { - -} - -.xxlines { - white-space: pre; - font-size: 0.95em; -} - -.sectiontitle { - margin-top: 1em; - margin-bottom: 0em; - color: black; - font-size: 1.2em; - font-weight: bold; -} - -div.imageleft { - text-align: left; -} - -div.imagecenter { - text-align: center; -} - -div.imageright { - text-align: right; -} - -div.imagejustify { - text-align: justify; -} - -div.mmobj { - margin-top: 1em; - margin-bottom: 1em; - text-align: center; -} - -div.mmobjleft { - margin-top: 1em; - margin-bottom: 1em; - text-align: left; -} - -div.mmobjcenter { - margin-top: 1em; - margin-bottom: 1em; - text-align: center; -} - -div.mmobjright { - margin-top: 1em; - margin-bottom: 1em; - text-align: right; -} - -pre.screen { - padding: 1em 1em 1em 1em; - margin-top: 0.4em; - margin-bottom: 0.4em; - border: thin solid Black; - font-size: 100%; -} - -.prereq { - margin-left: 1.5em; -} - -.defListHead { - font-weight: bold; - text-decoration: underline; -} - -span.mv { - font-style: italic; -} - -span.md { - text-decoration: line-through; -} - -.pk,span.pk { - font-weight: bold; -} - -span.pkdef { - font-weight: bold; - text-decoration: underline; -} - -span.pv { - font-style: italic; -} - -span.pvdef { - font-style: italic; - text-decoration: underline; -} - -span.kwd { - font-weight: bold; -} - -span.kdwdef { - font-weight: bold; - text-decoration: underline; -} - -.parmListKwd { - font-weight: bold; -} - -.parmListVar { - font-style: italic; -} - -span.oper { - font-style: normal; -} - -span.operdef { - text-decoration: underline; -} - -VAR,span.var { - font-style: italic; -} - -span.vardef { - font-style: italic; - text-decoration: underline; -} - -div.msg { - padding: 0.2em 1em 1em 1em; - margin-top: 0.4em; - margin-bottom: 0.4em; -} - -div.msgnum { - float: left; - font-weight: bold; - margin-bottom: 1em; - margin-right: 1em; -} - -div.msgtext { - font-weight: bold; - margin-bottom: 1em; -} - -div.msgitemtitle { - font-weight: bold; -} - -p.msgitem { - margin-top: 0em; -} - -.attention,div.attention { - margin-top: 1em; - margin-bottom: 1em; -} - -.attentiontitle,span.attentiontitle { - font-weight: bold; -} - -.cautiontitle,div.cautiontitle { - margin-top: 1em; - font-weight: bold; -} - -.caution,div.caution { - margin-top: 1em; - margin-bottom: 1em; -} - -.danger,div.danger { - padding: 0.5em 0.5em 0.5em 0.5em; - border: solid; - border-width: thin; - font-weight: bold; - margin-top: 0.2em; - margin-bottom: 1em; -} - -.dangertitle,div.dangertitle { - margin-top: 1em; - font-weight: bold; -} - -.important { - margin-top: 1em; - margin-bottom: 1em; -} - -.importanttitle { - font-weight: bold; -} - -.remember { - margin-top: 1em; - margin-bottom: 1em; -} - -.remembertitle { - font-weight: bold; -} - -.restriction { - margin-top: 1em; - margin-bottom: 1em; -} - -.restrictiontitle { - font-weight: bold; -} - -div.warningtitle { - font-weight: bold; -} - -div.warningbody { - margin-left: 2em -} - -.note { - margin-top: 1em; - margin-bottom: 1em; -} - -.notetitle,div.notetitle { - font-weight: bold; -} - -div.notebody { - margin-left: 2em; -} - -div.notelisttitle { - font-weight: bold; -} - -div.fnnum { - float: left; -} - -div.fntext { - margin-left: 2em; -} - -div.stepl { - margin-left: 2em; -} - -div.steplnum { - font-weight: bold; - float: left; - margin-left: 0.5em; -} - -div.stepltext { - margin-left: 5em; -} - -div.steplnum { - font-style: italic; - font-weight: bold; - float: left; - margin-left: 0.5em; -} - -div.stepltext { - margin-bottom: 0.5em; - margin-left: 3em; -} - -div.ledi { - margin-left: 3em; -} - -div.ledesc { - margin-left: 3em; -} - -span.pblktitle { - font-weight: bold; -} - -div.pblklblbox { - padding: 0.5em 0.5em 0.5em 0.5em; - border: solid; - border-width: thin; - margin-top: 0.2em; -} - -span.ednoticestitle { - font-weight: bold; -} - -span.uicontrol { - font-weight: bold; -} - -span.term { - font-weight: bold; -} - -span.idxshow { - color: green; -} - -div.code { - font-weight: bold; - margin-bottom: 1em; -} - -span.refkey { - font-weight: bold; - color: white; - background-color: black; -} - -tt.apl { - font-style: italic; -} - -div.qualifstart { - padding: 0.1em 0.5em 0.5em 0.5em; - border-top: solid; - border-left: solid; - border-right: solid; - border-width: thin; - font-weight: bold; - margin-top: 0.2em; - margin-bottom: 0.2em; - text-align: center; -} - -div.qualifend { - padding: 0.5em 0.5em 0.1em 0.5em; - border-bottom: solid; - border-left: solid; - border-right: solid; - border-width: thin; - font-weight: bold; - margin-bottom: 0.2em; - text-align: center; -} - -.noshade { - background-color: transparent; -} - -.xlight { - background-color: #DADADA; -} - -.light { - background-color: #B0B0B0; -} - -.medium { - background-color: #8C8C8C; -} - -.dark { - background-color: #6E6E6E; -} - -.xdark { - background-color: #585858; -} - -.light-yellow { - background-color: #FFFFCC; -} - -.khaki { - background-color: #CCCC99; -} - -.medium-blue { - background-color: #6699CC; -} - -.light-blue { - background-color: #CCCCFF; -} - -.mid-grey { - background-color: #CCCCCC; -} - -.light-grey { - background-color: #DADADA; -} - -.lightest-grey { - background-color: #E6E6E6; -} - -#changed { - position: absolute; - left: 0.2em; - color: #7B68EE; - background-color: #FFFFFF; - font-style: normal; - font-weight: bold; -} - -INPUT.buttons { - font-size: 0.75em; - border-top: 0.2em outset #B1B1B1; - border-right: 0.2em outset #000000; - border-bottom: 0.2em outset #000000; - border-left: 0.2em outset #B1B1B1; - background-color: #E2E2E2; - margin-bottom: 0.2em; -} - -.cgraphic { - font-size: 90%; - color: black; -} - -.aix,.hpux,.sun,.unix,.win2,.winnt,.win,.zos,.linux,.os390,.os400,.c,.cplusplus,.cobol,.fortran,.java,.macosx,.os2,.pl1,.rpg - { - background-repeat: no-repeat; - background-position: top left; - margin-top: 0.5em; - text-indent: 55px; -} - -.aix { - background-image: url(ngaix.gif); -} - -.hpux { - background-image: url(nghpux.gif); -} - -.sun { - background-image: url(ngsolaris.gif); -} - -.unix { - background-image: url(ngunix.gif); -} - -.win2 { - background-image: url(ng2000.gif); -} - -.winxp { - background-image: url(ngxp.gif); -} - -.winnt { - background-image: url(ngnt.gif); -} - -.win { - background-image: url(ngwin.gif); -} - -.zos { - background-image: url(ngzos.gif); -} - -.linux { - background-image: url(nglinux.gif); -} - -.os390 { - background-image: url(ng390.gif); -} - -.os400 { - background-image: url(ng400.gif); -} - -.c { - background-image: url(ngc.gif); -} - -.cplusplus { - background-image: url(ngcpp.gif); -} - -.cobol { - background-image: url(ngcobol.gif); -} - -.fortran { - background-image: url(ngfortran.gif); -} - -.java { - background-image: url(ngjava.gif); -} - -.macosx { - background-image: url(ngmacosx.gif); -} - -.os2 { - background-image: url(ngos2.gif); -} - -.pl1 { - background-image: url(ngpl1.gif); -} - -.rpg { - background-image: url(ngrpg.gif); -}
\ No newline at end of file diff --git a/docs/org.eclipse.wst.doc.user/commonltr.css b/docs/org.eclipse.wst.doc.user/commonltr.css deleted file mode 100644 index e6a81958c6..0000000000 --- a/docs/org.eclipse.wst.doc.user/commonltr.css +++ /dev/null @@ -1,1306 +0,0 @@ -/* - | (c) Copyright IBM Corp. 2004, 2005 All Rights Reserved. - */ - -.unresolved { background-color: skyblue; } -.noTemplate { background-color: yellow; } - -.base { background-color: #ffffff; } - -/* Add space for top level topics */ -.nested0 { margin-top : 1em;} - -/* div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid */ -.p {margin-top: 1em} - -/* Default of italics to set apart figure captions */ -.figcap { font-style: italic } -.figdesc { font-style: normal } - -/* Use @frame to create frames on figures */ -.figborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;} -.figsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;} -.figtop { border-top : 2px solid; margin-top: 1em; border-color : Silver;} -.figbottom { border-bottom : 2px solid; border-color : Silver;} -.figtopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;} - -/* Most link groups are created with <div>. Ensure they have space before and after. */ -.ullinks { list-style-type: none } -.ulchildlink { margin-top: 1em; margin-bottom: 1em } -.olchildlink { margin-top: 1em; margin-bottom: 1em } -.linklist { margin-bottom: 1em } -.linklistwithchild { margin-left: 1.5em; margin-bottom: 1em } -.sublinklist { margin-left: 1.5em; margin-bottom: 1em } -.relconcepts { margin-top: 1em; margin-bottom: 1em } -.reltasks { margin-top: 1em; margin-bottom: 1em } -.relref { margin-top: 1em; margin-bottom: 1em } -.relinfo { margin-top: 1em; margin-bottom: 1em } -.breadcrumb { font-size : smaller; margin-bottom: 1em } -.prereq { margin-left : 20px;} - -/* Set heading sizes, getting smaller for deeper nesting */ -.topictitle1 { margin-top: 0pc; margin-bottom: .1em; font-size: 1.34em; } -.topictitle2 { margin-top: 1pc; margin-bottom: .45em; font-size: 1.17em; } -.topictitle3 { margin-top: 1pc; margin-bottom: .17em; font-size: 1.17em; font-weight: bold; } -.topictitle4 { margin-top: .83em; font-size: 1.17em; font-weight: bold; } -.topictitle5 { font-size: 1.17em; font-weight: bold; } -.topictitle6 { font-size: 1.17em; font-style: italic; } -.sectiontitle { margin-top: 1em; margin-bottom: 0em; color: black; font-size: 1.17em; font-weight: bold;} -.section { margin-top: 1em; margin-bottom: 1em } -.example { margin-top: 1em; margin-bottom: 1em } - -/* All note formats have the same default presentation */ -.note { margin-top: 1em; margin-bottom : 1em;} -.notetitle { font-weight: bold } -.notelisttitle { font-weight: bold } -.tip { margin-top: 1em; margin-bottom : 1em;} -.tiptitle { font-weight: bold } -.fastpath { margin-top: 1em; margin-bottom : 1em;} -.fastpathtitle { font-weight: bold } -.important { margin-top: 1em; margin-bottom : 1em;} -.importanttitle { font-weight: bold } -.remember { margin-top: 1em; margin-bottom : 1em;} -.remembertitle { font-weight: bold } -.restriction { margin-top: 1em; margin-bottom : 1em;} -.restrictiontitle { font-weight: bold } -.attention { margin-top: 1em; margin-bottom : 1em;} -.attentiontitle { font-weight: bold } -.dangertitle { font-weight: bold } -.danger { margin-top: 1em; margin-bottom : 1em;} -.cautiontitle { font-weight: bold } -.caution { font-weight: bold; margin-bottom : 1em; } - -/* Simple lists do not get a bullet */ -ul.simple { list-style-type: none } - -/* Used on the first column of a table, when rowheader="firstcol" is used */ -.firstcol { font-weight : bold;} - -/* Various basic phrase styles */ -.bold { font-weight: bold; } -.boldItalic { font-weight: bold; font-style: italic; } -.italic { font-style: italic; } -.underlined { text-decoration: underline; } -.uicontrol { font-weight: bold; } -.parmname { font-weight: bold; } -.kwd { font-weight: bold; } -.defkwd { font-weight: bold; text-decoration: underline; } -.var { font-style : italic;} -.shortcut { text-decoration: underline; } - -/* Default of bold for definition list terms */ -.dlterm { font-weight: bold; } - -/* Use CSS to expand lists with @compact="no" */ -.dltermexpand { font-weight: bold; margin-top: 1em; } -*[compact="yes"]>li { margin-top: 0em;} -*[compact="no"]>li { margin-top: .53em;} -.liexpand { margin-top: 1em; margin-bottom: 1em } -.sliexpand { margin-top: 1em; margin-bottom: 1em } -.dlexpand { margin-top: 1em; margin-bottom: 1em } -.ddexpand { margin-top: 1em; margin-bottom: 1em } -.stepexpand { margin-top: 1em; margin-bottom: 1em } -.substepexpand { margin-top: 1em; margin-bottom: 1em } - -/* Align images based on @align on topic/image */ -div.imageleft { text-align: left } -div.imagecenter { text-align: center } -div.imageright { text-align: right } -div.imagejustify { text-align: justify } - -pre.screen { padding: 5px 5px 5px 5px; border: outset; background-color: #CCCCCC; margin-top: 2px; margin-bottom : 2px; white-space: pre} - -/* copied from common.css */ -body { - font-family: Arial, sans-serif; - font-size: 0.8em; - background-color: #ffffff; - color: Black; - margin-right: 5em; - margin-bottom: 1em; -} - -.ibmfilepath { - font-family: monospace; - font-size: 100%; -} - -.ibmcommand { - font-weight: bold; -} - -.ibmemphasis { - font-style: italic; -} - -.mv,.pk,.pkdef,.pv { - font-family: monospace; - font-size: 100%; - padding-top: 0em; - padding-right: .3em; - padding-bottom: 0em; - padding-left: .3em; -} - -tt,samp { - font-family: monospace; - font-size: 100%; -} - -BODY.nav { - background-color: #FFFFFF; - border-right: 0.2em ridge black; - font-size: 0.95em; -} - -.base { - font-weight: normal; - font-style: normal; - font-variant: normal; - text-decoration: none; - background-color: #ffffff; -} - -TABLE { - color: black; - width: 90%; - border-collapse: collapse; - border-color: Black; - background: white; - margin-top: 0.5em; - margin-bottom: 0.5em; - margin-left: 0em; - margin-right: 0em; -} - -.tbldesc { - font-style: italic; -} - -TH { - font-weight: bold; - font-size: 0.7em; - color: black; - background-color: #dadada; - padding-top: 0.1em; - padding-bottom: 0.3em; - padding-left: 1em; - padding-right: 1em; -} - -TH.base { - font-weight: bold; - color: black; - border: 1 solid #606060; - background-color: #dcdada; - padding-top: 0.65em; - padding-bottom: 0.65em; - padding-left: 1em; - padding-right: 1em; -} - -TD { - font-size: 0.7em; - color: black; - background-color: white; - padding-top: 0.1em; - padding-bottom: 0.3em; - padding-left: 1em; - padding-right: 1em; -} - -CITE { - font-style: italic; -} - -EM { - font-style: italic; -} - -STRONG { - font-weight: bold; -} - -caption { - text-align: left; - font-style: italic; -} - -DT { - margin-top: 0.5em; - margin-bottom: 0.5em; -} - -DD { - margin-left: 1.0em; -} - -PRE,pre.cgraphic { - font-family: monospace; - font-size: 12px; - background-color: #dadada; - padding: 5px; -} - -.italic { - font-style: italic; -} - -.bold { - font-weight: bold; -} - -.underlined { - text-decoration: underline; -} - -.bold-italic,.boldItalic { - font-weight: bold; - font-style: italic; -} - -.smallCaps,.smallcaps { - text-transform: uppercase; - font-size: smaller; - font-variant: small-caps; -} - -.italic-underlined { - font-style: italic; - text-decoration: underline; -} - -.bold-underlined { - font-weight: bold; - text-decoration: underline; -} - -.bold-italic-underlined { - font-weight: bold; - font-style: italic; - text-decoration: underline; -} - -.smallcaps-underlined { - font-variant: small-caps; - text-decoration: underline; -} - -.emphasis { - font-style: italic; -} - -.inlinedef { - font-style: italic; -} - -.sidebar { - background: #cccccc; -} - -A:link { - color: #006699; - text-decoration: underline; -} - -A:visited { - color: #996699; - text-decoration: underline; -} - -A:active { - color: #006699; - text-decoration: underline; -} - -A:hover { - color: #996699;; - text-decoration: underline; -} - -a.toclink:link { - text-decoration: none; -} - -a.toclink:active { - text-decoration: none; -} - -a.toclink:visited { - text-decoration: none; -} - -a.toclink:hover { - text-decoration: underline; -} - -a.ptoclink:link { - text-decoration: none; -} - -a.ptoclink:active { - text-decoration: none; -} - -a.ptoclink:visited { - text-decoration: none; -} - -a.ptoclink:hover { - text-decoration: underline; -} - -a.indexlink:link { - text-decoration: none; -} - -a.indexlink:active { - text-decoration: none; -} - -a.indexlink:visited { - text-decoration: none; -} - -a.indexlink:hover { - text-decoration: underline; -} - -a.figurelist:link { - text-decoration: none; -} - -a.figurelist:active { - text-decoration: none; -} - -a.figurelist:visited { - text-decoration: none; -} - -a.figurelist:hover { - text-decoration: underline; -} - -a.tablelist:link { - text-decoration: none; -} - -a.tablelist:active { - text-decoration: none; -} - -a.tablelist:visited { - text-decoration: none; -} - -a.tablelist:hover { - text-decoration: underline; -} - -a.boldgreylink:link { - text-decoration: none; - color: #333333; - font-family: Verdana, Arial, sans-serif; - font-weight: bold; - font-size: 0.9em; -} - -a.boldgreylink:visited { - text-decoration: none; - color: #333333; - font-family: Verdana, Arial, sans-serif; - font-weight: bold; - font-size: 0.9em; -} - -a.boldgreylink:hover { - text-decoration: underline; - color: #333333; - font-family: Verdana, Arial, sans-serif; - font-weight: bold; - font-size: 0.9em; -} - -.runningheader { - font-family: Verdana, Arial, sans-serif; - font-size: 0.7em; -} - -.runningfooter { - font-family: Verdana, Arial, sans-serif; - font-size: 0.7em; -} - -.runningfooter a:link { - font-weight: bold; - color: #000000; - text-decoration: none; -} - -.runningfooter a:active { - font-weight: bold; - color: #000000; - text-decoration: none; -} - -.runningfooter a:visited { - font-weight: bold; - color: #000000; - text-decoration: none; -} - -.runningfooter a:hover { - font-weight: bold; - color: #000000; - text-decoration: underline; -} - -#breadcrumb,.breadcrumb,span.breadcrumbs { - font-size: 0.75em; -} - -.fastpath { - margin-top: 1em; - margin-bottom: 1em; -} - -.fastpathtitle { - font-weight: bold; -} - -.toc { - font-size: small; -} - -.nested0 { - margin-top: 0em; -} - -.p { - margin-top: 1em; -} - -span.figcap { - font-style: italic; -} - -span.figdesc { - font-style: italic; -} - -div.figbox { - -} - -div.figrules { - -} - -div.fignone { - -} - -.fignone { - -} - -.figborder { - -} - -.figsides { - -} - -.figtop { - -} - -.figbottom { - -} - -.figtopbot { - -} - -.parentlink { - -} - -.prevlink { - -} - -.nextlink { - -} - -.relconceptshd { - -} - -.reltaskshd { - -} - -.relrefhd { - -} - -.synnone { - -} - -.synborder { - -} - -.synsides { - -} - -.syntop { - -} - -.synbottom { - -} - -.syntopbot { - -} - -.skip { - margin-top: 1em; -} - -.skipspace { - margin-top: 1em; - margin-bottom: 1em; -} - -.ulchildlink { - margin-top: 1em; - margin-bottom: 1em; -} - -.olchildlink { - margin-top: 1em; - margin-bottom: 1em; -} - -ul,ol { - margin-top: 0.1em; - padding-top: 0.1em; -} - -ul.simple { - list-style-type: none; -} - -ul.indexlist { - list-style-type: none; -} - -OL LI { - margin-top: 0.0em; - margin-bottom: 0.0em; - margin-left: 0.0em; -} - -UL LI { - margin-top: 0.0em; - margin-bottom: 0.0em; - margin-left: 0.0em; -} - -OL LI DIV P { - list-style-type: decimal; - margin-top: 0.2em; - margin-bottom: 0.2em; -} - -UL LI DIV P { - list-style-type: disc; - margin-top: 0.2em; - margin-bottom: 0.2em; -} - -* [compact="yes"]>li { - margin-top: 0 em; -} - -* [compact="no"]>li { - margin-top: 0.5em; -} - -hr { - margin-bottom: 0em; - margin-top: 0em; - padding-top: 0em; - padding-bottom: 0em; - width: 90%; - color: #cccccc; - text-align: center; -} - -H1,.title,.pagetitle,.topictitle1 { - font-size: 1.5em; - font-style: normal; - font-weight: bold; - margin-bottom: 0.5em; - word-spacing: 0.1em; -} - -H2,.subtitle,.pagesubtitle,.topictitle2 { - font-size: 1.25em; - font-style: normal; - font-weight: bold; - margin-bottom: 0.0em; - padding-bottom: 0.0em; -} - -H3,.boldtitle,.topictitle3 { - font-size: 1.0em; - font-style: normal; - font-weight: bold; - margin-bottom: 0.2em; - padding-bottom: 0.1em; -} - -H4,.topictitle4 { - font-size: 0.9em; - font-style: normal; - font-weight: bold; - margin-bottom: 0.1em; - padding-bottom: 0.1em; -} - -h5,.topictitle5 { - font-size: 0.8em; - font-style: normal; - font-weight: bold; - margin-bottom: 0em; - padding-bottom: 0em; -} - -h6,.topictitle6 { - font-size: 0.7em; - font-style: normal; - font-weight: bold; - margin-bottom: 0em; - padding-bottom: 0em; -} - -div.headtitle { - font-size: 1em; - font-weight: bold; - margin-left: 0em; -} - -div.head0 { - font-size: 0.9em; - font-weight: bold; - margin-left: 0em; - margin-top: 0.5em; -} - -div.head1 { - font-size: 0.8em; - font-weight: bold; - margin-left: 1em; - padding-top: 0.5em; -} - -div.head2 { - font-size: 0.7em; - font-weight: normal; - margin-left: 2em; -} - -div.head3 { - font-size: 0.7em; - font-weight: normal; - margin-left: 3em; -} - -div.head4 { - font-size: 0.7em; - font-weight: normal; - margin-left: 4em; -} - -div.head5 { - font-size: 0.7em; - font-weight: normal; - margin-left: 5em; -} - -div.head6 { - font-size: 0.7em; - font-weight: normal; - margin-left: 6em; -} - -div.head7 { - font-size: 0.7em; - font-weight: normal; - margin-left: 7em; -} - -div.head8 { - font-size: 0.7em; - font-weight: normal; - margin-left: 8em; -} - -div.head9 { - font-size: 0.7em; - font-weight: normal; - margin-left: 9em; -} - -.tip { - margin-top: 1em; - margin-bottom: 1em; -} - -.tiptitle { - font-weight: bold; -} - -.firstcol { - font-weight: bold; -} - -.ptocH1 { - font-size: x-small; -} - -.ptocH2 { - font-size: x-small; -} - -.stitle { - font-style: italic; - text-decoration: underline; -} - -.nte { - -} - -.xxlines { - white-space: pre; - font-size: 0.95em; -} - -.sectiontitle { - margin-top: 1em; - margin-bottom: 0em; - color: black; - font-size: 1.2em; - font-weight: bold; -} - -div.imageleft { - text-align: left; -} - -div.imagecenter { - text-align: center; -} - -div.imageright { - text-align: right; -} - -div.imagejustify { - text-align: justify; -} - -div.mmobj { - margin-top: 1em; - margin-bottom: 1em; - text-align: center; -} - -div.mmobjleft { - margin-top: 1em; - margin-bottom: 1em; - text-align: left; -} - -div.mmobjcenter { - margin-top: 1em; - margin-bottom: 1em; - text-align: center; -} - -div.mmobjright { - margin-top: 1em; - margin-bottom: 1em; - text-align: right; -} - -pre.screen { - padding: 1em 1em 1em 1em; - margin-top: 0.4em; - margin-bottom: 0.4em; - border: thin solid Black; - font-size: 100%; -} - -.prereq { - margin-left: 1.5em; -} - -.defListHead { - font-weight: bold; - text-decoration: underline; -} - -span.mv { - font-style: italic; -} - -span.md { - text-decoration: line-through; -} - -.pk,span.pk { - font-weight: bold; -} - -span.pkdef { - font-weight: bold; - text-decoration: underline; -} - -span.pv { - font-style: italic; -} - -span.pvdef { - font-style: italic; - text-decoration: underline; -} - -span.kwd { - font-weight: bold; -} - -span.kdwdef { - font-weight: bold; - text-decoration: underline; -} - -.parmListKwd { - font-weight: bold; -} - -.parmListVar { - font-style: italic; -} - -span.oper { - font-style: normal; -} - -span.operdef { - text-decoration: underline; -} - -VAR,span.var { - font-style: italic; -} - -span.vardef { - font-style: italic; - text-decoration: underline; -} - -div.msg { - padding: 0.2em 1em 1em 1em; - margin-top: 0.4em; - margin-bottom: 0.4em; -} - -div.msgnum { - float: left; - font-weight: bold; - margin-bottom: 1em; - margin-right: 1em; -} - -div.msgtext { - font-weight: bold; - margin-bottom: 1em; -} - -div.msgitemtitle { - font-weight: bold; -} - -p.msgitem { - margin-top: 0em; -} - -.attention,div.attention { - margin-top: 1em; - margin-bottom: 1em; -} - -.attentiontitle,span.attentiontitle { - font-weight: bold; -} - -.cautiontitle,div.cautiontitle { - margin-top: 1em; - font-weight: bold; -} - -.caution,div.caution { - margin-top: 1em; - margin-bottom: 1em; -} - -.danger,div.danger { - padding: 0.5em 0.5em 0.5em 0.5em; - border: solid; - border-width: thin; - font-weight: bold; - margin-top: 0.2em; - margin-bottom: 1em; -} - -.dangertitle,div.dangertitle { - margin-top: 1em; - font-weight: bold; -} - -.important { - margin-top: 1em; - margin-bottom: 1em; -} - -.importanttitle { - font-weight: bold; -} - -.remember { - margin-top: 1em; - margin-bottom: 1em; -} - -.remembertitle { - font-weight: bold; -} - -.restriction { - margin-top: 1em; - margin-bottom: 1em; -} - -.restrictiontitle { - font-weight: bold; -} - -div.warningtitle { - font-weight: bold; -} - -div.warningbody { - margin-left: 2em -} - -.note { - margin-top: 1em; - margin-bottom: 1em; -} - -.notetitle,div.notetitle { - font-weight: bold; -} - -div.notebody { - margin-left: 2em; -} - -div.notelisttitle { - font-weight: bold; -} - -div.fnnum { - float: left; -} - -div.fntext { - margin-left: 2em; -} - -div.stepl { - margin-left: 2em; -} - -div.steplnum { - font-weight: bold; - float: left; - margin-left: 0.5em; -} - -div.stepltext { - margin-left: 5em; -} - -div.steplnum { - font-style: italic; - font-weight: bold; - float: left; - margin-left: 0.5em; -} - -div.stepltext { - margin-bottom: 0.5em; - margin-left: 3em; -} - -div.ledi { - margin-left: 3em; -} - -div.ledesc { - margin-left: 3em; -} - -span.pblktitle { - font-weight: bold; -} - -div.pblklblbox { - padding: 0.5em 0.5em 0.5em 0.5em; - border: solid; - border-width: thin; - margin-top: 0.2em; -} - -span.ednoticestitle { - font-weight: bold; -} - -span.term { - font-weight: bold; -} - -span.idxshow { - color: green; -} - -div.code { - font-weight: bold; - margin-bottom: 1em; -} - -span.refkey { - font-weight: bold; - color: white; - background-color: black; -} - -tt.apl { - font-style: italic; -} - -div.qualifstart { - padding: 0.1em 0.5em 0.5em 0.5em; - border-top: solid; - border-left: solid; - border-right: solid; - border-width: thin; - font-weight: bold; - margin-top: 0.2em; - margin-bottom: 0.2em; - text-align: center; -} - -div.qualifend { - padding: 0.5em 0.5em 0.1em 0.5em; - border-bottom: solid; - border-left: solid; - border-right: solid; - border-width: thin; - font-weight: bold; - margin-bottom: 0.2em; - text-align: center; -} - -.noshade { - background-color: transparent; -} - -.xlight { - background-color: #DADADA; -} - -.light { - background-color: #B0B0B0; -} - -.medium { - background-color: #8C8C8C; -} - -.dark { - background-color: #6E6E6E; -} - -.xdark { - background-color: #585858; -} - -.light-yellow { - background-color: #FFFFCC; -} - -.khaki { - background-color: #CCCC99; -} - -.medium-blue { - background-color: #6699CC; -} - -.light-blue { - background-color: #CCCCFF; -} - -.mid-grey { - background-color: #CCCCCC; -} - -.light-grey { - background-color: #DADADA; -} - -.lightest-grey { - background-color: #E6E6E6; -} - -#changed { - position: absolute; - left: 0.2em; - color: #7B68EE; - background-color: #FFFFFF; - font-style: normal; - font-weight: bold; -} - -INPUT.buttons { - font-size: 0.75em; - border-top: 0.2em outset #B1B1B1; - border-right: 0.2em outset #000000; - border-bottom: 0.2em outset #000000; - border-left: 0.2em outset #B1B1B1; - background-color: #E2E2E2; - margin-bottom: 0.2em; -} - -.cgraphic { - font-size: 90%; - color: black; -} - -.aix,.hpux,.sun,.unix,.win2,.winnt,.win,.zos,.linux,.os390,.os400,.c,.cplusplus,.cobol,.fortran,.java,.macosx,.os2,.pl1,.rpg - { - background-repeat: no-repeat; - background-position: top left; - margin-top: 0.5em; - text-indent: 55px; -} - -.aix { - background-image: url(ngaix.gif); -} - -.hpux { - background-image: url(nghpux.gif); -} - -.sun { - background-image: url(ngsolaris.gif); -} - -.unix { - background-image: url(ngunix.gif); -} - -.win2 { - background-image: url(ng2000.gif); -} - -.winxp { - background-image: url(ngxp.gif); -} - -.winnt { - background-image: url(ngnt.gif); -} - -.win { - background-image: url(ngwin.gif); -} - -.zos { - background-image: url(ngzos.gif); -} - -.linux { - background-image: url(nglinux.gif); -} - -.os390 { - background-image: url(ng390.gif); -} - -.os400 { - background-image: url(ng400.gif); -} - -.c { - background-image: url(ngc.gif); -} - -.cplusplus { - background-image: url(ngcpp.gif); -} - -.cobol { - background-image: url(ngcobol.gif); -} - -.fortran { - background-image: url(ngfortran.gif); -} - -.java { - background-image: url(ngjava.gif); -} - -.macosx { - background-image: url(ngmacosx.gif); -} - -.os2 { - background-image: url(ngos2.gif); -} - -.pl1 { - background-image: url(ngpl1.gif); -} - -.rpg { - background-image: url(ngrpg.gif); -}
\ No newline at end of file diff --git a/docs/org.eclipse.wst.doc.user/commonrtl.css b/docs/org.eclipse.wst.doc.user/commonrtl.css deleted file mode 100644 index 2350b01fc2..0000000000 --- a/docs/org.eclipse.wst.doc.user/commonrtl.css +++ /dev/null @@ -1,113 +0,0 @@ -/* - | (c) Copyright IBM Corp. 2004, 2005 All Rights Reserved. - */ - -.unresolved { background-color: skyblue; } -.noTemplate { background-color: yellow; } - -.base { background-color: #ffffff; } - -/* Add space for top level topics */ -.nested0 { margin-top : 1em;} - -/* div with class=p is used for paragraphs that contain blocks, to keep the XHTML valid */ -.p {margin-top: 1em} - -/* Default of italics to set apart figure captions */ -.figcap { font-style: italic } -.figdesc { font-style: normal } - -/* Use @frame to create frames on figures */ -.figborder { border-style: solid; padding-left : 3px; border-width : 2px; padding-right : 3px; margin-top: 1em; border-color : Silver;} -.figsides { border-left : 2px solid; padding-left : 3px; border-right : 2px solid; padding-right : 3px; margin-top: 1em; border-color : Silver;} -.figtop { border-top : 2px solid; margin-top: 1em; border-color : Silver;} -.figbottom { border-bottom : 2px solid; border-color : Silver;} -.figtopbot { border-top : 2px solid; border-bottom : 2px solid; margin-top: 1em; border-color : Silver;} - -/* Most link groups are created with <div>. Ensure they have space before and after. */ -.ullinks { list-style-type: none } -.ulchildlink { margin-top: 1em; margin-bottom: 1em } -.olchildlink { margin-top: 1em; margin-bottom: 1em } -.linklist { margin-top: 1em; margin-bottom: 1em } -.linklistwithchild { margin-top: 1em; margin-right: 1.5em; margin-bottom: 1em } -.sublinklist { margin-top: 1em; margin-right: 1.5em; margin-bottom: 1em } -.relconcepts { margin-top: 1em; margin-bottom: 1em } -.reltasks { margin-top: 1em; margin-bottom: 1em } -.relref { margin-top: 1em; margin-bottom: 1em } -.relinfo { margin-top: 1em; margin-bottom: 1em } -.breadcrumb { font-size : smaller; margin-bottom: 1em } -.prereq { margin-right : 20px;} - -/* Set heading sizes, getting smaller for deeper nesting */ -.topictitle1 { margin-top: 0pc; margin-bottom: .1em; font-size: 1.34em; } -.topictitle2 { margin-top: 1pc; margin-bottom: .45em; font-size: 1.17em; } -.topictitle3 { margin-top: 1pc; margin-bottom: .17em; font-size: 1.17em; font-weight: bold; } -.topictitle4 { margin-top: .83em; font-size: 1.17em; font-weight: bold; } -.topictitle5 { font-size: 1.17em; font-weight: bold; } -.topictitle6 { font-size: 1.17em; font-style: italic; } -.sectiontitle { margin-top: 1em; margin-bottom: 0em; color: black; font-size: 1.17em; font-weight: bold;} -.section { margin-top: 1em; margin-bottom: 1em } -.example { margin-top: 1em; margin-bottom: 1em } - -/* All note formats have the same default presentation */ -.note { margin-top: 1em; margin-bottom : 1em;} -.notetitle { font-weight: bold } -.notelisttitle { font-weight: bold } -.tip { margin-top: 1em; margin-bottom : 1em;} -.tiptitle { font-weight: bold } -.fastpath { margin-top: 1em; margin-bottom : 1em;} -.fastpathtitle { font-weight: bold } -.important { margin-top: 1em; margin-bottom : 1em;} -.importanttitle { font-weight: bold } -.remember { margin-top: 1em; margin-bottom : 1em;} -.remembertitle { font-weight: bold } -.restriction { margin-top: 1em; margin-bottom : 1em;} -.restrictiontitle { font-weight: bold } -.attention { margin-top: 1em; margin-bottom : 1em;} -.attentiontitle { font-weight: bold } -.dangertitle { font-weight: bold } -.danger { margin-top: 1em; margin-bottom : 1em;} -.cautiontitle { font-weight: bold } -.caution { font-weight: bold; margin-bottom : 1em; } - -/* Simple lists do not get a bullet */ -ul.simple { list-style-type: none } - -/* Used on the first column of a table, when rowheader="firstcol" is used */ -.firstcol { font-weight : bold;} - -/* Various basic phrase styles */ -.bold { font-weight: bold; } -.boldItalic { font-weight: bold; font-style: italic; } -.italic { font-style: italic; } -.underlined { text-decoration: underline; } -.uicontrol { font-weight: bold; } -.parmname { font-weight: bold; } -.kwd { font-weight: bold; } -.defkwd { font-weight: bold; text-decoration: underline; } -.var { font-style : italic;} -.shortcut { text-decoration: underline; } - -/* Default of bold for definition list terms */ -.dlterm { font-weight: bold; } - -/* Use CSS to expand lists with @compact="no" */ -.dltermexpand { font-weight: bold; margin-top: 1em; } -*[compact="yes"]>li { margin-top: 0em;} -*[compact="no"]>li { margin-top: .53em;} -.liexpand { margin-top: 1em; margin-bottom: 1em } -.sliexpand { margin-top: 1em; margin-bottom: 1em } -.dlexpand { margin-top: 1em; margin-bottom: 1em } -.ddexpand { margin-top: 1em; margin-bottom: 1em } -.stepexpand { margin-top: 1em; margin-bottom: 1em } -.substepexpand { margin-top: 1em; margin-bottom: 1em } - -/* Align images based on @align on topic/image */ -div.imageleft { text-align: left } -div.imagecenter { text-align: center } -div.imageright { text-align: right } -div.imagejustify { text-align: justify } - -pre.screen { padding: 5px 5px 5px 5px; border: outset; background-color: #CCCCCC; margin-top: 2px; margin-bottom : 2px; white-space: pre} - - diff --git a/docs/org.eclipse.wst.doc.user/images/SelectExistingServer.jpg b/docs/org.eclipse.wst.doc.user/images/SelectExistingServer.jpg Binary files differdeleted file mode 100644 index 398dbe4b1b..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/SelectExistingServer.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/SelectNewServer.jpg b/docs/org.eclipse.wst.doc.user/images/SelectNewServer.jpg Binary files differdeleted file mode 100644 index 95f6b44a90..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/SelectNewServer.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure1.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure1.jpg Binary files differdeleted file mode 100644 index 9064bb8fa9..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure1.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure2.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure2.jpg Binary files differdeleted file mode 100644 index eca4347bbf..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure2.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure3.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure3.jpg Binary files differdeleted file mode 100644 index 5d87d0cc8f..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure3.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure4.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure4.jpg Binary files differdeleted file mode 100644 index c334bbfdde..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure4.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure5.jpg b/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure5.jpg Binary files differdeleted file mode 100644 index a94614ea39..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/XMLCatalog-Figure5.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/image99L.jpg b/docs/org.eclipse.wst.doc.user/images/image99L.jpg Binary files differdeleted file mode 100644 index 506abdb128..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/image99L.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/imageEJ9.jpg b/docs/org.eclipse.wst.doc.user/images/imageEJ9.jpg Binary files differdeleted file mode 100644 index be7350eb39..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/imageEJ9.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/imageIAI.jpg b/docs/org.eclipse.wst.doc.user/images/imageIAI.jpg Binary files differdeleted file mode 100644 index d2f625c121..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/imageIAI.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/imageLKF.jpg b/docs/org.eclipse.wst.doc.user/images/imageLKF.jpg Binary files differdeleted file mode 100644 index ff98f424ce..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/imageLKF.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/imageO78.jpg b/docs/org.eclipse.wst.doc.user/images/imageO78.jpg Binary files differdeleted file mode 100644 index 67077f8434..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/imageO78.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/imageU71.jpg b/docs/org.eclipse.wst.doc.user/images/imageU71.jpg Binary files differdeleted file mode 100644 index 9ee0430709..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/imageU71.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/note.gif b/docs/org.eclipse.wst.doc.user/images/note.gif Binary files differdeleted file mode 100644 index f6260dbc72..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/note.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/selectRootElementDTD.png b/docs/org.eclipse.wst.doc.user/images/selectRootElementDTD.png Binary files differdeleted file mode 100644 index 25f260f36a..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/selectRootElementDTD.png +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/selectRootElementXSD.png b/docs/org.eclipse.wst.doc.user/images/selectRootElementXSD.png Binary files differdeleted file mode 100644 index 9955ed3050..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/selectRootElementXSD.png +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdl.gif b/docs/org.eclipse.wst.doc.user/images/wsdl.gif Binary files differdeleted file mode 100644 index 8fb844f5b3..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdl.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdl_main.gif b/docs/org.eclipse.wst.doc.user/images/wsdl_main.gif Binary files differdeleted file mode 100644 index 9f074e8a10..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdl_main.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-backbutton.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-backbutton.jpg Binary files differdeleted file mode 100644 index ebcd1c7629..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-backbutton.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-binding.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-binding.jpg Binary files differdeleted file mode 100644 index be74d5702a..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-binding.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-complex-type.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-complex-type.jpg Binary files differdeleted file mode 100644 index 15d6071292..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-complex-type.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-finished-wsdl.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-finished-wsdl.jpg Binary files differdeleted file mode 100644 index 9c56342415..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-finished-wsdl.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-operation.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-operation.jpg Binary files differdeleted file mode 100644 index 8dc34a301d..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-operation.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-skeleton.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-skeleton.jpg Binary files differdeleted file mode 100644 index 57ddb29309..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-skeleton.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-wizard.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-wizard.jpg Binary files differdeleted file mode 100644 index 50553f6408..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-new-wizard.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-setelement-dialog.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-setelement-dialog.jpg Binary files differdeleted file mode 100644 index f48165e9f6..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-setelement-dialog.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-settype-dialog.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-settype-dialog.jpg Binary files differdeleted file mode 100644 index 8a36a66b40..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-settype-dialog.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/wsdleditor-smart-rename1.jpg b/docs/org.eclipse.wst.doc.user/images/wsdleditor-smart-rename1.jpg Binary files differdeleted file mode 100644 index cc68a44456..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/wsdleditor-smart-rename1.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-backbutton.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-backbutton.jpg Binary files differdeleted file mode 100644 index 20926057ff..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-backbutton.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure1.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure1.jpg Binary files differdeleted file mode 100644 index f3b4f6f28b..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure1.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure2.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure2.jpg Binary files differdeleted file mode 100644 index 518c6063aa..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure2.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure3.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure3.jpg Binary files differdeleted file mode 100644 index a66b6e794c..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure3.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure4.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure4.jpg Binary files differdeleted file mode 100644 index 2a187da984..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure4.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure5.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure5.jpg Binary files differdeleted file mode 100644 index b9622efc4a..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure5.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure6.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure6.jpg Binary files differdeleted file mode 100644 index 6e253b820c..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure6.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure7.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure7.jpg Binary files differdeleted file mode 100644 index dfb7523c7c..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure7.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure8.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure8.jpg Binary files differdeleted file mode 100644 index ef617721a8..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure8.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure9.jpg b/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure9.jpg Binary files differdeleted file mode 100644 index 664eeccffa..0000000000 --- a/docs/org.eclipse.wst.doc.user/images/xsdeditor-figure9.jpg +++ /dev/null diff --git a/docs/org.eclipse.wst.doc.user/notices.html b/docs/org.eclipse.wst.doc.user/notices.html deleted file mode 100644 index 58b60690af..0000000000 --- a/docs/org.eclipse.wst.doc.user/notices.html +++ /dev/null @@ -1,17 +0,0 @@ -<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> -<html> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> -<LINK REL="STYLESHEET" HREF="book.css" CHARSET="ISO-8859-1" - TYPE="text/css"> -<title>Legal Notices</title> -</head> -<body> - -<h3><a NAME="Notices"></a>Notices</h3> -<p>The material in this guide is Copyright (c) IBM Corporation and -others 2000, 2007.</p> -<p><a href="about.html">Terms and conditions regarding the use of this -guide.</a></p> -</body> -</html> diff --git a/docs/org.eclipse.wst.doc.user/plugin.properties b/docs/org.eclipse.wst.doc.user/plugin.properties deleted file mode 100644 index 6163b89f3b..0000000000 --- a/docs/org.eclipse.wst.doc.user/plugin.properties +++ /dev/null @@ -1,13 +0,0 @@ -############################################################################### -# Copyright (c) 2005 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### - -pluginName = Master User Doc TOC -providerName = Eclipse.org diff --git a/docs/org.eclipse.wst.doc.user/plugin.xml b/docs/org.eclipse.wst.doc.user/plugin.xml deleted file mode 100644 index 0aa617f840..0000000000 --- a/docs/org.eclipse.wst.doc.user/plugin.xml +++ /dev/null @@ -1,7 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<plugin> - <extension point="org.eclipse.help.toc"> - <toc file="toc.xml" primary="true" /> - </extension> -</plugin> diff --git a/docs/org.eclipse.wst.doc.user/toc.xml b/docs/org.eclipse.wst.doc.user/toc.xml deleted file mode 100644 index 5213a438eb..0000000000 --- a/docs/org.eclipse.wst.doc.user/toc.xml +++ /dev/null @@ -1,46 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<!-- ============================================================================= --> -<!-- Define the top level topics --> -<!-- ============================================================================= --> -<toc label="Web Application Development User Guide" - topic="topics/overview.html"> - - <topic label="Creating Web applications"> - <link - toc="../org.eclipse.wst.webtools.doc.user/webtools_toc.xml" /> - </topic> - <topic label="Creating J2EE and enterprise applications"> - <link toc="../org.eclipse.jst.j2ee.doc.user/jst_j2ee_toc.xml" /> - <link toc="../org.eclipse.jst.ejb.doc.user/ejb_toc.xml" /> - </topic> - <topic label="Editing markup language files" - href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"> - <link toc="../org.eclipse.wst.sse.doc.user/sse_toc.xml" /> - <link - toc="../org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.xml" /> - <link - toc="../org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml" /> - <link - toc="../org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml" /> - </topic> - <!-- <link toc="../org.eclipse.wst.xml.doc.user/xml_toc.xml"/>--> - <topic label="Developing Web service applications"> - <link toc="../org.eclipse.jst.ws.doc.user/webservice_toc.xml" /> - </topic> - <topic label="Using the server tools"> - <link toc="../org.eclipse.wst.server.ui.doc.user/wtp_main_toc.xml" /> - </topic> - <topic label="Limitations and Known Issues" href="topics/limitations.html" /> - <topic label="Legal" href="notices.html" /> -</toc>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.doc.user/topics/limitations.html b/docs/org.eclipse.wst.doc.user/topics/limitations.html deleted file mode 100644 index e3c110f207..0000000000 --- a/docs/org.eclipse.wst.doc.user/topics/limitations.html +++ /dev/null @@ -1,43 +0,0 @@ -<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> -<head> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2006 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" - href="../../org.eclipse.wst.doc.user/common.css" > -<title>Web Tools Project Limitations and Known Issues</title> -</head> -<body> -<h1>Web Tools Project Limitations and Known Issues</h1> -<p>The following are limitations and known issues:</p> -<dl> -<dt class="dlterm"><b>When using XDoclet the generation does not appear to run.</b></dt> -<dd><p>Cause: XDoclet has some limitations with long path names.</p> -<p>Solution: You should install Eclipse and the Web Tools Platform into a directory with a short -path.</p> -</dd> -<dt class="dlterm"><b>When creating a Web service you may see a message similar to the following one:</b></dt> -<dd><p><samp>org.apache.axis.utils.JavaUtils isAttachmentSupported -WARNING: Unable to find required classes (javax.activation.DataHandler and -javax.mail.internet.MimeMultipart). Attachment support is disabled. -</samp></p> -<p>Cause: Attachment support is disabled.</p> -<p>Solution: The Apache Axis tools should auto-detect the javax.activation classes provided you add -<samp>activation.jar</samp> to the build path of the project to which you are generating your Web service or client. -For services, you will also need to make sure <samp>activation.jar</samp> is available to the Tomcat JRE, either by -including it in the server's global classpath or by placing a copy of activation.jar into the target Web -project's <samp>lib/</samp> directory. -</p> -</dd> -</dl> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.doc.user/topics/overview.html b/docs/org.eclipse.wst.doc.user/topics/overview.html deleted file mode 100644 index eab51be9c5..0000000000 --- a/docs/org.eclipse.wst.doc.user/topics/overview.html +++ /dev/null @@ -1,25 +0,0 @@ -<!doctype HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<html> -<head> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" - href="../../org.eclipse.wst.doc.user/common.css" > -<title>Web Tools Project Overview</title> -</head> -<body> -<h1>Web Tools Project Overview</h1> -<p>The Web Tools Project aims to provide common infrastructure available -to any Eclipse-based development environment targeting Web-enabled -applications.</p> -</body> -</html> diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.cvsignore b/docs/org.eclipse.wst.dtd.ui.infopop/.cvsignore deleted file mode 100644 index c14487ceac..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -build.xml diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.project b/docs/org.eclipse.wst.dtd.ui.infopop/.project deleted file mode 100644 index df2f69dc2c..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.dtd.ui.infopop</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts.xml b/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts.xml deleted file mode 100644 index 0cf4da1919..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts.xml +++ /dev/null @@ -1,54 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> - -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<contexts> -<context id="csh_outer_container"> -<description/> -</context> -<context id="webx0020"> -<description>This page lets you specify the line delimiter and the text encoding that will be used when you create or save a document type definition (DTD) file. - -The line delimiters are Ctrl-J (UNIX), Ctrl-M (Mac), or Ctrl-M Ctrl-J (Windows).</description> -</context> -<context id="webx0021"> -<description>This page lets you customize the syntax highlighting that the document type definition (DTD) editor does when you are editing a file. - -The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting. - -The <b>Foreground</b> and <b>Background</b> push buttons open <b>Color</b> dialog boxes that allow you to specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold. - -Click the <b>Restore Default</b> push button to set the highlighting styles back to their default values.</description> -<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html" label="Setting source highlighting styles"/> -</context> -<context id="webx0022"> -<description>Templates are a chunk of predefined code that you can insert into a DTD file when it is created. - -Click <b>New</b> if you want to create a completely new template. - -Supply a new template <b>Name</b> and <b>Description</b>. The <b>Context</b> for the template is the context in which the template is available in the proposal list when content assist is requested. Specify the <b>Pattern</b> for your template using the appropriate tags, attributes, or attribute values to be inserted by content assist. - -If you want to insert a variable, click the <b>Insert Variable</b> button and select the variable to be inserted. For example, the <b>date</b> variable indicates the current date will be inserted. - -You can edit, remove, import, or export a template by using the same Preferences page. - -If you have a template that you do not want to remove but you no longer want it to appear in the content assist list, clear its check box in the <b>Templates</b> preferences page.</description> -<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html" label="Working with DTD templates"/> -<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html" label="Creating DTD files"/> -</context> -<context id="dtdw0010"> -<description>Click the <b>Use DTD Template</b> check box if you want to use a DTD template as the initial content in your new DTD page. A list of available DTD templates is listed - select the one you want to use. A preview of your DTD file is shown once you select a DTD template.</description> -<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html" label="Working with DTD templates"/> -<topic href="../org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html" label="Creating DTD files"/> -</context> -</contexts> diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts2.xml b/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts2.xml deleted file mode 100644 index 3a44d26b3e..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/EditorDtdContexts2.xml +++ /dev/null @@ -1,25 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> - -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<contexts> -<context id="csh_outer_container"> -<description/> -</context> -<context id="dtdsource_source_HelpId"> -<description>The DTD editor lets you edit a document type definition. - -The editor provides text editing features such as syntax highlighting and unlimited undo and redo. -</description> -</context> -</contexts> diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.dtd.ui.infopop/META-INF/MANIFEST.MF deleted file mode 100644 index c8829c74ba..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/META-INF/MANIFEST.MF +++ /dev/null @@ -1,7 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.wst.dtd.ui.infopop; singleton:=true -Bundle-Version: 1.0.2.qualifier -Bundle-Vendor: %pluginProvider -Bundle-Localization: plugin diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/about.html b/docs/org.eclipse.wst.dtd.ui.infopop/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/build.properties b/docs/org.eclipse.wst.dtd.ui.infopop/build.properties deleted file mode 100644 index 784ca85afa..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/build.properties +++ /dev/null @@ -1,7 +0,0 @@ -bin.includes = plugin.xml,\ - plugin.properties,\ - about.html,\ - EditorDtdContexts.xml,\ - META-INF/,\ - EditorDtdContexts2.xml -src.includes = build.properties diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties deleted file mode 100644 index 76c52ba755..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/plugin.properties +++ /dev/null @@ -1,13 +0,0 @@ -############################################################################### -# Copyright (c) 2001, 2004 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### - -pluginName = DTD Editor infopops -pluginProvider = Eclipse.org diff --git a/docs/org.eclipse.wst.dtd.ui.infopop/plugin.xml b/docs/org.eclipse.wst.dtd.ui.infopop/plugin.xml deleted file mode 100644 index aa57fbcde2..0000000000 --- a/docs/org.eclipse.wst.dtd.ui.infopop/plugin.xml +++ /dev/null @@ -1,25 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<!-- ================================================= --> -<!-- This is the plugin for declaring the help --> -<!-- contributions for using the tool. --> -<!-- ================================================= --> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - -<extension point="org.eclipse.help.contexts"> - <contexts file="EditorDtdContexts.xml" plugin ="org.eclipse.wst.dtd.ui"/> - <contexts file="EditorDtdContexts2.xml" plugin ="org.eclipse.wst.dtd.core"/> -</extension> - - -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.cvsignore b/docs/org.eclipse.wst.dtdeditor.doc.user/.cvsignore deleted file mode 100644 index 180fc9b54f..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/.cvsignore +++ /dev/null @@ -1,3 +0,0 @@ -build.xml -org.eclipse.wst.dtdeditor.doc.user_1.0.0.jar -temp
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.project b/docs/org.eclipse.wst.dtdeditor.doc.user/.project deleted file mode 100644 index 4486d7a271..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.dtdeditor.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.ditamap b/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.ditamap deleted file mode 100644 index b8a5163ecf..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.ditamap +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
-<map collection-type="sequence" title="DTD Editor">
-<topicref href="topics/cworkdtds.dita" navtitle="Working with DTDs" type="concept">
-<topicref href="topics/tcretdtd.dita" linking="normal" navtitle="Creating DTDs"
-type="task">
-<topicref href="topics/cdtdover.dita" linking="sourceonly" navtitle="Document type definition - Overview"
-type="concept"></topicref>
-<topicref href="topics/tedtsrcst.dita" linking="sourceonly" navtitle="Setting source highlighting styles"
-type="task"></topicref>
-<topicref href="topics/tdtemplt.dita" linking="sourceonly" navtitle="Working with DTD templates"
-type="task"></topicref>
-</topicref>
-<topicref href="topics/timptdtd.dita" navtitle="Importing DTDs" type="task">
-</topicref>
-<topicref href="topics/tvaldtd.dita" navtitle="Validating DTDs" type="task">
-</topicref>
-<topicref href="topics/rdtdicons.dita" navtitle="Icons used in the DTD editor"
-type="reference"></topicref>
-</topicref>
-</map>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.xml b/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.xml deleted file mode 100644 index e959eb81a7..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/DTDEditormap_toc.xml +++ /dev/null @@ -1,16 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<?NLS TYPE="org.eclipse.help.toc"?> - -<toc label="DTD Editor" topic="topics/cworkdtds.html"> -<topic label="Working with DTDs" href="topics/cworkdtds.html"> -<topic label="Creating DTDs" href="topics/tcretdtd.html"> -<topic label="Document type definitions (DTDs) - overview" href="topics/cdtdover.html"/> -<topic label="Setting source highlighting styles" href="topics/tedtsrcst.html"/> -<topic label="Working with DTD templates" href="topics/tdtemplt.html"/> -</topic> -<topic label="Importing DTDs" href="topics/timptdtd.html"/> -<topic label="Validating DTDs" href="topics/tvaldtd.html"/> -<topic label="Icons used in the DTD editor" href="topics/rdtdicons.html"/> -</topic> -</toc> diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/DTDreftable.ditamap b/docs/org.eclipse.wst.dtdeditor.doc.user/DTDreftable.ditamap deleted file mode 100644 index f05b032f4f..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/DTDreftable.ditamap +++ /dev/null @@ -1,23 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
-<map>
-<topicgroup collection-type="family">
-<topicref href="topics/tcretdtd.dita" linking="normal" navtitle="Creating a new DTD"
-type="task"></topicref>
-<topicref href="topics/cdtdover.dita" linking="targetonly" navtitle="Document type definition - Overview"
-type="concept"></topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/cdtdover.dita" navtitle="Document type definition - Overview"
-type="concept"></topicref>
-<topicref href="topics/tvaldtd.dita" linking="targetonly" navtitle="Validating DTDs"
-type="task"></topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/tcretdtd.dita" linking="normal" navtitle="Creating a new DTD"
-type="task"></topicref>
-<topicref href="topics/tdtemplt.dita" navtitle="Working with DTD templates"
-type="task"></topicref>
-</topicgroup>
-</map>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/DocBuild.xml b/docs/org.eclipse.wst.dtdeditor.doc.user/DocBuild.xml deleted file mode 100644 index dd9be9e1f4..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/DocBuild.xml +++ /dev/null @@ -1,59 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<!-- - - This script build the Help plug-in by transforming the DITA source files into HTML. - - To use this script, you must install DITA-OT on your machine in the directory - defined by the dita.ot.dir property. - - Run the default target after you edit the DITA source files to regenerate the HTML. - - To customize this script for other Help plug-ins, modify the value of the args.input property - to be the DITA map file for the plug-in. - - NOTE: This script assumes that links to sibling Help plug-ins have scope="peer", otherwise the - output directory structure will be shifted incorrectly. - - NOTE: This script assumes that you hand code your plugin.xml file in myplugin.xml. This file - will be copied over the generated plugin.xml which is currently not being generated correctly - by DITA-OT. - - ChangeLog: - 2006-04-05 Arthur Ryman <ryman@ca.ibm.com> - - Created. - ---> -<project name="eclipsehelp" default="all"> - - <property name="dita.ot.dir" location="C:/DITA-OT1.2.2" /> - - <path id="dost.class.path"> - <pathelement location="${dita.ot.dir}${file.separator}lib${file.separator}dost.jar" /> - </path> - - <taskdef name="integrate" classname="org.dita.dost.platform.IntegratorTask"> - <classpath refid="dost.class.path" /> - </taskdef> - <target name="all" depends="integrate, eclipsehelp"> - </target> - <target name="integrate"> - <integrate ditadir="${dita.ot.dir}" /> - </target> - - <!-- revise below here --> - <target name="eclipsehelp"> - <ant antfile="${dita.ot.dir}${file.separator}conductor.xml" target="init" dir="${dita.ot.dir}"> - <property name="args.copycss" value="no" /> - <property name="args.csspath" value="org.eclipse.wst.doc.user" /> - <property name="args.eclipse.provider" value="Eclipse.org" /> - <property name="args.eclipse.version" value="1.5.0" /> - <property name="args.input" location="DTDEditormap_toc.ditamap" /> - <property name="clean.temp" value="true" /> - <property name="dita.extname" value=".dita" /> - <property name="dita.temp.dir" location="temp" /> - <property name="output.dir" location=".." /> - <property name="transtype" value="eclipsehelp" /> - </ant> - <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" /> - </target> -</project> diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.dtdeditor.doc.user/META-INF/MANIFEST.MF deleted file mode 100644 index 5496ab43e0..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.wst.dtdeditor.doc.user; singleton:=true -Bundle-Version: 1.0.300.qualifier -Bundle-Vendor: %pluginProvider -Bundle-Localization: plugin -Bundle-RequiredExecutionEnvironment: J2SE-1.4 diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/about.html b/docs/org.eclipse.wst.dtdeditor.doc.user/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties b/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties deleted file mode 100644 index 92aaedd1a0..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/build.properties +++ /dev/null @@ -1,15 +0,0 @@ -bin.includes = DTDEditormap_toc.xml,\ - about.html,\ - org.eclipse.wst.dtdeditor.doc.userindex.xml,\ - images/,\ - plugin.properties,\ - plugin.xml,\ - topics/*.htm*,\ - index/,\ - META-INF/ -src.includes = build.properties,\ - *.maplist,\ - *.ditamap,\ - topics/*.dita -bin.excludes = DocBuild.xml,\ - myPlugin*.xml
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Comment.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Comment.gif Binary files differdeleted file mode 100644 index 39611d6c63..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Comment.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Element.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Element.gif Binary files differdeleted file mode 100644 index 01f4889869..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Element.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity.gif Binary files differdeleted file mode 100644 index cb415064e0..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity_Reference.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity_Reference.gif Binary files differdeleted file mode 100644 index 5efa9b905e..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Entity_Reference.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Notation.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Notation.gif Binary files differdeleted file mode 100644 index 57ad089a69..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/ADD_Notation.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDChoice.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDChoice.gif Binary files differdeleted file mode 100644 index 89ba825253..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDChoice.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDSequence.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDSequence.gif Binary files differdeleted file mode 100644 index 8bf3f972d2..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/XSDSequence.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute.gif Binary files differdeleted file mode 100644 index c6cde94672..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute_list.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute_list.gif Binary files differdeleted file mode 100644 index 6df029174d..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/attribute_list.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nDTDFile.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nDTDFile.gif Binary files differdeleted file mode 100644 index e79914369a..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nDTDFile.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nany.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nany.gif Binary files differdeleted file mode 100644 index 7017d91b91..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nany.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nempty.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/nempty.gif Binary files differdeleted file mode 100644 index 119e3d4523..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/nempty.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/organize_dtd_logically.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/organize_dtd_logically.gif Binary files differdeleted file mode 100644 index 093c6bad04..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/organize_dtd_logically.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/images/sort.gif b/docs/org.eclipse.wst.dtdeditor.doc.user/images/sort.gif Binary files differdeleted file mode 100644 index 23c5d0b11c..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/images/sort.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/index/_8.cfs b/docs/org.eclipse.wst.dtdeditor.doc.user/index/_8.cfs Binary files differdeleted file mode 100644 index 0f963abb9a..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/index/_8.cfs +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/index/deletable b/docs/org.eclipse.wst.dtdeditor.doc.user/index/deletable Binary files differdeleted file mode 100644 index e423242b3e..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/index/deletable +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_contributions b/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_contributions deleted file mode 100644 index 92fe3c5f8c..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_contributions +++ /dev/null @@ -1,3 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:14:27 EDT 2007
-org.eclipse.wst.dtdeditor.doc.user=org.eclipse.wst.dtdeditor.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_dependencies b/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_dependencies deleted file mode 100644 index 771ea1ccbc..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_dependencies +++ /dev/null @@ -1,4 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:14:27 EDT 2007
-lucene=1.4.103.v20060601
-analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_docs b/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_docs deleted file mode 100644 index af1ba6ab41..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/index/indexed_docs +++ /dev/null @@ -1,10 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:14:27 EDT 2007
-/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html=0
-/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html=0
-/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html=0
-/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.html=0
-/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html=0
-/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html=0
-/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html=0
-/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html=0
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/index/segments b/docs/org.eclipse.wst.dtdeditor.doc.user/index/segments Binary files differdeleted file mode 100644 index 19b5d0c420..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/index/segments +++ /dev/null diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/myplugin.xml b/docs/org.eclipse.wst.dtdeditor.doc.user/myplugin.xml deleted file mode 100644 index 8c806834a1..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/myplugin.xml +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.1"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="DTDEditormap_toc.xml"/> - <index path="index/"/> - </extension> - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.wst.dtdeditor.doc.userindex.xml"/> - </extension> -</plugin> diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.user.maplist b/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.user.maplist deleted file mode 100644 index 13cbd726bb..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.user.maplist +++ /dev/null @@ -1,9 +0,0 @@ -<maplist version="3.6.2">
- <nav>
- <map file="DTDEditormap_toc.ditamap"/>
- </nav>
- <link>
- <map file="DTDEditormap_toc.ditamap"/>
- <map file="DTDreftable.ditamap"/>
- </link>
-</maplist>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.userindex.html b/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.userindex.html deleted file mode 100644 index 993d81a1d4..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.userindex.html +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<meta name="copyright" content="(C) Copyright IBM Corporation 2007" /> -<meta name="security" content="public" /> -<meta name="Robots" content="index,follow" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta name="DC.Format" content="XHTML" /> -<!-- All rights reserved. Licensed Materials Property of IBM --> -<!-- US Government Users Restricted Rights --> -<!-- Use, duplication or disclosure restricted by --> -<!-- GSA ADP Schedule Contract with IBM Corp. --> -<link rel="stylesheet" type="text/css" href="ibmdita.css" /> -<title>Index</title> -</head> -<body> -<h1>Index</h1> -<strong>D</strong> -<ul class="indexlist"> -<li>DTD -<ul class="indexlist"> -<li><a href="topics/tcretdtd.html#tcretdtd">creating</a> -</li> -<li><a href="topics/tdtemplt.html#twmacro">creating templates</a> -</li> -<li><a href="topics/rdtdicons.html#ricons">editor icons</a> -</li> -<li><a href="topics/tedtsrcst.html#ttaghilt">highlighting styles</a> -</li> -<li><a href="topics/timptdtd.html#timptdtd">importing</a> -</li> -<li><a href="topics/cdtdover.html#cdtdover">overview</a> -</li> -<li><a href="topics/tvaldtd.html#tvaldtd">validating</a> -</li> -</ul> -</li> -</ul> -<strong>T</strong> -<ul class="indexlist"> -<li>templates -<ul class="indexlist"> -<li><a href="topics/tdtemplt.html#twmacro">DTD</a> -</li> -</ul> -</li> -</ul> -<strong>X</strong> -<ul class="indexlist"> -<li>XML editor -<ul class="indexlist"> -<li><a href="topics/tedtsrcst.html#ttaghilt">DTD highlighting styles</a> -</li> -</ul> -</li> -</ul> -</body></html> diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.userindex.xml b/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.userindex.xml deleted file mode 100644 index ce9760daaf..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/org.eclipse.wst.dtdeditor.doc.userindex.xml +++ /dev/null @@ -1,36 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<index> - <entry keyword="DTD"> - <entry keyword="creating"> - <topic href="topics/tcretdtd.html#tcretdtd" title="Creating DTDs"/> - </entry> - <entry keyword="overview"> - <topic href="topics/cdtdover.html#cdtdover" title="Document type definitions (DTDs) - overview"/> - </entry> - <entry keyword="highlighting styles"> - <topic href="topics/tedtsrcst.html#ttaghilt" title="Setting source highlighting styles"/> - </entry> - <entry keyword="creating templates"> - <topic href="topics/tdtemplt.html#twmacro" title="Working with DTD templates"/> - </entry> - <entry keyword="importing"> - <topic href="topics/timptdtd.html#timptdtd" title="Importing DTDs"/> - </entry> - <entry keyword="validating"> - <topic href="topics/tvaldtd.html#tvaldtd" title="Validating DTDs"/> - </entry> - <entry keyword="editor icons"> - <topic href="topics/rdtdicons.html#ricons" title="Icons used in the DTD editor"/> - </entry> - </entry> - <entry keyword="XML editor"> - <entry keyword="DTD highlighting styles"> - <topic href="topics/tedtsrcst.html#ttaghilt" title="Setting source highlighting styles"/> - </entry> - </entry> - <entry keyword="templates"> - <entry keyword="DTD"> - <topic href="topics/tdtemplt.html#twmacro" title="Working with DTD templates"/> - </entry> - </entry> -</index>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.properties b/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.properties deleted file mode 100644 index d10ce86a89..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.properties +++ /dev/null @@ -1,4 +0,0 @@ -# NLS_MESSAGEFORMAT_VAR - -pluginName = DTD Editor documentation -pluginProvider = Eclipse.org diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.xml b/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.xml deleted file mode 100644 index 8c806834a1..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/plugin.xml +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.1"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="DTDEditormap_toc.xml"/> - <index path="index/"/> - </extension> - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.wst.dtdeditor.doc.userindex.xml"/> - </extension> -</plugin> diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.dita b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.dita deleted file mode 100644 index f947171424..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.dita +++ /dev/null @@ -1,33 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="cdtdover" xml:lang="en-us">
-<title>Document type definitions (DTDs) - overview</title>
-<titlealts>
-<searchtitle>Document type definition (DTD) - overview</searchtitle>
-</titlealts>
-<shortdesc>A document type definition (DTD) provides you with the means to
-validate XML files against a set of rules. When you create a DTD file, you
-can specify rules that control the structure of any XML files that reference
-the DTD file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DTD<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>A DTD can contain declarations that define elements, attributes, notations,
-and entities for any XML files that reference the DTD file. It also establishes
-constraints for how each element, attribute, notation, and entity can be used
-within any of the XML files that reference the DTD file.</p>
-<p>To be considered a valid XML file, the document must be accompanied by
-a DTD (or an XML schema), and conform to all of the declarations in the DTD
-(or XML schema).</p>
-<p>Certain XML parsers have the ability to read DTDs and check to see if the
-XML file it is reading follows all of those rules. While the parser is reading
-the XML file, it will check each line to be sure that it conforms to the rules
-that are laid out in the DTD file. If there is a problem, the parser generates
-an error and points to where the error occurs in the XML file. This kind of
-parser is called a validating parser because it validates the content of the
-XML file against the DTD.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html deleted file mode 100644 index efe3ea403f..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cdtdover.html +++ /dev/null @@ -1,62 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Document type definitions (DTDs) - overview" /> -<meta name="abstract" content="A document type definition (DTD) provides you with the means to validate XML files against a set of rules. When you create a DTD file, you can specify rules that control the structure of any XML files that reference the DTD file." /> -<meta name="description" content="A document type definition (DTD) provides you with the means to validate XML files against a set of rules. When you create a DTD file, you can specify rules that control the structure of any XML files that reference the DTD file." /> -<meta content="DTDs (document type definitions), overview" name="DC.subject" /> -<meta content="DTDs (document type definitions), overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretdtd.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cdtdover" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Document type definition (DTD) - overview</title> -</head> -<body id="cdtdover"><a name="cdtdover"><!-- --></a> - - -<h1 class="topictitle1">Document type definitions (DTDs) - overview</h1> - - - - -<div><p>A document type definition (DTD) provides you with the means to -validate XML files against a set of rules. When you create a DTD file, you -can specify rules that control the structure of any XML files that reference -the DTD file.</p> - -<p>A DTD can contain declarations that define elements, attributes, notations, -and entities for any XML files that reference the DTD file. It also establishes -constraints for how each element, attribute, notation, and entity can be used -within any of the XML files that reference the DTD file.</p> - -<p>To be considered a valid XML file, the document must be accompanied by -a DTD (or an XML schema), and conform to all of the declarations in the DTD -(or XML schema).</p> - -<p>Certain XML parsers have the ability to read DTDs and check to see if the -XML file it is reading follows all of those rules. While the parser is reading -the XML file, it will check each line to be sure that it conforms to the rules -that are laid out in the DTD file. If there is a problem, the parser generates -an error and points to where the error occurs in the XML file. This kind of -parser is called a validating parser because it validates the content of the -XML file against the DTD.</p> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/tcretdtd.html" title="A document type definition (DTD) contains a set of rules that can be used to validate an XML file. After you have created a DTD, you can edit it manually, adding declarations that define elements, attributes, entities, and notations, and how they can be used for any XML files that reference the DTD file.">Creating DTDs</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.dita b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.dita deleted file mode 100644 index 72850d4eeb..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.dita +++ /dev/null @@ -1,10 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<?Pub Inc?>
-<concept id="workingwithdtds" xml:lang="en-us">
-<title>Working with DTDs</title>
-<shortdesc>This sections contains information on the following:</shortdesc>
-<conbody></conbody>
-</concept>
-<?Pub *0000000395?>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.html deleted file mode 100644 index f43a5812dd..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/cworkdtds.html +++ /dev/null @@ -1,47 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Working with DTDs" /> -<meta name="abstract" content="This sections contains information on the following:" /> -<meta name="description" content="This sections contains information on the following:" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/timptdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tvaldtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rdtdicons.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="workingwithdtds" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Working with DTDs</title> -</head> -<body id="workingwithdtds"><a name="workingwithdtds"><!-- --></a> - - -<h1 class="topictitle1">Working with DTDs</h1> - - -<div><p>This sections contains information on the following:</p> -</div> - -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../topics/tcretdtd.html">Creating DTDs</a></strong><br /> -A document type definition (DTD) contains a set of rules that can be used to validate an XML file. After you have created a DTD, you can edit it manually, adding declarations that define elements, attributes, entities, and notations, and how they can be used for any XML files that reference the DTD file.</li> -<li class="ulchildlink"><strong><a href="../topics/timptdtd.html">Importing DTDs</a></strong><br /> -If you want to work with DTD files that you created outside of the product, you can import them into the workbench and open them in the DTD editor.</li> -<li class="ulchildlink"><strong><a href="../topics/tvaldtd.html">Validating DTDs</a></strong><br /> -Validating a DTD file lets you verify that it is well formed and does not contain any errors.</li> -<li class="ulchildlink"><strong><a href="../topics/rdtdicons.html">Icons used in the DTD editor</a></strong><br /> -These DTD editor icons appear in the Outline view.</li> -</ul> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.dita b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.dita deleted file mode 100644 index 003c581cc6..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.dita +++ /dev/null @@ -1,88 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="ricons" xml:lang="en-us">
-<title>Icons used in the DTD editor</title>
-<titlealts>
-<searchtitle>Icons used in the DTD editor</searchtitle>
-</titlealts>
-<shortdesc>These DTD editor icons appear in the Outline view.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DTD<indexterm>editor icons</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<refbody>
-<table>
-<tgroup cols="2"><colspec colname="COLSPEC0"/><colspec colname="COLSPEC1"/>
-<thead>
-<row>
-<entry>Icon </entry>
-<entry>Description</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry colname="COLSPEC0"></entry>
-<entry colname="COLSPEC1"></entry>
-</row>
-<row>
-<entry> <image href="../images/nany.gif"><alt>This graphic is the ANY content
-icon</alt></image> </entry>
-<entry>ANY content (content model)</entry>
-</row>
-<row>
-<entry><image href="../images/attribute.gif"><alt>This graphic is the attribute
-icon</alt></image> </entry>
-<entry>attribute</entry>
-</row>
-<row>
-<entry><image href="../images/attribute_list.gif"><alt>This graphic is the
-attribute list icon</alt></image> </entry>
-<entry>attribute list</entry>
-</row>
-<row>
-<entry colname="COLSPEC0"><image href="../images/ADD_Comment.gif"><alt>This
-graphic is the comment icon</alt></image></entry>
-<entry colname="COLSPEC1">comment</entry>
-</row>
-<row>
-<entry> <image href="../images/XSDChoice.gif"><alt>This graphic is the content
-model - choice icon</alt></image></entry>
-<entry>content model - choice</entry>
-</row>
-<row>
-<entry> <image href="../images/XSDSequence.gif"><alt>This graphic is the content
-model - sequence icon</alt></image></entry>
-<entry>content model - sequence</entry>
-</row>
-<row>
-<entry><image href="../images/ADD_Element.gif"><alt>This graphic is the element
-icon</alt></image> </entry>
-<entry>element</entry>
-</row>
-<row>
-<entry> <image href="../images/nempty.gif"><alt>This graphic is the EMPTY
-content (content model) icon</alt></image> </entry>
-<entry>EMPTY content (content model)</entry>
-</row>
-<row>
-<entry><image href="../images/ADD_Entity.gif"><alt>This graphic is the entity
-icon</alt></image> </entry>
-<entry>entity</entry>
-</row>
-<row>
-<entry><image href="../images/ADD_Notation.gif"><alt>This graphic is the notation
-icon</alt></image> </entry>
-<entry>notation</entry>
-</row>
-<row>
-<entry> <image href="../images/ADD_Entity_Reference.gif"><alt>This graphic
-is the parameter entity reference icon</alt></image></entry>
-<entry>parameter entity reference</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-<section></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html deleted file mode 100644 index 9b01e7dc26..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/rdtdicons.html +++ /dev/null @@ -1,146 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Icons used in the DTD editor" /> -<meta name="abstract" content="These DTD editor icons appear in the Outline view." /> -<meta name="description" content="These DTD editor icons appear in the Outline view." /> -<meta content="DTD editor, icons" name="DC.subject" /> -<meta content="DTD editor, icons" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cworkdtds.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ricons" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Icons used in the DTD editor</title> -</head> -<body id="ricons"><a name="ricons"><!-- --></a> - - -<h1 class="topictitle1">Icons used in the DTD editor</h1> - - - - -<div><p>These DTD editor icons appear in the Outline view.</p> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<thead align="left"> -<tr> -<th valign="top" id="N10063">Icon </th> - -<th valign="top" id="N1006A">Description</th> - -</tr> - -</thead> - -<tbody> -<tr> -<td valign="top" headers="N10063 "> </td> - -<td valign="top" headers="N1006A "> </td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "> <img src="../images/nany.gif" alt="This graphic is the ANY content icon" /> </td> - -<td valign="top" headers="N1006A ">ANY content (content model)</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "><img src="../images/attribute.gif" alt="This graphic is the attribute icon" /> </td> - -<td valign="top" headers="N1006A ">attribute</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "><img src="../images/attribute_list.gif" alt="This graphic is the attribute list icon" /> </td> - -<td valign="top" headers="N1006A ">attribute list</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "><img src="../images/ADD_Comment.gif" alt="This graphic is the comment icon" /></td> - -<td valign="top" headers="N1006A ">comment</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "> <img src="../images/XSDChoice.gif" alt="This graphic is the content model - choice icon" /></td> - -<td valign="top" headers="N1006A ">content model - choice</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "> <img src="../images/XSDSequence.gif" alt="This graphic is the content model - sequence icon" /></td> - -<td valign="top" headers="N1006A ">content model - sequence</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "><img src="../images/ADD_Element.gif" alt="This graphic is the element icon" /> </td> - -<td valign="top" headers="N1006A ">element</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "> <img src="../images/nempty.gif" alt="This graphic is the EMPTY content (content model) icon" /> </td> - -<td valign="top" headers="N1006A ">EMPTY content (content model)</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "><img src="../images/ADD_Entity.gif" alt="This graphic is the entity icon" /> </td> - -<td valign="top" headers="N1006A ">entity</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "><img src="../images/ADD_Notation.gif" alt="This graphic is the notation icon" /> </td> - -<td valign="top" headers="N1006A ">notation</td> - -</tr> - -<tr> -<td valign="top" headers="N10063 "> <img src="../images/ADD_Entity_Reference.gif" alt="This graphic is the parameter entity reference icon" /></td> - -<td valign="top" headers="N1006A ">parameter entity reference</td> - -</tr> - -</tbody> - -</table> -</div> - -<div class="section" /> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cworkdtds.html" title="This sections contains information on the following:">Working with DTDs</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.dita b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.dita deleted file mode 100644 index 8aaa14c0a3..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.dita +++ /dev/null @@ -1,45 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tcretdtd" xml:lang="en-us">
-<title>Creating DTDs</title>
-<titlealts>
-<searchtitle>Creating a new document type definition (DTD)</searchtitle>
-</titlealts>
-<shortdesc>A document type definition (DTD) contains a set of rules that can
-be used to validate an XML file. After you have created a DTD, you can edit
-it manually, adding declarations that define elements, attributes, entities,
-and notations, and how they can be used for any XML files that reference the
-DTD file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DTD<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p></p><p>The following instructions were written for the Resource
-perspective, but they will also work in many other perspectives.</p><p>Follow
-these steps to create a new DTD:</p></context>
-<steps>
-<step><cmd>If necessary, create a project to contain the DTD.</cmd></step>
-<step><cmd>In the workbench, select <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Other</uicontrol><uicontrol>XML</uicontrol>
-<uicontrol> DTD</uicontrol></menucascade> and click <uicontrol>Next</uicontrol>. </cmd>
-</step>
-<step><cmd>Select the project or folder that will contain the DTD.</cmd></step>
-<step><cmd>In the <uicontrol>File name</uicontrol> field, type the name of
-the DTD, for example <userinput>MyDTD.dtd</userinput>.</cmd><info>The name
-of your DTD file must end with the extension <userinput>.dtd</userinput></info>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>You can use a DTD template as the basis for your new DTD file.
-To do so, click the <uicontrol>Use DTD Template</uicontrol> check box, and
-select the template you want to use.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<result><p>The DTD appears in the Navigator view and automatically, by default,
-opens in the DTD editor. In the DTD editor, you can manually add elements,
-attributes, notations, entities, and comments to the DTD. If you close the
-file, and want to later re-open it in the DTD editor, double-click it in the
-Navigator view.</p></result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html deleted file mode 100644 index 712f40c478..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tcretdtd.html +++ /dev/null @@ -1,85 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating DTDs" /> -<meta name="abstract" content="A document type definition (DTD) contains a set of rules that can be used to validate an XML file. After you have created a DTD, you can edit it manually, adding declarations that define elements, attributes, entities, and notations, and how they can be used for any XML files that reference the DTD file." /> -<meta name="description" content="A document type definition (DTD) contains a set of rules that can be used to validate an XML file. After you have created a DTD, you can edit it manually, adding declarations that define elements, attributes, entities, and notations, and how they can be used for any XML files that reference the DTD file." /> -<meta content="DTDs (document type definitions), creating" name="DC.subject" /> -<meta content="DTDs (document type definitions), creating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cworkdtds.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcretdtd" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating a new document type definition (DTD)</title> -</head> -<body id="tcretdtd"><a name="tcretdtd"><!-- --></a> - - -<h1 class="topictitle1">Creating DTDs</h1> - - - - -<div><p>A document type definition (DTD) contains a set of rules that can -be used to validate an XML file. After you have created a DTD, you can edit -it manually, adding declarations that define elements, attributes, entities, -and notations, and how they can be used for any XML files that reference the -DTD file.</p> - -<div class="section"><p /> -<p>The following instructions were written for the Resource -perspective, but they will also work in many other perspectives.</p> -<p>Follow -these steps to create a new DTD:</p> -</div> - -<ol> -<li class="stepexpand"><span>If necessary, create a project to contain the DTD.</span></li> - -<li class="stepexpand"><span>In the workbench, select <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span> > <span class="uicontrol">XML</span> - > <span class="uicontrol"> DTD</span></span> and click <span class="uicontrol">Next</span>. </span> -</li> - -<li class="stepexpand"><span>Select the project or folder that will contain the DTD.</span></li> - -<li class="stepexpand"><span>In the <span class="uicontrol">File name</span> field, type the name of -the DTD, for example <kbd class="userinput">MyDTD.dtd</kbd>.</span> The name -of your DTD file must end with the extension <kbd class="userinput">.dtd</kbd> -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>You can use a DTD template as the basis for your new DTD file. -To do so, click the <span class="uicontrol">Use DTD Template</span> check box, and -select the template you want to use.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> - -</ol> - -<div class="section"><p>The DTD appears in the Navigator view and automatically, by default, -opens in the DTD editor. In the DTD editor, you can manually add elements, -attributes, notations, entities, and comments to the DTD. If you close the -file, and want to later re-open it in the DTD editor, double-click it in the -Navigator view.</p> -</div> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cworkdtds.html" title="This sections contains information on the following:">Working with DTDs</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.dita b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.dita deleted file mode 100644 index a379bc521e..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.dita +++ /dev/null @@ -1,46 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="twmacro" xml:lang="en-us">
-<title>Working with DTD templates</title>
-<titlealts>
-<searchtitle>Working with DTD templates</searchtitle>
-</titlealts>
-<shortdesc>Templates are a chunk of predefined code that you can insert into
-a DTD file when it is created. You may find a template useful when you have
-a certain piece of code you want to reuse several times, and you do not want
-to write it out every time.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DTD<indexterm>creating templates</indexterm></indexterm>
-<indexterm>templates<indexterm>DTD</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To create a new DTD template follow these steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>DTD Files</uicontrol><uicontrol>DTD
-Templates</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Click <uicontrol>New</uicontrol> if you want to create a completely
-new template.</cmd></step>
-<step><cmd>Supply a new template <uicontrol>Name</uicontrol> and <uicontrol>Description</uicontrol>.</cmd>
-</step>
-<step><cmd>Specify the <uicontrol>Context</uicontrol> for the template.</cmd>
-<info>This is the context in which the template is available in the proposal
-list when content assist is requested. </info></step>
-<step><cmd>Specify the <uicontrol>Pattern</uicontrol> for your template using
-the appropriate tags, attributes, or attribute values to be inserted by content
-assist.</cmd></step>
-<step><cmd>If you want to insert a variable, click the <uicontrol>Insert Variable</uicontrol> button
-and select the variable to be inserted. </cmd><info>For example, the <b>date</b> variable
-indicates the current date will be inserted. </info></step>
-<step><cmd>Click <uicontrol>Apply</uicontrol> and then <uicontrol>OK</uicontrol> to
-save your changes.</cmd></step>
-</steps>
-<postreq>You can edit, remove, import, or export a template by using the same
-preferences page. <p>If you have a template that you do not want to remove,
-but you no longer want the template to appear in the DTD templates list when
-you create a file, go to the<b> DTD Templates</b> preferences page and clear
-its check box.</p></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html deleted file mode 100644 index 333a75447e..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tdtemplt.html +++ /dev/null @@ -1,83 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Working with DTD templates" /> -<meta name="abstract" content="Templates are a chunk of predefined code that you can insert into a DTD file when it is created. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time." /> -<meta name="description" content="Templates are a chunk of predefined code that you can insert into a DTD file when it is created. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time." /> -<meta content="DTD templates, creating, templates, DTDs" name="DC.subject" /> -<meta content="DTD templates, creating, templates, DTDs" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretdtd.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twmacro" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Working with DTD templates</title> -</head> -<body id="twmacro"><a name="twmacro"><!-- --></a> - - -<h1 class="topictitle1">Working with DTD templates</h1> - - - - -<div><p>Templates are a chunk of predefined code that you can insert into -a DTD file when it is created. You may find a template useful when you have -a certain piece of code you want to reuse several times, and you do not want -to write it out every time.</p> - -<div class="section"><p>To create a new DTD template follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">DTD Files</span> > <span class="uicontrol">DTD -Templates</span></span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">New</span> if you want to create a completely -new template.</span></li> - -<li class="stepexpand"><span>Supply a new template <span class="uicontrol">Name</span> and <span class="uicontrol">Description</span>.</span> -</li> - -<li class="stepexpand"><span>Specify the <span class="uicontrol">Context</span> for the template.</span> - This is the context in which the template is available in the proposal -list when content assist is requested. </li> - -<li class="stepexpand"><span>Specify the <span class="uicontrol">Pattern</span> for your template using -the appropriate tags, attributes, or attribute values to be inserted by content -assist.</span></li> - -<li class="stepexpand"><span>If you want to insert a variable, click the <span class="uicontrol">Insert Variable</span> button -and select the variable to be inserted. </span> For example, the <strong>date</strong> variable -indicates the current date will be inserted. </li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Apply</span> and then <span class="uicontrol">OK</span> to -save your changes.</span></li> - -</ol> - -<div class="section">You can edit, remove, import, or export a template by using the same -preferences page. <p>If you have a template that you do not want to remove, -but you no longer want the template to appear in the DTD templates list when -you create a file, go to the<strong> DTD Templates</strong> preferences page and clear -its check box.</p> -</div> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/tcretdtd.html" title="A document type definition (DTD) contains a set of rules that can be used to validate an XML file. After you have created a DTD, you can edit it manually, adding declarations that define elements, attributes, entities, and notations, and how they can be used for any XML files that reference the DTD file.">Creating DTDs</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.dita b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.dita deleted file mode 100644 index 1714d29e08..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="ttaghilt" xml:lang="en-us">
-<title>Setting source highlighting styles</title>
-<titlealts>
-<searchtitle>Setting source highlighting styles for DTD files</searchtitle>
-</titlealts>
-<shortdesc>If desired, you can change various aspects of how the DTD source
-code is displayed in the Source view of the DTD editor, such as the colors
-the tags will be displayed in.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DTD<indexterm>highlighting styles</indexterm></indexterm>
-<indexterm>XML editor<indexterm>DTD highlighting styles</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To set highlighting styles for the DTD code, follow these steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>DTD Files</uicontrol><uicontrol> DTD
-Styles</uicontrol></menucascade>.</cmd></step>
-<step><cmd>In the <uicontrol>Content type</uicontrol> list, select the source
-tag type that you wish to set a highlighting style for. You can also click
-text in the sample text to specify the source tag type that you wish to set
-a highlighting style for.</cmd></step>
-<step><cmd>Click the <uicontrol>Foreground</uicontrol> box.</cmd></step>
-<step><cmd>Select the color that you want the text of the tag to appear in
-and click <uicontrol>OK</uicontrol>.</cmd></step>
-<step><cmd>Click the <uicontrol>Background</uicontrol> box.</cmd></step>
-<step><cmd>Select the color that you want to appear behind the tag and click <uicontrol>OK</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the <uicontrol>Bold</uicontrol> check box if you want to
-make the type bold.</cmd></step>
-<step><cmd>Click <uicontrol>Restore Default</uicontrol> to set the highlighting
-styles back to their default values. If you only want to reset the value for
-a particular content type, select it in the <uicontrol>Content type </uicontrol> field,
-the click the <uicontrol>Restore Default</uicontrol> button next to it. </cmd>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to save your changes.</cmd></step>
-</steps>
-<result></result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html deleted file mode 100644 index 1e343822fc..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tedtsrcst.html +++ /dev/null @@ -1,82 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting source highlighting styles" /> -<meta name="abstract" content="If desired, you can change various aspects of how the DTD source code is displayed in the Source view of the DTD editor, such as the colors the tags will be displayed in." /> -<meta name="description" content="If desired, you can change various aspects of how the DTD source code is displayed in the Source view of the DTD editor, such as the colors the tags will be displayed in." /> -<meta content="DTDs (document type definitions), XML editor preferences, setting highlighting styles, XML editor, preferences, setting DTD highlighting styles" name="DC.subject" /> -<meta content="DTDs (document type definitions), XML editor preferences, setting highlighting styles, XML editor, preferences, setting DTD highlighting styles" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretdtd.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ttaghilt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting source highlighting styles for DTD files</title> -</head> -<body id="ttaghilt"><a name="ttaghilt"><!-- --></a> - - -<h1 class="topictitle1">Setting source highlighting styles</h1> - - - - -<div><p>If desired, you can change various aspects of how the DTD source -code is displayed in the Source view of the DTD editor, such as the colors -the tags will be displayed in.</p> - -<div class="section"><p>To set highlighting styles for the DTD code, follow these steps:</p> -</div> - -<ol> -<li><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">DTD Files</span> > <span class="uicontrol"> DTD -Styles</span></span>.</span></li> - -<li><span>In the <span class="uicontrol">Content type</span> list, select the source -tag type that you wish to set a highlighting style for. You can also click -text in the sample text to specify the source tag type that you wish to set -a highlighting style for.</span></li> - -<li><span>Click the <span class="uicontrol">Foreground</span> box.</span></li> - -<li><span>Select the color that you want the text of the tag to appear in -and click <span class="uicontrol">OK</span>.</span></li> - -<li><span>Click the <span class="uicontrol">Background</span> box.</span></li> - -<li><span>Select the color that you want to appear behind the tag and click <span class="uicontrol">OK</span>.</span> -</li> - -<li><span>Select the <span class="uicontrol">Bold</span> check box if you want to -make the type bold.</span></li> - -<li><span>Click <span class="uicontrol">Restore Default</span> to set the highlighting -styles back to their default values. If you only want to reset the value for -a particular content type, select it in the <span class="uicontrol">Content type </span> field, -the click the <span class="uicontrol">Restore Default</span> button next to it. </span> -</li> - -<li><span>Click <span class="uicontrol">OK</span> to save your changes.</span></li> - -</ol> - -<div class="section" /> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/tcretdtd.html" title="A document type definition (DTD) contains a set of rules that can be used to validate an XML file. After you have created a DTD, you can edit it manually, adding declarations that define elements, attributes, entities, and notations, and how they can be used for any XML files that reference the DTD file.">Creating DTDs</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.dita b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.dita deleted file mode 100644 index 18993b857f..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.dita +++ /dev/null @@ -1,33 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="timptdtd" xml:lang="en-us">
-<title>Importing DTDs</title>
-<titlealts>
-<searchtitle>Importing DTDs</searchtitle>
-</titlealts>
-<shortdesc>If you want to work with DTD files that you created outside of
-the product, you can import them into the workbench and open them in the DTD
-editor. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DTD<indexterm>importing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To import a DTD into the workbench, follow these steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>File</uicontrol><uicontrol>Import</uicontrol>
-</menucascade>.</cmd></step>
-<step><cmd>Select the import source and click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>Fill in the fields in the <uicontrol>Import</uicontrol> wizard
-as necessary.</cmd></step>
-<step><cmd>When you are finished, click <uicontrol>Finish</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the DTD file in the Navigator view and double-click it to
-open it in the DTD editor.</cmd></step>
-</steps>
-<result><p>After you have imported a DTD file into the workbench and opened
-it in the DTD editor, you can edit it manually.</p></result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html deleted file mode 100644 index 24cfbbe275..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/timptdtd.html +++ /dev/null @@ -1,69 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Importing DTDs" /> -<meta name="abstract" content="If you want to work with DTD files that you created outside of the product, you can import them into the workbench and open them in the DTD editor." /> -<meta name="description" content="If you want to work with DTD files that you created outside of the product, you can import them into the workbench and open them in the DTD editor." /> -<meta content="DTDs (document type definitions), importing" name="DC.subject" /> -<meta content="DTDs (document type definitions), importing" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cworkdtds.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="timptdtd" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Importing DTDs</title> -</head> -<body id="timptdtd"><a name="timptdtd"><!-- --></a> - - -<h1 class="topictitle1">Importing DTDs</h1> - - - - -<div><p>If you want to work with DTD files that you created outside of -the product, you can import them into the workbench and open them in the DTD -editor. </p> - -<div class="section"><p>To import a DTD into the workbench, follow these steps:</p> -</div> - -<ol> -<li><span>Click <span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">Import</span> -</span>.</span></li> - -<li><span>Select the import source and click <span class="uicontrol">Next</span>.</span> -</li> - -<li><span>Fill in the fields in the <span class="uicontrol">Import</span> wizard -as necessary.</span></li> - -<li><span>When you are finished, click <span class="uicontrol">Finish</span>.</span> -</li> - -<li><span>Select the DTD file in the Navigator view and double-click it to -open it in the DTD editor.</span></li> - -</ol> - -<div class="section"><p>After you have imported a DTD file into the workbench and opened -it in the DTD editor, you can edit it manually.</p> -</div> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cworkdtds.html" title="This sections contains information on the following:">Working with DTDs</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.dita b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.dita deleted file mode 100644 index d4c49df5ee..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.dita +++ /dev/null @@ -1,42 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tvaldtd" xml:lang="en-us">
-<title>Validating DTDs</title>
-<titlealts>
-<searchtitle>Validating DTDs</searchtitle>
-</titlealts>
-<shortdesc>Validating a DTD file lets you verify that it is well formed and
-does not contain any errors.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DTD<indexterm>validating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives. </p><p>To validate
-a DTD, follow these steps:</p></context>
-<steps>
-<step><cmd>In the Navigator view, right-click the DTD and click <menucascade>
-<uicontrol>Validate DTD File</uicontrol></menucascade>.</cmd></step>
-</steps>
-<result>A dialog opens, indicating if the DTD file was successfully validated
-or not. If the file is invalid, any errors will appear in the Problems view. <p><b>Note</b>:
-If you receive an error message indicating that the Problems view is full,
-you can increase the number of error messages allowed by selecting <menucascade>
-<uicontrol>Properties</uicontrol><uicontrol>Validation</uicontrol></menucascade> from
-the project's pop-up menu and specifying the maximum number of error messages
-allowed. You might have to select the <uicontrol>Override validation preferences</uicontrol> check
-box in order to enable the <uicontrol>Maximum number of validation messages</uicontrol> field</p><p>You
-can set up project's properties so that different types of project resources
-are automatically validated when you save them. From a project's pop-up menu
-select <uicontrol>Properties</uicontrol>, then select <uicontrol>Validation</uicontrol>.
-Any validators you can run against your project will be listed in the
-Validation page. </p></result>
-</taskbody>
-<related-links>
-<link href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.dita" scope="peer">
-<desc>General validation information</desc>
-</link>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html b/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html deleted file mode 100644 index 5a49f1dcc3..0000000000 --- a/docs/org.eclipse.wst.dtdeditor.doc.user/topics/tvaldtd.html +++ /dev/null @@ -1,74 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Validating DTDs" /> -<meta name="abstract" content="Validating a DTD file lets you verify that it is well formed and does not contain any errors." /> -<meta name="description" content="Validating a DTD file lets you verify that it is well formed and does not contain any errors." /> -<meta content="DTDs (document type definitions), validating" name="DC.subject" /> -<meta content="DTDs (document type definitions), validating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cworkdtds.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tvaldtd" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Validating DTDs</title> -</head> -<body id="tvaldtd"><a name="tvaldtd"><!-- --></a> - - -<h1 class="topictitle1">Validating DTDs</h1> - - - - -<div><p>Validating a DTD file lets you verify that it is well formed and -does not contain any errors.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives. </p> -<p>To validate -a DTD, follow these steps:</p> -</div> - - -<div class="p"><span>In the Navigator view, right-click the DTD and click <span class="menucascade"> -<span class="uicontrol">Validate DTD File</span></span>.</span></div> - - -<div class="section">A dialog opens, indicating if the DTD file was successfully validated -or not. If the file is invalid, any errors will appear in the Problems view.  <p><strong>Note</strong>: -If you receive an error message indicating that the Problems view is full, -you can increase the number of error messages allowed by selecting <span class="menucascade"> -<span class="uicontrol">Properties</span> > <span class="uicontrol">Validation</span></span> from -the project's pop-up menu and specifying the maximum number of error messages -allowed. You might have to select the <span class="uicontrol">Override validation preferences</span> check -box in order to enable the <span class="uicontrol">Maximum number of validation messages</span> field</p> -<p>You -can set up project's properties so that different types of project resources -are automatically validated when you save them. From a project's pop-up menu -select <span class="uicontrol">Properties</span>, then select <span class="uicontrol">Validation</span>. -Any validators you can run against your project will be listed in the -Validation page. </p> -</div> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../topics/cworkdtds.html" title="This sections contains information on the following:">Working with DTDs</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" title="General validation information">../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.html.ui.infopop/.cvsignore b/docs/org.eclipse.wst.html.ui.infopop/.cvsignore deleted file mode 100644 index c14487ceac..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -build.xml diff --git a/docs/org.eclipse.wst.html.ui.infopop/.project b/docs/org.eclipse.wst.html.ui.infopop/.project deleted file mode 100644 index 05aa1b4bed..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.html.ui.infopop</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts.xml b/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts.xml deleted file mode 100644 index 8b8dc10ff2..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts.xml +++ /dev/null @@ -1,95 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> - -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<contexts> -<context id="misc0170"> -<description>Use this dialog to edit the Web content settings for a Web project. You can specify the default document type, CSS profile, and target device. The public ID and system ID are populated automatically. To restore the defaults, click <b>Restore Defaults</b>. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="webx0030"> -<description>This page lets you specify the line delimiter and the text encoding that will be used when you create, save, or load an HTML file. - -Various development platforms use different line delimiters to indicate the start of a new line. Select the operating system that corresponds to your development or deployment platform. -<b>Note:</b> This delimiter will not automatically be added to any documents that currently exist. It will be added only to documents that you create after you select the line delimiter type and click <b>Apply</b>, or to existing files that you open and then resave after you select the line delimiter type and click <b>Apply</b>. - -The encoding attribute is used to specify the default character encoding set that is used when either creating HTML files or loading your HTML files into the editor. Changing the creating files encoding causes any new HTML files that are created from scratch to use the selected encoding. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="webx0031"> -<description>This page lets you specify the formatting, content assist, and capitalization style that will be used when you edit an HTML file. - -Enter a maximum width in the <b>Line width</b> field to specify the line width to break a line to fit onto more than one line when the document is formatted. - -Select <b>Split multiple attributes each on a new line</b> to start every attribute on a new line when the document is formatted. Attributes will return to the same margin as the previous line. - -Select <b>Indent using tabs</b> if you want to use tab characters (\t) as the standard formatting indentation. - -If you prefer to use spaces, select <b>Indent using spaces</b>. - -You can also specify the <b>Indentation size</b> which is the number of tabs or space characters used for formatting indentation. - -Select <b>Clear all blank lines</b> to remove blank lines when the document is formatted. - -To apply these formatting styles, select the <b>Format Document</b> menu item. - -If the <b>Automatically make suggestions</b> check box is selected, you can specify that certain characters will cause the content assist list to pop up automatically. Specify these characters in the <b>Prompt when these characters are inserted</b> field. - -Select the Uppercase or Lowercase radio button to determine the case for tag and attribute names that are inserted into the document when using content assist or code generation. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="webx0032"> -<description>This page lets you customize the syntax highlighting that the HTML editor does when you are editing a file. - -The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting. - -The <b>Foreground</b> and <b>Background</b> push buttons open <b>Color</b> dialog boxes that allow you to specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold. - -Click the <b>Restore Default</b> push button to set the highlighting styles back to their default values. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="webx0033"> -<description>This page lets you create new and edit existing templates that will be used when you edit an HTML file. -</description> -<topic label="Adding and removing HTML templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html"/> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -</context> - -<context id="xmlm1100"> -<description>Cleanup options enable you to update a document so that it is well-formed and formatted. - -The following cleanup options let you select radio buttons to choose the type of cleanup to be performed: -- <b>Tag name case for HTML</b>: Unless set to <b>As-is</b>, changes the case of all tags in a file for easier visual parsing and consistency. -- <b>Attribute name case for HTML</b>: Unless set to <b>As-is</b>, changes the case of all attributes in a file for easier visual parsing and consistency. - -The following cleanup options can be set to on or off, so that you can limit the type of cleanup performed: -- <b>Insert required attributes</b>: Inserts an missing attributes that are required by the tag to make the element or document well-formed. -- <b>Insert missing tags</b>: Completes any missing tags (such as adding an end tag) necessary to make the element or document well-formed. -- <b>Quote attribute values</b>: Appropriately adds double- or single-quotes before and after attribute values if they are missing. -- <b>Format source</b>: Formats the document just as the <b>Format Document</b> context menu option does, immediately after performing any other specified <b>Cleanup</b> options. -- <b>Convert line delimiters to</b>: Converts all line delimiters in the file to the selected operating system's type. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -</contexts> diff --git a/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts2.xml b/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts2.xml deleted file mode 100644 index b614187af7..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/EditorHtmlContexts2.xml +++ /dev/null @@ -1,23 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> - -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<contexts> -<context id="htmlsource_source_HelpId"> -<description>The HTML source page editor lets you edit a file that is coded in the Hypertext Markup Language or in XHTML. The editor provides many text editing features, such as content assist, user-defined templates, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -<topic label="Adding and removing HTML templates" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html"/> -</context> -</contexts> diff --git a/docs/org.eclipse.wst.html.ui.infopop/HTMLWizContexts.xml b/docs/org.eclipse.wst.html.ui.infopop/HTMLWizContexts.xml deleted file mode 100644 index ed68cf2de7..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/HTMLWizContexts.xml +++ /dev/null @@ -1,21 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> -<context id="htmlw0010"> -<description>Select the HTML template checkbox to create your HTML file based on a default template. Choose one of the frameset templates if you are developing a Web site with frames. If you do not select a template, your newly created JSP file will be completely blank. -</description> -</context> - - - -</contexts> diff --git a/docs/org.eclipse.wst.html.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.html.ui.infopop/META-INF/MANIFEST.MF deleted file mode 100644 index 6c2c257da1..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/META-INF/MANIFEST.MF +++ /dev/null @@ -1,7 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %Bundle-Name.0 -Bundle-SymbolicName: org.eclipse.wst.html.ui.infopop; singleton:=true -Bundle-Version: 1.0.2.qualifier -Bundle-Vendor: %Bundle-Vendor.0 -Bundle-Localization: plugin diff --git a/docs/org.eclipse.wst.html.ui.infopop/about.html b/docs/org.eclipse.wst.html.ui.infopop/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.html.ui.infopop/build.properties b/docs/org.eclipse.wst.html.ui.infopop/build.properties deleted file mode 100644 index 71f97011b5..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/build.properties +++ /dev/null @@ -1,7 +0,0 @@ -bin.includes = plugin.xml,\ - about.html,\ - EditorHtmlContexts.xml,\ - META-INF/,\ - EditorHtmlContexts2.xml,\ - plugin.properties -src.includes = build.properties diff --git a/docs/org.eclipse.wst.html.ui.infopop/plugin.properties b/docs/org.eclipse.wst.html.ui.infopop/plugin.properties deleted file mode 100644 index a24444c18a..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/plugin.properties +++ /dev/null @@ -1,3 +0,0 @@ -# properties file for org.eclipse.wst.html.ui.infopop -Bundle-Vendor.0 = Eclipse.org -Bundle-Name.0 = HTML editor infopops
\ No newline at end of file diff --git a/docs/org.eclipse.wst.html.ui.infopop/plugin.xml b/docs/org.eclipse.wst.html.ui.infopop/plugin.xml deleted file mode 100644 index 9b085e76a4..0000000000 --- a/docs/org.eclipse.wst.html.ui.infopop/plugin.xml +++ /dev/null @@ -1,26 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<!-- ================================================= --> -<!-- This is the plugin for declaring the help --> -<!-- contributions for using the tool. --> -<!-- ================================================= --> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - -<extension point="org.eclipse.help.contexts"> - <contexts file="EditorHtmlContexts.xml" plugin ="org.eclipse.wst.html.ui"/> - <contexts file="EditorHtmlContexts2.xml" plugin ="org.eclipse.wst.html.core"/> - <contexts file="HTMLWizContexts.xml" plugin="org.eclipse.wst.html.ui"/> -</extension> - - -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/.cvsignore b/docs/org.eclipse.wst.sse.doc.user/.cvsignore deleted file mode 100644 index 33a2f88503..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -build.xml -org.eclipse.wst.sse.doc.user_1.0.0.jar -temp -DitaLink.cat
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/.project b/docs/org.eclipse.wst.sse.doc.user/.project deleted file mode 100644 index e2d640609c..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.sse.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.wst.sse.doc.user/DocBuild.xml b/docs/org.eclipse.wst.sse.doc.user/DocBuild.xml deleted file mode 100644 index d8406e0f33..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/DocBuild.xml +++ /dev/null @@ -1,59 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<!-- - - This script build the Help plug-in by transforming the DITA source files into HTML. - - To use this script, you must install DITA-OT on your machine in the directory - defined by the dita.ot.dir property. - - Run the default target after you edit the DITA source files to regenerate the HTML. - - To customize this script for other Help plug-ins, modify the value of the args.input property - to be the DITA map file for the plug-in. - - NOTE: This script assumes that links to sibling Help plug-ins have scope="peer", otherwise the - output directory structure will be shifted incorrectly. - - NOTE: This script assumes that you hand code your plugin.xml file in myplugin.xml. This file - will be copied over the generated plugin.xml which is currently not being generated correctly - by DITA-OT. - - ChangeLog: - 2006-04-05 Arthur Ryman <ryman@ca.ibm.com> - - Created. - ---> -<project name="eclipsehelp" default="all"> - - <property name="dita.ot.dir" location="C:/DITA-OT1.2.2" /> - - <path id="dost.class.path"> - <pathelement location="${dita.ot.dir}${file.separator}lib${file.separator}dost.jar" /> - </path> - - <taskdef name="integrate" classname="org.dita.dost.platform.IntegratorTask"> - <classpath refid="dost.class.path" /> - </taskdef> - <target name="all" depends="integrate, eclipsehelp"> - </target> - <target name="integrate"> - <integrate ditadir="${dita.ot.dir}" /> - </target> - - <!-- revise below here --> - <target name="eclipsehelp"> - <ant antfile="${dita.ot.dir}${file.separator}conductor.xml" target="init" dir="${dita.ot.dir}"> - <property name="args.copycss" value="no" /> - <property name="args.csspath" value="org.eclipse.wst.doc.user" /> - <property name="args.eclipse.provider" value="Eclipse.org" /> - <property name="args.eclipse.version" value="1.5.0" /> - <property name="args.input" location="sse_toc.ditamap" /> - <property name="clean.temp" value="true" /> - <property name="dita.extname" value=".dita" /> - <property name="dita.temp.dir" location="temp" /> - <property name="output.dir" location=".." /> - <property name="transtype" value="eclipsehelp" /> - </ant> - <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" /> - </target> -</project> diff --git a/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF deleted file mode 100644 index 819206196c..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %Bundle-Name.0 -Bundle-SymbolicName: org.eclipse.wst.sse.doc.user; singleton:=true -Bundle-Version: 1.1.0.qualifier -Bundle-Vendor: %Bundle-Vendor.0 -Bundle-Localization: plugin -Bundle-RequiredExecutionEnvironment: J2SE-1.4 diff --git a/docs/org.eclipse.wst.sse.doc.user/about.html b/docs/org.eclipse.wst.sse.doc.user/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.sse.doc.user/build.properties b/docs/org.eclipse.wst.sse.doc.user/build.properties deleted file mode 100644 index 950d6430da..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/build.properties +++ /dev/null @@ -1,16 +0,0 @@ -bin.includes = about.html,\ - images/,\ - plugin.xml,\ - sse_toc.xml,\ - org.eclipse.wst.sse.doc.userindex.xml,\ - topics/*.htm*,\ - index/,\ - META-INF/,\ - plugin.properties -src.includes = build.properties,\ - *.maplist,\ - *.ditamap,\ - topics/*.dita -bin.excludes = DocBuild.xml,\ - myPlugin*.xml - diff --git a/docs/org.eclipse.wst.sse.doc.user/images/ncontass.gif b/docs/org.eclipse.wst.sse.doc.user/images/ncontass.gif Binary files differdeleted file mode 100644 index d82014f049..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/images/ncontass.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/images/njscdast.gif b/docs/org.eclipse.wst.sse.doc.user/images/njscdast.gif Binary files differdeleted file mode 100644 index 41a141cb43..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/images/njscdast.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/images/nlinux.gif b/docs/org.eclipse.wst.sse.doc.user/images/nlinux.gif Binary files differdeleted file mode 100644 index 7c135cfe64..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/images/nlinux.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/images/nmacscrp.gif b/docs/org.eclipse.wst.sse.doc.user/images/nmacscrp.gif Binary files differdeleted file mode 100644 index 54a6371b3a..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/images/nmacscrp.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/images/nquest.gif b/docs/org.eclipse.wst.sse.doc.user/images/nquest.gif Binary files differdeleted file mode 100644 index 3faa1e262a..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/images/nquest.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/images/nwin.gif b/docs/org.eclipse.wst.sse.doc.user/images/nwin.gif Binary files differdeleted file mode 100644 index 895f9ca06d..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/images/nwin.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/index/_p.cfs b/docs/org.eclipse.wst.sse.doc.user/index/_p.cfs Binary files differdeleted file mode 100644 index ac3ffd252c..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/index/_p.cfs +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/index/deletable b/docs/org.eclipse.wst.sse.doc.user/index/deletable Binary files differdeleted file mode 100644 index e423242b3e..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/index/deletable +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/index/indexed_contributions b/docs/org.eclipse.wst.sse.doc.user/index/indexed_contributions deleted file mode 100644 index 1207a6ca91..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/index/indexed_contributions +++ /dev/null @@ -1,3 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:15:03 EDT 2007
-org.eclipse.wst.sse.doc.user=org.eclipse.wst.sse.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.wst.sse.doc.user/index/indexed_dependencies b/docs/org.eclipse.wst.sse.doc.user/index/indexed_dependencies deleted file mode 100644 index 2810719387..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/index/indexed_dependencies +++ /dev/null @@ -1,4 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:15:03 EDT 2007
-lucene=1.4.103.v20060601
-analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.wst.sse.doc.user/index/indexed_docs b/docs/org.eclipse.wst.sse.doc.user/index/indexed_docs deleted file mode 100644 index ef97094052..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/index/indexed_docs +++ /dev/null @@ -1,24 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:15:03 EDT 2007
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html=0
-/org.eclipse.wst.sse.doc.user/topics/tcontenttype.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html=0
-/org.eclipse.wst.sse.doc.user/topics/csrcedt001.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html=0
-/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html=0
-/org.eclipse.wst.sse.doc.user/topics/cvalidate.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html=0
-/org.eclipse.wst.sse.doc.user/topics/cencoding.html=0
-/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html=0
-/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html=0
diff --git a/docs/org.eclipse.wst.sse.doc.user/index/segments b/docs/org.eclipse.wst.sse.doc.user/index/segments Binary files differdeleted file mode 100644 index 19b5d0c420..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/index/segments +++ /dev/null diff --git a/docs/org.eclipse.wst.sse.doc.user/myplugin.xml b/docs/org.eclipse.wst.sse.doc.user/myplugin.xml deleted file mode 100644 index a9942932d6..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/myplugin.xml +++ /dev/null @@ -1,29 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<!-- /******************************************************************************* - * Copyright (c) 2001, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<!-- ===================================================== --> -<!-- This is the plug-in for declaring the help pages --> -<!-- for the structured text editors (source editors). --> -<!-- ===================================================== --> - -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="sse_toc.xml"> - <index path="index/"/> - </toc> - </extension> - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.wst.sse.doc.userindex.xml"/> -</extension> -</plugin> diff --git a/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.user.maplist b/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.user.maplist deleted file mode 100644 index b0f4da55cb..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.user.maplist +++ /dev/null @@ -1,7 +0,0 @@ -<maplist version="3.6.2">
- <nav>
- <map file="sse_toc.ditamap"/>
- </nav>
- <link>
- </link>
-</maplist>
diff --git a/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.userindex.html b/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.userindex.html deleted file mode 100644 index 10a8886d0e..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.userindex.html +++ /dev/null @@ -1,242 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<meta name="copyright" content="(C) Copyright IBM Corporation 2007" /> -<meta name="security" content="public" /> -<meta name="Robots" content="index,follow" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta name="DC.Format" content="XHTML" /> -<!-- All rights reserved. Licensed Materials Property of IBM --> -<!-- US Government Users Restricted Rights --> -<!-- Use, duplication or disclosure restricted by --> -<!-- GSA ADP Schedule Contract with IBM Corp. --> -<link rel="stylesheet" type="text/css" href="ibmdita.css" /> -<title>Index</title> -</head> -<body> -<h1>Index</h1> -<a name="IDX0_41" href="#IDX1_41">A</a> -<a name="IDX0_43" href="#IDX1_43">C</a> -<a name="IDX0_44" href="#IDX1_44">D</a> -<a name="IDX0_46" href="#IDX1_46">F</a> -<a name="IDX0_48" href="#IDX1_48">H</a> -<a name="IDX0_4A" href="#IDX1_4A">J</a> -<a name="IDX0_4D" href="#IDX1_4D">M</a> -<a name="IDX0_53" href="#IDX1_53">S</a> -<a name="IDX0_54" href="#IDX1_54">T</a> -<a name="IDX0_56" href="#IDX1_56">V</a> -<a name="IDX0_58" href="#IDX1_58">X</a> -<hr></hr> -<strong><a name="IDX1_41" href="#IDX0_41">A</a></strong> -<ul class="indexlist"> -<li>annotation preferences -<ul class="indexlist"> -<li><a href="topics/tsrcedt001.html#tsrcedt001">markup language settings</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_43" href="#IDX0_43">C</a></strong> -<ul class="indexlist"> -<li>character encoding -<ul class="indexlist"> -<li><a href="topics/cencoding.html#cencoding">location in files</a> -</li> -</ul> -</li> -<li>content assistance -<ul class="indexlist"> -<li><a href="topics/tsrcedt023.html#tsrcedt023">enabling for JSP files</a> -</li> -<li><a href="topics/csrcedt006.html#csrcedt006">overview</a> -</li> -<li><a href="topics/tsrcedt005.html#tsrcedt005">structured text editors</a> -</li> -</ul> -</li> -<li>content types -<ul class="indexlist"> -<li><a href="topics/tcontenttype.html#tcontenttype">mapping file extensions</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_44" href="#IDX0_44">D</a></strong> -<ul class="indexlist"> -<li>drawers -<ul class="indexlist"> -<li><a href="topics/tsrcedt016.html#tsrcedt016">snippets view</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_46" href="#IDX0_46">F</a></strong> -<ul class="indexlist"> -<li>file extensions -<ul class="indexlist"> -<li><a href="topics/tcontenttype.html#tcontenttype">mapping content types</a> -</li> -</ul> -</li> -<li>file types -<ul class="indexlist"> -<li><a href="topics/tcontenttype.html#tcontenttype">editors</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_48" href="#IDX0_48">H</a></strong> -<ul class="indexlist"> -<li>HTML -<ul class="indexlist"> -<li>templates -<ul class="indexlist"> -<li><a href="topics/tsrcedt024.html#tsrcedt024">adding</a> -</li> -<li><a href="topics/tsrcedt024.html#tsrcedt024">removing</a> -</li> -</ul> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_4A" href="#IDX0_4A">J</a></strong> -<ul class="indexlist"> -<li>JSP files -<ul class="indexlist"> -<li><a href="topics/cencoding.html#cencoding">character encoding</a> -</li> -<li><a href="topics/tsrcedt023.html#tsrcedt023">enabling content assistance</a> -</li> -</ul> -</li> -<li>JSP pages -<ul class="indexlist"> -<li><a href="topics/tsrcedt028.html#tsrcedt028">templates</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_4D" href="#IDX0_4D">M</a></strong> -<ul class="indexlist"> -<li>markup languages -<ul class="indexlist"> -<li><a href="topics/tsrcedt000.html#tsrcedt000">editing text</a> -</li> -<li><a href="topics/tsrcedt001.html#tsrcedt001">setting annotation preferences</a> -</li> -<li><a href="topics/tsrcedt027.html#tsrcedt027">templates</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_53" href="#IDX0_53">S</a></strong> -<ul class="indexlist"> -<li>snippet drawers -<ul class="indexlist"> -<li><a href="topics/tsrcedt015.html#tsrcedt015">adding items</a> -</li> -</ul> -</li> -<li>snippet items -<ul class="indexlist"> -<li><a href="topics/tsrcedt015.html#tsrcedt015">adding to drawers</a> -</li> -</ul> -</li> -<li>snippets -<ul class="indexlist"> -<li><a href="topics/tsrcedt014.html#tsrcedt014">drawer customization</a> -</li> -<li><a href="topics/tsrcedt022.html#tsrcedt022">editing items</a> -</li> -<li><a href="topics/tsrcedt016.html#tsrcedt016">modifying drawers</a> -</li> -<li><a href="topics/tsrcedt026.html#tsrcedt026">overview</a> -</li> -</ul> -</li> -<li>Snippets view -<ul class="indexlist"> -<li><a href="topics/csrcedt001.html#csrcedt001">overview</a> -</li> -</ul> -</li> -<li>spell check -<ul class="indexlist"> -<li><a href="topics/tsrcedt010.html#tsrcedt010">structured text editors</a> -</li> -</ul> -</li> -<li>structured text editors -<ul class="indexlist"> -<li>content assistance <a href="topics/tsrcedt005.html#tsrcedt005">(1)</a>, <a href="topics/csrcedt006.html#csrcedt006">(2)</a> -</li> -<li><a href="topics/csrcedt004.html#csrcedt004">overview</a> -</li> -<li><a href="topics/tsrcedt025.html#tsrcedt025">preference setting</a> -</li> -<li><a href="topics/tsrcedt010.html#tsrcedt010">spell check</a> -</li> -<li><a href="topics/tsrcedt007.html#tsrcedt007">text search</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_54" href="#IDX0_54">T</a></strong> -<ul class="indexlist"> -<li>templates -<ul class="indexlist"> -<li><a href="topics/tsrcedt024.html#tsrcedt024">HTML</a> -</li> -<li><a href="topics/tsrcedt028.html#tsrcedt028">JSP pages</a> -</li> -<li><a href="topics/tsrcedt027.html#tsrcedt027">markup languages</a> -</li> -<li><a href="topics/csrcedt004.html#csrcedt004">structured text editors</a> -</li> -<li><a href="topics/tsrcedt029.html#tsrcedt027">XML</a> -</li> -</ul> -</li> -<li>text -<ul class="indexlist"> -<li><a href="topics/tsrcedt000.html#tsrcedt000">editing in markup languages</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_56" href="#IDX0_56">V</a></strong> -<ul class="indexlist"> -<li>validation -<ul class="indexlist"> -<li><a href="topics/cvalidate.html#csrcedt001">source vs batch</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_58" href="#IDX0_58">X</a></strong> -<ul class="indexlist"> -<li>XHTML -<ul class="indexlist"> -<li><a href="topics/cencoding.html#cencoding">character encoding</a> -</li> -</ul> -</li> -<li>XML -<ul class="indexlist"> -<li><a href="topics/cencoding.html#cencoding">character encoding</a> -</li> -</ul> -</li> -<li>xml templates -<ul class="indexlist"> -<li><a href="topics/tsrcedt029.html#tsrcedt027">adding</a> -</li> -</ul> -</li> -</ul> -</body></html> diff --git a/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.userindex.xml b/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.userindex.xml deleted file mode 100644 index 02d9209501..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/org.eclipse.wst.sse.doc.userindex.xml +++ /dev/null @@ -1,172 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<index> - <entry keyword="structured text editors"> - <entry keyword="overview"> - <topic href="topics/csrcedt004.html#csrcedt004" title="Structured text editors for markup languages"/> - </entry> - <entry keyword="preference setting"> - <topic href="topics/tsrcedt025.html#tsrcedt025" title="Setting preferences for structured text editors"/> - </entry> - <entry keyword="content assistance"> - <topic href="topics/tsrcedt005.html#tsrcedt005" title="Getting content assistance in structured text editors"/> - <topic href="topics/csrcedt006.html#csrcedt006" title="Content assist"/> - </entry> - <entry keyword="text search"> - <topic href="topics/tsrcedt007.html#tsrcedt007" title="Searching or finding text within a file"/> - </entry> - <entry keyword="spell check"> - <topic href="topics/tsrcedt010.html#tsrcedt010" title="Checking spelling"/> - </entry> - </entry> - <entry keyword="templates"> - <entry keyword="structured text editors"> - <topic href="topics/csrcedt004.html#csrcedt004" title="Structured text editors for markup languages"/> - </entry> - <entry keyword="markup languages"> - <topic href="topics/tsrcedt027.html#tsrcedt027" title="Adding and removing markup language templates - overview"/> - </entry> - <entry keyword="HTML"> - <topic href="topics/tsrcedt024.html#tsrcedt024" title="Adding and removing HTML templates"/> - </entry> - <entry keyword="JSP pages"> - <topic href="topics/tsrcedt028.html#tsrcedt028" title="Adding and removing JSP templates"/> - </entry> - <entry keyword="XML"> - <topic href="topics/tsrcedt029.html#tsrcedt027" title="Adding and removing XML templates"/> - </entry> - </entry> - <entry keyword="markup languages"> - <entry keyword="editing text"> - <topic href="topics/tsrcedt000.html#tsrcedt000" title="Editing text coded in markup languages - overview"/> - </entry> - <entry keyword="setting annotation preferences"> - <topic href="topics/tsrcedt001.html#tsrcedt001" title="Setting annotation preferences for markup languages"/> - </entry> - <entry keyword="templates"> - <topic href="topics/tsrcedt027.html#tsrcedt027" title="Adding and removing markup language templates - overview"/> - </entry> - </entry> - <entry keyword="text"> - <entry keyword="editing in markup languages"> - <topic href="topics/tsrcedt000.html#tsrcedt000" title="Editing text coded in markup languages - overview"/> - </entry> - </entry> - <entry keyword="validation"> - <entry keyword="source vs batch"> - <topic href="topics/cvalidate.html#csrcedt001" title="Source and batch validation"/> - </entry> - </entry> - <entry keyword="annotation preferences"> - <entry keyword="markup language settings"> - <topic href="topics/tsrcedt001.html#tsrcedt001" title="Setting annotation preferences for markup languages"/> - </entry> - </entry> - <entry keyword="content assistance"> - <entry keyword="structured text editors"> - <topic href="topics/tsrcedt005.html#tsrcedt005" title="Getting content assistance in structured text editors"/> - </entry> - <entry keyword="overview"> - <topic href="topics/csrcedt006.html#csrcedt006" title="Content assist"/> - </entry> - <entry keyword="enabling for JSP files"> - <topic href="topics/tsrcedt023.html#tsrcedt023" title="Enabling content assist for JSP files"/> - </entry> - </entry> - <entry keyword="JSP files"> - <entry keyword="enabling content assistance"> - <topic href="topics/tsrcedt023.html#tsrcedt023" title="Enabling content assist for JSP files"/> - </entry> - <entry keyword="character encoding"> - <topic href="topics/cencoding.html#cencoding" title="File Encoding"/> - </entry> - </entry> - <entry keyword="content types"> - <entry keyword="mapping file extensions"> - <topic href="topics/tcontenttype.html#tcontenttype" title="Associating editors with additional files types"/> - </entry> - </entry> - <entry keyword="file extensions"> - <entry keyword="mapping content types"> - <topic href="topics/tcontenttype.html#tcontenttype" title="Associating editors with additional files types"/> - </entry> - </entry> - <entry keyword="file types"> - <entry keyword="editors"> - <topic href="topics/tcontenttype.html#tcontenttype" title="Associating editors with additional files types"/> - </entry> - </entry> - <entry keyword="character encoding"> - <entry keyword="location in files"> - <topic href="topics/cencoding.html#cencoding" title="File Encoding"/> - </entry> - </entry> - <entry keyword="XHTML"> - <entry keyword="character encoding"> - <topic href="topics/cencoding.html#cencoding" title="File Encoding"/> - </entry> - </entry> - <entry keyword="XML"> - <entry keyword="character encoding"> - <topic href="topics/cencoding.html#cencoding" title="File Encoding"/> - </entry> - </entry> - <entry keyword="spell check"> - <entry keyword="structured text editors"> - <topic href="topics/tsrcedt010.html#tsrcedt010" title="Checking spelling"/> - </entry> - </entry> - <entry keyword="HTML"> - <entry keyword="templates"> - <entry keyword="removing"> - <topic href="topics/tsrcedt024.html#tsrcedt024" title="Adding and removing HTML templates"/> - </entry> - <entry keyword="adding"> - <topic href="topics/tsrcedt024.html#tsrcedt024" title="Adding and removing HTML templates"/> - </entry> - </entry> - </entry> - <entry keyword="JSP pages"> - <entry keyword="templates"> - <topic href="topics/tsrcedt028.html#tsrcedt028" title="Adding and removing JSP templates"/> - </entry> - </entry> - <entry keyword="xml templates"> - <entry keyword="adding"> - <topic href="topics/tsrcedt029.html#tsrcedt027" title="Adding and removing XML templates"/> - </entry> - </entry> - <entry keyword="snippets"> - <entry keyword="overview"> - <topic href="topics/tsrcedt026.html#tsrcedt026" title="Editing with snippets - overview"/> - </entry> - <entry keyword="drawer customization"> - <topic href="topics/tsrcedt014.html#tsrcedt014" title="Adding snippets drawers"/> - </entry> - <entry keyword="editing items"> - <topic href="topics/tsrcedt022.html#tsrcedt022" title="Editing snippet items"/> - </entry> - <entry keyword="modifying drawers"> - <topic href="topics/tsrcedt016.html#tsrcedt016" title="Deleting or hiding snippet items or drawers"/> - </entry> - </entry> - <entry keyword="Snippets view"> - <entry keyword="overview"> - <topic href="topics/csrcedt001.html#csrcedt001" title="Snippets view"/> - </entry> - </entry> - <entry keyword="snippet drawers"> - <entry keyword="adding items"> - <topic href="topics/tsrcedt015.html#tsrcedt015" title="Adding items to snippets drawers"/> - </entry> - </entry> - <entry keyword="snippet items"> - <entry keyword="adding to drawers"> - <topic href="topics/tsrcedt015.html#tsrcedt015" title="Adding items to snippets drawers"/> - </entry> - </entry> - <entry keyword="drawers"> - <entry keyword="snippets view"> - <topic href="topics/tsrcedt016.html#tsrcedt016" title="Deleting or hiding snippet items or drawers"/> - </entry> - </entry> -</index>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/plugin.properties b/docs/org.eclipse.wst.sse.doc.user/plugin.properties deleted file mode 100644 index d97c2f1e6f..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/plugin.properties +++ /dev/null @@ -1,3 +0,0 @@ -# properties file for org.eclipse.wst.sse.doc.user -Bundle-Vendor.0 = Eclipse.org -Bundle-Name.0 = Structured text editor and snippets documentation
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/plugin.xml b/docs/org.eclipse.wst.sse.doc.user/plugin.xml deleted file mode 100644 index ebbb6bd131..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/plugin.xml +++ /dev/null @@ -1,28 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<!-- /******************************************************************************* - * Copyright (c) 2001, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<!-- ===================================================== --> -<!-- This is the plug-in for declaring the help pages --> -<!-- for the structured text editors (source editors). --> -<!-- ===================================================== --> - -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="sse_toc.xml"/> - <index path="index/"/> - </extension> - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.wst.sse.doc.userindex.xml"/> -</extension> -</plugin> diff --git a/docs/org.eclipse.wst.sse.doc.user/sse_toc.ditamap b/docs/org.eclipse.wst.sse.doc.user/sse_toc.ditamap deleted file mode 100644 index 90bc7518f8..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/sse_toc.ditamap +++ /dev/null @@ -1,55 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN"
- "map.dtd">
-<map id="wstssetoc" linking="none" title="Editing text coded in markup languages - overview">
-<topicref href="topics/csrcedt004.dita" navtitle="Structured text editors">
-<topicref href="topics/tsrcedt000.dita" locktitle="yes" navtitle="Editing text coded in markup languages "
-type="task">
-<topicref href="topics/cvalidate.dita" navtitle="Source and batch validation"
-type="concept"></topicref>
-<topicref href="topics/tsrcedt025.dita" navtitle="Setting preferences for structured text editors"
-type="task">
-<topicref href="topics/tsrcedt001.dita" navtitle="Setting annotation preferences for markup languages"
-type="task"></topicref>
-</topicref>
-<topicref href="topics/tsrcedt005.dita" navtitle="Getting content assistance in structured text editors"
-type="task">
-<topicref href="topics/csrcedt006.dita" navtitle="Content assist" type="concept">
-</topicref>
-<topicref href="topics/tsrcedt023.dita" navtitle="Making content assist work for JSP files"
-type="task"></topicref>
-</topicref>
-<topicref href="topics/tcontenttype.dita" navtitle="Associating editors with file types"
-type="task"></topicref>
-<topicref href="topics/cencoding.dita" navtitle="File Encoding" type="concept">
-</topicref>
-<topicref href="topics/tsrcedt007.dita" navtitle="Searching or finding text within a file"
-type="task"></topicref>
-<topicref href="topics/tsrcedt010.dita" navtitle="Checking spelling" type="task">
-</topicref>
-<topicref href="topics/tsrcedt027.dita" navtitle="Adding and removing markup language templates - overview"
-type="task">
-<topicref href="topics/tsrcedt024.dita" navtitle="Adding and removing HTML templates"
-type="task"></topicref>
-<topicref href="topics/tsrcedt028.dita" navtitle="Adding and removing JSP templates"
-type="task"></topicref>
-<topicref href="topics/tsrcedt029.dita" navtitle="Adding and removing XML templates"
-type="task"></topicref>
-</topicref>
-<topicref href="topics/tsrcedt026.dita" navtitle="Editing with snippets - overview"
-type="task">
-<topicref href="topics/csrcedt001.dita" navtitle="Snippets view" type="concept">
-</topicref>
-<topicref href="topics/tsrcedt014.dita" navtitle="Adding snippets drawers"
-type="task"></topicref>
-<topicref href="topics/tsrcedt015.dita" navtitle="Adding items to snippets drawers"
-type="task"></topicref>
-<topicref href="topics/tsrcedt022.dita" navtitle="Editing snippet items" type="task">
-</topicref>
-<topicref href="topics/tsrcedt016.dita" navtitle="Deleting or hiding snippet items or drawers"
-type="task"></topicref>
-</topicref>
-</topicref>
-</topicref>
-</map>
diff --git a/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml b/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml deleted file mode 100644 index 36f3b7fc15..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml +++ /dev/null @@ -1,42 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2001, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<toc label="Structured text editors" topics="topics/csrcedt004.html"> - <topic label="Structured text editors" href="topics/csrcedt004.html"> - <topic label="Editing text coded in markup languages " href="topics/tsrcedt000.html"> - <topic label="Source and batch validation" href="topics/cvalidate.html"/> - <topic label="Setting preferences for structured text editors" href="topics/tsrcedt025.html"> - <topic label="Setting annotation preferences for markup languages" href="topics/tsrcedt001.html"/> - </topic> - <topic label="Getting content assistance in structured text editors" href="topics/tsrcedt005.html"> - <topic label="Content assist" href="topics/csrcedt006.html"/> - <topic label="Making content assist work for JSP files" href="topics/tsrcedt023.html"/> - </topic> - <topic label="Associating editors with file types" href="topics/tcontenttype.html"/> - <topic label="File Encoding" href="topics/cencoding.html"/> - <topic label="Searching or finding text within a file" href="topics/tsrcedt007.html"/> - <topic label="Checking spelling" href="topics/tsrcedt010.html"/> - <topic label="Adding and removing markup language templates - overview" href="topics/tsrcedt027.html"> - <topic label="Adding and removing HTML templates" href="topics/tsrcedt024.html"/> - <topic label="Adding and removing JSP templates" href="topics/tsrcedt028.html"/> - <topic label="Adding and removing XML templates" href="topics/tsrcedt029.html"/> - </topic> - <topic label="Editing with snippets - overview" href="topics/tsrcedt026.html"> - <topic label="Snippets view" href="topics/csrcedt001.html"/> - <topic label="Adding snippets drawers" href="topics/tsrcedt014.html"/> - <topic label="Adding items to snippets drawers" href="topics/tsrcedt015.html"/> - <topic label="Editing snippet items" href="topics/tsrcedt022.html"/> - <topic label="Deleting or hiding snippet items or drawers" href="topics/tsrcedt016.html"/> - </topic> - </topic> - </topic> -</toc> diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.dita b/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.dita deleted file mode 100644 index c7a7322e8f..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.dita +++ /dev/null @@ -1,31 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "..\dtd\concept.dtd">
-<concept id="cencoding" xml:lang="en-us">
-<title>File Encoding</title>
-<shortdesc></shortdesc>
-<prolog><metadata>
-<keywords><indexterm>character encoding<indexterm>location in files</indexterm></indexterm>
-<indexterm>JSP files<indexterm>character encoding</indexterm></indexterm>
-<indexterm>XHTML<indexterm>character encoding</indexterm></indexterm>
-<indexterm>XML<indexterm>character encoding</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p> The character encoding in XML, (X)HTML files, and JSP files can be specified
-and invoked in many different ways; however, we recommend that you specify
-the encoding in each one of your source files, for that is where many XML,
-HTML, JSP editors expect to find the encoding.</p>
-<p>For example, for JSP files, you might use the pageEncoding attribute and/or
-the contentType attribute in the page directive, as shown in the following
-example:<codeblock><%@ page language="java" contentType="text/html; charset=ISO-8859-1"
- pageEncoding="ISO-8859-1"%>
-</codeblock></p>
-<p>For XML files, you might use the encoding pseudo-attribute in the xml declaration
-at the start of a document or the text declaration at the start of an entity,
-as in the following example: <codeblock><?xml version="1.0" encoding="iso-8859-1" ?></codeblock></p>
-<p>For (X)HTML files, you might use the <meta> tag inside the <head>
-tags, as shown in the following example:<codeblock><meta http-equiv="Content-Type" content="text/html;charset=utf-8" /></codeblock></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.html b/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.html deleted file mode 100644 index a63fabd6e9..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.html +++ /dev/null @@ -1,40 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2006 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>File Encoding</title> -</head> -<body id="cencoding"><a name="cencoding"><!-- --></a> -<h1 class="topictitle1">File Encoding</h1> -<div><p></p> -<p> The character encoding in XML, (X)HTML files, and JSP files can be specified -and invoked in many different ways; however, we recommend that you specify -the encoding in each one of your source files, for that is where many XML, -HTML, JSP editors expect to find the encoding.</p> -<div class="p">For example, for JSP files, you might use the pageEncoding attribute and/or -the contentType attribute in the page directive, as shown in the following -example:<pre><%@ page language="java" contentType="text/html; charset=ISO-8859-1" - pageEncoding="ISO-8859-1"%></pre> -</div> -<div class="p">For XML files, you might use the encoding pseudo-attribute in the xml declaration -at the start of a document or the text declaration at the start of an entity, -as in the following example: <pre><?xml version="1.0" encoding="iso-8859-1" ?></pre> -</div> -<div class="p">For (X)HTML files, you might use the <meta> tag inside the <head> -tags, as shown in the following example:<pre><meta http-equiv="Content-Type" content="text/html;charset=utf-8" /></pre> -</div> -</div> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.dita b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.dita deleted file mode 100644 index 7f85c95b4e..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.dita +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "..\dtd\concept.dtd">
-<concept id="csrcedt001" xml:lang="en-us">
-<title>Snippets view</title>
-<shortdesc>The Snippets view lets you catalog and organize reusable programming
-objects, such as HTML tagging, <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm>, and JSP code, along with
-files and custom JSP tags.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Snippets view<indexterm>overview</indexterm></indexterm>
-
-</keywords>
-</metadata></prolog>
-<conbody>
-<p> The Snippets view can be extended based on additional objects that you
-define and include. To view or collapse the objects in a specific drawer,
-click the drawer name.</p>
-<p>The Snippets view has the following features: <ul>
-<li>Drag-and-drop to various source editing pages: You can drag items from
-the view into the active editor and the text will be dropped into the document
-at the cursor location </li>
-<li>Double-click support: You can double-click on an item and have it inserted
-at the current cursor position in the active editor </li>
-<li>User-defined drawers and items: You can define, edit, and remove items
-from view drawers as desired.</li>
-<li>Plug-in-defined drawers and items: Plug-in developers can contribute a
-default list of items to their own drawers.</li>
-<li>Variables in insertions: By default, items will be edited using a dialog
-and, when inserted, you will be prompted for values for each of the variables.</li>
-<li>Customization: You can select which drawers and items are shown in the
-Snippets view.</li>
-<li>Custom insertion: Plug-in developers can customize the behavior of items
-so that when they are dropped during a drag-and-drop action, both the text
-that is inserted and the insertion location are strictly defined.</li>
-</ul></p>
-</conbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt026.dita"><linktext>Editing with snippets - overview</linktext>
-</link>
-<link href="tsrcedt014.dita"><linktext>Adding snippets drawers</linktext>
-</link>
-<link href="tsrcedt015.dita"><linktext>Adding items to snippets drawers</linktext>
-</link>
-<link href="tsrcedt022.dita"><linktext>Editing snippet items</linktext></link>
-<link href="tsrcedt016.dita"><linktext>Deleting or hiding snippet items or
-drawers</linktext></link>
-<link href="tsrcedt000.dita"></link>
-</linkpool>
-</related-links>
-</concept>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.html b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.html deleted file mode 100644 index a37e9dee9c..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt001.html +++ /dev/null @@ -1,89 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Snippets view" /> -<meta name="abstract" content="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags." /> -<meta name="description" content="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags." /> -<meta content="Snippets view, overview" name="DC.subject" /> -<meta content="Snippets view, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt026.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt014.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt015.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt022.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt016.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="csrcedt001" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Snippets view</title> -</head> -<body id="csrcedt001"><a name="csrcedt001"><!-- --></a> - - -<h1 class="topictitle1">Snippets view</h1> - - - -<div><p>The Snippets view lets you catalog and organize reusable programming -objects, such as HTML tagging, JavaScriptâ„¢, and JSP code, along with -files and custom JSP tags.</p> - -<p> The Snippets view can be extended based on additional objects that you -define and include. To view or collapse the objects in a specific drawer, -click the drawer name.</p> - -<div class="p">The Snippets view has the following features: <ul> -<li>Drag-and-drop to various source editing pages: You can drag items from -the view into the active editor and the text will be dropped into the document -at the cursor location </li> - -<li>Double-click support: You can double-click on an item and have it inserted -at the current cursor position in the active editor </li> - -<li>User-defined drawers and items: You can define, edit, and remove items -from view drawers as desired.</li> - -<li>Plug-in-defined drawers and items: Plug-in developers can contribute a -default list of items to their own drawers.</li> - -<li>Variables in insertions: By default, items will be edited using a dialog -and, when inserted, you will be prompted for values for each of the variables.</li> - -<li>Customization: You can select which drawers and items are shown in the -Snippets view.</li> - -<li>Custom insertion: Plug-in developers can customize the behavior of items -so that when they are dropped during a drag-and-drop action, both the text -that is inserted and the insertion location are strictly defined.</li> - -</ul> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a></div> -<div><a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a></div> -<div><a href="tsrcedt015.html" title="">Adding items to snippets drawers</a></div> -<div><a href="tsrcedt022.html" title="">Editing snippet items</a></div> -<div><a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or -drawers</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages - overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.dita b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.dita deleted file mode 100644 index de02cbe539..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.dita +++ /dev/null @@ -1,125 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "..\dtd\concept.dtd">
-<concept id="csrcedt004" xml:lang="en-us">
-<title>Structured text editors for markup languages</title>
-<titlealts>
-<navtitle>Structured text editors</navtitle>
-</titlealts>
-<shortdesc><q>Structured text editor</q> is any of several text editors that
-you can use to edit various markup languages such as HTML, JavaScript, or
-XML.</shortdesc>
-<prolog><metadata>
-<keywords><keyword>source editors</keyword></keywords>
-</metadata></prolog>
-<conbody>
-<p><indexterm>structured text editors<indexterm>overview</indexterm></indexterm>
-<indexterm>templates<indexterm>structured text editors</indexterm></indexterm>
-
-The structured text editor is represented by various editors that you can
-use to edit files coded with markup tags:</p>
-<table>
-<tgroup cols="3"><colspec colname="col1" colwidth="89*"/><colspec colname="col2"
-colwidth="134*"/><colspec colname="COLSPEC0" colwidth="69*"/>
-<thead>
-<row>
-<entry colname="col1" valign="top">File type</entry>
-<entry colname="col2" valign="top">Editor</entry>
-<entry colname="COLSPEC0" valign="top">Content assist?</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry colname="col1">Cascading style sheet</entry>
-<entry colname="col2">CSS source page editor</entry>
-<entry colname="COLSPEC0">Yes</entry>
-</row>
-<row>
-<entry colname="col1">Document type definitions</entry>
-<entry colname="col2">DTD source page editor</entry>
-<entry colname="COLSPEC0">No</entry>
-</row>
-<row>
-<entry colname="col1">HTML</entry>
-<entry colname="col2">HTML source page editor</entry>
-<entry colname="COLSPEC0">Yes</entry>
-</row>
-<row>
-<entry colname="col1"><tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm></entry>
-<entry colname="col2"><tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm> source page editor or source
-tab of JavaScript editor</entry>
-<entry colname="COLSPEC0">Yes</entry>
-</row>
-<row>
-<entry colname="col1">JSP</entry>
-<entry colname="col2">JSP source page editor</entry>
-<entry colname="COLSPEC0">Yes</entry>
-</row>
-<row>
-<entry colname="col1">XML</entry>
-<entry colname="col2">Source tab of XML editor</entry>
-<entry colname="COLSPEC0">Yes</entry>
-</row>
-<row>
-<entry colname="col1">XSD (schema)</entry>
-<entry colname="col2">Source tab of XML schema editor</entry>
-<entry colname="COLSPEC0">Yes</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-<p>You can access the structured text editor by right-clicking on a relevant
-file name in Navigator or Package Explorer view and then clicking <uicontrol>Open
-With</uicontrol> and selecting the editor mentioned above.</p>
-<p>The structured text editor provides a consistent interface regardless of
-the markup language with which it is associated. It provides capabilities
-such as find and replace, undo, redo, a spelling checker, and coding assistance
-(unless otherwise noted). It also highlights syntax in different colors. Following
-is a brief description of some of the structured text editor's capabilities:</p>
-<dl><dlentry>
-<dt>syntax highlighting</dt>
-<dd>Each keyword type and syntax type is highlighted differently, enabling
-you to easily find a certain kind of keyword for editing. For example, in
-HTML, element names, attribute names, attribute values, and comments have
-different colors; in <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm>, function and variable
-names, quoted text strings, and comments have different colors.</dd>
-</dlentry><dlentry>
-<dt>unlimited undo and redo</dt>
-<dd>These options allow you to incrementally undo and redo every change made
-to a file for the entire editing session. For text, changes are incremented
-one character or set of selected characters at a time.</dd>
-</dlentry><dlentry>
-<dt>content assist</dt>
-<dd>Content assist helps you to insert <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm> functions, HTML tags, or
-other keywords. Choices available in the content assist list are based on
-functions defined by the syntax of the language in which the file is coded.</dd>
-</dlentry><dlentry>
-<dt>user-defined templates and snippets</dt>
-<dd>By using the Snippets view, you can access user-defined code snippets
-and (for all code types except <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm>) templates to help you
-quickly add regularly used text strings.</dd>
-</dlentry><dlentry>
-<dt>function selection</dt>
-<dd>Based on the location of your cursor, the function or tag selection indicator
-highlights the line numbers that include a function or tag in the vertical
-ruler on the left area of the Source page.</dd>
-</dlentry><dlentry>
-<dt>pop-up menu options</dt>
-<dd>These are the same editing options available in the workbench <uicontrol>Edit</uicontrol> menu.</dd>
-</dlentry></dl>
-</conbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt006.dita"><linktext>Content assist</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt000.dita"></link>
-</linkpool>
-</related-links>
-</concept>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html deleted file mode 100644 index ec3d55efa7..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt004.html +++ /dev/null @@ -1,190 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Structured text editors for markup languages" /> -<meta name="abstract" content="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML." /> -<meta name="description" content="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML." /> -<meta content="source editors" name="DC.subject" /> -<meta content="source editors" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt006.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="csrcedt004" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Structured text editors for markup languages</title> -</head> -<body id="csrcedt004"><a name="csrcedt004"><!-- --></a> - - -<h1 class="topictitle1">Structured text editors for markup languages</h1> - - - - -<div><p><span class="q">"Structured text editor"</span> is any of several text editors that -you can use to edit various markup languages such as HTML, JavaScript, or -XML.</p> - -<p> - -The structured text editor is represented by various editors that you can -use to edit files coded with markup tags:</p> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<thead align="left"> -<tr> -<th valign="top" width="30.47945205479452%" id="N1008A">File type</th> - -<th valign="top" width="45.89041095890411%" id="N10092">Editor</th> - -<th valign="top" width="23.63013698630137%" id="N1009A">Content assist?</th> - -</tr> - -</thead> - -<tbody> -<tr> -<td valign="top" width="30.47945205479452%" headers="N1008A ">Cascading style sheet</td> - -<td valign="top" width="45.89041095890411%" headers="N10092 ">CSS source page editor</td> - -<td valign="top" width="23.63013698630137%" headers="N1009A ">Yes</td> - -</tr> - -<tr> -<td valign="top" width="30.47945205479452%" headers="N1008A ">Document type definitions</td> - -<td valign="top" width="45.89041095890411%" headers="N10092 ">DTD source page editor</td> - -<td valign="top" width="23.63013698630137%" headers="N1009A ">No</td> - -</tr> - -<tr> -<td valign="top" width="30.47945205479452%" headers="N1008A ">HTML</td> - -<td valign="top" width="45.89041095890411%" headers="N10092 ">HTML source page editor</td> - -<td valign="top" width="23.63013698630137%" headers="N1009A ">Yes</td> - -</tr> - -<tr> -<td valign="top" width="30.47945205479452%" headers="N1008A ">JavaScriptâ„¢</td> - -<td valign="top" width="45.89041095890411%" headers="N10092 ">JavaScript source page editor or source -tab of JavaScript editor</td> - -<td valign="top" width="23.63013698630137%" headers="N1009A ">Yes</td> - -</tr> - -<tr> -<td valign="top" width="30.47945205479452%" headers="N1008A ">JSP</td> - -<td valign="top" width="45.89041095890411%" headers="N10092 ">JSP source page editor</td> - -<td valign="top" width="23.63013698630137%" headers="N1009A ">Yes</td> - -</tr> - -<tr> -<td valign="top" width="30.47945205479452%" headers="N1008A ">XML</td> - -<td valign="top" width="45.89041095890411%" headers="N10092 ">Source tab of XML editor</td> - -<td valign="top" width="23.63013698630137%" headers="N1009A ">Yes</td> - -</tr> - -<tr> -<td valign="top" width="30.47945205479452%" headers="N1008A ">XSD (schema)</td> - -<td valign="top" width="45.89041095890411%" headers="N10092 ">Source tab of XML schema editor</td> - -<td valign="top" width="23.63013698630137%" headers="N1009A ">Yes</td> - -</tr> - -</tbody> - -</table> -</div> - -<p>You can access the structured text editor by right-clicking on a relevant -file name in Navigator or Package Explorer view and then clicking <span class="uicontrol">Open -With</span> and selecting the editor mentioned above.</p> - -<p>The structured text editor provides a consistent interface regardless of -the markup language with which it is associated. It provides capabilities -such as find and replace, undo, redo, a spelling checker, and coding assistance -(unless otherwise noted). It also highlights syntax in different colors. Following -is a brief description of some of the structured text editor's capabilities:</p> - -<dl> -<dt class="dlterm">syntax highlighting</dt> - -<dd>Each keyword type and syntax type is highlighted differently, enabling -you to easily find a certain kind of keyword for editing. For example, in -HTML, element names, attribute names, attribute values, and comments have -different colors; in JavaScript, function and variable -names, quoted text strings, and comments have different colors.</dd> - - -<dt class="dlterm">unlimited undo and redo</dt> - -<dd>These options allow you to incrementally undo and redo every change made -to a file for the entire editing session. For text, changes are incremented -one character or set of selected characters at a time.</dd> - - -<dt class="dlterm">content assist</dt> - -<dd>Content assist helps you to insert JavaScript functions, HTML tags, or -other keywords. Choices available in the content assist list are based on -functions defined by the syntax of the language in which the file is coded.</dd> - - -<dt class="dlterm">user-defined templates and snippets</dt> - -<dd>By using the Snippets view, you can access user-defined code snippets -and (for all code types except JavaScript) templates to help you -quickly add regularly used text strings.</dd> - - -<dt class="dlterm">function selection</dt> - -<dd>Based on the location of your cursor, the function or tag selection indicator -highlights the line numbers that include a function or tag in the vertical -ruler on the left area of the Source page.</dd> - - -<dt class="dlterm">pop-up menu options</dt> - -<dd>These are the same editing options available in the workbench <span class="uicontrol">Edit</span> menu.</dd> - -</dl> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt006.html" title="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion.">Content assist</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages - overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.dita b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.dita deleted file mode 100644 index 79203a5e58..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.dita +++ /dev/null @@ -1,115 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "..\dtd\concept.dtd">
-<concept id="csrcedt006" xml:lang="en-us">
-<title>Content assist</title>
-<shortdesc>Content assist helps you insert or finish a tag or function or
-finish a line of code in a structured text editor. The placement of the cursor
-in the source file provides the context for the content assist to offer suggestions
-for completion.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>content assistance<indexterm>overview</indexterm></indexterm>
-<indexterm>structured text editors<indexterm>content assistance</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>Most of the structured text editors have content assist. For a list of
-editors that have content assist, see <xref href="csrcedt004.dita" type="concept">Structured
-text editors for markup languages</xref>. For information on how to get content
-assistance, see <xref href="tsrcedt005.dita" type="task">Getting content assistance
-in structured text editors</xref></p>
-<p>The sections below describe specifics of HTML content assist, <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="JavaScript">JavaScript</tm> content
-assist, and JSP content assist.</p>
-<section><title>HTML content assist</title><p>HTML is flexible in that some
-HTML elements allow end tags to be optionally omitted, such as <codeph>P</codeph>, <codeph>DT</codeph>, <codeph>DD</codeph>, <codeph>LI</codeph>, <codeph
->THEAD</codeph>, <codeph>TR</codeph>, <codeph>TD</codeph>, <codeph>TH</codeph>,
-and so on. Other HTML elements that are defined to have no content may require
-the end tag always be omitted, such as <codeph>BR</codeph>, <codeph>HR</codeph>, <codeph>LINK</codeph>, <codeph>META</codeph>,
-and <codeph>IMG</codeph>. This flexibility makes the content assist function
-within the HTML source page editor less precise than it might be with a more
-rigidly constrained markup language.</p><p>HTML content assist is most beneficial
-when you need to complete a tag name, add an attribute name-value pair within
-a start tag, or select from an enumerated list of attribute values.</p><p>Although
-content assist only shows attribute names that have not already been specified
-in a start tag, it does not take into account grammar constraints for tags.
-For example, the <codeph>HEAD</codeph> element in HTML only permits zero or
-one occurrences of a <codeph>TITLE</codeph> tag in its content. If you prompt
-for content assist within a <codeph>HEAD</codeph> content that already contains
-a <codeph>TITLE</codeph> tag, content assist will still show <codeph>TITLE</codeph> in
-its proposal list.</p><p>However, if an attribute is required according to
-the DTD/Schema, that attribute will show up at the top of the list, with a
-yellow circle indicator on its icon.</p><p>If your cursor is in a position
-where content assist is available, a pop-up list of available choices is displayed.
-The list is based on the context. For example, if you use content assist directly
-after an opening paragraph tag (<codeph><p></codeph>) , the first item
-in the content assist list will be the corresponding closing paragraph (<codeph></p></codeph>)
-tag.</p><p>The content assist list displays all available tags for the current
-cursor position, including templates. The picture below shows the default
-content assist list for a paragraph tag example:<image alt="HTML Content assist"
-href="../images/ncontass.gif" placement="break"></image></p><p>Tag proposals
-are listed alphabetically. If you type a <codeph><</codeph> (to begin a
-new tag) before prompting for content assist, and begin typing the first one
-or two letters of the tag that you want to add, the proposal list automatically
-refreshes to reflect proposals that match the pattern you have typed. If you
-do not type a <codeph><</codeph> before prompting for content assist, you
-can click within the proposal list and then type the letter that the tag begins
-with, to reduce (somewhat) the amount of scrolling to locate the desired tag.</p><p>As
-you type the first one or two letters of the attribute names or enumerated
-attribute values that you want to add to a tag, the list automatically refreshes
-to reflect proposals that match the pattern you have typed.</p><note type="restriction"><image
-alt="For Linux." href="../images/nlinux.gif"></image> When using Linux (Motif
-or GTK) and a DBCS locale, double-clicking on the content assist list can
-sometimes cause the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> VM to terminate. Instead of double-clicking
-on the list, use the arrows and Enter keys to make the selection from the
-list.</note></section>
-<section><?Pub Caret1?><title>JSP content assist</title><p>You have many options
-for embedding <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> and HTML code in your JSP pages by using content
-assist.</p><p>All of the JSP tags are included both in the template list and
-in XML format (for example, <codeph><jsp:expression></codeph>). To add
-JSP scriptlet tags, for example, move the cursor to the appropriate position
-in the file and press Ctrl+Space to use content assist. Select <image alt="JSP scriptlet content assist"
-href="../images/nmacscrp.gif" placement="inline"></image> from the proposal
-list to insert <codeph><% %></codeph> in the document.</p><p>Scriptlets
-are inserted in a tag <codeph><% %></codeph>. For example: <codeblock><% System.currentTimeMillis() %></codeblock></p><p>This
-example will evaluate the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> statement to get the current time in
-milliseconds.</p><p>To have the result of the statement inserted in the file,
-put an equals sign (=) in the front of the statement. For example: <codeblock><b>This is the time : <%= System.currentTimeMillis()%></b></codeblock
-></p><p>When you are within a scriptlet you are writing pure <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> code.
-Therefore, content assist works exactly the same as it does for the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> editor.
-For example, if you request content assist after <codeph>System</codeph>,
-content assist displays a list of methods. <note><tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> content assist works only in a Web
-project, because it requires a buildpath to find the appropriate <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> classes.</note></p><p>There
-are also special tags such as useBean. For example: <codeblock><jsp:useBean id="useBean" class="java.lang.String"/></codeblock></p><p>The
-useBean tag enables you to create a bean called <codeph>aString</codeph> of
-type <codeph>String</codeph>. Then when you use content assist, this is recognized
-as a declared variable. For example, if you use content assist after <codeph>aString</codeph>,
-as follows:</p><p> <codeblock><% aString. %> </codeblock>the content assist
-list shows available methods. This is because <codeph>aString</codeph> has
-been declared as a bean of type String.</p><p>If you use content assist after
-the <codeph>a</codeph>, as follows: <codeblock><% a %> </codeblock>content
-assist knows that <codeph>aString</codeph> exists, and it is shown in the
-content assist list.</p></section>
-</conbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt005.dita"><linktext>Getting content assistance in structured
-text editors</linktext></link>
-<link href="tsrcedt024.dita"><linktext>Adding and removing HTML templates</linktext>
-</link>
-</linkpool>
-</related-links>
-</concept>
-<?Pub *0000008076?>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html b/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html deleted file mode 100644 index 1fc5f54e2f..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/csrcedt006.html +++ /dev/null @@ -1,148 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Content assist" /> -<meta name="abstract" content="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion." /> -<meta name="description" content="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion." /> -<meta content="content assist, overview, structured text editors" name="DC.subject" /> -<meta content="content assist, overview, structured text editors" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt005.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt024.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="csrcedt006" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Content assist</title> -</head> -<body id="csrcedt006"><a name="csrcedt006"><!-- --></a> - - -<h1 class="topictitle1">Content assist</h1> - - - -<div><p>Content assist helps you insert or finish a tag or function or -finish a line of code in a structured text editor. The placement of the cursor -in the source file provides the context for the content assist to offer suggestions -for completion.</p> - -<p>Most of the structured text editors have content assist. For a list of -editors that have content assist, see <a href="csrcedt004.html">Structured text editors for markup languages</a>. For information on how to get content -assistance, see <a href="tsrcedt005.html">Getting content assistance in structured text editors</a></p> - -<p>The sections below describe specifics of HTML content assist, JavaScriptâ„¢ content -assist, and JSP content assist.</p> - -<div class="section"><h4 class="sectiontitle">HTML content assist</h4><p>HTML is flexible in that some -HTML elements allow end tags to be optionally omitted, such as <samp class="codeph">P</samp>, <samp class="codeph">DT</samp>, <samp class="codeph">DD</samp>, <samp class="codeph">LI</samp>, <samp class="codeph">THEAD</samp>, <samp class="codeph">TR</samp>, <samp class="codeph">TD</samp>, <samp class="codeph">TH</samp>, -and so on. Other HTML elements that are defined to have no content may require -the end tag always be omitted, such as <samp class="codeph">BR</samp>, <samp class="codeph">HR</samp>, <samp class="codeph">LINK</samp>, <samp class="codeph">META</samp>, -and <samp class="codeph">IMG</samp>. This flexibility makes the content assist function -within the HTML source page editor less precise than it might be with a more -rigidly constrained markup language.</p> -<p>HTML content assist is most beneficial -when you need to complete a tag name, add an attribute name-value pair within -a start tag, or select from an enumerated list of attribute values.</p> -<p>Although -content assist only shows attribute names that have not already been specified -in a start tag, it does not take into account grammar constraints for tags. -For example, the <samp class="codeph">HEAD</samp> element in HTML only permits zero or -one occurrences of a <samp class="codeph">TITLE</samp> tag in its content. If you prompt -for content assist within a <samp class="codeph">HEAD</samp> content that already contains -a <samp class="codeph">TITLE</samp> tag, content assist will still show <samp class="codeph">TITLE</samp> in -its proposal list.</p> -<p>However, if an attribute is required according to -the DTD/Schema, that attribute will show up at the top of the list, with a -yellow circle indicator on its icon.</p> -<p>If your cursor is in a position -where content assist is available, a pop-up list of available choices is displayed. -The list is based on the context. For example, if you use content assist directly -after an opening paragraph tag (<samp class="codeph"><p></samp>) , the first item -in the content assist list will be the corresponding closing paragraph (<samp class="codeph"></p></samp>) -tag.</p> -<p>The content assist list displays all available tags for the current -cursor position, including templates. The picture below shows the default -content assist list for a paragraph tag example:<br /><img src="../images/ncontass.gif" alt="HTML Content assist" /><br /></p> -<p>Tag proposals -are listed alphabetically. If you type a <samp class="codeph"><</samp> (to begin a -new tag) before prompting for content assist, and begin typing the first one -or two letters of the tag that you want to add, the proposal list automatically -refreshes to reflect proposals that match the pattern you have typed. If you -do not type a <samp class="codeph"><</samp> before prompting for content assist, you -can click within the proposal list and then type the letter that the tag begins -with, to reduce (somewhat) the amount of scrolling to locate the desired tag.</p> -<p>As -you type the first one or two letters of the attribute names or enumerated -attribute values that you want to add to a tag, the list automatically refreshes -to reflect proposals that match the pattern you have typed.</p> -<div class="restriction"><span class="restrictiontitle">Restriction:</span> <img src="../images/nlinux.gif" alt="For Linux." /> When using Linux (Motif -or GTK) and a DBCS locale, double-clicking on the content assist list can -sometimes cause the Javaâ„¢ VM to terminate. Instead of double-clicking -on the list, use the arrows and Enter keys to make the selection from the -list.</div> -</div> - -<div class="section"><h4 class="sectiontitle">JSP content assist</h4><p>You have many options for embedding Java and -HTML code in your JSP pages by using content assist.</p> -<p>All of the JSP -tags are included both in the template list and in XML format (for example, <samp class="codeph"><jsp:expression></samp>). -To add JSP scriptlet tags, for example, move the cursor to the appropriate -position in the file and press Ctrl+Space to use content assist. Select <img src="../images/nmacscrp.gif" alt="JSP scriptlet content assist" /> from the proposal list to insert <samp class="codeph"><% %></samp> in the -document.</p> -<div class="p">Scriptlets are inserted in a tag <samp class="codeph"><% %></samp>. -For example: <pre><% System.currentTimeMillis() %></pre> -</div> -<p>This -example will evaluate the Java statement to get the current time in -milliseconds.</p> -<div class="p">To have the result of the statement inserted in the file, -put an equals sign (=) in the front of the statement. For example: <pre><b>This is the time : <%= System.currentTimeMillis()%></b></pre> -</div> -<div class="p">When you are within a scriptlet you are writing pure Java code. -Therefore, content assist works exactly the same as it does for the Java editor. -For example, if you request content assist after <samp class="codeph">System</samp>, -content assist displays a list of methods. <div class="note"><span class="notetitle">Note:</span> Java content assist works only in a Web -project, because it requires a buildpath to find the appropriate Java classes.</div> -</div> -<div class="p">There -are also special tags such as useBean. For example: <pre><jsp:useBean id="useBean" class="java.lang.String"/></pre> -</div> -<p>The -useBean tag enables you to create a bean called <samp class="codeph">aString</samp> of -type <samp class="codeph">String</samp>. Then when you use content assist, this is recognized -as a declared variable. For example, if you use content assist after <samp class="codeph">aString</samp>, -as follows:</p> -<div class="p"> <pre><% aString. %> </pre> -the content assist -list shows available methods. This is because <samp class="codeph">aString</samp> has -been declared as a bean of type String.</div> -<div class="p">If you use content assist after -the <samp class="codeph">a</samp>, as follows: <pre><% a %> </pre> -content -assist knows that <samp class="codeph">aString</samp> exists, and it is shown in the -content assist list.</div> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt005.html" title="To get help in adding markup to a file, you can use content assist in a structured text editor. Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor.">Getting content assistance in structured -text editors</a></div> -<div><a href="tsrcedt024.html" title="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing HTML templates</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.dita b/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.dita deleted file mode 100644 index 7f9287b4f5..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.dita +++ /dev/null @@ -1,48 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "..\dtd\concept.dtd">
-<concept id="csrcedt001" xml:lang="en-us">
-<title>Source and batch validation</title>
-<shortdesc></shortdesc>
-<prolog><metadata>
-<keywords><indexterm>validation<indexterm>source vs batch</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>There are two types of validation that can occur when you are working with
-source files in a structured source editor: source validation and batch validation. </p>
-<p>Source validation occurs as you type your code; this validation reflects
-the "unsaved" and "unbuilt" contents of the source you are editing. For example,
-if you were to type the following code in a JSP editor:<lines><codeph><foo:bar></codeph></lines>where <codeph>foo:bar</codeph>is
-a tag that does not exist, the problem would be discovered immediately and
-would appear underlined in the editor. The advantage of this type of validation
-is that it can alert you to errors instantly.<note>To turn source validation
-on (or off) for all structured text editors, click <menucascade><uicontrol>Window</uicontrol>
-<uicontrol>Preferences</uicontrol><uicontrol>General</uicontrol><uicontrol>Editors</uicontrol>
-<uicontrol>Structured Text Editors</uicontrol></menucascade> and check (or
-uncheck) <b>Report problems as you type</b>.</note></p>
-<p>Batch validation occurs on saved files. It can catch build process errors
-and other errors that the source validator cannot. For example, suppose you
-typed the following in a JSP editor:<lines>
-<codeph><%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
-<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%></codeph></lines>In
-this example, the same prefix is used twice. This would prompt the batch validator
-to trigger markers and to generate build warnings in the Problems view and
-in the Navigator. </p>
-<p>Batch validation can uncover errors in multiple files at once and give
-you a comprehensive view of where problematic code can be found in your project.
-Moreover, you do not need to open files in an editor to run batch validation.
-To run batch validation on specific files, select and right click the files
-in the Project Explorer and then select <menucascade><uicontrol>Run Validation</uicontrol>
-</menucascade> from the popup menu.</p>
-<note>To set preferences for batch validation, click <menucascade><uicontrol>Window</uicontrol>
-<uicontrol>Preferences</uicontrol><uicontrol>Validation</uicontrol></menucascade></note>
-</conbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-</related-links>
-</concept>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.html b/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.html deleted file mode 100644 index 05fe0f2111..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.html +++ /dev/null @@ -1,54 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2006 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>Source and batch validation</title> -</head> -<body id="csrcedt001"><a name="csrcedt001"><!-- --></a> -<h1 class="topictitle1">Source and batch validation</h1> -<div><p></p> -<p>There are two types of validation that can occur when you are working with -source files in a structured source editor: source validation and batch validation. </p> -<div class="p">Source validation occurs as you type your code; this validation reflects -the "unsaved" and "unbuilt" contents of the source you are editing. For example, -if you were to type the following code in a JSP editor:<p><samp class="codeph"><foo:bar></samp></p> -where <samp class="codeph">foo:bar</samp>is -a tag that does not exist, the problem would be discovered immediately and -would appear underlined in the editor. The advantage of this type of validation -is that it can alert you to errors instantly.<div class="note"><span class="notetitle">Note:</span> To turn source validation -on (or off) for all structured text editors, click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">General</span> > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editors</span></span> and check (or -uncheck) <strong>Report problems as you type</strong>.</div> -</div> -<div class="p">Batch validation occurs on saved files. It can catch build process errors -and other errors that the source validator cannot. For example, suppose you -typed the following in a JSP editor:<p><samp class="codeph"><%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%><br /> -<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%></samp></p> -In -this example, the same prefix is used twice. This would prompt the batch validator -to trigger markers and to generate build warnings in the Problems view and -in the Navigator. </div> -<p>Batch validation can uncover errors in multiple files at once and give -you a comprehensive view of where problematic code can be found in your project. -Moreover, you do not need to open files in an editor to run batch validation. -To run batch validation on specific files, select and right click the files -in the Project Explorer and then select <span class="menucascade"><span class="uicontrol">Run Validation</span></span> from the popup menu.</p> -<div class="note"><span class="notetitle">Note:</span> To set preferences for batch validation, click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Validation</span></span></div> -</div> -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -</div></body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.dita deleted file mode 100644 index c63d1e14b6..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.dita +++ /dev/null @@ -1,32 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tcontenttype" xml:lang="en-us">
-<title>Associating editors with additional files types</title>
-<shortdesc></shortdesc>
-<prolog><metadata>
-<keywords><indexterm>content types<indexterm>mapping file extensions</indexterm></indexterm>
-<indexterm>file extensions<indexterm>mapping content types</indexterm></indexterm>
-<indexterm>file types<indexterm>editors</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>You can associate certain editors with a file type by clicking
-on <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>General</uicontrol><uicontrol>Editors</uicontrol><uicontrol>File
-Association</uicontrol></menucascade> and setting up the associations in the
-File Associations Window.</p><p>Some Eclipse-based editors, however, will
-only recognize a file based on the contents of the file. Consequently, if
-you want to associate an additional file type with some editors, you may have
-to first map the content type with its file extension. To map a content type
-with a file extension, complete the following steps: </p><ol>
-<li>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>General</uicontrol>
-<uicontrol>Content Types</uicontrol></menucascade>. The Content Type window
-appears. </li>
-<li>Select a content type in the Content Type window, and then select <b>Add</b> .
-The Define a New File Type window appears.</li>
-<li>Type the name of the file type, and then click <b>OK</b>.</li>
-</ol></context>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.html b/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.html deleted file mode 100644 index ae9df239fa..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.html +++ /dev/null @@ -1,40 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2006 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>Associating editors with additional files types</title> -</head> -<body id="tcontenttype"><a name="tcontenttype"><!-- --></a> -<h1 class="topictitle1">Associating editors with additional files types</h1> -<div><p></p> -<div class="section"><p>You can associate certain editors with a file type by clicking -on <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">General</span> > <span class="uicontrol">Editors</span> > <span class="uicontrol">File -Association</span></span> and setting up the associations in the -File Associations Window.</p> -<p>Some Eclipse-based editors, however, will -only recognize a file based on the contents of the file. Consequently, if -you want to associate an additional file type with some editors, you may have -to first map the content type with its file extension. To map a content type -with a file extension, complete the following steps: </p> -<ol><li>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">General</span> > <span class="uicontrol">Content Types</span></span>. The Content Type window -appears. </li> -<li>Select a content type in the Content Type window, and then select <strong>Add</strong> . -The Define a New File Type window appears.</li> -<li>Type the name of the file type, and then click <strong>OK</strong>.</li> -</ol> -</div> -</div> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.dita deleted file mode 100644 index 42b7b97f48..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.dita +++ /dev/null @@ -1,52 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt000" xml:lang="en-us">
-<title>Editing text coded in markup languages - overview</title>
-<titlealts>
-<navtitle>Editing markup languages - overview</navtitle>
-</titlealts>
-<shortdesc>You can edit text coded in markup languages with a <term>structured
-text editor</term>. This is a generic term for several editors that you can
-use to edit any of several markup languages, such as HTML.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>markup languages<indexterm>editing text</indexterm></indexterm>
-<indexterm>text<indexterm>editing in markup languages</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>In addition to basic editing tasks such as adding, modifying, and
-deleting text, you can perform the following tasks:</context>
-<steps-unordered>
-<step><cmd><xref href="tsrcedt025.dita" type="task">Set preferences for structured
-text editors</xref></cmd></step>
-<step><cmd><xref href="tsrcedt005.dita" type="task">Get content assistance
-in structured text editors</xref></cmd></step>
-<step><cmd><xref href="tsrcedt007.dita" type="task">Search or find text within
-a file</xref></cmd></step>
-<step><cmd><xref href="tsrcedt010.dita" type="task">Check spelling</xref></cmd>
-</step>
-<step><cmd><xref href="tsrcedt027.dita" type="task">Add or remove markup language
-templates</xref></cmd></step>
-<step><cmd><xref href="tsrcedt026.dita" type="task">Edit with snippets</xref></cmd>
-</step>
-</steps-unordered>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-<link href="csrcedt006.dita"><linktext>Content assist</linktext></link>
-<link href="csrcedt001.dita"><linktext>Snippets view</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt025.dita"></link>
-<link href="tsrcedt005.dita"></link>
-<link href="tsrcedt007.dita"></link>
-<link href="tsrcedt010.dita"></link>
-<link href="tsrcedt027.dita"></link>
-<link href="tsrcedt026.dita"></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html deleted file mode 100644 index e38d4f102e..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html +++ /dev/null @@ -1,82 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing text coded in markup languages - overview" /> -<meta name="abstract" content="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML." /> -<meta name="description" content="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML." /> -<meta content="markup languages, editing, structured text editors, markup language editing, overview" name="DC.subject" /> -<meta content="markup languages, editing, structured text editors, markup language editing, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt006.html" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt001.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt025.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt005.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt007.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt010.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt027.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt026.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt000" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing text coded in markup languages - overview</title> -</head> -<body id="tsrcedt000"><a name="tsrcedt000"><!-- --></a> - - -<h1 class="topictitle1">Editing text coded in markup languages - overview</h1> - - - - -<div><p>You can edit text coded in markup languages with a <dfn class="term">structured -text editor</dfn>. This is a generic term for several editors that you can -use to edit any of several markup languages, such as HTML.</p> - -<div class="section">In addition to basic editing tasks such as adding, modifying, and -deleting text, you can perform the following tasks:</div> - -<ul> -<li><span><a href="tsrcedt025.html">Set preferences for structured text editors</a></span></li> - -<li><span><a href="tsrcedt005.html">Get content assistance in structured text editors</a></span></li> - -<li><span><a href="tsrcedt007.html">Search or find text within a file</a></span></li> - -<li><span><a href="tsrcedt010.html">Check spelling</a></span> -</li> - -<li><span><a href="tsrcedt027.html">Add or remove markup language templates</a></span></li> - -<li><span><a href="tsrcedt026.html">Edit with snippets</a></span> -</li> - -</ul> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -<div><a href="csrcedt006.html" title="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion.">Content assist</a></div> -<div><a href="csrcedt001.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags.">Snippets view</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt025.html" title="">Setting preferences for structured text editors</a></div> -<div><a href="tsrcedt005.html" title="To get help in adding markup to a file, you can use content assist in a structured text editor. Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor.">Getting content assistance in structured text editors</a></div> -<div><a href="tsrcedt007.html" title="">Searching or finding text within a file</a></div> -<div><a href="tsrcedt010.html" title="This documentation describes how to check spelling in a structured text editor.">Checking spelling</a></div> -<div><a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language templates - overview</a></div> -<div><a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.dita deleted file mode 100644 index 471b837b5d..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.dita +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt001" xml:lang="en-us">
-<title>Setting annotation preferences for markup languages</title>
-<titlealts>
-<navtitle>Setting annotation preferences</navtitle>
-</titlealts>
-<shortdesc>This documentation describes how to set <term>annotation preferences</term> for
-Web and XML files. The annotation preferences include whether to analyze the
-syntactic validity of your file while you are typing and what colors to use
-to highlight errors, warnings, tasks, search results, bookmarks, and other
-text.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>annotation preferences<indexterm>markup language settings</indexterm></indexterm><indexterm>markup languages<indexterm>setting annotation preferences</indexterm></indexterm>
-
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>By default, when you edit in a structured text editor, your source
-code is validated as you type it in. Like other Eclipse-based editors, the
-structured text editors for markup languages flag warnings and errors in the
-source code in the editor area. The warnings and errors also show up in the
-Tasks view when you save the file.</p><note>Highlighting is fully dynamic
-with the exception of search results. Search results are highlighted based
-upon what has been saved to disk.</note><note type="tip">You can improve a
-structured text editor's performance by turning off the real-time validation.</note><p>To
-set annotation preferences, complete the following steps:</p> </context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-</menucascade>.</cmd><stepresult>A Preferences window appears.</stepresult>
-</step>
-<step><cmd>In the Preferences window, click <menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Editors</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Select one of the following options:</cmd>
-<choices>
-<choice>To turn off real-time syntax validation, click <uicontrol>Structured
-Text Editor</uicontrol> and uncheck the <uicontrol>Analyze annotations while
-typing</uicontrol> box.</choice>
-<choice>To control other annotation settings, click <uicontrol>Annotations</uicontrol> and
-select your annotation preferences.</choice>
-</choices>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to save your preferences and close
-the page.</cmd></step>
-</steps>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt025.dita"><linktext>Setting preferences for structured
-text editors</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html deleted file mode 100644 index b069e85dfa..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt001.html +++ /dev/null @@ -1,91 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting annotation preferences for markup languages" /> -<meta name="abstract" content="This documentation describes how to set annotation preferences for Web and XML files. The annotation preferences include whether to analyze the syntactic validity of your file while you are typing and what colors to use to highlight errors, warnings, tasks, search results, bookmarks, and other text." /> -<meta name="description" content="This documentation describes how to set annotation preferences for Web and XML files. The annotation preferences include whether to analyze the syntactic validity of your file while you are typing and what colors to use to highlight errors, warnings, tasks, search results, bookmarks, and other text." /> -<meta content="annotation preferences, markup language settings, markup languages, setting annotation preferences" name="DC.subject" /> -<meta content="annotation preferences, markup language settings, markup languages, setting annotation preferences" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt025.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt001" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting annotation preferences for markup languages</title> -</head> -<body id="tsrcedt001"><a name="tsrcedt001"><!-- --></a> - - -<h1 class="topictitle1">Setting annotation preferences for markup languages</h1> - - - - -<div><p>This documentation describes how to set <dfn class="term">annotation preferences</dfn> for -Web and XML files. The annotation preferences include whether to analyze the -syntactic validity of your file while you are typing and what colors to use -to highlight errors, warnings, tasks, search results, bookmarks, and other -text.</p> - -<div class="section"> <p>By default, when you edit in a structured text editor, your source -code is validated as you type it in. Like other Eclipse-based editors, the -structured text editors for markup languages flag warnings and errors in the -source code in the editor area. The warnings and errors also show up in the -Tasks view when you save the file.</p> -<div class="note"><span class="notetitle">Note:</span> Highlighting is fully dynamic -with the exception of search results. Search results are highlighted based -upon what has been saved to disk.</div> -<div class="tip"><span class="tiptitle">Tip:</span> You can improve a -structured text editor's performance by turning off the real-time validation.</div> -<p>To -set annotation preferences, complete the following steps:</p> - </div> - -<ol> -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> -</span>.</span> A Preferences window appears. -</li> - -<li class="stepexpand"><span>In the Preferences window, click <span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Editors</span></span>.</span></li> - -<li class="stepexpand"><span>Select one of the following options:</span> -<ul> -<li>To turn off real-time syntax validation, click <span class="uicontrol">Structured -Text Editor</span> and uncheck the <span class="uicontrol">Analyze annotations while -typing</span> box.</li> - -<li>To control other annotation settings, click <span class="uicontrol">Annotations</span> and -select your annotation preferences.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span> to save your preferences and close -the page.</span></li> - -</ol> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt025.html" title="">Setting preferences for structured -text editors</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.dita deleted file mode 100644 index 958f2eecb1..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.dita +++ /dev/null @@ -1,68 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt005" xml:lang="en-us">
-<title>Getting content assistance in structured text editors</title>
-<!--Formerly "Using JavaScript content assist"; moved some JavaScript-specific content to csrcedt006.dita ("Content assist")-->
-<titlealts>
-<navtitle>Getting content assistance</navtitle>
-</titlealts>
-<shortdesc>To get help in adding markup to a file, you can use content assist
-in a structured text editor. Content assist helps you insert or finish a tag
-or function or finish a line of code in a structured text editor.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>content assistance<indexterm>structured text editors</indexterm></indexterm>
-<indexterm>structured text editors<indexterm>content assistance</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>Content assist also enables you to select and insert templates in
-structured text editors. The placement of the cursor in the source file provides
-the context for the content assist to offer suggestions for completion.</context>
-<steps-unordered>
-<step><cmd></cmd><info>You can request content assist in either of the following
-two ways:</info>
-<choices>
-<choice>From the <uicontrol>Edit</uicontrol> menu, select <uicontrol>Content
-Assist</uicontrol></choice>
-<choice>Press Ctrl+Space</choice>
-</choices>
-<info><p>In addition, you can set a preference that causes content assist
-to pop up automatically when certain characters are typed, such as <codeph>.</codeph> in
-the case of <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="JavaScript">JavaScript</tm> or <codeph><</codeph> in the case
-of HTML and XML. To set this preference, select <uicontrol>Preferences</uicontrol> from
-the <uicontrol>Window</uicontrol> menu, and then select <uicontrol>Web and
-XML Files</uicontrol>, followed by one of the following sequences:<ul>
-<li><menucascade><uicontrol>HTML Files</uicontrol><uicontrol>HTML Source</uicontrol>
-</menucascade></li>
-<li><menucascade><uicontrol>JavaScript Files</uicontrol><uicontrol>JavaScript
-Source</uicontrol></menucascade></li>
-<li><menucascade><uicontrol>XML Files</uicontrol><uicontrol>XML Source</uicontrol>
-</menucascade></li>
-</ul>In the <uicontrol>Content assist</uicontrol> group box, select the <uicontrol>Automatically
-make suggestions</uicontrol> check box, and supply any additional characters
-that should trigger content assist.</p><p>If your cursor is in a position
-where content assist is available, a pop-up list of all available choices
-is displayed. For each of these choices, a brief description of the code is
-provided.</p></info></step>
-</steps-unordered>
-</taskbody>
-<related-links>
-<!-- <link href="contentassist" type="showme" format="viewlet"><linktext>Show Me</linktext></link> -->
-<linkpool type="concept">
-<link href="csrcedt006.dita"><linktext>Content assist</linktext></link>
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt023.dita"><linktext>Making content assist work for JSP
-files</linktext></link>
-<link href="tsrcedt027.dita"><linktext>Adding and removing markup language
-templates - overview</linktext></link>
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html deleted file mode 100644 index 39640bd7eb..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html +++ /dev/null @@ -1,99 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Getting content assistance in structured text editors" /> -<meta name="abstract" content="To get help in adding markup to a file, you can use content assist in a structured text editor. Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor." /> -<meta name="description" content="To get help in adding markup to a file, you can use content assist in a structured text editor. Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor." /> -<meta content="content assist, structured text editors" name="DC.subject" /> -<meta content="content assist, structured text editors" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt006.html" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt023.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt027.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt005" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Getting content assistance in structured text editors</title> -</head> -<body id="tsrcedt005"><a name="tsrcedt005"><!-- --></a> - - -<h1 class="topictitle1">Getting content assistance in structured text editors</h1> - - - - - -<div><p>To get help in adding markup to a file, you can use content assist -in a structured text editor. Content assist helps you insert or finish a tag -or function or finish a line of code in a structured text editor.</p> - -<div class="section">Content assist also enables you to select and insert templates in -structured text editors. The placement of the cursor in the source file provides -the context for the content assist to offer suggestions for completion.</div> - - -<div class="p"><span /> You can request content assist in either of the following -two ways: -<ul> -<li>From the <span class="uicontrol">Edit</span> menu, select <span class="uicontrol">Content -Assist</span></li> - -<li>Press Ctrl+Space</li> - -</ul> - - <div class="p">In addition, you can set a preference that causes content assist -to pop up automatically when certain characters are typed, such as <samp class="codeph">.</samp> in -the case of JavaScriptâ„¢ or <samp class="codeph"><</samp> in the case -of HTML and XML. To set this preference, select <span class="uicontrol">Preferences</span> from -the <span class="uicontrol">Window</span> menu, and then select <span class="uicontrol">Web and -XML Files</span>, followed by one of the following sequences:<ul> -<li><span class="menucascade"><span class="uicontrol">HTML Files</span> > <span class="uicontrol">HTML Source</span> -</span></li> - -<li><span class="menucascade"><span class="uicontrol">JavaScript Files</span> > <span class="uicontrol">JavaScript -Source</span></span></li> - -<li><span class="menucascade"><span class="uicontrol">XML Files</span> > <span class="uicontrol">XML Source</span> -</span></li> - -</ul> -In the <span class="uicontrol">Content assist</span> group box, select the <span class="uicontrol">Automatically -make suggestions</span> check box, and supply any additional characters -that should trigger content assist.</div> -<p>If your cursor is in a position -where content assist is available, a pop-up list of all available choices -is displayed. For each of these choices, a brief description of the code is -provided.</p> -</div> - - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt006.html" title="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion.">Content assist</a></div> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt023.html" title="Having the proper files defined in the Java build class path is essential for content assist to work properly in JSP files. It is also essential for the links builder to be able to correctly resolve links to servlets or Java beans in JSP and HTML files.">Making content assist work for JSP -files</a></div> -<div><a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language -templates - overview</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.dita deleted file mode 100644 index 38aa8b613c..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt007" xml:lang="en-us">
-<title>Searching or finding text within a file</title>
-<prolog><metadata>
-<keywords><indexterm>structured text editors<indexterm>text search</indexterm></indexterm>
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<prereq><note type="tip">Before you do a Search operation in a structured
-text editor, save the file you are searching. The search function works from
-the most recently saved version of the file rather than from the contents
-that you see in the editor area. You do not need to save your file before
-you do a Find/Replace operation. </note></prereq>
-<context>Each structured text editor provides two ways to locate a text string
-in the file you are editing and optionally replace it with another string: <dl>
-<dlentry>
-<dt>Find/Replace</dt>
-<dd>Lets you locate text in the file currently being edited.</dd>
-</dlentry><dlentry>
-<dt>Search</dt>
-<dd>Lets you locate text in files that have been saved to your workspace.</dd>
-</dlentry></dl><p>To locate and optionally replace text, select one of the
-following menu paths:</p></context>
-<steps-unordered>
-<step><cmd><menucascade><uicontrol>Edit</uicontrol><uicontrol>Find/Replace</uicontrol>
-</menucascade> (or <uicontrol>Ctrl+F</uicontrol>)</cmd><info>This option is
-self-explanatory.</info></step>
-</steps-unordered>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html deleted file mode 100644 index 3c6a789633..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt007.html +++ /dev/null @@ -1,72 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Searching or finding text within a file" /> -<meta content="structured text editors, text search" name="DC.subject" /> -<meta content="structured text editors, text search" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt007" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Searching or finding text within a file</title> -</head> -<body id="tsrcedt007"><a name="tsrcedt007"><!-- --></a> - - -<h1 class="topictitle1">Searching or finding text within a file</h1> - - -<div> -<div class="p"><div class="tip"><span class="tiptitle">Tip:</span> Before you do a Search operation in a structured -text editor, save the file you are searching. The search function works from -the most recently saved version of the file rather than from the contents -that you see in the editor area. You do not need to save your file before -you do a Find/Replace operation. </div> -</div> - -<div class="section">Each structured text editor provides two ways to locate a text string -in the file you are editing and optionally replace it with another string: <dl> - -<dt class="dlterm">Find/Replace</dt> - -<dd>Lets you locate text in the file currently being edited.</dd> - - -<dt class="dlterm">Search</dt> - -<dd>Lets you locate text in files that have been saved to your workspace.</dd> - -</dl> -<p>To locate and optionally replace text, select one of the -following menu paths:</p> -</div> - - -<div class="p"><span><span class="menucascade"><span class="uicontrol">Edit</span> > <span class="uicontrol">Find/Replace</span> -</span> (or <span class="uicontrol">Ctrl+F</span>)</span> This option is -self-explanatory.</div> - - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.dita deleted file mode 100644 index 4ac6d01c35..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.dita +++ /dev/null @@ -1,51 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt010" xml:lang="en-us">
-<title>Checking spelling</title>
-<shortdesc>This documentation describes how to check spelling in a structured
-text editor.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>spell check<indexterm>structured text editors</indexterm></indexterm><indexterm>structured text editors<indexterm>spell check</indexterm></indexterm>
-
-
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>The structured text editors for markup languages (accessed from
-the Project Explorer's pop-up menu or by clicking the Source tab in certain
-editors) provide a spell checking feature.</p><p>To check spelling in an HTML,
-XML, or other file that uses a structured markup language:</p> </context>
-<steps>
-<step><cmd>(Optional) To select the dictionary that will be used, click <menucascade>
-<uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol><uicontrol>Spell
-Check</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Open in a structured text editor the file whose spelling you want
-to check.</cmd></step>
-<step><cmd>Start the spelling checker by clicking <menucascade><uicontrol>Edit</uicontrol>
-<uicontrol>Spell Check</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Type a new spelling into the <uicontrol>Change to</uicontrol> field,
-or select one of the available options. Click the <uicontrol>Change</uicontrol> button
-to change the current instance of the word in the current document. Click
-the <uicontrol>Change All</uicontrol> button to change all instances of the
-word in the current document. You can also click the <uicontrol>Add</uicontrol> button
-to add the currently selected spelling to your dictionary.</cmd></step>
-<step><cmd>Use the controls in the Spell Check dialog box to ignore, change,
-or add terms to the current dictionary. (To remove a word after it has been
-added to the dictionary, click the <uicontrol>Dictionary</uicontrol> push
-button.)</cmd></step>
-</steps>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html deleted file mode 100644 index 0df273203c..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt010.html +++ /dev/null @@ -1,79 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Checking spelling" /> -<meta name="abstract" content="This documentation describes how to check spelling in a structured text editor." /> -<meta name="description" content="This documentation describes how to check spelling in a structured text editor." /> -<meta content="spell check, structured text editors" name="DC.subject" /> -<meta content="spell check, structured text editors" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt010" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Checking spelling</title> -</head> -<body id="tsrcedt010"><a name="tsrcedt010"><!-- --></a> - - -<h1 class="topictitle1">Checking spelling</h1> - - - -<div><p>This documentation describes how to check spelling in a structured -text editor.</p> - -<div class="section"> <p>The structured text editors for markup languages (accessed from -the Project Explorer's pop-up menu or by clicking the Source tab in certain -editors) provide a spell checking feature.</p> -<p>To check spelling in an HTML, -XML, or other file that uses a structured markup language:</p> - </div> - -<ol> -<li><span>(Optional) To select the dictionary that will be used, click <span class="menucascade"> -<span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> > <span class="uicontrol">Spell -Check</span></span>.</span></li> - -<li><span>Open in a structured text editor the file whose spelling you want -to check.</span></li> - -<li><span>Start the spelling checker by clicking <span class="menucascade"><span class="uicontrol">Edit</span> - > <span class="uicontrol">Spell Check</span></span>.</span></li> - -<li><span>Type a new spelling into the <span class="uicontrol">Change to</span> field, -or select one of the available options. Click the <span class="uicontrol">Change</span> button -to change the current instance of the word in the current document. Click -the <span class="uicontrol">Change All</span> button to change all instances of the -word in the current document. You can also click the <span class="uicontrol">Add</span> button -to add the currently selected spelling to your dictionary.</span></li> - -<li><span>Use the controls in the Spell Check dialog box to ignore, change, -or add terms to the current dictionary. (To remove a word after it has been -added to the dictionary, click the <span class="uicontrol">Dictionary</span> push -button.)</span></li> - -</ol> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.dita deleted file mode 100644 index ce2bb1dcbc..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.dita +++ /dev/null @@ -1,53 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt014" xml:lang="en-us">
-<title>Adding snippets drawers</title>
-<shortdesc>This documentation explains how to customize the Snippets view
-by adding a new drawer.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>snippets<indexterm>drawer customization</indexterm></indexterm>
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>To add a new drawer to the Snippets view:</context>
-<steps>
-<step><cmd>Right-click anywhere in the Snippets view and select <uicontrol>Customize</uicontrol> from
-the pop-up menu.</cmd></step>
-<step><cmd>Click <menucascade><uicontrol>New</uicontrol><uicontrol>Category</uicontrol>
-</menucascade> and type the name of the new drawer in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>Optionally, type a description in the <uicontrol>Description</uicontrol> field.</cmd>
-</step>
-<step><cmd>Select the drawer's behavior by checking check boxes as appropriate.
-The check boxes are as follows:</cmd>
-<choicetable>
-<chrow><choption>Hide</choption><chdesc>Do not display the drawer.</chdesc>
-</chrow>
-<chrow><choption>Open drawer at start-up</choption><chdesc>At start-up, display
-the drawer's items.</chdesc></chrow>
-<chrow><choption>Pin drawer open at start-up</choption><chdesc>Keep the drawer
-open.</chdesc></chrow>
-</choicetable>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol>. The new drawer will be added to
-the list of drawers in the Snippets view.</cmd></step>
-</steps>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt001.dita"><linktext>Snippets view</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt026.dita"><linktext>Editing with snippets - overview</linktext>
-</link>
-<link href="tsrcedt015.dita"><linktext>Adding items to snippets drawers</linktext>
-</link>
-<link href="tsrcedt022.dita"><linktext>Editing snippet items</linktext></link>
-<link href="tsrcedt016.dita"><linktext>Deleting or hiding snippet items or
-drawers</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html deleted file mode 100644 index 22bbb84b6a..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt014.html +++ /dev/null @@ -1,96 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding snippets drawers" /> -<meta name="abstract" content="This documentation explains how to customize the Snippets view by adding a new drawer." /> -<meta name="description" content="This documentation explains how to customize the Snippets view by adding a new drawer." /> -<meta content="snippets, drawers, adding, deleting, editing items, hiding" name="DC.subject" /> -<meta content="snippets, drawers, adding, deleting, editing items, hiding" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt001.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt026.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt015.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt022.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt016.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt014" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding snippets drawers</title> -</head> -<body id="tsrcedt014"><a name="tsrcedt014"><!-- --></a> - - -<h1 class="topictitle1">Adding snippets drawers</h1> - - - -<div><p>This documentation explains how to customize the Snippets view -by adding a new drawer.</p> - -<div class="section">To add a new drawer to the Snippets view:</div> - -<ol> -<li><span>Right-click anywhere in the Snippets view and select <span class="uicontrol">Customize</span> from -the pop-up menu.</span></li> - -<li><span>Click <span class="menucascade"><span class="uicontrol">New</span> > <span class="uicontrol">Category</span> -</span> and type the name of the new drawer in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li><span>Optionally, type a description in the <span class="uicontrol">Description</span> field.</span> -</li> - -<li><span>Select the drawer's behavior by checking check boxes as appropriate. -The check boxes are as follows:</span> - -<table class="choicetableborder" summary="" cellspacing="0" cellpadding="4" rules="rows" frame="hsides" border="1"> -<thead><tr><th valign="bottom" id="N100A4-option" align="left">Option</th> -<th valign="bottom" id="N100A4-desc" align="left">Description</th></tr></thead> -<tbody> -<tr><td valign="top" headers="N100A4-option" id="N100AE"><strong>Hide</strong></td> -<td valign="top" headers="N100A4-desc N100AE">Do not display the drawer.</td> - -</tr> - -<tr><td valign="top" headers="N100A4-option" id="N100BE"><strong>Open drawer at start-up</strong></td> -<td valign="top" headers="N100A4-desc N100BE">At start-up, display -the drawer's items.</td> -</tr> - -<tr><td valign="top" headers="N100A4-option" id="N100CD"><strong>Pin drawer open at start-up</strong></td> -<td valign="top" headers="N100A4-desc N100CD">Keep the drawer -open.</td> -</tr> - -</tbody></table> - -</li> - -<li><span>Click <span class="uicontrol">OK</span>. The new drawer will be added to -the list of drawers in the Snippets view.</span></li> - -</ol> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt001.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags.">Snippets view</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a></div> -<div><a href="tsrcedt015.html" title="">Adding items to snippets drawers</a></div> -<div><a href="tsrcedt022.html" title="">Editing snippet items</a></div> -<div><a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or -drawers</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.dita deleted file mode 100644 index e1195f90f8..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.dita +++ /dev/null @@ -1,82 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt015" xml:lang="en-us">
-<title>Adding items to snippets drawers</title>
-<prolog><metadata>
-<keywords><indexterm>snippet drawers<indexterm>adding items</indexterm></indexterm>
-<indexterm>snippet items<indexterm>adding to drawers</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> To add new items to an existing snippets drawer::</context>
-<steps>
-<step><cmd>Do one of the following choices:</cmd><info><table colsep="0" frame="topbot">
-<tgroup cols="2"><colspec colname="col1" colwidth="72*"/><colspec colname="col2"
-colwidth="127*"/>
-<thead>
-<row>
-<entry colname="col1" valign="top">To start with this:</entry>
-<entry colname="col2" valign="top">Do this:</entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry colname="col1">An empty item that you can edit</entry>
-<entry colname="col2">Right-click anywhere in an existing drawer, select <uicontrol>Customize</uicontrol>,
-and click <menucascade><uicontrol>New</uicontrol><uicontrol>New Item</uicontrol>
-</menucascade>.</entry>
-</row>
-<row>
-<entry colname="col1">Existing text pasted into a new item in an existing
-drawer</entry>
-<entry colname="col2">Copy or cut text to the clipboard. In the Snippets view,
-right-click anywhere in an existing drawer and click <uicontrol>Paste</uicontrol>.</entry>
-</row>
-<row>
-<entry colname="col1">Existing text pasted into a new item in a new or existing
-drawer</entry>
-<entry colname="col2">Select the text, right-click, click <uicontrol>Add to
-Snippets</uicontrol>, specify the name of the drawer in the Snippets view
-to which you want to add the item, and click <uicontrol>OK</uicontrol>.</entry>
-</row>
-</tbody>
-</tgroup>
-</table></info><stepresult>A <wintitle>Customize Palette</wintitle> window
-appears.</stepresult></step>
-<step><cmd>Type a name for the new item, and, optionally, provide a description.</cmd>
-<stepresult>The value that you type in the <uicontrol>Name</uicontrol> field
-will appear next to the item's icon in the Snippets view.</stepresult></step>
-<step><cmd>To include in the <uicontrol>Template Pattern</uicontrol> field
-a variable that you have already defined, click <uicontrol>Insert Variable
-Placeholder</uicontrol>. </cmd><info>A variable placeholder is a marker that,
-when tagging is inserted into the active file, will be replaced by the value
-that is entered into the <uicontrol>Insert Template:</uicontrol><varname>Item_name</varname> dialog
-at insertion time. Clicking the <uicontrol>Insert Variable Placeholder</uicontrol> button
-or typing Ctrl+Space activates a pop-up in the text area that prompts you
-with the correct sequences to create a marker for the variable.</info><stepxmp>For
-example, if you create two variables named <varname>uri</varname> and <varname>prefix</varname>,
-and create variable placeholders for both, the template pattern might look
-like this:<codeblock><%@ taglib uri="${uri}" prefix="${prefix}" %></codeblock></stepxmp>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<result>The new item will be added to the list of items in the appropriate
-drawer.</result>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt001.dita"><linktext>Snippets view</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt026.dita"><linktext>Editing with snippets - overview</linktext>
-</link>
-<link href="tsrcedt014.dita"><linktext>Adding snippets drawers</linktext>
-</link>
-<link href="tsrcedt022.dita"><linktext>Editing snippet items</linktext></link>
-<link href="tsrcedt016.dita"><linktext>Deleting or hiding snippet items or
-drawers</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html deleted file mode 100644 index 2c928aa438..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt015.html +++ /dev/null @@ -1,123 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding items to snippets drawers" /> -<meta content="snippet drawers, adding items to, snippet items, adding to drawers" name="DC.subject" /> -<meta content="snippet drawers, adding items to, snippet items, adding to drawers" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt001.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt026.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt014.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt022.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt016.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt015" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding items to snippets drawers</title> -</head> -<body id="tsrcedt015"><a name="tsrcedt015"><!-- --></a> - - -<h1 class="topictitle1">Adding items to snippets drawers</h1> - - -<div> -<div class="section"> To add new items to an existing snippets drawer::</div> - -<ol> -<li class="stepexpand"><span>Do one of the following choices:</span> -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="hsides" border="1" rules="rows"> -<thead align="left"> -<tr> -<th valign="top" width="36.18090452261307%" id="N10079">To start with this:</th> - -<th valign="top" width="63.81909547738693%" id="N10081">Do this:</th> - -</tr> - -</thead> - -<tbody> -<tr> -<td valign="top" width="36.18090452261307%" headers="N10079 ">An empty item that you can edit</td> - -<td valign="top" width="63.81909547738693%" headers="N10081 ">Right-click anywhere in an existing drawer, select <span class="uicontrol">Customize</span>, -and click <span class="menucascade"><span class="uicontrol">New</span> > <span class="uicontrol">New Item</span> -</span>.</td> - -</tr> - -<tr> -<td valign="top" width="36.18090452261307%" headers="N10079 ">Existing text pasted into a new item in an existing -drawer</td> - -<td valign="top" width="63.81909547738693%" headers="N10081 ">Copy or cut text to the clipboard. In the Snippets view, -right-click anywhere in an existing drawer and click <span class="uicontrol">Paste</span>.</td> - -</tr> - -<tr> -<td valign="top" width="36.18090452261307%" headers="N10079 ">Existing text pasted into a new item in a new or existing -drawer</td> - -<td valign="top" width="63.81909547738693%" headers="N10081 ">Select the text, right-click, click <span class="uicontrol">Add to -Snippets</span>, specify the name of the drawer in the Snippets view -to which you want to add the item, and click <span class="uicontrol">OK</span>.</td> - -</tr> - -</tbody> - -</table> -</div> - A <span class="wintitle">Customize Palette</span> window -appears.</li> - -<li class="stepexpand"><span>Type a name for the new item, and, optionally, provide a description.</span> - The value that you type in the <span class="uicontrol">Name</span> field -will appear next to the item's icon in the Snippets view.</li> - -<li class="stepexpand"><span>To include in the <span class="uicontrol">Template Pattern</span> field -a variable that you have already defined, click <span class="uicontrol">Insert Variable -Placeholder</span>. </span> A variable placeholder is a marker that, -when tagging is inserted into the active file, will be replaced by the value -that is entered into the <span class="uicontrol">Insert Template:</span><var class="varname">Item_name</var> dialog -at insertion time. Clicking the <span class="uicontrol">Insert Variable Placeholder</span> button -or typing Ctrl+Space activates a pop-up in the text area that prompts you -with the correct sequences to create a marker for the variable. For -example, if you create two variables named <var class="varname">uri</var> and <var class="varname">prefix</var>, -and create variable placeholders for both, the template pattern might look -like this:<pre><%@ taglib uri="${uri}" prefix="${prefix}" %></pre> - -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -<div class="section">The new item will be added to the list of items in the appropriate -drawer.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt001.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags.">Snippets view</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a></div> -<div><a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a></div> -<div><a href="tsrcedt022.html" title="">Editing snippet items</a></div> -<div><a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or -drawers</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.dita deleted file mode 100644 index fd624afcea..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.dita +++ /dev/null @@ -1,47 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt016" xml:lang="en-us">
-<title>Deleting or hiding snippet items or drawers</title>
-<titlealts>
-<navtitle>Deleting and hiding drawers and items</navtitle>
-</titlealts>
-<shortdesc>This documentation describes how to delete or hide drawers and
-items in the Snippets view.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>drawers<indexterm>snippets view</indexterm></indexterm>
-<indexterm>snippets<indexterm>modifying drawers</indexterm></indexterm>
-
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>You can hide any drawer or item that shows up in the Snippets view.
-If the drawer or item is user-defined, you can delete it permanently. To delete
-or hide a drawer or item, complete the following steps:</context>
-<steps>
-<step><cmd>Select the item or drawer that you want to remove.</cmd></step>
-<step><cmd>Right-click and select <uicontrol>Customize</uicontrol> from the
-pop-up menu.</cmd></step>
-<step><cmd>Select the item or drawer and click <uicontrol>Delete</uicontrol> or <uicontrol>Hide</uicontrol>.</cmd>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol>. The item or drawer will be deleted
-or hidden from the Snippets view.</cmd></step>
-</steps>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt001.dita"><linktext>Snippets view</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt026.dita"><linktext>Editing with snippets - overview</linktext>
-</link>
-<link href="tsrcedt014.dita"><linktext>Adding snippets drawers</linktext>
-</link>
-<link href="tsrcedt015.dita"><linktext>Adding items to snippets drawers</linktext>
-</link>
-<link href="tsrcedt022.dita"><linktext>Editing snippet items</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html deleted file mode 100644 index f3d75044ae..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt016.html +++ /dev/null @@ -1,70 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Deleting or hiding snippet items or drawers" /> -<meta name="abstract" content="This documentation describes how to delete or hide drawers and items in the Snippets view." /> -<meta name="description" content="This documentation describes how to delete or hide drawers and items in the Snippets view." /> -<meta content="snippets, deleting or hiding drawers, drawers, deleting snippets, hiding snippets" name="DC.subject" /> -<meta content="snippets, deleting or hiding drawers, drawers, deleting snippets, hiding snippets" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt001.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt026.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt014.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt015.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt022.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt016" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Deleting or hiding snippet items or drawers</title> -</head> -<body id="tsrcedt016"><a name="tsrcedt016"><!-- --></a> - - -<h1 class="topictitle1">Deleting or hiding snippet items or drawers</h1> - - - - -<div><p>This documentation describes how to delete or hide drawers and -items in the Snippets view.</p> - -<div class="section">You can hide any drawer or item that shows up in the Snippets view. -If the drawer or item is user-defined, you can delete it permanently. To delete -or hide a drawer or item, complete the following steps:</div> - -<ol> -<li><span>Select the item or drawer that you want to remove.</span></li> - -<li><span>Right-click and select <span class="uicontrol">Customize</span> from the -pop-up menu.</span></li> - -<li><span>Select the item or drawer and click <span class="uicontrol">Delete</span> or <span class="uicontrol">Hide</span>.</span> -</li> - -<li><span>Click <span class="uicontrol">OK</span>. The item or drawer will be deleted -or hidden from the Snippets view.</span></li> - -</ol> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt001.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags.">Snippets view</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a></div> -<div><a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a></div> -<div><a href="tsrcedt015.html" title="">Adding items to snippets drawers</a></div> -<div><a href="tsrcedt022.html" title="">Editing snippet items</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.dita deleted file mode 100644 index 63b31bfa78..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt022" xml:lang="en-us">
-<title>Editing snippet items</title>
-<prolog><metadata>
-<keywords><indexterm>snippets<indexterm>editing items</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> To modify an existing item in a Snippets drawer, complete the steps
-listed below. If you have just completed the task <xref href="tsrcedt015.dita"
-type="task">Adding an item to a snippets drawer</xref> and the <wintitle>Customize
-Palette</wintitle> window is still open, you can skip steps 1 and 2.</context>
-<steps>
-<step><cmd>In the Snippets view, right-click the name of the item that you
-want to modify, and select <uicontrol>Customize</uicontrol>.</cmd></step>
-<step><cmd>Optionally, type a new name and a new description for the item.</cmd>
-</step>
-<step><cmd>To declare a variable, click <uicontrol>New</uicontrol> and type
-the variable's name, description, and default value.</cmd></step>
-<step><cmd>To edit an existing variable, type over the existing values.</cmd>
-</step>
-<step><cmd>To edit the <uicontrol>Template Pattern</uicontrol> field, type
-into the field, cut and paste into the field, or, if you have defined one
-or more variables, click the <uicontrol>Insert Variable Placeholder</uicontrol> button,
-and double-click the name of the variable that you want to insert.</cmd><stepxmp>For
-example, if you have declare variables named <varname>uri</varname> and <varname>prefix</varname>,
-clicking the button brings up a menu that contains those names. Double-clicking <varname>uri</varname> inserts <codeph>${uri}</codeph>,
-as in the following example:<codeblock><%@ taglib uri="${uri}" prefix="${prefix}" %></codeblock></stepxmp>
-<stepresult>Later, when you insert the snippet into a file, <codeph>${uri}</codeph> and <codeph>${prefix}</codeph> are
-each converted to the default value declared in the Variables table. Users
-can replace the default values in the <uicontrol>Insert Template:</uicontrol><varname>Item_name</varname> dialog
-at insertion time.</stepresult></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<result>The modified item will be added to the list of items in the appropriate
-drawer.</result>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt001.dita"><linktext>Snippets view</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt026.dita"><linktext>Editing with snippets - overview</linktext>
-</link>
-<link href="tsrcedt014.dita"><linktext>Adding snippets drawers</linktext>
-</link>
-<link href="tsrcedt015.dita"><linktext>Adding items to snippets drawers</linktext>
-</link>
-<link href="tsrcedt016.dita"><linktext>Deleting or hiding snippet items or
-drawers</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html deleted file mode 100644 index d1a8987b1b..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt022.html +++ /dev/null @@ -1,84 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing snippet items" /> -<meta content="snippets, editing items" name="DC.subject" /> -<meta content="snippets, editing items" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt001.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt026.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt014.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt015.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt016.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt022" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing snippet items</title> -</head> -<body id="tsrcedt022"><a name="tsrcedt022"><!-- --></a> - - -<h1 class="topictitle1">Editing snippet items</h1> - - -<div> -<div class="section"> To modify an existing item in a Snippets drawer, complete the steps -listed below. If you have just completed the task <a href="tsrcedt015.html">Adding an item to a snippets drawer</a> and the <span class="wintitle">Customize -Palette</span> window is still open, you can skip steps 1 and 2.</div> - -<ol> -<li class="stepexpand"><span>In the Snippets view, right-click the name of the item that you -want to modify, and select <span class="uicontrol">Customize</span>.</span></li> - -<li class="stepexpand"><span>Optionally, type a new name and a new description for the item.</span> -</li> - -<li class="stepexpand"><span>To declare a variable, click <span class="uicontrol">New</span> and type -the variable's name, description, and default value.</span></li> - -<li class="stepexpand"><span>To edit an existing variable, type over the existing values.</span> -</li> - -<li class="stepexpand"><span>To edit the <span class="uicontrol">Template Pattern</span> field, type -into the field, cut and paste into the field, or, if you have defined one -or more variables, click the <span class="uicontrol">Insert Variable Placeholder</span> button, -and double-click the name of the variable that you want to insert.</span> For -example, if you have declare variables named <var class="varname">uri</var> and <var class="varname">prefix</var>, -clicking the button brings up a menu that contains those names. Double-clicking <var class="varname">uri</var> inserts <samp class="codeph">${uri}</samp>, -as in the following example:<pre><%@ taglib uri="${uri}" prefix="${prefix}" %></pre> - - Later, when you insert the snippet into a file, <samp class="codeph">${uri}</samp> and <samp class="codeph">${prefix}</samp> are -each converted to the default value declared in the Variables table. Users -can replace the default values in the <span class="uicontrol">Insert Template:</span><var class="varname">Item_name</var> dialog -at insertion time.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -<div class="section">The modified item will be added to the list of items in the appropriate -drawer.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt001.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags.">Snippets view</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt026.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include.">Editing with snippets - overview</a></div> -<div><a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a></div> -<div><a href="tsrcedt015.html" title="">Adding items to snippets drawers</a></div> -<div><a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or -drawers</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.dita deleted file mode 100644 index 0bd8065709..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.dita +++ /dev/null @@ -1,63 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt023" xml:lang="en-us">
-<title>Enabling content assist for JSP files</title>
-<shortdesc>Having the proper files defined in the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> build class path is essential for content
-assist to work properly in JSP files. It is also essential for the links builder
-to be able to correctly resolve links to servlets or <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> beans
-in JSP and HTML files.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>content assistance<indexterm>enabling for JSP files</indexterm></indexterm>
-<indexterm>JSP files<indexterm>enabling content assistance</indexterm></indexterm>
-
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>To enable content assist for JSP files:</context>
-<steps>
-<step><cmd>To determine whether the build path is correct, select <uicontrol>Properties</uicontrol> from
-the project's pop-up menu. </cmd></step>
-<step><cmd>Select <uicontrol>Java Build Path</uicontrol>, and then the <uicontrol>Libraries</uicontrol> page. </cmd>
-<info>You should see the following files:<ul>
-<li>j2ee.jar</li>
-<li>rt.jar </li>
-<li>servlet.jar</li>
-<li>webcontainer.jar</li>
-</ul></info></step>
-<step><cmd>If they are not present, add them as External JAR files. You may
-have your own versions of these files, depending on the level of JDK or Servlet
-API for which you are developing.</cmd></step>
-<step><cmd>If your Web applications reference other JARs, you can place them
-in the build path as follows:</cmd>
-<substeps>
-<substep><cmd>Use the <uicontrol>Add JARs</uicontrol> button on the Library
-page. You must ensure that the JAR file is available to the server by properly
-configuring the server.</cmd></substep>
-<substep><cmd>Add the JARs to the <filepath>WEB-INF/lib</filepath> directory.
-They will be automatically added to the build path and deployed to the server
-in as part of the project WAR.</cmd></substep>
-</substeps>
-</step>
-</steps>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt006.dita"><linktext>Content assist</linktext></link>
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt005.dita"><linktext>Getting content assistance in structured
-text editors</linktext></link>
-<link href="tsrcedt028.dita"><linktext>Adding and removing JSP templates</linktext>
-</link>
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html deleted file mode 100644 index e50a1553c4..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt023.html +++ /dev/null @@ -1,96 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Enabling content assist for JSP files" /> -<meta name="abstract" content="Having the proper files defined in the Java build class path is essential for content assist to work properly in JSP files. It is also essential for the links builder to be able to correctly resolve links to servlets or Java beans in JSP and HTML files." /> -<meta name="description" content="Having the proper files defined in the Java build class path is essential for content assist to work properly in JSP files. It is also essential for the links builder to be able to correctly resolve links to servlets or Java beans in JSP and HTML files." /> -<meta content="JSP files, content assist enablement, content assist, enabling for JSP files" name="DC.subject" /> -<meta content="JSP files, content assist enablement, content assist, enabling for JSP files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt006.html" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt005.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt028.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt023" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Enabling content assist for JSP files</title> -</head> -<body id="tsrcedt023"><a name="tsrcedt023"><!-- --></a> - - -<h1 class="topictitle1">Enabling content assist for JSP files</h1> - - - -<div><p>Having the proper files defined in the Javaâ„¢ build class path is essential for content -assist to work properly in JSP files. It is also essential for the links builder -to be able to correctly resolve links to servlets or Java beans -in JSP and HTML files.</p> - -<div class="section">To enable content assist for JSP files:</div> - -<ol> -<li class="stepexpand"><span>To determine whether the build path is correct, select <span class="uicontrol">Properties</span> from -the project's pop-up menu. </span></li> - -<li class="stepexpand"><span>Select <span class="uicontrol">Java Build Path</span>, and then the <span class="uicontrol">Libraries</span> page. </span> - You should see the following files:<ul> -<li>j2ee.jar</li> - -<li>rt.jar </li> - -<li>servlet.jar</li> - -<li>webcontainer.jar</li> - -</ul> -</li> - -<li class="stepexpand"><span>If they are not present, add them as External JAR files. You may -have your own versions of these files, depending on the level of JDK or Servlet -API for which you are developing.</span></li> - -<li class="stepexpand"><span>If your Web applications reference other JARs, you can place them -in the build path as follows:</span> -<ol type="a"> -<li><span>Use the <span class="uicontrol">Add JARs</span> button on the Library -page. You must ensure that the JAR file is available to the server by properly -configuring the server.</span></li> - -<li><span>Add the JARs to the <span class="filepath">WEB-INF/lib</span> directory. -They will be automatically added to the build path and deployed to the server -in as part of the project WAR.</span></li> - -</ol> - -</li> - -</ol> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt006.html" title="Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor. The placement of the cursor in the source file provides the context for the content assist to offer suggestions for completion.">Content assist</a></div> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt005.html" title="To get help in adding markup to a file, you can use content assist in a structured text editor. Content assist helps you insert or finish a tag or function or finish a line of code in a structured text editor.">Getting content assistance in structured -text editors</a></div> -<div><a href="tsrcedt028.html" title="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing JSP templates</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.dita deleted file mode 100644 index c475e981c8..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.dita +++ /dev/null @@ -1,74 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt024" xml:lang="en-us">
-<title>Adding and removing HTML templates</title>
-<shortdesc>HTML content assist provides several templates, or chunks of predefined
-code, that you can insert into a file. You can use the default templates as
-provided, customize the default templates, or create your own templates.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>HTML<indexterm>templates<indexterm>removing</indexterm></indexterm></indexterm><indexterm>templates<indexterm>HTML</indexterm></indexterm><indexterm>HTML<indexterm>templates<indexterm>adding</indexterm></indexterm></indexterm>
-
-
-
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>For example, you may work on a group of HTML pages that should
-all contain a table with a specific appearance. Create a template that contains
-the tags for that table, including the appropriate attributes and attribute
-values for each tag. (You can copy and paste the tags from a structured text
-editor into the template's <uicontrol>Pattern</uicontrol> field.) Then select
-the name of the template from a content assist proposal list whenever you
-want to insert your custom table into an HTML or XHTML file.</p><p>To add
-a new HTML template, complete the following steps:</p> </context>
-<steps>
-<step><cmd>From the <uicontrol>Window</uicontrol> menu, select <uicontrol>Preferences</uicontrol>.</cmd>
-</step>
-<step><cmd>In the Preferences page, select <menucascade><uicontrol>Web and
-XML</uicontrol><uicontrol>HTML Files</uicontrol><uicontrol>HTML Templates</uicontrol>
-</menucascade>.</cmd></step>
-<step><cmd>Click <uicontrol>New</uicontrol>. </cmd></step>
-<step><cmd>Enter the new template name (a text string) and a brief description
-of the template.</cmd></step>
-<step><cmd>Using the <uicontrol>Context</uicontrol> drop-down list, specify
-the context in which the template is available in the proposal list when content
-assist is requested.</cmd></step>
-<step><cmd>In the <uicontrol>Pattern</uicontrol> field, enter the appropriate
-tags, attributes, or attribute values (the content of the template) to be
-inserted by content assist.</cmd></step>
-<step><cmd>If you want to insert a variable, click the <uicontrol>Variable</uicontrol> button
-and select the variable to be inserted.</cmd><stepxmp>For example, the <varname>word_selection</varname> variable
-indicates the word that is selected at the beginning of template insertion,
-and the <varname>cursor</varname> variable determines where the cursor will
-be after the template is inserted in the HTML document.</stepxmp></step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to save the new template.</cmd>
-</step>
-</steps>
-<postreq><p>You can edit, remove, import, or export a template by using the
-same Preferences page. If you have modified a default template, you can restore
-it to its default value. You can also restore a removed template if you have
-not exited from the workbench since it was removed.</p><p>If you have a template
-that you do not want to remove but you no longer want the template to appear
-in the content assist list, go to the Templates preferences page and uncheck
-its check box.</p></postreq>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt027.dita"><linktext>Adding and removing markup language
-templates - overview</linktext></link>
-<link href="tsrcedt028.dita"><linktext>Adding and removing JSP templates</linktext>
-</link>
-<link href="tsrcedt029.dita"><linktext>Adding and removing XML templates</linktext>
-</link>
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html deleted file mode 100644 index f627370b28..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt024.html +++ /dev/null @@ -1,108 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding and removing HTML templates" /> -<meta name="abstract" content="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates." /> -<meta name="description" content="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates." /> -<meta content="HTML, templates, removing, adding" name="DC.subject" /> -<meta content="HTML, templates, removing, adding" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt027.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt028.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt029.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt024" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding and removing HTML templates</title> -</head> -<body id="tsrcedt024"><a name="tsrcedt024"><!-- --></a> - - -<h1 class="topictitle1">Adding and removing HTML templates</h1> - - - -<div><p>HTML content assist provides several templates, or chunks of predefined -code, that you can insert into a file. You can use the default templates as -provided, customize the default templates, or create your own templates.</p> - -<div class="section"> <p>For example, you may work on a group of HTML pages that should -all contain a table with a specific appearance. Create a template that contains -the tags for that table, including the appropriate attributes and attribute -values for each tag. (You can copy and paste the tags from a structured text -editor into the template's <span class="uicontrol">Pattern</span> field.) Then select -the name of the template from a content assist proposal list whenever you -want to insert your custom table into an HTML or XHTML file.</p> -<p>To add -a new HTML template, complete the following steps:</p> - </div> - -<ol> -<li class="stepexpand"><span>From the <span class="uicontrol">Window</span> menu, select <span class="uicontrol">Preferences</span>.</span> -</li> - -<li class="stepexpand"><span>In the Preferences page, select <span class="menucascade"><span class="uicontrol">Web and -XML</span> > <span class="uicontrol">HTML Files</span> > <span class="uicontrol">HTML Templates</span> -</span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">New</span>. </span></li> - -<li class="stepexpand"><span>Enter the new template name (a text string) and a brief description -of the template.</span></li> - -<li class="stepexpand"><span>Using the <span class="uicontrol">Context</span> drop-down list, specify -the context in which the template is available in the proposal list when content -assist is requested.</span></li> - -<li class="stepexpand"><span>In the <span class="uicontrol">Pattern</span> field, enter the appropriate -tags, attributes, or attribute values (the content of the template) to be -inserted by content assist.</span></li> - -<li class="stepexpand"><span>If you want to insert a variable, click the <span class="uicontrol">Variable</span> button -and select the variable to be inserted.</span> For example, the <var class="varname">word_selection</var> variable -indicates the word that is selected at the beginning of template insertion, -and the <var class="varname">cursor</var> variable determines where the cursor will -be after the template is inserted in the HTML document.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span> to save the new template.</span> -</li> - -</ol> - -<div class="section"><p>You can edit, remove, import, or export a template by using the -same Preferences page. If you have modified a default template, you can restore -it to its default value. You can also restore a removed template if you have -not exited from the workbench since it was removed.</p> -<p>If you have a template -that you do not want to remove but you no longer want the template to appear -in the content assist list, go to the Templates preferences page and uncheck -its check box.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language -templates - overview</a></div> -<div><a href="tsrcedt028.html" title="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing JSP templates</a></div> -<div><a href="tsrcedt029.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You can use the default template as provided, customize that template, or create your own templates.">Adding and removing XML templates</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.dita deleted file mode 100644 index e3905428bc..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.dita +++ /dev/null @@ -1,86 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt025" xml:lang="en-us">
-<title>Setting preferences for structured text editors</title>
-<titlealts>
-<navtitle>Setting structured text editor preferences</navtitle>
-</titlealts>
-<prolog><metadata>
-<keywords><indexterm>structured text editors<indexterm>preference setting</indexterm></indexterm>
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>You can customize your working environment by specifying preferences
-for the structured text editor.</context>
-<steps>
-<step><cmd>In the main menu, click <menucascade><uicontrol>Window</uicontrol>
-<uicontrol>Preferences</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Select one of the choices that are shown in the following table:</cmd>
-<choicetable relcolwidth="10* 30*">
-<chhead><choptionhd>Item</choptionhd><chdeschd>Menu path</chdeschd></chhead>
-<chrow><choption>Annotation settings</choption><chdesc><menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Editors</uicontrol><uicontrol>Annotations</uicontrol></menucascade></chdesc>
-</chrow>
-<chrow><choption>Character encoding</choption><chdesc><uicontrol>Web and XML</uicontrol>,
-then one of the following choices: <uicontrol>CSS Files</uicontrol>, <uicontrol>HTML
-Files</uicontrol>, <uicontrol>JSP Files</uicontrol>, <uicontrol>*XML Files
-( *not implemented in WTP)</uicontrol></chdesc></chrow>
-<chrow><choption>Content assist: HTML</choption><chdesc><menucascade><uicontrol>Web
-and XML</uicontrol><uicontrol>HTML Files</uicontrol><uicontrol>HTML Source</uicontrol>
-</menucascade></chdesc></chrow>
-<chrow><choption>Content assist: JavaScript</choption><chdesc><menucascade>
-<uicontrol>Web and XML</uicontrol><uicontrol>JavaScript Files</uicontrol>
-<uicontrol>JavaScript Source</uicontrol></menucascade></chdesc></chrow>
-<chrow><choption>Content assist: XML</choption><chdesc><menucascade><uicontrol>Web
-and XML</uicontrol><uicontrol>*XML Files (*not implemented in WTP)</uicontrol>
-<uicontrol>XML Source</uicontrol></menucascade></chdesc></chrow>
-<chrow><choption>Editor appearance</choption><chdesc><menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Editors</uicontrol><uicontrol>Structured Text Editor</uicontrol>
-<uicontrol>Appearance</uicontrol></menucascade></chdesc></chrow>
-<chrow><choption>Editor font</choption><chdesc><menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Colors and Fonts</uicontrol><uicontrol>Structured Text Editor</uicontrol>
-</menucascade></chdesc></chrow>
-<chrow><choption>Editor navigation</choption><chdesc><menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Editors</uicontrol><uicontrol>Structured Text Editor</uicontrol>
-<uicontrol>Navigation</uicontrol></menucascade></chdesc></chrow>
-<chrow><choption>File-type-specific settings</choption><chdesc><uicontrol>Web
-and XML</uicontrol>, then navigate to the file type and particular setting</chdesc>
-</chrow>
-<chrow><choption>Hover help</choption><chdesc><menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Editors</uicontrol><uicontrol>Structured Text Editor</uicontrol>
-<uicontrol>Hovers</uicontrol></menucascade></chdesc></chrow>
-<chrow><choption>Key bindings</choption><chdesc><menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Keys</uicontrol><uicontrol>Keyboard Shortcuts</uicontrol></menucascade> then
-in the <uicontrol>Category</uicontrol> field specify <uicontrol>Source</uicontrol></chdesc>
-</chrow>
-<chrow><choption>Spell checking</choption><chdesc><uicontrol>Spell Check</uicontrol></chdesc>
-</chrow>
-<chrow><choption>Syntax checking</choption><chdesc><menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Editors</uicontrol><uicontrol>Structured Text Editor</uicontrol>
-<uicontrol>Appearance</uicontrol></menucascade> then check or uncheck the <uicontrol>Analyze
-annotations while typing</uicontrol> box.</chdesc></chrow>
-</choicetable>
-<info><note>You cannot set <uicontrol>Web and XML</uicontrol> preferences
-unless the Core XML Support capability (<menucascade><uicontrol>Workbench</uicontrol>
-<uicontrol>Capabilities</uicontrol></menucascade>) is enabled, and you cannot
-set preferences for DTD files unless the XML Development capability is enabled.</note></info>
-</step>
-</steps>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt001.dita"><linktext>Setting annotation preferences for
-markup languages</linktext></link>
-<link href="tsrcedt010.dita"><linktext>Checking spelling</linktext></link>
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html deleted file mode 100644 index 2194f1e219..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html +++ /dev/null @@ -1,153 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting preferences for structured text editors" /> -<meta content="structured text editors, preference setting" name="DC.subject" /> -<meta content="structured text editors, preference setting" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt001.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt010.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt025" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting preferences for structured text editors</title> -</head> -<body id="tsrcedt025"><a name="tsrcedt025"><!-- --></a> - - -<h1 class="topictitle1">Setting preferences for structured text editors</h1> - - - -<div> -<div class="section">You can customize your working environment by specifying preferences -for the structured text editor.</div> - -<ol> -<li class="stepexpand"><span>In the main menu, click <span class="menucascade"><span class="uicontrol">Window</span> - > <span class="uicontrol">Preferences</span></span>.</span></li> - -<li class="stepexpand"><span>Select one of the choices that are shown in the following table:</span> - -<table class="choicetableborder" summary="" cellspacing="0" cellpadding="4" rules="rows" frame="hsides" border="1"> -<thead><tr><th valign="bottom" id="N1006E-option">Item</th> -<th valign="bottom" id="N1006E-desc">Menu path</th></tr></thead> -<tbody> - -<tr><td valign="top" headers="N1006E-option" id="N10088"><strong>Annotation settings</strong></td> -<td valign="top" headers="N1006E-desc N10088"><span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Editors</span> > <span class="uicontrol">Annotations</span></span></td> - -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N100AB"><strong>Character encoding</strong></td> -<td valign="top" headers="N1006E-desc N100AB"><span class="uicontrol">Web and XML</span>, -then one of the following choices: <span class="uicontrol">CSS Files</span>, <span class="uicontrol">HTML -Files</span>, <span class="uicontrol">JSP Files</span>, <span class="uicontrol">*XML Files -( *not implemented in WTP)</span></td> -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N100D6"><strong>Content assist: HTML</strong></td> -<td valign="top" headers="N1006E-desc N100D6"><span class="menucascade"><span class="uicontrol">Web -and XML</span> > <span class="uicontrol">HTML Files</span> > <span class="uicontrol">HTML Source</span> -</span></td> -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N100F8"><strong>Content assist: JavaScript</strong></td> -<td valign="top" headers="N1006E-desc N100F8"><span class="menucascade"> -<span class="uicontrol">Web and XML</span> > <span class="uicontrol">JavaScript Files</span> - > <span class="uicontrol">JavaScript Source</span></span></td> -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N1011B"><strong>Content assist: XML</strong></td> -<td valign="top" headers="N1006E-desc N1011B"><span class="menucascade"><span class="uicontrol">Web -and XML</span> > <span class="uicontrol">*XML Files (*not implemented in WTP)</span> - > <span class="uicontrol">XML Source</span></span></td> -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N1013D"><strong>Editor appearance</strong></td> -<td valign="top" headers="N1006E-desc N1013D"><span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editor</span> - > <span class="uicontrol">Appearance</span></span></td> -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N10165"><strong>Editor font</strong></td> -<td valign="top" headers="N1006E-desc N10165"><span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Colors and Fonts</span> > <span class="uicontrol">Structured Text Editor</span> -</span></td> -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N10188"><strong>Editor navigation</strong></td> -<td valign="top" headers="N1006E-desc N10188"><span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editor</span> - > <span class="uicontrol">Navigation</span></span></td> -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N101B0"><strong>File-type-specific settings</strong></td> -<td valign="top" headers="N1006E-desc N101B0"><span class="uicontrol">Web -and XML</span>, then navigate to the file type and particular setting</td> - -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N101C5"><strong>Hover help</strong></td> -<td valign="top" headers="N1006E-desc N101C5"><span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editor</span> - > <span class="uicontrol">Hovers</span></span></td> -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N101ED"><strong>Key bindings</strong></td> -<td valign="top" headers="N1006E-desc N101ED"><span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Keys</span> > <span class="uicontrol">Keyboard Shortcuts</span></span> then -in the <span class="uicontrol">Category</span> field specify <span class="uicontrol">Source</span></td> - -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N1021C"><strong>Spell checking</strong></td> -<td valign="top" headers="N1006E-desc N1021C"><span class="uicontrol">Spell Check</span></td> - -</tr> - -<tr><td valign="top" headers="N1006E-option" id="N10230"><strong>Syntax checking</strong></td> -<td valign="top" headers="N1006E-desc N10230"><span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Editors</span> > <span class="uicontrol">Structured Text Editor</span> - > <span class="uicontrol">Appearance</span></span> then check or uncheck the <span class="uicontrol">Analyze -annotations while typing</span> box.</td> -</tr> - -</tbody></table> - - <div class="note"><span class="notetitle">Note:</span> You cannot set <span class="uicontrol">Web and XML</span> preferences -unless the Core XML Support capability (<span class="menucascade"><span class="uicontrol">Workbench</span> - > <span class="uicontrol">Capabilities</span></span>) is enabled, and you cannot -set preferences for DTD files unless the XML Development capability is enabled.</div> - -</li> - -</ol> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt001.html" title="This documentation describes how to set annotation preferences for Web and XML files. The annotation preferences include whether to analyze the syntactic validity of your file while you are typing and what colors to use to highlight errors, warnings, tasks, search results, bookmarks, and other text.">Setting annotation preferences for -markup languages</a></div> -<div><a href="tsrcedt010.html" title="This documentation describes how to check spelling in a structured text editor.">Checking spelling</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.dita deleted file mode 100644 index d7cf9273fa..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt026" xml:lang="en-us">
-<title>Editing with snippets - overview</title>
-<shortdesc>The Snippets view lets you catalog and organize reusable programming
-objects, such as HTML tagging, <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm>, and JSP code, along with
-files and custom JSP tags. The view can be extended based on additional objects
-that you define and include.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>snippets<indexterm>overview</indexterm></indexterm>
-
-
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>In the Snippets view you can perform the following tasks:</context>
-<steps-unordered>
-<step><cmd>Add snippets drawers</cmd></step>
-<step><cmd>Add items to snippets drawers</cmd></step>
-<step><cmd>Edit snippet items</cmd></step>
-<step><cmd>Delete or hide snippet items or drawers</cmd></step>
-</steps-unordered>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt001.dita"><linktext>Snippets view</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt014.dita"><linktext>Adding snippets drawers</linktext>
-</link>
-<link href="tsrcedt015.dita"><linktext>Adding items to snippets drawers</linktext>
-</link>
-<link href="tsrcedt022.dita"><linktext>Editing snippet items</linktext></link>
-<link href="tsrcedt016.dita"><linktext>Deleting or hiding snippet items or
-drawers</linktext></link>
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html deleted file mode 100644 index 85e03ed11c..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt026.html +++ /dev/null @@ -1,70 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing with snippets - overview" /> -<meta name="abstract" content="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include." /> -<meta name="description" content="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags. The view can be extended based on additional objects that you define and include." /> -<meta content="snippets, overview, HTML, editing, reuse with snippets, JavaScript, JSP code, JSP tags, custom" name="DC.subject" /> -<meta content="snippets, overview, HTML, editing, reuse with snippets, JavaScript, JSP code, JSP tags, custom" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt001.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt014.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt015.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt022.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt016.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt026" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing with snippets - overview</title> -</head> -<body id="tsrcedt026"><a name="tsrcedt026"><!-- --></a> - - -<h1 class="topictitle1">Editing with snippets - overview</h1> - - - -<div><p>The Snippets view lets you catalog and organize reusable programming -objects, such as HTML tagging, JavaScriptâ„¢, and JSP code, along with -files and custom JSP tags. The view can be extended based on additional objects -that you define and include.</p> - -<div class="section">In the Snippets view you can perform the following tasks:</div> - -<ul> -<li><span>Add snippets drawers</span></li> - -<li><span>Add items to snippets drawers</span></li> - -<li><span>Edit snippet items</span></li> - -<li><span>Delete or hide snippet items or drawers</span></li> - -</ul> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt001.html" title="The Snippets view lets you catalog and organize reusable programming objects, such as HTML tagging, JavaScript, and JSP code, along with files and custom JSP tags.">Snippets view</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt014.html" title="This documentation explains how to customize the Snippets view by adding a new drawer.">Adding snippets drawers</a></div> -<div><a href="tsrcedt015.html" title="">Adding items to snippets drawers</a></div> -<div><a href="tsrcedt022.html" title="">Editing snippet items</a></div> -<div><a href="tsrcedt016.html" title="This documentation describes how to delete or hide drawers and items in the Snippets view.">Deleting or hiding snippet items or -drawers</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.dita deleted file mode 100644 index 7d324eb281..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.dita +++ /dev/null @@ -1,40 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt027" xml:lang="en-us">
-<title>Adding and removing markup language templates - overview</title>
-<titlealts>
-<navtitle>Adding markup language templates</navtitle>
-</titlealts>
-<shortdesc>Content assist provides templates, or chunks of predefined code,
-that you can insert into a file. You can use the default templates as provided,
-customize the default templates, or create your own templates.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>markup languages<indexterm>templates</indexterm></indexterm>
-<indexterm>templates<indexterm>markup languages</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>Templates are available for the following markup languages:<ul>
-<li>HTML or XHTML</li>
-<li>JSP</li>
-</ul></context>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt024.dita"><linktext>Adding and removing HTML templates</linktext>
-</link>
-<link href="tsrcedt028.dita"><linktext>Adding and removing JSP templates</linktext>
-</link>
-<link href="tsrcedt029.dita"><linktext>Adding and removing XML templates</linktext>
-</link>
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html deleted file mode 100644 index 66434c32b4..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt027.html +++ /dev/null @@ -1,63 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding and removing markup language templates - overview" /> -<meta name="abstract" content="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates." /> -<meta name="description" content="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates." /> -<meta content="markup languages, adding and removing templates" name="DC.subject" /> -<meta content="markup languages, adding and removing templates" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt024.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt028.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt029.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt027" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding and removing markup language templates - overview</title> -</head> -<body id="tsrcedt027"><a name="tsrcedt027"><!-- --></a> - - -<h1 class="topictitle1">Adding and removing markup language templates - overview</h1> - - - - -<div><p>Content assist provides templates, or chunks of predefined code, -that you can insert into a file. You can use the default templates as provided, -customize the default templates, or create your own templates.</p> - -<div class="section">Templates are available for the following markup languages:<ul> -<li>HTML or XHTML</li> - -<li>JSP</li> - -</ul> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt024.html" title="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing HTML templates</a></div> -<div><a href="tsrcedt028.html" title="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing JSP templates</a></div> -<div><a href="tsrcedt029.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You can use the default template as provided, customize that template, or create your own templates.">Adding and removing XML templates</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.dita deleted file mode 100644 index cb9bc26c2a..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.dita +++ /dev/null @@ -1,72 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<task id="tsrcedt028" xml:lang="en-us">
-<title>Adding and removing JSP templates</title>
-<shortdesc>JSP content assist provides several templates, or chunks of predefined
-code, that you can insert into a file. You can use the default templates as
-provided, customize the default templates, or create your own templates.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>JSP pages<indexterm>templates</indexterm></indexterm>
-<indexterm>templates<indexterm>JSP pages</indexterm></indexterm>
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>For example, you may work on a group of JSP pages that should
-all contain a table with a specific appearance. Create a template that contains
-the tags for that table, including the appropriate attributes and attribute
-values for each tag. (You can copy and paste the tags from a structured text
-editor into the template's <uicontrol>Pattern</uicontrol> field.) Then select
-the name of the template from a content assist proposal list whenever you
-want to insert your custom table into a JSP file.</p><p>To add a new JSP template,
-complete the following steps:</p> </context>
-<steps>
-<step><cmd>From the <uicontrol>Window</uicontrol> menu, select <uicontrol>Preferences</uicontrol>.</cmd>
-</step>
-<step><cmd>In the Preferences page, select <menucascade><uicontrol>Web and
-XML</uicontrol><uicontrol>JSP Files</uicontrol><uicontrol>JSP Templates</uicontrol>
-</menucascade>.</cmd></step>
-<step><cmd>Click <uicontrol>New</uicontrol>. </cmd></step>
-<step><cmd>Enter the new template name (a text string) and a brief description
-of the template.</cmd></step>
-<step><cmd>Using the <uicontrol>Context</uicontrol> drop-down list, specify
-the context in which the template is available in the proposal list when content
-assist is requested.</cmd></step>
-<step><cmd>In the <uicontrol>Pattern</uicontrol> field, enter the appropriate
-tags, attributes, or attribute values (the content of the template) to be
-inserted by content assist.</cmd></step>
-<step><cmd>If you want to insert a variable, click the <uicontrol>Variable</uicontrol> button
-and select the variable to be inserted.</cmd><stepxmp>For example, the <varname>word_selection</varname> variable
-indicates the word that is selected at the beginning of template insertion,
-and the <varname>cursor</varname> variable determines where the cursor will
-be after the template is inserted in the HTML document.</stepxmp></step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to save the new template.</cmd>
-</step>
-</steps>
-<postreq><p>You can edit, remove, import, or export a template by using the
-same Preferences page. If you have modified a default template, you can restore
-it to its default value. You can also restore a removed template if you have
-not exited from the workbench since it was removed.</p><p>If you have a template
-that you do not want to remove but you no longer want the template to appear
-in the content assist list, go to the Templates preferences page and uncheck
-its check box.</p></postreq>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt027.dita"><linktext>Adding and removing markup language
-templates - overview</linktext></link>
-<link href="tsrcedt024.dita"><linktext>Adding and removing HTML templates</linktext>
-</link>
-<link href="tsrcedt029.dita"><linktext>Adding and removing XML templates</linktext>
-</link>
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html deleted file mode 100644 index 57cf2d47aa..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt028.html +++ /dev/null @@ -1,108 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding and removing JSP templates" /> -<meta name="abstract" content="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates." /> -<meta name="description" content="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates." /> -<meta content="JSP templates, adding, removing, templates, JSP" name="DC.subject" /> -<meta content="JSP templates, adding, removing, templates, JSP" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt027.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt024.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt029.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt028" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding and removing JSP templates</title> -</head> -<body id="tsrcedt028"><a name="tsrcedt028"><!-- --></a> - - -<h1 class="topictitle1">Adding and removing JSP templates</h1> - - - -<div><p>JSP content assist provides several templates, or chunks of predefined -code, that you can insert into a file. You can use the default templates as -provided, customize the default templates, or create your own templates.</p> - -<div class="section"> <p>For example, you may work on a group of JSP pages that should -all contain a table with a specific appearance. Create a template that contains -the tags for that table, including the appropriate attributes and attribute -values for each tag. (You can copy and paste the tags from a structured text -editor into the template's <span class="uicontrol">Pattern</span> field.) Then select -the name of the template from a content assist proposal list whenever you -want to insert your custom table into a JSP file.</p> -<p>To add a new JSP template, -complete the following steps:</p> - </div> - -<ol> -<li class="stepexpand"><span>From the <span class="uicontrol">Window</span> menu, select <span class="uicontrol">Preferences</span>.</span> -</li> - -<li class="stepexpand"><span>In the Preferences page, select <span class="menucascade"><span class="uicontrol">Web and -XML</span> > <span class="uicontrol">JSP Files</span> > <span class="uicontrol">JSP Templates</span> -</span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">New</span>. </span></li> - -<li class="stepexpand"><span>Enter the new template name (a text string) and a brief description -of the template.</span></li> - -<li class="stepexpand"><span>Using the <span class="uicontrol">Context</span> drop-down list, specify -the context in which the template is available in the proposal list when content -assist is requested.</span></li> - -<li class="stepexpand"><span>In the <span class="uicontrol">Pattern</span> field, enter the appropriate -tags, attributes, or attribute values (the content of the template) to be -inserted by content assist.</span></li> - -<li class="stepexpand"><span>If you want to insert a variable, click the <span class="uicontrol">Variable</span> button -and select the variable to be inserted.</span> For example, the <var class="varname">word_selection</var> variable -indicates the word that is selected at the beginning of template insertion, -and the <var class="varname">cursor</var> variable determines where the cursor will -be after the template is inserted in the HTML document.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span> to save the new template.</span> -</li> - -</ol> - -<div class="section"><p>You can edit, remove, import, or export a template by using the -same Preferences page. If you have modified a default template, you can restore -it to its default value. You can also restore a removed template if you have -not exited from the workbench since it was removed.</p> -<p>If you have a template -that you do not want to remove but you no longer want the template to appear -in the content assist list, go to the Templates preferences page and uncheck -its check box.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language -templates - overview</a></div> -<div><a href="tsrcedt024.html" title="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing HTML templates</a></div> -<div><a href="tsrcedt029.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You can use the default template as provided, customize that template, or create your own templates.">Adding and removing XML templates</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.dita b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.dita deleted file mode 100644 index e41bd7cf09..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.dita +++ /dev/null @@ -1,74 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "..\dtd\task.dtd">
-<!-- $Id: tsrcedt029.dita,v 1.4 2006/04/13 20:37:13 bkorn Exp $ -->
-<task id="tsrcedt027" xml:lang="en-us">
-<title>Adding and removing XML templates</title>
-<shortdesc>XML content assist provides a comment template, a chunk of predefined
-code that you can insert into a file. You can use the default template as
-provided, customize that template, or create your own templates.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>templates<indexterm>XML</indexterm></indexterm>
-<indexterm>xml templates<indexterm>adding</indexterm></indexterm>
-
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>For example, you may work on a group of XML pages that should
-all contain a table with a specific appearance. Create a template that contains
-the tags for that table, including the appropriate attributes and attribute
-values for each tag. (You can copy and paste the tags from a structured text
-editor into the template's <uicontrol>Pattern</uicontrol> field.) Then select
-the name of the template from a content assist proposal list whenever you
-want to insert your custom table into an XML file.</p><p>To add a new XML
-template, complete the following steps: </p> </context>
-<steps>
-<step><cmd>From the <uicontrol>Window</uicontrol> menu, select <uicontrol>Preferences</uicontrol>.</cmd>
-</step>
-<step><cmd>In the Preferences page, select <menucascade><uicontrol>Web and
-XML</uicontrol><uicontrol>XML Files</uicontrol><uicontrol>XML Templates</uicontrol>
-</menucascade>.</cmd></step>
-<step><cmd>Click <uicontrol>New</uicontrol>. </cmd></step>
-<step><cmd>Enter the new template name (a text string) and a brief description
-of the template.</cmd></step>
-<step><cmd>Using the <uicontrol>Context</uicontrol> drop-down list, specify
-the context in which the template is available in the proposal list when content
-assist is requested.</cmd></step>
-<step><cmd>In the <uicontrol>Pattern</uicontrol> field, enter the appropriate
-tags, attributes, or attribute values (the content of the template) to be
-inserted by content assist.</cmd></step>
-<step><cmd>If you want to insert a variable, click the <uicontrol>Variable</uicontrol> button
-and select the variable to be inserted.</cmd><stepxmp>For example, the <varname>word_selection</varname> variable
-indicates the word that is selected at the beginning of template insertion,
-and the <varname>cursor</varname> variable determines where the cursor will
-be after the template is inserted in the XML document.</stepxmp></step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to save the new template.</cmd>
-</step>
-</steps>
-<postreq><p>You can edit, remove, import, or export a template by using the
-same Preferences page. If you have modified a default template, you can restore
-it to its default value. You can also restore a removed template if you have
-not exited from the workbench since it was removed.</p><p>If you have a template
-that you do not want to remove but you no longer want the template to appear
-in the content assist list, go to the Templates preferences page and uncheck
-its check box.</p></postreq>
-</taskbody>
-<related-links>
-<linkpool type="concept">
-<link href="csrcedt004.dita"><linktext>Structured text editors for markup
-languages</linktext></link>
-</linkpool>
-<linkpool type="task">
-<link href="tsrcedt027.dita"><linktext>Adding and removing markup language
-templates - overview</linktext></link>
-<link href="tsrcedt024.dita"><linktext>Adding and removing HTML templates</linktext>
-</link>
-<link href="tsrcedt028.dita"><linktext>Adding and removing JSP templates</linktext>
-</link>
-<link href="tsrcedt000.dita"><linktext>Editing text coded in markup languages
-- overview</linktext></link>
-</linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html b/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html deleted file mode 100644 index 07d266908b..0000000000 --- a/docs/org.eclipse.wst.sse.doc.user/topics/tsrcedt029.html +++ /dev/null @@ -1,108 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding and removing XML templates" /> -<meta name="abstract" content="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You can use the default template as provided, customize that template, or create your own templates." /> -<meta name="description" content="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You can use the default template as provided, customize that template, or create your own templates." /> -<meta content="xml templates, adding, removing, templates, XML" name="DC.subject" /> -<meta content="xml templates, adding, removing, templates, XML" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="csrcedt004.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt027.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt024.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt028.html" /> -<meta scheme="URI" name="DC.Relation" content="tsrcedt000.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tsrcedt027" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding and removing XML templates</title> -</head> -<body id="tsrcedt027"><a name="tsrcedt027"><!-- --></a> - - -<h1 class="topictitle1">Adding and removing XML templates</h1> - - - -<div><p>XML content assist provides a comment template, a chunk of predefined -code that you can insert into a file. You can use the default template as -provided, customize that template, or create your own templates.</p> - -<div class="section"> <p>For example, you may work on a group of XML pages that should -all contain a table with a specific appearance. Create a template that contains -the tags for that table, including the appropriate attributes and attribute -values for each tag. (You can copy and paste the tags from a structured text -editor into the template's <span class="uicontrol">Pattern</span> field.) Then select -the name of the template from a content assist proposal list whenever you -want to insert your custom table into an XML file.</p> -<p>To add a new XML -template, complete the following steps: </p> - </div> - -<ol> -<li class="stepexpand"><span>From the <span class="uicontrol">Window</span> menu, select <span class="uicontrol">Preferences</span>.</span> -</li> - -<li class="stepexpand"><span>In the Preferences page, select <span class="menucascade"><span class="uicontrol">Web and -XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol">XML Templates</span> -</span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">New</span>. </span></li> - -<li class="stepexpand"><span>Enter the new template name (a text string) and a brief description -of the template.</span></li> - -<li class="stepexpand"><span>Using the <span class="uicontrol">Context</span> drop-down list, specify -the context in which the template is available in the proposal list when content -assist is requested.</span></li> - -<li class="stepexpand"><span>In the <span class="uicontrol">Pattern</span> field, enter the appropriate -tags, attributes, or attribute values (the content of the template) to be -inserted by content assist.</span></li> - -<li class="stepexpand"><span>If you want to insert a variable, click the <span class="uicontrol">Variable</span> button -and select the variable to be inserted.</span> For example, the <var class="varname">word_selection</var> variable -indicates the word that is selected at the beginning of template insertion, -and the <var class="varname">cursor</var> variable determines where the cursor will -be after the template is inserted in the XML document.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span> to save the new template.</span> -</li> - -</ol> - -<div class="section"><p>You can edit, remove, import, or export a template by using the -same Preferences page. If you have modified a default template, you can restore -it to its default value. You can also restore a removed template if you have -not exited from the workbench since it was removed.</p> -<p>If you have a template -that you do not want to remove but you no longer want the template to appear -in the content assist list, go to the Templates preferences page and uncheck -its check box.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup -languages</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tsrcedt027.html" title="Content assist provides templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing markup language -templates - overview</a></div> -<div><a href="tsrcedt024.html" title="HTML content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing HTML templates</a></div> -<div><a href="tsrcedt028.html" title="JSP content assist provides several templates, or chunks of predefined code, that you can insert into a file. You can use the default templates as provided, customize the default templates, or create your own templates.">Adding and removing JSP templates</a></div> -<div><a href="tsrcedt000.html" title="You can edit text coded in markup languages with a structured text editor. This is a generic term for several editors that you can use to edit any of several markup languages, such as HTML.">Editing text coded in markup languages -- overview</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.ui.infopop/.cvsignore b/docs/org.eclipse.wst.sse.ui.infopop/.cvsignore deleted file mode 100644 index c14487ceac..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -build.xml diff --git a/docs/org.eclipse.wst.sse.ui.infopop/.project b/docs/org.eclipse.wst.sse.ui.infopop/.project deleted file mode 100644 index 2d9cc8449f..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.sse.ui.infopop</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.wst.sse.ui.infopop/EditorContexts.xml b/docs/org.eclipse.wst.sse.ui.infopop/EditorContexts.xml deleted file mode 100644 index b68067e244..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/EditorContexts.xml +++ /dev/null @@ -1,85 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2001, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> - -<context id="sted0001"> -<description>This page lets you customize the appearance of the structured text editors. -When the <b>Highlight matching brackets</b> option is selected, whenever the cursor is next to a bracket or curly braces, its opening or closing counter part is highlighted. -Select the <b>Report problems as you type</b> check box to update validity annotations (temporary annotations, such as missing required attributes based on a DTD, that go away when the editor is closed, or the problem is fixed) as the user types. -In the <b>Appearance color options</b> table, you can adjust various editor appearance features. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="sted0003"> -<description>This page lets you customize hover text in the structured text editors. -</description> -<topic label="Setting preferences for structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt025.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclispe.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="xmlm1010"> -<description>Content assist helps you to finish tags or lines of code and insert templates. Depending on the source markup language, the choices that are available in the content assist list are based on tags defined by DTD and schema files, tag library descriptors, or content model standard that is specified for the file being edited. HTML content assist choices are based on the W3C HTML 4.01 content model. - -If your cursor is in a position where content assist is available, a pop-up list of available choices is displayed. The content assist list displays all available completions for the current cursor position, including templates. Content assist is also available by pressing Ctrl+Space. -</description> -<topic label="Content assist" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt006.html"/> -<topic label="Getting content assistance in structured text editors" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt005.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="xmlm1030"> -<description>Select this option to format an entire document. Formatting restores element and attribute indentation and positioning, which may have been offset during editing, to see nesting hierarchies and relationships more clearly in the file. Edit the appropriate Preferences pages to make changes in specific formatting behavior. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="xmlm1040"> -<description>Select this option to format selected elements. Formatting restores element and attribute indentation and positioning, which may have been offset during editing, to see nesting hierarchies and relationships more clearly in the file. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="xmlm1070"> -<description>Select this option to open the <b>Properties</b> view, which displays properties relevant to the current element if any exist. -</description> -<topic label="Properties view" href="../org.eclipse.platform.doc.user/concepts/cpropview.htm"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="xmlm2000"> -<description>This structured text editor lets you edit a text file that is coded in a markup language. The editor provides many text editing features, such as content assist, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting. For a more specific list of editing features, see the first link below. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - -<context id="webx0000"> -<description>This page lets you customize task tag discovery in the structured text editors. -</description> -</context> - -<context id="ecss0000"> -<description>The CSS source page editor lets you edit a cascading style sheet. The editor provides many text editing features, such as content assist, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> -<context id="misc0180"> - <description>Use this dialog to edit the CSS content settings for a CSS file. You can specify CSS profile or restore the default by clicking <b>Restore Defaults</b>. - </description> -</context> -</contexts> diff --git a/docs/org.eclipse.wst.sse.ui.infopop/EditorCssContexts2.xml b/docs/org.eclipse.wst.sse.ui.infopop/EditorCssContexts2.xml deleted file mode 100644 index f8bc39deab..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/EditorCssContexts2.xml +++ /dev/null @@ -1,30 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> -<context id="csssource_source_HelpId"> -<description>The CSS source page editor lets you edit a cascading style sheet. The editor provides many text editing features, such as content assist, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> -<context id="ecss0000"> -<description>The CSS source page editor lets you edit a cascading style sheet. The editor provides many text editing features, such as content assist, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting. -</description> -<topic label="Structured text editors for markup languages" href="../org.eclipse.wst.sse.doc.user/topics/csrcedt004.html"/> -<topic label="Editing text coded in markup languages - overview" href="../org.eclipse.wst.sse.doc.user/topics/tsrcedt000.html"/> -</context> - <context id="misc0180"> - <description>Use this dialog to edit the CSS content settings for a CSS file. You can specify CSS profile or restore the default by clicking <b>Restore Defaults</b>. - </description> -</context> -</contexts> diff --git a/docs/org.eclipse.wst.sse.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.sse.ui.infopop/META-INF/MANIFEST.MF deleted file mode 100644 index 7bdd756f8f..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/META-INF/MANIFEST.MF +++ /dev/null @@ -1,7 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %Bundle-Name.0 -Bundle-SymbolicName: org.eclipse.wst.sse.ui.infopop; singleton:=true -Bundle-Version: 1.0.102.qualifier -Bundle-Vendor: %Bundle-Vendor.0 -Bundle-Localization: plugin diff --git a/docs/org.eclipse.wst.sse.ui.infopop/about.html b/docs/org.eclipse.wst.sse.ui.infopop/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.sse.ui.infopop/build.properties b/docs/org.eclipse.wst.sse.ui.infopop/build.properties deleted file mode 100644 index f92d471ec7..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/build.properties +++ /dev/null @@ -1,7 +0,0 @@ -bin.includes = EditorContexts.xml,\ - about.html,\ - plugin.xml,\ - META-INF/,\ - EditorCssContexts2.xml,\ - plugin.properties -src.includes = build.properties diff --git a/docs/org.eclipse.wst.sse.ui.infopop/plugin.properties b/docs/org.eclipse.wst.sse.ui.infopop/plugin.properties deleted file mode 100644 index 84f306f8a8..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/plugin.properties +++ /dev/null @@ -1,3 +0,0 @@ -# properties file for org.eclipse.wst.sse.ui.infopop -Bundle-Vendor.0 = Eclipse.org -Bundle-Name.0 = SSE infopops
\ No newline at end of file diff --git a/docs/org.eclipse.wst.sse.ui.infopop/plugin.xml b/docs/org.eclipse.wst.sse.ui.infopop/plugin.xml deleted file mode 100644 index 2a3796f2a7..0000000000 --- a/docs/org.eclipse.wst.sse.ui.infopop/plugin.xml +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<!-- /******************************************************************************* - * Copyright (c) 2001, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<plugin> - -<extension point="org.eclipse.help.contexts"> - <contexts file="EditorContexts.xml" plugin ="org.eclipse.wst.sse.ui"/> - <contexts file="EditorCssContexts2.xml" plugin ="org.eclipse.wst.sse.ui"/> -</extension> - - -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.web.ui.infopop/.cvsignore b/docs/org.eclipse.wst.web.ui.infopop/.cvsignore deleted file mode 100644 index c14487ceac..0000000000 --- a/docs/org.eclipse.wst.web.ui.infopop/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -build.xml diff --git a/docs/org.eclipse.wst.web.ui.infopop/.project b/docs/org.eclipse.wst.web.ui.infopop/.project deleted file mode 100644 index 10c4a6e98c..0000000000 --- a/docs/org.eclipse.wst.web.ui.infopop/.project +++ /dev/null @@ -1,11 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.web.ui.infopop</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - </buildSpec> - <natures> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.web.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.web.ui.infopop/META-INF/MANIFEST.MF deleted file mode 100644 index f703703db8..0000000000 --- a/docs/org.eclipse.wst.web.ui.infopop/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: Static Web infopop -Bundle-SymbolicName: org.eclipse.wst.web.ui.infopop; singleton:=true -Bundle-Version: 1.0.202.qualifier -Bundle-Vendor: %pluginProvider -Bundle-Localization: plugin -Eclipse-AutoStart: true diff --git a/docs/org.eclipse.wst.web.ui.infopop/StaticWebWizContexts.xml b/docs/org.eclipse.wst.web.ui.infopop/StaticWebWizContexts.xml deleted file mode 100644 index bf0f403b04..0000000000 --- a/docs/org.eclipse.wst.web.ui.infopop/StaticWebWizContexts.xml +++ /dev/null @@ -1,33 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2006 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> -<context id="webw2000"> -<description> Use this page to name your Web project and specify the file system location (the place where the resources you create are stored.) When the Use default check box is selected, the project will be created in the file system location where your workspace resides. To change the default file system location, clear the checkbox and locate the path using the <b>Browse</b> button. To configure additional options, select the <b>Next</b> button. -In the Target Runtime field, select the server where you want to publish the Web project. if a server is not already defined, click <b>New</b> to select a server runtime environment. </description> -<topic label="Creating a static Web project" href="../org.eclipse.wst.webtools.doc.user/topics/twcresta.html"/> -</context> - -<context id="webw2100"> -<description>Presets are used to define a default set of facet versions that will configure a project for a particular type of development. The Static Web Module facet enables the project to be deployed as a static -Web module. Click Show Runtimes to view the available runtimes and runtime compositions.</description> -<topic label="Creating a static Web project" href="../org.eclipse.wst.webtools.doc.user/topics/twcresta.html"/> -</context> - -<context id="webw2200"> -<description>The Web content folder is where the elements of your Web site such as Web pages, graphics and style sheets are stored. This directory structure is necessary to ensure that the content of your Web site will be included in the WAR file at deployment and that link validation will work correctly. -</description> -<topic label="Creating a static Web project" href="../org.eclipse.wst.webtools.doc.user/topics/twcresta.html"/> -</context> - - -</contexts> diff --git a/docs/org.eclipse.wst.web.ui.infopop/about.html b/docs/org.eclipse.wst.web.ui.infopop/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.web.ui.infopop/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.web.ui.infopop/build.properties b/docs/org.eclipse.wst.web.ui.infopop/build.properties deleted file mode 100644 index d9a93d8cea..0000000000 --- a/docs/org.eclipse.wst.web.ui.infopop/build.properties +++ /dev/null @@ -1,6 +0,0 @@ -bin.includes = StaticWebWizContexts.xml,\ - about.html,\ - plugin.xml,\ - plugin.properties,\ - META-INF/ -src.includes = build.properties diff --git a/docs/org.eclipse.wst.web.ui.infopop/plugin.properties b/docs/org.eclipse.wst.web.ui.infopop/plugin.properties deleted file mode 100644 index b61d2de9cd..0000000000 --- a/docs/org.eclipse.wst.web.ui.infopop/plugin.properties +++ /dev/null @@ -1,13 +0,0 @@ -############################################################################### -# Copyright (c) 2006 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### - -pluginName = Static Web infopop -pluginProvider = Eclipse.org
\ No newline at end of file diff --git a/docs/org.eclipse.wst.web.ui.infopop/plugin.xml b/docs/org.eclipse.wst.web.ui.infopop/plugin.xml deleted file mode 100644 index 20ac018932..0000000000 --- a/docs/org.eclipse.wst.web.ui.infopop/plugin.xml +++ /dev/null @@ -1,24 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> - -<!-- ================================================= --> -<!-- This is the plugin for declaring the help --> -<!-- contributions for using the tool. --> -<!-- ================================================= --> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2006 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - -<extension point="org.eclipse.help.contexts"> - <contexts file="StaticWebWizContexts.xml" plugin ="org.eclipse.wst.web.ui"/> -</extension> - - -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/.cvsignore b/docs/org.eclipse.wst.webtools.doc.user/.cvsignore deleted file mode 100644 index d1dca983e1..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/.cvsignore +++ /dev/null @@ -1,3 +0,0 @@ -build.xml -org.eclipse.wst.webtools.doc.user_1.0.0.jar -temp
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/.project b/docs/org.eclipse.wst.webtools.doc.user/.project deleted file mode 100644 index bd5b15799c..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.webtools.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.webtools.doc.user/DocBuild.xml b/docs/org.eclipse.wst.webtools.doc.user/DocBuild.xml deleted file mode 100644 index 9c9ddbee57..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/DocBuild.xml +++ /dev/null @@ -1,59 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<!-- - - This script build the Help plug-in by transforming the DITA source files into HTML. - - To use this script, you must install DITA-OT on your machine in the directory - defined by the dita.ot.dir property. - - Run the default target after you edit the DITA source files to regenerate the HTML. - - To customize this script for other Help plug-ins, modify the value of the args.input property - to be the DITA map file for the plug-in. - - NOTE: This script assumes that links to sibling Help plug-ins have scope="peer", otherwise the - output directory structure will be shifted incorrectly. - - NOTE: This script assumes that you hand code your plugin.xml file in myplugin.xml. This file - will be copied over the generated plugin.xml which is currently not being generated correctly - by DITA-OT. - - ChangeLog: - 2006-04-05 Arthur Ryman <ryman@ca.ibm.com> - - Created. - ---> -<project name="eclipsehelp" default="all"> - - <property name="dita.ot.dir" location="C:/DITA-OT1.2.2" /> - - <path id="dost.class.path"> - <pathelement location="${dita.ot.dir}${file.separator}lib${file.separator}dost.jar" /> - </path> - - <taskdef name="integrate" classname="org.dita.dost.platform.IntegratorTask"> - <classpath refid="dost.class.path" /> - </taskdef> - <target name="all" depends="integrate, eclipsehelp"> - </target> - <target name="integrate"> - <integrate ditadir="${dita.ot.dir}" /> - </target> - - <!-- revise below here --> - <target name="eclipsehelp"> - <ant antfile="${dita.ot.dir}${file.separator}conductor.xml" target="init" dir="${dita.ot.dir}"> - <property name="args.copycss" value="no" /> - <property name="args.csspath" value="org.eclipse.wst.doc.user" /> - <property name="args.eclipse.provider" value="Eclipse.org" /> - <property name="args.eclipse.version" value="1.5.0" /> - <property name="args.input" location="webtools_toc.ditamap" /> - <property name="clean.temp" value="true" /> - <property name="dita.extname" value=".dita" /> - <property name="dita.temp.dir" location="temp" /> - <property name="output.dir" location=".." /> - <property name="transtype" value="eclipsehelp" /> - </ant> - <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" /> - </target> -</project> diff --git a/docs/org.eclipse.wst.webtools.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.webtools.doc.user/META-INF/MANIFEST.MF deleted file mode 100644 index cf2b706359..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.wst.webtools.doc.user; singleton:=true -Bundle-Version: 1.0.300.qualifier -Bundle-Vendor: %providerName -Bundle-Localization: plugin -Eclipse-LazyStart: true diff --git a/docs/org.eclipse.wst.webtools.doc.user/about.html b/docs/org.eclipse.wst.webtools.doc.user/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.webtools.doc.user/build.properties b/docs/org.eclipse.wst.webtools.doc.user/build.properties deleted file mode 100644 index f7faab09d4..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/build.properties +++ /dev/null @@ -1,15 +0,0 @@ -bin.includes = plugin.xml,\ - webtools_toc.xml,\ - org.eclipse.wst.webtools.doc.userindex.xml,\ - about.html,\ - images/,\ - topics/*htm*,\ - index/,\ - META-INF/,\ - plugin.properties -src.includes = build.properties,\ - *.maplist,\ - *.ditamap,\ - topics/*.dita -bin.excludes = DocBuild.xml,\ - myPlugin*.xml
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/fixit.gif b/docs/org.eclipse.wst.webtools.doc.user/images/fixit.gif Binary files differdeleted file mode 100644 index ffafc3dbf4..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/fixit.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/grptype.gif b/docs/org.eclipse.wst.webtools.doc.user/images/grptype.gif Binary files differdeleted file mode 100644 index 46d245f0b6..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/grptype.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/menubutton.gif b/docs/org.eclipse.wst.webtools.doc.user/images/menubutton.gif Binary files differdeleted file mode 100644 index 7ef1a62ba7..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/menubutton.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nlinux.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nlinux.gif Binary files differdeleted file mode 100644 index 7c135cfe64..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nlinux.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nshowerr.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nshowerr.gif Binary files differdeleted file mode 100644 index c2bfdd606b..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nshowerr.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwarning.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwarning.gif Binary files differdeleted file mode 100644 index cf4fdf93c7..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwarning.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwin.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwin.gif Binary files differdeleted file mode 100644 index 895f9ca06d..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwin.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkbrk.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkbrk.gif Binary files differdeleted file mode 100644 index 6321433aff..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkbrk.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkcss.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkcss.gif Binary files differdeleted file mode 100644 index 1a0caf64ab..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkcss.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr-l.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr-l.gif Binary files differdeleted file mode 100644 index 9c73b6a197..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr-l.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr.gif Binary files differdeleted file mode 100644 index f3c626150e..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkgr.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkind.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkind.gif Binary files differdeleted file mode 100644 index 943f756328..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkind.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkmal.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkmal.gif Binary files differdeleted file mode 100644 index 889c47f6dd..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkmal.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnknum.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnknum.gif Binary files differdeleted file mode 100644 index f324a6341b..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnknum.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkotr.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkotr.gif Binary files differdeleted file mode 100644 index f596591d52..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkotr.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkque.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkque.gif Binary files differdeleted file mode 100644 index 345f939ac1..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnkque.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnktsk.gif b/docs/org.eclipse.wst.webtools.doc.user/images/nwlnktsk.gif Binary files differdeleted file mode 100644 index 9cd47eec4c..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/nwlnktsk.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/skipit.gif b/docs/org.eclipse.wst.webtools.doc.user/images/skipit.gif Binary files differdeleted file mode 100644 index 55f5b1bec2..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/skipit.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/images/viewlink.gif b/docs/org.eclipse.wst.webtools.doc.user/images/viewlink.gif Binary files differdeleted file mode 100644 index 407b051b28..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/images/viewlink.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/index/_u.cfs b/docs/org.eclipse.wst.webtools.doc.user/index/_u.cfs Binary files differdeleted file mode 100644 index 3a8c50aec6..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/index/_u.cfs +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/index/deletable b/docs/org.eclipse.wst.webtools.doc.user/index/deletable Binary files differdeleted file mode 100644 index e423242b3e..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/index/deletable +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/index/indexed_contributions b/docs/org.eclipse.wst.webtools.doc.user/index/indexed_contributions deleted file mode 100644 index c2b7f40402..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/index/indexed_contributions +++ /dev/null @@ -1,3 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:15:21 EDT 2007
-org.eclipse.wst.webtools.doc.user=org.eclipse.wst.webtools.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.wst.webtools.doc.user/index/indexed_dependencies b/docs/org.eclipse.wst.webtools.doc.user/index/indexed_dependencies deleted file mode 100644 index 9e7fe0edbd..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/index/indexed_dependencies +++ /dev/null @@ -1,4 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:15:21 EDT 2007
-lucene=1.4.103.v20060601
-analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.wst.webtools.doc.user/index/indexed_docs b/docs/org.eclipse.wst.webtools.doc.user/index/indexed_docs deleted file mode 100644 index f39e5f07e7..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/index/indexed_docs +++ /dev/null @@ -1,29 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:15:21 EDT 2007
-/org.eclipse.wst.webtools.doc.user/topics/ccwtover.html=0
-/org.eclipse.wst.webtools.doc.user/topics/tjdetags.html=0
-/org.eclipse.wst.webtools.doc.user/topics/cwebresources.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.html=0
-/org.eclipse.wst.webtools.doc.user/topics/tservertarget.html=0
-/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.html=0
-/org.eclipse.wst.webtools.doc.user/topics/cwservbn.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twprjset.html=0
-/org.eclipse.wst.webtools.doc.user/topics/tjprefs.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twcvsr.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twcreprj.html=0
-/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.html=0
-/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.html=0
-/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.html=0
-/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.html=0
-/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twcresta.html=0
-/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twplib.html=0
-/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twimpwar.html=0
-/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twcrewar.html=0
-/org.eclipse.wst.webtools.doc.user/topics/ccstatic.html=0
-/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.html=0
-/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.html=0
-/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.html=0
diff --git a/docs/org.eclipse.wst.webtools.doc.user/index/segments b/docs/org.eclipse.wst.webtools.doc.user/index/segments Binary files differdeleted file mode 100644 index 19b5d0c420..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/index/segments +++ /dev/null diff --git a/docs/org.eclipse.wst.webtools.doc.user/myplugin.xml b/docs/org.eclipse.wst.webtools.doc.user/myplugin.xml deleted file mode 100644 index 1caf97686e..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/myplugin.xml +++ /dev/null @@ -1,23 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - <plugin> - <extension point="org.eclipse.help.toc"> - <toc file="webtools_toc.xml" /> - <index path="index/"/> - </extension> - - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.wst.webtools.doc.userindex.xml"/> - </extension> - </plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.user.maplist b/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.user.maplist deleted file mode 100644 index d9d52db4ae..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.user.maplist +++ /dev/null @@ -1,8 +0,0 @@ -<maplist version="3.6.2">
- <nav>
- <map file="webtools_toc.ditamap"/>
- </nav>
- <link>
- <map file="relatedlinks.ditamap"/>
- </link>
-</maplist>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.userindex.html b/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.userindex.html deleted file mode 100644 index 86c8662a6f..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.userindex.html +++ /dev/null @@ -1,306 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<meta name="copyright" content="(C) Copyright IBM Corporation 2007" /> -<meta name="security" content="public" /> -<meta name="Robots" content="index,follow" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta name="DC.Format" content="XHTML" /> -<!-- All rights reserved. Licensed Materials Property of IBM --> -<!-- US Government Users Restricted Rights --> -<!-- Use, duplication or disclosure restricted by --> -<!-- GSA ADP Schedule Contract with IBM Corp. --> -<link rel="stylesheet" type="text/css" href="ibmdita.css" /> -<title>Index</title> -</head> -<body> -<h1>Index</h1> -<a name="IDX0_42" href="#IDX1_42">B</a> -<a name="IDX0_43" href="#IDX1_43">C</a> -<a name="IDX0_44" href="#IDX1_44">D</a> -<a name="IDX0_45" href="#IDX1_45">E</a> -<a name="IDX0_46" href="#IDX1_46">F</a> -<a name="IDX0_48" href="#IDX1_48">H</a> -<a name="IDX0_4A" href="#IDX1_4A">J</a> -<a name="IDX0_50" href="#IDX1_50">P</a> -<a name="IDX0_52" href="#IDX1_52">R</a> -<a name="IDX0_53" href="#IDX1_53">S</a> -<a name="IDX0_56" href="#IDX1_56">V</a> -<a name="IDX0_57" href="#IDX1_57">W</a> -<a name="IDX0_58" href="#IDX1_58">X</a> -<hr></hr> -<strong><a name="IDX1_42" href="#IDX0_42">B</a></strong> -<ul class="indexlist"> -<li>build output folders -<ul class="indexlist"> -<li><a href="topics/twcvsr.html#twcvsr">ignoring in CVS</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_43" href="#IDX0_43">C</a></strong> -<ul class="indexlist"> -<li>CVS -<ul class="indexlist"> -<li><a href="topics/twcvsr.html#twcvsr">setting repository defaults</a> -</li> -</ul> -</li> -<li>cvsignore files -<ul class="indexlist"> -<li><a href="topics/twcvsr.html#twcvsr">creating</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_44" href="#IDX0_44">D</a></strong> -<ul class="indexlist"> -<li>DOCTYPE declarations -<ul class="indexlist"> -<li><a href="topics/tjprefs.html#tjprefs">adding automatically</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_45" href="#IDX0_45">E</a></strong> -<ul class="indexlist"> -<li>enterprise applications -<ul class="indexlist"> -<li>projects -<ul class="indexlist"> -<li><a href="topics/ccwebprj.html#ccwebprj">dynamic Web projects</a> -</li> -</ul> -</li> -</ul> -</li> -<li>exporting -<ul class="indexlist"> -<li><a href="topics/twcrewar.html#twcrewar">WAR files</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_46" href="#IDX0_46">F</a></strong> -<ul class="indexlist"> -<li>framesets -<ul class="indexlist"> -<li><a href="topics/tjcrehtm.html#tjcrehtm">creating</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_48" href="#IDX0_48">H</a></strong> -<ul class="indexlist"> -<li>HTML -<ul class="indexlist"> -<li><a href="topics/tjcrehtm.html#tjcrehtm">creating files</a> -</li> -</ul> -</li> -<li>HTML files -<ul class="indexlist"> -<li><a href="topics/tjprefs.html#tjprefs">editing preferences</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_4A" href="#IDX0_4A">J</a></strong> -<ul class="indexlist"> -<li>JSP files -<ul class="indexlist"> -<li><a href="topics/tjcrejsp.html#tjcrejsp">creating</a> -</li> -</ul> -</li> -<li>JSP pages -<ul class="indexlist"> -<li><a href="topics/cpdjsps.html#cpdjsps">overview</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_50" href="#IDX0_50">P</a></strong> -<ul class="indexlist"> -<li>Project Explorer view -<ul class="indexlist"> -<li><a href="topics/ccwebvw.html#ccwebvw">overview</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_52" href="#IDX0_52">R</a></strong> -<ul class="indexlist"> -<li>repositories -<ul class="indexlist"> -<li><a href="topics/twcvsr.html#twcvsr">default CVS settings</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_53" href="#IDX0_53">S</a></strong> -<ul class="indexlist"> -<li>servers -<ul class="indexlist"> -<li><a href="topics/tservertarget.html#tservertarget">targeting</a> -</li> -</ul> -</li> -<li>servlets -<ul class="indexlist"> -<li><a href="topics/twsrvwiz.html#twsrvwiz">creating</a> -</li> -<li><a href="topics/cwservbn.html#cwservbn">overview</a> -</li> -</ul> -</li> -<li>static Web projects -<ul class="indexlist"> -<li><a href="topics/twpcnvrt.html#twpcnvrt">converting to dynamic</a> -</li> -<li><a href="topics/twcresta.html#twcresta">creating</a> -</li> -<li><a href="topics/ccstatic.html#ccstatic">overview</a> -</li> -</ul> -</li> -<li>style sheets -<ul class="indexlist"> -<li><a href="topics/tstylesheet.html#tstylesheet">creating</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_56" href="#IDX0_56">V</a></strong> -<ul class="indexlist"> -<li>virtual JAR files associations -<ul class="indexlist"> -<li><a href="topics/twplib.html#twplib">Web library projects</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_57" href="#IDX0_57">W</a></strong> -<ul class="indexlist"> -<li>WAR files -<ul class="indexlist"> -<li><a href="topics/twcrewar.html#twcrewar">exporting</a> -</li> -<li><a href="topics/twimpwar.html#twimpwar">importing</a> -</li> -<li><a href="topics/cwwarovr.html#cwwarovr">overview</a> -</li> -</ul> -</li> -<li>Web applications -<ul class="indexlist"> -<li><a href="topics/cwebprojects.html#cwebprojects">creating or importing</a> -</li> -<li><a href="topics/ccwtover.html#ccwtover">overview</a> -</li> -<li><a href="topics/twcreprj.html#twcreprj">resources</a> -</li> -<li><a href="topics/tservertarget.html#tservertarget">server targeting</a> -</li> -</ul> -</li> -<li>Web content -<ul class="indexlist"> -<li><a href="topics/cpdjsps.html#cpdjsps">generating dynamically</a> -</li> -</ul> -</li> -<li>Web development -<ul class="indexlist"> -<li><a href="topics/ccwebvw.html#ccwebvw">Project Explorer view</a> -</li> -</ul> -</li> -<li>Web editors -<ul class="indexlist"> -<li><a href="topics/cwwedtvw.html#cwwedtvw">workbench integration</a> -</li> -</ul> -</li> -<li>Web library projects -<ul class="indexlist"> -<li><a href="topics/twplib.html#twplib">virtual JAR files and projects</a> -</li> -</ul> -</li> -<li>Web page design -<ul class="indexlist"> -<li><a href="topics/cwebpagedesign.html#cwebpagedesign">overview</a> -</li> -</ul> -</li> -<li>Web pages -<ul class="indexlist"> -<li><a href="topics/tjdetags.html#tjdetags">creating</a> -</li> -</ul> -</li> -<li>Web perspective -<ul class="indexlist"> -<li><a href="topics/ccwebvw.html#ccwebvw">Project Explorer view</a> -</li> -</ul> -</li> -<li>Web projects -<ul class="indexlist"> -<li><a href="topics/twpcnvrt.html#twpcnvrt">converting static to dynamic</a> -</li> -<li><a href="topics/twcreprj.html#twcreprj">creating dynamic projects</a> -</li> -<li><a href="topics/twcresta.html#twcresta">creating static</a> -</li> -<li><a href="topics/ccwebprj.html#ccwebprj">dynamic projects overview</a> -</li> -<li><a href="topics/twcrewar.html#twcrewar">exporting WAR files</a> -</li> -<li><a href="topics/cwebprojects.html#cwebprojects">overview</a> -</li> -<li><a href="topics/twprjset.html#twprjset">properties settings</a> -</li> -<li><a href="topics/ccstatic.html#ccstatic">static</a> -</li> -</ul> -</li> -<li>Web resources -<ul class="indexlist"> -<li><a href="topics/cwebresources.html#cwebresources">overview</a> -</li> -</ul> -</li> -<li>Web servers -<ul class="indexlist"> -<li><a href="topics/cwservbn.html#cwservbn">generating dynamic content</a> -</li> -</ul> -</li> -<li>Web tools -<ul class="indexlist"> -<li><a href="topics/cwtfeatures.html#cwtfeatures">features</a> -</li> -</ul> -</li> -<li>WML -<ul class="indexlist"> -<li><a href="topics/tjcrehtm.html#tjcrehtm">creating files</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_58" href="#IDX0_58">X</a></strong> -<ul class="indexlist"> -<li>XHTML -<ul class="indexlist"> -<li><a href="topics/tjcrehtm.html#tjcrehtm">creating files</a> -</li> -</ul> -</li> -</ul> -</body></html> diff --git a/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.userindex.xml b/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.userindex.xml deleted file mode 100644 index 83ed10a96b..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/org.eclipse.wst.webtools.doc.userindex.xml +++ /dev/null @@ -1,215 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<index> - <entry keyword="Web applications"> - <entry keyword="overview"> - <topic href="topics/ccwtover.html#ccwtover" title="Web application overview"/> - </entry> - <entry keyword="creating or importing"> - <topic href="topics/cwebprojects.html#cwebprojects" title="Web projects"/> - </entry> - <entry keyword="resources"> - <topic href="topics/twcreprj.html#twcreprj" title="Creating a dynamic Web project"/> - </entry> - <entry keyword="server targeting"> - <topic href="topics/tservertarget.html#tservertarget" title="Server targeting for Web applications"/> - </entry> - </entry> - <entry keyword="Web tools"> - <entry keyword="features"> - <topic href="topics/cwtfeatures.html#cwtfeatures" title="Web tools features"/> - </entry> - </entry> - <entry keyword="Project Explorer view"> - <entry keyword="overview"> - <topic href="topics/ccwebvw.html#ccwebvw" title="Project Explorer view and Web development"/> - </entry> - </entry> - <entry keyword="Web development"> - <entry keyword="Project Explorer view"> - <topic href="topics/ccwebvw.html#ccwebvw" title="Project Explorer view and Web development"/> - </entry> - </entry> - <entry keyword="Web perspective"> - <entry keyword="Project Explorer view"> - <topic href="topics/ccwebvw.html#ccwebvw" title="Project Explorer view and Web development"/> - </entry> - </entry> - <entry keyword="Web resources"> - <entry keyword="overview"> - <topic href="topics/cwebresources.html#cwebresources" title="Web resources"/> - </entry> - </entry> - <entry keyword="Web page design"> - <entry keyword="overview"> - <topic href="topics/cwebpagedesign.html#cwebpagedesign" title="Web page design"/> - </entry> - </entry> - <entry keyword="Web projects"> - <entry keyword="overview"> - <topic href="topics/cwebprojects.html#cwebprojects" title="Web projects"/> - </entry> - <entry keyword="creating dynamic projects"> - <topic href="topics/twcreprj.html#twcreprj" title="Creating a dynamic Web project"/> - </entry> - <entry keyword="dynamic projects overview"> - <topic href="topics/ccwebprj.html#ccwebprj" title="Dynamic Web projects and applications"/> - </entry> - <entry keyword="creating static"> - <topic href="topics/twcresta.html#twcresta" title="Creating a static Web project"/> - </entry> - <entry keyword="converting static to dynamic"> - <topic href="topics/twpcnvrt.html#twpcnvrt" title="Converting static Web projects to dynamic Web projects"/> - </entry> - <entry keyword="static"> - <topic href="topics/ccstatic.html#ccstatic" title="Static Web projects"/> - </entry> - <entry keyword="exporting WAR files"> - <topic href="topics/twcrewar.html#twcrewar" title="Exporting Web Archive (WAR) files"/> - </entry> - <entry keyword="properties settings"> - <topic href="topics/twprjset.html#twprjset" title="Setting Web project properties"/> - </entry> - </entry> - <entry keyword="WAR files"> - <entry keyword="overview"> - <topic href="topics/cwwarovr.html#cwwarovr" title="Web archive (WAR) files"/> - </entry> - <entry keyword="importing"> - <topic href="topics/twimpwar.html#twimpwar" title="Importing Web archive (WAR) files"/> - </entry> - <entry keyword="exporting"> - <topic href="topics/twcrewar.html#twcrewar" title="Exporting Web Archive (WAR) files"/> - </entry> - </entry> - <entry keyword="enterprise applications"> - <entry keyword="projects"> - <entry keyword="dynamic Web projects"> - <topic href="topics/ccwebprj.html#ccwebprj" title="Dynamic Web projects and applications"/> - </entry> - </entry> - </entry> - <entry keyword="static Web projects"> - <entry keyword="creating"> - <topic href="topics/twcresta.html#twcresta" title="Creating a static Web project"/> - </entry> - <entry keyword="converting to dynamic"> - <topic href="topics/twpcnvrt.html#twpcnvrt" title="Converting static Web projects to dynamic Web projects"/> - </entry> - <entry keyword="overview"> - <topic href="topics/ccstatic.html#ccstatic" title="Static Web projects"/> - </entry> - </entry> - <entry keyword="exporting"> - <entry keyword="WAR files"> - <topic href="topics/twcrewar.html#twcrewar" title="Exporting Web Archive (WAR) files"/> - </entry> - </entry> - <entry keyword="Web library projects"> - <entry keyword="virtual JAR files and projects"> - <topic href="topics/twplib.html#twplib" title="Adding Web library projects"/> - </entry> - </entry> - <entry keyword="virtual JAR files associations"> - <entry keyword="Web library projects"> - <topic href="topics/twplib.html#twplib" title="Adding Web library projects"/> - </entry> - </entry> - <entry keyword="Web editors"> - <entry keyword="workbench integration"> - <topic href="topics/cwwedtvw.html#cwwedtvw" title="Workbench integration with Web editors"/> - </entry> - </entry> - <entry keyword="Web pages"> - <entry keyword="creating"> - <topic href="topics/tjdetags.html#tjdetags" title="Creating and editing Web pages - overview"/> - </entry> - </entry> - <entry keyword="framesets"> - <entry keyword="creating"> - <topic href="topics/tjcrehtm.html#tjcrehtm" title="Creating HTML and XHTML files and framesets"/> - </entry> - </entry> - <entry keyword="HTML"> - <entry keyword="creating files"> - <topic href="topics/tjcrehtm.html#tjcrehtm" title="Creating HTML and XHTML files and framesets"/> - </entry> - </entry> - <entry keyword="WML"> - <entry keyword="creating files"> - <topic href="topics/tjcrehtm.html#tjcrehtm" title="Creating HTML and XHTML files and framesets"/> - </entry> - </entry> - <entry keyword="XHTML"> - <entry keyword="creating files"> - <topic href="topics/tjcrehtm.html#tjcrehtm" title="Creating HTML and XHTML files and framesets"/> - </entry> - </entry> - <entry keyword="DOCTYPE declarations"> - <entry keyword="adding automatically"> - <topic href="topics/tjprefs.html#tjprefs" title="Defining HTML file preferences"/> - </entry> - </entry> - <entry keyword="HTML files"> - <entry keyword="editing preferences"> - <topic href="topics/tjprefs.html#tjprefs" title="Defining HTML file preferences"/> - </entry> - </entry> - <entry keyword="style sheets"> - <entry keyword="creating"> - <topic href="topics/tstylesheet.html#tstylesheet" title="Creating cascading style sheets"/> - </entry> - </entry> - <entry keyword="servlets"> - <entry keyword="creating"> - <topic href="topics/twsrvwiz.html#twsrvwiz" title="Creating servlets"/> - </entry> - <entry keyword="overview"> - <topic href="topics/cwservbn.html#cwservbn" title="Servlets"/> - </entry> - </entry> - <entry keyword="Web servers"> - <entry keyword="generating dynamic content"> - <topic href="topics/cwservbn.html#cwservbn" title="Servlets"/> - </entry> - </entry> - <entry keyword="JSP files"> - <entry keyword="creating"> - <topic href="topics/tjcrejsp.html#tjcrejsp" title="Creating JavaServer Pages (JSP) files"/> - </entry> - </entry> - <entry keyword="JSP pages"> - <entry keyword="overview"> - <topic href="topics/cpdjsps.html#cpdjsps" title="JavaServer Pages (JSP) technology"/> - </entry> - </entry> - <entry keyword="Web content"> - <entry keyword="generating dynamically"> - <topic href="topics/cpdjsps.html#cpdjsps" title="JavaServer Pages (JSP) technology"/> - </entry> - </entry> - <entry keyword="build output folders"> - <entry keyword="ignoring in CVS"> - <topic href="topics/twcvsr.html#twcvsr" title="Setting CVS repository defaults"/> - </entry> - </entry> - <entry keyword="CVS"> - <entry keyword="setting repository defaults"> - <topic href="topics/twcvsr.html#twcvsr" title="Setting CVS repository defaults"/> - </entry> - </entry> - <entry keyword="cvsignore files"> - <entry keyword="creating"> - <topic href="topics/twcvsr.html#twcvsr" title="Setting CVS repository defaults"/> - </entry> - </entry> - <entry keyword="repositories"> - <entry keyword="default CVS settings"> - <topic href="topics/twcvsr.html#twcvsr" title="Setting CVS repository defaults"/> - </entry> - </entry> - <entry keyword="servers"> - <entry keyword="targeting"> - <topic href="topics/tservertarget.html#tservertarget" title="Server targeting for Web applications"/> - </entry> - </entry> -</index>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/plugin.properties b/docs/org.eclipse.wst.webtools.doc.user/plugin.properties deleted file mode 100644 index acba0268b1..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/plugin.properties +++ /dev/null @@ -1,13 +0,0 @@ -############################################################################### -# Copyright (c) 2001, 2004 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### - -pluginName = Web tools documentation -providerName = Eclipse.org
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/plugin.xml b/docs/org.eclipse.wst.webtools.doc.user/plugin.xml deleted file mode 100644 index 1caf97686e..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/plugin.xml +++ /dev/null @@ -1,23 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - <plugin> - <extension point="org.eclipse.help.toc"> - <toc file="webtools_toc.xml" /> - <index path="index/"/> - </extension> - - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.wst.webtools.doc.userindex.xml"/> - </extension> - </plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/relatedlinks.ditamap b/docs/org.eclipse.wst.webtools.doc.user/relatedlinks.ditamap deleted file mode 100644 index 2a26dfff7e..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/relatedlinks.ditamap +++ /dev/null @@ -1,447 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE map PUBLIC "-//IBM//DTD DITA IBM Map//EN"
- "ibm-map.dtd">
-<map title="Web tools related links"><?Pub Caret1?>
-<reltable>
-<relheader>
-<relcolspec type="concept"></relcolspec>
-<relcolspec type="task"></relcolspec>
-<relcolspec type="reference"></relcolspec>
-</relheader>
-<relrow>
-<relcell></relcell>
-<relcell></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell>
-<topicref href="topics/tjchgxdt.dita" navtitle="Specifying an implicit document type for an HTML, XHTML, or JSP fragment">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjcrehtm.dita" navtitle="Creating HTML and XHTML files and framesets">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/cpdjsps.dita" linking="targetonly" navtitle="JavaServer Pages (JSP) technology"
-scope="peer"></topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjcrejsp.dita" navtitle="Creating JavaServer Pages (JSP) files">
-</topicref>
-<topicref href="topics/twcreprj.dita" linking="targetonly" navtitle="Creating a dynamic Web project">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell collection-type="family">
-<topicref href="topics/tservertarget.dita" navtitle="Server targeting for Web applications">
-</topicref>
-<topicref href="topics/twcreprj.dita" linking="targetonly" navtitle="Creating a dynamic Web project">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/ccstatic.dita" navtitle="Static Web projects" scope="peer">
-</topicref>
-<topicref href="topics/ccwebprj.dita" navtitle="Dynamic Web projects and applications"
-scope="peer"></topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/twcreprj.dita" navtitle="Creating a dynamic Web project">
-</topicref>
-<topicref href="topics/tjcrejsp.dita" linking="targetonly" navtitle="Creating JavaServer Pages (JSP) files">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/ccstatic.dita" navtitle="Static Web projects" scope="peer">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/twcresta.dita" navtitle="Creating a static Web project">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/cwwarovr.dita" navtitle="Web archive (WAR) files" scope="peer">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/twcrewar.dita" navtitle="Exporting Web Archive (WAR) files">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell>
-<topicref href="topics/twcvsr.dita" navtitle="Setting CVS repository defaults"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/cwwarovr.dita" navtitle="Web archive (WAR) files" scope="peer">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/twimpwar.dita" navtitle="Importing Web archive (WAR) files">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell collection-type="family"></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/ccstatic.dita" navtitle="Static Web projects" scope="peer">
-</topicref>
-<topicref href="topics/ccwebprj.dita" navtitle="Dynamic Web projects and applications"
-scope="peer"></topicref>
-</relcell>
-<relcell>
-<topicref href="topics/twpcnvrt.dita" navtitle="Converting static Web projects to dynamic Web projects">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell>
-<topicref href="topics/twplib.dita" navtitle="Adding Web library projects">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell>
-<topicref href="topics/twprjset.dita" navtitle="Setting Web project properties">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwservbn.dita" linking="targetonly" navtitle="Servlets"
-scope="peer"></topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/twsrvwiz.dita" navtitle="Creating servlets"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/ccwebvw.dita" navtitle="Project Explorer view and Web development">
-</topicref>
-</relcell>
-<relcell></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwebprojects.dita" navtitle="Web projects" scope="peer">
-</topicref>
-<topicref href="topics/ccwtover.dita" navtitle="Web application overview"
-scope="peer"></topicref>
-<topicref href="topics/cpdjsps.dita" navtitle="JavaServer Pages (JSP) technology"
-scope="peer"></topicref>
-</relcell>
-<relcell>
-<topicref href="topics/twimpwar.dita" linking="targetonly" navtitle="Importing Web archive (WAR) files">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/ccwtover.dita" navtitle="Web application overview">
-</topicref>
-<topicref href="topics/cwtfeatures.dita" linking="targetonly" navtitle="Web tools features">
-</topicref>
-<!-- <topicref href="topics/cwebdevelopmenttools.dita" linking="targetonly" navtitle="Web development tools">
-</topicref> -->
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/twcreprj.dita" linking="targetonly" navtitle="Creating a dynamic Web project"
-scope="peer">
-<topicref href="topics/tjdetags.dita" linking="targetonly" navtitle="Creating and editing Web pages - overview">
-</topicref>
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwtfeatures.dita" navtitle="Web tools features"></topicref>
-<!-- <topicref href="topics/cwebdevelopmenttools.dita" linking="targetonly" navtitle="Web development tools">
-</topicref> -->
-<topicref href="topics/ccwebprj.dita" linking="targetonly" navtitle="Dynamic Web projects and applications">
-</topicref>
-<topicref href="topics/cwebpagedesign.dita" linking="targetonly" navtitle="Web page design">
-</topicref>
-<!-- <topicref href="topics/cwebtechnologies.dita" linking="targetonly" navtitle="Web technologies">
-</topicref> -->
-</relcell>
-<relcell>
-<topicref href="topics/twcreprj.dita" linking="targetonly" navtitle="Creating a dynamic Web project"
-scope="peer"></topicref>
-<topicref href="topics/tjcrejsp.dita" linking="targetonly" navtitle="Creating JavaServer Pages (JSP) files"
-scope="peer"></topicref>
-<topicref href="topics/twsrvwiz.dita" linking="targetonly" navtitle="Creating servlets"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<!-- <topicref href="topics/cwebtechnologies.dita" navtitle="Web technologies">
-</topicref> -->
-<topicref href="topics/ccwebprj.dita" linking="targetonly" navtitle="Dynamic Web projects and applications">
-</topicref>
-<topicref href="topics/cpdjsps.dita" linking="targetonly" navtitle="JavaServer Pages (JSP) technology">
-</topicref>
-</relcell>
-<relcell></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cpdjsps.dita" navtitle="JavaServer Pages (JSP) technology">
-</topicref>
-<topicref href="topics/cwservbn.dita" linking="targetonly" navtitle="Servlets">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjcrejsp.dita" linking="targetonly" navtitle="Creating JavaServer Pages (JSP) files"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwservbn.dita" navtitle="Servlets"></topicref>
-<topicref href="topics/ccwtover.dita" linking="targetonly" navtitle="Web application overview">
-</topicref>
-<!-- <topicref href="topics/cwebdevelopmenttools.dita" linking="targetonly" navtitle="Web development tools">
-</topicref> -->
-</relcell>
-<relcell>
-<topicref href="topics/twsrvwiz.dita" linking="targetonly" navtitle="Creating servlets"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<!-- <topicref href="topics/cwebdevelopmenttools.dita" navtitle="Web development tools">
-</topicref> -->
-<topicref href="topics/ccstatic.dita" linking="targetonly" navtitle="Static Web projects">
-</topicref>
-<topicref href="topics/ccwebprj.dita" linking="targetonly" navtitle="Dynamic Web projects and applications">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/twcresta.dita" linking="targetonly" navtitle="Creating a static Web project"
-scope="peer"></topicref>
-<topicref href="topics/twcreprj.dita" linking="targetonly" navtitle="Creating a dynamic Web project"
-scope="peer"></topicref>
-<topicref href="topics/tjcrehtm.dita" linking="targetonly" navtitle="Creating HTML and XHTML files and framesets"
-scope="peer"></topicref>
-<topicref href="topics/tjcrejsp.dita" linking="targetonly" navtitle="Creating JavaServer Pages (JSP) files"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/ccwtover.dita" linking="targetonly" navtitle="Web application overview">
-</topicref>
-<topicref href="topics/cwwedtvw.dita" linking="targetonly" navtitle="Workbench integration with Web editors">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/tjprefs.dita" linking="targetonly" navtitle="Defining HTML file preferences">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cpdjsps.dita" linking="targetonly" navtitle="JavaServer Pages (JSP) technology">
-</topicref>
-</relcell>
-<relcell collection-type="family"></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwebprojects.dita" navtitle="Web projects"></topicref>
-<topicref href="topics/ccstatic.dita" linking="targetonly" navtitle="Static Web projects">
-</topicref>
-<topicref href="topics/ccwebprj.dita" linking="targetonly" navtitle="Dynamic Web projects and applications">
-</topicref>
-<topicref href="topics/cwwarovr.dita" linking="targetonly" navtitle="Web archive (WAR) files">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/twcresta.dita" linking="targetonly" navtitle="Creating a static Web project"
-scope="peer"></topicref>
-<topicref href="topics/twcreprj.dita" linking="targetonly" navtitle="Creating a dynamic Web project"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/ccstatic.dita" navtitle="Static Web projects"></topicref>
-<topicref href="topics/cwebresources.dita" linking="targetonly" navtitle="Web resources">
-</topicref>
-<topicref href="topics/cwwarovr.dita" linking="targetonly" navtitle="Web archive (WAR) files">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/twcresta.dita" linking="targetonly" navtitle="Creating a static Web project"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/ccwebprj.dita" navtitle="Dynamic Web projects and applications">
-</topicref>
-<topicref href="topics/cwebresources.dita" linking="targetonly" navtitle="Web resources">
-</topicref>
-<topicref href="topics/cwwarovr.dita" linking="targetonly" navtitle="Web archive (WAR) files">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/twcreprj.dita" linking="targetonly" navtitle="Creating a dynamic Web project"
-scope="peer"></topicref>
-<topicref href="topics/tjcrejsp.dita" linking="targetonly" navtitle="Creating JavaServer Pages (JSP) files"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwebpagedesign.dita" navtitle="Web page design"></topicref>
-<!-- <topicref href="topics/cwebdevelopmenttools.dita" linking="targetonly" navtitle="Web development tools">
-</topicref> -->
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjdetags.dita" linking="targetonly" navtitle="Creating and editing Web pages - overview">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwebresources.dita" navtitle="Web resources"></topicref>
-<topicref href="topics/cwwarovr.dita" linking="targetonly" navtitle="Web archive (WAR) files">
-</topicref>
-</relcell>
-<relcell collection-type="family"></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwwedtvw.dita" navtitle="Workbench integration with Web editors">
-</topicref>
-<!-- <topicref href="topics/cwebdevelopmenttools.dita" linking="targetonly" navtitle="Web development tools">
-</topicref> -->
-</relcell>
-<relcell></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwebresources.dita" linking="targetonly" navtitle="Web resources">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/tjcrejsp.dita" linking="targetonly" navtitle="Creating JavaServer Pages (JSP) files"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell collection-type="family">
-<topicref href="topics/cwwarovr.dita" navtitle="Web archive (WAR) files">
-</topicref>
-<topicref href="topics/cwebresources.dita" linking="targetonly" navtitle="Web resources">
-</topicref>
-</relcell>
-<relcell>
-<topicref href="topics/twimpwar.dita" linking="targetonly" navtitle="Importing Web archive (WAR) files"
-scope="peer"></topicref>
-<topicref href="topics/twcrewar.dita" linking="targetonly" navtitle="Exporting Web Archive (WAR) files"
-scope="peer"></topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<topicref href="topics/cwebresources.dita" linking="targetonly" navtitle="Web resources">
-</topicref>
-</relcell>
-<relcell collection-type="family"></relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell>
-<!-- <topicref href="topics/cwebdevelopmenttools.dita" linking="targetonly" navtitle="Web development tools">
-</topicref> -->
-<topicref href="topics/ccwtover.dita" linking="targetonly" navtitle="Web application overview">
-</topicref>
-</relcell>
-<relcell collection-type="family">
-<topicref href="topics/tjdetags.dita" navtitle="Creating and editing Web pages - overview">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-<relrow>
-<relcell></relcell>
-<relcell>
-<topicref href="topics/tjprefs.dita" navtitle="Defining HTML file preferences">
-</topicref>
-</relcell>
-<relcell></relcell>
-</relrow>
-</reltable>
-</map>
-<?Pub *0000014944?>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.dita deleted file mode 100644 index 7e809fbf88..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.dita +++ /dev/null @@ -1,63 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="ccstatic" xml:lang="en-us">
-<title>Static Web projects</title>
-<prolog><metadata>
-<keywords><indexterm>Web projects<indexterm>static</indexterm></indexterm>
-<indexterm>static Web projects<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>If you want to create a content-based Web application that does not contain
-any dynamic content (such as servlets, JSP files, filters, and associated
-metadata) you might prefer to create a static Web project, as opposed to a <xref
-href="ccwebprj.dita" scope="peer"><desc></desc>dynamic Web project</xref>.</p>
-<p>Static Web projects have the following characteristics: <ul>
-<li>a Web content folder (called WebContent) for all publishable resources,
-You can change the name of this folder from the project's pop-up menu.</li>
-<li>a Theme folder, the suggested directory for storing cascading style sheets
-and other style-related objects.</li>
-<li>the ability to define folders outside of the Web content folder, for storing
-intermediate files, such as MIF files</li>
-<li>a conversion path from a static Web project to a dynamic Web project.
-If you decide to <xref href="twpcnvrt.dita" scope="peer"><desc></desc>convert</xref> the
-project, it will be a fully-valid dynamic Web project. </li>
-</ul></p>
-<p>In addition, your project will still have the following features (which
-are common to both static and dynamic Web projects ) : <ul>
-<li>HTML syntax validation</li>
-<li>a broken link fix-up wizard</li>
-<li>a Web site navigation tool</li>
-<li>a new server type, the Static Web server, which makes it easy to publish
-static Web projects</li>
-</ul> </p>
-<p>The folder that a static Web project is published to is modifiable, so
-that when you set the publishing "root" value (called a <i>context root</i>),
-such as <codeph>/web1</codeph>, for a static project, everything in the Web
-content folder will be published to the <filepath>web1</filepath> folder under
-the Web server's doc root. This enables you to group Web resources on a Web
-server in folders that correspond to Web projects in the workbench. When projects
-defined in this way are ready for production, you can publish specific projects
-directly to the doc root by changing the value to <codeph>/</codeph> and all
-publishing, link fixing, and browsing will update automatically.</p>
-<p>Aliases can also be used to specify a context root value. For example,
-suppose that there is an alias that is defined on the target Web server, as
-follows: <codeblock>Alias /scripts/ "/var/www/scripts"</codeblock>In this
-example, in which the current static Web project will contain common <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="JavaScript">JavaScript</tm> files,
-you can set the context root value to be <ph>"scripts"</ph>. In order for
-the resources in the static Web project to be published to the correct location
-on the Web server, you must add this Alias mapping to the server tools instance
-of the static Web server, as follows. <ol>
-<li>From the Server view, double-click on the static Web server configuration
-to open the server configuration editor.<note>This assumes that you've already
-defined the static Web server.</note></li>
-<li>Click the <uicontrol>Configuration</uicontrol> editor tab.</li>
-<li>Scroll down to the <uicontrol>Alias Path Mapping</uicontrol> section,
-and add the new Alias mapping.</li>
-</ol>Now that <ph>"scripts"</ph> is defined as an Alias, the Web content in
-the static Web project will be published to the mapped path, <filepath>/var/www/scripts</filepath>.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.html b/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.html deleted file mode 100644 index ae164c9504..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/ccstatic.html +++ /dev/null @@ -1,99 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Static Web projects" /> -<meta content="Web projects, static, static Web projects, overview" name="DC.subject" /> -<meta content="Web projects, static, static Web projects, overview" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ccstatic" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Static Web projects</title> -</head> -<body id="ccstatic"><a name="ccstatic"><!-- --></a> - - -<h1 class="topictitle1">Static Web projects</h1> - - -<div> -<p>If you want to create a content-based Web application that does not contain -any dynamic content (such as servlets, JSP files, filters, and associated -metadata) you might prefer to create a static Web project, as opposed to a <a href="ccwebprj.html" title="">dynamic Web project</a>.</p> - -<div class="p">Static Web projects have the following characteristics: <ul> -<li>a Web content folder (called WebContent) for all publishable resources, -You can change the name of this folder from the project's pop-up menu.</li> - -<li>a Theme folder, the suggested directory for storing cascading style sheets -and other style-related objects.</li> - -<li>the ability to define folders outside of the Web content folder, for storing -intermediate files, such as MIF files</li> - -<li>a conversion path from a static Web project to a dynamic Web project. -If you decide to <a href="twpcnvrt.html" title="">convert</a> the -project, it will be a fully-valid dynamic Web project. </li> - -</ul> -</div> - -<div class="p">In addition, your project will still have the following features (which -are common to both static and dynamic Web projects ) : <ul> -<li>HTML syntax validation</li> - -<li>a broken link fix-up wizard</li> - -<li>a Web site navigation tool</li> - -<li>a new server type, the Static Web server, which makes it easy to publish -static Web projects</li> - -</ul> - </div> - -<p>The folder that a static Web project is published to is modifiable, so -that when you set the publishing "root" value (called a <em>context root</em>), -such as <samp class="codeph">/web1</samp>, for a static project, everything in the Web -content folder will be published to the <span class="filepath">web1</span> folder under -the Web server's doc root. This enables you to group Web resources on a Web -server in folders that correspond to Web projects in the workbench. When projects -defined in this way are ready for production, you can publish specific projects -directly to the doc root by changing the value to <samp class="codeph">/</samp> and all -publishing, link fixing, and browsing will update automatically.</p> - -<div class="p">Aliases can also be used to specify a context root value. For example, -suppose that there is an alias that is defined on the target Web server, as -follows: <pre>Alias /scripts/ "/var/www/scripts"</pre> -In this -example, in which the current static Web project will contain common JavaScriptâ„¢ files, -you can set the context root value to be <span>"scripts"</span>. In order for -the resources in the static Web project to be published to the correct location -on the Web server, you must add this Alias mapping to the server tools instance -of the static Web server, as follows. <ol> -<li>From the Server view, double-click on the static Web server configuration -to open the server configuration editor.<div class="note"><span class="notetitle">Note:</span> This assumes that you've already -defined the static Web server.</div> -</li> - -<li>Click the <span class="uicontrol">Configuration</span> editor tab.</li> - -<li>Scroll down to the <span class="uicontrol">Alias Path Mapping</span> section, -and add the new Alias mapping.</li> - -</ol> -Now that <span>"scripts"</span> is defined as an Alias, the Web content in -the static Web project will be published to the mapped path, <span class="filepath">/var/www/scripts</span>.</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.dita deleted file mode 100644 index ade1bbbb58..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.dita +++ /dev/null @@ -1,140 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="ccwebprj" xml:lang="en-us">
-<title>Dynamic Web projects and applications</title>
-<prolog><metadata>
-<keywords><indexterm>enterprise applications<indexterm>projects<indexterm>dynamic Web projects</indexterm></indexterm></indexterm>
-<indexterm>Web projects<indexterm>dynamic projects overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>There are two types of Web projects: dynamic and <xref href="ccstatic.dita"
-scope="peer"><desc></desc>static</xref>. Dynamic web projects can contain
-dynamic J2EE resources such as servlets, JSP files, filters, and associated
-metadata, in addition to static resources such as images and HTML files. Static
-web projects only contains static resources. When you create Web projects,
-you can include cascading style sheets and JSP tag libraries (for dynamic
-Web projects), so that you can begin development with a richer set of project
-resources.</p>
-<p>Dynamic Web projects are always imbedded in Enterprise Application projects.
-The wizard that you use to create a dynamic Web project will also create an
-Enterprise Application (EAR) project if it does not already exist. The wizard
-will also update the <filepath>application.xml</filepath> deployment descriptor
-of the specified Enterprise Application project to define the Web project
-as a module element. If you are importing a WAR file rather than creating
-a dynamic Web project new, the WAR Import wizard requires that you specify
-a Web project, which already requires an EAR project. </p>
-<p>J2EE conventions may represent extra overhead if you only want to create
-a static, content-based Web application, which contains no dynamic files,
-such as JSP files or servlets. In this case, when you need only the most basic
-Web project, you might want to use the <i>static</i> Web project type (see <xref
-href="ccstatic.dita" scope="peer"><desc></desc>Static Web projects</xref>).
- Note that static Web projects can be converted to dynamic Web projects by
-selecting <b>Convert to a Dynamic Web Project</b>, from the Project menu.</p>
-<p>The J2EE model, and more specifically, the <cite>Sun Microsystems <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Servlet
-2.3 Specification</cite>, defines a Web application directory structure that
-specifies the location of Web content files, class files, class paths, deployment
-descriptors, and supporting metadata. The Web project hierarchy mirrors that
-of the Web application created from a project. In the workbench, you can use
-the <ph>New Web Project</ph> wizard to create a new Web project.</p>
-<p>The main project folder contains all development objects related to a Web
-application. The Web content folder contains the elements of the project necessary
-to create a Web application. This folder structure maps to the Web application
-archive (WAR) structure defined by Sun Microsystems.. The following default
-elements are located in the Web project folder hierarchy: <note>In the Project
-Explorer view, Web projects are filtered into folder nodes to customize the
-display of Web resources for easy management during development. For information
-on the filtered structure, see <xref href="ccwebvw.dita" scope="peer"><desc></desc>Project
-Explorer view</xref>.</note><dl><dlentry>
-<dt>Web Deployment Descriptor</dt>
-<dd>The standard Web application deployment descriptor (the <filepath>web.xml</filepath> file).</dd>
-</dlentry><dlentry>
-<dt>JavaSource</dt>
-<dd>Contains the project's <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> source code for classes, beans, and
-servlets. When these resources are added to a Web project, they are automatically
-compiled and the generated files are added to the WEB-INF/classes directory.
-The contents of the source directory are not packaged in WAR files unless
-an option is specified when a WAR file is created. <note>Though the default
-name given to the folder is JavaSources, you can change the name by right
-clicking on the name in the Project Explorer and clicking on <menucascade>
-<uicontrol>Refactor</uicontrol><uicontrol>Rename</uicontrol></menucascade>.</note></dd>
-</dlentry><dlentry>
-<dt>imported_classes folder</dt>
-<dd>This folder may be created during a WAR import, and contains class files
-that do not have accompanying source. The <uicontrol>imported_classes</uicontrol> folder
-is a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> classes
-folder; <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> classes folders can also be created using the Web
-project <uicontrol>Java Build Path</uicontrol> properties page.</dd>
-</dlentry><dlentry>
-<dt>WebContent folder</dt>
-<dd>The mandatory location of all Web resources, including HTML, JSP, graphic
-files, and so on. If the files are not placed in this directory (or in a subdirectory
-structure under this directory), the files will not be available when the
-application is executed on a server. The Web content folder represents the
-contents of the WAR file that will be deployed to the server. Any files not
-under the Web content folder are considered development-time resources (for
-example, .java files, .sql files, and .mif files), and are not deployed when
-the project is unit tested or published. <note>Though the default name given
-to the folder is <filepath>WebContent</filepath>, you can change the name
- in the Project Explorer by right-clicking the folder and selecting <uicontrol>Refactor</uicontrol><uicontrol>Rename</uicontrol> or
-from the Web page of the project's Properties dialog. In a dynamic Web project,
-changing the folder name will update the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> build output directory. </note></dd>
-</dlentry><dlentry>
-<dt>META-INF</dt>
-<dd>This directory contains the <filepath>MANIFEST.MF</filepath> file, which
-is used to map class paths for dependent JAR files that exist in other projects
-in the same Enterprise Application project. An entry in this file will update
-the run-time project class path and <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> build settings to include the referenced
-JAR files.</dd>
-</dlentry><dlentry>
-<dt>theme</dt>
-<dd>The suggested directory for cascading style sheets and other style-related
-objects.</dd>
-</dlentry><dlentry>
-<dt>WEB-INF</dt>
-<dd>Based on the <cite>Sun Microsystems <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> Servlet 2.3 Specification</cite>, this
-directory contains the supporting Web resources for a Web application, including
-the <filepath>web.xml</filepath> file and the classes and lib directories.</dd>
-</dlentry><dlentry>
-<dt>/classes</dt>
-<dd>This directory is for servlets, utility classes, and the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> compiler
-output directory. The classes in this directory are used by the application
-class loader to load the classes. Folders in this directory will map package
-and class names, as in: <codeph>/WEB-INF/classes/com/mycorp/servlets/MyServlet.class</codeph>.<p>Do
-not place any .class files directly into this directory. The .class files
-are placed in this directory automatically when the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> compiler
-compiles <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> source files that are in the <filepath>Java Resources</filepath> directory.
-Any files placed directly in this directory will be deleted by the <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> compiler
-when it runs.</p></dd>
-</dlentry><dlentry>
-<dt>/lib</dt>
-<dd>The supporting JAR files that your Web application references. Any classes
-in .jar files placed in this directory will be available for your Web application</dd>
-</dlentry><dlentry>
-<dt>Libraries</dt>
-<dd>The supporting JAR files that your Web application references. This folder
-mirrors the content of the lib folder. In addition, Web Library Projects,
-which are "virtual" JAR files that do not physically reside in the Web project,
-but are associated with <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> projects elsewhere in your workspace,
-are included in this folder. They are packaged with your project when you
-export the application's WAR file.</dd>
-</dlentry></dl> <note>A library entry on the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> build path will remain there unless
-the actual JAR file is deleted from the WEB-INF/lib folder. If you remove
-a library path entry but not the JAR file, the library entry will be re-added
-to the path automatically.</note></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.html b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.html deleted file mode 100644 index 9ac3b45deb..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebprj.html +++ /dev/null @@ -1,173 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Dynamic Web projects and applications" /> -<meta content="Web projects, dynamic, overview, dynamic Web projects" name="DC.subject" /> -<meta content="Web projects, dynamic, overview, dynamic Web projects" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ccwebprj" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Dynamic Web projects and applications</title> -</head> -<body id="ccwebprj"><a name="ccwebprj"><!-- --></a> - - -<h1 class="topictitle1">Dynamic Web projects and applications</h1> - - -<div> -<p>There are two types of Web projects: dynamic and <a href="ccstatic.html" title="">static</a>. Dynamic web projects can contain -dynamic J2EE resources such as servlets, JSP files, filters, and associated -metadata, in addition to static resources such as images and HTML files. Static -web projects only contains static resources. When you create Web projects, -you can include cascading style sheets and JSP tag libraries (for dynamic -Web projects), so that you can begin development with a richer set of project -resources.</p> - -<p>Dynamic Web projects are always imbedded in Enterprise Application projects. -The wizard that you use to create a dynamic Web project will also create an -Enterprise Application (EAR) project if it does not already exist. The wizard -will also update the <span class="filepath">application.xml</span> deployment descriptor -of the specified Enterprise Application project to define the Web project -as a module element. If you are importing a WAR file rather than creating -a dynamic Web project new, the WAR Import wizard requires that you specify -a Web project, which already requires an EAR project. </p> - -<p>J2EE conventions may represent extra overhead if you only want to create -a static, content-based Web application, which contains no dynamic files, -such as JSP files or servlets. In this case, when you need only the most basic -Web project, you might want to use the <em>static</em> Web project type (see <a href="ccstatic.html" title="">Static Web projects</a>). - Note that static Web projects can be converted to dynamic Web projects by -selecting <strong>Convert to a Dynamic Web Project</strong>, from the Project menu.</p> - -<p>The J2EE model, and more specifically, the <cite>Sun Microsystems Javaâ„¢ Servlet -2.3 Specification</cite>, defines a Web application directory structure that -specifies the location of Web content files, class files, class paths, deployment -descriptors, and supporting metadata. The Web project hierarchy mirrors that -of the Web application created from a project. In the workbench, you can use -the <span>New Web Project</span> wizard to create a new Web project.</p> - -<div class="p">The main project folder contains all development objects related to a Web -application. The Web content folder contains the elements of the project necessary -to create a Web application. This folder structure maps to the Web application -archive (WAR) structure defined by Sun Microsystems.. The following default -elements are located in the Web project folder hierarchy: <div class="note"><span class="notetitle">Note:</span> In the Project -Explorer view, Web projects are filtered into folder nodes to customize the -display of Web resources for easy management during development. For information -on the filtered structure, see <a href="ccwebvw.html" title="">Project Explorer view</a>.</div> -<dl> -<dt class="dlterm">Web Deployment Descriptor</dt> - -<dd>The standard Web application deployment descriptor (the <span class="filepath">web.xml</span> file).</dd> - - -<dt class="dlterm">JavaSource</dt> - -<dd>Contains the project's Java source code for classes, beans, and -servlets. When these resources are added to a Web project, they are automatically -compiled and the generated files are added to the WEB-INF/classes directory. -The contents of the source directory are not packaged in WAR files unless -an option is specified when a WAR file is created. <div class="note"><span class="notetitle">Note:</span> Though the default -name given to the folder is JavaSources, you can change the name by right -clicking on the name in the Project Explorer and clicking on <span class="menucascade"> -<span class="uicontrol">Refactor</span> > <span class="uicontrol">Rename</span></span>.</div> -</dd> - - -<dt class="dlterm">imported_classes folder</dt> - -<dd>This folder may be created during a WAR import, and contains class files -that do not have accompanying source. The <span class="uicontrol">imported_classes</span> folder -is a Java classes -folder; Java classes folders can also be created using the Web -project <span class="uicontrol">Java Build Path</span> properties page.</dd> - - -<dt class="dlterm">WebContent folder</dt> - -<dd>The mandatory location of all Web resources, including HTML, JSP, graphic -files, and so on. If the files are not placed in this directory (or in a subdirectory -structure under this directory), the files will not be available when the -application is executed on a server. The Web content folder represents the -contents of the WAR file that will be deployed to the server. Any files not -under the Web content folder are considered development-time resources (for -example, .java files, .sql files, and .mif files), and are not deployed when -the project is unit tested or published. <div class="note"><span class="notetitle">Note:</span> Though the default name given -to the folder is <span class="filepath">WebContent</span>, you can change the name - in the Project Explorer by right-clicking the folder and selecting <span class="uicontrol">Refactor</span><span class="uicontrol">Rename</span> or -from the Web page of the project's Properties dialog. In a dynamic Web project, -changing the folder name will update the Java build output directory. </div> -</dd> - - -<dt class="dlterm">META-INF</dt> - -<dd>This directory contains the <span class="filepath">MANIFEST.MF</span> file, which -is used to map class paths for dependent JAR files that exist in other projects -in the same Enterprise Application project. An entry in this file will update -the run-time project class path and Java build settings to include the referenced -JAR files.</dd> - - -<dt class="dlterm">theme</dt> - -<dd>The suggested directory for cascading style sheets and other style-related -objects.</dd> - - -<dt class="dlterm">WEB-INF</dt> - -<dd>Based on the <cite>Sun Microsystems Java Servlet 2.3 Specification</cite>, this -directory contains the supporting Web resources for a Web application, including -the <span class="filepath">web.xml</span> file and the classes and lib directories.</dd> - - -<dt class="dlterm">/classes</dt> - -<dd>This directory is for servlets, utility classes, and the Java compiler -output directory. The classes in this directory are used by the application -class loader to load the classes. Folders in this directory will map package -and class names, as in: <samp class="codeph">/WEB-INF/classes/com/mycorp/servlets/MyServlet.class</samp>.<p>Do -not place any .class files directly into this directory. The .class files -are placed in this directory automatically when the Java compiler -compiles Java source files that are in the <span class="filepath">Java Resources</span> directory. -Any files placed directly in this directory will be deleted by the Java compiler -when it runs.</p> -</dd> - - -<dt class="dlterm">/lib</dt> - -<dd>The supporting JAR files that your Web application references. Any classes -in .jar files placed in this directory will be available for your Web application</dd> - - -<dt class="dlterm">Libraries</dt> - -<dd>The supporting JAR files that your Web application references. This folder -mirrors the content of the lib folder. In addition, Web Library Projects, -which are "virtual" JAR files that do not physically reside in the Web project, -but are associated with Java projects elsewhere in your workspace, -are included in this folder. They are packaged with your project when you -export the application's WAR file.</dd> - -</dl> - <div class="note"><span class="notetitle">Note:</span> A library entry on the Java build path will remain there unless -the actual JAR file is deleted from the WEB-INF/lib folder. If you remove -a library path entry but not the JAR file, the library entry will be re-added -to the path automatically.</div> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.dita deleted file mode 100644 index cc86113077..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="ccwebvw" xml:lang="en-us">
-<title>Project Explorer view and Web development</title>
-<prolog><metadata>
-<keywords><indexterm>Project Explorer view<indexterm>overview</indexterm></indexterm>
-<indexterm>Web development<indexterm>Project Explorer view</indexterm></indexterm>
-<indexterm>Web perspective<indexterm>Project Explorer view</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<section><p>The Project Explorer view provides the following notable features: <ul>
-<li><image alt="For Windows" href="../images/nwin.gif" placement="inline">
-</image> You can drag and drop files from <tm tmclass="special" tmowner="Microsoft Corporation"
-tmtype="reg" trademark="Windows">Windows</tm> Explorer or the desktop into
-the Navigator view.</li>
-<li>View filtering is supported by selecting <ph><uicontrol>Filters</uicontrol></ph> from
-the Navigator view <ph><uicontrol>Menu</uicontrol></ph> button. Resources
-can be filtered by name, project type or content type. Files beginning with
-a period are filtered out by default.</li>
-<li>The status line shows the full path of the selected resource.</li>
-<li>Dragging a .java file from the Navigator view into a JSP file will insert
-a usebean tag, the same behavior that is exhibited when a .class file is dragged
-into a JSP file.</li>
-<li>Errors and warnings on resources (including <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm>, HTML/JSP, and Links Builder errors
-and warnings) are indicated with a red error <image alt="Error icon" href="../images/nshowerr.gif"
-placement="inline"></image> or yellow warning <image alt="Warning icon" href="../images/nwarning.gif"
-placement="inline"></image> next to the resource with the error, as well as
-the parent containers up to the project. This applies for all project types,
-not only Web projects.</li>
-<li>Items available from the <ph><uicontrol>New</uicontrol></ph> cascading
-menu in the project pop-up menu are context sensitive. All menus will have <ph><uicontrol>Project</uicontrol></ph> and <ph><uicontrol>Other</uicontrol
-></ph> options.</li>
-</ul></p></section>
-<section><title>Organization of the Project Explorer view</title><p>The Project
-Explorer view shows a custom view of all Web projects. The following are some
-of the notable top-level objects that appear beneath the project node (based
-on default folder names).</p><p><b>Web content folder</b> - This folder contains
-items to be published to the server. By default, this folder will be named <b>WebContent</b> for
-newly created static and dynamic Web projects. <note>You can change the name
-in the creation wizard Web facet page.</note><ul>
-<li><b>META-INF</b> - This directory contains the <filepath>MANIFEST.MF</filepath> file,
-which is used to map class paths for dependent JAR files that exist in other
-projects in the same Enterprise Application project. An entry in this file
-will update the run-time project class path and <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> build settings to include the referenced
-JAR files.</li>
-</ul><ul>
-<li><b>WEB-INF</b> - The directory where supporting Web resources for a Web
-application are kept (for example: .xmi files, .xml files, and web.xml.) </li>
-</ul> </p> </section>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.html b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.html deleted file mode 100644 index b067d6dd9f..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwebvw.html +++ /dev/null @@ -1,82 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Project Explorer view and Web development" /> -<meta content="Project Explorer view, overview, Web perspective, project explorer view, version control management, turning on and off, Web development" name="DC.subject" /> -<meta content="Project Explorer view, overview, Web perspective, project explorer view, version control management, turning on and off, Web development" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ccwebvw" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Project Explorer view and Web development</title> -</head> -<body id="ccwebvw"><a name="ccwebvw"><!-- --></a> - - -<h1 class="topictitle1">Project Explorer view and Web development</h1> - - -<div> -<div class="section"><div class="p">The Project Explorer view provides the following notable features: <ul> -<li><img src="../images/nwin.gif" alt="For Windows" /> You can drag and drop files from Windows<sup>®</sup> Explorer or the desktop into -the Navigator view.</li> - -<li>View filtering is supported by selecting <span><span class="uicontrol">Filters</span></span> from -the Navigator view <span><span class="uicontrol">Menu</span></span> button. Resources -can be filtered by name, project type or content type. Files beginning with -a period are filtered out by default.</li> - -<li>The status line shows the full path of the selected resource.</li> - -<li>Dragging a .java file from the Navigator view into a JSP file will insert -a usebean tag, the same behavior that is exhibited when a .class file is dragged -into a JSP file.</li> - -<li>Errors and warnings on resources (including Java™, HTML/JSP, and Links Builder errors -and warnings) are indicated with a red error <img src="../images/nshowerr.gif" alt="Error icon" /> or yellow warning <img src="../images/nwarning.gif" alt="Warning icon" /> next to the resource with the error, as well as -the parent containers up to the project. This applies for all project types, -not only Web projects.</li> - -<li>Items available from the <span><span class="uicontrol">New</span></span> cascading -menu in the project pop-up menu are context sensitive. All menus will have <span><span class="uicontrol">Project</span></span> and <span><span class="uicontrol">Other</span></span> options.</li> - -</ul> -</div> -</div> - -<div class="section"><h4 class="sectiontitle">Organization of the Project Explorer view</h4><p>The Project -Explorer view shows a custom view of all Web projects. The following are some -of the notable top-level objects that appear beneath the project node (based -on default folder names).</p> -<div class="p"><strong>Web content folder</strong> - This folder contains -items to be published to the server. By default, this folder will be named <strong>WebContent</strong> for -newly created static and dynamic Web projects. <div class="note"><span class="notetitle">Note:</span> You can change the name -in the creation wizard Web facet page.</div> -<ul> -<li><strong>META-INF</strong> - This directory contains the <span class="filepath">MANIFEST.MF</span> file, -which is used to map class paths for dependent JAR files that exist in other -projects in the same Enterprise Application project. An entry in this file -will update the run-time project class path and Java build settings to include the referenced -JAR files.</li> - -</ul> -<ul> -<li><strong>WEB-INF</strong> - The directory where supporting Web resources for a Web -application are kept (for example: .xmi files, .xml files, and web.xml.) </li> - -</ul> - </div> - </div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.dita deleted file mode 100644 index 880cc3a16b..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.dita +++ /dev/null @@ -1,27 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<!-- ArborText, Inc., 1988-2002, v.4002 -->
-<concept id="ccwtover" xml:lang="en-us">
-<title>Web application overview</title>
-<prolog><metadata>
-<keywords><indexterm>Web applications<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>The Web development environment provides the tools you need to develop
-Web applications as defined in the <cite>Sun Microsystems <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Servlet
-2.3 Specification</cite> and the <cite>Sun Microsystems JSP 1.2 Specification</cite>.
-Web applications can be simple (consisting of only static Web pages) or they
-can be more advanced and include JavaServer Pages (JSP) files and <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> servlets.
-These resources, along with an XML deployment descriptor (and other <xref
-href="cwebresources.dita" scope="peer"><desc></desc> Web resources</xref>, are contained
-within a Web project during development. When you are ready to publish the
-Web application to the Web, you deploy the Web project to the server in the
-form of a Web archive (WAR) file . The end user can then view the Web application
-as a Web site from a URL.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.html b/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.html deleted file mode 100644 index 36bf69b5fd..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/ccwtover.html +++ /dev/null @@ -1,42 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web application overview" /> -<meta content="Web applications, overview, development phases, information pathways" name="DC.subject" /> -<meta content="Web applications, overview, development phases, information pathways" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ccwtover" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Web application overview</title> -</head> -<body id="ccwtover"><a name="ccwtover"><!-- --></a> - - -<h1 class="topictitle1">Web application overview</h1> - - -<div> -<p>The Web development environment provides the tools you need to develop -Web applications as defined in the <cite>Sun Microsystems Javaâ„¢ Servlet -2.3 Specification</cite> and the <cite>Sun Microsystems JSP 1.2 Specification</cite>. -Web applications can be simple (consisting of only static Web pages) or they -can be more advanced and include JavaServer Pages (JSP) files and Java servlets. -These resources, along with an XML deployment descriptor (and other <a href="cwebresources.html" title="">Web resources</a>, are contained -within a Web project during development. When you are ready to publish the -Web application to the Web, you deploy the Web project to the server in the -form of a Web archive (WAR) file . The end user can then view the Web application -as a Web site from a URL.</p> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.dita deleted file mode 100644 index 07a94f1850..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.dita +++ /dev/null @@ -1,45 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cpdjsps" xml:lang="en-us">
-<title>JavaServer Pages (JSP) technology</title>
-<prolog><metadata>
-<keywords><indexterm>JSP pages<indexterm>overview</indexterm></indexterm>
-<indexterm>Web content<indexterm>generating dynamically</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>The JavaServer Pages technology enables you to generate dynamic web content,
-such as HTML, DHTML, XHTML, and XML files, to include in a Web application.
-JSP files are one way to implement server-side dynamic page content. JSP files
-allow a Web server, such as Apache Tomcat, to add content dynamically to your
-HTML pages before they are sent to a requesting browser.</p>
-<p>When you deploy a JSP file to a Web server that provides a servlet engine,
-it is preprocessed into a servlet that runs on the Web server. This is in
-contrast with client-side <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm> (within <codeph><SCRIPT></codeph> tags),
-which is run in a browser. A JSP page is ideal for tasks that are better suited
-to execution on the server, such as accessing databases or calling Enterprise <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> beans.</p>
-<p>You can create and edit a JSP file in the HTML editor by adding your own
-text and images using HTML, JSP tagging, or <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm>, including <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> source
-code inside of scriptlet tags. Typically, JSP files have the file extension
-.jsp. Additionally, the JSP specification suggests that JSP fragment files
-should have file extension .jspf. If this convention is not followed, the
-JSP validator will treat JSP fragments as regular standalone JSP files, and
-compilation errors might be reported.</p>
-<p>The <cite>Sun Microsystems JSP 1.2 Specification</cite> provides the ability
-to create custom JSP tags. Custom tags simplify complex actions and provide
-developers with greater control over page content. Custom tags are collected
-into a library (taglib). A tag library descriptor file (taglib.tld) is an
-XML document that provides information about the tag library, including the
-taglib short name, library description, and tag descriptions. Refer to the <cite>Sun
-Microsystems JSP 1.2 Specification</cite> for more details.</p>
-<p>To use JSP 1.2 custom taglibs, you can import the tag library .tld and
-.jar files into your project to use them, or associate them as Web Library
-projects. You can also reference a TLD file by using a URI.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.html deleted file mode 100644 index 183a375f64..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cpdjsps.html +++ /dev/null @@ -1,63 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="JavaServer Pages (JSP) technology" /> -<meta content="JavaServer pages, overview, dynamic Web content, generating" name="DC.subject" /> -<meta content="JavaServer pages, overview, dynamic Web content, generating" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cpdjsps" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>JavaServer Pages (JSP) technology</title> -</head> -<body id="cpdjsps"><a name="cpdjsps"><!-- --></a> - - -<h1 class="topictitle1">JavaServer Pages (JSP) technology</h1> - - -<div> -<p>The JavaServer Pages technology enables you to generate dynamic web content, -such as HTML, DHTML, XHTML, and XML files, to include in a Web application. -JSP files are one way to implement server-side dynamic page content. JSP files -allow a Web server, such as Apache Tomcat, to add content dynamically to your -HTML pages before they are sent to a requesting browser.</p> - -<p>When you deploy a JSP file to a Web server that provides a servlet engine, -it is preprocessed into a servlet that runs on the Web server. This is in -contrast with client-side JavaScriptâ„¢ (within <samp class="codeph"><SCRIPT></samp> tags), -which is run in a browser. A JSP page is ideal for tasks that are better suited -to execution on the server, such as accessing databases or calling Enterprise Javaâ„¢ beans.</p> - -<p>You can create and edit a JSP file in the HTML editor by adding your own -text and images using HTML, JSP tagging, or JavaScript, including Java source -code inside of scriptlet tags. Typically, JSP files have the file extension -.jsp. Additionally, the JSP specification suggests that JSP fragment files -should have file extension .jspf. If this convention is not followed, the -JSP validator will treat JSP fragments as regular standalone JSP files, and -compilation errors might be reported.</p> - -<p>The <cite>Sun Microsystems JSP 1.2 Specification</cite> provides the ability -to create custom JSP tags. Custom tags simplify complex actions and provide -developers with greater control over page content. Custom tags are collected -into a library (taglib). A tag library descriptor file (taglib.tld) is an -XML document that provides information about the tag library, including the -taglib short name, library description, and tag descriptions. Refer to the <cite>Sun -Microsystems JSP 1.2 Specification</cite> for more details.</p> - -<p>To use JSP 1.2 custom taglibs, you can import the tag library .tld and -.jar files into your project to use them, or associate them as Web Library -projects. You can also reference a TLD file by using a URI.</p> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.dita deleted file mode 100644 index 3f1624f575..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.dita +++ /dev/null @@ -1,20 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cwebpagedesign" xml:lang="en-us">
-<title>Web page design</title>
-<prolog><metadata>
-<keywords><indexterm>Web page design<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>Web pages are an integral part of every Web application. Each Web page
-should serve to help achieve the overall goal of the entire Web site.</p>
-<p> There are many types of Web pages, ranging from simple HTML pages that
-contain no dynamic elements, to advanced Java-based pages that make use of
-servlets, scripts, forms, or data access components.</p>
-<p>A few of the many items you should consider when designing your pages are
-markup language, links, images, and style sheets.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.html deleted file mode 100644 index 4e33359fed..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebpagedesign.html +++ /dev/null @@ -1,41 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web page design" /> -<meta content="Web page design, overview" name="DC.subject" /> -<meta content="Web page design, overview" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwebpagedesign" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Web page design</title> -</head> -<body id="cwebpagedesign"><a name="cwebpagedesign"><!-- --></a> - - -<h1 class="topictitle1">Web page design</h1> - - -<div> -<p>Web pages are an integral part of every Web application. Each Web page -should serve to help achieve the overall goal of the entire Web site.</p> - -<p> There are many types of Web pages, ranging from simple HTML pages that -contain no dynamic elements, to advanced Java-based pages that make use of -servlets, scripts, forms, or data access components.</p> - -<p>A few of the many items you should consider when designing your pages are -markup language, links, images, and style sheets.</p> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.dita deleted file mode 100644 index 99b82cde48..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.dita +++ /dev/null @@ -1,28 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cwebprojects" xml:lang="en-us">
-<title>Web projects</title>
-<prolog><metadata>
-<keywords><indexterm>Web projects<indexterm>overview</indexterm></indexterm>
-<indexterm>Web applications<indexterm>creating or importing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>Web projects hold all of the Web resources that are created and used when
-developing your Web application. The first step to creating or importing a
-Web application is to create either a static or a dynamic Web project. Static
-Web projects are meant to contain only simple Web site resources, such as
-HTML files. Dynamic Web projects are used to structure Web applications that
-will use more complicated, dynamic Web technologies, such as JavaServer Pages
-files, and possibly data access resources.</p>
-<p>Though the Web project is structured on your file system in compliance
-with the J2EE Web application standard for deployment purposes, the Project
-Explorer view is designed to show the most convenient display of project resources
-for use while you are actually developing the Web application. When you are
-finished developing your Web application, you use the Web project to deploy
-the correct resources to the server. These resources will be packaged in a
-file called a Web archive, or WAR file.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.html deleted file mode 100644 index 782fcfef81..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebprojects.html +++ /dev/null @@ -1,47 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web projects" /> -<meta content="Web projects, overview, Web applications, creating or importing" name="DC.subject" /> -<meta content="Web projects, overview, Web applications, creating or importing" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwebprojects" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Web projects</title> -</head> -<body id="cwebprojects"><a name="cwebprojects"><!-- --></a> - - -<h1 class="topictitle1">Web projects</h1> - - -<div> -<p>Web projects hold all of the Web resources that are created and used when -developing your Web application. The first step to creating or importing a -Web application is to create either a static or a dynamic Web project. Static -Web projects are meant to contain only simple Web site resources, such as -HTML files. Dynamic Web projects are used to structure Web applications that -will use more complicated, dynamic Web technologies, such as JavaServer Pages -files, and possibly data access resources.</p> - -<p>Though the Web project is structured on your file system in compliance -with the J2EE Web application standard for deployment purposes, the Project -Explorer view is designed to show the most convenient display of project resources -for use while you are actually developing the Web application. When you are -finished developing your Web application, you use the Web project to deploy -the correct resources to the server. These resources will be packaged in a -file called a Web archive, or WAR file.</p> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.dita deleted file mode 100644 index 05f8d71058..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.dita +++ /dev/null @@ -1,23 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cwebresources" xml:lang="en-us">
-<title>Web resources</title>
-<prolog><metadata>
-<keywords><indexterm>Web resources<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>In most cases, all of the resources that you need to create for your Web
-application are developed during Web site or Web page design; however, there
-are additional resources that you may need to include in your Web project
-if you are using more advanced Web technologies in your application.</p>
-<p>These Web resources are not typical Web page files, and are often not the
-resources that you consider part of the final Web site. For example, tag libraries
-and <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> resources,
-such as JAR files, are resources you might need to include in your Web project. </p>
-<p>In fact, even the WAR file itself could be considered a Web resource, if
-you consider importing or exporting the resource.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.html deleted file mode 100644 index c288bc0d72..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwebresources.html +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web resources" /> -<meta content="Web resources, overview" name="DC.subject" /> -<meta content="Web resources, overview" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwebresources" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Web resources</title> -</head> -<body id="cwebresources"><a name="cwebresources"><!-- --></a> - - -<h1 class="topictitle1">Web resources</h1> - - -<div> -<p>In most cases, all of the resources that you need to create for your Web -application are developed during Web site or Web page design; however, there -are additional resources that you may need to include in your Web project -if you are using more advanced Web technologies in your application.</p> - -<p>These Web resources are not typical Web page files, and are often not the -resources that you consider part of the final Web site. For example, tag libraries -and Javaâ„¢ resources, -such as JAR files, are resources you might need to include in your Web project. </p> - -<p>In fact, even the WAR file itself could be considered a Web resource, if -you consider importing or exporting the resource.</p> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.dita deleted file mode 100644 index fb05e747b3..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.dita +++ /dev/null @@ -1,49 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cwservbn" xml:lang="en-us">
-<title>Servlets</title>
-<prolog><metadata>
-<keywords><indexterm>servlets<indexterm>overview</indexterm></indexterm>
-<indexterm>Web servers<indexterm>generating dynamic content</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>Servlets are server-side <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> programs that use the <cite>Sun Microsystems <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Servlet
-API</cite> and its associated classes and methods, as defined in the <cite>Sun
-Microsystems <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> Servlet 2.3 Specification</cite>. These <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> programs
-extend the functionality of a Web server by generating dynamic content and
-responding to Web client requests. When a browser sends a request to the server,
-the server can send the request information to a servlet, so that the servlet
-can construct the response that is sent back to the browser.</p>
-<p>Just as applets run on a Web browser and extend the browser's capabilities,
-servlets run on a Java-enabled Web server and extend the server's capabilities.
-Because of their flexibility and scalability, servlets are commonly used to
-enable businesses to connect databases to the Web.</p>
-<p>Although a servlet can be a completely self-contained program, you can
-split application development into two portions: <ul>
-<li>The business logic (content generation), which governs the relationship
-between input, processing, and output</li>
-<li>The presentation logic (content presentation, or graphic design rules),
-which determines how information is presented to the user</li>
-</ul>Using this paradigm, you may choose to have business logic handled by <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> beans,
-the presentation logic handled by JavaServer Pages (JSP) or HTML files, and
-the HTTP protocol handled by a servlet. <note>JSP files can be used to manage
-both the presentation and business logic for a Web application. JSP files
-use structured markup for presentation, and supply servlet model behavior
-at run time.</note></p>
-<p>You can develop, debug, and deploy servlets, set breakpoints within servlet
-objects, and step through code to make changes that are dynamically folded
-into the running servlet on a running server, without having to restart each
-time.</p>
-<p>For more information about servlets, refer to the <cite>Sun Microsystems <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Servlet
-2.3 Specification</cite> at <codeph>java.sun.com/products/servlet/download.html</codeph>.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.html deleted file mode 100644 index 3ab7815ec1..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwservbn.html +++ /dev/null @@ -1,69 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Servlets" /> -<meta content="servlets, overview, dynamic content" name="DC.subject" /> -<meta content="servlets, overview, dynamic content" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwservbn" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Servlets</title> -</head> -<body id="cwservbn"><a name="cwservbn"><!-- --></a> - - -<h1 class="topictitle1">Servlets</h1> - - -<div> -<p>Servlets are server-side Javaâ„¢ programs that use the <cite>Sun Microsystems Java Servlet -API</cite> and its associated classes and methods, as defined in the <cite>Sun -Microsystems Java Servlet 2.3 Specification</cite>. These Java programs -extend the functionality of a Web server by generating dynamic content and -responding to Web client requests. When a browser sends a request to the server, -the server can send the request information to a servlet, so that the servlet -can construct the response that is sent back to the browser.</p> - -<p>Just as applets run on a Web browser and extend the browser's capabilities, -servlets run on a Java-enabled Web server and extend the server's capabilities. -Because of their flexibility and scalability, servlets are commonly used to -enable businesses to connect databases to the Web.</p> - -<div class="p">Although a servlet can be a completely self-contained program, you can -split application development into two portions: <ul> -<li>The business logic (content generation), which governs the relationship -between input, processing, and output</li> - -<li>The presentation logic (content presentation, or graphic design rules), -which determines how information is presented to the user</li> - -</ul> -Using this paradigm, you may choose to have business logic handled by Java beans, -the presentation logic handled by JavaServer Pages (JSP) or HTML files, and -the HTTP protocol handled by a servlet. <div class="note"><span class="notetitle">Note:</span> JSP files can be used to manage -both the presentation and business logic for a Web application. JSP files -use structured markup for presentation, and supply servlet model behavior -at run time.</div> -</div> - -<p>You can develop, debug, and deploy servlets, set breakpoints within servlet -objects, and step through code to make changes that are dynamically folded -into the running servlet on a running server, without having to restart each -time.</p> - -<p>For more information about servlets, refer to the <cite>Sun Microsystems Java Servlet -2.3 Specification</cite> at <samp class="codeph">java.sun.com/products/servlet/download.html</samp>.</p> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.dita deleted file mode 100644 index 623bc9f168..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.dita +++ /dev/null @@ -1,40 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<!-- ArborText, Inc., 1988-2002, v.4002 -->
-<concept id="cwtfeatures" xml:lang="en-us">
-<title>Web tools features</title>
-<shortdesc> The integrated Web development environment makes it easy to cooperatively
-create, assemble, publish, deploy and maintain dynamic, interactive Web applications.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Web tools<indexterm>features</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>The Web development environment provides the following high-level capabilities:
- <ul>
-<li>Dynamic Web project creation, using the J2EE-defined hierarchy, or a static
-version that reduces project overhead when dynamic elements are not required.
- Static Web projects can later be converted to dynamic Web projects.<p></p></li>
-<li>Creation and editing of a Web application deployment descriptor (<filepath>web.xml</filepath>)
- file<p></p></li>
-<li>JSP and HTML file creation, validation, editing, and debugging<p></p></li>
-<li>An extensible view, called the Snippets view, which allows users to catalog
- and organize reusable programming objects, such as HTML, <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="JavaScript">JavaScript</tm>,
- and JSP markup, along with files and custom tags, that can be embedded in
- existing files<p></p></li>
-<li>Dynamic tag help (content assist) , which displays tag usage and attribute
-information for HTML, JSP, and <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="JavaScript">JavaScript</tm> tags based on cursor location
- in the Source page. (You invoke Content Assist by pressing (Ctrl+Spacebar)
-)<p></p></li>
-<li>Cascading style sheet (CSS) editing support<p></p></li>
-<li>HTTP/FTP import<p></p></li>
-<li>FTP export (simple resource copy) to a server<p></p></li>
-<li>WAR file import, export, and validation<p></p></li>
-<li>Servlet creation, which employs the Servlet Wizard to create new servlets.<p></p></li>
-</ul></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.html deleted file mode 100644 index ab3323d8ba..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwtfeatures.html +++ /dev/null @@ -1,80 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web tools features" /> -<meta name="abstract" content="The integrated Web development environment makes it easy to cooperatively create, assemble, publish, deploy and maintain dynamic, interactive Web applications." /> -<meta name="description" content="The integrated Web development environment makes it easy to cooperatively create, assemble, publish, deploy and maintain dynamic, interactive Web applications." /> -<meta content="Web tools, features and capabilities" name="DC.subject" /> -<meta content="Web tools, features and capabilities" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwtfeatures" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Web tools features</title> -</head> -<body id="cwtfeatures"><a name="cwtfeatures"><!-- --></a> - - -<h1 class="topictitle1">Web tools features</h1> - - - -<div><p> The integrated Web development environment makes it easy to cooperatively -create, assemble, publish, deploy and maintain dynamic, interactive Web applications.</p> - -<div class="p">The Web development environment provides the following high-level capabilities: - <ul> -<li>Dynamic Web project creation, using the J2EE-defined hierarchy, or a static -version that reduces project overhead when dynamic elements are not required. - Static Web projects can later be converted to dynamic Web projects.<p /> -</li> - -<li>Creation and editing of a Web application deployment descriptor (<span class="filepath">web.xml</span>) - file<p /> -</li> - -<li>JSP and HTML file creation, validation, editing, and debugging<p /> -</li> - -<li>An extensible view, called the Snippets view, which allows users to catalog - and organize reusable programming objects, such as HTML, JavaScriptâ„¢, - and JSP markup, along with files and custom tags, that can be embedded in - existing files<p /> -</li> - -<li>Dynamic tag help (content assist) , which displays tag usage and attribute -information for HTML, JSP, and JavaScript tags based on cursor location - in the Source page. (You invoke Content Assist by pressing (Ctrl+Spacebar) -)<p /> -</li> - -<li>Cascading style sheet (CSS) editing support<p /> -</li> - -<li>HTTP/FTP import<p /> -</li> - -<li>FTP export (simple resource copy) to a server<p /> -</li> - -<li>WAR file import, export, and validation<p /> -</li> - -<li>Servlet creation, which employs the Servlet Wizard to create new servlets.<p /> -</li> - -</ul> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.dita deleted file mode 100644 index 23e1ee0af6..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.dita +++ /dev/null @@ -1,31 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cwwarovr" xml:lang="en-us">
-<title>Web archive (WAR) files</title>
-<prolog><metadata>
-<keywords><indexterm>WAR files<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p> A Web application is a group of HTML pages, JSP pages, servlets, resources
-and source file, which can be managed as a single unit. A Web archive (WAR)
-file is a packaged Web application. WAR files can be used to import a Web
-application into a Web server.</p>
-<p>In addition to project resources, the WAR file includes a Web deployment
-descriptor file. The Web deployment descriptor is an XML file that contains
-deployment information, MIME types, session configuration details, and other
-settings for a Web application. The Web deployment descriptor file (<filepath>web.xml</filepath>)
-provides information about the WAR file is shared with the developers, assemblers,
-and deployers in a J2EE environment.</p>
-<p>The Web development environment provides facilities for importing and exporting
-WAR files, using the following wizards: <ul>
-<li><ph>Import Resources from a WAR File</ph>, which requires that you to
-specify a Web project. You can use existing projects or create them as you
-use the wizard.</li>
-<li><ph>Export Resources to a WAR File</ph>, which requires only an export
-location and some optional settings</li>
-</ul></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.html deleted file mode 100644 index 16d50c5cf1..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwarovr.html +++ /dev/null @@ -1,55 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web archive (WAR) files" /> -<meta content="WAR files, overview" name="DC.subject" /> -<meta content="WAR files, overview" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwwarovr" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Web archive (WAR) files</title> -</head> -<body id="cwwarovr"><a name="cwwarovr"><!-- --></a> - - -<h1 class="topictitle1">Web archive (WAR) files</h1> - - -<div> -<p> A Web application is a group of HTML pages, JSP pages, servlets, resources -and source file, which can be managed as a single unit. A Web archive (WAR) -file is a packaged Web application. WAR files can be used to import a Web -application into a Web server.</p> - -<p>In addition to project resources, the WAR file includes a Web deployment -descriptor file. The Web deployment descriptor is an XML file that contains -deployment information, MIME types, session configuration details, and other -settings for a Web application. The Web deployment descriptor file (<span class="filepath">web.xml</span>) -provides information about the WAR file is shared with the developers, assemblers, -and deployers in a J2EE environment.</p> - -<div class="p">The Web development environment provides facilities for importing and exporting -WAR files, using the following wizards: <ul> -<li><span>Import Resources from a WAR File</span>, which requires that you to -specify a Web project. You can use existing projects or create them as you -use the wizard.</li> - -<li><span>Export Resources to a WAR File</span>, which requires only an export -location and some optional settings</li> - -</ul> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.dita deleted file mode 100644 index 7c8ea6172d..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.dita +++ /dev/null @@ -1,52 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cwwedtvw" xml:lang="en-us">
-<title>Workbench integration with Web editors</title>
-<prolog><metadata>
-<keywords><indexterm>Web editors<indexterm>workbench integration</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>There are several editors for use in various contexts for various file
-types. To edit a file using its default editor, double-click on the file name
-in the Project Explorer view, or right-click on the file and select <uicontrol>Open</uicontrol>.
-The editor that is last used to open a file becomes the default for that particular
-file. To edit the file with a different editor, right-click on the file and
-select <uicontrol>Open With</uicontrol> to choose from a list of available
-editors.</p>
-<p>In the workbench, you can associate file-name extensions for different
-types of resources with various editors. A resource extension can have more
-than one editor associated with it; the last editor used for a particular
-extension type is indicated by a black dot before it in the <uicontrol>Open
-With</uicontrol> pop-up menu. You can associate extensions that are known
-to the workbench with additional editors, by using the <b>File Associations</b> preferences
-page, accessed by selecting <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Workbench</uicontrol><uicontrol>File Associations</uicontrol></menucascade>.</p>
-<p>The Properties view provides general capabilities that are advantageous
-to Web editor users. <dl><dlentry>
-<dt>Properties view</dt>
-<dd>The Properties view (<menucascade><uicontrol>Window</uicontrol><uicontrol>Show
-View</uicontrol><uicontrol>Properties</uicontrol></menucascade>) contains
-a list of attributes and editable attribute values. For example, when you
-select an image tag <uicontrol>img</uicontrol> , the width and height values
-appear for editing. In addition, any other attributes allowed by the standard
-specified in the DOCTYPE for the file (such as the HTML 4.0.1 DTD) are listed.
-When you click the value column of a property, you can select from among the
-list of available attribute values. <p>The pop-up menu in the Properties view
-enables you to undo, cut, copy, paste, delete, and select all. The options
-that are available at a given time depends on where the cursor is located
-when you right-click to display the pop-up menu. To see the pop-up menu that
-contains undo, cut, and so on, the property value field must be active. (This
-is accomplished by selecting the property and then selecting its value.) Otherwise,
-the pop-up menu will contain different options.</p> <p>Use the <uicontrol>Restore
-Default Value</uicontrol> button to change any value back to the default setting.</p> <p>After
-you are in the Properties view, you can modify other property values for specific
-tags. To edit another tag using the Properties view, move the cursor within
-the editing area of the Source page or Design page to the tag you want to
-edit. The appropriate properties and values are displayed in the Properties
-view.</p></dd>
-</dlentry></dl></p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.html b/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.html deleted file mode 100644 index 546ffce23f..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/cwwedtvw.html +++ /dev/null @@ -1,79 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Workbench integration with Web editors" /> -<meta content="Web editors, workbench integration" name="DC.subject" /> -<meta content="Web editors, workbench integration" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwwedtvw" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Workbench integration with Web editors</title> -</head> -<body id="cwwedtvw"><a name="cwwedtvw"><!-- --></a> - - -<h1 class="topictitle1">Workbench integration with Web editors</h1> - - -<div> -<p>There are several editors for use in various contexts for various file -types. To edit a file using its default editor, double-click on the file name -in the Project Explorer view, or right-click on the file and select <span class="uicontrol">Open</span>. -The editor that is last used to open a file becomes the default for that particular -file. To edit the file with a different editor, right-click on the file and -select <span class="uicontrol">Open With</span> to choose from a list of available -editors.</p> - -<p>In the workbench, you can associate file-name extensions for different -types of resources with various editors. A resource extension can have more -than one editor associated with it; the last editor used for a particular -extension type is indicated by a black dot before it in the <span class="uicontrol">Open -With</span> pop-up menu. You can associate extensions that are known -to the workbench with additional editors, by using the <strong>File Associations</strong> preferences -page, accessed by selecting <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Workbench</span> > <span class="uicontrol">File Associations</span></span>.</p> - -<div class="p">The Properties view provides general capabilities that are advantageous -to Web editor users. <dl> -<dt class="dlterm">Properties view</dt> - -<dd>The Properties view (<span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Show -View</span> > <span class="uicontrol">Properties</span></span>) contains -a list of attributes and editable attribute values. For example, when you -select an image tag <span class="uicontrol">img</span> , the width and height values -appear for editing. In addition, any other attributes allowed by the standard -specified in the DOCTYPE for the file (such as the HTML 4.0.1 DTD) are listed. -When you click the value column of a property, you can select from among the -list of available attribute values. <p>The pop-up menu in the Properties view -enables you to undo, cut, copy, paste, delete, and select all. The options -that are available at a given time depends on where the cursor is located -when you right-click to display the pop-up menu. To see the pop-up menu that -contains undo, cut, and so on, the property value field must be active. (This -is accomplished by selecting the property and then selecting its value.) Otherwise, -the pop-up menu will contain different options.</p> - <p>Use the <span class="uicontrol">Restore -Default Value</span> button to change any value back to the default setting.</p> - <p>After -you are in the Properties view, you can modify other property values for specific -tags. To edit another tag using the Properties view, move the cursor within -the editing area of the Source page or Design page to the tag you want to -edit. The appropriate properties and values are displayed in the Properties -view.</p> -</dd> - -</dl> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.dita deleted file mode 100644 index c35c3f6c4c..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.dita +++ /dev/null @@ -1,38 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjchgxdt" xml:lang="en-us">
-<title>Specifying an implicit document type for an HTML, XHTML, or JSP fragment</title>
-<prolog><metadata>
-<keywords><indexterm>DOCTYPE declarations<indexterm>implicit for fragments</indexterm></indexterm>
-<indexterm>document types<indexterm>implicit for fragments</indexterm></indexterm>
-<indexterm>HTML fragments<indexterm>implicit document types</indexterm></indexterm>
-<indexterm>JSP fragments<indexterm>implicit document types</indexterm></indexterm>
-<indexterm>XHTML fragments<indexterm>implicit document type for fragments</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>An <i>implicit</i> document type is used for content assist (CTRL+Spacebar),
-the Properties view, and other editing contexts when no DOCTYPE declaration
-is specified in an HTML, XHTML, or JSP file. Typically, this feature is used
-for a fragment (partial document) that can be included in other pages using
-JSP include or server-side include.</p><p>To assign an implicit document type
-to an HTML, XHTML, or JSP fragment, do the following: </p> </context>
-<steps>
-<step><cmd>From the Project Explorer view, select the HTML, XHTML, or JSP
-fragment.</cmd></step>
-<step><cmd>Select <ph><uicontrol>Properties</uicontrol></ph> from the file's
-pop-up menu.</cmd></step>
-<step><cmd>In the <uicontrol>Web Content Settings</uicontrol> page, select
-the desired DOCTYPE from the <ph><uicontrol>Document type</uicontrol></ph> drop-down
-list.</cmd><info><p>The <ph><uicontrol>Properties</uicontrol></ph> dialog
-for Web projects also includes an <ph><uicontrol>Web Content Settings</uicontrol></ph> page,
-where you can specify project-default HTML document type. This setting will
-be used if no DOCTYPE declaration is specified in the file, and no default
-document type is specified in the <ph><uicontrol>Web Content Settings</uicontrol></ph> page
-on the <ph><uicontrol>Properties</uicontrol></ph> dialog for the file.</p></info>
-</step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.html deleted file mode 100644 index 00a974d04a..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjchgxdt.html +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//IETF//DTD HTML 4.0//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html><head> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2006 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css"/> -<title>Specifying an implicit document type for an HTML, XHTML, or JSP fragment</title> -</head> -<body id="tjchgxdt"><a name="tjchgxdt"><!-- --></a> -<h1 class="topictitle1">Specifying an implicit document type for an HTML, XHTML, or JSP fragment</h1> -<div><div class="section"> <p>An <em>implicit</em> document type is used for content assist (CTRL+Spacebar), -the Properties view, and other editing contexts when no DOCTYPE declaration -is specified in an HTML, XHTML, or JSP file. Typically, this feature is used -for a fragment (partial document) that can be included in other pages using -JSP include or server-side include.</p> -<p>To assign an implicit document type -to an HTML, XHTML, or JSP fragment, do the following: </p> - </div> -<ol><li class="stepexpand"><span>From the Project Explorer view, select the HTML, XHTML, or JSP -fragment.</span></li> -<li class="stepexpand"><span>Select <span><b>Properties</b></span> from the file's -pop-up menu.</span></li> -<li class="stepexpand"><span>In the <b>Web Content Settings</b> page, select -the desired DOCTYPE from the <span><b>Document type</b></span> drop-down -list.</span> <p>The <span><b>Properties</b></span> dialog -for Web projects also includes an <span><b>Web Content Settings</b></span> page, -where you can specify project-default HTML document type. This setting will -be used if no DOCTYPE declaration is specified in the file, and no default -document type is specified in the <span><b>Web Content Settings</b></span> page -on the <span><b>Properties</b></span> dialog for the file.</p> -</li> -</ol> -</div> -<div></div> -</body></html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.dita deleted file mode 100644 index 516efe1304..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.dita +++ /dev/null @@ -1,47 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjcrehtm" xml:lang="en-us">
-<title>Creating HTML and XHTML files and framesets</title>
-<shortdesc>You can use the New HTML File wizard to create HTML and XHTML files
-and framesets. </shortdesc>
-<prolog><metadata>
-<keywords>
-<indexterm>framesets<indexterm>creating</indexterm></indexterm>
-<indexterm>HTML<indexterm>creating files</indexterm></indexterm>
-<indexterm>WML<indexterm>creating files</indexterm></indexterm>
-<indexterm>XHTML<indexterm>creating files</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> </context>
-<steps>
-<step><cmd>Create a static or a dynamic Web project if you have not already
-done so.</cmd></step>
-<step><cmd>In the Project Explorer, expand your project and right click on
-your WebContent folder or on a subfolder under WebContent. </cmd><info>Note
-that if you choose any other folder in which to create the HTML file, then
-it will not be included in the WAR file that is deployed to the server. In
-addition, link validation will not encompass files that are not under the
-WebContent folder.</info></step>
-<step><cmd>From the context menu, select <menucascade><uicontrol>New</uicontrol>
-<uicontrol>Other</uicontrol><uicontrol>Web</uicontrol><uicontrol>HTML</uicontrol>
-</menucascade>.</cmd><stepresult>The New HTML Page window appears with your
-folder selected</stepresult></step>
-<step><cmd>Type a file name into the File name field, making sure you include
-an html extension (html, htm, xhtml, htpl, wml, shtml, or shtm) in the file
-name.</cmd></step>
-<step><cmd> You have several options for proceeding:</cmd>
-<choices>
-<choice>To accept the defaults associated with a new HTML file, select <uicontrol>Finish.</uicontrol></choice>
-<choice> To use a template file for the initial content of your HTML page,
-select <uicontrol>Next</uicontrol>. The Select HTML Template window appears.
-Select the <uicontrol>Use HTML Template</uicontrol> check box, and then select
-one of the sample templates. You can also select the <uicontrol>HTML Templates</uicontrol> link
-to add or remove HTML templates to your list of templates.</choice>
-</choices>
-</step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.html deleted file mode 100644 index 8af7382269..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrehtm.html +++ /dev/null @@ -1,74 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating HTML and XHTML files and framesets" /> -<meta name="abstract" content="You can use the New HTML File wizard to create HTML and XHTML files and framesets." /> -<meta name="description" content="You can use the New HTML File wizard to create HTML and XHTML files and framesets." /> -<meta content="HTML files, creating, XHTML files, WML files, framesets" name="DC.subject" /> -<meta content="HTML files, creating, XHTML files, WML files, framesets" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tjcrehtm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating HTML and XHTML files and framesets</title> -</head> -<body id="tjcrehtm"><a name="tjcrehtm"><!-- --></a> - - -<h1 class="topictitle1">Creating HTML and XHTML files and framesets</h1> - - - -<div><p>You can use the New HTML File wizard to create HTML and XHTML files -and framesets. </p> - -<div class="section"> </div> - -<ol> -<li class="stepexpand"><span>Create a static or a dynamic Web project if you have not already -done so.</span></li> - -<li class="stepexpand"><span>In the Project Explorer, expand your project and right click on -your WebContent folder or on a subfolder under WebContent. </span> Note -that if you choose any other folder in which to create the HTML file, then -it will not be included in the WAR file that is deployed to the server. In -addition, link validation will not encompass files that are not under the -WebContent folder.</li> - -<li class="stepexpand"><span>From the context menu, select <span class="menucascade"><span class="uicontrol">New</span> - > <span class="uicontrol">Other</span> > <span class="uicontrol">Web</span> > <span class="uicontrol">HTML</span> -</span>.</span> The New HTML Page window appears with your -folder selected</li> - -<li class="stepexpand"><span>Type a file name into the File name field, making sure you include -an html extension (html, htm, xhtml, htpl, wml, shtml, or shtm) in the file -name.</span></li> - -<li class="stepexpand"><span> You have several options for proceeding:</span> -<ul> -<li>To accept the defaults associated with a new HTML file, select <span class="uicontrol">Finish.</span></li> - -<li> To use a template file for the initial content of your HTML page, -select <span class="uicontrol">Next</span>. The Select HTML Template window appears. -Select the <span class="uicontrol">Use HTML Template</span> check box, and then select -one of the sample templates. You can also select the <span class="uicontrol">HTML Templates</span> link -to add or remove HTML templates to your list of templates.</li> - -</ul> - -</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.dita deleted file mode 100644 index 5e75b315ef..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.dita +++ /dev/null @@ -1,42 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjcrejsp" xml:lang="en-us">
-<title>Creating JavaServer Pages (JSP) files</title>
-<prolog><metadata>
-<keywords><indexterm>JSP files<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>Most types of JSP files can be created using the New JSP File
-wizard. To create a basic JSP file using the wizard, complete the following
-steps: </p></context>
-<steps>
-<step><cmd>Create a dynamic Web project if you have not already done so.</cmd>
-</step>
-<step><cmd>In the Project Explorer, expand your project and right click on
-your WebContent folder or on a subfolder under WebContent. Note that if you
-choose any other folder in which to create the JSP, then it will not be included
-in the WAR file that is deployed to the server. In addition, link validation
-will not encompass files that are not under the WebContent folder.</cmd></step>
-<step><cmd>From the context menu, select <menucascade><uicontrol>New</uicontrol>
-<uicontrol>JSP</uicontrol></menucascade>.</cmd><stepresult>The New Java Server
-Page window appears with your folder selected</stepresult></step>
-<step><cmd>Type a file name into the File name field, making sure you include
-the jsp extension (jsp, jsv, jtpl, or jspx) in the file name.</cmd></step>
-<step><cmd> You have several options for proceeding:</cmd>
-<choices>
-<choice>To accept the defaults associated with a new JSP file, select <uicontrol>Finish.</uicontrol></choice>
-<choice>To link to a file in the file system and specify path variables, select <uicontrol>Advanced</uicontrol> and
-then make your selections using the <uicontrol>Browse</uicontrol> and <uicontrol>Variables</uicontrol> buttons. </choice>
-<choice> To use a template file for the initial content of your JSP page,
-select <uicontrol>Next</uicontrol>. The Select JSP Template window appears.
-Select the <uicontrol>Use JSP Template</uicontrol> check box, and then select
-one of the sample templates. You can also select the <uicontrol>JSP Templates</uicontrol> link
-to add or remove JSP templates to your list of templates.</choice>
-</choices>
-</step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.html deleted file mode 100644 index 0c563029a9..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjcrejsp.html +++ /dev/null @@ -1,72 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating JavaServer Pages (JSP) files" /> -<meta content="JSP files, creating" name="DC.subject" /> -<meta content="JSP files, creating" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tjcrejsp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating JavaServer Pages (JSP) files</title> -</head> -<body id="tjcrejsp"><a name="tjcrejsp"><!-- --></a> - - -<h1 class="topictitle1">Creating JavaServer Pages (JSP) files</h1> - - -<div> -<div class="section"><p>Most types of JSP files can be created using the New JSP File -wizard. To create a basic JSP file using the wizard, complete the following -steps: </p> -</div> - -<ol> -<li class="stepexpand"><span>Create a dynamic Web project if you have not already done so.</span> -</li> - -<li class="stepexpand"><span>In the Project Explorer, expand your project and right click on -your WebContent folder or on a subfolder under WebContent. Note that if you -choose any other folder in which to create the JSP, then it will not be included -in the WAR file that is deployed to the server. In addition, link validation -will not encompass files that are not under the WebContent folder.</span></li> - -<li class="stepexpand"><span>From the context menu, select <span class="menucascade"><span class="uicontrol">New</span> - > <span class="uicontrol">JSP</span></span>.</span> The New Java Server -Page window appears with your folder selected</li> - -<li class="stepexpand"><span>Type a file name into the File name field, making sure you include -the jsp extension (jsp, jsv, jtpl, or jspx) in the file name.</span></li> - -<li class="stepexpand"><span> You have several options for proceeding:</span> -<ul> -<li>To accept the defaults associated with a new JSP file, select <span class="uicontrol">Finish.</span></li> - -<li>To link to a file in the file system and specify path variables, select <span class="uicontrol">Advanced</span> and -then make your selections using the <span class="uicontrol">Browse</span> and <span class="uicontrol">Variables</span> buttons. </li> - -<li> To use a template file for the initial content of your JSP page, -select <span class="uicontrol">Next</span>. The Select JSP Template window appears. -Select the <span class="uicontrol">Use JSP Template</span> check box, and then select -one of the sample templates. You can also select the <span class="uicontrol">JSP Templates</span> link -to add or remove JSP templates to your list of templates.</li> - -</ul> - -</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.dita deleted file mode 100644 index deffb67b5f..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.dita +++ /dev/null @@ -1,28 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tjdetags" xml:lang="en-us">
-<title>Creating and editing Web pages - overview</title>
-<prolog><metadata>
-<keywords><indexterm>Web pages<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>To aid in Web site development and editing, there is local tag
-hover help for all supported tag sets, as well as <xref href="../../org.eclipse.wst.sse.doc.user/topics/csrcedt006.dita"
-scope="peer"><desc></desc>content assist</xref> (Ctrl+Spacebar), a tool that
-helps you insert or finish a tag or function or finish a line of code in a
-structured text editor.</p><p> You can toggle among various viewing modes
-(which are determined by file type) to visually design pages, work with HTML, <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="JavaScript">JavaScript</tm> or
-JSP content, and preview your pages. To help you create the visual impact
-you want on your Web sites, the editor includes its own library of reusable
-graphics and two graphic programs for creating, editing, and animating image
-files. </p><note>Use either uppercase or lowercase alphanumeric characters
-consistently when naming HTML files and embedded files (such as image files)
-used in your Web pages, because some server operating systems are case sensitive.
-Do not use spaces or special characters such as exclamation points or question
-marks in file names.</note> </context>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.html deleted file mode 100644 index 14cec57b25..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjdetags.html +++ /dev/null @@ -1,48 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating and editing Web pages - overview" /> -<meta content="Web pages, creating" name="DC.subject" /> -<meta content="Web pages, creating" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tjdetags" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating and editing Web pages - overview</title> -</head> -<body id="tjdetags"><a name="tjdetags"><!-- --></a> - - -<h1 class="topictitle1">Creating and editing Web pages - overview</h1> - - -<div> -<div class="section"> <p>To aid in Web site development and editing, there is local tag -hover help for all supported tag sets, as well as <a href="../../org.eclipse.wst.sse.doc.user/topics/csrcedt006.html" title="">content assist</a> (Ctrl+Spacebar), a tool that -helps you insert or finish a tag or function or finish a line of code in a -structured text editor.</p> -<p> You can toggle among various viewing modes -(which are determined by file type) to visually design pages, work with HTML, JavaScriptâ„¢ or -JSP content, and preview your pages. To help you create the visual impact -you want on your Web sites, the editor includes its own library of reusable -graphics and two graphic programs for creating, editing, and animating image -files. </p> -<div class="note"><span class="notetitle">Note:</span> Use either uppercase or lowercase alphanumeric characters -consistently when naming HTML files and embedded files (such as image files) -used in your Web pages, because some server operating systems are case sensitive. -Do not use spaces or special characters such as exclamation points or question -marks in file names.</div> - </div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.dita deleted file mode 100644 index 94e4948b25..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.dita +++ /dev/null @@ -1,62 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<!-- ArborText, Inc., 1988-2002, v.4002-->
-<task id="tjprefs" xml:lang="en-us">
-<title>Defining HTML file preferences</title>
-<prolog><metadata>
-<keywords>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p><indexterm>DOCTYPE declarations<indexterm>adding automatically</indexterm></indexterm>
-<indexterm>HTML files<indexterm>editing preferences</indexterm></indexterm>
-To define general HTML file preferences, complete the following
-steps::</p></context>
-<steps>
-<step><cmd>From the <uicontrol>Window</uicontrol> menu, select <uicontrol>Preferences</uicontrol>.</cmd>
-</step>
-<step><cmd>In the Preferences window, select <menucascade><uicontrol>Web and
-XML</uicontrol><uicontrol>HTML Files</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Specify the following settings related to saving an HTML source
-page. The defaults are recommended and should only be modified when there
-is a specific reason to do so. </cmd><info><dl><dlentry>
-<dt>Line delimiter</dt>
-<dd>Specify the appropriate EOL character for your environment. The default
-is <uicontrol>No translation</uicontrol>.</dd>
-</dlentry><dlentry>
-<dt>Add this suffix</dt>
-<dd>Specify a default suffix for files that you save. The default is <userinput>html</userinput>.</dd>
-</dlentry><dlentry>
-<dt>Encoding, IANA, (Use workbench default)</dt>
-<dd>Specify the default encoding (code page) for files that you create. The
-default is the Workbench's encoding preference. </dd>
-</dlentry><dlentry>
-<dt>Insert DOCTYPE declaration</dt>
-<dd>Optionally, you can automatically add a DOCTYPE declaration to HTML files.
-The default DOCTYPE is determined when you create an HTML file or a JSP file
-using a wizard. If you add the DOCTYPE declaration, you should include at
-least a Public ID specification, and, optionally, a System ID.</dd>
-</dlentry><dlentry>
-<dt>Insert GENERATOR with META tag</dt>
-<dd>Optionally, select the check box to specify GENERATOR in a META tag in
-the HTML file header.</dd>
-</dlentry><dlentry>
-<dt>Loading files</dt>
-<dd>Specify the default encoding (code page) for files that you open. The
-default is the Workbench's encoding preference. Deselect the <uicontrol>Use
-workbench default</uicontrol> check box to select another encoding. <note>Encoding
-detection (when loading files) is performed in the following order: <ul>
-<li>Locate the encoding name embedded in the document.</li>
-<li>When no encoding is embedded in the document, an automatic encoding detector
-attempts to determine encoding used in the document.</li>
-<li>If the encoding still cannot be determined, the encoding defined in the <uicontrol>Encoding</uicontrol> field
-is used.</li>
-</ul> </note> </dd>
-</dlentry></dl> </info></step>
-<step><cmd>Click <uicontrol>Apply</uicontrol> then <uicontrol>OK</uicontrol> to
-save your changes.</cmd></step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.html deleted file mode 100644 index 65ab12d865..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tjprefs.html +++ /dev/null @@ -1,101 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Defining HTML file preferences" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tjprefs" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Defining HTML file preferences</title> -</head> -<body id="tjprefs"><a name="tjprefs"><!-- --></a> - - -<h1 class="topictitle1">Defining HTML file preferences</h1> - - -<div> -<div class="section"> <p> -To define general HTML file preferences, complete the following -steps::</p> -</div> - -<ol> -<li class="stepexpand"><span>From the <span class="uicontrol">Window</span> menu, select <span class="uicontrol">Preferences</span>.</span> -</li> - -<li class="stepexpand"><span>In the Preferences window, select <span class="menucascade"><span class="uicontrol">Web and -XML</span> > <span class="uicontrol">HTML Files</span></span>.</span></li> - -<li class="stepexpand"><span>Specify the following settings related to saving an HTML source -page. The defaults are recommended and should only be modified when there -is a specific reason to do so. </span> <dl> -<dt class="dlterm">Line delimiter</dt> - -<dd>Specify the appropriate EOL character for your environment. The default -is <span class="uicontrol">No translation</span>.</dd> - - -<dt class="dlterm">Add this suffix</dt> - -<dd>Specify a default suffix for files that you save. The default is <kbd class="userinput">html</kbd>.</dd> - - -<dt class="dlterm">Encoding, IANA, (Use workbench default)</dt> - -<dd>Specify the default encoding (code page) for files that you create. The -default is the Workbench's encoding preference. </dd> - - -<dt class="dlterm">Insert DOCTYPE declaration</dt> - -<dd>Optionally, you can automatically add a DOCTYPE declaration to HTML files. -The default DOCTYPE is determined when you create an HTML file or a JSP file -using a wizard. If you add the DOCTYPE declaration, you should include at -least a Public ID specification, and, optionally, a System ID.</dd> - - -<dt class="dlterm">Insert GENERATOR with META tag</dt> - -<dd>Optionally, select the check box to specify GENERATOR in a META tag in -the HTML file header.</dd> - - -<dt class="dlterm">Loading files</dt> - -<dd>Specify the default encoding (code page) for files that you open. The -default is the Workbench's encoding preference. Deselect the <span class="uicontrol">Use -workbench default</span> check box to select another encoding. <div class="note"><span class="notetitle">Note:</span> Encoding -detection (when loading files) is performed in the following order: <ul> -<li>Locate the encoding name embedded in the document.</li> - -<li>When no encoding is embedded in the document, an automatic encoding detector -attempts to determine encoding used in the document.</li> - -<li>If the encoding still cannot be determined, the encoding defined in the <span class="uicontrol">Encoding</span> field -is used.</li> - -</ul> - </div> - </dd> - -</dl> - </li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Apply</span> then <span class="uicontrol">OK</span> to -save your changes.</span></li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.dita deleted file mode 100644 index 3c481d76cd..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.dita +++ /dev/null @@ -1,21 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="tservertarget" xml:lang="en-us">
-<title>Server targeting for Web applications</title>
-<prolog><metadata>
-<keywords><indexterm>servers<indexterm>targeting</indexterm></indexterm><indexterm>Web applications<indexterm>server targeting</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>To support different J2EE application servers, the J2EE tooling allows
-you to target a specific server during your Enterprise Application (EAR) project
-development. In most cases, a Web project must target the same server as the
-EAR project in order to deploy the Web application to the server properly. </p>
-<p>After you have a Web project created, you can modify the target server
-using the project's properties dialog. To do this, right-click on the project
-in the Project Explorer view, and select <menucascade><uicontrol>Properties</uicontrol>
-<uicontrol>Server</uicontrol></menucascade>.</p>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.html deleted file mode 100644 index 6980747141..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tservertarget.html +++ /dev/null @@ -1,41 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Server targeting for Web applications" /> -<meta content="servers, targeting, Web applications, server targeting" name="DC.subject" /> -<meta content="servers, targeting, Web applications, server targeting" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tservertarget" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Server targeting for Web applications</title> -</head> -<body id="tservertarget"><a name="tservertarget"><!-- --></a> - - -<h1 class="topictitle1">Server targeting for Web applications</h1> - - -<div> -<p>To support different J2EE application servers, the J2EE tooling allows -you to target a specific server during your Enterprise Application (EAR) project -development. In most cases, a Web project must target the same server as the -EAR project in order to deploy the Web application to the server properly. </p> - -<p>After you have a Web project created, you can modify the target server -using the project's properties dialog. To do this, right-click on the project -in the Project Explorer view, and select <span class="menucascade"><span class="uicontrol">Properties</span> - > <span class="uicontrol">Server</span></span>.</p> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.dita deleted file mode 100644 index bef37e29d5..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.dita +++ /dev/null @@ -1,42 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tstylesheet" xml:lang="en-us">
-<title>Creating cascading style sheets</title>
-<shortdesc>Cascading style sheets enable you to define a consistent look and
-feel throughout your Web site by maintaining the contents (Web pages) and
-the design (the style sheet) separately.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>style sheets<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>To create a new cascading style sheet:</context>
-<steps>
-<step><cmd>Create a static or a dynamic Web project if you have not already
-done so.</cmd></step>
-<step><cmd>In the Project Explorer, expand your project and right click on
-your WebContent folder or on a subfolder under WebContent. </cmd><info>Note
-that if you choose any other folder in which to create the CSS file, then
-it will not be included in the WAR file that is deployed to the server. </info>
-</step>
-<step><cmd>From the context menu, select <menucascade><uicontrol>New</uicontrol>
-<uicontrol>Other</uicontrol><uicontrol>Web</uicontrol><uicontrol>CSS</uicontrol>
-</menucascade>.</cmd><stepresult>The New Cascading Style Sheet window appears
-with your folder selected</stepresult></step>
-<step><cmd>Type a file name into the File name field, making sure you include
-a css extension in the file name.</cmd></step>
-<step><cmd> You have several options for proceeding:</cmd>
-<choices>
-<choice>To accept the defaults associated with a new CSS file, select <uicontrol>Finish.</uicontrol></choice>
-<choice> To use a template file for the initial content of your CSS file,
-select <uicontrol>Next</uicontrol>. The Select CSS Template window appears.
-Select the <uicontrol>Use CSS Template</uicontrol> check box, and then select
-one of the sample templates. You can also select the <uicontrol>CSS Templates</uicontrol> link
-to add or remove HTML templates to your list of templates.</choice>
-</choices>
-</step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.html b/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.html deleted file mode 100644 index d3aa09b5c7..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/tstylesheet.html +++ /dev/null @@ -1,73 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating cascading style sheets" /> -<meta name="abstract" content="Cascading style sheets enable you to define a consistent look and feel throughout your Web site by maintaining the contents (Web pages) and the design (the style sheet) separately." /> -<meta name="description" content="Cascading style sheets enable you to define a consistent look and feel throughout your Web site by maintaining the contents (Web pages) and the design (the style sheet) separately." /> -<meta content="style sheets, creating" name="DC.subject" /> -<meta content="style sheets, creating" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tstylesheet" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating cascading style sheets</title> -</head> -<body id="tstylesheet"><a name="tstylesheet"><!-- --></a> - - -<h1 class="topictitle1">Creating cascading style sheets</h1> - - - -<div><p>Cascading style sheets enable you to define a consistent look and -feel throughout your Web site by maintaining the contents (Web pages) and -the design (the style sheet) separately.</p> - -<div class="section">To create a new cascading style sheet:</div> - -<ol> -<li class="stepexpand"><span>Create a static or a dynamic Web project if you have not already -done so.</span></li> - -<li class="stepexpand"><span>In the Project Explorer, expand your project and right click on -your WebContent folder or on a subfolder under WebContent. </span> Note -that if you choose any other folder in which to create the CSS file, then -it will not be included in the WAR file that is deployed to the server. -</li> - -<li class="stepexpand"><span>From the context menu, select <span class="menucascade"><span class="uicontrol">New</span> - > <span class="uicontrol">Other</span> > <span class="uicontrol">Web</span> > <span class="uicontrol">CSS</span> -</span>.</span> The New Cascading Style Sheet window appears -with your folder selected</li> - -<li class="stepexpand"><span>Type a file name into the File name field, making sure you include -a css extension in the file name.</span></li> - -<li class="stepexpand"><span> You have several options for proceeding:</span> -<ul> -<li>To accept the defaults associated with a new CSS file, select <span class="uicontrol">Finish.</span></li> - -<li> To use a template file for the initial content of your CSS file, -select <span class="uicontrol">Next</span>. The Select CSS Template window appears. -Select the <span class="uicontrol">Use CSS Template</span> check box, and then select -one of the sample templates. You can also select the <span class="uicontrol">CSS Templates</span> link -to add or remove HTML templates to your list of templates.</li> - -</ul> - -</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.dita deleted file mode 100644 index e2b3adda77..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.dita +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<!-- ArborText, Inc., 1988-2002, v.4002-->
-<task id="twcreprj" xml:lang="en-us">
-<title>Creating a dynamic Web project</title>
-<shortdesc>You create and maintain the resources for your Web applications
-in Web projects.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>Web projects<indexterm>creating dynamic projects</indexterm></indexterm>
-<indexterm>Web applications<indexterm>resources</indexterm></indexterm>
-
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p> Unlike with <xref href="twcresta.dita" scope="peer"><desc></desc>static</xref> Web
-projects, dynamic Web projects enable you to create resources such as JavaServer
-Pages and servlets.</p><p>To create a new dynamic Web project, complete the
-following steps:</p></context>
-<steps>
-<step><cmd>Open the J2EE perspective.</cmd></step>
-<step><cmd>In the Project Explorer, right click on Dynamic Web Projects, and
-select <menucascade><uicontrol>New</uicontrol><uicontrol>Dynamic Web Project</uicontrol>
-</menucascade> from the context menu. The New Dynamic Web Project wizard starts.</cmd>
-</step>
-<step><cmd>Follow the project wizard prompts.</cmd></step>
-</steps>
-<postreq><p><b>General Information</b></p><dl><dlentry>
-<dt>Project Facets </dt>
-<dd>A facet represents a unit of functionality in a Web project. For example,
-the Dynamic Web Module facet enables the project to be deployed as a dynamic
-Web module. A brief description of a project facet appears in the wizard when
-you select it. Note that in many instances, you can view the constraints
-for a project facet by right clicking on the facet and selecting project constraints
-from the pop up menu. </dd>
-</dlentry><dlentry>
-<dt>Target Runtime</dt>
-<dd>Use this field to define a new installed runtime environment. Runtimes
-are used at build time to compile projects.</dd>
-</dlentry><dlentry>
-<dt>Enterprise Application project (EAR Project)</dt>
-<dd>A new or existing Enterprise Application project (EAR Project) must be
-associated with your new Web project to facilitate deployment. If you want
-to override the default settings for the Enterprise Application project, you
-can do so using the wizard. When your Web project is created at the end of
-the wizard, the new Enterprise Application project is also created with the
-name specified in the EAR project field. Note that the default is the name
-of the web project appended with EAR (unless the ear project was selected
-when you opened the wizard.)</dd>
-</dlentry><dlentry>
-<dt>Context Root</dt>
-<dd>The context root is the Web application root, which is the top-level directory
-of your application when it is deployed to the Web server. You can change
-the context root after you create a project using the project Properties dialog,
-which you access from the project's pop-up menu. The context root can also
-be used by the links builder to ensure that your links remain ready to publish
-as you move and rename files inside your project.</dd>
-</dlentry></dl></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.html deleted file mode 100644 index a4699b078d..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twcreprj.html +++ /dev/null @@ -1,97 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating a dynamic Web project" /> -<meta name="abstract" content="You create and maintain the resources for your Web applications in Web projects." /> -<meta name="description" content="You create and maintain the resources for your Web applications in Web projects." /> -<meta content="dynamic Web projects, creating, Web projects, dynamic" name="DC.subject" /> -<meta content="dynamic Web projects, creating, Web projects, dynamic" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twcreprj" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating a dynamic Web project</title> -</head> -<body id="twcreprj"><a name="twcreprj"><!-- --></a> - - -<h1 class="topictitle1">Creating a dynamic Web project</h1> - - - -<div><p>You create and maintain the resources for your Web applications -in Web projects.</p> - -<div class="section"> <p> Unlike with <a href="twcresta.html" title="">static</a> Web -projects, dynamic Web projects enable you to create resources such as JavaServer -Pages and servlets.</p> -<p>To create a new dynamic Web project, complete the -following steps:</p> -</div> - -<ol> -<li><span>Open the J2EE perspective.</span></li> - -<li><span>In the Project Explorer, right click on Dynamic Web Projects, and -select <span class="menucascade"><span class="uicontrol">New</span> > <span class="uicontrol">Dynamic Web Project</span> -</span> from the context menu. The New Dynamic Web Project wizard starts.</span> -</li> - -<li><span>Follow the project wizard prompts.</span></li> - -</ol> - -<div class="section"><p><strong>General Information</strong></p> -<dl> -<dt class="dlterm">Project Facets </dt> - -<dd>A facet represents a unit of functionality in a Web project. For example, -the Dynamic Web Module facet enables the project to be deployed as a dynamic -Web module. A brief description of a project facet appears in the wizard when -you select it. Note that in many instances, you can view the constraints -for a project facet by right clicking on the facet and selecting project constraints -from the pop up menu. </dd> - - -<dt class="dlterm">Target Runtime</dt> - -<dd>Use this field to define a new installed runtime environment. Runtimes -are used at build time to compile projects.</dd> - - -<dt class="dlterm">Enterprise Application project (EAR Project)</dt> - -<dd>A new or existing Enterprise Application project (EAR Project) must be -associated with your new Web project to facilitate deployment. If you want -to override the default settings for the Enterprise Application project, you -can do so using the wizard. When your Web project is created at the end of -the wizard, the new Enterprise Application project is also created with the -name specified in the EAR project field. Note that the default is the name -of the web project appended with EAR (unless the ear project was selected -when you opened the wizard.)</dd> - - -<dt class="dlterm">Context Root</dt> - -<dd>The context root is the Web application root, which is the top-level directory -of your application when it is deployed to the Web server. You can change -the context root after you create a project using the project Properties dialog, -which you access from the project's pop-up menu. The context root can also -be used by the links builder to ensure that your links remain ready to publish -as you move and rename files inside your project.</dd> - -</dl> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.dita deleted file mode 100644 index f3e6b59b99..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.dita +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twcresta" xml:lang="en-us">
-<title>Creating a static Web project</title>
-<shortdesc></shortdesc>
-<prolog><metadata>
-<keywords><indexterm>static Web projects<indexterm>creating</indexterm></indexterm>
-<indexterm>Web projects<indexterm>creating static</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> In the workbench, you create and maintain resources for Web applications
-in Web projects. If you want to create a static, content-based Web application
-that contains no dynamic elements, such as JSP files or servlets, use the <ph><uicontrol>New
-Static Web Project</uicontrol></ph> wizard. </p><p>To create a new static
-Web project, complete the following steps:</p></context>
-<steps>
-<step><cmd>Open the J2EE perspective </cmd><info></info></step>
-<step><cmd>In the Project Explorer, right click on Other Projects and select <b>New->Other->Web->Static
-Web Project</b> from the context menu. The New Static Web Project wizard starts. </cmd>
-</step>
-<step><cmd>Follow the project wizard prompts</cmd><info></info></step>
-</steps>
-<postreq><p><b>General Information</b></p><dl><dlentry>
-<dt>Project Facets </dt>
-<dd>A facet represents a unit of functionality in a Web project. For example,
-the Static Web Module facet enables the project to be deployed as a static
-Web module. A brief description of a project facet appears in the wizard when
-you select it. Note that in many instances, you can view the constraints
-for a project facet by right clicking on the facet and selecting project constraints
-from the pop up menu. </dd>
-</dlentry><dlentry>
-<dt>Target Runtime</dt>
-<dd>Use this field to define a new installed runtime environment. Runtimes
-are used at build time to compile projects. </dd>
-</dlentry></dl><dl><dlentry>
-<dt>Web Content Folder</dt>
-<dd>The folder in which you want to store your publishable resources. </dd>
-</dlentry></dl></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.html deleted file mode 100644 index 45e52f6c27..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twcresta.html +++ /dev/null @@ -1,80 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating a static Web project" /> -<meta name="abstract" content="" /> -<meta name="description" content="" /> -<meta content="static Web projects, creating, Web projects, creating static" name="DC.subject" /> -<meta content="static Web projects, creating, Web projects, creating static" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twcresta" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating a static Web project</title> -</head> -<body id="twcresta"><a name="twcresta"><!-- --></a> - - -<h1 class="topictitle1">Creating a static Web project</h1> - - - -<div><p /> - -<div class="section"><p> In the workbench, you create and maintain resources for Web applications -in Web projects. If you want to create a static, content-based Web application -that contains no dynamic elements, such as JSP files or servlets, use the <span><span class="uicontrol">New -Static Web Project</span></span> wizard. </p> -<p>To create a new static -Web project, complete the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the J2EE perspective </span> </li> - -<li class="stepexpand"><span>In the Project Explorer, right click on Other Projects and select <strong>New->Other->Web->Static -Web Project</strong> from the context menu. The New Static Web Project wizard starts. </span> -</li> - -<li class="stepexpand"><span>Follow the project wizard prompts</span> </li> - -</ol> - -<div class="section"><p><strong>General Information</strong></p> -<dl> -<dt class="dlterm">Project Facets </dt> - -<dd>A facet represents a unit of functionality in a Web project. For example, -the Static Web Module facet enables the project to be deployed as a static -Web module. A brief description of a project facet appears in the wizard when -you select it. Note that in many instances, you can view the constraints -for a project facet by right clicking on the facet and selecting project constraints -from the pop up menu. </dd> - - -<dt class="dlterm">Target Runtime</dt> - -<dd>Use this field to define a new installed runtime environment. Runtimes -are used at build time to compile projects. </dd> - -</dl> -<dl> -<dt class="dlterm">Web Content Folder</dt> - -<dd>The folder in which you want to store your publishable resources. </dd> - -</dl> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.dita deleted file mode 100644 index 86699ab894..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.dita +++ /dev/null @@ -1,33 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twcrewar" xml:lang="en-us">
-<title>Exporting Web Archive (WAR) files</title>
-<prolog><metadata>
-<keywords><indexterm>exporting<indexterm>WAR files</indexterm></indexterm>
-<indexterm>WAR files<indexterm>exporting</indexterm></indexterm>
-<indexterm>Web projects<indexterm>exporting WAR files</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p> A Web archive (WAR) file is a packaged Web application that
-can be exported to test, publish, and deploy the resources developed within
-a Web project.</p><p>To export a WAR file from a Web project, do the following: </p></context>
-<steps>
-<step><cmd>Right click on a Web project folder and select <b>Export</b> from
-the pop-up menu. Then select<b> WAR file</b> in the Export window and then
-select <b>Next</b>.</cmd></step>
-<step><cmd>Specify the Web project you want to export (this field is primed
-if you used the pop-up menu to open the wizard), and specify a location for
-the new WAR file</cmd></step>
-<step importance="optional"><cmd>Optionally, supply WAR export <ph>Options</ph>,
-such as whether or not to include <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> source files in the WAR, and whether
-to overwrite any existing resources during the export process. </cmd><info>Source
-files are not usually included in a WAR file, because they are not necessary
-for the server to run the web application.</info></step>
-<step><cmd>Click <ph><uicontrol>Finish</uicontrol></ph>.</cmd></step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.html deleted file mode 100644 index 15d45370f3..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twcrewar.html +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Exporting Web Archive (WAR) files" /> -<meta content="WAR files, exporting, War files, Web projects, exporting WAR files, War files" name="DC.subject" /> -<meta content="WAR files, exporting, War files, Web projects, exporting WAR files, War files" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twcrewar" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Exporting Web Archive (WAR) files</title> -</head> -<body id="twcrewar"><a name="twcrewar"><!-- --></a> - - -<h1 class="topictitle1">Exporting Web Archive (WAR) files</h1> - - -<div> -<div class="section"> <p> A Web archive (WAR) file is a packaged Web application that -can be exported to test, publish, and deploy the resources developed within -a Web project.</p> -<p>To export a WAR file from a Web project, do the following: </p> -</div> - -<ol> -<li class="stepexpand"><span>Right click on a Web project folder and select <strong>Export</strong> from -the pop-up menu. Then select<strong> WAR file</strong> in the Export window and then -select <strong>Next</strong>.</span></li> - -<li class="stepexpand"><span>Specify the Web project you want to export (this field is primed -if you used the pop-up menu to open the wizard), and specify a location for -the new WAR file</span></li> - -<li class="stepexpand"><strong>Optional: </strong><span>Optionally, supply WAR export <span>Options</span>, -such as whether or not to include Javaâ„¢ source files in the WAR, and whether -to overwrite any existing resources during the export process. </span> Source -files are not usually included in a WAR file, because they are not necessary -for the server to run the web application.</li> - -<li class="stepexpand"><span>Click <span><span class="uicontrol">Finish</span></span>.</span></li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.dita deleted file mode 100644 index 66cfcc864c..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.dita +++ /dev/null @@ -1,37 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twcvsr" xml:lang="en-us">
-<title>Setting CVS repository defaults</title>
-<prolog><metadata>
-<keywords><indexterm>build output folders<indexterm>ignoring in CVS</indexterm></indexterm>
-<indexterm>CVS<indexterm>setting repository defaults</indexterm></indexterm>
-<indexterm>cvsignore files<indexterm>creating</indexterm></indexterm>
-<indexterm>repositories<indexterm>default CVS settings</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>When you use a CVS repository during team development, you might
-want to use the following setup to ensure that the CVS versioning support
-ignores the project's build output folder:</p> </context>
-<steps>
-<step><cmd>Create a file called .cvsignore in your project's <filepath>WebContent/WEB-INF</filepath> folder.</cmd>
-</step>
-<step><cmd>In this file, add a line with the name of the build output folder
-(for example, <codeph>classes</codeph>).</cmd><info><p>Currently, you have
-the option of creating this file automatically (as a feature) when using the
-New Dynamic Web Project wizard.</p><p>When you synchronize with a CVS team
-stream, the output folder will be ignored.</p></info></step>
-<step><cmd>In addition, you should turn off the <ph><uicontrol>Prune empty
-directories</uicontrol></ph> option. Select <ph><menucascade><uicontrol>Windows</uicontrol>
-<uicontrol>Preferences</uicontrol></menucascade></ph>, switch to the <ph><menucascade>
-<uicontrol>Team</uicontrol><uicontrol>CVS</uicontrol></menucascade></ph> properties
-page, and ensure that the <ph><uicontrol>Prune empty directories</uicontrol></ph> check
-box is not checked.</cmd><info><p>If this option is enabled and your Web project's
-source directory is empty, it will be deleted when the project is added to
-your workspace from a CVS repository, causing a <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> build error.</p></info></step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.html deleted file mode 100644 index bea54aa4aa..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twcvsr.html +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting CVS repository defaults" /> -<meta content="CVS, setting repository defaults, cvsignore file, creating" name="DC.subject" /> -<meta content="CVS, setting repository defaults, cvsignore file, creating" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twcvsr" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting CVS repository defaults</title> -</head> -<body id="twcvsr"><a name="twcvsr"><!-- --></a> - - -<h1 class="topictitle1">Setting CVS repository defaults</h1> - - -<div> -<div class="section"> <p>When you use a CVS repository during team development, you might -want to use the following setup to ensure that the CVS versioning support -ignores the project's build output folder:</p> - </div> - -<ol> -<li class="stepexpand"><span>Create a file called .cvsignore in your project's <span class="filepath">WebContent/WEB-INF</span> folder.</span> -</li> - -<li class="stepexpand"><span>In this file, add a line with the name of the build output folder -(for example, <samp class="codeph">classes</samp>).</span> <p>Currently, you have -the option of creating this file automatically (as a feature) when using the -New Dynamic Web Project wizard.</p> -<p>When you synchronize with a CVS team -stream, the output folder will be ignored.</p> -</li> - -<li class="stepexpand"><span>In addition, you should turn off the <span><span class="uicontrol">Prune empty -directories</span></span> option. Select <span><span class="menucascade"><span class="uicontrol">Windows</span> - > <span class="uicontrol">Preferences</span></span></span>, switch to the <span><span class="menucascade"> -<span class="uicontrol">Team</span> > <span class="uicontrol">CVS</span></span></span> properties -page, and ensure that the <span><span class="uicontrol">Prune empty directories</span></span> check -box is not checked.</span> <p>If this option is enabled and your Web project's -source directory is empty, it will be deleted when the project is added to -your workspace from a CVS repository, causing a Javaâ„¢ build error.</p> -</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.dita deleted file mode 100644 index a797bd37c8..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.dita +++ /dev/null @@ -1,46 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twimpwar" xml:lang="en-us">
-<title>Importing Web archive (WAR) files</title>
-<prolog><metadata>
-<keywords><indexterm>WAR files<indexterm>importing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>A Web Archive (WAR) file is a portable, packaged Web application
-that you can import into your workspace. </p><p> Before importing a WAR file,
-you should first determine if the WAR file contains needed <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> source
-files. When importing a WAR file into an existing Web project, the imported
-Web deployment descriptor files are either not changed or overwritten by the
-ones included in the imported WAR file, based on your response to the prompt
-that is provided. In either case, this action does <i>not</i> represent a
-merging of the two sets of deployment descriptors. </p> <p>To import the
-Web project resources in a WAR file into your workspace, complete the following
-steps:</p></context>
-<steps>
-<step><cmd>Select <ph><menucascade><uicontrol>File</uicontrol><uicontrol>Import</uicontrol>
-</menucascade></ph>.</cmd></step>
-<step><cmd> In the Import dialog, select <ph><uicontrol>WAR file</uicontrol></ph> and
-then click <ph><uicontrol>Next</uicontrol></ph>. </cmd></step>
-<step><cmd>Locate the WAR file that you want to import using the <ph><uicontrol>Browse</uicontrol></ph> button.</cmd>
-</step>
-<step><cmd> The wizard assumes you want to create a new Web project with the
-same name as the WAR file. If you accept this choice, the project will be
-created with the same servlet version as specified by the WAR file and in
-the same location. If you want to override these settings, you can click <b>New</b> and
-specify your new settings in the Dynamic Web Project wizard.</cmd><info> <p>If
-you want to import the WAR file into an existing Web project, you can select
-the project from the Web project drop-down list. Note that if you select an
-existing project, you must decide whether you want to select the setting to <b>overwrite
-existing resources without warning</b></p></info></step>
-<step><cmd>Click <ph><uicontrol>Finish</uicontrol></ph> to populate the Web
-project.</cmd></step>
-</steps>
-</taskbody>
-<related-links>
-<linkpool type="concept"></linkpool>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.html deleted file mode 100644 index 0ad0a96ca3..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twimpwar.html +++ /dev/null @@ -1,72 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Importing Web archive (WAR) files" /> -<meta content="WAR files, importing" name="DC.subject" /> -<meta content="WAR files, importing" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twimpwar" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Importing Web archive (WAR) files</title> -</head> -<body id="twimpwar"><a name="twimpwar"><!-- --></a> - - -<h1 class="topictitle1">Importing Web archive (WAR) files</h1> - - -<div> -<div class="section"> <p>A Web Archive (WAR) file is a portable, packaged Web application -that you can import into your workspace. </p> -<p> Before importing a WAR file, -you should first determine if the WAR file contains needed Javaâ„¢ source -files. When importing a WAR file into an existing Web project, the imported -Web deployment descriptor files are either not changed or overwritten by the -ones included in the imported WAR file, based on your response to the prompt -that is provided. In either case, this action does <em>not</em> represent a -merging of the two sets of deployment descriptors. </p> - <p>To import the -Web project resources in a WAR file into your workspace, complete the following -steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Select <span><span class="menucascade"><span class="uicontrol">File</span> > <span class="uicontrol">Import</span> -</span></span>.</span></li> - -<li class="stepexpand"><span> In the Import dialog, select <span><span class="uicontrol">WAR file</span></span> and -then click <span><span class="uicontrol">Next</span></span>. </span></li> - -<li class="stepexpand"><span>Locate the WAR file that you want to import using the <span><span class="uicontrol">Browse</span></span> button.</span> -</li> - -<li class="stepexpand"><span> The wizard assumes you want to create a new Web project with the -same name as the WAR file. If you accept this choice, the project will be -created with the same servlet version as specified by the WAR file and in -the same location. If you want to override these settings, you can click <strong>New</strong> and -specify your new settings in the Dynamic Web Project wizard.</span> <p>If -you want to import the WAR file into an existing Web project, you can select -the project from the Web project drop-down list. Note that if you select an -existing project, you must decide whether you want to select the setting to <strong>overwrite -existing resources without warning</strong></p> -</li> - -<li class="stepexpand"><span>Click <span><span class="uicontrol">Finish</span></span> to populate the Web -project.</span></li> - -</ol> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.dita deleted file mode 100644 index 1a9890cd10..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.dita +++ /dev/null @@ -1,30 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twpcnvrt" xml:lang="en-us">
-<title>Converting static Web projects to dynamic Web projects</title>
-<prolog><metadata>
-<keywords><indexterm>static Web projects<indexterm>converting to dynamic</indexterm></indexterm>
-<indexterm>Web projects<indexterm>converting static to dynamic</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p> If you want to add dynamic elements to a static web project,
-such as <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm"
-trademark="Java">Java</tm> servlets and JSP files, you must convert the project
-from a static to a dynamic one. To convert a static Web project to a dynamic
-Web project, complete the following steps:</p> </context>
-<steps>
-<step><cmd>Select the project in the Project Explorer view, and then select <ph><uicontrol>Convert
-to a Dynamic Web Project</uicontrol></ph> from the <b>Project</b> menu.</cmd>
-<info>This conversion assumes the project name and location will be the same.
-The conversion does not change the CSS file specified in the original static
-project, so it will be included in the resulting dynamic Web project. </info>
-</step>
-<step><cmd> Specify the project properties that are available when <xref
-href="twcreprj.dita" scope="peer"><desc></desc>Creating a Dynamic Web project.</xref></cmd>
-</step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.html deleted file mode 100644 index 522a48490e..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twpcnvrt.html +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Converting static Web projects to dynamic Web projects" /> -<meta content="static Web projects, converting to dynamic, dynamic Web projects, converting from static, Web projects, dynamic" name="DC.subject" /> -<meta content="static Web projects, converting to dynamic, dynamic Web projects, converting from static, Web projects, dynamic" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twpcnvrt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Converting static Web projects to dynamic Web projects</title> -</head> -<body id="twpcnvrt"><a name="twpcnvrt"><!-- --></a> - - -<h1 class="topictitle1">Converting static Web projects to dynamic Web projects</h1> - - -<div> -<div class="section"> <p> If you want to add dynamic elements to a static web project, -such as Javaâ„¢ servlets and JSP files, you must convert the project -from a static to a dynamic one. To convert a static Web project to a dynamic -Web project, complete the following steps:</p> - </div> - -<ol> -<li class="stepexpand"><span>Select the project in the Project Explorer view, and then select <span><span class="uicontrol">Convert -to a Dynamic Web Project</span></span> from the <strong>Project</strong> menu.</span> - This conversion assumes the project name and location will be the same. -The conversion does not change the CSS file specified in the original static -project, so it will be included in the resulting dynamic Web project. -</li> - -<li class="stepexpand"><span> Specify the project properties that are available when <a href="twcreprj.html" title="">Creating a Dynamic Web project.</a></span> -</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.dita deleted file mode 100644 index afbb10d48e..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.dita +++ /dev/null @@ -1,32 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twplib" xml:lang="en-us">
-<title>Adding Web library projects</title>
-<prolog><metadata>
-<keywords><indexterm>Web library projects<indexterm>virtual JAR files and
-projects</indexterm></indexterm><indexterm>virtual JAR files associations<indexterm>Web
-library projects</indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>Web library projects allow you to associate <tm tmclass="special"
-tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> projects
-with "virtual" JAR files in a Web project's WEB-INF/lib directory. You can
-reference JAR files that exist elsewhere in the Enterprise Application project
-that contains your Web project, if they are in the Web project's build path,
-and avoid the need to explicitly copy these JAR files into the project's lib
-folder before you publish the Web application to a server.</p><p>To set up
-these associations:</p> </context>
-<steps>
-<step><cmd>Right click on a Web project and select <uicontrol>Properties</uicontrol> from
-the pop-up menu.</cmd><info></info></step>
-<step><cmd>Click on <uicontrol>J2EE Module Dependencies</uicontrol></cmd>
-</step>
-<step><cmd>Set up your associations in the J2EE Module Dependencies window</cmd>
-</step>
-<step><cmd>Click <ph><uicontrol>OK</uicontrol></ph> when you are done.</cmd>
-</step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.html deleted file mode 100644 index 6aae3985cc..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twplib.html +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding Web library projects" /> -<meta content="Web library projects, virtual JAR files and projects, virtual JAR files associations, Web library projects" name="DC.subject" /> -<meta content="Web library projects, virtual JAR files and projects, virtual JAR files associations, Web library projects" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twplib" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding Web library projects</title> -</head> -<body id="twplib"><a name="twplib"><!-- --></a> - - -<h1 class="topictitle1">Adding Web library projects</h1> - - -<div> -<div class="section"> <p>Web library projects allow you to associate Javaâ„¢ projects -with "virtual" JAR files in a Web project's WEB-INF/lib directory. You can -reference JAR files that exist elsewhere in the Enterprise Application project -that contains your Web project, if they are in the Web project's build path, -and avoid the need to explicitly copy these JAR files into the project's lib -folder before you publish the Web application to a server.</p> -<p>To set up -these associations:</p> - </div> - -<ol> -<li class="stepexpand"><span>Right click on a Web project and select <span class="uicontrol">Properties</span> from -the pop-up menu.</span> </li> - -<li class="stepexpand"><span>Click on <span class="uicontrol">J2EE Module Dependencies</span></span> -</li> - -<li class="stepexpand"><span>Set up your associations in the J2EE Module Dependencies window</span> -</li> - -<li class="stepexpand"><span>Click <span><span class="uicontrol">OK</span></span> when you are done.</span> -</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.dita deleted file mode 100644 index 23ef25ab2c..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.dita +++ /dev/null @@ -1,124 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twprjset" xml:lang="en-us">
-<title>Setting Web project properties</title>
-<prolog><metadata>
-<keywords><indexterm>Web projects<indexterm>properties settings</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>There are many Web project properties that you can set that affect
-the phases in the lifecycle of your project and its dependencies on other
-Web resources and Web development processes. You might want to verify or update
-these properties after you have updated an existing project or have imported
-Web resources into a project .</p><p>To view or set Web project properties,
-do the following: </p> </context>
-<steps>
-<step><cmd>Right-click on a Web Project, and from the pop-up menu select <ph><uicontrol>Properties</uicontrol></ph>.</cmd>
-</step>
-<step><cmd>Select a property type in the left pane of the Properties dialog
-to view or update properties in the Web project. For each property, you can
-apply changes and modify default settings. Based on whether you have a static
-or a dynamic Web project, the following property types are available:</cmd>
-<info><dl><dlentry>
-<dt>Info</dt>
-<dd>Provides general information about project type, location, and modification
-status. </dd>
-</dlentry><dlentry>
-<dt>BeanInfo Path (Dynamic Web project only)</dt>
-<dd>If you select the Enable Beaninfo Introspection on this project, you can
-specify the contents and order of <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> Bean search paths to provide Bean information
-relevant to the project. You can add, remove, and reorder (using the <ph>Up</ph> and <ph>Down</ph> buttons)
-the packages used to include Bean information.</dd>
-</dlentry><dlentry>
-<dt>Builders</dt>
-<dd>Add, remove, or reorder external tools in the build order. When you select <uicontrol>New</uicontrol> to
-create a new external tool to the list, the New External Tool wizard opens,
-so that you can define the new build tool.</dd>
-</dlentry><dlentry>
-<dt>J2EE (Dynamic Web project only)</dt>
-<dd>Identify Web level specification and modify context root and Web content
-folder name</dd>
-</dlentry><dlentry>
-<dt><tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Build
-Path (Dynamic Web project only)</dt>
-<dd>View or change the information about the <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> build path that you supplied when creating
-the project using the <ph>Create a DynamicWeb Project</ph> wizard. Whenever
-the Web project is rebuilt, any class files that are created or updated will
-be output to the specified output folder. <note>A library entry on the <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> build
-path will remain there unless the actual JAR file is deleted from the WEB-INF/lib
-folder. If you remove a library path entry but not the JAR file, the library
-entry will be re-added to the path automatically.</note></dd>
-</dlentry><dlentry>
-<dt><tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> Compiler
-(Dynamic Web project only)</dt>
-<dd>Define whether to use workspace settings or project setting for compiling <tm
-tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> code,
-including settings for Problems, Style, Compliance and Classfiles, and Build
-Path.</dd>
-</dlentry><dlentry>
-<dt>Javadoc Location (Dynamic Web project only)</dt>
-<dd>Define a default location (URL) for any Javadoc available to the project.</dd>
-</dlentry><dlentry>
-<dt><tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> JAR
-Dependencies (Dynamic Web project only)</dt>
-<dd>Define and reorder JAR dependencies for the project. Note that these dependencies
-may differ based on a Web project's association with multiple Enterprise application
-projects.</dd>
-</dlentry><dlentry>
-<dt>JSP Task Tags</dt>
-<dd>Add, edit, or remove JSP task tags and assign tag priorities. These "to
-do" items appear in your Tasks view.</dd>
-</dlentry><dlentry>
-<dt>JSP Compilation</dt>
-<dd>Specify when in the build process a JSP should be set to compile</dd>
-</dlentry><dlentry>
-<dt>JSP Fragment (dynamic Web project only)</dt>
-<dd>Define default encoding, page directive, and content type values for JSP
-fragment documents in the web project.</dd>
-</dlentry><dlentry>
-<dt>Links Validation/Refactoring</dt>
-<dd>Define project-level link management and validation settings. These settings
-override corresponding settings in the Workbench Preference settings for the
-current project.</dd>
-</dlentry><dlentry>
-<dt>Project References</dt>
-<dd>Reference other Web projects that exist on your workbench workspace.</dd>
-</dlentry><dlentry>
-<dt>Server</dt>
-<dd>Select the server instance used to perform necessary development, test,
-and publishing functions for the project.</dd>
-</dlentry><dlentry>
-<dt>Validation</dt>
-<dd>Specify which validators should run for the project, and whether validation
-should occur automatically when resource updates are written to the project.
-The available validators are based on the types of resources in your project.
-By default, validators are automatically run when you save resources in a
-Web project. If you do not want validators to run automatically when you save
-these resources, enable the <uicontrol>Override validation</uicontrol> preferences
-option and disable the <uicontrol>Run validation automatically when you save
-changes to resources</uicontrol> option. <note>You can also disable automatic
-validation (and builds) for all projects by disabling <uicontrol>Perform build
- automatically on resource modification</uicontrol> from the <uicontrol>Workbench</uicontrol> properties.
-If you disable automatic builds, you can manually run a build (and validation)
-by selecting <menucascade><uicontrol>Project</uicontrol><uicontrol>Rebuild
-project</uicontrol></menucascade>.</note></dd>
-</dlentry><dlentry>
-<dt>Web Content Settings</dt>
-<dd>Provide any applicable Web content settings for a Web project. You can
-specify the document type, CSS profile, and target device.</dd>
-</dlentry><dlentry>
-<dt>Web Project Features</dt>
-<dd>Select the features you want to be enabled for your Web project, such
-as Page Template support.</dd>
-</dlentry></dl></info></step>
-<step><cmd>When you have completed updates to Web project settings, click <ph><uicontrol>OK</uicontrol></ph> to
-save and close the Properties dialog.</cmd></step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.html deleted file mode 100644 index 8fcec30301..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twprjset.html +++ /dev/null @@ -1,182 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting Web project properties" /> -<meta content="Web projects, properties settings" name="DC.subject" /> -<meta content="Web projects, properties settings" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twprjset" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting Web project properties</title> -</head> -<body id="twprjset"><a name="twprjset"><!-- --></a> - - -<h1 class="topictitle1">Setting Web project properties</h1> - - -<div> -<div class="section"> <p>There are many Web project properties that you can set that affect -the phases in the lifecycle of your project and its dependencies on other -Web resources and Web development processes. You might want to verify or update -these properties after you have updated an existing project or have imported -Web resources into a project .</p> -<p>To view or set Web project properties, -do the following: </p> - </div> - -<ol> -<li class="stepexpand"><span>Right-click on a Web Project, and from the pop-up menu select <span><span class="uicontrol">Properties</span></span>.</span> -</li> - -<li class="stepexpand"><span>Select a property type in the left pane of the Properties dialog -to view or update properties in the Web project. For each property, you can -apply changes and modify default settings. Based on whether you have a static -or a dynamic Web project, the following property types are available:</span> - <dl> -<dt class="dlterm">Info</dt> - -<dd>Provides general information about project type, location, and modification -status. </dd> - - -<dt class="dlterm">BeanInfo Path (Dynamic Web project only)</dt> - -<dd>If you select the Enable Beaninfo Introspection on this project, you can -specify the contents and order of Javaâ„¢ Bean search paths to provide Bean information -relevant to the project. You can add, remove, and reorder (using the <span>Up</span> and <span>Down</span> buttons) -the packages used to include Bean information.</dd> - - -<dt class="dlterm">Builders</dt> - -<dd>Add, remove, or reorder external tools in the build order. When you select <span class="uicontrol">New</span> to -create a new external tool to the list, the New External Tool wizard opens, -so that you can define the new build tool.</dd> - - -<dt class="dlterm">J2EE (Dynamic Web project only)</dt> - -<dd>Identify Web level specification and modify context root and Web content -folder name</dd> - - -<dt class="dlterm">Java Build -Path (Dynamic Web project only)</dt> - -<dd>View or change the information about the Java build path that you supplied when creating -the project using the <span>Create a DynamicWeb Project</span> wizard. Whenever -the Web project is rebuilt, any class files that are created or updated will -be output to the specified output folder. <div class="note"><span class="notetitle">Note:</span> A library entry on the Java build -path will remain there unless the actual JAR file is deleted from the WEB-INF/lib -folder. If you remove a library path entry but not the JAR file, the library -entry will be re-added to the path automatically.</div> -</dd> - - -<dt class="dlterm">Java Compiler -(Dynamic Web project only)</dt> - -<dd>Define whether to use workspace settings or project setting for compiling Java code, -including settings for Problems, Style, Compliance and Classfiles, and Build -Path.</dd> - - -<dt class="dlterm">Javadoc Location (Dynamic Web project only)</dt> - -<dd>Define a default location (URL) for any Javadoc available to the project.</dd> - - -<dt class="dlterm">Java JAR -Dependencies (Dynamic Web project only)</dt> - -<dd>Define and reorder JAR dependencies for the project. Note that these dependencies -may differ based on a Web project's association with multiple Enterprise application -projects.</dd> - - -<dt class="dlterm">JSP Task Tags</dt> - -<dd>Add, edit, or remove JSP task tags and assign tag priorities. These "to -do" items appear in your Tasks view.</dd> - - -<dt class="dlterm">JSP Compilation</dt> - -<dd>Specify when in the build process a JSP should be set to compile</dd> - - -<dt class="dlterm">JSP Fragment (dynamic Web project only)</dt> - -<dd>Define default encoding, page directive, and content type values for JSP -fragment documents in the web project.</dd> - - -<dt class="dlterm">Links Validation/Refactoring</dt> - -<dd>Define project-level link management and validation settings. These settings -override corresponding settings in the Workbench Preference settings for the -current project.</dd> - - -<dt class="dlterm">Project References</dt> - -<dd>Reference other Web projects that exist on your workbench workspace.</dd> - - -<dt class="dlterm">Server</dt> - -<dd>Select the server instance used to perform necessary development, test, -and publishing functions for the project.</dd> - - -<dt class="dlterm">Validation</dt> - -<dd>Specify which validators should run for the project, and whether validation -should occur automatically when resource updates are written to the project. -The available validators are based on the types of resources in your project. -By default, validators are automatically run when you save resources in a -Web project. If you do not want validators to run automatically when you save -these resources, enable the <span class="uicontrol">Override validation</span> preferences -option and disable the <span class="uicontrol">Run validation automatically when you save -changes to resources</span> option. <div class="note"><span class="notetitle">Note:</span> You can also disable automatic -validation (and builds) for all projects by disabling <span class="uicontrol">Perform build - automatically on resource modification</span> from the <span class="uicontrol">Workbench</span> properties. -If you disable automatic builds, you can manually run a build (and validation) -by selecting <span class="menucascade"><span class="uicontrol">Project</span> > <span class="uicontrol">Rebuild -project</span></span>.</div> -</dd> - - -<dt class="dlterm">Web Content Settings</dt> - -<dd>Provide any applicable Web content settings for a Web project. You can -specify the document type, CSS profile, and target device.</dd> - - -<dt class="dlterm">Web Project Features</dt> - -<dd>Select the features you want to be enabled for your Web project, such -as Page Template support.</dd> - -</dl> -</li> - -<li class="stepexpand"><span>When you have completed updates to Web project settings, click <span><span class="uicontrol">OK</span></span> to -save and close the Properties dialog.</span></li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.dita b/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.dita deleted file mode 100644 index ce1102b689..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.dita +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twsrvwiz" xml:lang="en-us">
-<title>Creating servlets</title>
-<shortdesc>The servlet wizard helps you create <tm tmclass="special" tmowner="Sun Microsystems, Inc."
-tmtype="tm" trademark="Java">Java</tm> servlets by walking you through the
-creation process and by providing you with output files that you can use or
-that you can modify for use with your Web application. The servlets can run
-on J2EE-compliant Web servers.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>servlets<indexterm>creating</indexterm></indexterm></keywords>
-</metadata></prolog>
-<taskbody>
-<context> <p>To create a servlet, complete the following steps: </p></context>
-<steps>
-<step><cmd>From the J2EE perspective, expand your <xref href="ccwebprj.dita"
-scope="peer"><desc></desc>dynamic project</xref> in the Project Explorer view.</cmd></step>
-<step><cmd>Right click on the <b>Servlet</b> icon, and select <menucascade>
-<uicontrol>New</uicontrol><uicontrol>Servlet</uicontrol></menucascade> from
-the pop-up menu.</cmd><stepresult> The <uicontrol>Create Servlet</uicontrol> wizard
-appears.</stepresult></step>
-<step><cmd>Follow the project wizard prompts.</cmd></step>
-</steps>
-<postreq><p><b>General Information</b></p><dl><dlentry>
-<dt>Modifiers</dt>
-<dd>You can select a modifier in the wizard to specify whether your servlet
-class is public, abstract, or final. Note that classes cannot be both abstract
-and final.</dd>
-</dlentry><dlentry>
-<dt>javax.servlet.Servlet</dt>
-<dd>Although javax.servlet.Servlet is provided as the default interface, you
-can use the wizard to add additional interfaces to implement.</dd>
-</dlentry><dlentry>
-<dt>Interface selection dialog</dt>
-<dd>This dialog appears if you elect to add an interface to your servlet.
-As you type the name of the interface that you are adding, a list of available
-interfaces listed in the Matching types list box updates dynamically to display
-only the interfaces that match the pattern. You should choose an interface
-to see the qualifier, and then click OK when finished.</dd>
-</dlentry><dlentry>
-<dt>Method stubs</dt>
-<dd>You can select any appropriate method stubs to be created in the servlet
-file. The stubs created by using the Inherited abstract methods option must
-be implemented if you do not intend to create an abstract servlet. Note that
-this is not true for Constructors from superclass</dd>
-</dlentry></dl></postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.html b/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.html deleted file mode 100644 index 6168cca467..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/topics/twsrvwiz.html +++ /dev/null @@ -1,87 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating servlets" /> -<meta name="abstract" content="The servlet wizard helps you create Java servlets by walking you through the creation process and by providing you with output files that you can use or that you can modify for use with your Web application. The servlets can run on J2EE-compliant Web servers." /> -<meta name="description" content="The servlet wizard helps you create Java servlets by walking you through the creation process and by providing you with output files that you can use or that you can modify for use with your Web application. The servlets can run on J2EE-compliant Web servers." /> -<meta content="servlets, creating" name="DC.subject" /> -<meta content="servlets, creating" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twsrvwiz" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating servlets</title> -</head> -<body id="twsrvwiz"><a name="twsrvwiz"><!-- --></a> - - -<h1 class="topictitle1">Creating servlets</h1> - - - -<div><p>The servlet wizard helps you create Javaâ„¢ servlets by walking you through the -creation process and by providing you with output files that you can use or -that you can modify for use with your Web application. The servlets can run -on J2EE-compliant Web servers.</p> - -<div class="section"> <p>To create a servlet, complete the following steps: </p> -</div> - -<ol> -<li class="stepexpand"><span>From the J2EE perspective, expand your <a href="ccwebprj.html" title="">dynamic project</a> in the Project Explorer view.</span></li> - -<li class="stepexpand"><span>Right click on the <strong>Servlet</strong> icon, and select <span class="menucascade"> -<span class="uicontrol">New</span> > <span class="uicontrol">Servlet</span></span> from -the pop-up menu.</span> The <span class="uicontrol">Create Servlet</span> wizard -appears.</li> - -<li class="stepexpand"><span>Follow the project wizard prompts.</span></li> - -</ol> - -<div class="section"><p><strong>General Information</strong></p> -<dl> -<dt class="dlterm">Modifiers</dt> - -<dd>You can select a modifier in the wizard to specify whether your servlet -class is public, abstract, or final. Note that classes cannot be both abstract -and final.</dd> - - -<dt class="dlterm">javax.servlet.Servlet</dt> - -<dd>Although javax.servlet.Servlet is provided as the default interface, you -can use the wizard to add additional interfaces to implement.</dd> - - -<dt class="dlterm">Interface selection dialog</dt> - -<dd>This dialog appears if you elect to add an interface to your servlet. -As you type the name of the interface that you are adding, a list of available -interfaces listed in the Matching types list box updates dynamically to display -only the interfaces that match the pattern. You should choose an interface -to see the qualifier, and then click OK when finished.</dd> - - -<dt class="dlterm">Method stubs</dt> - -<dd>You can select any appropriate method stubs to be created in the servlet -file. The stubs created by using the Inherited abstract methods option must -be implemented if you do not intend to create an abstract servlet. Note that -this is not true for Constructors from superclass</dd> - -</dl> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.ditamap b/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.ditamap deleted file mode 100644 index f1ed01c34e..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.ditamap +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN"
- "map.dtd">
-<map linking="none" title="Web application development">
-<topicmeta></topicmeta>
-<topicref href="topics/ccwtover.dita" navtitle="Web application overview">
-<topicref href="topics/cwtfeatures.dita" navtitle="Web tools features">
-<topicref href="topics/ccwebvw.dita" navtitle="Project Explorer view and Web development">
-</topicref>
-<topicref href="topics/cwebresources.dita" navtitle="Web resources"></topicref>
-<topicref href="topics/cwebpagedesign.dita" navtitle="Web page design"></topicref>
-</topicref>
-</topicref>
-<topicref href="topics/cwebprojects.dita" navtitle="Web projects">
-<topicref href="topics/cwwarovr.dita" navtitle="Web archive (WAR) files">
-</topicref>
-<topicref href="topics/twcreprj.dita" navtitle="Creating a dynamic Web project">
-<topicref href="topics/ccwebprj.dita" navtitle="Dynamic Web projects and applications">
-</topicref>
-</topicref>
-<topicref href="topics/twcresta.dita" navtitle="Creating a static Web project">
-<topicref href="topics/twpcnvrt.dita" navtitle="Converting static Web projects to dynamic Web projects">
-</topicref>
-<topicref href="topics/ccstatic.dita" navtitle="Static Web projects"></topicref>
-</topicref>
-<topicref href="topics/twimpwar.dita" navtitle="Importing Web archive (WAR) files">
-</topicref>
-<topicref href="topics/twcrewar.dita" navtitle="Exporting Web Archive (WAR) files">
-</topicref>
-<topicref href="topics/twplib.dita" navtitle="Adding Web library projects">
-</topicref>
-<topicref href="topics/twprjset.dita" navtitle="Setting Web project properties">
-</topicref>
-</topicref>
-<topicref href="topics/cwwedtvw.dita" navtitle="Workbench integration with Web editors">
-</topicref>
-<topicref href="topics/tjdetags.dita" navtitle="Creating and editing Web pages - overview">
-<topicref href="topics/tjcrehtm.dita" navtitle="Creating HTML and XHTML files and framesets">
-</topicref>
-<topicref href="topics/tjprefs.dita" navtitle="Defining HTML file preferences">
-</topicref>
-<topicref href="topics/tstylesheet.dita" navtitle="Creating cascading style sheets">
-</topicref>
-<topicref href="topics/twsrvwiz.dita" navtitle="Creating servlets">
-<topicref href="topics/cwservbn.dita" navtitle="Servlets"></topicref>
-</topicref>
-<topicref href="topics/tjcrejsp.dita" navtitle="Creating JavaServer Pages (JSP) files">
-<topicref href="topics/cpdjsps.dita" navtitle="JavaServer Pages (JSP) technology">
-</topicref>
-</topicref>
-</topicref>
-<topicref href="topics/twcvsr.dita" navtitle="Setting CVS repository defaults">
-</topicref>
-<topicref href="topics/tservertarget.dita" navtitle="Server targeting for Web applications">
-</topicref>
-</map>
diff --git a/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.xml b/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.xml deleted file mode 100644 index f274bd56de..0000000000 --- a/docs/org.eclipse.wst.webtools.doc.user/webtools_toc.xml +++ /dev/null @@ -1,41 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<?NLS TYPE="org.eclipse.help.toc"?> - -<toc label="Web application development" topic="topics/ccwtover.html"> -<topic label="Web application overview" href="topics/ccwtover.html"> -<topic label="Web tools features" href="topics/cwtfeatures.html"> -<topic label="Project Explorer view and Web development" href="topics/ccwebvw.html"/> -<topic label="Web resources" href="topics/cwebresources.html"/> -<topic label="Web page design" href="topics/cwebpagedesign.html"/> -</topic> -</topic> -<topic label="Web projects" href="topics/cwebprojects.html"> -<topic label="Web archive (WAR) files" href="topics/cwwarovr.html"/> -<topic label="Creating a dynamic Web project" href="topics/twcreprj.html"> -<topic label="Dynamic Web projects and applications" href="topics/ccwebprj.html"/> -</topic> -<topic label="Creating a static Web project" href="topics/twcresta.html"> -<topic label="Converting static Web projects to dynamic Web projects" href="topics/twpcnvrt.html"/> -<topic label="Static Web projects" href="topics/ccstatic.html"/> -</topic> -<topic label="Importing Web archive (WAR) files" href="topics/twimpwar.html"/> -<topic label="Exporting Web Archive (WAR) files" href="topics/twcrewar.html"/> -<topic label="Adding Web library projects" href="topics/twplib.html"/> -<topic label="Setting Web project properties" href="topics/twprjset.html"/> -</topic> -<topic label="Workbench integration with Web editors" href="topics/cwwedtvw.html"/> -<topic label="Creating and editing Web pages - overview" href="topics/tjdetags.html"> -<topic label="Creating HTML and XHTML files and framesets" href="topics/tjcrehtm.html"/> -<topic label="Defining HTML file preferences" href="topics/tjprefs.html"/> -<topic label="Creating cascading style sheets" href="topics/tstylesheet.html"/> -<topic label="Creating servlets" href="topics/twsrvwiz.html"> -<topic label="Servlets" href="topics/cwservbn.html"/> -</topic> -<topic label="Creating JavaServer Pages (JSP) files" href="topics/tjcrejsp.html"> -<topic label="JavaServer Pages (JSP) technology" href="topics/cpdjsps.html"/> -</topic> -</topic> -<topic label="Setting CVS repository defaults" href="topics/twcvsr.html"/> -<topic label="Server targeting for Web applications" href="topics/tservertarget.html"/> -</toc> diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.cvsignore b/docs/org.eclipse.wst.xml.ui.infopop/.cvsignore deleted file mode 100644 index c14487ceac..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/.cvsignore +++ /dev/null @@ -1 +0,0 @@ -build.xml diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.project b/docs/org.eclipse.wst.xml.ui.infopop/.project deleted file mode 100644 index 110ff69a25..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.xml.ui.infopop</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts.xml b/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts.xml deleted file mode 100644 index 364fca98f5..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts.xml +++ /dev/null @@ -1,143 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> -<context id="csh_outer_container"> -<description/> -</context> -<context id="webx0060"> -<description>This page lets you specify the line delimiter and the text encoding that will be used when you create or save an XML related file. - -Various development platforms use different line delimiters to indicate the start of a new line. Select the operating system that corresponds to your development or deployment platform. - -<b>Note:</b> This delimiter will not automatically be added to any documents that currently exist. It will be added only to documents that you create after you select the line delimiter type and click <b>Apply</b>, or to existing files that you open and then resave after you select the line delimiter type and click <b>Apply</b>. - -The encoding attribute is used to specify the default character encoding set that is used when creating XML related files (DTDs, XML files, XML schemas). Changing the encoding causes any new, XML related files that are created from scratch to use the selected encoding.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html" label="Specifying XML default encoding and line delimiters"/> -</context> -<context id="webx0061"> -<description>This page lets you specify the formatting and content assist preferences that will be used when editing an XML file. - -Enter a maximum width in the <b>Line width</b> field to specify when a line should be broken to fit onto more than one line. This will be applied when the document is formatted. - -Select <b>Split multiple attributes each on a new line</b> to start every attribute on a new line when the document is formatted. - -Select <b>Clear all blank lines</b> to remove blank lines when the document is formatted. - -Select <b>Indent using tabs</b> if you want to use tab characters (\t) as the standard formatting indentation. - -If you prefer to use spaces, select <b>Indent using spaces</b>. - -You can also specify the <b>Indentation size</b> which is the number of tabs or space characters used for formatting indentation. - -To apply these formatting styles, right-click in your XML document, and click <b>Format > Document</b>. - -If the <b>Automatically make suggestions</b> check box is selected, you can specify that certain characters will cause the content assist list to pop up automatically. Specify these characters in the <b>Prompt when these characters are inserted</b> field. - -If you select <b>Strict</b> from the <b>Suggestion strategy</b> list, suggestions that are grammatically valid will be shown first (with bold icons) in the content assist list. Other suggestions that are applicable to the element scope, but not grammatically valid, will be shown below them with a de-emphasized icon. The default value for this field is <b>Lax</b>. - -If a DTD or schema (or other model) is not specified for an XML file, selecting <b>Use inferred grammar in absence of DTD/Schema</b> allows the editor to "guess" what elements or attributes are available based on existing content.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html" label="Defining XML editor preferences"/> -</context> -<context id="webx0062"> -<description>This page lets you customize the syntax highlighting that the XML editor does when you are editing a file. - -The <b>Content type</b> field contains a list of all the source types that you can select a highlighting style for. You can either select the content type that you want to work with from the drop-down list, or click text in the text sample window that corresponds to the content type for which you want to change the text highlighting. - -The <b>Foreground</b> and <b>Background</b> buttons open <b>Color</b> dialog boxes that allow you to specify text foreground and background colors, respectively. Select the <b>Bold</b> check box to make the specified content type appear in bold. - -Click the <b>Restore Defaults</b> button to set the highlighting styles back to their default values. If you only want to reset the value for a particular content type, select it in the <b>Content type</b> field, the click the <b>Restore Default</b> button next to it.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html" label="Setting source highlighting styles"/> -</context> -<context id="webx0063"> -<description>This page lets you create new templates and edit existing ones that can be used when editing an XML file. A template is a chunk of predefined code that you can insert into a file. - -Click <b>New</b> if you want to create a completely new template. - -Supply a new template <b>Name</b> and <b>Description</b>. The <b>Context</b> for the template is the context in which the template is available in the proposal list when content assist is requested. Specify the <b>Pattern</b> for your template using the appropriate tags, attributes, or attribute values to be inserted by content assist. - -If you want to insert a variable, click the <b>Insert Variable</b> button and select the variable to be inserted. For example, the <b>date</b> variable indicates the current date will be inserted. - -You can edit, remove, import, or export a template by using the same Preferences page. If you have modified a default template, you can restore it to its default value. You can also restore a removed template if you have not exited from the workbench since it was removed. - -If you have a template that you do not want to remove but you no longer want it to appear in the content assist list, clear its check box in the <b>Templates</b> preferences page.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html" label="Working with XML templates"/> -</context> -<context id="xmlm1200"> -<description>Cleanup options enable you to update a document so that it is well-formed and consistently formatted. - -The following cleanup options can be set to on or off, so that you can limit the type of cleanup performed: - -- <b>Compress empty element tags</b>: Compress element tags with no content to one tag with an end tag delimiter (ie: change <tag></tag> to <tag/>). - -- <b>Insert required attributes</b>: Inserts any missing attributes that are required by the tag to make the element or document well-formed. - -- <b>Insert missing tags</b>: Completes any missing tags (such as adding an end tag) necessary to make the element or document well-formed. - -- <b>Quote attribute values</b>: Appropriately adds double- or single-quotes before and after attribute values if they are missing. - -- <b>Format source</b>: Formats the document just as the <b>Format Document</b> context menu option does, immediately after performing any other specified <b>Cleanup</b> options. - -- <b>Convert line delimiters to</b>: Converts all line delimiters in the file to the selected operating system's type.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html" label="Editing in the Source view"/> -</context> -<context id="xcui0500"> -<description>Enter the name of the attribute in the <b>Name</b> field, then enter the value of the attribute in the <b>Value</b> field. Click <b>OK</b>. The attribute will be added to the file.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -</context> -<context id="xcui0010"> -<description>The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can use the <b>Public ID</b> field to create an association using an XML Catalog entry or the <b>System ID</b> field to create an association using a file in the workbench.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html" label="Editing DOCTYPE declarations"/> -</context> -<context id="xcui0020"> -<description>This should match the name of your XML file's root element.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html" label="Editing DOCTYPE declarations"/> -</context> -<context id="xcui0030"> -<description>The value in this field is the Public Identifier. It is used to associate the XML file (using an XML catalog entry) with a DTD file by providing a hint to the XML processor.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html" label="Editing DOCTYPE declarations"/> -</context> -<context id="xcui0050"> -<description>The value in this field is the DTD the XML file is associated with. You can change the DTD the file is associated with by editing this field. The XML processor will try to use the Public ID to locate the DTD, and if this fails, it will use the System ID to find it.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html" label="Editing DOCTYPE declarations"/> -</context> -<context id="xcui0600"> -<description>Enter the name of the element in the <b>Element name</b> field, then click <b>OK</b>. The element will be added to the file.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -</context> -<context id="xcui0300"> -<description>A processing instruction is a syntax in XML for passing instructions along to the application using an XML document. The <b>Target</b> field is used to identify the application the instructions belongs to. The <b>Data</b> field contains the instructions.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html" label="Editing XML processing instructions"/> -</context> -<context id="xcui0100"> -<description>This is a read-only dialog. Select the entry you want to edit and click <b>Edit</b>.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing your namespace information"/> -</context> -<context id="xcui0200"> -<description>The value in the <b>Namespace Name</b> field is the namespace the XML file belongs to. - -All qualified elements and attributes in the XML file associated with the namespace will be prefixed with the <b>Prefix</b> value. - -The <b>Location Hint</b> field contains the location of the XML schema the XML file is associated with. An XML Catalog ID or a URI can be specified in this field. You can search for the schema you want to use by clicking <b>Browse</b>. Once you select a file, the <b>Namespace Name</b> and <b>Prefix</b> fields will automatically be filled with the appropriate values from the schema (you must leave the fields blank for this to occur). <b>Note</b>: If you are creating an XML file from an XML schema, you cannot change the <b>Namespace Name</b> or <b>Location Hint</b> values.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing your namespace information"/> -</context> -<context id="xcui0400"> -<description>An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a URI (which contains information about a DTD or XML schema's location). Select the catalog entry you want to associate your XML file with.</description> -</context> -</contexts> diff --git a/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts2.xml b/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts2.xml deleted file mode 100644 index 60ebab5cfb..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/EditorXmlContexts2.xml +++ /dev/null @@ -1,21 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<contexts> -<context id="csh_outer_container"> -<description/> -</context> -<context id="xml_source_HelpId"> -<description>The XML source view lets you edit a file that is coded in the Extensible Markup Language. The editor provides many text editing features, such as content assist, user-defined templates, syntax highlighting, unlimited undo and redo, element selection and formatting, and document formatting.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html" label="Editing in the Source view"/> -</context> -</contexts>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xml.ui.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.xml.ui.infopop/META-INF/MANIFEST.MF deleted file mode 100644 index df3c14e894..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/META-INF/MANIFEST.MF +++ /dev/null @@ -1,7 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.wst.xml.ui.infopop; singleton:=true -Bundle-Version: 1.0.2.qualifier -Bundle-Vendor: %pluginProvider -Bundle-Localization: plugin diff --git a/docs/org.eclipse.wst.xml.ui.infopop/TableTree.xml b/docs/org.eclipse.wst.xml.ui.infopop/TableTree.xml deleted file mode 100644 index 263c6e1396..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/TableTree.xml +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<contexts> -<context id="csh_outer_container"> -<description/> -</context> -<context id="xmlm3000"> -<description>The Design view of the XML editor represents your file simultaneously as a table and a tree, which helps make navigation and editing easier. Depending on the kind of file you are working with, content and attribute values can be edited directly in table cells, while pop-up menus on tree elements give alternatives that are valid for that location.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html" label="Editing in the Design view"/> -</context> -</contexts>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xml.ui.infopop/XMLWizardContexts.xml b/docs/org.eclipse.wst.xml.ui.infopop/XMLWizardContexts.xml deleted file mode 100644 index 4e781c58f0..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/XMLWizardContexts.xml +++ /dev/null @@ -1,78 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS type="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<contexts> -<context id="csh_outer_container"> -<description/> -</context> -<context id="xmlc0101"> -<description>Select the <b>Create XML file from a DTD file</b> radio button to create an XML file from a DTD file. The file will contain the selected root element, populated with any required elements and attributes.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/> -</context> -<context id="xmlc0102"> -<description>Select the <b>Create XML file from an XML schema file</b> radio button to create an XML file from an XML schema. The file will contain the selected root element of the XML schema and any elements or attributes it contains.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/> -</context> -<context id="xmlc0103"> -<description>Select the <b>Create XML file from scratch</b> radio button if you want to create an XML file not associated with any XML schema or DTD file.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html" label="Creating empty XML files"/> -</context> -<context id="xmlc0500"> -<description>Select the <b>Select file from workbench</b> radio button if you want to create your XML file from a DTD or XML schema that is in the workbench. - -Select the <b>Select XML Catalog entry</b> radio button if you want to use a file listed in the XML Catalog to create your XML file.</description> -</context> -<context id="xmlc0410"> -<description>The root element of an XML file is the element that contains all other elements in that file. All elements defined in the DTD or all global elements defined in the XML schema are included in this list. - -<b>Note</b>: If you do not have any elements in your DTD or any global elements in your XML schema, you cannot create an XML file from it.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/> -</context> -<context id="xmlc0441"> -<description>If you select this check box, both mandatory and optional attributes will be generated. If you do not select it, only mandatory attributes will be generated.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/> -</context> -<context id="xmlc0442"> -<description>If you select this check box, both the mandatory and optional elements will be generated. If you do not select it, only mandatory elements will be generated.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/> -</context> -<context id="xmlc0443"> -<description>If you select this check box, the first choice of a required choice will be generated in your XML file. - -For example, if you have the following code in your source file: - -<b><choice> <element name="a" type="string> <element name="b" type="integer> </choice></b> - -and you select this check box, an element such as the following will be created in your XML file: - -<b><a>hello</a></b> </description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/> -</context> -<context id="xmlc0444"> -<description>If you select this check box, any elements and attributes generated will be filled with sample data, such as <b><text>EmptyText</text>.</b> Otherwise, they will be empty - that is, <b><text></text>.</b> </description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html" label="Generating XML files from XML schemas"/> -</context> -<context id="xmlc0210"> -<description>The System ID value corresponds to the URI (physical location) of the DTD file. The Public ID value can refer to a DTD entry in an XML Catalog.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/> -</context> -<context id="xmlc0220"> -<description>The System ID value corresponds to the URI (physical location) of the DTD file. The Public ID value can refer to a DTD entry in an XML Catalog.</description> -<topic href="../org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html" label="Generating XML files from DTDs"/> -</context> -</contexts>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xml.ui.infopop/about.html b/docs/org.eclipse.wst.xml.ui.infopop/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.xml.ui.infopop/build.properties b/docs/org.eclipse.wst.xml.ui.infopop/build.properties deleted file mode 100644 index 29a969bc9f..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/build.properties +++ /dev/null @@ -1,8 +0,0 @@ -bin.includes = META-INF/,\ - EditorXmlContexts.xml,\ - EditorXmlContexts2.xml,\ - about.html,\ - plugin.properties,\ - plugin.xml -src.includes = XMLWizardContexts.xml,\ - TableTree.xml diff --git a/docs/org.eclipse.wst.xml.ui.infopop/plugin.properties b/docs/org.eclipse.wst.xml.ui.infopop/plugin.properties deleted file mode 100644 index 8725f94824..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/plugin.properties +++ /dev/null @@ -1,13 +0,0 @@ -############################################################################### -# Copyright (c) 2006 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### - -pluginName = XML infopops -pluginProvider = Eclipse.org diff --git a/docs/org.eclipse.wst.xml.ui.infopop/plugin.xml b/docs/org.eclipse.wst.xml.ui.infopop/plugin.xml deleted file mode 100644 index 2287c849d6..0000000000 --- a/docs/org.eclipse.wst.xml.ui.infopop/plugin.xml +++ /dev/null @@ -1,24 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.1"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - -<extension point="org.eclipse.help.contexts"> - <contexts file="EditorXmlContexts.xml" plugin ="org.eclipse.wst.xml.ui"/> - <contexts file="EditorXmlContexts2.xml" plugin ="org.eclipse.core.runtime"/> - <contexts file="TableTree.xml" plugin ="org.eclipse.wst.xml.ui"/> - <contexts file="XMLWizardContexts.xml" plugin ="org.eclipse.wst.xml.ui"/> - -</extension> - - -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.cvsignore b/docs/org.eclipse.wst.xmleditor.doc.user/.cvsignore deleted file mode 100644 index b53298e136..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/.cvsignore +++ /dev/null @@ -1,5 +0,0 @@ -build.xml -org.eclipse.wst.xmleditor.doc.user_1.0.0.jar -bak -temp -DitaLink.cat
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.project b/docs/org.eclipse.wst.xmleditor.doc.user/.project deleted file mode 100644 index 2e33af6b20..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.xmleditor.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/DocBuild.xml b/docs/org.eclipse.wst.xmleditor.doc.user/DocBuild.xml deleted file mode 100644 index 380e99e1be..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/DocBuild.xml +++ /dev/null @@ -1,59 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<!-- - - This script build the Help plug-in by transforming the DITA source files into HTML. - - To use this script, you must install DITA-OT on your machine in the directory - defined by the dita.ot.dir property. - - Run the default target after you edit the DITA source files to regenerate the HTML. - - To customize this script for other Help plug-ins, modify the value of the args.input property - to be the DITA map file for the plug-in. - - NOTE: This script assumes that links to sibling Help plug-ins have scope="peer", otherwise the - output directory structure will be shifted incorrectly. - - NOTE: This script assumes that you hand code your plugin.xml file in myplugin.xml. This file - will be copied over the generated plugin.xml which is currently not being generated correctly - by DITA-OT. - - ChangeLog: - 2006-04-05 Arthur Ryman <ryman@ca.ibm.com> - - Created. - ---> -<project name="eclipsehelp" default="all"> - - <property name="dita.ot.dir" location="C:/DITA-OT1.2.2" /> - - <path id="dost.class.path"> - <pathelement location="${dita.ot.dir}${file.separator}lib${file.separator}dost.jar" /> - </path> - - <taskdef name="integrate" classname="org.dita.dost.platform.IntegratorTask"> - <classpath refid="dost.class.path" /> - </taskdef> - <target name="all" depends="integrate, eclipsehelp"> - </target> - <target name="integrate"> - <integrate ditadir="${dita.ot.dir}" /> - </target> - - <!-- revise below here --> - <target name="eclipsehelp"> - <ant antfile="${dita.ot.dir}${file.separator}conductor.xml" target="init" dir="${dita.ot.dir}"> - <property name="args.copycss" value="no" /> - <property name="args.csspath" value="org.eclipse.wst.doc.user" /> - <property name="args.eclipse.provider" value="Eclipse.org" /> - <property name="args.eclipse.version" value="1.5.0" /> - <property name="args.input" location="XMLBuilderrel.ditamap" /> - <property name="clean.temp" value="true" /> - <property name="dita.extname" value=".dita" /> - <property name="dita.temp.dir" location="temp" /> - <property name="output.dir" location=".." /> - <property name="transtype" value="eclipsehelp" /> - </ant> - <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" /> - </target> -</project> diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.xmleditor.doc.user/META-INF/MANIFEST.MF deleted file mode 100644 index 96e38c0a7c..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,8 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.wst.xmleditor.doc.user; singleton:=true -Bundle-Version: 1.0.300.qualifier -Bundle-Vendor: %pluginProvider -Bundle-Localization: plugin -Bundle-RequiredExecutionEnvironment: J2SE-1.4 diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.ditamap b/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.ditamap deleted file mode 100644 index 09ea42a36d..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.ditamap +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
-<map collection-type="sequence" title="Developing XML files">
-<topicref href="topics/cworkXML.dita" linking="sourceonly" navtitle="Working with XML files"><?Pub Caret1?>
-<topicref href="topics/ccreatxm.dita" navtitle="Creating XML files">
-<topicref href="topics/tcretxml.dita" id="xmlcretxml" navtitle="Creating empty XML files">
-</topicref>
-<topicref href="topics/tcrexdtd.dita" navtitle="Generating XML files from DTDs">
-</topicref>
-<topicref href="topics/tcrexxsd.dita" navtitle="Generating XML files from XML schemas">
-</topicref>
-</topicref>
-<topicref href="topics/rlimitations_slushXML.dita" navtitle="Limitations of XML Editor"
-toc="no"></topicref>
-<topicref href="topics/txedttag.dita" navtitle="Editing XML files">
-<topicref href="topics/cwxmledt.dita" navtitle="XML editor">
-<topicref href="topics/txprefs.dita" navtitle="Defining XML editor preferences">
-<topicref href="topics/ttaghilt.dita" id="taghilt" navtitle="Setting source highlighting styles">
-</topicref>
-<topicref href="topics/tedtenc.dita" navtitle="Specifying XML default encoding line delimiters">
-<topicref href="topics/cxmlenc.dita" navtitle="XML and HTML encodings"></topicref>
-</topicref>
-<topicref href="topics/tsugstrat.dita" navtitle="Setting the XML source suggestion strategy used by content assist">
-</topicref>
-</topicref>
-</topicref>
-<topicref href="topics/txedtdes.dita" id="txedtdes" linking="none" navtitle="Editing in the Design view">
-<topicref href="topics/tedtdoc.dita" id="tedtdoc" navtitle="Editing DOCTYPE declarations">
-</topicref>
-<topicref href="topics/tedtsch.dita" id="tedtsch" navtitle="Editing namespace information">
-</topicref>
-<topicref href="topics/tedtproc.dita" id="tedtproc" navtitle="Editing XML processing instructions">
-</topicref>
-</topicref>
-<topicref href="topics/txedtsrc.dita" id="txedsrc" linking="none" navtitle="Editing in the Source view">
-<topicref href="topics/twcdast.dita" navtitle="Using XML content assist">
-</topicref>
-<topicref href="topics/twmacro.dita" id="twmacro" navtitle="Working with XML templates">
-</topicref>
-</topicref>
-<topicref href="topics/tedtcnst.dita" id="tedtcnt" navtitle="Editing with DTD or XML schema constraints">
-</topicref>
-<topicref href="topics/txsityp.dita" navtitle="Using xsi:type"></topicref>
-<topicref href="topics/rextctn.dita" id="rextctn" navtitle="Editing XML documents with multiple namespaces">
-</topicref>
-</topicref>
-<topicref href="topics/twxvalid.dita" id="xmlvalid" navtitle="Validating XML files">
-</topicref>
-<topicref href="topics/cxmlcat.dita" linking="none" navtitle="XML file associations with DTDs and XML schemas">
-<topicref href="topics/txmlcat.dita" id="txmlcat" navtitle="Adding entries to the XML Catalog">
-</topicref>
-<topicref href="topics/tedtgram.dita" id="tedtgram" navtitle="Updating XML files with changes made to DTDs and schemas">
-</topicref>
-</topicref>
-<topicref href="topics/rxmlbicons.dita" id="ricons" navtitle="Icons used in the XML editor">
-</topicref>
-</topicref>
-</map>
-<?Pub *0000003143?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml b/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml deleted file mode 100644 index 94554d572e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuildermap_toc.xml +++ /dev/null @@ -1,42 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<?NLS TYPE="org.eclipse.help.toc"?> - -<toc label="Developing XML files" topic="topics/cworkXML.html"> -<topic label="Working with XML files" href="topics/cworkXML.html"> -<topic label="Creating XML files" href="topics/ccreatxm.html"> -<topic label="Creating XML files" href="topics/tcretxml.html"/> -<topic label="Generating XML files from DTDs" href="topics/tcrexdtd.html"/> -<topic label="Generating XML files from XML schemas" href="topics/tcrexxsd.html"/> -</topic> -<topic label="Editing XML files" href="topics/txedttag.html"> -<topic label="XML editor" href="topics/cwxmledt.html"> -<topic label="Defining XML editor preferences" href="topics/txprefs.html"> -<topic label="Setting source highlighting styles" href="topics/ttaghilt.html"/> -<topic label="Specifying XML default encoding line delimiters" href="topics/tedtenc.html"> -<topic label="XML and HTML encodings" href="topics/cxmlenc.html"/> -</topic> -<topic label="Setting the XML source suggestion strategy used by content assist" href="topics/tsugstrat.html"/> -</topic> -</topic> -<topic label="Editing in the Design view" href="topics/txedtdes.html"> -<topic label="Editing DOCTYPE declarations" href="topics/tedtdoc.html"/> -<topic label="Editing namespace information" href="topics/tedtsch.html"/> -<topic label="Editing XML processing instructions" href="topics/tedtproc.html"/> -</topic> -<topic label="Editing in the Source view" href="topics/txedtsrc.html"> -<topic label="Using XML content assist" href="topics/twcdast.html"/> -<topic label="Working with XML templates" href="topics/twmacro.html"/> -</topic> -<topic label="Editing with DTD or XML schema constraints" href="topics/tedtcnst.html"/> -<topic label="Using xsi:type" href="topics/txsityp.html"/> -<topic label="Editing XML documents with multiple namespaces" href="topics/rextctn.html"/> -</topic> -<topic label="Validating XML files" href="topics/twxvalid.html"/> -<topic label="XML file associations with DTDs and XML schemas" href="topics/cxmlcat.html"> -<topic label="Adding entries to the XML Catalog" href="topics/txmlcat.html"/> -<topic label="Updating XML files with changes made to DTDs and schemas" href="topics/tedtgram.html"/> -</topic> -<topic label="Icons used in the XML editor" href="topics/rxmlbicons.html"/> -</topic> -</toc> diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuilderrel.ditamap b/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuilderrel.ditamap deleted file mode 100644 index 74ddb7c64e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuilderrel.ditamap +++ /dev/null @@ -1,136 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
-<map>
-<topicgroup collection-type="family"><?Pub Caret1?>
-<topicref href="topics/tcretxml.dita" id="xmlcretxml" navtitle="Creating empty XML files">
-</topicref>
-<topicref href="topics/tcrexdtd.dita" navtitle="Generating XML files from DTDs">
-</topicref>
-<topicref href="topics/tcrexxsd.dita" navtitle="Generating XML files from XML schemas">
-</topicref>
-<topicref href="topics/txedttag.dita" linking="targetonly" navtitle="Editing XML files">
-</topicref>
-<topicref href="topics/cwxmledt.dita" navtitle="XML editor"></topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/txedttag.dita" linking="sourceonly" navtitle="Editing XML files">
-</topicref>
-<topicref href="topics/cwxmledt.dita" linking="targetonly" navtitle="XML editor">
-</topicref>
-<topicref href="topics/txedtdes.dita" linking="targetonly" navtitle="Editing in the Design view">
-</topicref>
-<topicref href="topics/txedtsrc.dita" linking="targetonly" navtitle="Editing in the Source view">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/cxmlcat.dita" navtitle="XML file associations with DTDs and XML schemas">
-</topicref>
-<topicref href="topics/tedtcnst.dita" navtitle="Editing with DTD or XML schema constraints">
-</topicref>
-<topicref href="topics/tedtdoc.dita" navtitle="Editing DOCTYPE declarations">
-</topicref>
-<topicref href="topics/txmlcat.dita" id="txmlcat" navtitle="Adding entries to the XML Catalog">
-</topicref>
-<topicref href="topics/tedtgram.dita" id="tedtgram" navtitle="Updating XML files with changes made to DTDs and schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/cxmlcat.dita" navtitle="XML file associations with DTDs and XML schemas">
-</topicref>
-<topicref href="topics/tedtcnst.dita" navtitle="Editing with DTD or XML schema constraints">
-</topicref>
-<topicref href="topics/tedtsch.dita" navtitle="Editing namespace information">
-</topicref>
-<topicref href="topics/txmlcat.dita" navtitle="Adding entries to the XML Catalog">
-</topicref>
-<topicref href="topics/tedtgram.dita" navtitle="Updating XML files with changes made to DTDs and schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family" linking="normal">
-<topicref href="topics/tedtproc.dita" id="tedtproc" linking="targetonly" navtitle="Editing XML processing instructions">
-</topicref>
-<topicref href="topics/cxmlcat.dita" navtitle="XML file associations with DTDs and XML schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family" linking="normal">
-<topicref href="topics/cwxmledt.dita" navtitle="XML editor"></topicref>
-<topicref href="topics/txedtdes.dita" navtitle="Editing in the Design view">
-</topicref>
-<topicref href="topics/txedtsrc.dita" navtitle="Editing in the Source view">
-</topicref>
-<topicref href="topics/cxmlcat.dita" navtitle="XML file associations with DTDs and XML schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family" linking="normal">
-<topicref href="topics/twxvalid.dita" navtitle="Validating XML files"></topicref>
-<topicref href="topics/cwxmledt.dita" navtitle="XML editor"></topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/tcrexxsd.dita" navtitle="Generating XML files from XML schemas">
-</topicref>
-<topicref href="../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.dita"
-linking="targetonly" navtitle="XML namespaces" scope="peer"></topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/tedtsch.dita" navtitle="Editing namespace information">
-</topicref>
-<topicref href="../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.dita"
-linking="targetonly" navtitle="XML namespaces" scope="peer"></topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/txedtsrc.dita" id="txedsrc" navtitle="Editing in the Source view">
-</topicref>
-<topicref href="topics/twcdast.dita" navtitle="Using XML content assist">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/txedtsrc.dita" navtitle="Editing in the Source view">
-</topicref>
-<topicref href="topics/twmacro.dita" navtitle="Working with XML templates">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/txedtsrc.dita" navtitle="Editing in the Source view">
-</topicref>
-<topicref href="topics/ttaghilt.dita" navtitle="Setting source highlighting styles">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/twcdast.dita" navtitle="Using XML content assist">
-</topicref>
-<topicref href="topics/twmacro.dita" navtitle="Working with XML templates">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/twcdast.dita" navtitle="Using XML content assist">
-</topicref>
-<topicref href="topics/tsugstrat.dita" navtitle="XML source suggestion strategy">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/txedtdes.dita" navtitle="Editing in the Design view">
-</topicref>
-<topicref href="topics/tedtdoc.dita" navtitle="Editing DOCTYPE declarations">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/txedtdes.dita" navtitle="Editing in the Design view">
-</topicref>
-<topicref href="topics/tedtsch.dita" navtitle="Editing namespace information">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/txedtdes.dita" navtitle="Editing in the Design view">
-</topicref>
-<topicref href="topics/tedtproc.dita" navtitle="Editing XML processing instructions">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/txedtdes.dita" navtitle="Editing in the Design view">
-</topicref>
-<topicref href="topics/rxmlbicons.dita" navtitle="Icons used in the XML editor">
-</topicref>
-</topicgroup>
-</map>
-<?Pub *0000006002?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuilderrel.xml b/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuilderrel.xml deleted file mode 100644 index 400ab50c42..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/XMLBuilderrel.xml +++ /dev/null @@ -1,55 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<?NLS TYPE="org.eclipse.help.toc"?> - -<toc topic="topics/tcretxml.html"> -<topic label="Creating XML files" href="topics/tcretxml.html"/> -<topic label="Generating XML files from DTDs" href="topics/tcrexdtd.html"/> -<topic label="Generating XML files from XML schemas" href="topics/tcrexxsd.html"/> -<topic label="Editing XML files" href="topics/txedttag.html"/> -<topic label="XML editor" href="topics/cwxmledt.html"/> -<topic label="Editing XML files" href="topics/txedttag.html"/> -<topic label="XML editor" href="topics/cwxmledt.html"/> -<topic label="Editing in the Design view" href="topics/txedtdes.html"/> -<topic label="Editing in the Source view" href="topics/txedtsrc.html"/> -<topic label="XML file associations with DTDs and XML schemas" href="topics/cxmlcat.html"/> -<topic label="Editing with DTD or XML schema constraints" href="topics/tedtcnst.html"/> -<topic label="Editing DOCTYPE declarations" href="topics/tedtdoc.html"/> -<topic label="Adding entries to the XML Catalog" href="topics/txmlcat.html"/> -<topic label="Updating XML files with changes made to DTDs and schemas" href="topics/tedtgram.html"/> -<topic label="XML file associations with DTDs and XML schemas" href="topics/cxmlcat.html"/> -<topic label="Editing with DTD or XML schema constraints" href="topics/tedtcnst.html"/> -<topic label="Editing namespace information" href="topics/tedtsch.html"/> -<topic label="Adding entries to the XML Catalog" href="topics/txmlcat.html"/> -<topic label="Updating XML files with changes made to DTDs and schemas" href="topics/tedtgram.html"/> -<topic label="Editing XML processing instructions" href="topics/tedtproc.html"/> -<topic label="XML file associations with DTDs and XML schemas" href="topics/cxmlcat.html"/> -<topic label="XML editor" href="topics/cwxmledt.html"/> -<topic label="Editing in the Design view" href="topics/txedtdes.html"/> -<topic label="Editing in the Source view" href="topics/txedtsrc.html"/> -<topic label="XML file associations with DTDs and XML schemas" href="topics/cxmlcat.html"/> -<topic label="Validating XML files" href="topics/twxvalid.html"/> -<topic label="XML editor" href="topics/cwxmledt.html"/> -<topic label="Generating XML files from XML schemas" href="topics/tcrexxsd.html"/> -<topic label="XML namespaces" href="../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html"/> -<topic label="Editing namespace information" href="topics/tedtsch.html"/> -<topic label="XML namespaces" href="../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html"/> -<topic label="Editing in the Source view" href="topics/txedtsrc.html"/> -<topic label="Using XML content assist" href="topics/twcdast.html"/> -<topic label="Editing in the Source view" href="topics/txedtsrc.html"/> -<topic label="Working with XML templates" href="topics/twmacro.html"/> -<topic label="Editing in the Source view" href="topics/txedtsrc.html"/> -<topic label="Setting source highlighting styles" href="topics/ttaghilt.html"/> -<topic label="Using XML content assist" href="topics/twcdast.html"/> -<topic label="Working with XML templates" href="topics/twmacro.html"/> -<topic label="Using XML content assist" href="topics/twcdast.html"/> -<topic label="Setting the XML source suggestion strategy used by content assist" href="topics/tsugstrat.html"/> -<topic label="Editing in the Design view" href="topics/txedtdes.html"/> -<topic label="Editing DOCTYPE declarations" href="topics/tedtdoc.html"/> -<topic label="Editing in the Design view" href="topics/txedtdes.html"/> -<topic label="Editing namespace information" href="topics/tedtsch.html"/> -<topic label="Editing in the Design view" href="topics/txedtdes.html"/> -<topic label="Editing XML processing instructions" href="topics/tedtproc.html"/> -<topic label="Editing in the Design view" href="topics/txedtdes.html"/> -<topic label="Icons used in the XML editor" href="topics/rxmlbicons.html"/> -</toc> diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/about.html b/docs/org.eclipse.wst.xmleditor.doc.user/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/build.properties b/docs/org.eclipse.wst.xmleditor.doc.user/build.properties deleted file mode 100644 index 9f51d547dc..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/build.properties +++ /dev/null @@ -1,15 +0,0 @@ -bin.includes = XMLBuildermap_toc.xml,\ - about.html,\ - images/,\ - org.eclipse.wst.xmleditor.doc.userindex.xml,\ - plugin.xml,\ - topics/*.htm*,\ - index/,\ - META-INF/,\ - plugin.properties -src.includes = build.properties,\ - *.maplist,\ - *.ditamap,\ - topics/*.dita -bin.excludes = DocBuild.xml,\ - myPlugin*.xml
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/cdatasection.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/cdatasection.gif Binary files differdeleted file mode 100644 index 6b0872c909..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/cdatasection.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/collapse_all.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/collapse_all.gif Binary files differdeleted file mode 100644 index 7dc0de5130..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/collapse_all.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/comment_obj.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/comment_obj.gif Binary files differdeleted file mode 100644 index 28c2ccb1e7..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/comment_obj.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/doctype.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/doctype.gif Binary files differdeleted file mode 100644 index 3300f82862..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/doctype.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/expand_all.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/expand_all.gif Binary files differdeleted file mode 100644 index 492c14f6e1..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/expand_all.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/nattrib.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/nattrib.gif Binary files differdeleted file mode 100644 index bea9974e0b..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/nattrib.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/nelem.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/nelem.gif Binary files differdeleted file mode 100644 index afabddad89..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/nelem.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/nrstrval.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/nrstrval.gif Binary files differdeleted file mode 100644 index 4742b8cd96..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/nrstrval.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/proinst_obj.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/proinst_obj.gif Binary files differdeleted file mode 100644 index 74436d8d3c..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/proinst_obj.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/rldgrmr.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/rldgrmr.gif Binary files differdeleted file mode 100644 index 049cac696c..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/rldgrmr.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/images/suggestion.gif b/docs/org.eclipse.wst.xmleditor.doc.user/images/suggestion.gif Binary files differdeleted file mode 100644 index b4ea849dab..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/images/suggestion.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/index/_u.cfs b/docs/org.eclipse.wst.xmleditor.doc.user/index/_u.cfs Binary files differdeleted file mode 100644 index 795be84c02..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/index/_u.cfs +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/index/deletable b/docs/org.eclipse.wst.xmleditor.doc.user/index/deletable Binary files differdeleted file mode 100644 index e423242b3e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/index/deletable +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_contributions b/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_contributions deleted file mode 100644 index 66ea04d48b..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_contributions +++ /dev/null @@ -1,3 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:16:15 EDT 2007
-org.eclipse.wst.xmleditor.doc.user=org.eclipse.wst.xmleditor.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_dependencies b/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_dependencies deleted file mode 100644 index 5d57cada9f..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_dependencies +++ /dev/null @@ -1,4 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:16:15 EDT 2007
-lucene=1.4.103.v20060601
-analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_docs b/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_docs deleted file mode 100644 index 56fe33a943..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/index/indexed_docs +++ /dev/null @@ -1,29 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:16:15 EDT 2007
-/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html=0
-/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.html=0
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/index/segments b/docs/org.eclipse.wst.xmleditor.doc.user/index/segments Binary files differdeleted file mode 100644 index 19b5d0c420..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/index/segments +++ /dev/null diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/myplugin.xml b/docs/org.eclipse.wst.xmleditor.doc.user/myplugin.xml deleted file mode 100644 index f0c28f188a..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/myplugin.xml +++ /dev/null @@ -1,32 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<!-- ================================================= --> -<!-- This is the plugin for declaring the help --> -<!-- contributions for using the tool. --> -<!-- ================================================= --> - -<plugin> - -<extension point="org.eclipse.help.toc"> - <toc file="XMLBuildermap_toc.xml"/> - <index path="index/"/> - -</extension> - -<extension - point="org.eclipse.help.index"> - <index file="org.eclipse.wst.xmleditor.doc.userindex.xml"/> - </extension> - -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/org.eclipse.wst.xmleditor.doc.userindex.html b/docs/org.eclipse.wst.xmleditor.doc.user/org.eclipse.wst.xmleditor.doc.userindex.html deleted file mode 100644 index 384cdcdc3a..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/org.eclipse.wst.xmleditor.doc.userindex.html +++ /dev/null @@ -1,162 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<meta name="copyright" content="(C) Copyright IBM Corporation 2007" /> -<meta name="security" content="public" /> -<meta name="Robots" content="index,follow" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta name="DC.Format" content="XHTML" /> -<!-- All rights reserved. Licensed Materials Property of IBM --> -<!-- US Government Users Restricted Rights --> -<!-- Use, duplication or disclosure restricted by --> -<!-- GSA ADP Schedule Contract with IBM Corp. --> -<link rel="stylesheet" type="text/css" href="ibmdita.css" /> -<title>Index</title> -</head> -<body> -<h1>Index</h1> -<a name="IDX0_43" href="#IDX1_43">C</a> -<a name="IDX0_44" href="#IDX1_44">D</a> -<a name="IDX0_45" href="#IDX1_45">E</a> -<a name="IDX0_4C" href="#IDX1_4C">L</a> -<a name="IDX0_50" href="#IDX1_50">P</a> -<a name="IDX0_58" href="#IDX1_58">X</a> -<hr></hr> -<strong><a name="IDX1_43" href="#IDX0_43">C</a></strong> -<ul class="indexlist"> -<li>character encoding -<ul class="indexlist"> -<li><a href="topics/cxmlenc.html#cxmlenc">text in files</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_44" href="#IDX0_44">D</a></strong> -<ul class="indexlist"> -<li>DOCTYPE declarations -<ul class="indexlist"> -<li><a href="topics/tedtdoc.html#tedtdoc">XML editor</a> -</li> -</ul> -</li> -<li>DTD -<ul class="indexlist"> -<li><a href="topics/tcrexdtd.html#tcrexdtd">generating XML files</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_45" href="#IDX0_45">E</a></strong> -<ul class="indexlist"> -<li>encodings -<ul class="indexlist"> -<li><a href="topics/cxmlenc.html#cxmlenc">supported character sets</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_4C" href="#IDX0_4C">L</a></strong> -<ul class="indexlist"> -<li>line delimiters -<ul class="indexlist"> -<li><a href="topics/tedtenc.html#tedtenc">XML files</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_50" href="#IDX0_50">P</a></strong> -<ul class="indexlist"> -<li>preferences -<ul class="indexlist"> -<li><a href="topics/txprefs.html#txprefs">XML editor</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_58" href="#IDX0_58">X</a></strong> -<ul class="indexlist"> -<li>XML catalog -<ul class="indexlist"> -<li><a href="topics/txmlcat.html#txmlcat">adding entries</a> -</li> -<li><a href="topics/cxmlcat.html#cxmlcat">overview</a> -</li> -</ul> -</li> -<li>XML editor -<ul class="indexlist"> -<li><a href="topics/twcdast.html#twcdast">content assist</a> -</li> -<li><a href="topics/txedtdes.html#txedtdes">Design view</a> -</li> -<li><a href="topics/tedtdoc.html#tedtdoc">DOCTYPE declarations</a> -</li> -<li><a href="topics/tedtcnst.html#tedtcnst">editing with constraints</a> -</li> -<li><a href="topics/rxmlbicons.html#ricons">icons</a> -</li> -<li><a href="topics/tedtsch.html#tedtsch">namespace information</a> -</li> -<li><a href="topics/cwxmledt.html#cwxmledt">overview</a> -</li> -<li><a href="topics/txprefs.html#txprefs">preferences</a> -</li> -<li><a href="topics/tedtproc.html#tedtproc">processing instructions</a> -</li> -<li><a href="topics/ttaghilt.html#ttaghilt">setting source highlighting styles</a> -</li> -<li><a href="topics/tsugstrat.html#xmlsourcesuggestionstrategy">source suggestion strategy</a> -</li> -<li><a href="topics/txedtsrc.html#txedtsrc">Source view</a> -</li> -<li><a href="topics/tedtgram.html#tedtgram">updating XML files</a> -</li> -<li><a href="topics/txedttag.html#txedttag">XML files</a> -</li> -</ul> -</li> -<li>XML files -<ul class="indexlist"> -<li><a href="topics/cxmlcat.html#cxmlcat">associations</a> -</li> -<li><a href="topics/twcdast.html#twcdast">content assist</a> -</li> -<li><a href="topics/tcretxml.html#tcretxml">creating</a> -</li> -<li><a href="topics/txedttag.html#txedttag">editing</a> -</li> -<li><a href="topics/tedtcnst.html#tedtcnst">editing with constraints</a> -</li> -<li><a href="topics/tcrexdtd.html#tcrexdtd">generating from DTDs</a> -</li> -<li><a href="topics/tcrexxsd.html#tcrexxsd">generating from XML schemas</a> -</li> -<li><a href="topics/tedtsch.html#tedtsch">namespace information</a> -</li> -<li><a href="topics/tedtproc.html#tedtproc">processing instructions</a> -</li> -<li><a href="topics/tedtenc.html#tedtenc">specifying line delimiters</a> -</li> -<li><a href="topics/tedtgram.html#tedtgram">updating with associated changes</a> -</li> -<li><a href="topics/twxvalid.html#twxvalid">validating</a> -</li> -</ul> -</li> -<li>XML schemas -<ul class="indexlist"> -<li><a href="topics/tcrexxsd.html#tcrexxsd">generating XML files</a> -</li> -</ul> -</li> -<li>XML templates -<ul class="indexlist"> -<li><a href="topics/twmacro.html#twmacro">working with predefined code</a> -</li> -</ul> -</li> -</ul> -</body></html> diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/org.eclipse.wst.xmleditor.doc.userindex.xml b/docs/org.eclipse.wst.xmleditor.doc.user/org.eclipse.wst.xmleditor.doc.userindex.xml deleted file mode 100644 index 4b66584a9b..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/org.eclipse.wst.xmleditor.doc.userindex.xml +++ /dev/null @@ -1,133 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<index> - <entry keyword="XML files"> - <entry keyword="creating"> - <topic href="topics/tcretxml.html#tcretxml" title="Creating XML files"/> - </entry> - <entry keyword="generating from DTDs"> - <topic href="topics/tcrexdtd.html#tcrexdtd" title="Generating XML files from DTDs"/> - </entry> - <entry keyword="generating from XML schemas"> - <topic href="topics/tcrexxsd.html#tcrexxsd" title="Generating XML files from XML schemas"/> - </entry> - <entry keyword="editing"> - <topic href="topics/txedttag.html#txedttag" title="Editing XML files"/> - </entry> - <entry keyword="specifying line delimiters"> - <topic href="topics/tedtenc.html#tedtenc" title="Specifying XML default encoding line delimiters"/> - </entry> - <entry keyword="namespace information"> - <topic href="topics/tedtsch.html#tedtsch" title="Editing namespace information"/> - </entry> - <entry keyword="processing instructions"> - <topic href="topics/tedtproc.html#tedtproc" title="Editing XML processing instructions"/> - </entry> - <entry keyword="content assist"> - <topic href="topics/twcdast.html#twcdast" title="Using XML content assist"/> - </entry> - <entry keyword="editing with constraints"> - <topic href="topics/tedtcnst.html#tedtcnst" title="Editing with DTD or XML schema constraints"/> - </entry> - <entry keyword="validating"> - <topic href="topics/twxvalid.html#twxvalid" title="Validating XML files"/> - </entry> - <entry keyword="associations"> - <topic href="topics/cxmlcat.html#cxmlcat" title="XML file associations with DTDs and XML schemas"/> - </entry> - <entry keyword="updating with associated changes"> - <topic href="topics/tedtgram.html#tedtgram" title="Updating XML files with changes made to DTDs and schemas"/> - </entry> - </entry> - <entry keyword="DTD"> - <entry keyword="generating XML files"> - <topic href="topics/tcrexdtd.html#tcrexdtd" title="Generating XML files from DTDs"/> - </entry> - </entry> - <entry keyword="XML schemas"> - <entry keyword="generating XML files"> - <topic href="topics/tcrexxsd.html#tcrexxsd" title="Generating XML files from XML schemas"/> - </entry> - </entry> - <entry keyword="XML editor"> - <entry keyword="XML files"> - <topic href="topics/txedttag.html#txedttag" title="Editing XML files"/> - </entry> - <entry keyword="overview"> - <topic href="topics/cwxmledt.html#cwxmledt" title="XML editor"/> - </entry> - <entry keyword="preferences"> - <topic href="topics/txprefs.html#txprefs" title="Defining XML editor preferences"/> - </entry> - <entry keyword="setting source highlighting styles"> - <topic href="topics/ttaghilt.html#ttaghilt" title="Setting source highlighting styles"/> - </entry> - <entry keyword="source suggestion strategy"> - <topic href="topics/tsugstrat.html#xmlsourcesuggestionstrategy" title="Setting the XML source suggestion strategy used by content assist"/> - </entry> - <entry keyword="Design view"> - <topic href="topics/txedtdes.html#txedtdes" title="Editing in the Design view"/> - </entry> - <entry keyword="DOCTYPE declarations"> - <topic href="topics/tedtdoc.html#tedtdoc" title="Editing DOCTYPE declarations"/> - </entry> - <entry keyword="namespace information"> - <topic href="topics/tedtsch.html#tedtsch" title="Editing namespace information"/> - </entry> - <entry keyword="processing instructions"> - <topic href="topics/tedtproc.html#tedtproc" title="Editing XML processing instructions"/> - </entry> - <entry keyword="Source view"> - <topic href="topics/txedtsrc.html#txedtsrc" title="Editing in the Source view"/> - </entry> - <entry keyword="content assist"> - <topic href="topics/twcdast.html#twcdast" title="Using XML content assist"/> - </entry> - <entry keyword="editing with constraints"> - <topic href="topics/tedtcnst.html#tedtcnst" title="Editing with DTD or XML schema constraints"/> - </entry> - <entry keyword="updating XML files"> - <topic href="topics/tedtgram.html#tedtgram" title="Updating XML files with changes made to DTDs and schemas"/> - </entry> - <entry keyword="icons"> - <topic href="topics/rxmlbicons.html#ricons" title="Icons used in the XML editor"/> - </entry> - </entry> - <entry keyword="preferences"> - <entry keyword="XML editor"> - <topic href="topics/txprefs.html#txprefs" title="Defining XML editor preferences"/> - </entry> - </entry> - <entry keyword="line delimiters"> - <entry keyword="XML files"> - <topic href="topics/tedtenc.html#tedtenc" title="Specifying XML default encoding line delimiters"/> - </entry> - </entry> - <entry keyword="character encoding"> - <entry keyword="text in files"> - <topic href="topics/cxmlenc.html#cxmlenc" title="XML and HTML encodings"/> - </entry> - </entry> - <entry keyword="encodings"> - <entry keyword="supported character sets"> - <topic href="topics/cxmlenc.html#cxmlenc" title="XML and HTML encodings"/> - </entry> - </entry> - <entry keyword="DOCTYPE declarations"> - <entry keyword="XML editor"> - <topic href="topics/tedtdoc.html#tedtdoc" title="Editing DOCTYPE declarations"/> - </entry> - </entry> - <entry keyword="XML templates"> - <entry keyword="working with predefined code"> - <topic href="topics/twmacro.html#twmacro" title="Working with XML templates"/> - </entry> - </entry> - <entry keyword="XML catalog"> - <entry keyword="overview"> - <topic href="topics/cxmlcat.html#cxmlcat" title="XML file associations with DTDs and XML schemas"/> - </entry> - <entry keyword="adding entries"> - <topic href="topics/txmlcat.html#txmlcat" title="Adding entries to the XML Catalog"/> - </entry> - </entry> -</index>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/plugin.properties b/docs/org.eclipse.wst.xmleditor.doc.user/plugin.properties deleted file mode 100644 index 13ed1ee38c..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/plugin.properties +++ /dev/null @@ -1,13 +0,0 @@ -############################################################################### -# Copyright (c) 2006 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### - -pluginName = XML editor -pluginProvider = Eclipse.org diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/plugin.xml b/docs/org.eclipse.wst.xmleditor.doc.user/plugin.xml deleted file mode 100644 index f0c28f188a..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/plugin.xml +++ /dev/null @@ -1,32 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<!-- ================================================= --> -<!-- This is the plugin for declaring the help --> -<!-- contributions for using the tool. --> -<!-- ================================================= --> - -<plugin> - -<extension point="org.eclipse.help.toc"> - <toc file="XMLBuildermap_toc.xml"/> - <index path="index/"/> - -</extension> - -<extension - point="org.eclipse.help.index"> - <index file="org.eclipse.wst.xmleditor.doc.userindex.xml"/> - </extension> - -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.dita deleted file mode 100644 index 9019048638..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.dita +++ /dev/null @@ -1,19 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<?Pub Inc?>
-<concept id="creatingxmlfiles" xml:lang="en-us">
-<title>Creating XML files</title>
-<shortdesc>This section contains information on creating XML files:</shortdesc>
-<conbody></conbody>
-<related-links>
-<linklist>
-<link href="tcretxml.dita"><linktext>Creating empty XML files</linktext></link>
-<link href="tcrexdtd.dita"><linktext>Generating XML files from a DTDs</linktext>
-</link>
-<link href="tcrexxsd.dita"><linktext>Generating XML files from XML
-schemas</linktext></link>
-</linklist>
-</related-links>
-</concept>
-<?Pub *0000000718?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html deleted file mode 100644 index 1ebbd51acf..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ccreatxm.html +++ /dev/null @@ -1,41 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Creating XML files" /> -<meta name="abstract" content="This section contains information on creating XML files:" /> -<meta name="description" content="This section contains information on creating XML files:" /> -<meta scheme="URI" name="DC.Relation" content="tcretxml.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrexdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="tcrexxsd.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="creatingxmlfiles" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating XML files</title> -</head> -<body id="creatingxmlfiles"><a name="creatingxmlfiles"><!-- --></a> - - -<h1 class="topictitle1">Creating XML files</h1> - - -<div><p>This section contains information on creating XML files:</p> -</div> - -<div> -<div class="linklist"> -<div><a href="tcretxml.html" title="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating empty XML files</a></div> -<div><a href="tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from a DTDs</a></div> -<div><a href="tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML -schemas</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html deleted file mode 100644 index e4aa40e820..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkXML.html +++ /dev/null @@ -1,45 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Working with XML files" /> -<meta name="abstract" content="This section contains information on the following:" /> -<meta name="description" content="This section contains information on the following:" /> -<meta scheme="URI" name="DC.Relation" content="ccreatxm.html" /> -<meta scheme="URI" name="DC.Relation" content="txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="twxvalid.html" /> -<meta scheme="URI" name="DC.Relation" content="cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="rxmlbicons.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="workingwithxmlfiles" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Working with XML files</title> -</head> -<body id="workingwithxmlfiles"><a name="workingwithxmlfiles"><!-- --></a> - - -<h1 class="topictitle1">Working with XML files</h1> - - -<div><p>This section contains information on the following:</p> -</div> - -<div> -<div class="linklist"> -<div><a href="ccreatxm.html" title="This section contains information on creating XML files:">Creating XML files</a></div> -<div><a href="txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -<div><a href="twxvalid.html" title="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed.">Validating XML files</a></div> -<div><a href="cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML -schema</a></div> -<div><a href="rxmlbicons.html" title="The following XML editor icons appear in the Outline and Design view.">Icons used in the XML editor</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkxml.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkxml.dita deleted file mode 100644 index a6fa3e16f2..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cworkxml.dita +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<?Pub Inc?>
-<concept id="workingwithxmlfiles" xml:lang="en-us">
-<title>Working with XML files</title>
-<shortdesc>This section contains information on the following:</shortdesc>
-<conbody></conbody>
-<related-links>
-<linklist>
-<link href="ccreatxm.dita"><linktext>Creating XML files</linktext></link>
-<link href="txedttag.dita"><linktext>Editing XML files</linktext>
-</link>
-<link href="twxvalid.dita"><linktext>Validating XML files</linktext></link>
-<link href="cxmlcat.dita"><linktext>XML file associations with DTDs and XML
-schema</linktext></link>
-<link href="rxmlbicons.dita"><linktext>Icons used in the XML editor</linktext>
-</link>
-</linklist>
-</related-links>
-</concept>
-<?Pub *0000000871?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.dita deleted file mode 100644 index 34a2e0f6d3..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="cwxmledt" xml:lang="en-us">
-<title>XML editor</title>
-<titlealts>
-<searchtitle>XML editor</searchtitle>
-</titlealts>
-<shortdesc>The XML editor is a tool for creating and viewing XML files.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>You can use it to perform a variety of tasks such as:</p>
-<ul>
-<li>Creating new, empty XML files or generating them from existing DTDs or
-existing XML schemas</li>
-<li>Editing XML files</li>
-<li>Importing existing XML files for structured viewing</li>
-<li>Associating XML files with DTDs or XML schemas</li>
-</ul>
-<p>The XML editor has two main views - the Source view and the Design view.
-You can also use the <b>Outline</b> view to insert and delete elements.</p>
-<section><title>Source view</title><p>The Source view enables you to view
-and work directly with a file's source code. Many of the XML editing features
-in the XML editor Source view are very similar to those available in the Source
-view of Page Designer.</p><p>The Source view has many text editing features,
-such as: <ul>
-<li> Syntax highlighting, unlimited undo/redo, and user-defined templates.</li>
-<li> Content assist, which uses the information in a DTD or schema content
-model to provide a list of acceptable continuations depending on where the
-cursor is located in an XML file, or what has just been type</li>
-<li>"Smart" double-clicking behavior. If your cursor is placed in an attribute
-value, one double-click selects that value, another double click selects the
-attribute-value pair, and a third double-click selects the entire tag. This
-makes it easier to copy and paste commonly used pieces of XML.</li>
-</ul></p></section>
-<section><title>Design view</title><p>The XML editor also has a Design view.
-In it: <ul>
-<li>The XML file is represented simultaneously as a table and a tree. This
-helps make navigation and editing easier.</li>
-<li>Content and attribute values can be edited directly in the table cells,
-while pop-up menus on the tree nodes give alternatives that are valid for
-that location. For example, the <uicontrol>Add child</uicontrol> menu item
-will list only those elements from a DTD or XML schema which would be valid
-children at that point (as long as grammar constraints are on).</li>
-</ul></p><p>The Design view is especially helpful if you are new to XML, or
-need to do form-oriented editing. For example, you could use the Create XML
-File wizard to create a template XML file for a job description form from
-a job description DTD. After those steps are completed, you would
-only have to fill in the form data using the Design view.</p><p>The following
-links provide more information about the XML editor:</p></section>
-</conbody>
-</concept>
-<?Pub *0000002994?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html deleted file mode 100644 index 0515a1de8c..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cwxmledt.html +++ /dev/null @@ -1,117 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="XML editor" /> -<meta name="abstract" content="The XML editor is a tool for creating and viewing XML files." /> -<meta name="description" content="The XML editor is a tool for creating and viewing XML files." /> -<meta content="XML editor, overview" name="DC.subject" /> -<meta content="XML editor, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretxml.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexxsd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twxvalid.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwxmledt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML editor</title> -</head> -<body id="cwxmledt"><a name="cwxmledt"><!-- --></a> - - -<h1 class="topictitle1">XML editor</h1> - - - - -<div><p>The XML editor is a tool for creating and viewing XML files.</p> - -<p>You can use it to perform a variety of tasks such as:</p> - -<ul> -<li>Creating new, empty XML files or generating them from existing DTDs or -existing XML schemas</li> - -<li>Editing XML files</li> - -<li>Importing existing XML files for structured viewing</li> - -<li>Associating XML files with DTDs or XML schemas</li> - -</ul> - -<p>The XML editor has two main views - the Source view and the Design view. -You can also use the <strong>Outline</strong> view to insert and delete elements.</p> - -<div class="section"><h4 class="sectiontitle">Source view</h4><p>The Source view enables you to view -and work directly with a file's source code. Many of the XML editing features -in the XML editor Source view are very similar to those available in the Source -view of Page Designer.</p> -<div class="p">The Source view has many text editing features, -such as: <ul> -<li> Syntax highlighting, unlimited undo/redo, and user-defined templates.</li> - -<li> Content assist, which uses the information in a DTD or schema content -model to provide a list of acceptable continuations depending on where the -cursor is located in an XML file, or what has just been type</li> - -<li>"Smart" double-clicking behavior. If your cursor is placed in an attribute -value, one double-click selects that value, another double click selects the -attribute-value pair, and a third double-click selects the entire tag. This -makes it easier to copy and paste commonly used pieces of XML.</li> - -</ul> -</div> -</div> - -<div class="section"><h4 class="sectiontitle">Design view</h4><div class="p">The XML editor also has a Design view. -In it: <ul> -<li>The XML file is represented simultaneously as a table and a tree. This -helps make navigation and editing easier.</li> - -<li>Content and attribute values can be edited directly in the table cells, -while pop-up menus on the tree nodes give alternatives that are valid for -that location. For example, the <span class="uicontrol">Add child</span> menu item -will list only those elements from a DTD or XML schema which would be valid -children at that point (as long as grammar constraints are on).</li> - -</ul> -</div> -<p>The Design view is especially helpful if you are new to XML, or -need to do form-oriented editing. For example, you could use the Create XML -File wizard to create a template XML file for a job description form from -a job description DTD. After those steps are completed, you would -only have to fill in the form data using the Design view.</p> -<p>The following -links provide more information about the XML editor:</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcretxml.html" title="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating XML files</a></div> -<div><a href="../topics/tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from DTDs</a></div> -<div><a href="../topics/tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML schemas</a></div> -<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -<div><a href="../topics/twxvalid.html" title="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed.">Validating XML files</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.dita deleted file mode 100644 index fc8a56b76e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.dita +++ /dev/null @@ -1,123 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cxmlcat" xml:lang="en-us">
-<title>XML file associations with DTDs and XML schemas</title>
-<titlealts>
-<searchtitle>XML file associations with DTDs and XML schemas</searchtitle>
-</titlealts>
-<shortdesc>When an XML file is associated with a DTD or XML schema, it is
-bound by any structural rules contained in the DTD or XML schema. To be considered
-a valid XML file, a document must be accompanied by a DTD or an XML schema,
-and conform to all of the declarations in the DTD or the XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML catalog<indexterm>overview</indexterm></indexterm>
-<indexterm>XML files<indexterm>associations</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>There are two different ways to associate XML files with DTDs or XML schemas.</p>
-<ol>
-<li>Direct association - The XML file contains either the name of a DTD in
-its doctype declaration (for example, <!DOCTYPE root-element SYSTEM " <varname>dtdfile.dtd</varname>"
->, where <varname>dtdfile.dtd</varname> is the name of the DTD file) or it
-contains the path of an XML schema in the schemaLocation attribute of the
-XML file root element (for example, <xsi:schemaLocation="http://www.ibm.com
- <varname>schema.xsd</varname>">, where <varname>schema.xsd</varname> is
-the name of the XML schema.</li>
-<li>XML Catalog entry - You can register DTD and XML schema files in the XML
-Catalog and associate them with a <varname>Key</varname> that represents
-them. You can then refer to a DTD or XML schema file <varname>Key</varname> from
-an XML file instead of referring directly to the DTD or XML schema file. An
-XML Catalog entry contains two parts - the Key (which represents the DTD or
-XML schema) and a URI (which contains information about the DTD or XML schema
-location).</li>
-</ol>
-<section><title>How an association works</title><b>Associating an XML file
-with a DTD </b><p>If an XML file is associated with a DTD, a DOCTYPE tag such
-as the following one is included in the XML file:<codeblock><!DOCTYPE root-name PUBLIC "<varname>InvoiceId</varname>" "<varname>C:\mydtds\Invoice.dtd</varname
->">
-</codeblock></p><p><varname>InvoiceId</varname> is the public identifier of
-the DTD file. It is used to associate the XML file with a DTD file (in this
-case, the DTD file is <varname>Invoice.dtd</varname>). If the public identifier
-InvoiceId corresponds to the <varname>Key</varname> of the XML Catalog entry
-for Invoice.dtd, then the <varname>URI</varname> of the XML Catalog entry
-(which contains information about the location of Invoice.dtd) is used to
-locate the DTD. Otherwise, the DOCTYPE's system identifier ( <varname>"C:\mydtds\Invoice.dtd"</varname>),
-which refers directly to the file system location of the DTD, is used to locate
-the DTD.</p><p> <b>Note</b>: You can also use a system identifier as a Key
-in an XML Catalog entry. If you use a system identifier as a Key, a DOCTYPE
-tag such as the following one is included in an XML file:</p><codeblock><!DOCTYPE Root-name SYSTEM "<varname>MyDTD.dtd</varname>"> </codeblock
-><p>where <varname>MyDTD.dtd</varname> is the system identifier that corresponds
-to the Key of an XML Catalog entry.</p></section>
-<section><b>Associating an XML file with an XML schema</b><p>If an XML file
-is associated with an XML schema, one or more schema location attributes are
-included in the XML file. The information in the schemaLocation is provided
-as a "hint" to the XML processor. The following examples show schemaLocation
-attributes.</p><p> <b>Example 1 </b><codeblock><purchaseOrder xmlns="http://www.ibm.com"
-xsi:schemaLocation="http://www.ibm.com C:\myschemas\PurchaseOrder.xsd">
-<shipTo country="US">
-...</codeblock> </p><p><b>Example 2 </b><codeblock><purchaseOrder xmlns="http://www.ibm.com"
-xsi:schemaLocation="http://www.ibm.com PO.xsd">
-<shipTo country="US">
-....</codeblock> </p><p>In Example 1, the schemaLocation 'hint' ('C:\myschemas\PurchaseOrder.xsd')
-refers directly to the file system location or URI of the XML schema. In this
-case, the schema file will be located by the XML processor directly.</p><p>In
-Example 2, the schemaLocation 'hint' ('PO.xsd') refers to an XML Catalog entry.
-PO.xsd corresponds to the <varname>Key</varname> of the XML Catalog entry
-for PurchaseOrder.xsd, and the URI of the XML Catalog entry (which contains
-information about the location of PurchaseOrder.xsd) will be used to located
-the XML schema.</p><p>In both examples, <codeph>http://www.ibm.com</codeph> in
-the <codeph>xsi:schemaLocation</codeph> tag is a URI that identifies the namespace
-for the XML schema.</p><p>You can also use a namespace as a Key for an XML
-Catalog entry. If you use a namespace as a Key, a schemaLocation tag such
-as the following one is included in an XML file:<codeblock><purchaseOrder xmlns:="www.ibm.com"
-xsi:schemaLocation="http://www.ibm.com po/xsd/PurchaseOrder.xsd "></codeblock></p><p>The
-schemaLocation attribute points to both the Key and the actual location of
-the schema.</p><p><b>DTD or XML schema resides on a remote server</b></p><p>Several
-functions in the XML editor, such as validation and content assist, require
-the availability of a DTD or an XML schema. The product documentation provides
-usage information for cases when the DTD or XML schema resides on your local
-machine. However, in many cases, the DTD or XML schema can reside on a remote
-server, for example:</p><p><codeph><!DOCTYPE Catalog PUBLIC "abc/Catalog"
-"http://xyz.abc.org/dtds/catalog.dtd"></codeph></p><p>Normally, this case
-poses no problem, because the DTD or XML schema can be retrieved from the
-remote server. However, if you are behind a firewall, and do not have a SOCKSified
-system, the workbench currently does not provide a way for you to specify
-a socks server for retrieving a DTD or XML schema. If you are unable to SOCKSify
-your system, the workaround for this problem is to retrieve a copy of the
-DTD or XML schema (using a Web browser, for example) and save that copy on
-your local machine. Then, you can either place a local copy in the same project
-as your XML file, or use the XML Catalog to associate a public identifier
-with the DTD's (local) location.</p><p><b>Note</b>: If you have an XML file
-associated with an XML schema or DTD that is elsewhere in the network, and
-you are working on a machine disconnected from the network, you can follow
-the steps described previously if you want to use content assist or validate
-your XML file. </p></section>
-<section><title>Advantages of XML Catalog entry associations</title><p>If
-you create a direct association between an XML file and an XML schema or DTD
-file, any time you change the location of the schema or DTD you have to track
-down and update all of the referencing XML files with the new location of
-the DTD or schema. If, however, you associate an XML file with an XML schema
-or DTD Key, then, when you change the location of the schema or DTD, you only
-have to update the XML Catalog entry, instead of each individual XML file.</p><p>For
-example, you have a DTD called "Building.dtd", which is associated with five
-XML files - Office.xml, House.xml, Apartment.xml, Bank.xml, and PostOffice.xml.
-You move the DTD file Building.dtd to a new location. If you have a direction
-association between Building.dtd and all the XML files, you will have to update
-the <DOCTTYPE> declaration in each XML file to reflect the new location
-of Building.dtd. If, however, you have an XML Catalog association, and all
-the XML files just refer to the Key of Building.dtd, then you only have to
-update the URI and all the XML files will point to the new location of Building.dtd.</p></section>
-<section><title>Updating an entry in the XML Catalog</title><p>After you have
-updated an entry in the XML Catalog, you might need to refresh the XML editor
-view so that it uses the new information. To do this, click the <uicontrol>Reload
-Dependencies</uicontrol> toolbar button <image href="../images/rldgrmr.gif">
-<alt>This graphic is the Reload Dependencies toolbar button</alt></image> and
-the view will be updated using the current XML Catalog settings. You only
-need to refresh the XML editor view when you have an XML file open that references
-the XML Catalog entry that was updated.</p><p>For more information, refer
-to the related tasks.</p></section>
-</conbody>
-</concept>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html deleted file mode 100644 index cb76c1432e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlcat.html +++ /dev/null @@ -1,198 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="XML file associations with DTDs and XML schemas" /> -<meta name="abstract" content="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema." /> -<meta name="description" content="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema." /> -<meta content="XML files, associating with DTDs, associating with XML schemas, XML catalog, overview" name="DC.subject" /> -<meta content="XML files, associating with DTDs, associating with XML schemas, XML catalog, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtproc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cxmlcat" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML file associations with DTDs and XML schemas</title> -</head> -<body id="cxmlcat"><a name="cxmlcat"><!-- --></a> - - -<h1 class="topictitle1">XML file associations with DTDs and XML schemas</h1> - - - - -<div><p>When an XML file is associated with a DTD or XML schema, it is -bound by any structural rules contained in the DTD or XML schema. To be considered -a valid XML file, a document must be accompanied by a DTD or an XML schema, -and conform to all of the declarations in the DTD or the XML schema.</p> - -<p>There are two different ways to associate XML files with DTDs or XML schemas.</p> - -<ol> -<li>Direct association - The XML file contains either the name of a DTD in -its doctype declaration (for example, <!DOCTYPE root-element SYSTEM " <var class="varname">dtdfile.dtd</var>" ->, where <var class="varname">dtdfile.dtd</var> is the name of the DTD file) or it -contains the path of an XML schema in the schemaLocation attribute of the -XML file root element (for example, <xsi:schemaLocation="http://www.ibm.com - <var class="varname">schema.xsd</var>">, where <var class="varname">schema.xsd</var> is -the name of the XML schema.</li> - -<li>XML Catalog entry - You can register DTD and XML schema files in the XML -Catalog and associate them with a <var class="varname">Key</var> that represents -them. You can then refer to a DTD or XML schema file <var class="varname">Key</var> from -an XML file instead of referring directly to the DTD or XML schema file. An -XML Catalog entry contains two parts - the Key (which represents the DTD or -XML schema) and a URI (which contains information about the DTD or XML schema -location).</li> - -</ol> - -<div class="section"><h4 class="sectiontitle">How an association works</h4><strong>Associating an XML file -with a DTD </strong><div class="p">If an XML file is associated with a DTD, a DOCTYPE tag such -as the following one is included in the XML file:<pre><!DOCTYPE root-name PUBLIC "<var class="varname">InvoiceId</var>" "<var class="varname">C:\mydtds\Invoice.dtd</var>"> -</pre> -</div> -<p><var class="varname">InvoiceId</var> is the public identifier of -the DTD file. It is used to associate the XML file with a DTD file (in this -case, the DTD file is <var class="varname">Invoice.dtd</var>). If the public identifier -InvoiceId corresponds to the <var class="varname">Key</var> of the XML Catalog entry -for Invoice.dtd, then the <var class="varname">URI</var> of the XML Catalog entry -(which contains information about the location of Invoice.dtd) is used to -locate the DTD. Otherwise, the DOCTYPE's system identifier ( <var class="varname">"C:\mydtds\Invoice.dtd"</var>), -which refers directly to the file system location of the DTD, is used to locate -the DTD.</p> -<p> <strong>Note</strong>: You can also use a system identifier as a Key -in an XML Catalog entry. If you use a system identifier as a Key, a DOCTYPE -tag such as the following one is included in an XML file:</p> -<pre><!DOCTYPE Root-name SYSTEM "<var class="varname">MyDTD.dtd</var>"> </pre> -<p>where <var class="varname">MyDTD.dtd</var> is the system identifier that corresponds -to the Key of an XML Catalog entry.</p> -</div> - -<div class="section"><strong>Associating an XML file with an XML schema</strong><p>If an XML file -is associated with an XML schema, one or more schema location attributes are -included in the XML file. The information in the schemaLocation is provided -as a "hint" to the XML processor. The following examples show schemaLocation -attributes.</p> -<div class="p"> <strong>Example 1 </strong><pre><purchaseOrder xmlns="http://www.ibm.com" -xsi:schemaLocation="http://www.ibm.com C:\myschemas\PurchaseOrder.xsd"> -<shipTo country="US"> -...</pre> - </div> -<div class="p"><strong>Example 2 </strong><pre><purchaseOrder xmlns="http://www.ibm.com" -xsi:schemaLocation="http://www.ibm.com PO.xsd"> -<shipTo country="US"> -....</pre> - </div> -<p>In Example 1, the schemaLocation 'hint' ('C:\myschemas\PurchaseOrder.xsd') -refers directly to the file system location or URI of the XML schema. In this -case, the schema file will be located by the XML processor directly.</p> -<p>In -Example 2, the schemaLocation 'hint' ('PO.xsd') refers to an XML Catalog entry. -PO.xsd corresponds to the <var class="varname">Key</var> of the XML Catalog entry -for PurchaseOrder.xsd, and the URI of the XML Catalog entry (which contains -information about the location of PurchaseOrder.xsd) will be used to located -the XML schema.</p> -<p>In both examples, <samp class="codeph">http://www.ibm.com</samp> in -the <samp class="codeph">xsi:schemaLocation</samp> tag is a URI that identifies the namespace -for the XML schema.</p> -<div class="p">You can also use a namespace as a Key for an XML -Catalog entry. If you use a namespace as a Key, a schemaLocation tag such -as the following one is included in an XML file:<pre><purchaseOrder xmlns:="www.ibm.com" -xsi:schemaLocation="http://www.ibm.com po/xsd/PurchaseOrder.xsd "></pre> -</div> -<p>The -schemaLocation attribute points to both the Key and the actual location of -the schema.</p> -<p><strong>DTD or XML schema resides on a remote server</strong></p> -<p>Several -functions in the XML editor, such as validation and content assist, require -the availability of a DTD or an XML schema. The product documentation provides -usage information for cases when the DTD or XML schema resides on your local -machine. However, in many cases, the DTD or XML schema can reside on a remote -server, for example:</p> -<p><samp class="codeph"><!DOCTYPE Catalog PUBLIC "abc/Catalog" -"http://xyz.abc.org/dtds/catalog.dtd"></samp></p> -<p>Normally, this case -poses no problem, because the DTD or XML schema can be retrieved from the -remote server. However, if you are behind a firewall, and do not have a SOCKSified -system, the workbench currently does not provide a way for you to specify -a socks server for retrieving a DTD or XML schema. If you are unable to SOCKSify -your system, the workaround for this problem is to retrieve a copy of the -DTD or XML schema (using a Web browser, for example) and save that copy on -your local machine. Then, you can either place a local copy in the same project -as your XML file, or use the XML Catalog to associate a public identifier -with the DTD's (local) location.</p> -<p><strong>Note</strong>: If you have an XML file -associated with an XML schema or DTD that is elsewhere in the network, and -you are working on a machine disconnected from the network, you can follow -the steps described previously if you want to use content assist or validate -your XML file. </p> -</div> - -<div class="section"><h4 class="sectiontitle">Advantages of XML Catalog entry associations</h4><p>If -you create a direct association between an XML file and an XML schema or DTD -file, any time you change the location of the schema or DTD you have to track -down and update all of the referencing XML files with the new location of -the DTD or schema. If, however, you associate an XML file with an XML schema -or DTD Key, then, when you change the location of the schema or DTD, you only -have to update the XML Catalog entry, instead of each individual XML file.</p> -<p>For -example, you have a DTD called "Building.dtd", which is associated with five -XML files - Office.xml, House.xml, Apartment.xml, Bank.xml, and PostOffice.xml. -You move the DTD file Building.dtd to a new location. If you have a direction -association between Building.dtd and all the XML files, you will have to update -the <DOCTTYPE> declaration in each XML file to reflect the new location -of Building.dtd. If, however, you have an XML Catalog association, and all -the XML files just refer to the Key of Building.dtd, then you only have to -update the URI and all the XML files will point to the new location of Building.dtd.</p> -</div> - -<div class="section"><h4 class="sectiontitle">Updating an entry in the XML Catalog</h4><p>After you have -updated an entry in the XML Catalog, you might need to refresh the XML editor -view so that it uses the new information. To do this, click the <span class="uicontrol">Reload -Dependencies</span> toolbar button <img src="../images/rldgrmr.gif" alt="This graphic is the Reload Dependencies toolbar button" /> and -the view will be updated using the current XML Catalog settings. You only -need to refresh the XML editor view when you have an XML file open that references -the XML Catalog entry that was updated.</p> -<p>For more information, refer -to the related tasks.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -<div><a href="../topics/tedtproc.html" title="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction.">Editing XML processing instructions</a></div> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.dita deleted file mode 100644 index 21aa5904d0..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.dita +++ /dev/null @@ -1,162 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<?Pub Inc?>
-<concept id="cxmlenc" xml:lang="en-us">
-<title>XML and HTML encodings</title>
-<titlealts>
-<searchtitle>XML and HTML encodings</searchtitle>
-</titlealts>
-<shortdesc>Encodings enable you to specify what character encoding your text
-is in.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>character encoding<indexterm>text in files</indexterm></indexterm>
-<indexterm>encodings<indexterm>supported character sets</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>The IANA name is used in the encoding statement of an XML file, or charset
-directive in an HTML file.</p>
-<p>The HTML and XML editors support the following encodings:</p>
-<table rowheader="firstcol">
-<tgroup cols="2"><colspec colname="COLSPEC0"/><colspec colname="COLSPEC1"/>
-<thead>
-<row>
-<entry colname="COLSPEC0" valign="top"> <p><b>XML Encoding (IANA Name)</b></p> </entry>
-<entry colname="COLSPEC1" valign="top"> <p><b>Description</b></p> </entry>
-</row>
-</thead>
-<tbody>
-<row>
-<entry> <p>BIG5</p> </entry>
-<entry> <p>Big5, Traditional Chinese</p> </entry>
-</row>
-<row>
-<entry> <p>EUC-JP</p> </entry>
-<entry> <p>EUC encoding, Japanese</p> </entry>
-</row>
-<row>
-<entry> <p>EUC-KR</p> </entry>
-<entry> <p>EUC encoding, Korean</p> </entry>
-</row>
-<row>
-<entry> <p>GB2312</p> </entry>
-<entry> <p>GBK, Simplified Chinese</p> </entry>
-</row>
-<row>
-<entry>GB18030</entry>
-<entry>National Standard, Chinese</entry>
-</row>
-<row>
-<entry>IBM864</entry>
-<entry>PC Arabic (encoding not supported by the Page Designer Design page.
-)</entry>
-</row>
-<row>
-<entry> <p>ISO-2022-JP</p> </entry>
-<entry> <p>ISO 2022, Japanese</p> </entry>
-</row>
-<row>
-<entry> <p>ISO-2022-KR</p> </entry>
-<entry> <p>ISO 2022, Korean</p> </entry>
-</row>
-<row>
-<entry> <p>ISO-8859-1</p> </entry>
-<entry> <p>ISO Latin-1</p> </entry>
-</row>
-<row>
-<entry>ISO-8859-2</entry>
-<entry>Central/East European (Slavic)</entry>
-</row>
-<row>
-<entry>ISO-8859-3</entry>
-<entry>Southern European</entry>
-</row>
-<row>
-<entry>ISO-8859-4</entry>
-<entry>ISO 8859-4, Cyrillic</entry>
-</row>
-<row>
-<entry>ISO-8859-5</entry>
-<entry>ISO 8859-5, Cyrillic</entry>
-</row>
-<row>
-<entry> <p>ISO-8859-6</p> </entry>
-<entry> <p>Arabic (Logical)</p> </entry>
-</row>
-<row>
-<entry>ISO-8859-7</entry>
-<entry>Greek</entry>
-</row>
-<row>
-<entry> <p>ISO-8859-8-I</p> </entry>
-<entry> <p>Hebrew (Logical)</p> </entry>
-</row>
-<row>
-<entry> <p>ISO-8859-8</p> </entry>
-<entry> <p>Hebrew (Visual)(encoding supported, but not supported by the Page
-Designer Design page)</p> </entry>
-</row>
-<row>
-<entry>ISO-8859-9</entry>
-<entry>Turkish</entry>
-</row>
-<row>
-<entry> <p>SHIFT_JIS</p> </entry>
-<entry> <p>Shift-JIS, Japanese</p> </entry>
-</row>
-<row>
-<entry>TIS-620</entry>
-<entry>TISI, Thai</entry>
-</row>
-<row>
-<entry> <p>US-ASCII</p> </entry>
-<entry> <p>US ASCII</p> </entry>
-</row>
-<row>
-<entry> <p>UTF-8</p> </entry>
-<entry> <p>ISO 10646/Unicode, one-byte encoding</p> </entry>
-</row>
-<row>
-<entry> <p>UTF-16</p> </entry>
-<entry> <p>ISO 10646/Unicode, two-byte encoding</p> </entry>
-</row>
-<row>
-<entry> <p>UTF-16BE</p> </entry>
-<entry> <p>Unicode BigEndian</p> </entry>
-</row>
-<row>
-<entry> <p>UTF-16LE</p> </entry>
-<entry> <p>Unicode LittleEndian</p> </entry>
-</row>
-<row>
-<entry>WINDOWS-874</entry>
-<entry>Thai, <tm tmclass="special" tmowner="Microsoft Corporation" tmtype="reg"
-trademark="Microsoft">Microsoft</tm></entry>
-</row>
-<row>
-<entry> <p>WINDOWS-1252</p> </entry>
-<entry> <p>ISO Latin-1</p> </entry>
-</row>
-<row>
-<entry> <p>WINDOWS-1255</p> </entry>
-<entry> <p>Hebrew</p> </entry>
-</row>
-<row>
-<entry> <p>WINDOWS-1256</p> </entry>
-<entry> <p>Arabic</p> </entry>
-</row>
-<row>
-<entry>X-EUC-JP</entry>
-<entry>EUC encoding, Japanese (alias for EUC-JP)</entry>
-</row>
-<row>
-<entry>X-SJIS</entry>
-<entry>Shift-JIS, Japanese (alias for SHIFT_JIS)</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-</conbody>
-</concept>
-<?Pub *0000003991?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html deleted file mode 100644 index 26b1018f71..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmlenc.html +++ /dev/null @@ -1,320 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="XML and HTML encodings" /> -<meta name="abstract" content="Encodings enable you to specify what character encoding your text is in." /> -<meta name="description" content="Encodings enable you to specify what character encoding your text is in." /> -<meta content="Encodings, HTML, XML" name="DC.subject" /> -<meta content="Encodings, HTML, XML" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cxmlenc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML and HTML encodings</title> -</head> -<body id="cxmlenc"><a name="cxmlenc"><!-- --></a> - - -<h1 class="topictitle1">XML and HTML encodings</h1> - - - - -<div><p>Encodings enable you to specify what character encoding your text -is in.</p> - -<p>The IANA name is used in the encoding statement of an XML file, or charset -directive in an HTML file.</p> - -<p>The HTML and XML editors support the following encodings:</p> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<thead align="left"> -<tr> -<th valign="top" class="firstcol" id="N1007B"> <p><strong>XML Encoding (IANA Name)</strong></p> - </th> - -<th valign="top" id="N1008D"> <p><strong>Description</strong></p> - </th> - -</tr> - -</thead> - -<tbody> -<tr> -<th valign="top" class="firstcol" id="N100AB" headers="N1007B "> <p>BIG5</p> - </th> - -<td valign="top" headers="N100AB N1008D "> <p>Big5, Traditional Chinese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N100CB" headers="N1007B "> <p>EUC-JP</p> - </th> - -<td valign="top" headers="N100CB N1008D "> <p>EUC encoding, Japanese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N100EB" headers="N1007B "> <p>EUC-KR</p> - </th> - -<td valign="top" headers="N100EB N1008D "> <p>EUC encoding, Korean</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1010B" headers="N1007B "> <p>GB2312</p> - </th> - -<td valign="top" headers="N1010B N1008D "> <p>GBK, Simplified Chinese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1012B" headers="N1007B ">GB18030</th> - -<td valign="top" headers="N1012B N1008D ">National Standard, Chinese</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1013F" headers="N1007B ">IBM864</th> - -<td valign="top" headers="N1013F N1008D ">PC Arabic (encoding not supported by the Page Designer Design page. -)</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10153" headers="N1007B "> <p>ISO-2022-JP</p> - </th> - -<td valign="top" headers="N10153 N1008D "> <p>ISO 2022, Japanese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10173" headers="N1007B "> <p>ISO-2022-KR</p> - </th> - -<td valign="top" headers="N10173 N1008D "> <p>ISO 2022, Korean</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10193" headers="N1007B "> <p>ISO-8859-1</p> - </th> - -<td valign="top" headers="N10193 N1008D "> <p>ISO Latin-1</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N101B3" headers="N1007B ">ISO-8859-2</th> - -<td valign="top" headers="N101B3 N1008D ">Central/East European (Slavic)</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N101C7" headers="N1007B ">ISO-8859-3</th> - -<td valign="top" headers="N101C7 N1008D ">Southern European</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N101DB" headers="N1007B ">ISO-8859-4</th> - -<td valign="top" headers="N101DB N1008D ">ISO 8859-4, Cyrillic</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N101EF" headers="N1007B ">ISO-8859-5</th> - -<td valign="top" headers="N101EF N1008D ">ISO 8859-5, Cyrillic</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10203" headers="N1007B "> <p>ISO-8859-6</p> - </th> - -<td valign="top" headers="N10203 N1008D "> <p>Arabic (Logical)</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10223" headers="N1007B ">ISO-8859-7</th> - -<td valign="top" headers="N10223 N1008D ">Greek</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10237" headers="N1007B "> <p>ISO-8859-8-I</p> - </th> - -<td valign="top" headers="N10237 N1008D "> <p>Hebrew (Logical)</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10257" headers="N1007B "> <p>ISO-8859-8</p> - </th> - -<td valign="top" headers="N10257 N1008D "> <p>Hebrew (Visual)(encoding supported, but not supported by the Page -Designer Design page)</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N10277" headers="N1007B ">ISO-8859-9</th> - -<td valign="top" headers="N10277 N1008D ">Turkish</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1028B" headers="N1007B "> <p>SHIFT_JIS</p> - </th> - -<td valign="top" headers="N1028B N1008D "> <p>Shift-JIS, Japanese</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N102AB" headers="N1007B ">TIS-620</th> - -<td valign="top" headers="N102AB N1008D ">TISI, Thai</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N102BF" headers="N1007B "> <p>US-ASCII</p> - </th> - -<td valign="top" headers="N102BF N1008D "> <p>US ASCII</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N102DF" headers="N1007B "> <p>UTF-8</p> - </th> - -<td valign="top" headers="N102DF N1008D "> <p>ISO 10646/Unicode, one-byte encoding</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N102FF" headers="N1007B "> <p>UTF-16</p> - </th> - -<td valign="top" headers="N102FF N1008D "> <p>ISO 10646/Unicode, two-byte encoding</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1031F" headers="N1007B "> <p>UTF-16BE</p> - </th> - -<td valign="top" headers="N1031F N1008D "> <p>Unicode BigEndian</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1033F" headers="N1007B "> <p>UTF-16LE</p> - </th> - -<td valign="top" headers="N1033F N1008D "> <p>Unicode LittleEndian</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1035F" headers="N1007B ">WINDOWS-874</th> - -<td valign="top" headers="N1035F N1008D ">Thai, Microsoft<sup>®</sup></td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1037C" headers="N1007B "> <p>WINDOWS-1252</p> - </th> - -<td valign="top" headers="N1037C N1008D "> <p>ISO Latin-1</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N1039C" headers="N1007B "> <p>WINDOWS-1255</p> - </th> - -<td valign="top" headers="N1039C N1008D "> <p>Hebrew</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N103BC" headers="N1007B "> <p>WINDOWS-1256</p> - </th> - -<td valign="top" headers="N103BC N1008D "> <p>Arabic</p> - </td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N103DC" headers="N1007B ">X-EUC-JP</th> - -<td valign="top" headers="N103DC N1008D ">EUC encoding, Japanese (alias for EUC-JP)</td> - -</tr> - -<tr> -<th valign="top" class="firstcol" id="N103F0" headers="N1007B ">X-SJIS</th> - -<td valign="top" headers="N103F0 N1008D ">Shift-JIS, Japanese (alias for SHIFT_JIS)</td> - -</tr> - -</tbody> - -</table> -</div> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.dita deleted file mode 100644 index dbfc5b2589..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.dita +++ /dev/null @@ -1,38 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="cxmltool" xml:lang="en-us">
-<title>XML tools - overview</title>
-<titlealts>
-<searchtitle>XML tools - overview</searchtitle>
-</titlealts>
-<shortdesc>This product provides a comprehensive visual XML development environment.
-The tool set includes components for building DTDs, XML schemas, and XML files.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML tools<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>The following XML tools are available. </p>
-<p>The <b>XML editor</b> is a tool for creating and viewing XML files. You
-can use it to create new XML files, either from scratch, existing DTDs, or
-existing XML schemas. You can also use it to edit XML files, associate them
-with DTDs or schemas, and validate them. </p>
-<p> The <b>DTD editor</b> is a tool for creating and viewing DTDs. </p>
-<p>The <b>XML schema editor</b> is a tool for creating, viewing, and validating
-XML schemas. You can use the XML schema editor to perform tasks such as creating
-XML schema components and importing and viewing XML schemas. </p>
-<p><b>Notes:</b></p>
-<section>Exercise caution when opening large files with any of the XML editors.
-If the memory limits of the workbench are exceeded, it will abruptly close
-without saving any data (and without warning or error messages). The number
-of elements in an XML file, not its size, is the best indicator of how much
-memory will be required. Memory requirements also depend on what else is open
-in the workbench - in some cases you can open a fifteen megabytes file, but
-in other cases a one megabyte file might cause problems. Therefore, we recommend
-you save all data in the workbench before opening large XML files. This is
-a permanent restriction.</section>
-<section conref="rlimitations_slushXML.dita#rlimitations_slushXML/unresolv_URI"></section>
-</conbody>
-</concept>
-<?Pub *0000002064?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html deleted file mode 100644 index 76696338e6..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/cxmltool.html +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>XML tools - overview</title> -</head> -<body id="cxmltool"><a name="cxmltool"><!-- --></a> - -<h1 class="topictitle1">XML tools - overview</h1> -<div><p>This product provides a comprehensive visual XML development environment. -The tool set includes components for building DTDs, XML schemas, and XML files.</p><p>The following XML tools are available:</p> -<p>The <b>XML editor</b> is a tool for creating and viewing XML files. You -can use it to create new XML files, either from scratch, existing DTDs, or -existing XML schemas. You can also use it to edit XML files, associate them -with DTDs or schemas, and validate them.</p> -<p>The <b>DTD editor</b> is a tool for creating and viewing DTDs. </p> -<p>The <b>XML schema editor</b> is a tool for creating, viewing, and validating -XML schemas. You can use the XML schema editor to perform tasks such as creating -XML schema components and importing and viewing XML schemas. </p> -<div class="skipspace">Exercise caution when opening large files with any of the XML editors. -If the memory limits of the workbench are exceeded, it will abruptly close -without saving any data (and without warning or error messages). The number -of elements in an XML file, not its size, is the best indicator of how much -memory will be required. Memory requirements also depend on what else is open -in the workbench - in some cases you can open a 15 megabytes file, but in -other cases a one-megabyte file may cause problems. Therefore, we recommend -you save all data in the workbench before opening large XML files. This is -a permanent restriction.</div> -<div class="skipspace"><p>The -behavior of the XML parser when encountering an unresolvable URI (for example, -in a DOCTYPE declaration) is to report a fatal IO error and stop any further -processing. An unresolved URI is seen neither as a syntactic nor a semantic -error and as such, the parser does not attempt to handle it. Essentially, -the document remains unchecked. This is a known problem.</p> -</div> -</div> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.dita deleted file mode 100644 index b2be71435d..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.dita +++ /dev/null @@ -1,25 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rextctn" xml:lang="en-us">
-<title>Editing XML documents with multiple namespaces</title>
-<titlealts>
-<searchtitle>Editing XML documents with multiple namespaces</searchtitle>
-</titlealts>
-<shortdesc>You can use the XML schema <codeph>any</codeph> element to extend
-the content model of an XML document.</shortdesc>
-<refbody>
-<section><p>For example, you have an XML schema file called Book.xsd that
-contains a complex type called BookType. BookType contains 4 elements (title,
-author, year, and ISBN) and one <codeph>any</codeph> element. The namespace
-for the <codeph>any</codeph> element is <codeph>##any</codeph>. This means
-that in an instance document, you can insert any XML element to extend the
-definition of the BookType.</p><p>You can also provide a more specific namespace.
-For example, you have another schema called My_Book.xsd, which contains a
-complex type called My_BookType. My_BookType contains 4 elements (title, author,
-year, and ISBN) and one <codeph>any</codeph> element, but in this case the
-namespace for the BookType element is www.wesley.com. This means that in
-an instance document, you can insert any XML element to extend the definition
-of the BookType, provided that they belong to the namespace http://www.wesley.com.</p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html deleted file mode 100644 index ee9086b236..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rextctn.html +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML documents with multiple namespaces" /> -<meta name="abstract" content="You can use the XML schema any element to extend the content model of an XML document." /> -<meta name="description" content="You can use the XML schema any element to extend the content model of an XML document." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rextctn" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML documents with multiple namespaces</title> -</head> -<body id="rextctn"><a name="rextctn"><!-- --></a> - - -<h1 class="topictitle1">Editing XML documents with multiple namespaces</h1> - - - -<div><p>You can use the XML schema <samp class="codeph">any</samp> element to extend -the content model of an XML document.</p> - -<div class="section"><p>For example, you have an XML schema file called Book.xsd that -contains a complex type called BookType. BookType contains 4 elements (title, -author, year, and ISBN) and one <samp class="codeph">any</samp> element. The namespace -for the <samp class="codeph">any</samp> element is <samp class="codeph">##any</samp>. This means -that in an instance document, you can insert any XML element to extend the -definition of the BookType.</p> -<p>You can also provide a more specific namespace. -For example, you have another schema called My_Book.xsd, which contains a -complex type called My_BookType. My_BookType contains 4 elements (title, author, -year, and ISBN) and one <samp class="codeph">any</samp> element, but in this case the -namespace for the BookType element is www.wesley.com. This means that in -an instance document, you can insert any XML element to extend the definition -of the BookType, provided that they belong to the namespace http://www.wesley.com.</p> -</div> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.dita deleted file mode 100644 index c7ee4b0777..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.dita +++ /dev/null @@ -1,19 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rlimitations_slushXML" xml:lang="en-us">
-<title>Limitations of XML Editor</title>
-<titlealts>
-<searchtitle>Limitations of XML Editor</searchtitle>
-</titlealts>
-<shortdesc>This section describes known product aspect limitations and workarounds.</shortdesc>
-<refbody>
-<!--Use this template to single source the readme information. The content for the readme information is maintained in this topic and is inserted into the related topic using the conref attribute. This file will not be surfaced in your navigation.-->
-<section id="unresolv_URI"><!--No defect associated with this. It is from the 5.1. readme.--><p>The
-behavior of the XML parser when encountering an unresolvable URI (for example,
-in a DOCTYPE declaration) is to report a fatal IO error and stop any further
-processing. An unresolved URI is seen neither as a syntactic nor a semantic
-error and as such, the parser does not attempt to handle it. Essentially,
-the document remains unchecked. This is a known problem.</p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html deleted file mode 100644 index dfece6aae6..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rlimitations_slushXML.html +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Limitations of XML Editor" /> -<meta name="abstract" content="This section describes known product aspect limitations and workarounds." /> -<meta name="description" content="This section describes known product aspect limitations and workarounds." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rlimitations_slushXML" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Limitations of XML Editor</title> -</head> -<body id="rlimitations_slushXML"><a name="rlimitations_slushXML"><!-- --></a> - - -<h1 class="topictitle1">Limitations of XML Editor</h1> - - - -<div><p>This section describes known product aspect limitations and workarounds.</p> - - -<div class="section" id="rlimitations_slushXML__unresolv_URI"><a name="rlimitations_slushXML__unresolv_URI"><!-- --></a><p>The -behavior of the XML parser when encountering an unresolvable URI (for example, -in a DOCTYPE declaration) is to report a fatal IO error and stop any further -processing. An unresolved URI is seen neither as a syntactic nor a semantic -error and as such, the parser does not attempt to handle it. Essentially, -the document remains unchecked. This is a known problem.</p> -</div> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.dita deleted file mode 100644 index a398b072db..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.dita +++ /dev/null @@ -1,58 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<?Pub Inc?>
-<reference id="ricons" xml:lang="en-us">
-<title>Icons used in the XML editor</title>
-<titlealts>
-<searchtitle>Icons used in the XML editor</searchtitle>
-</titlealts>
-<shortdesc>The following XML editor icons appear in the Outline and Design
-view.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>icons</indexterm></indexterm></keywords>
-</metadata></prolog>
-<refbody>
-<table>
-<tgroup cols="2"><colspec colname="COLSPEC0"/><colspec colname="COLSPEC1"/>
-<tbody>
-<row>
-<entry colname="COLSPEC0" valign="bottom"><b>Icon</b></entry>
-<entry colname="COLSPEC1" valign="bottom"><b>Description</b></entry>
-</row>
-<row>
-<entry> <image href="../images/nattrib.gif"><alt>This graphic is the attribute
-icon</alt></image> </entry>
-<entry>attribute</entry>
-</row>
-<row>
-<entry> <image href="../images/cdatasection.gif"><alt>This graphic is the
-character data icon</alt></image></entry>
-<entry>character data (CDATA) section</entry>
-</row>
-<row>
-<entry> <image href="../images/comment_obj.gif"><alt>This graphic is the comment
-icon</alt></image></entry>
-<entry>comment</entry>
-</row>
-<row>
-<entry> <image href="../images/doctype.gif"><alt>This graphic is the DOCTYPE
-icon</alt></image></entry>
-<entry>DOCTYPE declaration</entry>
-</row>
-<row>
-<entry> <image href="../images/nelem.gif"><alt>This graphic is the element
-icon</alt></image> </entry>
-<entry>element</entry>
-</row>
-<row>
-<entry> <image href="../images/proinst_obj.gif"><alt>This graphic is the processing
-instructions icon</alt></image></entry>
-<entry>processing instructions</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-</refbody>
-</reference>
-<?Pub *0000001824?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html deleted file mode 100644 index 50087a8307..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/rxmlbicons.html +++ /dev/null @@ -1,99 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Icons used in the XML editor" /> -<meta name="abstract" content="The following XML editor icons appear in the Outline and Design view." /> -<meta name="description" content="The following XML editor icons appear in the Outline and Design view." /> -<meta content="XML editor, icons" name="DC.subject" /> -<meta content="XML editor, icons" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ricons" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Icons used in the XML editor</title> -</head> -<body id="ricons"><a name="ricons"><!-- --></a> - - -<h1 class="topictitle1">Icons used in the XML editor</h1> - - - - -<div><p>The following XML editor icons appear in the Outline and Design -view.</p> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<tbody> -<tr> -<td valign="bottom"><strong>Icon</strong></td> - -<td valign="bottom"><strong>Description</strong></td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/nattrib.gif" alt="This graphic is the attribute icon" /> </td> - -<td valign="top">attribute</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/cdatasection.gif" alt="This graphic is the character data icon" /></td> - -<td valign="top">character data (CDATA) section</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/comment_obj.gif" alt="This graphic is the comment icon" /></td> - -<td valign="top">comment</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/doctype.gif" alt="This graphic is the DOCTYPE icon" /></td> - -<td valign="top">DOCTYPE declaration</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/nelem.gif" alt="This graphic is the element icon" /> </td> - -<td valign="top">element</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/proinst_obj.gif" alt="This graphic is the processing instructions icon" /></td> - -<td valign="top">processing instructions</td> - -</tr> - -</tbody> - -</table> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.dita deleted file mode 100644 index ad0b19e1e3..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.dita +++ /dev/null @@ -1,39 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tcretxml" xml:lang="en-us">
-<title>Creating XML files</title>
-<titlealts>
-<searchtitle>Creating XML files</searchtitle>
-</titlealts>
-<shortdesc>You can create a new XML file which you can then edit in the XML
-editor. You create a new XML file that is not associated with a DTD or XML
-schema file, so there are no restrictions on the kind of content it can contain.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To create a new
-XML file, follow these instructions:</p></context>
-<steps>
-<step><cmd>If necessary, create a project to contain the XML file.</cmd></step>
-<step><cmd>In the workbench, click <menucascade><uicontrol>File</uicontrol>
-<uicontrol>New</uicontrol><uicontrol>Other</uicontrol><uicontrol>XML</uicontrol>
-<uicontrol>XML</uicontrol></menucascade> and click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the project or folder that will contain the XML file.</cmd>
-</step>
-<step><cmd>In the <uicontrol>File name</uicontrol> field, type the name of
-the XML file, for example <userinput>MyXMLFile.xml</userinput>. The name of
-your XML file <varname>must</varname> end in <userinput>.xml</userinput>.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Next.</uicontrol></cmd></step>
-<step><cmd>Click the <uicontrol>Create XML file from an XML template</uicontrol> radio
-button.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html deleted file mode 100644 index 63438a9c9a..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcretxml.html +++ /dev/null @@ -1,82 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating XML files" /> -<meta name="abstract" content="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain." /> -<meta name="description" content="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain." /> -<meta content="XML files, creating" name="DC.subject" /> -<meta content="XML files, creating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexxsd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcretxml" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating XML files</title> -</head> -<body id="tcretxml"><a name="tcretxml"><!-- --></a> - - -<h1 class="topictitle1">Creating XML files</h1> - - - - -<div><p>You can create a new XML file which you can then edit in the XML -editor. You create a new XML file that is not associated with a DTD or XML -schema file, so there are no restrictions on the kind of content it can contain.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To create a new -XML file, follow these instructions:</p> -</div> - -<ol> -<li><span>If necessary, create a project to contain the XML file.</span></li> - -<li><span>In the workbench, click <span class="menucascade"><span class="uicontrol">File</span> - > <span class="uicontrol">New</span> > <span class="uicontrol">Other</span> > <span class="uicontrol">XML</span> - > <span class="uicontrol">XML</span></span> and click <span class="uicontrol">Next</span>.</span> -</li> - -<li><span>Select the project or folder that will contain the XML file.</span> -</li> - -<li><span>In the <span class="uicontrol">File name</span> field, type the name of -the XML file, for example <kbd class="userinput">MyXMLFile.xml</kbd>. The name of -your XML file <var class="varname">must</var> end in <kbd class="userinput">.xml</kbd>.</span> -</li> - -<li><span>Click <span class="uicontrol">Next.</span></span></li> - -<li><span>Click the <span class="uicontrol">Create XML file from an XML template</span> radio -button.</span></li> - -<li><span>Click <span class="uicontrol">Finish</span>.</span></li> - -</ol> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from DTDs</a></div> -<div><a href="../topics/tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML schemas</a></div> -<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.dita deleted file mode 100644 index fe8a065d5e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.dita +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tcrexdtd" xml:lang="en-us">
-<title>Generating XML files from DTDs</title>
-<titlealts>
-<searchtitle>Generate an XML file from a DTD</searchtitle>
-</titlealts>
-<shortdesc>You can generate an XML file from your DTD if you want to quickly
-create an XML file based on your DTD file. Generating an XML file from your
-DTD saves you time by creating an XML file that is already associated with
-your DTD, and contains at least some of the elements and attributes in your
-DTD.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>generating from DTDs</indexterm></indexterm>
-<indexterm>DTD<indexterm>generating XML files</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>After you have generated your XML file, you can further customize
-it in the XML editor.</p><p>The following instructions were written for the
-Resource perspective, but they will also work in many other perspectives.</p><p>To
-create an XML file from a DTD file follow these steps:</p></context>
-<steps>
-<step><cmd>In the Navigator view, right-click the DTD file that you want to
-work with.</cmd></step>
-<step><cmd>From its pop-up menu click <menucascade><uicontrol>Generate</uicontrol>
-<uicontrol>XML File</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Select a project or folder to contain the XML file and type a name
-for it.</cmd><info>The name of the file must end in <userinput>.xml</userinput>.</info>
-</step>
-<step><cmd>Click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Select the <uicontrol>Root element</uicontrol> of the XML file.</cmd>
-<info>The root element of an XML file is the element that contains all other
-elements in that file. All the elements that you have defined in the DTD will
-be shown in the <uicontrol>Root element</uicontrol> list.</info></step>
-<step><cmd>Select from the following content options: </cmd>
-<choices>
-<choice><uicontrol>Create optional attributes</uicontrol>. Both mandatory
-and optional attributes will be generated.</choice>
-<choice><uicontrol>Create optional elements</uicontrol>. Both mandatory and
-optional elements will be generated.</choice>
-<choice><uicontrol>Create first choice of required choice</uicontrol>. The
-first option of a required choice will be generated in your XML file.</choice>
-<choice><uicontrol>Fill elements and attributes with data</uicontrol>. Any
-elements and attributes generated will be filled with sample data.</choice>
-</choices>
-<info> <p>If you do not select any of these options, then only the minimum
-amount of content required for the XML file will be created.</p></info></step>
-<step><cmd>Specify the <uicontrol>Public ID</uicontrol> or <uicontrol>System
-ID</uicontrol>.</cmd><info>You do not need to specify both. If you do, the
-Public ID will be used before the System ID. </info></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<result><p>The XML file will only contain the selected root element and any
-elements or attributes contained in the root element. You can now add elements,
-attributes, entities, and notations to the XML file, however, they must follow
-the rules established in the DTD that you used to create the XML file.</p></result>
-</taskbody>
-</task>
-<?Pub *0000003334?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html deleted file mode 100644 index f4c76ce0bb..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexdtd.html +++ /dev/null @@ -1,113 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Generating XML files from DTDs" /> -<meta name="abstract" content="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD." /> -<meta name="description" content="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD." /> -<meta content="XML files, generating from DTDs" name="DC.subject" /> -<meta content="XML files, generating from DTDs" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretxml.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexxsd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcrexdtd" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Generate an XML file from a DTD</title> -</head> -<body id="tcrexdtd"><a name="tcrexdtd"><!-- --></a> - - -<h1 class="topictitle1">Generating XML files from DTDs</h1> - - - - -<div><p>You can generate an XML file from your DTD if you want to quickly -create an XML file based on your DTD file. Generating an XML file from your -DTD saves you time by creating an XML file that is already associated with -your DTD, and contains at least some of the elements and attributes in your -DTD.</p> - -<div class="section"><p>After you have generated your XML file, you can further customize -it in the XML editor.</p> -<p>The following instructions were written for the -Resource perspective, but they will also work in many other perspectives.</p> -<p>To -create an XML file from a DTD file follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Navigator view, right-click the DTD file that you want to -work with.</span></li> - -<li class="stepexpand"><span>From its pop-up menu click <span class="menucascade"><span class="uicontrol">Generate</span> - > <span class="uicontrol">XML File</span></span>.</span></li> - -<li class="stepexpand"><span>Select a project or folder to contain the XML file and type a name -for it.</span> The name of the file must end in <kbd class="userinput">.xml</kbd>. -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>Select the <span class="uicontrol">Root element</span> of the XML file.</span> - The root element of an XML file is the element that contains all other -elements in that file. All the elements that you have defined in the DTD will -be shown in the <span class="uicontrol">Root element</span> list.</li> - -<li class="stepexpand"><span>Select from the following content options: </span> -<ul> -<li><span class="uicontrol">Create optional attributes</span>. Both mandatory -and optional attributes will be generated.</li> - -<li><span class="uicontrol">Create optional elements</span>. Both mandatory and -optional elements will be generated.</li> - -<li><span class="uicontrol">Create first choice of required choice</span>. The -first option of a required choice will be generated in your XML file.</li> - -<li><span class="uicontrol">Fill elements and attributes with data</span>. Any -elements and attributes generated will be filled with sample data.</li> - -</ul> - - <p>If you do not select any of these options, then only the minimum -amount of content required for the XML file will be created.</p> -</li> - -<li class="stepexpand"><span>Specify the <span class="uicontrol">Public ID</span> or <span class="uicontrol">System -ID</span>.</span> You do not need to specify both. If you do, the -Public ID will be used before the System ID. </li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> - -</ol> - -<div class="section"><p>The XML file will only contain the selected root element and any -elements or attributes contained in the root element. You can now add elements, -attributes, entities, and notations to the XML file, however, they must follow -the rules established in the DTD that you used to create the XML file.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcretxml.html" title="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating XML files</a></div> -<div><a href="../topics/tcrexxsd.html" title="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema.">Generating XML files from XML schemas</a></div> -<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.dita deleted file mode 100644 index 20df2b6ea4..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.dita +++ /dev/null @@ -1,85 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<?Pub Inc?>
-<task id="tcrexxsd" xml:lang="en-us">
-<title>Generating XML files from XML schemas</title>
-<titlealts>
-<searchtitle>Generating an XML file from an XML schema</searchtitle>
-</titlealts>
-<shortdesc>You can generate an XML file from your XML schema if you want to
-quickly create an XML file based on your XML schema file. Generating an XML
-file from your XML schema saves you time by creating an XML file that is already
-associated with your XML schema, and contains at least some of the elements
-and attributes in your XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>generating from XML schemas</indexterm></indexterm>
-<indexterm>XML schemas<indexterm>generating XML files</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>After you have generated your XML file, you can further customize
-it in the XML editor.</p><p>The following instructions were written for the
-Resource perspective, but they will also work in many other perspectives.</p><p>To
-generate an XML file from a schema file follow these steps:</p></context>
-<steps>
-<step><cmd>In the Navigator view, right-click the XML schema file that you
-want to work with.</cmd></step>
-<step><cmd>From its pop-up menu click <menucascade><uicontrol>Generate</uicontrol>
-<uicontrol>XML File</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Select a project or folder to contain the XML file, type a name
-for it and click <uicontrol>Next</uicontrol>.</cmd><info>The name of the file
-must end in<systemoutput>.xml.</systemoutput> </info></step>
-<step><cmd>Click the <uicontrol>Root element</uicontrol> of the XML file.</cmd>
-<info>The root element of an XML file is the element that contains all other
-elements in that file. All of the global elements you have defined in the
-XML schema will be included in the Root element list. If you do not have any
-global elements in your XML schema, you cannot create an XML file from it.</info>
-</step>
-<step><cmd>Select from the following content options:</cmd>
-<choices>
-<choice><uicontrol>Create optional attributes</uicontrol>. Both mandatory
-and optional attributes will be generated.</choice>
-<choice><uicontrol>Create optional elements</uicontrol>. Both mandatory and
-optional elements will be generated.</choice>
-<choice><uicontrol>Create first choice of required choice</uicontrol>. The
-first option of a required choice will be generated in your XML file.</choice>
-<choice><uicontrol>Fill elements and attributes with data</uicontrol>. Any
-elements and attributes generated will be filled with sample data.</choice>
-</choices>
-<info>If you do not select any of these options, then only the minimum amount
-of content required for the XML file will be created.</info></step>
-<step><cmd>The Namespace information section contains information about the
-target namespace of the XML schema, its prefix, and the schema location.</cmd>
-<info>For more information about namespaces and namespace prefixes, refer
-to the related references.</info></step>
-<step><cmd>Select the entry you want to edit and click <uicontrol>Edit</uicontrol>.</cmd>
-</step>
-<step><cmd>The value in the <uicontrol>Namespace Name</uicontrol> field is
-the target namespace of the XML schema.</cmd><info>Your XML file should be
-associated with the same namespace as its XML schema is associated with.</info>
-</step>
-<step><cmd>All qualified elements and attributes in the XML file associated
-with the namespace will be prefixed with the <uicontrol>Prefix</uicontrol> value.</cmd>
-</step>
-<step><cmd>The <uicontrol>Location Hint</uicontrol> field contains the location
-of the XML schema.</cmd></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>, then <uicontrol>Finish</uicontrol>.</cmd>
-</step>
-</steps>
-<result><p>The XML file will contain the selected root element and any elements
-or attributes contained in the root element. It also contains information
-about the XML file namespace and location. You can now add elements and attributes
-to the XML file.</p><p><b>Note:</b> In certain cases, when an XML file is
-generated from a complex XML schema file, the XML file might not be valid.
-If this occurs, you can open the generated file in the XML editor and correct
-any errors that occur. Usually, only a few errors need to be fixed. The following
-XML schema constructs might present problems:</p><ol>
-<li>Restrictions. Sometimes restricted elements are erroneously generated. </li>
-<li>Facets: Default generated data values might not conform to complex facets
-(for example, patterns).</li>
-<li>Abstract elements. abstract elements are sometimes erroneously generated.</li>
-</ol></result>
-</taskbody>
-</task>
-<?Pub *0000004757?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html deleted file mode 100644 index 0d32765702..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tcrexxsd.html +++ /dev/null @@ -1,147 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Generating XML files from XML schemas" /> -<meta name="abstract" content="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema." /> -<meta name="description" content="You can generate an XML file from your XML schema if you want to quickly create an XML file based on your XML schema file. Generating an XML file from your XML schema saves you time by creating an XML file that is already associated with your XML schema, and contains at least some of the elements and attributes in your XML schema." /> -<meta content="XML files, generating from XML schemas" name="DC.subject" /> -<meta content="XML files, generating from XML schemas" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcretxml.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcrexdtd.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedttag.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcrexxsd" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Generating an XML file from an XML schema</title> -</head> -<body id="tcrexxsd"><a name="tcrexxsd"><!-- --></a> - - -<h1 class="topictitle1">Generating XML files from XML schemas</h1> - - - - -<div><p>You can generate an XML file from your XML schema if you want to -quickly create an XML file based on your XML schema file. Generating an XML -file from your XML schema saves you time by creating an XML file that is already -associated with your XML schema, and contains at least some of the elements -and attributes in your XML schema.</p> - -<div class="section"><p>After you have generated your XML file, you can further customize -it in the XML editor.</p> -<p>The following instructions were written for the -Resource perspective, but they will also work in many other perspectives.</p> -<p>To -generate an XML file from a schema file follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Navigator view, right-click the XML schema file that you -want to work with.</span></li> - -<li class="stepexpand"><span>From its pop-up menu click <span class="menucascade"><span class="uicontrol">Generate</span> - > <span class="uicontrol">XML File</span></span>.</span></li> - -<li class="stepexpand"><span>Select a project or folder to contain the XML file, type a name -for it and click <span class="uicontrol">Next</span>.</span> The name of the file -must end in<tt class="sysout">.xml.</tt> </li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Root element</span> of the XML file.</span> - The root element of an XML file is the element that contains all other -elements in that file. All of the global elements you have defined in the -XML schema will be included in the Root element list. If you do not have any -global elements in your XML schema, you cannot create an XML file from it. -</li> - -<li class="stepexpand"><span>Select from the following content options:</span> -<ul> -<li><span class="uicontrol">Create optional attributes</span>. Both mandatory -and optional attributes will be generated.</li> - -<li><span class="uicontrol">Create optional elements</span>. Both mandatory and -optional elements will be generated.</li> - -<li><span class="uicontrol">Create first choice of required choice</span>. The -first option of a required choice will be generated in your XML file.</li> - -<li><span class="uicontrol">Fill elements and attributes with data</span>. Any -elements and attributes generated will be filled with sample data.</li> - -</ul> - - If you do not select any of these options, then only the minimum amount -of content required for the XML file will be created.</li> - -<li class="stepexpand"><span>The Namespace information section contains information about the -target namespace of the XML schema, its prefix, and the schema location.</span> - For more information about namespaces and namespace prefixes, refer -to the related references.</li> - -<li class="stepexpand"><span>Select the entry you want to edit and click <span class="uicontrol">Edit</span>.</span> -</li> - -<li class="stepexpand"><span>The value in the <span class="uicontrol">Namespace Name</span> field is -the target namespace of the XML schema.</span> Your XML file should be -associated with the same namespace as its XML schema is associated with. -</li> - -<li class="stepexpand"><span>All qualified elements and attributes in the XML file associated -with the namespace will be prefixed with the <span class="uicontrol">Prefix</span> value.</span> -</li> - -<li class="stepexpand"><span>The <span class="uicontrol">Location Hint</span> field contains the location -of the XML schema.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>, then <span class="uicontrol">Finish</span>.</span> -</li> - -</ol> - -<div class="section"><p>The XML file will contain the selected root element and any elements -or attributes contained in the root element. It also contains information -about the XML file namespace and location. You can now add elements and attributes -to the XML file.</p> -<p><strong>Note:</strong> In certain cases, when an XML file is -generated from a complex XML schema file, the XML file might not be valid. -If this occurs, you can open the generated file in the XML editor and correct -any errors that occur. Usually, only a few errors need to be fixed. The following -XML schema constructs might present problems:</p> -<ol> -<li>Restrictions. Sometimes restricted elements are erroneously generated. </li> - -<li>Facets: Default generated data values might not conform to complex facets -(for example, patterns).</li> - -<li>Abstract elements. abstract elements are sometimes erroneously generated.</li> - -</ol> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcretxml.html" title="You can create a new XML file which you can then edit in the XML editor. You create a new XML file that is not associated with a DTD or XML schema file, so there are no restrictions on the kind of content it can contain.">Creating XML files</a></div> -<div><a href="../topics/tcrexdtd.html" title="You can generate an XML file from your DTD if you want to quickly create an XML file based on your DTD file. Generating an XML file from your DTD saves you time by creating an XML file that is already associated with your DTD, and contains at least some of the elements and attributes in your DTD.">Generating XML files from DTDs</a></div> -<div><a href="../topics/txedttag.html" title="This file contains information about editing XML files.">Editing XML files</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita deleted file mode 100644 index 63f1b5c77d..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.dita +++ /dev/null @@ -1,62 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtcnst" xml:lang="en-us">
-<title>Editing with DTD or XML schema constraints</title>
-<titlealts>
-<searchtitle>Editing with DTD or XML schema constraints</searchtitle>
-</titlealts>
-<shortdesc>In the Design view, when you edit an XML file that has a set of
-constraints (that is, a set of rules) defined by a DTD or an XML schema, you
-can turn the constraints on and off to provide flexibility in the way you
-edit, but still maintain the validity of the document periodically.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>editing with constraints</indexterm></indexterm>
-<indexterm>XML files<indexterm>editing with constraints</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> When the constraints are turned on, and you are working in the
-Design view, the XML editor prevents you from inserting elements, attributes,
-or attribute values not permitted by the rules of the XML schema or DTD, and
-from removing necessary or predefined sets of tags and values. In this mode,
-an element's content must be valid to use the XML editor's guided editing
-options.</p><p>You might want to turn the constraints off for an XML file
-if you need more flexibility. For example, you want to try working with elements
-or attributes not permitted by the associated DTD or XML schema, without actually
-removing the association with the DTD or XML schema.</p><p>To turn the constraints
-for an XML file off, click <uicontrol>XML > Turn Grammar Constraints Off</uicontrol>.
-After you have turned the constraints off for a file, you can insert or delete
-any element or attribute regardless of the DTD or XML schema rules. You can
-create new elements or attributes that are not in the DTD or schema - these
-Design view prompts will only appear when you have turned constraints off.
-The file might not be valid, however, if you do this. </p><p>The following
-instructions were written for the Resource perspective, but they will also
-work in many other perspectives.</p><p>The following example shows what you
-can do if you turn the constraints of a DTD off:</p></context>
-<steps>
-<step><cmd>Open the XML file in the XML editor (right-click the file in the
-Navigator view and click <uicontrol>Open With > XML Editor</uicontrol>). </cmd>
-</step>
-<step><cmd>You have a DTD that specifies that an element requires at least
-one of a specific child element: </cmd><info><codeblock><!ELEMENT parentElement (childElement+)>
-</codeblock></info></step>
-<step><cmd>If, in an XML file associated with your DTD, you attempt to remove
-the final child element of the element with the DTD constraints turned on,
-the editor will not allow you to do this, as it will make the document invalid.</cmd>
-<info>You can confirm this by using the element's pop-up menu to verify that
-the <uicontrol>Remove</uicontrol> option is grayed out.</info></step>
-<step><cmd>To turn the DTD constraints off, click <uicontrol>XML > Turn Grammar
-Constraints Off</uicontrol>. </cmd></step>
-<step><cmd>If you attempt to remove the same child element with constraints
-off, the editor will allow you to.</cmd></step>
-<step><cmd>To correct the invalid document, you will have to re-add the necessary
-element, or remove the invalid tagging or value.</cmd></step>
-</steps>
-<result>If you introduce errors into your files, you must save and validate
-the file in order to see a list of the errors you have introduced. They will
-be listed in the Problems view. After you fix the errors, you must save and
-validate your file again to see if the file is now valid.</result>
-</taskbody>
-</task>
-<?Pub *0000003854?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html deleted file mode 100644 index ab8acd73dd..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtcnst.html +++ /dev/null @@ -1,113 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing with DTD or XML schema constraints" /> -<meta name="abstract" content="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically." /> -<meta name="description" content="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically." /> -<meta content="XML editor, editing, with DTD or XML schema constraints, XML files, with DTD or XML schema constraints" name="DC.subject" /> -<meta content="XML editor, editing, with DTD or XML schema constraints, XML files, with DTD or XML schema constraints" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtcnst" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing with DTD or XML schema constraints</title> -</head> -<body id="tedtcnst"><a name="tedtcnst"><!-- --></a> - - -<h1 class="topictitle1">Editing with DTD or XML schema constraints</h1> - - - - -<div><p>In the Design view, when you edit an XML file that has a set of -constraints (that is, a set of rules) defined by a DTD or an XML schema, you -can turn the constraints on and off to provide flexibility in the way you -edit, but still maintain the validity of the document periodically.</p> - -<div class="section"><p> When the constraints are turned on, and you are working in the -Design view, the XML editor prevents you from inserting elements, attributes, -or attribute values not permitted by the rules of the XML schema or DTD, and -from removing necessary or predefined sets of tags and values. In this mode, -an element's content must be valid to use the XML editor's guided editing -options.</p> -<p>You might want to turn the constraints off for an XML file -if you need more flexibility. For example, you want to try working with elements -or attributes not permitted by the associated DTD or XML schema, without actually -removing the association with the DTD or XML schema.</p> -<p>To turn the constraints -for an XML file off, click <span class="uicontrol">XML > Turn Grammar Constraints Off</span>. -After you have turned the constraints off for a file, you can insert or delete -any element or attribute regardless of the DTD or XML schema rules. You can -create new elements or attributes that are not in the DTD or schema - these -Design view prompts will only appear when you have turned constraints off. -The file might not be valid, however, if you do this. </p> -<p>The following -instructions were written for the Resource perspective, but they will also -work in many other perspectives.</p> -<p>The following example shows what you -can do if you turn the constraints of a DTD off:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the XML file in the XML editor (right-click the file in the -Navigator view and click <span class="uicontrol">Open With > XML Editor</span>). </span> -</li> - -<li class="stepexpand"><span>You have a DTD that specifies that an element requires at least -one of a specific child element: </span> <pre><!ELEMENT parentElement (childElement+)> -</pre> -</li> - -<li class="stepexpand"><span>If, in an XML file associated with your DTD, you attempt to remove -the final child element of the element with the DTD constraints turned on, -the editor will not allow you to do this, as it will make the document invalid.</span> - You can confirm this by using the element's pop-up menu to verify that -the <span class="uicontrol">Remove</span> option is grayed out.</li> - -<li class="stepexpand"><span>To turn the DTD constraints off, click <span class="uicontrol">XML > Turn Grammar -Constraints Off</span>. </span></li> - -<li class="stepexpand"><span>If you attempt to remove the same child element with constraints -off, the editor will allow you to.</span></li> - -<li class="stepexpand"><span>To correct the invalid document, you will have to re-add the necessary -element, or remove the invalid tagging or value.</span></li> - -</ol> - -<div class="section">If you introduce errors into your files, you must save and validate -the file in order to see a list of the errors you have introduced. They will -be listed in the Problems view. After you fix the errors, you must save and -validate your file again to see if the file is now valid.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.dita deleted file mode 100644 index 5f5a6820c8..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtdoc" xml:lang="en-us">
-<title>Editing DOCTYPE declarations</title>
-<titlealts>
-<searchtitle>Editing DOCTYPE declarations</searchtitle>
-</titlealts>
-<shortdesc>The DOCTYPE declaration in an XML file is used at the beginning
-of it to associate it with a DTD file. You can edit your DOCTYPE declaration
-to change the DTD file your XML file is associated with.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>DOCTYPE declarations<indexterm>XML editor</indexterm></indexterm>
-<indexterm>XML editor<indexterm>DOCTYPE declarations</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To edit your DOCTYPE
-declaration, follow these steps:</p></context>
-<steps>
-<step><cmd>In the Design view of the XML editor, right-click <uicontrol>DOCTYPE</uicontrol> and
-click <uicontrol>Edit DOCTYPE</uicontrol>.</cmd></step>
-<step><cmd>The value in the <uicontrol>Root element name</uicontrol> field
-should match the root element of your XML file exactly.</cmd><info>You should
-only edit the value in this field if your root element changes.</info></step>
-<step><cmd>You can select a Public ID for any existing XML Catalog entries
-by clicking <uicontrol>Browse</uicontrol>. </cmd><info>The value in the <uicontrol>Public
-ID</uicontrol> field is the Public Identifier. It is used to associate the
-XML file (using an XML Catalog entry) with a DTD file. For more information
-on XML Catalog entries, refer to the related tasks.</info></step>
-<step><cmd>The value in the <uicontrol>System ID</uicontrol> field is the
-DTD the XML file is associated with. Type the path of the DTD file (or browse
-for it) you want the XML file associated with in this field. </cmd><info> <b>Note</b>:
-When the XML file is processed by the XML processor, it will first try to
-use the Public ID to locate the DTD, and if this fails, it will use the System
-ID to find it.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<postreq>If you do not have a DOCTYPE declaration in your XML file, you can
-right-click in the Design view and click <uicontrol>Add DTD Information</uicontrol> to
-add one.</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html deleted file mode 100644 index 4d877a3400..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtdoc.html +++ /dev/null @@ -1,88 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing DOCTYPE declarations" /> -<meta name="abstract" content="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with." /> -<meta name="description" content="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with." /> -<meta content="XML editor, editing, DOCTYPE declarations, XML files" name="DC.subject" /> -<meta content="XML editor, editing, DOCTYPE declarations, XML files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtdoc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing DOCTYPE declarations</title> -</head> -<body id="tedtdoc"><a name="tedtdoc"><!-- --></a> - - -<h1 class="topictitle1">Editing DOCTYPE declarations</h1> - - - - -<div><p>The DOCTYPE declaration in an XML file is used at the beginning -of it to associate it with a DTD file. You can edit your DOCTYPE declaration -to change the DTD file your XML file is associated with.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To edit your DOCTYPE -declaration, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view of the XML editor, right-click <span class="uicontrol">DOCTYPE</span> and -click <span class="uicontrol">Edit DOCTYPE</span>.</span></li> - -<li class="stepexpand"><span>The value in the <span class="uicontrol">Root element name</span> field -should match the root element of your XML file exactly.</span> You should -only edit the value in this field if your root element changes.</li> - -<li class="stepexpand"><span>You can select a Public ID for any existing XML Catalog entries -by clicking <span class="uicontrol">Browse</span>. </span> The value in the <span class="uicontrol">Public -ID</span> field is the Public Identifier. It is used to associate the -XML file (using an XML Catalog entry) with a DTD file. For more information -on XML Catalog entries, refer to the related tasks.</li> - -<li class="stepexpand"><span>The value in the <span class="uicontrol">System ID</span> field is the -DTD the XML file is associated with. Type the path of the DTD file (or browse -for it) you want the XML file associated with in this field. </span> <strong>Note</strong>: -When the XML file is processed by the XML processor, it will first try to -use the Public ID to locate the DTD, and if this fails, it will use the System -ID to find it.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -<div class="section">If you do not have a DOCTYPE declaration in your XML file, you can -right-click in the Design view and click <span class="uicontrol">Add DTD Information</span> to -add one.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.dita deleted file mode 100644 index 92ec6ed1fb..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.dita +++ /dev/null @@ -1,36 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtenc" xml:lang="en-us">
-<title>Specifying XML default encoding line delimiters</title>
-<titlealts>
-<searchtitle>Specifying line delimiters</searchtitle>
-</titlealts>
-<shortdesc>This page lets you specify the line delimiter and the text encoding
-that will be used when you create or save an XML related file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>specifying line delimiters</indexterm></indexterm>
-<indexterm>line delimiters<indexterm>XML files</indexterm></indexterm>
-</keywords>
-<keywords></keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To specify the line delimiter you want to use:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Files</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>In the <uicontrol>Line delimiter</uicontrol> list, select the operating
-system that applies to your development or deployment platform. </cmd></step>
-<step><cmd>From the <uicontrol>Encoding</uicontrol> field, specify
-the default character encoding set that is used when creating XML related
-files (DTDs, XML files, XML schemas). Changing the encoding causes any new,
-XML related files that are created from scratch to use the selected encoding.</cmd>
-</step>
-<step><cmd>Click <uicontrol>Apply</uicontrol>, then <uicontrol>OK</uicontrol>.</cmd>
-</step>
-</steps>
-<result></result>
-</taskbody>
-</task>
-<?Pub *0000001698?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html deleted file mode 100644 index 4f0cfd729c..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtenc.html +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Specifying XML default encoding line delimiters" /> -<meta name="abstract" content="This page lets you specify the line delimiter and the text encoding that will be used when you create or save an XML related file." /> -<meta name="description" content="This page lets you specify the line delimiter and the text encoding that will be used when you create or save an XML related file." /> -<meta content="XML files, specifying, line delimiters, encoding" name="DC.subject" /> -<meta content="XML files, specifying, line delimiters, encoding" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtenc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Specifying line delimiters</title> -</head> -<body id="tedtenc"><a name="tedtenc"><!-- --></a> - - -<h1 class="topictitle1">Specifying XML default encoding line delimiters</h1> - - - - -<div><p>This page lets you specify the line delimiter and the text encoding -that will be used when you create or save an XML related file.</p> - -<div class="section"><p>To specify the line delimiter you want to use:</p> -</div> - -<ol> -<li><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span></span>.</span> -</li> - -<li><span>In the <span class="uicontrol">Line delimiter</span> list, select the operating -system that applies to your development or deployment platform. </span></li> - -<li><span>From the <span class="uicontrol">Encoding</span> field, specify -the default character encoding set that is used when creating XML related -files (DTDs, XML files, XML schemas). Changing the encoding causes any new, -XML related files that are created from scratch to use the selected encoding.</span> -</li> - -<li><span>Click <span class="uicontrol">Apply</span>, then <span class="uicontrol">OK</span>.</span> -</li> - -</ol> - -<div class="section" /> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.dita deleted file mode 100644 index 83dc689aea..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtgram" xml:lang="en-us">
-<title>Updating XML files with changes made to DTDs and schemas</title>
-<titlealts>
-<searchtitle>Updating XML files with changes made to DTDs and schemas</searchtitle>
-</titlealts>
-<shortdesc>If you make changes to a DTD file or XML schema associated with
-an XML file (that is currently open), click <uicontrol>XML > Reload Dependencies</uicontrol> to
-update the XML file with these changes. The changes will be reflected in the
-guided editing mechanisms available in the editor, such as content assist.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>updating XML files</indexterm></indexterm>
-<indexterm>XML files<indexterm>updating with associated changes</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>For example, you have a DTD file called "Contact.dtd" and an XML
-file called "Contact.xml" associated with it. Contact.dtd contains a root
-element called <uicontrol>Contact</uicontrol> that can contain any of the
-following children elements: <uicontrol>Name</uicontrol>, <uicontrol>PostalAddress</uicontrol>,
- <uicontrol>Email</uicontrol>. If you remove the child element <uicontrol>Email</uicontrol> from
-the DTD, you will no longer be able to add an <uicontrol>Email</uicontrol> child
-element to your root element Contact in your Contact.xml file. This change,
-however, will not come into effect until you save your changes in the DTD
-and click <uicontrol>XML > Reload Dependencies</uicontrol> in the XML editor.
-Until you click it, you will still be able to add <uicontrol>Email</uicontrol> elements
-to Contact.xml.</p><p>This feature is very handy when you are making updates
-to both DTDs and XML schemas and XML files that are associated with DTDs and
-XML schemas.</p></context>
-</taskbody>
-</task>
-<?Pub *0000002040?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html deleted file mode 100644 index d1aba1d921..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtgram.html +++ /dev/null @@ -1,73 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Updating XML files with changes made to DTDs and schemas" /> -<meta name="abstract" content="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist." /> -<meta name="description" content="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist." /> -<meta content="XML editor, updating, XML files with associated changes, XML files, updating with associated changes" name="DC.subject" /> -<meta content="XML editor, updating, XML files with associated changes, XML files, updating with associated changes" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtgram" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Updating XML files with changes made to DTDs and schemas</title> -</head> -<body id="tedtgram"><a name="tedtgram"><!-- --></a> - - -<h1 class="topictitle1">Updating XML files with changes made to DTDs and schemas</h1> - - - - -<div><p>If you make changes to a DTD file or XML schema associated with -an XML file (that is currently open), click <span class="uicontrol">XML > Reload Dependencies</span> to -update the XML file with these changes. The changes will be reflected in the -guided editing mechanisms available in the editor, such as content assist.</p> - -<div class="section"><p>For example, you have a DTD file called "Contact.dtd" and an XML -file called "Contact.xml" associated with it. Contact.dtd contains a root -element called <span class="uicontrol">Contact</span> that can contain any of the -following children elements: <span class="uicontrol">Name</span>, <span class="uicontrol">PostalAddress</span>, - <span class="uicontrol">Email</span>. If you remove the child element <span class="uicontrol">Email</span> from -the DTD, you will no longer be able to add an <span class="uicontrol">Email</span> child -element to your root element Contact in your Contact.xml file. This change, -however, will not come into effect until you save your changes in the DTD -and click <span class="uicontrol">XML > Reload Dependencies</span> in the XML editor. -Until you click it, you will still be able to add <span class="uicontrol">Email</span> elements -to Contact.xml.</p> -<p>This feature is very handy when you are making updates -to both DTDs and XML schemas and XML files that are associated with DTDs and -XML schemas.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.dita deleted file mode 100644 index 0450ec76de..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtproc" xml:lang="en-us">
-<title>Editing XML processing instructions</title>
-<titlealts>
-<searchtitle>Editing XML processing instructions</searchtitle>
-</titlealts>
-<shortdesc>If you have instructions you want to pass along to an application
-using an XML document, you can use a processing instruction. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>processing instructions</indexterm></indexterm>
-<indexterm>XML files<indexterm>processing instructions</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To edit a processing
-instruction, follow these steps:</p></context>
-<steps>
-<step><cmd>In the Design view of the XML editor, right-click your processing
-instruction, and click <uicontrol>Edit Processing Instruction</uicontrol>.</cmd>
-</step>
-<step><cmd>The <uicontrol>Target</uicontrol> field is used to identify the
-application the instructions belongs to.</cmd></step>
-<step><cmd>The <uicontrol>Data</uicontrol> field contains the instructions.</cmd>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<postreq>To create a new processing instruction, right-click in the Design
-view, and click <uicontrol>Add Child</uicontrol>, <uicontrol>Add Before</uicontrol> or <uicontrol>Add
-After</uicontrol>, then click <uicontrol>Add Processing Instruction</uicontrol>.</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html deleted file mode 100644 index c00534aade..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtproc.html +++ /dev/null @@ -1,67 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML processing instructions" /> -<meta name="abstract" content="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction." /> -<meta name="description" content="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction." /> -<meta content="XML editor, editing, processing instructions, editing, XML files" name="DC.subject" /> -<meta content="XML editor, editing, processing instructions, editing, XML files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtproc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML processing instructions</title> -</head> -<body id="tedtproc"><a name="tedtproc"><!-- --></a> - - -<h1 class="topictitle1">Editing XML processing instructions</h1> - - - - -<div><p>If you have instructions you want to pass along to an application -using an XML document, you can use a processing instruction. </p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To edit a processing -instruction, follow these steps:</p> -</div> - -<ol> -<li><span>In the Design view of the XML editor, right-click your processing -instruction, and click <span class="uicontrol">Edit Processing Instruction</span>.</span> -</li> - -<li><span>The <span class="uicontrol">Target</span> field is used to identify the -application the instructions belongs to.</span></li> - -<li><span>The <span class="uicontrol">Data</span> field contains the instructions.</span> -</li> - -<li><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -<div class="section">To create a new processing instruction, right-click in the Design -view, and click <span class="uicontrol">Add Child</span>, <span class="uicontrol">Add Before</span> or <span class="uicontrol">Add -After</span>, then click <span class="uicontrol">Add Processing Instruction</span>.</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.dita deleted file mode 100644 index f016bfcb52..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.dita +++ /dev/null @@ -1,54 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtsch" xml:lang="en-us">
-<title>Editing namespace information</title>
-<titlealts>
-<searchtitle>Editing namespace information</searchtitle>
-</titlealts>
-<shortdesc>Your namespace information is used to provide various information
-about the XML file, such as the XML schema and namespace it is associated
-with. If desired, you can change the schema and namespace your XML file is
-associated with or add a new association. Modifying any associations can impact
-what content is allowed in the XML file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>namespace information</indexterm></indexterm>
-<indexterm>XML files<indexterm>namespace information</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To edit your schema
-information, follow these steps:</p></context>
-<steps>
-<step><cmd>In the Design view of the XML editor, right-click your root element
-and click <uicontrol>Edit Namespaces</uicontrol>.</cmd></step>
-<step><cmd>Your XML file can be associated with more than one namespace or
-schema.</cmd><info>Select the entry you want to edit and click <uicontrol>Edit</uicontrol>.</info>
-</step>
-<step><cmd>The value in the <uicontrol>Namespace Name</uicontrol> field is
-a namespace the XML file is associated with.</cmd><info>Your XML file should
-be associated with the same namespace(s) its XML schema is associated with.
-For more information about namespaces, refer to the related reference.</info>
-</step>
-<step><cmd>All qualified elements and attributes in the XML file associated
-with the namespace will be prefixed with the <uicontrol>Prefix</uicontrol> value.</cmd>
-</step>
-<step><cmd>The <uicontrol>Location Hint</uicontrol> field contains the location
-of the XML schema the XML file is associated with.</cmd><info>An XML Catalog
-Key or a namespace name can be specified in this field. Click <uicontrol>Browse</uicontrol> to
-view all XML schemas in the workbench and XML Catalog.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>, then click <uicontrol>OK</uicontrol> again.</cmd>
-</step>
-</steps>
-<result><p>If you want to create a new association, click <uicontrol>Add</uicontrol> instead
-of <uicontrol>Edit</uicontrol>. You can then either click the <uicontrol>Specify
-From Registered Namespace</uicontrol> radio button and select the namespace
-declarations you want to add or click the <uicontrol>Specify New Namespace</uicontrol> radio
-button and fill in the fields as necessary.</p></result>
-<postreq>If you do not have namespace information in your XML file, you can
-right-click your root element in the Design view and click <uicontrol>Edit
-Namespaces</uicontrol> to add it. If you do not have a root element, you must
-create one before you can add the namespace information.</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html deleted file mode 100644 index d26938188e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tedtsch.html +++ /dev/null @@ -1,105 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing namespace information" /> -<meta name="abstract" content="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file." /> -<meta name="description" content="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file." /> -<meta content="XML editor, editing, namespace information, XML files" name="DC.subject" /> -<meta content="XML editor, editing, namespace information, XML files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtsch" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing namespace information</title> -</head> -<body id="tedtsch"><a name="tedtsch"><!-- --></a> - - -<h1 class="topictitle1">Editing namespace information</h1> - - - - -<div><p>Your namespace information is used to provide various information -about the XML file, such as the XML schema and namespace it is associated -with. If desired, you can change the schema and namespace your XML file is -associated with or add a new association. Modifying any associations can impact -what content is allowed in the XML file.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To edit your schema -information, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view of the XML editor, right-click your root element -and click <span class="uicontrol">Edit Namespaces</span>.</span></li> - -<li class="stepexpand"><span>Your XML file can be associated with more than one namespace or -schema.</span> Select the entry you want to edit and click <span class="uicontrol">Edit</span>. -</li> - -<li class="stepexpand"><span>The value in the <span class="uicontrol">Namespace Name</span> field is -a namespace the XML file is associated with.</span> Your XML file should -be associated with the same namespace(s) its XML schema is associated with. -For more information about namespaces, refer to the related reference. -</li> - -<li class="stepexpand"><span>All qualified elements and attributes in the XML file associated -with the namespace will be prefixed with the <span class="uicontrol">Prefix</span> value.</span> -</li> - -<li class="stepexpand"><span>The <span class="uicontrol">Location Hint</span> field contains the location -of the XML schema the XML file is associated with.</span> An XML Catalog -Key or a namespace name can be specified in this field. Click <span class="uicontrol">Browse</span> to -view all XML schemas in the workbench and XML Catalog.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>, then click <span class="uicontrol">OK</span> again.</span> -</li> - -</ol> - -<div class="section"><p>If you want to create a new association, click <span class="uicontrol">Add</span> instead -of <span class="uicontrol">Edit</span>. You can then either click the <span class="uicontrol">Specify -From Registered Namespace</span> radio button and select the namespace -declarations you want to add or click the <span class="uicontrol">Specify New Namespace</span> radio -button and fill in the fields as necessary.</p> -</div> - -<div class="section">If you do not have namespace information in your XML file, you can -right-click your root element in the Design view and click <span class="uicontrol">Edit -Namespaces</span> to add it. If you do not have a root element, you must -create one before you can add the namespace information.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/txmlcat.html" title="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key">Adding entries to the XML Catalog</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.dita deleted file mode 100644 index 2f5d1b51e8..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="xmlsourcesuggestionstrategy" xml:lang="en-us">
-<title>Setting the XML source suggestion strategy used by content assist</title>
-<shortdesc>You can customize the formatting of the suggestions given by content
-assist by choosing a suggestion strategy preference. When the suggestion strategy
-is set to "Strict", suggestions that are 'strictly' grammatically valid will
-be displayed first in the list of options and highlighted by bold icons. Other
-suggestions that are applicable to this element's scope but are not grammatically
-valid, will be displayed lower in the list with de-emphasized icons. When
-the suggestion strategy is set to "Lax", all suggestions will displayed in
-the list with de-emphasized icons.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>source suggestion strategy</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>To set the suggestion strategy used by content assist:</context>
-<steps>
-<step><cmd>From the menu bar, Click <menucascade><uicontrol>Window</uicontrol>
-<uicontrol>Preferences</uicontrol></menucascade></cmd></step>
-<step><cmd>Select <menucascade><uicontrol>Web and XML</uicontrol><uicontrol>XML
-Files</uicontrol><uicontrol>XML Source</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Beside Suggestion strategy in the Content assist section, select
-the appropriate setting (for example, <uicontrol>Strict</uicontrol>).</cmd>
-</step>
-</steps>
-<example><p>The following screen capture demonstrates content assist with
-the suggestion strategy set to "Strict":</p><image href="../images/suggestion.gif"
-placement="break"><alt>Example of Strict Suggestion Strategy</alt></image></example>
-</taskbody>
-</task>
-<?Pub *0000001917?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.html deleted file mode 100644 index 274ff98f5e..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/tsugstrat.html +++ /dev/null @@ -1,66 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting the XML source suggestion strategy used by content assist" /> -<meta name="abstract" content="You can customize the formatting of the suggestions given by content assist by choosing a suggestion strategy preference. When the suggestion strategy is set to "Strict", suggestions that are 'strictly' grammatically valid will be displayed first in the list of options and highlighted by bold icons. Other suggestions that are applicable to this element's scope but are not grammatically valid, will be displayed lower in the list with de-emphasized icons. When the suggestion strategy is set to "Lax", all suggestions will displayed in the list with de-emphasized icons." /> -<meta name="description" content="You can customize the formatting of the suggestions given by content assist by choosing a suggestion strategy preference. When the suggestion strategy is set to "Strict", suggestions that are 'strictly' grammatically valid will be displayed first in the list of options and highlighted by bold icons. Other suggestions that are applicable to this element's scope but are not grammatically valid, will be displayed lower in the list with de-emphasized icons. When the suggestion strategy is set to "Lax", all suggestions will displayed in the list with de-emphasized icons." /> -<meta content="XML editor, setting, source suggestion strategy" name="DC.subject" /> -<meta content="XML editor, setting, source suggestion strategy" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twcdast.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="xmlsourcesuggestionstrategy" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting the XML source suggestion strategy used by content assist</title> -</head> -<body id="xmlsourcesuggestionstrategy"><a name="xmlsourcesuggestionstrategy"><!-- --></a> - - -<h1 class="topictitle1">Setting the XML source suggestion strategy used by content assist</h1> - - - -<div><p>You can customize the formatting of the suggestions given by content -assist by choosing a suggestion strategy preference. When the suggestion strategy -is set to "Strict", suggestions that are 'strictly' grammatically valid will -be displayed first in the list of options and highlighted by bold icons. Other -suggestions that are applicable to this element's scope but are not grammatically -valid, will be displayed lower in the list with de-emphasized icons. When -the suggestion strategy is set to "Lax", all suggestions will displayed in -the list with de-emphasized icons.</p> - -<div class="section">To set the suggestion strategy used by content assist:</div> - -<ol> -<li><span>From the menu bar, Click <span class="menucascade"><span class="uicontrol">Window</span> - > <span class="uicontrol">Preferences</span></span></span></li> - -<li><span>Select <span class="menucascade"><span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML -Files</span> > <span class="uicontrol">XML Source</span></span>.</span></li> - -<li><span>Beside Suggestion strategy in the Content assist section, select -the appropriate setting (for example, <span class="uicontrol">Strict</span>).</span> -</li> - -</ol> - -<div class="example"><p>The following screen capture demonstrates content assist with -the suggestion strategy set to "Strict":</p> -<br /><img src="../images/suggestion.gif" alt="Example of Strict Suggestion Strategy" /><br /></div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/twcdast.html" title="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code.">Using XML content assist</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.dita deleted file mode 100644 index d1506978e4..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="ttaghilt" xml:lang="en-us">
-<title>Setting source highlighting styles</title>
-<titlealts>
-<searchtitle>Setting source highlighting styles</searchtitle>
-</titlealts>
-<shortdesc>If desired, you can change various aspects of how the XML source
-code is displayed in the Source view of the XML editor, such as the colors
-the tags will be displayed in.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>setting source highlighting styles</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To set highlighting styles for the XML code, follow these steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Files</uicontrol><uicontrol> XML
-Styles</uicontrol></menucascade>.</cmd></step>
-<step><cmd>In the <uicontrol>Content type</uicontrol> list, select the source
-tag type that you wish to set a highlighting style for. You can also click
-text in the sample text to specify the source tag type that you wish to set
-a highlighting style for.</cmd></step>
-<step><cmd>Click the <uicontrol>Foreground</uicontrol> box.</cmd></step>
-<step><cmd>Select the color that you want the text of the tag to appear in
-and click <uicontrol>OK</uicontrol>.</cmd></step>
-<step><cmd>Click the <uicontrol>Background</uicontrol> box.</cmd></step>
-<step><cmd>Select the color that you want to appear behind the tag and click <uicontrol>OK</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the <uicontrol>Bold</uicontrol> check box if you want to
-make the type bold.</cmd></step>
-<step><cmd>Click <uicontrol>Restore Default</uicontrol> to set the highlighting
-styles back to their default values. If you only want to reset the value for
-a particular content type, select it in the <uicontrol>Content type </uicontrol> field,
-the click the <uicontrol>Restore Default</uicontrol> button next to it. </cmd>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to save your changes.</cmd></step>
-</steps>
-<result></result>
-</taskbody>
-</task>
-<?Pub *0000002262?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html deleted file mode 100644 index de2dd481fe..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/ttaghilt.html +++ /dev/null @@ -1,81 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting source highlighting styles" /> -<meta name="abstract" content="If desired, you can change various aspects of how the XML source code is displayed in the Source view of the XML editor, such as the colors the tags will be displayed in." /> -<meta name="description" content="If desired, you can change various aspects of how the XML source code is displayed in the Source view of the XML editor, such as the colors the tags will be displayed in." /> -<meta content="XML editor, setting source highlighting styles" name="DC.subject" /> -<meta content="XML editor, setting source highlighting styles" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ttaghilt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting source highlighting styles</title> -</head> -<body id="ttaghilt"><a name="ttaghilt"><!-- --></a> - - -<h1 class="topictitle1">Setting source highlighting styles</h1> - - - - -<div><p>If desired, you can change various aspects of how the XML source -code is displayed in the Source view of the XML editor, such as the colors -the tags will be displayed in.</p> - -<div class="section"><p>To set highlighting styles for the XML code, follow these steps:</p> -</div> - -<ol> -<li><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol"> XML -Styles</span></span>.</span></li> - -<li><span>In the <span class="uicontrol">Content type</span> list, select the source -tag type that you wish to set a highlighting style for. You can also click -text in the sample text to specify the source tag type that you wish to set -a highlighting style for.</span></li> - -<li><span>Click the <span class="uicontrol">Foreground</span> box.</span></li> - -<li><span>Select the color that you want the text of the tag to appear in -and click <span class="uicontrol">OK</span>.</span></li> - -<li><span>Click the <span class="uicontrol">Background</span> box.</span></li> - -<li><span>Select the color that you want to appear behind the tag and click <span class="uicontrol">OK</span>.</span> -</li> - -<li><span>Select the <span class="uicontrol">Bold</span> check box if you want to -make the type bold.</span></li> - -<li><span>Click <span class="uicontrol">Restore Default</span> to set the highlighting -styles back to their default values. If you only want to reset the value for -a particular content type, select it in the <span class="uicontrol">Content type </span> field, -the click the <span class="uicontrol">Restore Default</span> button next to it. </span> -</li> - -<li><span>Click <span class="uicontrol">OK</span> to save your changes.</span></li> - -</ol> - -<div class="section" /> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.dita deleted file mode 100644 index 16ba4e3736..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.dita +++ /dev/null @@ -1,50 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<?Pub Inc?>
-<task id="twcdast" xml:lang="en-us">
-<title>Using XML content assist</title>
-<titlealts>
-<searchtitle>Using XML content assist</searchtitle>
-</titlealts>
-<shortdesc>You can use content assist to help you finish a tag or line of
-code in the Source view of the XML editor. You can also use content assist
-to insert templates into your XML code.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>content assist</indexterm></indexterm>
-<indexterm>XML files<indexterm>content assist</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The placement of the cursor in your source file provides the context
-for the content assist to offer suggestions for completion.</p><p>You can
-launch content assist in either of the following ways:</p><ul>
-<li>From the <uicontrol>Edit</uicontrol> menu, click <uicontrol>Content Assist</uicontrol>,
-or</li>
-<li>Press Ctrl+Space</li>
-</ul><p>In addition, you can set up an option that causes content assist to
-pop up automatically when certain characters are typed. To set up this option,
-click <menucascade><uicontrol>Window</uicontrol><uicontrol> Preferences</uicontrol>
-</menucascade> to open the Preferences window, then click <menucascade><uicontrol>Web
-and XML</uicontrol><uicontrol>XML Files </uicontrol><uicontrol>XML Source</uicontrol>
-</menucascade> . In the <uicontrol>Content assist</uicontrol> group box, select
-the <uicontrol>Automatically make suggestions</uicontrol> check box, and supply
-any additional characters that should trigger content assist.</p><p>If your
-cursor is in a position where content assist is available, a pop-up list of
-available choices is displayed when you launch content assist. The list is
-based on the context and whether a DTD or XML schema is associated with the
-XML file being edited. For example, if you have an Address element that can
-contain any of the following children elements: Name, Street, City, Zip Code,
-Country, and Province, and you place your cursor after any of them and launch
-content assist, all of the child elements will be listed in the content assist
-list.</p><p>The content assist list displays all valid tags for the current
-cursor position, including templates. If your grammar constraints are turned
-off, all available tags, not just valid ones are displayed. </p><p> </p><p>As
-you type the first one or two letters of the tag that you want, the list automatically
-refreshes with alphabetized choices that match your input.</p><p><b>Note</b>:
-The list only refreshes as described if you first type <userinput><</userinput> before
-prompting for content assist.</p><p>Scroll down and select the tag that you
-want to use by double-clicking on it. </p></context>
-</taskbody>
-</task>
-<?Pub *0000003061?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html deleted file mode 100644 index f70e050243..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twcdast.html +++ /dev/null @@ -1,89 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Using XML content assist" /> -<meta name="abstract" content="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code." /> -<meta name="description" content="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code." /> -<meta content="XML editor, editing, content assist, XML files" name="DC.subject" /> -<meta content="XML editor, editing, content assist, XML files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twmacro.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tsugstrat.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twcdast" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Using XML content assist</title> -</head> -<body id="twcdast"><a name="twcdast"><!-- --></a> - - -<h1 class="topictitle1">Using XML content assist</h1> - - - - -<div><p>You can use content assist to help you finish a tag or line of -code in the Source view of the XML editor. You can also use content assist -to insert templates into your XML code.</p> - -<div class="section"><p>The placement of the cursor in your source file provides the context -for the content assist to offer suggestions for completion.</p> -<p>You can -launch content assist in either of the following ways:</p> -<ul> -<li>From the <span class="uicontrol">Edit</span> menu, click <span class="uicontrol">Content Assist</span>, -or</li> - -<li>Press Ctrl+Space</li> - -</ul> -<p>In addition, you can set up an option that causes content assist to -pop up automatically when certain characters are typed. To set up this option, -click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol"> Preferences</span> -</span> to open the Preferences window, then click <span class="menucascade"><span class="uicontrol">Web -and XML</span> > <span class="uicontrol">XML Files </span> > <span class="uicontrol">XML Source</span> -</span> . In the <span class="uicontrol">Content assist</span> group box, select -the <span class="uicontrol">Automatically make suggestions</span> check box, and supply -any additional characters that should trigger content assist.</p> -<p>If your -cursor is in a position where content assist is available, a pop-up list of -available choices is displayed when you launch content assist. The list is -based on the context and whether a DTD or XML schema is associated with the -XML file being edited. For example, if you have an Address element that can -contain any of the following children elements: Name, Street, City, Zip Code, -Country, and Province, and you place your cursor after any of them and launch -content assist, all of the child elements will be listed in the content assist -list.</p> -<p>The content assist list displays all valid tags for the current -cursor position, including templates. If your grammar constraints are turned -off, all available tags, not just valid ones are displayed. </p> -<p> </p> -<p>As -you type the first one or two letters of the tag that you want, the list automatically -refreshes with alphabetized choices that match your input.</p> -<p><strong>Note</strong>: -The list only refreshes as described if you first type <kbd class="userinput"><</kbd> before -prompting for content assist.</p> -<p>Scroll down and select the tag that you -want to use by double-clicking on it. </p> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -<div><a href="../topics/twmacro.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time.">Working with XML templates</a></div> -<div><a href="../topics/tsugstrat.html" title="You can customize the formatting of the suggestions given by content assist by choosing a suggestion strategy preference. When the suggestion strategy is set to "Strict", suggestions that are 'strictly' grammatically valid will be displayed first in the list of options and highlighted by bold icons. Other suggestions that are applicable to this element's scope but are not grammatically valid, will be displayed lower in the list with de-emphasized icons. When the suggestion strategy is set to "Lax", all suggestions will displayed in the list with de-emphasized icons.">Setting the XML source suggestion strategy used by content assist</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.dita deleted file mode 100644 index c7ebd9a297..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="twmacro" xml:lang="en-us">
-<title>Working with XML templates</title>
-<titlealts>
-<searchtitle>Working with XML templates</searchtitle>
-</titlealts>
-<shortdesc>XML content assist provides a comment template, a chunk of predefined
-code that you can insert into a file. You may find a template useful when
-you have a certain piece of code you want to reuse several times, and you
-do not want to write it out every time.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML templates<indexterm>working with predefined code</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>You can use a default template as provided, customize that template,
-or create your own templates.</p>For example, you can work on a group of XML
-pages that should all contain a table with a specific appearance. Create a
-template that contains the tags for that table, including the appropriate
-attributes and attribute values for each tag. (You can copy and paste the
-tags from a structured text editor into the template's <uicontrol>Pattern</uicontrol> field.)
-Then select the name of the template from a content assist proposal list whenever
-you want to insert your custom table into an XML file.<p>To create a new XML
-template follow these steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Files</uicontrol><uicontrol>XML
-Templates</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Click <uicontrol>New</uicontrol> if you want to create a completely
-new template.</cmd></step>
-<step><cmd>Supply a new template <uicontrol>Name</uicontrol> and <uicontrol>Description</uicontrol>.</cmd>
-</step>
-<step><cmd>Specify the <uicontrol>Context</uicontrol> for the template.</cmd>
-<info>This is the context in which the template is available in the proposal
-list when content assist is requested. </info></step>
-<step><cmd>Specify the <uicontrol>Pattern</uicontrol> for your template using
-the appropriate tags, attributes, or attribute values to be inserted by content
-assist.</cmd></step>
-<step><cmd>If you want to insert a variable, click the <uicontrol>Insert Variable</uicontrol> button
-and select the variable to be inserted. </cmd><info>For example, the <b>date</b> variable
-indicates the current date will be inserted. </info></step>
-<step><cmd>Click <uicontrol>Apply</uicontrol> and then <uicontrol>OK</uicontrol> to
-save your changes.</cmd></step>
-</steps>
-<postreq>You can edit, remove, import, or export a template by using the same
-preferences page. If you have modified a default template, you can restore
-it to its default value. You can also restore a removed template if you have
-not exited from the workbench since it was removed. <p>If you have a template
-that you do not want to remove but you no longer want it to appear in the
-content assist list, go to the <b>XML Templates</b> preferences page and clear
-its check box.</p></postreq>
-</taskbody>
-</task>
-<?Pub *0000003427?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html deleted file mode 100644 index 5cfc5198e7..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twmacro.html +++ /dev/null @@ -1,95 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Working with XML templates" /> -<meta name="abstract" content="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time." /> -<meta name="description" content="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time." /> -<meta content="XML templates, creating, editing, XML templates, removing, importing, exporting" name="DC.subject" /> -<meta content="XML templates, creating, editing, XML templates, removing, importing, exporting" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twcdast.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twmacro" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Working with XML templates</title> -</head> -<body id="twmacro"><a name="twmacro"><!-- --></a> - - -<h1 class="topictitle1">Working with XML templates</h1> - - - - -<div><p>XML content assist provides a comment template, a chunk of predefined -code that you can insert into a file. You may find a template useful when -you have a certain piece of code you want to reuse several times, and you -do not want to write it out every time.</p> - -<div class="section"><p>You can use a default template as provided, customize that template, -or create your own templates.</p> -For example, you can work on a group of XML -pages that should all contain a table with a specific appearance. Create a -template that contains the tags for that table, including the appropriate -attributes and attribute values for each tag. (You can copy and paste the -tags from a structured text editor into the template's <span class="uicontrol">Pattern</span> field.) -Then select the name of the template from a content assist proposal list whenever -you want to insert your custom table into an XML file.<p>To create a new XML -template follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol">XML -Templates</span></span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">New</span> if you want to create a completely -new template.</span></li> - -<li class="stepexpand"><span>Supply a new template <span class="uicontrol">Name</span> and <span class="uicontrol">Description</span>.</span> -</li> - -<li class="stepexpand"><span>Specify the <span class="uicontrol">Context</span> for the template.</span> - This is the context in which the template is available in the proposal -list when content assist is requested. </li> - -<li class="stepexpand"><span>Specify the <span class="uicontrol">Pattern</span> for your template using -the appropriate tags, attributes, or attribute values to be inserted by content -assist.</span></li> - -<li class="stepexpand"><span>If you want to insert a variable, click the <span class="uicontrol">Insert Variable</span> button -and select the variable to be inserted. </span> For example, the <strong>date</strong> variable -indicates the current date will be inserted. </li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Apply</span> and then <span class="uicontrol">OK</span> to -save your changes.</span></li> - -</ol> - -<div class="section">You can edit, remove, import, or export a template by using the same -preferences page. If you have modified a default template, you can restore -it to its default value. You can also restore a removed template if you have -not exited from the workbench since it was removed. <p>If you have a template -that you do not want to remove but you no longer want it to appear in the -content assist list, go to the <strong>XML Templates</strong> preferences page and clear -its check box.</p> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -<div><a href="../topics/twcdast.html" title="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code.">Using XML content assist</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.dita deleted file mode 100644 index 09e77a0ed9..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.dita +++ /dev/null @@ -1,51 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="twxvalid" xml:lang="en-us">
-<title>Validating XML files</title>
-<titlealts>
-<searchtitle>Validating XML files</searchtitle>
-</titlealts>
-<shortdesc>When you validate your XML file, the XML validator will check to
-see that your file is valid and well-formed.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML files<indexterm>validating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The XML editor will process XML files that are invalid or not
-well-formed. The editor uses heuristics to open a file using the best interpretation
-of the tagging that it can. For example, an element with a missing end tag
-is simply assumed to end at the end of the document. As you make updates to
-a file, the editor incrementally reinterprets your document, changing the
-highlighting, tree view, and so on. Many formation errors are easy to spot
-in the syntax highlighting, so you can easily correct obvious errors on-the-fly.
-However, there will be other cases when it will be beneficial to perform formal
-validation on your documents.</p></context>
-<steps>
-<step><cmd>You can validate your file by selecting it in the Navigator view,
-right-clicking it, and clicking <uicontrol>Validate</uicontrol>.</cmd>
-</step>
-</steps>
-<result><p>Any validation problems are indicated in the Problems view. </p></result>
-<postreq><p>In the Problems view, you can double-click on individual errors,
-and you will be taken to the invalid tag in the file, so that you can make
-corrections. </p><p><b>Note</b>: If you receive an error message indicating
-that the Problems view is full, you can increase the number of error messages
-allowed by selecting <menucascade><uicontrol>Properties</uicontrol><uicontrol>Validation</uicontrol>
-</menucascade> from the project's pop-up menu and specifying the maximum number
-of error messages allowed. You must select the <uicontrol>Override validation
-preferences</uicontrol> check box in order to be able to do this.</p><p>As
-well, you can set up a project's properties so that different types of project
-resources are automatically validated when you save them. From a project's
-pop-up menu select <uicontrol>Properties</uicontrol>, then select <uicontrol>Validation</uicontrol>.
-Any validators you can run against your project will be listed in the Validation
-page.</p></postreq>
-</taskbody>
-<related-links>
-<link href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.dita" scope="peer">
-<linktext>Validating code in enterprise applications</linktext></link>
-</related-links>
-</task>
-<?Pub *0000002727?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html deleted file mode 100644 index 0b9ab90023..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/twxvalid.html +++ /dev/null @@ -1,83 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Validating XML files" /> -<meta name="abstract" content="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed." /> -<meta name="description" content="When you validate your XML file, the XML validator will check to see that your file is valid and well-formed." /> -<meta content="XML files, validating" name="DC.subject" /> -<meta content="XML files, validating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twxvalid" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Validating XML files</title> -</head> -<body id="twxvalid"><a name="twxvalid"><!-- --></a> - - -<h1 class="topictitle1">Validating XML files</h1> - - - - -<div><p>When you validate your XML file, the XML validator will check to -see that your file is valid and well-formed.</p> - -<div class="section"><p>The XML editor will process XML files that are invalid or not -well-formed. The editor uses heuristics to open a file using the best interpretation -of the tagging that it can. For example, an element with a missing end tag -is simply assumed to end at the end of the document. As you make updates to -a file, the editor incrementally reinterprets your document, changing the -highlighting, tree view, and so on. Many formation errors are easy to spot -in the syntax highlighting, so you can easily correct obvious errors on-the-fly. -However, there will be other cases when it will be beneficial to perform formal -validation on your documents.</p> -</div> - - -<div class="p"><span>You can validate your file by selecting it in the Navigator view, -right-clicking it, and clicking <span class="uicontrol">Validate</span>.</span> -</div> - - -<div class="section"><p>Any validation problems are indicated in the Problems view. </p> -</div> - -<div class="section"><p>In the Problems view, you can double-click on individual errors, -and you will be taken to the invalid tag in the file, so that you can make -corrections. </p> -<p><strong>Note</strong>: If you receive an error message indicating -that the Problems view is full, you can increase the number of error messages -allowed by selecting <span class="menucascade"><span class="uicontrol">Properties</span> > <span class="uicontrol">Validation</span> -</span> from the project's pop-up menu and specifying the maximum number -of error messages allowed. You must select the <span class="uicontrol">Override validation -preferences</span> check box in order to be able to do this.</p> -<p>As -well, you can set up a project's properties so that different types of project -resources are automatically validated when you save them. From a project's -pop-up menu select <span class="uicontrol">Properties</span>, then select <span class="uicontrol">Validation</span>. -Any validators you can run against your project will be listed in the Validation -page.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html">Validating code in enterprise applications</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.dita deleted file mode 100644 index c0b5f94e9a..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.dita +++ /dev/null @@ -1,94 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<?Pub Inc?>
-<task id="txedtdes" xml:lang="en-us">
-<title>Editing in the Design view</title>
-<titlealts>
-<searchtitle>Editing in the Design view</searchtitle>
-</titlealts>
-<shortdesc>The XML editor has a Design view, which represents the XML file
-simultaneously as a table and a tree. This helps make navigation and editing
-easier. Content and attribute values can be edited directly in the table cells,
-while pop-up menus on the tree elements give alternatives that are valid for
-that particular element.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>Design view</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> For example, the <uicontrol>Add child</uicontrol> menu item will
-list only those elements from a DTD or XML schema which would be valid children
-at that point.</p><p>When you have an XML file associated with an XML schema
-or DTD file, certain tags and rules for that file have already been established,
-which is why the Design view can provide prompts (via a pop-up menu) for those
-tags. When you create an XML file that is not associated with an XML schema
-or DTD file, it has no tags or rules associated with it, so the Design view
-cannot provide prompts for specific tags, but it can provide prompts to create
-new elements and attributes.</p><p>For any XML file associated with an XML
-schema or DTD file, you can use the Design view to add any items defined in
-the XML schema or DTD (such as elements and attributes) to the XML file. You
-can also use it to add processing instructions and comments to all XML files.</p><p>For
-more information on the icons used in the Design view, refer to the related
-reference.</p><p>The following instructions were written for the Resource
-perspective, but they will also work in many other perspectives.</p><p>To
-edit an XML file in the Design view, follow these steps:</p></context>
-<steps>
-<step><cmd>Open the XML file that you want to work with in the XML editor
-(right-click the file in the Navigator view and click <uicontrol>Open With
-> XML Editor</uicontrol>). If necessary, click the <uicontrol>Design</uicontrol> tab.</cmd>
-</step>
-<step><cmd>To expand all the items in your XML file, click the <uicontrol>Expand
-All</uicontrol> toolbar button <image href="../images/expand_all.gif"><alt>This
-graphic is the Expand All toolbar button</alt></image>.</cmd></step>
-<step><cmd>To collapse them, click the <uicontrol>Collapse All</uicontrol> toolbar
-button <image href="../images/collapse_all.gif"><alt>This graphic is the
-Collapse All toolbar button</alt></image>.</cmd></step>
-<step><cmd>Right-click the item that you want to work with.</cmd><info>Some
-or all of the following options (as applicable) will be available from the
-pop-up menu that appears:<ul>
-<li> <uicontrol>Add DTD Information</uicontrol> - Click this if you want to
-associate the XML file with a DTD.</li>
-<li> <uicontrol>Edit DOCTYPE</uicontrol> - Click this if you want to edit
-the DOCTYPE declaration. Refer to the related task for more details.</li>
-<li> <uicontrol>Edit Namespaces</uicontrol> - Click this if you want to edit
-the existing namespace information or create a new association with a namespace.
-Refer to the related task for more details.</li>
-<li> <uicontrol>Edit Processing Instruction</uicontrol> - Click this if you
-want to edit the processing instruction. Refer to the related task for more
-details.</li>
-<li> <uicontrol>Remove</uicontrol> - Click this if you want to remove the
-item that you have selected from the XML file. This option will not be available
-if the item you want to remove must exist (for example, in your DTD, you have
-declared that "One or more" of the item must always exist in your XML file,
-and the item you have selected is the only one that exists in your XML file).</li>
-<li> <uicontrol>Add Attribute</uicontrol> - Click this if you want to add
-an attribute to the element that you selected. Any attributes you are allowed
-to add to the element will be listed. After you have added the attribute to
-the XML file, you can click in the right-hand column to change the value of
-the attribute. If the attribute has set values, they will appear in a list.</li>
-<li> <uicontrol>Add Child</uicontrol> - Click this to add another element,
-a comment, or a processing instruction as a child of the parent element.</li>
-<li> <uicontrol>Add Before</uicontrol> - Click this to add a child element,
-comment, or processing instruction that can go before the item you have selected.
-For example, if you have a parent element called "CD Collections" that can
-contain an unlimited amount of children called "CD", you could click a CD
-element and click <menucascade><uicontrol>Add Before</uicontrol><uicontrol> CD</uicontrol>
-</menucascade> , as a CD element can go before another CD element.</li>
-<li> <uicontrol>Add After</uicontrol> - Click this to add a child element,
-comment, or processing instruction that can go after the item you have selected.
-For example, if you have a parent element called "CD Collections" that can
-contain an unlimited amount of children called "CD", you could click a CD
-element and click <menucascade><uicontrol>Add After</uicontrol><uicontrol> CD</uicontrol>
-</menucascade>, as a CD element can go after another CD element.</li>
-<li> <uicontrol>Replace With</uicontrol> - Click this if you want to replace
-one item with another. This option is not available if you turn grammar constraints
-off or if there are no valid alternatives for you to replace the item with.</li>
-</ul></info></step>
-<step><cmd>Click the appropriate option.</cmd></step>
-</steps>
-<result><p>Any changes you make in the Design view are also reflected in the
-Source view and the Outline view.</p></result>
-</taskbody>
-</task>
-<?Pub *0000005971?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html deleted file mode 100644 index ace05b2314..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtdes.html +++ /dev/null @@ -1,157 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing in the Design view" /> -<meta name="abstract" content="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element." /> -<meta name="description" content="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element." /> -<meta content="XML editor, editing, in the Design view" name="DC.subject" /> -<meta content="XML editor, editing, in the Design view" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtproc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rxmlbicons.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txedtdes" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing in the Design view</title> -</head> -<body id="txedtdes"><a name="txedtdes"><!-- --></a> - - -<h1 class="topictitle1">Editing in the Design view</h1> - - - - -<div><p>The XML editor has a Design view, which represents the XML file -simultaneously as a table and a tree. This helps make navigation and editing -easier. Content and attribute values can be edited directly in the table cells, -while pop-up menus on the tree elements give alternatives that are valid for -that particular element.</p> - -<div class="section"><p> For example, the <span class="uicontrol">Add child</span> menu item will -list only those elements from a DTD or XML schema which would be valid children -at that point.</p> -<p>When you have an XML file associated with an XML schema -or DTD file, certain tags and rules for that file have already been established, -which is why the Design view can provide prompts (via a pop-up menu) for those -tags. When you create an XML file that is not associated with an XML schema -or DTD file, it has no tags or rules associated with it, so the Design view -cannot provide prompts for specific tags, but it can provide prompts to create -new elements and attributes.</p> -<p>For any XML file associated with an XML -schema or DTD file, you can use the Design view to add any items defined in -the XML schema or DTD (such as elements and attributes) to the XML file. You -can also use it to add processing instructions and comments to all XML files.</p> -<p>For -more information on the icons used in the Design view, refer to the related -reference.</p> -<p>The following instructions were written for the Resource -perspective, but they will also work in many other perspectives.</p> -<p>To -edit an XML file in the Design view, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the XML file that you want to work with in the XML editor -(right-click the file in the Navigator view and click <span class="uicontrol">Open With -> XML Editor</span>). If necessary, click the <span class="uicontrol">Design</span> tab.</span> -</li> - -<li class="stepexpand"><span>To expand all the items in your XML file, click the <span class="uicontrol">Expand -All</span> toolbar button <img src="../images/expand_all.gif" alt="This graphic is the Expand All toolbar button" />.</span></li> - -<li class="stepexpand"><span>To collapse them, click the <span class="uicontrol">Collapse All</span> toolbar -button <img src="../images/collapse_all.gif" alt="This graphic is the Collapse All toolbar button" />.</span></li> - -<li class="stepexpand"><span>Right-click the item that you want to work with.</span> Some -or all of the following options (as applicable) will be available from the -pop-up menu that appears:<ul> -<li> <span class="uicontrol">Add DTD Information</span> - Click this if you want to -associate the XML file with a DTD.</li> - -<li> <span class="uicontrol">Edit DOCTYPE</span> - Click this if you want to edit -the DOCTYPE declaration. Refer to the related task for more details.</li> - -<li> <span class="uicontrol">Edit Namespaces</span> - Click this if you want to edit -the existing namespace information or create a new association with a namespace. -Refer to the related task for more details.</li> - -<li> <span class="uicontrol">Edit Processing Instruction</span> - Click this if you -want to edit the processing instruction. Refer to the related task for more -details.</li> - -<li> <span class="uicontrol">Remove</span> - Click this if you want to remove the -item that you have selected from the XML file. This option will not be available -if the item you want to remove must exist (for example, in your DTD, you have -declared that "One or more" of the item must always exist in your XML file, -and the item you have selected is the only one that exists in your XML file).</li> - -<li> <span class="uicontrol">Add Attribute</span> - Click this if you want to add -an attribute to the element that you selected. Any attributes you are allowed -to add to the element will be listed. After you have added the attribute to -the XML file, you can click in the right-hand column to change the value of -the attribute. If the attribute has set values, they will appear in a list.</li> - -<li> <span class="uicontrol">Add Child</span> - Click this to add another element, -a comment, or a processing instruction as a child of the parent element.</li> - -<li> <span class="uicontrol">Add Before</span> - Click this to add a child element, -comment, or processing instruction that can go before the item you have selected. -For example, if you have a parent element called "CD Collections" that can -contain an unlimited amount of children called "CD", you could click a CD -element and click <span class="menucascade"><span class="uicontrol">Add Before</span> > <span class="uicontrol"> CD</span> -</span> , as a CD element can go before another CD element.</li> - -<li> <span class="uicontrol">Add After</span> - Click this to add a child element, -comment, or processing instruction that can go after the item you have selected. -For example, if you have a parent element called "CD Collections" that can -contain an unlimited amount of children called "CD", you could click a CD -element and click <span class="menucascade"><span class="uicontrol">Add After</span> > <span class="uicontrol"> CD</span> -</span>, as a CD element can go after another CD element.</li> - -<li> <span class="uicontrol">Replace With</span> - Click this if you want to replace -one item with another. This option is not available if you turn grammar constraints -off or if there are no valid alternatives for you to replace the item with.</li> - -</ul> -</li> - -<li class="stepexpand"><span>Click the appropriate option.</span></li> - -</ol> - -<div class="section"><p>Any changes you make in the Design view are also reflected in the -Source view and the Outline view.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -<div><a href="../topics/tedtproc.html" title="If you have instructions you want to pass along to an application using an XML document, you can use a processing instruction.">Editing XML processing instructions</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rxmlbicons.html" title="The following XML editor icons appear in the Outline and Design view.">Icons used in the XML editor</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.dita deleted file mode 100644 index a453b108c6..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.dita +++ /dev/null @@ -1,82 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="txedtsrc" xml:lang="en-us">
-<title>Editing in the Source view</title>
-<titlealts>
-<searchtitle>Editing in the Source view</searchtitle>
-</titlealts>
-<shortdesc>You can use the Source view to view and work with a file's source
-code directly.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>Source view</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> The Source view has many text editing features, such as:</p><dl>
-<dlentry>
-<dt>Syntax highlighting</dt>
-<dd>Each tag type is highlighted differently, enabling you to easily find
-a certain kind of tag for editing. In addition, syntax highlighting is valuable
-in locating syntax errors. For example, if you begin a comment in the middle
-of the document with <codeph><!--</codeph> everything until the next <codeph>--></codeph> is
-considered a comment, and will be highlighted accordingly. The large highlighted
-area will indicate that you need to add <codeph>--></codeph> to close the
-comment.<p>You can customize the syntax highlighting. Refer to the related
-tasks for more information.</p></dd>
-</dlentry></dl><dl><dlentry>
-<dt>Unlimited undo and redo</dt>
-<dd>These options allow you to incrementally undo and redo every change made
-to a file for the entire editing session. For text, changes are incremented
-one character or set of selected characters at a time.</dd>
-</dlentry><dlentry>
-<dt>Content assist</dt>
-<dd>Content assist helps you finish tags and insert macros. Refer
-to the related task for more details.</dd>
-</dlentry><dlentry>
-<dt>Template</dt>
-<dd>You can access templates (using content assist) to help you quickly add
-regularly-used tagging combinations. Refer to the related task for more details.</dd>
-</dlentry><dlentry>
-<dt>Node selection</dt>
-<dd>Based on the location of your cursor (or selection in the Outline view),
-the node selection indicator highlights the line numbers that include a node
-(for example, an element or attribute), in the vertical ruler in the left
-area of the Source view.</dd>
-</dlentry><dlentry>
-<dt>Pop-up menu options</dt>
-<dd>From the editor's pop-up menu, you have many of the same editing options
-available as you do from the workbench <b>Edit</b> menu. You can select menu
-options such as: <uicontrol>Cleanup Document,</uicontrol> to open the <uicontrol>Cleanup</uicontrol>
-dialog, which contains settings to update a document so that it is well-formed
-and formatted and <uicontrol>Format,</uicontrol> which formats either the
-entire document or selected elements.</dd>
-</dlentry><dlentry>
-<dt>"Smart" double clicking</dt>
-<dd>You can use double-click to select attribute values, attribute-value pairs,
-and entire tag sets to quickly update, copy, or remove content.</dd>
-</dlentry></dl><p>To edit an XML file in the Source view, follow these steps:</p></context>
-<steps>
-<step><cmd>Open the XML file you want to work with in the XML editor (right-click
-the file in the Navigator view and click <uicontrol>Open With > XML Editor</uicontrol>). </cmd>
-<info>You might need to click the <uicontrol>Source</uicontrol> tab. Typically,
-all that you will need to do to open the file is to double-click it in the
-Navigator view. If this does not work, right-click it and click <uicontrol>Open
-With > XML Editor</uicontrol>.</info></step>
-<step><cmd>Edit the code as necessary, using any of the available features.</cmd>
-<info>As you move the cursor within your XML file (or select items from the
-Outline view), the node selection indicator will highlight the line numbers
-that encompass the node (for example, an element or attribute). You can use
-smart double-clicking behavior to select attribute values, attribute-value
-pairs, and entire tag sets to quickly update, copy, or remove content.</info>
-</step>
-<step><cmd>At intervals, you might wish to format individual nodes, or the
-entire XML file to restore element and attribute indentation to see nesting
-hierarchies more clearly in the file.</cmd></step>
-<step><cmd>If desired, validate and save the XML file.</cmd></step>
-</steps>
-<result><p>Any changes you make in the Source view are also reflected in the
-Design view and the Outline view.</p></result>
-</taskbody>
-</task>
-<?Pub *0000004423?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html deleted file mode 100644 index c96c43dc37..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedtsrc.html +++ /dev/null @@ -1,145 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing in the Source view" /> -<meta name="abstract" content="You can use the Source view to view and work with a file's source code directly." /> -<meta name="description" content="You can use the Source view to view and work with a file's source code directly." /> -<meta content="XML editor, editing, in the Source view" name="DC.subject" /> -<meta content="XML editor, editing, in the Source view" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twcdast.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/twmacro.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/ttaghilt.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txedtsrc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing in the Source view</title> -</head> -<body id="txedtsrc"><a name="txedtsrc"><!-- --></a> - - -<h1 class="topictitle1">Editing in the Source view</h1> - - - - -<div><p>You can use the Source view to view and work with a file's source -code directly.</p> - -<div class="section"><p> The Source view has many text editing features, such as:</p> -<dl> - -<dt class="dlterm">Syntax highlighting</dt> - -<dd>Each tag type is highlighted differently, enabling you to easily find -a certain kind of tag for editing. In addition, syntax highlighting is valuable -in locating syntax errors. For example, if you begin a comment in the middle -of the document with <samp class="codeph"><!--</samp> everything until the next <samp class="codeph">--></samp> is -considered a comment, and will be highlighted accordingly. The large highlighted -area will indicate that you need to add <samp class="codeph">--></samp> to close the -comment.<p>You can customize the syntax highlighting. Refer to the related -tasks for more information.</p> -</dd> - -</dl> -<dl> -<dt class="dlterm">Unlimited undo and redo</dt> - -<dd>These options allow you to incrementally undo and redo every change made -to a file for the entire editing session. For text, changes are incremented -one character or set of selected characters at a time.</dd> - - -<dt class="dlterm">Content assist</dt> - -<dd>Content assist helps you finish tags and insert macros. Refer -to the related task for more details.</dd> - - -<dt class="dlterm">Template</dt> - -<dd>You can access templates (using content assist) to help you quickly add -regularly-used tagging combinations. Refer to the related task for more details.</dd> - - -<dt class="dlterm">Node selection</dt> - -<dd>Based on the location of your cursor (or selection in the Outline view), -the node selection indicator highlights the line numbers that include a node -(for example, an element or attribute), in the vertical ruler in the left -area of the Source view.</dd> - - -<dt class="dlterm">Pop-up menu options</dt> - -<dd>From the editor's pop-up menu, you have many of the same editing options -available as you do from the workbench <strong>Edit</strong> menu. You can select menu -options such as: <span class="uicontrol">Cleanup Document,</span> to open the <span class="uicontrol">Cleanup</span> -dialog, which contains settings to update a document so that it is well-formed -and formatted and <span class="uicontrol">Format,</span> which formats either the -entire document or selected elements.</dd> - - -<dt class="dlterm">"Smart" double clicking</dt> - -<dd>You can use double-click to select attribute values, attribute-value pairs, -and entire tag sets to quickly update, copy, or remove content.</dd> - -</dl> -<p>To edit an XML file in the Source view, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the XML file you want to work with in the XML editor (right-click -the file in the Navigator view and click <span class="uicontrol">Open With > XML Editor</span>). </span> - You might need to click the <span class="uicontrol">Source</span> tab. Typically, -all that you will need to do to open the file is to double-click it in the -Navigator view. If this does not work, right-click it and click <span class="uicontrol">Open -With > XML Editor</span>.</li> - -<li class="stepexpand"><span>Edit the code as necessary, using any of the available features.</span> - As you move the cursor within your XML file (or select items from the -Outline view), the node selection indicator will highlight the line numbers -that encompass the node (for example, an element or attribute). You can use -smart double-clicking behavior to select attribute values, attribute-value -pairs, and entire tag sets to quickly update, copy, or remove content. -</li> - -<li class="stepexpand"><span>At intervals, you might wish to format individual nodes, or the -entire XML file to restore element and attribute indentation to see nesting -hierarchies more clearly in the file.</span></li> - -<li class="stepexpand"><span>If desired, validate and save the XML file.</span></li> - -</ol> - -<div class="section"><p>Any changes you make in the Source view are also reflected in the -Design view and the Outline view.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -<div><a href="../topics/twcdast.html" title="You can use content assist to help you finish a tag or line of code in the Source view of the XML editor. You can also use content assist to insert templates into your XML code.">Using XML content assist</a></div> -<div><a href="../topics/twmacro.html" title="XML content assist provides a comment template, a chunk of predefined code that you can insert into a file. You may find a template useful when you have a certain piece of code you want to reuse several times, and you do not want to write it out every time.">Working with XML templates</a></div> -<div><a href="../topics/ttaghilt.html" title="If desired, you can change various aspects of how the XML source code is displayed in the Source view of the XML editor, such as the colors the tags will be displayed in.">Setting source highlighting styles</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.dita deleted file mode 100644 index df24fd5cb4..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.dita +++ /dev/null @@ -1,46 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="txedttag" xml:lang="en-us">
-<title>Editing XML files</title>
-<titlealts>
-<searchtitle>Editing XML files</searchtitle>
-</titlealts>
-<shortdesc>This file contains information about editing XML files.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>XML files</indexterm></indexterm>
-<indexterm>XML files<indexterm>editing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To open an XML file in the XML editor, right-click it in the Navigator
-view and click <menucascade><uicontrol>Open With</uicontrol><uicontrol>XML
-Editor</uicontrol></menucascade>. </p><p>We recommend working in the Resource
-perspective when you are developing XML files. The views that appear by default
-in this perspective (such as the Outline view) help facilitate XML development.</p><p>The
-XML editor enables you to directly edit XML files. There are several different
-views you can use to edit your files:</p><ul>
-<li><b>Source view</b> - you can manually insert, edit, and delete elements
-and attributes in the Source view of the XML editor. To facilitate this effort,
-you can use content assist while you are in the Source view.</li>
-<li><b>Design view</b> - you can insert, delete, and edit elements, attributes,
-comments, and processing instructions in this view.</li>
-<li><b>Outline view </b>- you can insert and delete elements attributes, comments,
-and processing instructions in this view.</li>
-</ul><p>Often, you may find that you have more than one way to perform a specific
-task. For example, you have an XML file "MySchoolSubjects.xml" associated
-with an XML schema file "SchoolSubjects.xsd", which list all the subjects
-taught in a school. You want to insert a new element "Math" into your file.
-You can do so in the following ways:</p><ul>
-<li>In the Outline or Design view, right-click the appropriate parent element
-and select <uicontrol>Math</uicontrol> from the <uicontrol>Add Child</uicontrol> pop-up
-menu.</li>
-<li>In the Source view, use content assist to help you find the appropriate
-location and code for the <uicontrol>Math</uicontrol> element.</li>
-<li>In the Source view, type the code for the <uicontrol>Math</uicontrol> element
-in the file.</li>
-</ul></context>
-<postreq>The following links provide more information about the XML editor
-and editing XML files:</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html deleted file mode 100644 index af6b692b85..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txedttag.html +++ /dev/null @@ -1,90 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML files" /> -<meta name="abstract" content="This file contains information about editing XML files." /> -<meta name="description" content="This file contains information about editing XML files." /> -<meta content="XML files, editing, XML editor" name="DC.subject" /> -<meta content="XML files, editing, XML editor" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cwxmledt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtdes.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/txedtsrc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txedttag" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML files</title> -</head> -<body id="txedttag"><a name="txedttag"><!-- --></a> - - -<h1 class="topictitle1">Editing XML files</h1> - - - - -<div><p>This file contains information about editing XML files.</p> - -<div class="section"><p>To open an XML file in the XML editor, right-click it in the Navigator -view and click <span class="menucascade"><span class="uicontrol">Open With</span> > <span class="uicontrol">XML -Editor</span></span>. </p> -<p>We recommend working in the Resource -perspective when you are developing XML files. The views that appear by default -in this perspective (such as the Outline view) help facilitate XML development.</p> -<p>The -XML editor enables you to directly edit XML files. There are several different -views you can use to edit your files:</p> -<ul> -<li><strong>Source view</strong> - you can manually insert, edit, and delete elements -and attributes in the Source view of the XML editor. To facilitate this effort, -you can use content assist while you are in the Source view.</li> - -<li><strong>Design view</strong> - you can insert, delete, and edit elements, attributes, -comments, and processing instructions in this view.</li> - -<li><strong>Outline view </strong>- you can insert and delete elements attributes, comments, -and processing instructions in this view.</li> - -</ul> -<p>Often, you may find that you have more than one way to perform a specific -task. For example, you have an XML file "MySchoolSubjects.xml" associated -with an XML schema file "SchoolSubjects.xsd", which list all the subjects -taught in a school. You want to insert a new element "Math" into your file. -You can do so in the following ways:</p> -<ul> -<li>In the Outline or Design view, right-click the appropriate parent element -and select <span class="uicontrol">Math</span> from the <span class="uicontrol">Add Child</span> pop-up -menu.</li> - -<li>In the Source view, use content assist to help you find the appropriate -location and code for the <span class="uicontrol">Math</span> element.</li> - -<li>In the Source view, type the code for the <span class="uicontrol">Math</span> element -in the file.</li> - -</ul> -</div> - -<div class="section">The following links provide more information about the XML editor -and editing XML files:</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cwxmledt.html" title="The XML editor is a tool for creating and viewing XML files.">XML editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/txedtdes.html" title="The XML editor has a Design view, which represents the XML file simultaneously as a table and a tree. This helps make navigation and editing easier. Content and attribute values can be edited directly in the table cells, while pop-up menus on the tree elements give alternatives that are valid for that particular element.">Editing in the Design view</a></div> -<div><a href="../topics/txedtsrc.html" title="You can use the Source view to view and work with a file's source code directly.">Editing in the Source view</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.dita deleted file mode 100644 index 828484fcc1..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.dita +++ /dev/null @@ -1,115 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<?Pub Inc?>
-<task id="txmlcat" xml:lang="en-us">
-<title>Adding entries to the XML Catalog</title>
-<titlealts>
-<searchtitle>Adding entries to the XML Catalog</searchtitle>
-</titlealts>
-<shortdesc>An XML Catalog entry contains two parts - a Key (which represents
-a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains
-information about a DTD or XML schema's location). You can place the Key in
-an XML file. When the XML processor encounters it, it will use the XML Catalog
-entry to find the location of the DTD or XML schema associated with the Key</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML catalog<indexterm>adding entries</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>XML Catalog entries can be used in various situations. For example,
-you are working on an XML file on your main desktop computer and point its <codeph>schemaLocation</codeph> towards
-a schema called <codeph>c:\MySchema.xsd</codeph>. You then save it to your
-laptop computer so you can work on it later. When you open the file on your
-laptop, however, you encounter a problem - the XML editor cannot find the <codeph>MySchema.xsd</codeph> schema
-because it is actually installed on your D drive. You will have to edit the <codeph>schemaLocation</codeph> to
-point to <codeph>d:\MySchema.xsd</codeph>. When you have finished editing
-the XML file and are ready to publish it on the Web, you will need to edit
-the URI again so that it points to a resource that is accessible on the Web.
-By now, the problem is obvious. A URI used within an XML file is not as portable
-as you would like it to be. To avoid making frequent changes to your XML document,
-you can use the XML Catalog.</p><p>An XML Catalog entry is used by an XML
-processor when resolving entity references. You can provide rules to the catalog
-to specify how entities should be resolved. If you consider the preceding
-example, you could specify a rule that redirects an Internet resource reference
-(for example, <codeph>"http://www.ibm.com/published-schemas/MySchema.xsd"</codeph>)
-so that it points to a resource on the developer's local machine (for example,
- <codeph>"file:///C:/MySchema.xsd"</codeph>). Now, instead of frequently editing
-XML documents to update the URIs (especially when there are many documents
-in your project), you only need to update a single rule in your XML Catalog.</p><p>The
-following instructions were written for the Resource perspective, but they
-will also work in many other perspectives.</p><p>To add an entry to the XML
-Catalog, follow these steps:</p></context>
-<steps>
-<step><cmd>Open the XML file that you want to associate with a DTD or XML
-schema.</cmd></step>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Catalog</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>The <uicontrol>XML Catalog Entries</uicontrol> field contains
-a list of any user-defined and plug-in defined catalog entries.</cmd>
-<substeps>
-<substep><cmd>Select any entry to see details about it in the <uicontrol>Details</uicontrol> field. </cmd>
-</substep>
-<substep><cmd>Click <uicontrol>Add</uicontrol> to create a new catalog entry.</cmd>
-</substep>
-</substeps>
-</step>
-<step><cmd>In the <uicontrol>URI</uicontrol> field, type the location of the
-DTD or XML schema or browse for it.</cmd></step>
-<step><cmd>If you specified a DTD in the <uicontrol>URI</uicontrol> field,
-you can select either <uicontrol>Public ID</uicontrol> or <uicontrol>System
-ID</uicontrol> from the <uicontrol>Key Type</uicontrol> field.</cmd><info>If
-you select <uicontrol>Public ID,</uicontrol> the value you enter in the <uicontrol>Key</uicontrol> field
-should be the same as the Public ID in the XML file's DOCTYPE declaration.
-If you select <uicontrol>System ID</uicontrol>, the value you enter should
-correspond to the System ID in an XML file's DOCTYPE declaration.</info></step>
-<step><cmd>If you specified an XML schema in the <uicontrol>URI</uicontrol> field,
-you can select either <uicontrol>Namespace Name</uicontrol> or <uicontrol>Schema
-Location</uicontrol> from the <uicontrol>Key Type</uicontrol> field.</cmd>
-<info>If the schema defines a target namespace, it will automatically appear
-in the <uicontrol>Key</uicontrol> field. Otherwise, you can enter the schema
-location in the <uicontrol>Key</uicontrol> field.</info></step>
-<step><cmd>Select the <uicontrol>Specify alternative Web address</uicontrol> check
-box if you want to be able to specify an alternate Web address for the resource.</cmd>
-<info>This Web address is used when an XML instance is generated from this
-catalog entry. <b>Note</b>: This option is only available if you select <uicontrol>Public
-ID</uicontrol> (for a DTD) or <uicontrol>Namespace Name</uicontrol> (for
-a schema) in the <uicontrol>Key type</uicontrol> field.</info></step>
-<step><cmd>If you want to refer to another catalog without importing it into
-the workbench, click <uicontrol>Next Catalog</uicontrol>. Type or browse for
-the XML catalog you want to refer to. </cmd></step>
-<step><cmd>When you are done creating catalog entries, click <uicontrol>OK</uicontrol> to
-close the Add XML Catalog Entry dialog. </cmd></step>
-<step><cmd>Click <uicontrol>Advanced</uicontrol> if you want to import or
-export any XML Catalog settings.</cmd></step>
-<step><cmd>Click <uicontrol>Export</uicontrol> if you want to persist the
-XML Catalog information. Only your user specified entries will be exported.</cmd>
-<substeps>
-<substep><cmd>You will be prompted to select a project and provide a file
-name to store your catalog entries in an .xmlcatalog file, which can be opened
-from the Navigator view. Snce your catalog entries are stored in an .xmlcatalog
-file, you can check them in and out and share them like any other project
-resource. </cmd></substep>
-<substep><cmd>Click <uicontrol>OK</uicontrol>.</cmd></substep>
-</substeps>
-</step>
-<step><cmd>Click <uicontrol>Import</uicontrol> if you want to import an .xmlcatalog
-file. You will be prompted to select the file you want to import.</cmd>
-<substeps>
-<substep><cmd>When you import a .xmlcatalog file, any entries in it will be
-loaded into the XML Catalog (and any existing entries will be overwritten). </cmd>
-</substep>
-<substep><cmd>Click <uicontrol>OK</uicontrol>.</cmd></substep>
-</substeps>
-</step>
-<step><cmd>Click <uicontrol>OK</uicontrol> to close the Advanced XML Catalog
-Preferences dialog.</cmd></step>
-<step><cmd>Make sure the XML file is in focus and click the <uicontrol>Reload
-dependencies</uicontrol> toolbar button. </cmd></step>
-</steps>
-<result>The XML file is now associated with the latest version of the XML
-schema or DTD.</result>
-</taskbody>
-</task>
-<?Pub *0000007087?>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html deleted file mode 100644 index 2d172b4c26..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txmlcat.html +++ /dev/null @@ -1,181 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding entries to the XML Catalog" /> -<meta name="abstract" content="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key" /> -<meta name="description" content="An XML Catalog entry contains two parts - a Key (which represents a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains information about a DTD or XML schema's location). You can place the Key in an XML file. When the XML processor encounters it, it will use the XML Catalog entry to find the location of the DTD or XML schema associated with the Key" /> -<meta content="XML catalog, adding entries, importing entries, exporting entries" name="DC.subject" /> -<meta content="XML catalog, adding entries, importing entries, exporting entries" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtdoc.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlcat.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtcnst.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtgram.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txmlcat" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding entries to the XML Catalog</title> -</head> -<body id="txmlcat"><a name="txmlcat"><!-- --></a> - - -<h1 class="topictitle1">Adding entries to the XML Catalog</h1> - - - - -<div><p>An XML Catalog entry contains two parts - a Key (which represents -a DTD or XML schema) and a Uniform Resource Identifier (URI) (which contains -information about a DTD or XML schema's location). You can place the Key in -an XML file. When the XML processor encounters it, it will use the XML Catalog -entry to find the location of the DTD or XML schema associated with the Key</p> - -<div class="section"><p>XML Catalog entries can be used in various situations. For example, -you are working on an XML file on your main desktop computer and point its <samp class="codeph">schemaLocation</samp> towards -a schema called <samp class="codeph">c:\MySchema.xsd</samp>. You then save it to your -laptop computer so you can work on it later. When you open the file on your -laptop, however, you encounter a problem - the XML editor cannot find the <samp class="codeph">MySchema.xsd</samp> schema -because it is actually installed on your D drive. You will have to edit the <samp class="codeph">schemaLocation</samp> to -point to <samp class="codeph">d:\MySchema.xsd</samp>. When you have finished editing -the XML file and are ready to publish it on the Web, you will need to edit -the URI again so that it points to a resource that is accessible on the Web. -By now, the problem is obvious. A URI used within an XML file is not as portable -as you would like it to be. To avoid making frequent changes to your XML document, -you can use the XML Catalog.</p> -<p>An XML Catalog entry is used by an XML -processor when resolving entity references. You can provide rules to the catalog -to specify how entities should be resolved. If you consider the preceding -example, you could specify a rule that redirects an Internet resource reference -(for example, <samp class="codeph">"http://www.ibm.com/published-schemas/MySchema.xsd"</samp>) -so that it points to a resource on the developer's local machine (for example, - <samp class="codeph">"file:///C:/MySchema.xsd"</samp>). Now, instead of frequently editing -XML documents to update the URIs (especially when there are many documents -in your project), you only need to update a single rule in your XML Catalog.</p> -<p>The -following instructions were written for the Resource perspective, but they -will also work in many other perspectives.</p> -<p>To add an entry to the XML -Catalog, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open the XML file that you want to associate with a DTD or XML -schema.</span></li> - -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Catalog</span></span>.</span> -</li> - -<li class="stepexpand"><span>The <span class="uicontrol">XML Catalog Entries</span> field contains -a list of any user-defined and plug-in defined catalog entries.</span> -<ol type="a"> -<li><span>Select any entry to see details about it in the <span class="uicontrol">Details</span> field. </span> -</li> - -<li><span>Click <span class="uicontrol">Add</span> to create a new catalog entry.</span> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>In the <span class="uicontrol">URI</span> field, type the location of the -DTD or XML schema or browse for it.</span></li> - -<li class="stepexpand"><span>If you specified a DTD in the <span class="uicontrol">URI</span> field, -you can select either <span class="uicontrol">Public ID</span> or <span class="uicontrol">System -ID</span> from the <span class="uicontrol">Key Type</span> field.</span> If -you select <span class="uicontrol">Public ID,</span> the value you enter in the <span class="uicontrol">Key</span> field -should be the same as the Public ID in the XML file's DOCTYPE declaration. -If you select <span class="uicontrol">System ID</span>, the value you enter should -correspond to the System ID in an XML file's DOCTYPE declaration.</li> - -<li class="stepexpand"><span>If you specified an XML schema in the <span class="uicontrol">URI</span> field, -you can select either <span class="uicontrol">Namespace Name</span> or <span class="uicontrol">Schema -Location</span> from the <span class="uicontrol">Key Type</span> field.</span> - If the schema defines a target namespace, it will automatically appear -in the <span class="uicontrol">Key</span> field. Otherwise, you can enter the schema -location in the <span class="uicontrol">Key</span> field.</li> - -<li class="stepexpand"><span>Select the <span class="uicontrol">Specify alternative Web address</span> check -box if you want to be able to specify an alternate Web address for the resource.</span> - This Web address is used when an XML instance is generated from this -catalog entry. <strong>Note</strong>: This option is only available if you select <span class="uicontrol">Public -ID</span> (for a DTD) or <span class="uicontrol">Namespace Name</span> (for -a schema) in the <span class="uicontrol">Key type</span> field.</li> - -<li class="stepexpand"><span>If you want to refer to another catalog without importing it into -the workbench, click <span class="uicontrol">Next Catalog</span>. Type or browse for -the XML catalog you want to refer to. </span></li> - -<li class="stepexpand"><span>When you are done creating catalog entries, click <span class="uicontrol">OK</span> to -close the Add XML Catalog Entry dialog. </span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Advanced</span> if you want to import or -export any XML Catalog settings.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Export</span> if you want to persist the -XML Catalog information. Only your user specified entries will be exported.</span> -<ol type="a"> -<li><span>You will be prompted to select a project and provide a file -name to store your catalog entries in an .xmlcatalog file, which can be opened -from the Navigator view. Snce your catalog entries are stored in an .xmlcatalog -file, you can check them in and out and share them like any other project -resource. </span></li> - -<li><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Import</span> if you want to import an .xmlcatalog -file. You will be prompted to select the file you want to import.</span> -<ol type="a"> -<li><span>When you import a .xmlcatalog file, any entries in it will be -loaded into the XML Catalog (and any existing entries will be overwritten). </span> -</li> - -<li><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span> to close the Advanced XML Catalog -Preferences dialog.</span></li> - -<li class="stepexpand"><span>Make sure the XML file is in focus and click the <span class="uicontrol">Reload -dependencies</span> toolbar button. </span></li> - -</ol> - -<div class="section">The XML file is now associated with the latest version of the XML -schema or DTD.</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlcat.html" title="When an XML file is associated with a DTD or XML schema, it is bound by any structural rules contained in the DTD or XML schema. To be considered a valid XML file, a document must be accompanied by a DTD or an XML schema, and conform to all of the declarations in the DTD or the XML schema.">XML file associations with DTDs and XML schemas</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtcnst.html" title="In the Design view, when you edit an XML file that has a set of constraints (that is, a set of rules) defined by a DTD or an XML schema, you can turn the constraints on and off to provide flexibility in the way you edit, but still maintain the validity of the document periodically.">Editing with DTD or XML schema constraints</a></div> -<div><a href="../topics/tedtdoc.html" title="The DOCTYPE declaration in an XML file is used at the beginning of it to associate it with a DTD file. You can edit your DOCTYPE declaration to change the DTD file your XML file is associated with.">Editing DOCTYPE declarations</a></div> -<div><a href="../topics/tedtgram.html" title="If you make changes to a DTD file or XML schema associated with an XML file (that is currently open), click XML > Reload Dependencies to update the XML file with these changes. The changes will be reflected in the guided editing mechanisms available in the editor, such as content assist.">Updating XML files with changes made to DTDs and schemas</a></div> -<div><a href="../topics/tedtsch.html" title="Your namespace information is used to provide various information about the XML file, such as the XML schema and namespace it is associated with. If desired, you can change the schema and namespace your XML file is associated with or add a new association. Modifying any associations can impact what content is allowed in the XML file.">Editing namespace information</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.dita deleted file mode 100644 index 1fa7ac53ca..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.dita +++ /dev/null @@ -1,60 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="txprefs" xml:lang="en-us">
-<title>Defining XML editor preferences</title>
-<titlealts>
-<searchtitle>Defining XML editor preferences</searchtitle>
-</titlealts>
-<shortdesc>You can set various preferences for the Source view of the XML
-editor such as the formatter indentation style, line wrapping rules, and content
-assist rules. To apply the formatting styles, right-click in in the Source
-view for your XML document, and click <menucascade><uicontrol>Format</uicontrol>
-<uicontrol>Document</uicontrol></menucascade>.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML editor<indexterm>preferences</indexterm></indexterm>
-<indexterm>preferences<indexterm>XML editor</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To define XML preferences, perform the following steps:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML</uicontrol><uicontrol>XML Files</uicontrol><uicontrol>XML
-Source</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Enter a maximum width for formatted lines in the <uicontrol>Line
-width</uicontrol> field</cmd><info>The default value is 72.</info></step>
-<step><cmd>Select <uicontrol>Split multiple attributes each on a new line</uicontrol> to
-start every attribute on a new line.</cmd></step>
-<step><cmd>If you want blank lines to be removed when the document is formatted,
-select the <uicontrol>Clear all blank lines</uicontrol> check box. </cmd>
-<info>By default, blank lines are preserved in a formatted document.</info>
-</step>
-<step><cmd>Select <uicontrol>Indent using tabs</uicontrol> if you want to
-use tab characters (\t) as the standard formatting indentation, or, if you
-prefer to use spaces, select <uicontrol>Indent using spaces</uicontrol>.</cmd>
-</step>
-<step><cmd>You can also specify the <uicontrol>Indentation size</uicontrol> which
-is the number of tabs or space characters used for formatting indentation.</cmd>
-</step>
-<step><cmd>You can specify certain characters ('<' is default) that will
-cause the content assist list to pop up automatically. Ensure the <uicontrol>Automatically
-make suggestions</uicontrol> check box is selected and specify the characters
-in the <uicontrol>Prompt when these characters are inserted</uicontrol> field. </cmd>
-</step>
-<step><cmd>If you select <b>Strict</b> from the <b>Suggestion strategy</b> list,
-suggestions that are grammatically valid will be shown first (with bold icons)
-in the content assist list. Other suggestions that are applicable to the element
-scope, but not grammatically valid, will be shown below them with a de-emphasized
-icon. The default value for this field is <b>Strict</b>.</cmd></step>
-<step><cmd>The <uicontrol>Use inferred grammar in absence of DTD/Schema</uicontrol> check
-box is selected by default. </cmd><info>If this box is selected, when you
-have an XML file that is not associated with a DTD or XML schema, you will
-still be able to get content assist - the tool will infer what should come
-next in your file based on the existing content.</info></step>
-<step><cmd>Click <uicontrol>Apply</uicontrol> and then <uicontrol>OK</uicontrol> to
-save your changes.</cmd></step>
-</steps>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html deleted file mode 100644 index c14d8f95c8..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txprefs.html +++ /dev/null @@ -1,91 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Defining XML editor preferences" /> -<meta name="abstract" content="You can set various preferences for the Source view of the XML editor such as the formatter indentation style, line wrapping rules, and content assist rules. To apply the formatting styles, right-click in in the Source view for your XML document, and click Format > Document." /> -<meta name="description" content="You can set various preferences for the Source view of the XML editor such as the formatter indentation style, line wrapping rules, and content assist rules. To apply the formatting styles, right-click in in the Source view for your XML document, and click Format > Document." /> -<meta content="XML editor, setting, line wrapping rules, content assist rules, indentation style" name="DC.subject" /> -<meta content="XML editor, setting, line wrapping rules, content assist rules, indentation style" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txprefs" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Defining XML editor preferences</title> -</head> -<body id="txprefs"><a name="txprefs"><!-- --></a> - - -<h1 class="topictitle1">Defining XML editor preferences</h1> - - - - -<div><p>You can set various preferences for the Source view of the XML -editor such as the formatter indentation style, line wrapping rules, and content -assist rules. To apply the formatting styles, right-click in in the Source -view for your XML document, and click <span class="menucascade"><span class="uicontrol">Format</span> - > <span class="uicontrol">Document</span></span>.</p> - -<div class="section"><p>To define XML preferences, perform the following steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML</span> > <span class="uicontrol">XML Files</span> > <span class="uicontrol">XML -Source</span></span>.</span></li> - -<li class="stepexpand"><span>Enter a maximum width for formatted lines in the <span class="uicontrol">Line -width</span> field</span> The default value is 72.</li> - -<li class="stepexpand"><span>Select <span class="uicontrol">Split multiple attributes each on a new line</span> to -start every attribute on a new line.</span></li> - -<li class="stepexpand"><span>If you want blank lines to be removed when the document is formatted, -select the <span class="uicontrol">Clear all blank lines</span> check box. </span> - By default, blank lines are preserved in a formatted document. -</li> - -<li class="stepexpand"><span>Select <span class="uicontrol">Indent using tabs</span> if you want to -use tab characters (\t) as the standard formatting indentation, or, if you -prefer to use spaces, select <span class="uicontrol">Indent using spaces</span>.</span> -</li> - -<li class="stepexpand"><span>You can also specify the <span class="uicontrol">Indentation size</span> which -is the number of tabs or space characters used for formatting indentation.</span> -</li> - -<li class="stepexpand"><span>You can specify certain characters ('<' is default) that will -cause the content assist list to pop up automatically. Ensure the <span class="uicontrol">Automatically -make suggestions</span> check box is selected and specify the characters -in the <span class="uicontrol">Prompt when these characters are inserted</span> field. </span> -</li> - -<li class="stepexpand"><span>If you select <strong>Strict</strong> from the <strong>Suggestion strategy</strong> list, -suggestions that are grammatically valid will be shown first (with bold icons) -in the content assist list. Other suggestions that are applicable to the element -scope, but not grammatically valid, will be shown below them with a de-emphasized -icon. The default value for this field is <strong>Strict</strong>.</span></li> - -<li class="stepexpand"><span>The <span class="uicontrol">Use inferred grammar in absence of DTD/Schema</span> check -box is selected by default. </span> If this box is selected, when you -have an XML file that is not associated with a DTD or XML schema, you will -still be able to get content assist - the tool will infer what should come -next in your file based on the existing content.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Apply</span> and then <span class="uicontrol">OK</span> to -save your changes.</span></li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.dita b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.dita deleted file mode 100644 index 15a6bda6ac..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.dita +++ /dev/null @@ -1,41 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="txsityp" xml:lang="en-us">
-<title>Using xsi:type</title>
-<titlealts>
-<searchtitle>Using xsi:type</searchtitle>
-</titlealts>
-<shortdesc>If you have elements in your XML file whose type is a complex type,
-xsi:type support in the XML editor lets you choose between the complex type
-and any other complex types derived from it.</shortdesc>
-<taskbody>
-<context><p>The XML Schema specification allows you to derive types by extension.
-For example, you have an XML schema and you create a complex type for it called
- <userinput>Address</userinput>. You then add some basic elements to <userinput>Address</userinput>,
-such as <userinput>streetName</userinput> and <userinput>city</userinput>.</p><p>After
-this, you derive (by extension) two new complex types from <userinput>Address</userinput> - <userinput>USAddress</userinput> and <userinput>UKAddress</userinput
-> You add a new element to <userinput>USAddress</userinput> called <userinput>state</userinput>,
-and also a new element to <userinput>UKAddress</userinput> called <userinput>postcode</userinput>.</p><p>After
-you have done this, you create two more elements - <userinput>billTo</userinput> and <userinput>shipTo</userinput> -
-as <systemoutput>Address</systemoutput> types.</p><p>When you create an XML
-instance document for an element such as <systemoutput>billTo</systemoutput> or
- <userinput>Address</userinput>, an xsi:type attribute will automatically
-be added to it. For example:</p><codeblock><billTo xsi:type="ipo:Address"></codeblock><p>The
-xsi:type attribute is used to identify derived complex types (as well as complex
-types that have been derived from).</p><p>In the Design view of the XML editor,
-a list will be available, letting you select the appropriate type definition
-(<uicontrol>Address</uicontrol>, <uicontrol>USAddress</uicontrol>, or <uicontrol>UKAddress</uicontrol>).
-The guided editing for the content model will reflect the type definition
-that you choose. For example, if you select <uicontrol>USAddress</uicontrol> ,
-your <codeph>billTo</codeph> element can contain a <codeph>state</codeph> element,
-but it cannot contain a <codeph>postcode</codeph> element.</p><p>The XML example
-"Editing and validating XML files" demonstrates <b>xsi:type</b> support.</p><p>For
-more information about xsi:type, refer to the <b>Using Derived Types in Instance
-Documents</b> section in <xref format="html" href="http://www.w3.org/TR/xmlschema-0/#UseDerivInInstDocs"
-scope="external">XML Schema Part 0: Primer.</xref></p><p>For more information
-about validation semantics when xsi:type is used, refer to the <b>Schema-Related
-Markup in Documents Being Validated</b> section in <xref format="html" href="http://www.w3.org/TR/xmlschema-1/#xsi_type"
-scope="external">XML Schema Part 1: Structures</xref> </p></context>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html b/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html deleted file mode 100644 index 87ed2c68f7..0000000000 --- a/docs/org.eclipse.wst.xmleditor.doc.user/topics/txsityp.html +++ /dev/null @@ -1,70 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Using xsi:type" /> -<meta name="abstract" content="If you have elements in your XML file whose type is a complex type, xsi:type support in the XML editor lets you choose between the complex type and any other complex types derived from it." /> -<meta name="description" content="If you have elements in your XML file whose type is a complex type, xsi:type support in the XML editor lets you choose between the complex type and any other complex types derived from it." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="txsityp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Using xsi:type</title> -</head> -<body id="txsityp"><a name="txsityp"><!-- --></a> - - -<h1 class="topictitle1">Using xsi:type</h1> - - - -<div><p>If you have elements in your XML file whose type is a complex type, -xsi:type support in the XML editor lets you choose between the complex type -and any other complex types derived from it.</p> - -<div class="section"><p>The XML Schema specification allows you to derive types by extension. -For example, you have an XML schema and you create a complex type for it called - <kbd class="userinput">Address</kbd>. You then add some basic elements to <kbd class="userinput">Address</kbd>, -such as <kbd class="userinput">streetName</kbd> and <kbd class="userinput">city</kbd>.</p> -<p>After -this, you derive (by extension) two new complex types from <kbd class="userinput">Address</kbd> - <kbd class="userinput">USAddress</kbd> and <kbd class="userinput">UKAddress</kbd> You add a new element to <kbd class="userinput">USAddress</kbd> called <kbd class="userinput">state</kbd>, -and also a new element to <kbd class="userinput">UKAddress</kbd> called <kbd class="userinput">postcode</kbd>.</p> -<p>After -you have done this, you create two more elements - <kbd class="userinput">billTo</kbd> and <kbd class="userinput">shipTo</kbd> - -as <tt class="sysout">Address</tt> types.</p> -<p>When you create an XML -instance document for an element such as <tt class="sysout">billTo</tt> or - <kbd class="userinput">Address</kbd>, an xsi:type attribute will automatically -be added to it. For example:</p> -<pre><billTo xsi:type="ipo:Address"></pre> -<p>The -xsi:type attribute is used to identify derived complex types (as well as complex -types that have been derived from).</p> -<p>In the Design view of the XML editor, -a list will be available, letting you select the appropriate type definition -(<span class="uicontrol">Address</span>, <span class="uicontrol">USAddress</span>, or <span class="uicontrol">UKAddress</span>). -The guided editing for the content model will reflect the type definition -that you choose. For example, if you select <span class="uicontrol">USAddress</span> , -your <samp class="codeph">billTo</samp> element can contain a <samp class="codeph">state</samp> element, -but it cannot contain a <samp class="codeph">postcode</samp> element.</p> -<p>The XML example -"Editing and validating XML files" demonstrates <strong>xsi:type</strong> support.</p> -<p>For -more information about xsi:type, refer to the <strong>Using Derived Types in Instance -Documents</strong> section in <a href="http://www.w3.org/TR/xmlschema-0/#UseDerivInInstDocs" target="_blank">XML Schema Part 0: Primer.</a></p> -<p>For more information -about validation semantics when xsi:type is used, refer to the <strong>Schema-Related -Markup in Documents Being Validated</strong> section in <a href="http://www.w3.org/TR/xmlschema-1/#xsi_type" target="_blank">XML Schema Part 1: Structures</a> </p> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.cvsignore b/docs/org.eclipse.wst.xsdeditor.doc.user/.cvsignore deleted file mode 100644 index 41662288a7..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/.cvsignore +++ /dev/null @@ -1,4 +0,0 @@ -build.xml -org.eclipse.wst.xsdeditor.doc.user_1.0.0.jar -temp -DitaLink.cat
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.project b/docs/org.eclipse.wst.xsdeditor.doc.user/.project deleted file mode 100644 index 82170b5d7c..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.wst.xsdeditor.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.core.resources.prefs b/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.core.resources.prefs deleted file mode 100644 index afa5c91352..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.core.resources.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -encoding/<project>=ISO-8859-1 diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.jdt.core.prefs b/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.jdt.core.prefs deleted file mode 100644 index 2dd8b5cef1..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.jdt.core.prefs +++ /dev/null @@ -1,80 +0,0 @@ -#Sun Apr 16 14:37:21 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.jdt.core.builder.cleanOutputFolder=clean -org.eclipse.jdt.core.builder.duplicateResourceTask=warning -org.eclipse.jdt.core.builder.invalidClasspath=ignore -org.eclipse.jdt.core.builder.resourceCopyExclusionFilter=*.launch -org.eclipse.jdt.core.circularClasspath=error -org.eclipse.jdt.core.classpath.exclusionPatterns=enabled -org.eclipse.jdt.core.classpath.multipleOutputLocations=enabled -org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=disabled -org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.2 -org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve -org.eclipse.jdt.core.compiler.compliance=1.4 -org.eclipse.jdt.core.compiler.debug.lineNumber=generate -org.eclipse.jdt.core.compiler.debug.localVariable=generate -org.eclipse.jdt.core.compiler.debug.sourceFile=generate -org.eclipse.jdt.core.compiler.doc.comment.support=enabled -org.eclipse.jdt.core.compiler.maxProblemPerUnit=100 -org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning -org.eclipse.jdt.core.compiler.problem.assertIdentifier=warning -org.eclipse.jdt.core.compiler.problem.autoboxing=ignore -org.eclipse.jdt.core.compiler.problem.deprecation=warning -org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedCode=disabled -org.eclipse.jdt.core.compiler.problem.deprecationWhenOverridingDeprecatedMethod=enabled -org.eclipse.jdt.core.compiler.problem.discouragedReference=ignore -org.eclipse.jdt.core.compiler.problem.emptyStatement=warning -org.eclipse.jdt.core.compiler.problem.enumIdentifier=warning -org.eclipse.jdt.core.compiler.problem.fieldHiding=ignore -org.eclipse.jdt.core.compiler.problem.finalParameterBound=ignore -org.eclipse.jdt.core.compiler.problem.finallyBlockNotCompletingNormally=error -org.eclipse.jdt.core.compiler.problem.forbiddenReference=error -org.eclipse.jdt.core.compiler.problem.hiddenCatchBlock=warning -org.eclipse.jdt.core.compiler.problem.incompatibleNonInheritedInterfaceMethod=warning -org.eclipse.jdt.core.compiler.problem.incompleteEnumSwitch=ignore -org.eclipse.jdt.core.compiler.problem.indirectStaticAccess=error -org.eclipse.jdt.core.compiler.problem.invalidJavadoc=ignore -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsDeprecatedRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsNotVisibleRef=enabled -org.eclipse.jdt.core.compiler.problem.invalidJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.localVariableHiding=ignore -org.eclipse.jdt.core.compiler.problem.methodWithConstructorName=error -org.eclipse.jdt.core.compiler.problem.missingDeprecatedAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocComments=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocCommentsVisibility=public -org.eclipse.jdt.core.compiler.problem.missingJavadocTags=ignore -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsOverriding=enabled -org.eclipse.jdt.core.compiler.problem.missingJavadocTagsVisibility=private -org.eclipse.jdt.core.compiler.problem.missingOverrideAnnotation=ignore -org.eclipse.jdt.core.compiler.problem.missingSerialVersion=warning -org.eclipse.jdt.core.compiler.problem.noEffectAssignment=error -org.eclipse.jdt.core.compiler.problem.noImplicitStringConversion=warning -org.eclipse.jdt.core.compiler.problem.nonExternalizedStringLiteral=ignore -org.eclipse.jdt.core.compiler.problem.overridingPackageDefaultMethod=warning -org.eclipse.jdt.core.compiler.problem.possibleAccidentalBooleanAssignment=warning -org.eclipse.jdt.core.compiler.problem.specialParameterHidingField=enabled -org.eclipse.jdt.core.compiler.problem.staticAccessReceiver=error -org.eclipse.jdt.core.compiler.problem.suppressWarnings=enabled -org.eclipse.jdt.core.compiler.problem.syntheticAccessEmulation=warning -org.eclipse.jdt.core.compiler.problem.typeParameterHiding=ignore -org.eclipse.jdt.core.compiler.problem.uncheckedTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.undocumentedEmptyBlock=ignore -org.eclipse.jdt.core.compiler.problem.unhandledWarningToken=warning -org.eclipse.jdt.core.compiler.problem.unnecessaryElse=ignore -org.eclipse.jdt.core.compiler.problem.unnecessaryTypeCheck=error -org.eclipse.jdt.core.compiler.problem.unqualifiedFieldAccess=ignore -org.eclipse.jdt.core.compiler.problem.unsafeTypeOperation=warning -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownException=ignore -org.eclipse.jdt.core.compiler.problem.unusedDeclaredThrownExceptionWhenOverriding=disabled -org.eclipse.jdt.core.compiler.problem.unusedImport=error -org.eclipse.jdt.core.compiler.problem.unusedLabel=error -org.eclipse.jdt.core.compiler.problem.unusedLocal=error -org.eclipse.jdt.core.compiler.problem.unusedParameter=ignore -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenImplementingAbstract=disabled -org.eclipse.jdt.core.compiler.problem.unusedParameterWhenOverridingConcrete=disabled -org.eclipse.jdt.core.compiler.problem.unusedPrivateMember=error -org.eclipse.jdt.core.compiler.problem.varargsArgumentNeedCast=warning -org.eclipse.jdt.core.compiler.source=1.3 -org.eclipse.jdt.core.incompatibleJDKLevel=ignore -org.eclipse.jdt.core.incompleteClasspath=error diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.jdt.ui.prefs b/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.jdt.ui.prefs deleted file mode 100644 index ef2ac6532b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.jdt.ui.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:39 EDT 2006 -eclipse.preferences.version=1 -internal.default.compliance=default diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs b/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs deleted file mode 100644 index c59368c5e1..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.ltk.core.refactoring.prefs +++ /dev/null @@ -1,3 +0,0 @@ -#Tue Apr 04 03:36:32 EDT 2006 -eclipse.preferences.version=1 -org.eclipse.ltk.core.refactoring.enable.project.refactoring.history=false diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.pde.prefs b/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.pde.prefs deleted file mode 100644 index f724958463..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/.settings/org.eclipse.pde.prefs +++ /dev/null @@ -1,15 +0,0 @@ -#Sun Apr 16 14:05:29 EDT 2006 -compilers.p.build=0 -compilers.p.deprecated=1 -compilers.p.illegal-att-value=0 -compilers.p.no-required-att=0 -compilers.p.not-externalized-att=0 -compilers.p.unknown-attribute=0 -compilers.p.unknown-class=0 -compilers.p.unknown-element=0 -compilers.p.unknown-resource=0 -compilers.p.unresolved-ex-points=0 -compilers.p.unresolved-import=0 -compilers.p.unused-element-or-attribute=0 -compilers.use-project=true -eclipse.preferences.version=1 diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/DocBuild.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/DocBuild.xml deleted file mode 100644 index b75422b4fb..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/DocBuild.xml +++ /dev/null @@ -1,59 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<!-- - - This script build the Help plug-in by transforming the DITA source files into HTML. - - To use this script, you must install DITA-OT on your machine in the directory - defined by the dita.ot.dir property. - - Run the default target after you edit the DITA source files to regenerate the HTML. - - To customize this script for other Help plug-ins, modify the value of the args.input property - to be the DITA map file for the plug-in. - - NOTE: This script assumes that links to sibling Help plug-ins have scope="peer", otherwise the - output directory structure will be shifted incorrectly. - - NOTE: This script assumes that you hand code your plugin.xml file in myplugin.xml. This file - will be copied over the generated plugin.xml which is currently not being generated correctly - by DITA-OT. - - ChangeLog: - 2006-04-05 Arthur Ryman <ryman@ca.ibm.com> - - Created. - ---> -<project name="eclipsehelp" default="all"> - - <property name="dita.ot.dir" location="C:/DITA-OT1.2.2" /> - - <path id="dost.class.path"> - <pathelement location="${dita.ot.dir}${file.separator}lib${file.separator}dost.jar" /> - </path> - - <taskdef name="integrate" classname="org.dita.dost.platform.IntegratorTask"> - <classpath refid="dost.class.path" /> - </taskdef> - <target name="all" depends="integrate, eclipsehelp"> - </target> - <target name="integrate"> - <integrate ditadir="${dita.ot.dir}" /> - </target> - - <!-- revise below here --> - <target name="eclipsehelp"> - <ant antfile="${dita.ot.dir}${file.separator}conductor.xml" target="init" dir="${dita.ot.dir}"> - <property name="args.copycss" value="no" /> - <property name="args.csspath" value="org.eclipse.wst.doc.user" /> - <property name="args.eclipse.provider" value="Eclipse.org" /> - <property name="args.eclipse.version" value="1.5.0" /> - <property name="args.input" location="XSDLeditorrel.ditamap" /> - <property name="clean.temp" value="true" /> - <property name="dita.extname" value=".dita" /> - <property name="dita.temp.dir" location="temp" /> - <property name="output.dir" location=".." /> - <property name="transtype" value="eclipsehelp" /> - </ant> - <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" /> - </target> -</project> diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.xsdeditor.doc.user/META-INF/MANIFEST.MF deleted file mode 100644 index 2aeb2f5ba6..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,7 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %Plugin.name -Bundle-SymbolicName: org.eclipse.wst.xsdeditor.doc.user; singleton:=true -Bundle-Version: 1.0.300.qualifier -Bundle-Vendor: %Bundle-Vendor.0 -Bundle-Localization: plugin diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDLeditorrel.ditamap b/docs/org.eclipse.wst.xsdeditor.doc.user/XSDLeditorrel.ditamap deleted file mode 100644 index a13ee00271..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDLeditorrel.ditamap +++ /dev/null @@ -1,158 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
- <!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
-<map>
-<topicgroup collection-type="family">
-<topicref href="topics/tcxmlsch.dita" navtitle="Creating XML schemas"></topicref>
-<topicref href="topics/tedtschm.dita" linking="targetonly" navtitle="Editing XML schema properties">
-</topicref>
-<topicref href="topics/cxmlsced.dita" id="xsdconcepts" linking="targetonly"
-navtitle="XML schema editor"></topicref>
-<topicref href="topics/tvdtschm.dita" linking="targetonly" navtitle="Validating XML schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/tedtschm.dita" linking="targetonly" navtitle="Editing XML schema properties">
-</topicref>
-<topicref href="topics/cxmlsced.dita" linking="targetonly" navtitle="XML schema editor">
-</topicref>
-<topicref href="topics/tvdtschm.dita" linking="targetonly" navtitle="Validating XML schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/timpschm.dita" navtitle="Importing XML schemas"></topicref>
-<topicref href="topics/tedtschm.dita" linking="targetonly" navtitle="Editing XML schema properties">
-</topicref>
-<topicref href="topics/cxmlsced.dita" linking="targetonly" navtitle="XML schema editor">
-</topicref>
-<topicref href="topics/tvdtschm.dita" linking="targetonly" navtitle="Validating XML schemas">
-</topicref>
-<topicref href="topics/taddimpt.dita" linking="targetonly" navtitle="Adding import elements">
-</topicref>
-<topicref href="topics/taddincl.dita" linking="targetonly" navtitle="Adding include elements">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/tnavsrc.dita" navtitle="Navigating XML schemas"></topicref>
-<topicref href="topics/cxmlsced.dita" linking="targetonly" navtitle="XML schema editor">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/cxmlsced.dita" linking="normal" navtitle="XML schema editor">
-</topicref>
-<topicref href="topics/tcxmlsch.dita" linking="targetonly" navtitle="Creating XML schemas">
-</topicref>
-<topicref href="topics/tedtschm.dita" linking="targetonly" navtitle="Editing XML schema properties">
-</topicref>
-<topicref href="topics/tvdtschm.dita" linking="targetonly" navtitle="Validating XML schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddcmxt.dita" navtitle="Adding complex types"></topicref>
-<topicref href="topics/taddcmod.dita" linking="targetonly" navtitle="Adding content models">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddglem.dita" navtitle="Adding global elements"></topicref>
-<topicref href="topics/taddcmod.dita" linking="targetonly" navtitle="Adding content models">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddelm.dita" navtitle="Adding elements"></topicref>
-<topicref href="topics/taddcmod.dita" linking="targetonly" navtitle="Adding content models">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddelmr.dita" navtitle="Adding element references">
-</topicref>
-<topicref href="topics/taddglem.dita" navtitle="Adding global elements"></topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddgrup.dita" navtitle="Adding groups"></topicref>
-<topicref href="topics/taddgrpr.dita" linking="targetonly" navtitle="Adding group references">
-</topicref>
-<topicref href="topics/taddcmod.dita" linking="targetonly" navtitle="Adding content models">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddgrpr.dita" linking="normal" navtitle="Adding group references">
-</topicref>
-<topicref href="topics/taddgrup.dita" linking="targetonly" navtitle="Adding groups">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddimpt.dita" navtitle="Adding import elements"></topicref>
-<topicref href="topics/taddincl.dita" navtitle="Adding include elements">
-</topicref>
-<topicref href="topics/taddrdfn.dita" navtitle="Adding redefine elements">
-</topicref>
-<topicref href="topics/rnmspc.dita" linking="targetonly" navtitle="XML namespaces">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/tvdtschm.dita" navtitle="Validating XML schemas"></topicref>
-<topicref href="topics/tcxmlsch.dita" linking="targetonly" navtitle="Creating XML schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/tedtschm.dita" linking="targetonly" navtitle="Editing XML schema properties">
-</topicref>
-<topicref href="topics/tcxmlsch.dita" linking="targetonly" navtitle="Creating XML schemas">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/rrefintg.dita" navtitle="Referential integrity in the XML schema editor">
-</topicref>
-<topicref href="topics/cxmlsced.dita" linking="targetonly" navtitle="XML schema editor">
-</topicref>
-<topicref href="topics/tedtschm.dita" linking="targetonly" navtitle="Editing XML schema properties">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/rnmspc.dita" navtitle="XML namespaces"></topicref>
-<topicref href="topics/tedtpref.dita" linking="targetonly" navtitle="Editing XML schema file preferences">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddsmpt.dita" navtitle="Adding simple types"></topicref>
-<topicref href="topics/taddreg.dita" navtitle="Adding pattern facets to simple types">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddcmod.dita" navtitle="Adding content models"></topicref>
-<topicref href="topics/taddanye.dita" linking="targetonly" navtitle="Adding an any element">
-</topicref>
-<topicref href="topics/taddelm.dita" linking="targetonly" navtitle="Adding elements">
-</topicref>
-<topicref href="topics/taddelmr.dita" linking="targetonly" navtitle="Adding element references">
-</topicref>
-<topicref href="topics/taddgrpr.dita" linking="targetonly" navtitle="Adding group references">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/tdelscmp.dita" navtitle="Deleting XML schema components">
-</topicref>
-<topicref href="topics/rrefintg.dita" navtitle="Referential integrity in the XML schema editor">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddelm.dita" linking="sourceonly" navtitle="Adding elements">
-</topicref>
-<topicref href="topics/taddelmr.dita" linking="targetonly" navtitle="Adding element references">
-</topicref>
-<topicref href="topics/taddanye.dita" linking="targetonly" navtitle="Adding an any element">
-</topicref>
-<topicref href="topics/taddglba.dita" linking="targetonly" navtitle="Adding global attributes">
-</topicref>
-</topicgroup>
-<topicgroup collection-type="family">
-<topicref href="topics/taddelmr.dita" linking="sourceonly" navtitle="Adding element references">
-</topicref>
-<topicref href="topics/taddelm.dita" linking="targetonly" navtitle="Adding elements">
-</topicref>
-<topicref href="topics/taddanye.dita" linking="targetonly" navtitle="Adding an any element">
-</topicref>
-<topicref href="topics/taddglba.dita" linking="targetonly" navtitle="Adding global attributes">
-</topicref>
-</topicgroup>
-</map>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDLeditorrel.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/XSDLeditorrel.xml deleted file mode 100644 index cbac6ffeeb..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDLeditorrel.xml +++ /dev/null @@ -1,68 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<?NLS TYPE="org.eclipse.help.toc"?> - -<toc topic="topics/tcxmlsch.html"> -<topic label="Creating XML schemas" href="topics/tcxmlsch.html"/> -<topic label="Editing XML schema properties" href="topics/tedtschm.html"/> -<topic label="XML schema editor" href="topics/cxmlsced.html"/> -<topic label="Validating XML schemas" href="topics/tvdtschm.html"/> -<topic label="Editing XML schema properties" href="topics/tedtschm.html"/> -<topic label="XML schema editor" href="topics/cxmlsced.html"/> -<topic label="Validating XML schemas" href="topics/tvdtschm.html"/> -<topic label="Importing XML schemas" href="topics/timpschm.html"/> -<topic label="Editing XML schema properties" href="topics/tedtschm.html"/> -<topic label="XML schema editor" href="topics/cxmlsced.html"/> -<topic label="Validating XML schemas" href="topics/tvdtschm.html"/> -<topic label="Adding import elements" href="topics/taddimpt.html"/> -<topic label="Adding include elements" href="topics/taddincl.html"/> -<topic label="Navigating XML schemas" href="topics/tnavsrc.html"/> -<topic label="XML schema editor" href="topics/cxmlsced.html"/> -<topic label="XML schema editor" href="topics/cxmlsced.html"/> -<topic label="Creating XML schemas" href="topics/tcxmlsch.html"/> -<topic label="Editing XML schema properties" href="topics/tedtschm.html"/> -<topic label="Validating XML schemas" href="topics/tvdtschm.html"/> -<topic label="Adding complex types" href="topics/taddcmxt.html"/> -<topic label="Adding content models" href="topics/taddcmod.html"/> -<topic label="Adding global elements" href="topics/taddglem.html"/> -<topic label="Adding content models" href="topics/taddcmod.html"/> -<topic label="Adding elements" href="topics/taddelm.html"/> -<topic label="Adding content models" href="topics/taddcmod.html"/> -<topic label="Adding element references" href="topics/taddelmr.html"/> -<topic label="Adding global elements" href="topics/taddglem.html"/> -<topic label="Adding groups" href="topics/taddgrup.html"/> -<topic label="Adding group references" href="topics/taddgrpr.html"/> -<topic label="Adding content models" href="topics/taddcmod.html"/> -<topic label="Adding group references" href="topics/taddgrpr.html"/> -<topic label="Adding groups" href="topics/taddgrup.html"/> -<topic label="Adding import elements" href="topics/taddimpt.html"/> -<topic label="Adding include elements" href="topics/taddincl.html"/> -<topic label="Adding redefine elements" href="topics/taddrdfn.html"/> -<topic label="XML namespaces" href="topics/rnmspc.html"/> -<topic label="Validating XML schemas" href="topics/tvdtschm.html"/> -<topic label="Creating XML schemas" href="topics/tcxmlsch.html"/> -<topic label="Editing XML schema properties" href="topics/tedtschm.html"/> -<topic label="Creating XML schemas" href="topics/tcxmlsch.html"/> -<topic label="Referential integrity in the XML schema editor" href="topics/rrefintg.html"/> -<topic label="XML schema editor" href="topics/cxmlsced.html"/> -<topic label="Editing XML schema properties" href="topics/tedtschm.html"/> -<topic label="XML namespaces" href="topics/rnmspc.html"/> -<topic label="Editing XML schema file preferences" href="topics/tedtpref.html"/> -<topic label="Adding simple types" href="topics/taddsmpt.html"/> -<topic label="Adding pattern facets to simple types" href="topics/taddreg.html"/> -<topic label="Adding content models" href="topics/taddcmod.html"/> -<topic label="Adding an any element" href="topics/taddanye.html"/> -<topic label="Adding elements" href="topics/taddelm.html"/> -<topic label="Adding element references" href="topics/taddelmr.html"/> -<topic label="Adding group references" href="topics/taddgrpr.html"/> -<topic label="Deleting XML schema components" href="topics/tdelscmp.html"/> -<topic label="Referential integrity in the XML schema editor" href="topics/rrefintg.html"/> -<topic label="Adding elements" href="topics/taddelm.html"/> -<topic label="Adding element references" href="topics/taddelmr.html"/> -<topic label="Adding an any element" href="topics/taddanye.html"/> -<topic label="Adding global attributes" href="topics/taddglba.html"/> -<topic label="Adding element references" href="topics/taddelmr.html"/> -<topic label="Adding elements" href="topics/taddelm.html"/> -<topic label="Adding an any element" href="topics/taddanye.html"/> -<topic label="Adding global attributes" href="topics/taddglba.html"/> -</toc> diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.ditamap b/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.ditamap deleted file mode 100644 index 834bcf70b7..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.ditamap +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN"
- "map.dtd">
-<map collection-type="sequence" id="wstxsdtoc" title="XML schemas">
-<topicref href="topics/cworkXSD.dita" linking="sourceonly" navtitle="Working with XML schemas (XSDs)">
-<topicref href="topics/tcxmlsch.dita" navtitle="Creating XML schemas"></topicref>
-<topicref href="topics/rlimitations_slushXSD.dita" navtitle="XSD Slush file"
-toc="no"></topicref>
-<topicref href="topics/timpschm.dita" navtitle="Importing an XML schema">
-</topicref>
-<topicref href="topics/tnavsrc.dita" navtitle="Navigating XML schemas"></topicref>
-<topicref href="topics/trefactrXSD.dita" navtitle="Refactoring in XML Schemas">
-</topicref>
-<topicref href="topics/tedtpref.dita" navtitle="Editing XML schema editor preferences">
-</topicref>
-<topicref href="topics/tedtschm.dita" linking="none" navtitle="Editing XML schema properties">
-<topicref href="topics/cxmlsced.dita" id="xsdconcepts" navtitle="XML schema editor">
-</topicref>
-<topicref href="topics/taddagrp.dita" navtitle="Adding an attribute group">
-</topicref>
-<topicref href="topics/taddcmxt.dita" navtitle="Adding a complex type"></topicref>
-<topicref href="topics/taddcmod.dita" navtitle="Adding a content model">
-<topicref href="topics/taddanye.dita" navtitle="Adding an any element"></topicref>
-<topicref href="topics/taddelm.dita" navtitle="Adding an element"></topicref>
-<topicref href="topics/taddelmr.dita" navtitle="Adding an element reference">
-</topicref>
-<topicref href="topics/taddgrpr.dita" navtitle="Adding a group reference">
-</topicref>
-</topicref>
-<topicref href="topics/taddglba.dita" navtitle="Adding a global attribute">
-</topicref>
-<topicref href="topics/taddglem.dita" navtitle="Adding a global element">
-</topicref>
-<topicref href="topics/taddgrup.dita" navtitle="Adding a group"></topicref>
-<topicref href="topics/taddimpt.dita" navtitle="Adding an import element">
-</topicref>
-<topicref href="topics/taddincl.dita" navtitle="Adding an include element">
-</topicref>
-<topicref href="topics/taddrdfn.dita" navtitle="Adding a redefine element">
-</topicref>
-<topicref href="topics/taddsmpt.dita" navtitle="Adding a simple type">
-<topicref href="topics/taddreg.dita" navtitle="Adding a pattern facet to a simple type">
-</topicref>
-</topicref>
-</topicref>
-<topicref href="topics/rxsdicons.dita" id="xsdicons" navtitle="Icons used in the XML schema editor">
-</topicref>
-<topicref href="topics/tdelscmp.dita" navtitle="Deleting XML schema components">
-<topicref href="topics/rrefintg.dita" navtitle="Referential integrity in the XML schema editor">
-</topicref>
-</topicref>
-<topicref href="topics/tvdtschm.dita" navtitle="Validating an XML schema">
-</topicref>
-<topicref href="topics/rnmspc.dita" navtitle="XML namespaces"></topicref>
-</topicref>
-</map>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml deleted file mode 100644 index cc10b1d55b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/XSDeditormap_toc.xml +++ /dev/null @@ -1,39 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<?NLS TYPE="org.eclipse.help.toc"?> - -<toc label="XML schemas" topic="topics/cworkXSD.html"> -<topic label="Working with XML schemas" href="topics/cworkXSD.html"> -<topic label="Creating XML schemas" href="topics/tcxmlsch.html"/> -<topic label="Importing XML schemas" href="topics/timpschm.html"/> -<topic label="Navigating XML schemas" href="topics/tnavsrc.html"/> -<topic label="Refactoring in XML Schema Files" href="topics/trefactrXSD.html"/> -<topic label="Editing XML schema file preferences" href="topics/tedtpref.html"/> -<topic label="Editing XML schema properties" href="topics/tedtschm.html"> -<topic label="XML schema editor" href="topics/cxmlsced.html"/> -<topic label="Adding attribute groups" href="topics/taddagrp.html"/> -<topic label="Adding complex types" href="topics/taddcmxt.html"/> -<topic label="Adding content models" href="topics/taddcmod.html"> -<topic label="Adding an any element" href="topics/taddanye.html"/> -<topic label="Adding elements" href="topics/taddelm.html"/> -<topic label="Adding element references" href="topics/taddelmr.html"/> -<topic label="Adding group references" href="topics/taddgrpr.html"/> -</topic> -<topic label="Adding global attributes" href="topics/taddglba.html"/> -<topic label="Adding global elements" href="topics/taddglem.html"/> -<topic label="Adding groups" href="topics/taddgrup.html"/> -<topic label="Adding import elements" href="topics/taddimpt.html"/> -<topic label="Adding include elements" href="topics/taddincl.html"/> -<topic label="Adding redefine elements" href="topics/taddrdfn.html"/> -<topic label="Adding simple types" href="topics/taddsmpt.html"> -<topic label="Adding pattern facets to simple types" href="topics/taddreg.html"/> -</topic> -</topic> -<topic label="Icons used in the XML schema editor" href="topics/rxsdicons.html"/> -<topic label="Deleting XML schema components" href="topics/tdelscmp.html"> -<topic label="Referential integrity in the XML schema editor" href="topics/rrefintg.html"/> -</topic> -<topic label="Validating XML schemas" href="topics/tvdtschm.html"/> -<topic label="XML namespaces" href="topics/rnmspc.html"/> -</topic> -</toc> diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/about.html b/docs/org.eclipse.wst.xsdeditor.doc.user/about.html deleted file mode 100644 index 73db36ed5a..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/build.properties b/docs/org.eclipse.wst.xsdeditor.doc.user/build.properties deleted file mode 100644 index 695623ee40..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/build.properties +++ /dev/null @@ -1,15 +0,0 @@ -bin.includes = XSDeditormap_toc.xml,\ - about.html,\ - org.eclipse.wst.xsdeditor.doc.userindex.xml,\ - images/,\ - plugin.xml,\ - topics/*.htm*,\ - index/,\ - META-INF/,\ - plugin.properties -src.includes = build.properties,\ - *.maplist,\ - *.ditamap,\ - topics/*.dita -bin.excludes = DocBuild.xml,\ - myPlugin*.xml
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/Browse.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/Browse.gif Binary files differdeleted file mode 100644 index 63211bf915..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/Browse.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/More.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/More.gif Binary files differdeleted file mode 100644 index 63211bf915..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/More.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif Binary files differdeleted file mode 100644 index da37fbad3e..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAll.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif Binary files differdeleted file mode 100644 index a39f93cdce..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAny.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif Binary files differdeleted file mode 100644 index 5280cc2904..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAnyAttribute.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif Binary files differdeleted file mode 100644 index 79d49d037b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttribute.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif Binary files differdeleted file mode 100644 index 5a8df73015..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroup.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif Binary files differdeleted file mode 100644 index b2c1db9ef4..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeGroupRef.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif Binary files differdeleted file mode 100644 index 8365af2f3c..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDAttributeRef.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif Binary files differdeleted file mode 100644 index 8af583f4bd..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDChoice.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif Binary files differdeleted file mode 100644 index 878b94f132..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDComplexType.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif Binary files differdeleted file mode 100644 index dd45f08fb1..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElement.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif Binary files differdeleted file mode 100644 index 749acfc9c9..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDElementRef.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif Binary files differdeleted file mode 100644 index 79d49d037b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalAttribute.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif Binary files differdeleted file mode 100644 index dd45f08fb1..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGlobalElement.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif Binary files differdeleted file mode 100644 index 462c2d4aa5..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroup.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif Binary files differdeleted file mode 100644 index 068987bf0b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDGroupRef.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif Binary files differdeleted file mode 100644 index 9e44ce52a9..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDImport.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif Binary files differdeleted file mode 100644 index b26c527f5e..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDInclude.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif Binary files differdeleted file mode 100644 index 56964c13a5..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDRedefine.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif Binary files differdeleted file mode 100644 index 16b8612332..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSequence.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif Binary files differdeleted file mode 100644 index 11d7958525..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleEnum.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif Binary files differdeleted file mode 100644 index a113cf45a0..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimplePattern.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif b/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif Binary files differdeleted file mode 100644 index 2e74430cc2..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/images/XSDSimpleType.gif +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/index/_v.cfs b/docs/org.eclipse.wst.xsdeditor.doc.user/index/_v.cfs Binary files differdeleted file mode 100644 index 88fa958dd6..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/index/_v.cfs +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/index/deletable b/docs/org.eclipse.wst.xsdeditor.doc.user/index/deletable Binary files differdeleted file mode 100644 index e423242b3e..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/index/deletable +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_contributions b/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_contributions deleted file mode 100644 index de9744fdc5..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_contributions +++ /dev/null @@ -1,3 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:16:38 EDT 2007
-org.eclipse.wst.xsdeditor.doc.user=org.eclipse.wst.xsdeditor.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_dependencies b/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_dependencies deleted file mode 100644 index 93c25b2d40..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_dependencies +++ /dev/null @@ -1,4 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:16:38 EDT 2007
-lucene=1.4.103.v20060601
-analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_docs b/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_docs deleted file mode 100644 index 3951dc1036..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/index/indexed_docs +++ /dev/null @@ -1,30 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:16:38 EDT 2007
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html=0
-/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html=0
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/index/segments b/docs/org.eclipse.wst.xsdeditor.doc.user/index/segments Binary files differdeleted file mode 100644 index 19b5d0c420..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/index/segments +++ /dev/null diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/myplugin.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/myplugin.xml deleted file mode 100644 index 0e38d0e22f..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/myplugin.xml +++ /dev/null @@ -1,30 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<!-- ================================================= --> -<!-- This is the plugin for declaring the help --> -<!-- contributions for using the tool. --> -<!-- ================================================= --> - -<plugin> - -<extension point="org.eclipse.help.toc"> - <toc file="XSDeditormap_toc.xml"/> - <index path="index/"/> - -</extension> - - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.wst.xsdeditor.doc.userindex.xml"/> -</extension> -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.user.maplist b/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.user.maplist deleted file mode 100644 index 626f463896..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.user.maplist +++ /dev/null @@ -1,9 +0,0 @@ -<maplist version="3.6.2">
- <nav>
- <map file="XSDeditormap_toc.ditamap"/>
- </nav>
- <link>
- <map file="XSDeditormap_toc.ditamap"/>
- <map file="XSDLeditorrel.ditamap"/>
- </link>
-</maplist>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.userindex.html b/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.userindex.html deleted file mode 100644 index 2f07600ef8..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.userindex.html +++ /dev/null @@ -1,168 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<meta name="copyright" content="(C) Copyright IBM Corporation 2007" /> -<meta name="security" content="public" /> -<meta name="Robots" content="index,follow" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta name="DC.Format" content="XHTML" /> -<!-- All rights reserved. Licensed Materials Property of IBM --> -<!-- US Government Users Restricted Rights --> -<!-- Use, duplication or disclosure restricted by --> -<!-- GSA ADP Schedule Contract with IBM Corp. --> -<link rel="stylesheet" type="text/css" href="ibmdita.css" /> -<title>Index</title> -</head> -<body> -<h1>Index</h1> -<a name="IDX0_44" href="#IDX1_44">D</a> -<a name="IDX0_50" href="#IDX1_50">P</a> -<a name="IDX0_52" href="#IDX1_52">R</a> -<a name="IDX0_58" href="#IDX1_58">X</a> -<hr></hr> -<strong><a name="IDX1_44" href="#IDX0_44">D</a></strong> -<ul class="indexlist"> -<li>dependent artifacts -<ul class="indexlist"> -<li><a href="topics/trefactrXSD.html#refactoring">refactorting XML schema files</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_50" href="#IDX0_50">P</a></strong> -<ul class="indexlist"> -<li>preferences -<ul class="indexlist"> -<li><a href="topics/tedtpref.html#tedtpref">XML schema files</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_52" href="#IDX0_52">R</a></strong> -<ul class="indexlist"> -<li>refactoring -<ul class="indexlist"> -<li><a href="topics/trefactrXSD.html#refactoring">XML schema files</a> -</li> -</ul> -</li> -<li>renaming -<ul class="indexlist"> -<li><a href="topics/trefactrXSD.html#refactoring">XML schema files</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_58" href="#IDX0_58">X</a></strong> -<ul class="indexlist"> -<li>XML namespaces -<ul class="indexlist"> -<li><a href="topics/rnmspc.html#rnmspc">overview</a> -</li> -</ul> -</li> -<li>XML schema editor -<ul class="indexlist"> -<li><a href="topics/taddanye.html#taddanye">adding an any element</a> -</li> -<li><a href="topics/taddrdfn.html#taddrdfn">adding redefine elements</a> -</li> -<li><a href="topics/taddagrp.html#taddagrp">attribute groups</a> -</li> -<li><a href="topics/rrefintg.html#rrefintg">clean up in</a> -</li> -<li><a href="topics/taddcmxt.html#taddcmxt">complex types</a> -</li> -<li><a href="topics/taddcmod.html#taddcmod">content models</a> -</li> -<li><a href="topics/tdelscmp.html#tdelscmp">deleting components</a> -</li> -<li><a href="topics/taddelmr.html#taddelmr">element references</a> -</li> -<li><a href="topics/taddelm.html#taddelm">elements</a> -</li> -<li><a href="topics/taddglba.html#taddglba">global attributes</a> -</li> -<li><a href="topics/taddglem.html#taddglem">global elements</a> -</li> -<li><a href="topics/taddgrpr.html#taddgrpr">group features</a> -</li> -<li><a href="topics/taddgrup.html#taddgrup">groups</a> -</li> -<li><a href="topics/rxsdicons.html#ricons">icons</a> -</li> -<li><a href="topics/taddimpt.html#taddimpt">import elements</a> -</li> -<li><a href="topics/taddincl.html#taddincl">include elements</a> -</li> -<li><a href="topics/cxmlsced.html#cxmlsced">overview</a> -</li> -<li><a href="topics/taddreg.html#taddreg">pattern facets</a> -</li> -<li><a href="topics/rrefintg.html#rrefintg">referential integrity</a> -</li> -<li><a href="topics/taddsmpt.html#taddsmpt">simple types</a> -</li> -<li><a href="topics/tedtschm.html#tedtschm">XML schema properties</a> -</li> -</ul> -</li> -<li>XML schema files -<ul class="indexlist"> -<li><a href="topics/taddanye.html#taddanye">adding an any element</a> -</li> -<li><a href="topics/taddrdfn.html#taddrdfn">adding redefine elements</a> -</li> -<li><a href="topics/taddagrp.html#taddagrp">attribute groups</a> -</li> -<li><a href="topics/taddcmxt.html#taddcmxt">complex types</a> -</li> -<li><a href="topics/taddcmod.html#taddcmod">content models</a> -</li> -<li><a href="topics/tcxmlsch.html#tcxmlsch">creating</a> -</li> -<li><a href="topics/tdelscmp.html#tdelscmp">deleting components</a> -</li> -<li><a href="topics/tedtpref.html#tedtpref">editing preferences</a> -</li> -<li><a href="topics/tedtschm.html#tedtschm">editing properties</a> -</li> -<li><a href="topics/taddelmr.html#taddelmr">element references</a> -</li> -<li><a href="topics/taddelm.html#taddelm">elements</a> -</li> -<li><a href="topics/taddglba.html#taddglba">global attributes</a> -</li> -<li><a href="topics/taddglem.html#taddglem">global elements</a> -</li> -<li><a href="topics/taddgrpr.html#taddgrpr">group features</a> -</li> -<li><a href="topics/taddgrup.html#taddgrup">groups</a> -</li> -<li><a href="topics/taddimpt.html#taddimpt">import elements</a> -</li> -<li><a href="topics/timpschm.html#timpschm">importing</a> -</li> -<li><a href="topics/taddincl.html#taddincl">include elements</a> -</li> -<li><a href="topics/tnavsrc.html#tnavsrc">navigating</a> -</li> -<li><a href="topics/taddreg.html#taddreg">pattern facets</a> -</li> -<li><a href="topics/taddsmpt.html#taddsmpt">simple types</a> -</li> -<li><a href="topics/tvdtschm.html#tvdtschm">validating</a> -</li> -</ul> -</li> -<li>XML schemas -<ul class="indexlist"> -<li><a href="topics/trefactrXSD.html#refactoring">editing</a> -</li> -</ul> -</li> -</ul> -</body></html> diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.userindex.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.userindex.xml deleted file mode 100644 index f143942ac8..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/org.eclipse.wst.xsdeditor.doc.userindex.xml +++ /dev/null @@ -1,166 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<index> - <entry keyword="XML schema files"> - <entry keyword="creating"> - <topic href="topics/tcxmlsch.html#tcxmlsch" title="Creating XML schemas"/> - </entry> - <entry keyword="importing"> - <topic href="topics/timpschm.html#timpschm" title="Importing XML schemas"/> - </entry> - <entry keyword="navigating"> - <topic href="topics/tnavsrc.html#tnavsrc" title="Navigating XML schemas"/> - </entry> - <entry keyword="editing preferences"> - <topic href="topics/tedtpref.html#tedtpref" title="Editing XML schema file preferences"/> - </entry> - <entry keyword="editing properties"> - <topic href="topics/tedtschm.html#tedtschm" title="Editing XML schema properties"/> - </entry> - <entry keyword="attribute groups"> - <topic href="topics/taddagrp.html#taddagrp" title="Adding attribute groups"/> - </entry> - <entry keyword="complex types"> - <topic href="topics/taddcmxt.html#taddcmxt" title="Adding complex types"/> - </entry> - <entry keyword="content models"> - <topic href="topics/taddcmod.html#taddcmod" title="Adding content models"/> - </entry> - <entry keyword="adding an any element"> - <topic href="topics/taddanye.html#taddanye" title="Adding an any element"/> - </entry> - <entry keyword="elements"> - <topic href="topics/taddelm.html#taddelm" title="Adding elements"/> - </entry> - <entry keyword="element references"> - <topic href="topics/taddelmr.html#taddelmr" title="Adding element references"/> - </entry> - <entry keyword="group features"> - <topic href="topics/taddgrpr.html#taddgrpr" title="Adding group references"/> - </entry> - <entry keyword="global attributes"> - <topic href="topics/taddglba.html#taddglba" title="Adding global attributes"/> - </entry> - <entry keyword="global elements"> - <topic href="topics/taddglem.html#taddglem" title="Adding global elements"/> - </entry> - <entry keyword="groups"> - <topic href="topics/taddgrup.html#taddgrup" title="Adding groups"/> - </entry> - <entry keyword="import elements"> - <topic href="topics/taddimpt.html#taddimpt" title="Adding import elements"/> - </entry> - <entry keyword="include elements"> - <topic href="topics/taddincl.html#taddincl" title="Adding include elements"/> - </entry> - <entry keyword="adding redefine elements"> - <topic href="topics/taddrdfn.html#taddrdfn" title="Adding redefine elements"/> - </entry> - <entry keyword="simple types"> - <topic href="topics/taddsmpt.html#taddsmpt" title="Adding simple types"/> - </entry> - <entry keyword="pattern facets"> - <topic href="topics/taddreg.html#taddreg" title="Adding pattern facets to simple types"/> - </entry> - <entry keyword="deleting components"> - <topic href="topics/tdelscmp.html#tdelscmp" title="Deleting XML schema components"/> - </entry> - <entry keyword="validating"> - <topic href="topics/tvdtschm.html#tvdtschm" title="Validating XML schemas"/> - </entry> - </entry> - <entry keyword="dependent artifacts"> - <entry keyword="refactorting XML schema files"> - <topic href="topics/trefactrXSD.html#refactoring" title="Refactoring in XML Schema Files"/> - </entry> - </entry> - <entry keyword="refactoring"> - <entry keyword="XML schema files"> - <topic href="topics/trefactrXSD.html#refactoring" title="Refactoring in XML Schema Files"/> - </entry> - </entry> - <entry keyword="renaming"> - <entry keyword="XML schema files"> - <topic href="topics/trefactrXSD.html#refactoring" title="Refactoring in XML Schema Files"/> - </entry> - </entry> - <entry keyword="XML schemas"> - <entry keyword="editing"> - <topic href="topics/trefactrXSD.html#refactoring" title="Refactoring in XML Schema Files"/> - </entry> - </entry> - <entry keyword="preferences"> - <entry keyword="XML schema files"> - <topic href="topics/tedtpref.html#tedtpref" title="Editing XML schema file preferences"/> - </entry> - </entry> - <entry keyword="XML schema editor"> - <entry keyword="XML schema properties"> - <topic href="topics/tedtschm.html#tedtschm" title="Editing XML schema properties"/> - </entry> - <entry keyword="overview"> - <topic href="topics/cxmlsced.html#cxmlsced" title="XML schema editor"/> - </entry> - <entry keyword="attribute groups"> - <topic href="topics/taddagrp.html#taddagrp" title="Adding attribute groups"/> - </entry> - <entry keyword="complex types"> - <topic href="topics/taddcmxt.html#taddcmxt" title="Adding complex types"/> - </entry> - <entry keyword="content models"> - <topic href="topics/taddcmod.html#taddcmod" title="Adding content models"/> - </entry> - <entry keyword="adding an any element"> - <topic href="topics/taddanye.html#taddanye" title="Adding an any element"/> - </entry> - <entry keyword="elements"> - <topic href="topics/taddelm.html#taddelm" title="Adding elements"/> - </entry> - <entry keyword="element references"> - <topic href="topics/taddelmr.html#taddelmr" title="Adding element references"/> - </entry> - <entry keyword="group features"> - <topic href="topics/taddgrpr.html#taddgrpr" title="Adding group references"/> - </entry> - <entry keyword="global attributes"> - <topic href="topics/taddglba.html#taddglba" title="Adding global attributes"/> - </entry> - <entry keyword="global elements"> - <topic href="topics/taddglem.html#taddglem" title="Adding global elements"/> - </entry> - <entry keyword="groups"> - <topic href="topics/taddgrup.html#taddgrup" title="Adding groups"/> - </entry> - <entry keyword="import elements"> - <topic href="topics/taddimpt.html#taddimpt" title="Adding import elements"/> - </entry> - <entry keyword="include elements"> - <topic href="topics/taddincl.html#taddincl" title="Adding include elements"/> - </entry> - <entry keyword="adding redefine elements"> - <topic href="topics/taddrdfn.html#taddrdfn" title="Adding redefine elements"/> - </entry> - <entry keyword="simple types"> - <topic href="topics/taddsmpt.html#taddsmpt" title="Adding simple types"/> - </entry> - <entry keyword="pattern facets"> - <topic href="topics/taddreg.html#taddreg" title="Adding pattern facets to simple types"/> - </entry> - <entry keyword="icons"> - <topic href="topics/rxsdicons.html#ricons" title="Icons used in the XML schema editor"/> - </entry> - <entry keyword="deleting components"> - <topic href="topics/tdelscmp.html#tdelscmp" title="Deleting XML schema components"/> - </entry> - <entry keyword="referential integrity"> - <topic href="topics/rrefintg.html#rrefintg" title="Referential integrity in the XML schema editor"/> - </entry> - <entry keyword="clean up in"> - <topic href="topics/rrefintg.html#rrefintg" title="Referential integrity in the XML schema editor"/> - </entry> - </entry> - <entry keyword="XML namespaces"> - <entry keyword="overview"> - <topic href="topics/rnmspc.html#rnmspc" title="XML namespaces"/> - </entry> - </entry> -</index>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties deleted file mode 100644 index 4b1a11a1c9..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.properties +++ /dev/null @@ -1,3 +0,0 @@ -Plugin.name = XML schema editor - -Bundle-Vendor.0 = Eclipse.org
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml b/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml deleted file mode 100644 index 0e38d0e22f..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/plugin.xml +++ /dev/null @@ -1,30 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<!-- ================================================= --> -<!-- This is the plugin for declaring the help --> -<!-- contributions for using the tool. --> -<!-- ================================================= --> - -<plugin> - -<extension point="org.eclipse.help.toc"> - <toc file="XSDeditormap_toc.xml"/> - <index path="index/"/> - -</extension> - - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.wst.xsdeditor.doc.userindex.xml"/> -</extension> -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.dita deleted file mode 100644 index fe8040980e..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.dita +++ /dev/null @@ -1,29 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<?Pub Inc?>
-<concept id="workingwithxmlschemas" xml:lang="en-us">
-<title>Working with XML schemas</title>
-<shortdesc>XML schemas are an XML language for describing and constraining
-the content of XML files.</shortdesc>
-<conbody>
-<p>This sections contains information on the following:</p>
-</conbody>
-<related-links>
-<link href="tcxmlsch.dita"><linktext>Creating XML schemas</linktext></link>
-<link href="timpschm.dita"><linktext>Importing XML schemas</linktext></link>
-<link href="tnavsrc.dita"><linktext>Navigating XML schemas</linktext></link>
-<link href="trefactrXSD.dita"><linktext>Refactoring in XML schemas</linktext>
-</link>
-<link href="tedtpref.dita"><linktext>Editing XML schema file preferences</linktext>
-</link>
-<link href="rxsdicons.dita"><linktext>Icons used in the XML schema editor</linktext>
-</link>
-<link href="tdelscmp.dita"><linktext>Deleting XML schema components</linktext>
-</link>
-<link href="tvdtschm.dita"><linktext>Validating XML schemas</linktext></link>
-<link href="rnmspc.dita"><linktext>XML namespaces</linktext></link>
-</related-links>
-</concept>
-<?Pub *0000001267?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html deleted file mode 100644 index 45f35b6650..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cworkXSD.html +++ /dev/null @@ -1,58 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Working with XML schemas" /> -<meta name="abstract" content="XML schemas are an XML language for describing and constraining the content of XML files." /> -<meta name="description" content="XML schemas are an XML language for describing and constraining the content of XML files." /> -<meta scheme="URI" name="DC.Relation" content="tcxmlsch.html" /> -<meta scheme="URI" name="DC.Relation" content="timpschm.html" /> -<meta scheme="URI" name="DC.Relation" content="tnavsrc.html" /> -<meta scheme="URI" name="DC.Relation" content="trefactrXSD.html" /> -<meta scheme="URI" name="DC.Relation" content="tedtpref.html" /> -<meta scheme="URI" name="DC.Relation" content="rxsdicons.html" /> -<meta scheme="URI" name="DC.Relation" content="tdelscmp.html" /> -<meta scheme="URI" name="DC.Relation" content="tvdtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="workingwithxmlschemas" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Working with XML schemas</title> -</head> -<body id="workingwithxmlschemas"><a name="workingwithxmlschemas"><!-- --></a> - - -<h1 class="topictitle1">Working with XML schemas</h1> - - -<div><p>XML schemas are an XML language for describing and constraining -the content of XML files.</p> - -<p>This sections contains information on the following:</p> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div> -<div><a href="timpschm.html" title="If you want to work with XML schema files that you created outside of the product, you can import them into the workbench and open them in the XML schema editor. The XML schema editor provides you with a structured view of the XML schema.">Importing XML schemas</a></div> -<div><a href="tnavsrc.html" title="When you are working in the Source view, you can use F3 to navigate through the file by placing your cursor in the appropriate item and clicking F3 to jump to the item it refers to.">Navigating XML schemas</a></div> -<div><a href="trefactrXSD.html" title="Within an XML Schema file, refactoring allows authors to make a single artifact change, and have that change implemented throughout all other dependant artifacts.">Refactoring in XML schemas</a></div> -<div><a href="tedtpref.html" title="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used.">Editing XML schema file preferences</a></div> -<div><a href="tdelscmp.html" title="If you have created any XML schema components you no longer need, you can delete them.">Deleting XML schema components</a></div> -<div><a href="tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="rxsdicons.html" title="The following XML schema editor icons appear in the Outline, Design, and Properties view.">Icons used in the XML schema editor</a></div> -<div><a href="rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.dita deleted file mode 100644 index 9b3ad30815..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.dita +++ /dev/null @@ -1,56 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN"
- "concept.dtd">
-<concept id="cxmlsced" xml:lang="en-us">
-<title>XML schema editor</title>
-<titlealts>
-<searchtitle>XML schema editor</searchtitle>
-</titlealts>
-<shortdesc>This product provides an XML schema editor for creating, viewing,
-and validating XML schemas. XML schemas are a formal specification
-of element names that indicates which elements are allowed in an XML file,
-and in which combinations. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<conbody>
-<p>A schema is functionally equivalent to a DTD, but is written in XML; a
-schema also provides for extended functionality such as data typing, inheritance,
-and presentation rules.</p>
-<p>For more information on XML schema, refer to:</p>
-<ul>
-<li> <xref format="html" href="http://www.w3.org/TR/xmlschema-0/" scope="external">http://www.w3.org/TR/xmlschema-0/</xref> </li>
-<li> <xref format="html" href="http://www.w3.org/TR/xmlschema-1/" scope="external">http://www.w3.org/TR/xmlschema-1/</xref> </li>
-<li> <xref format="html" href="http://www.w3.org/TR/xmlschema-2/" scope="external">http://www.w3.org/TR/xmlschema-2/</xref> </li>
-</ul>
-<p>Using the XML schema editor, you can:</p>
-<ul>
-<li>Create and delete XML schema components such as complex types, simple
-types, elements, attributes, attribute groups, and groups.</li>
-<li>Edit XML schemas.</li>
-<li>Import existing XML schemas for structured viewing.</li>
-</ul>
-<p>The XML Schema specification from the W3C Web site is used for validation.</p>
-<section><title>XML schema editor views - Design, Outline, Properties, and
-Source</title>There are four main views you can work with in the XML schema
-editor:<ul>
-<li>Design - the Design view provides a graphical way to edit your schema</li>
-<li>Outline - the Outline view shows you the main components in your XML schema.
-You can use this view to add and remove certain components.</li>
-<li>Properties - the Properties view enables you to edit the properties of
-your XML schema components</li>
-<li>Source - the Source view enables you to edit your source code directly</li>
-</ul></section>
-<section><title>Status of the XML schema</title><p></p><p>Three status indicators
-for the schema are available. They are in the bottom right corner:</p><ul>
-<li> <uicontrol>Writable</uicontrol> or <uicontrol>Read Only</uicontrol>. </li>
-<li> (Source view only) <uicontrol>Smart Insert</uicontrol> or <uicontrol>Overwrite</uicontrol>.
-To toggle between these modes, press the <uicontrol>Insert</uicontrol> button
-on your keyboard.</li>
-<li> <uicontrol>Line</uicontrol> and <uicontrol>column</uicontrol> number. </li>
-</ul></section>
-</conbody>
-</concept>
-<?Pub *0000002883?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html deleted file mode 100644 index 869ad39d40..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/cxmlsced.html +++ /dev/null @@ -1,108 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="XML schema editor" /> -<meta name="abstract" content="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations." /> -<meta name="description" content="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations." /> -<meta content="XML schema editor, overview" name="DC.subject" /> -<meta content="XML schema editor, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcxmlsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cxmlsced" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML schema editor</title> -</head> -<body id="cxmlsced"><a name="cxmlsced"><!-- --></a> - - -<h1 class="topictitle1">XML schema editor</h1> - - - - -<div><p>This product provides an XML schema editor for creating, viewing, -and validating XML schemas. XML schemas are a formal specification -of element names that indicates which elements are allowed in an XML file, -and in which combinations. </p> - -<p>A schema is functionally equivalent to a DTD, but is written in XML; a -schema also provides for extended functionality such as data typing, inheritance, -and presentation rules.</p> - -<p>For more information on XML schema, refer to:</p> - -<ul> -<li> <a href="http://www.w3.org/TR/xmlschema-0/" target="_blank">http://www.w3.org/TR/xmlschema-0/</a> </li> - -<li> <a href="http://www.w3.org/TR/xmlschema-1/" target="_blank">http://www.w3.org/TR/xmlschema-1/</a> </li> - -<li> <a href="http://www.w3.org/TR/xmlschema-2/" target="_blank">http://www.w3.org/TR/xmlschema-2/</a> </li> - -</ul> - -<p>Using the XML schema editor, you can:</p> - -<ul> -<li>Create and delete XML schema components such as complex types, simple -types, elements, attributes, attribute groups, and groups.</li> - -<li>Edit XML schemas.</li> - -<li>Import existing XML schemas for structured viewing.</li> - -</ul> - -<p>The XML Schema specification from the W3C Web site is used for validation.</p> - -<div class="section"><h4 class="sectiontitle">XML schema editor views - Design, Outline, Properties, and -Source</h4>There are four main views you can work with in the XML schema -editor:<ul> -<li>Design - the Design view provides a graphical way to edit your schema</li> - -<li>Outline - the Outline view shows you the main components in your XML schema. -You can use this view to add and remove certain components.</li> - -<li>Properties - the Properties view enables you to edit the properties of -your XML schema components</li> - -<li>Source - the Source view enables you to edit your source code directly</li> - -</ul> -</div> - -<div class="section"><h4 class="sectiontitle">Status of the XML schema</h4><p /> -<p>Three status indicators -for the schema are available. They are in the bottom right corner:</p> -<ul> -<li> <span class="uicontrol">Writable</span> or <span class="uicontrol">Read Only</span>. </li> - -<li> (Source view only) <span class="uicontrol">Smart Insert</span> or <span class="uicontrol">Overwrite</span>. -To toggle between these modes, press the <span class="uicontrol">Insert</span> button -on your keyboard.</li> - -<li> <span class="uicontrol">Line</span> and <span class="uicontrol">column</span> number. </li> - -</ul> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div> -<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div> -<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.dita deleted file mode 100644 index e50260d98d..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.dita +++ /dev/null @@ -1,20 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rlimitations_slushXSD" xml:lang="en-us">
-<title>Limitations of XML schema editor</title>
-<titlealts>
-<searchtitle>Limitations of XML schema editor</searchtitle>
-</titlealts>
-<shortdesc>This section describes known product aspect limitations and workarounds.</shortdesc>
-<refbody>
-<!--Use this template to single source the readme information. The content for the readme information is maintained in this topic and is inserted into the related topic using the conref attribute. This file will not be surfaced in your navigation.-->
-<section><title>Hebrew Logical encoding</title><p id="encoding"><!--There is no defect associated with this entry. It is from the 5.1 readme.-->When
-Hebrew Logical (ISO-8859-8-I) encoding is selected as a preference for encoding
-of HTML files (<menucascade><uicontrol>Window</uicontrol><uicontrol>Preferences</uicontrol>
-<uicontrol>Web and XML Files</uicontrol><uicontrol>HTML files</uicontrol>
-</menucascade> in the "When creating files" section), the HTML documentation
-files generated from an XML schema file will still have a UTF-8 encoding.
-This is a known problem.</p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.html deleted file mode 100644 index 1a5cc5429d..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rlimitations_slushXSD.html +++ /dev/null @@ -1,43 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Limitations of XML schema editor" /> -<meta name="abstract" content="This section describes known product aspect limitations and workarounds." /> -<meta name="description" content="This section describes known product aspect limitations and workarounds." /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rlimitations_slushXSD" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Limitations of XML schema editor</title> -</head> -<body id="rlimitations_slushXSD"><a name="rlimitations_slushXSD"><!-- --></a> - - -<h1 class="topictitle1">Limitations of XML schema editor</h1> - - - -<div><p>This section describes known product aspect limitations and workarounds.</p> - - -<div class="section"><h4 class="sectiontitle">Hebrew Logical encoding</h4><p id="rlimitations_slushXSD__encoding"><a name="rlimitations_slushXSD__encoding"><!-- --></a>When -Hebrew Logical (ISO-8859-8-I) encoding is selected as a preference for encoding -of HTML files (<span class="menucascade"><span class="uicontrol">Window</span> > <span class="uicontrol">Preferences</span> - > <span class="uicontrol">Web and XML Files</span> > <span class="uicontrol">HTML files</span> -</span> in the "When creating files" section), the HTML documentation -files generated from an XML schema file will still have a UTF-8 encoding. -This is a known problem.</p> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.dita deleted file mode 100644 index 0237e988f7..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.dita +++ /dev/null @@ -1,189 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rnmspc" xml:lang="en-us">
-<title>XML namespaces</title>
-<titlealts>
-<searchtitle>XML namespaces</searchtitle>
-</titlealts>
-<shortdesc>An XML namespace is a collection of names, identified by a URI
-reference, which are used in XML documents as element types and attribute
-names.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML namespaces<indexterm>overview</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<refbody>
-<section>XML namespaces are defined by a W3C recommendation, dating 14 January
-1999, called <xref format="html" href="http://www.w3.org/TR/REC-xml-names/"
-scope="external">Namespaces in XML</xref>. XML tag names should be globally
-unique, as well as short for performance reasons. In order to resolve this
-conflict, the W3C namespace recommendation defines an attribute <b>xmlns</b> which
-can amend any XML element. If it is present in an element, it identifies the
-namespace for this element.</section>
-<section><p>The xmlns attribute has the following syntax:</p><p><codeph>xmlns:<varname>prefix</varname>=namespace</codeph> </p><p>where <codeph>namespace</codeph
-> is a unique URI (such as www.ibm.com) and where <codeph><varname>prefix</varname></codeph> represents
-the namespace and provides a pointer to it.</p><p>In the following customer
-element definition, an accounting namespace is defined in order to be able
-to distinguish the element tags from those appearing in customer records created
-by other business applications:</p><p><codeblock><acct:customer xmlns:acct="http://www.my.com/acct-REV10">
- <acct:name>Corporation</acct:name>
- <acct:order acct:ref="5566"/>
- <acct:status>invoice</acct:status>
-</acct:customer> </codeblock> </p><p>The <i>namespace definition</i> in
-the first line assigns the namespace <i>http://www.my.com/acct-REV10</i> to
-the prefix. This prefix is used on the element names such as name in order
-to attach them to the namespace. A second application, for example, a fulfillment
-system, can assign a different namespace to its customer elements:</p><p><codeblock><ful:customer xmlns:ful="http://www.your.com/ful">
- <ful:name>Corporation</ful:name>
- <ful:order ful:ref="A98756"/>
- <ful:status>shipped</ful:status>
- </ful:customer></codeblock> </p><p>An application processing both data
-structures is now able to treat the accounting and the fulfillment data differently.
-There is a default namespace. It is set if no local name is assigned in the
-namespace definition:</p><p><codeblock><acct:customer xmlns="http://www.my.com/acct-REV10" xmlns:acct="http://www.my.com/acct-REV10 ">
-<name>Corporation</name>
-<order acct:ref="5566"/>
-<status>invoice</status>
-</customer></codeblock></p><p>In this example, all tags in the customer
-record are qualified to reside in the namespace <i>http://www.my.com/acct-REV10.</i> No
-explicit prefix is needed because the default namespace is used. Note that
-the default namespace applies to any attributes definitions.</p></section>
-<section><title>XML schemas and namespaces</title><p>In the following XML
-schema, the default namespace for the schema is defined as the standard XML
-schema namespace <i>http://www.w3.org/2001/XMLSchem</i>a; there is also a
-schema specific namespace <i>http://www.ibm.com</i>.</p><p><codeblock><?xml version="1.0"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:TestSchema="http://www.ibm.com">
- <simpleType name="ZipCodeType">
- <restriction base="integer">
- <minInclusive value="10000"/>
- <maxInclusive value="99999"/>
-</restriction>
- </simpleType>
- <!--element definitions skipped -->
-</schema> </codeblock></p><p>Assuming that the preceding XML schema is
-saved as <filepath>C:\temp\TestSchema.xsd</filepath>, a sample XML file that
-validates against this schema is:</p><p><codeblock><?xml version="1.0"?>
-<x:addressList xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com file:///C:/temp/TestSchema.xsd">
- xsi:schemaLocation="http://www.ibm.com file:///C:/temp/TestSchema.xsd">
-<x:address>
- <x:street>x:Vangerowstrasse</x:street>
- <x:zipCode>69115</x:zipCode>
- <x:city>x:Heidelberg</x:city>
- </x:address>
- <x:address>
-<x:street>x:Bernal Road</x:street>
-<x:zipCode>90375</x:zipCode>
- <x:city>x:San Jose</x:city>
- </x:address>
-</x:addressList> </codeblock></p></section>
-<section><title>Target namespace</title><p> The target namespace serves to
-identify the namespace within which the association between the element and
-its name exists. In the case of declarations, this association determines
-the namespace of the elements in XML files conforming to the schema. An XML
-file importing a schema must reference its target namespace in the schemaLocation
-attribute. Any mismatches between the target and the actual namespace of an
-element are reported as schema validation errors. In our example, the target
-namespace is http://www.ibm.com; it is defined in the XML schema file and
-referenced twice in the XML file. Any mismatch between these three occurrences
-of the namespace lead to validation errors.</p><p> The following examples
-show how target namespaces and namespace prefixes work in XML schemas and
-their corresponding XML instance documents.</p></section>
-<section><title>Sample 1 - A schema with both a default and target namespace
-and unqualified locals</title><p>The XML schema: </p><p><codeblock><?xml version="1.0"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com">
-<complexType name="AddressType">
-<sequence>
-<element name="name" type="string"></element>
-</sequence>
-</complexType>
-<element name="MyAddress" type="x:AddressType"></element>
-</schema> </codeblock> </p><p>A valid XML instance document created from
-this schema looks like this. Local elements and attributes are <i>unqualified</i>.</p><p><codeblock><?xml version="1.0"?>
-<x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com x.xsd ">
-<name>Peter Smith</name>
-</x:MyAddress> </codeblock></p><p>When local elements (such as the <i>"name"</i> element)
-and attributes are unqualified in an XML file, then only the root element
-is qualified. So, in this example, the <i>"x"</i> namespace prefix is assigned
-to the root element <i>"MyAddress"</i>, associating it with the namespace <i>"http://www.ibm.com",</i> but
-the<i>"x"</i> prefix is not assigned to the local element <i>"name"</i>.</p></section>
-<section><title>Sample 2 - A schema with both a default and target namespace
-and qualified locals</title><p><codeblock><?xml version="1.0"?>
-<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com" elementFormDefault="qualified">
-<complexType name="AddressType">
-<sequence>
-<element name="name" type="string"></element>
-</sequence>
-</complexType>
-<element name="MyAddress" type="x:AddressType"></element>
- </schema> </codeblock></p><p>A valid XML instance document created from
-this schema looks like this. Local elements and attributes are <i>qualified</i> This
-is because the elementFormDefault attribute is set to qualified in the XML
-schema.</p><p><codeblock><?xml version="1.0"?>
- <x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xsi:schemaLocation="http://www.ibm.com x.xsd ">
-<x:name>Peter Smith</x:name>
- </x:MyAddress></codeblock> </p><p>In this example, the <i>"x"</i> namespace
-prefix is assigned to both the root element <i>"MyAddress"</i> and the local
-element <i>"name"</i>, associating them with the namespace <i>"http://www.ibm.com",</i>.</p></section>
-<section><title>Sample 3 - Schema with target Namespace, and explicitly defines
-xmlns:xsd</title><p>This XML schema adds this attribute: </p><codeph>xmlns:xsd="http://www.w3.org/2001/XMLSchema </codeph><p>What
-this means is that each of the constructs that are defined by the XML schema
-language will need to be qualified with the <varname>"xsd"</varname> prefix.
-For example, xsd:complexType and xsd:string</p><p>. Note that you can chose
-any other prefixes such as <varname>"xs"</varname> or <varname>"foobar"</varname> in
-your declaration and usage.</p><p>You can specify this prefix in the XML schema
-preferences page. For more information, refer to the related tasks.</p><p>All
-user defined types belong to the namespace http://www.ibm.com as defined
-by the targetNamespace attribute, and the prefix is <i>"x"</i> as defined
-by the xmlns:x attribute.</p><p><codeblock><?xml version="1.0"?>
-<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com">
-<xsd:complexType name="AddressType">
-<xsd:sequence>
- <xsd:element name="name" type="xsd:string"></xsd:element>
-</xsd:sequence>
- </xsd:complexType>
- <xsd:element name="MyAddress" type="x:AddressType"></xsd:element>
-</xsd:schema></codeblock> </p><p>A valid XML instance document created
-from this schema looks like this. Local elements and attributes are <i>unqualified</i>.
-The semantics of qualification is the same as Sample 1.</p><p><codeblock><?xml version="1.0"?>
- <x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ibm.com x.xsd ">
-<name>Peter Smith</name>
- </x:MyAddress></codeblock></p></section>
-<section><title>Sample 4 - Schema with undeclared target Namespace that explicitly
-defines xmlns:xsd</title><p>This XML schema has no target namespace for itself.
-In this case, it is highly recommended that all XML schema constructs be explicitly
-qualified with a prefix such as <i>"xsd"</i>. The definitions and declarations
-from this schema such as <i>AddressType</i> are referenced without namespace
-qualification since there is no namespace prefix. </p><p><codeblock><?xml version="1.0"?>
-<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
-<xsd:complexType name="AddressType">
-<xsd:sequence>
-<xsd:element name="name" type="xsd:string"></xsd:element>
-<xsd:element name="name" type="xsd:string"></xsd:element>
-<xsd:element name="name" type="xsd:string"></xsd:element>
-</xsd:sequence>
-</xsd:complexType>
-<xsd:element name="MyAddress" type="AddressType"></xsd:element>
-</xsd:schema> </codeblock></p><p>A valid XML instance document created
-from the schema looks like this. All elements are <i>unqualified</i>.</p><p><codeblock><?xml version="1.0"?>
-<MyAddress xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="x.xsd">
-<name>name</name>
-</MyAddress></codeblock> </p></section>
-<section><title>Sample 5 - A schema where the target namespace is the default
-namespace</title><p>This is an XML schema where the target namespace is the
-default namespace. As well, the namespace has no namespace prefix.</p><p><codeblock><?xml version="1.0"?>
- <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns="http://www.ibm.com">
-<xsd:complexType name="AddressType">
-<xsd:sequence>
-<xsd:element name="name" type="xsd:string"></xsd:element>
-</xsd:sequence>
-</xsd:complexType>
- <xsd:element name="MyAddress" type="AddressType"></xsd:element>
- </xsd:schema> </codeblock> </p><p>A valid XML instance document created
-from the schema looks like this:</p><p><codeblock><?xml version="1.0" encoding="UTF-8"?>
-<MyAddress xmlns="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com NewXMLSchema.xsd">
-<name>name</name>
- </MyAddress> </codeblock> </p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html deleted file mode 100644 index f4a0b4f53d..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rnmspc.html +++ /dev/null @@ -1,272 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="XML namespaces" /> -<meta name="abstract" content="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names." /> -<meta name="description" content="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names." /> -<meta content="XML namespaces, overview" name="DC.subject" /> -<meta content="XML namespaces, overview" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rnmspc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML namespaces</title> -</head> -<body id="rnmspc"><a name="rnmspc"><!-- --></a> - - -<h1 class="topictitle1">XML namespaces</h1> - - - - -<div><p>An XML namespace is a collection of names, identified by a URI -reference, which are used in XML documents as element types and attribute -names.</p> - -<div class="section">XML namespaces are defined by a W3C recommendation, dating 14 January -1999, called <a href="http://www.w3.org/TR/REC-xml-names/" target="_blank">Namespaces in XML</a>. XML tag names should be globally -unique, as well as short for performance reasons. In order to resolve this -conflict, the W3C namespace recommendation defines an attribute <strong>xmlns</strong> which -can amend any XML element. If it is present in an element, it identifies the -namespace for this element.</div> - -<div class="section"><p>The xmlns attribute has the following syntax:</p> -<p><samp class="codeph">xmlns:<var class="varname">prefix</var>=namespace</samp> </p> -<p>where <samp class="codeph">namespace</samp> is a unique URI (such as www.ibm.com) and where <samp class="codeph"><var class="varname">prefix</var></samp> represents -the namespace and provides a pointer to it.</p> -<p>In the following customer -element definition, an accounting namespace is defined in order to be able -to distinguish the element tags from those appearing in customer records created -by other business applications:</p> -<div class="p"><pre><acct:customer xmlns:acct="http://www.my.com/acct-REV10"> - <acct:name>Corporation</acct:name> - <acct:order acct:ref="5566"/> - <acct:status>invoice</acct:status> -</acct:customer> </pre> - </div> -<p>The <em>namespace definition</em> in -the first line assigns the namespace <em>http://www.my.com/acct-REV10</em> to -the prefix. This prefix is used on the element names such as name in order -to attach them to the namespace. A second application, for example, a fulfillment -system, can assign a different namespace to its customer elements:</p> -<div class="p"><pre><ful:customer xmlns:ful="http://www.your.com/ful"> - <ful:name>Corporation</ful:name> - <ful:order ful:ref="A98756"/> - <ful:status>shipped</ful:status> - </ful:customer></pre> - </div> -<p>An application processing both data -structures is now able to treat the accounting and the fulfillment data differently. -There is a default namespace. It is set if no local name is assigned in the -namespace definition:</p> -<div class="p"><pre><acct:customer xmlns="http://www.my.com/acct-REV10" xmlns:acct="http://www.my.com/acct-REV10 "> -<name>Corporation</name> -<order acct:ref="5566"/> -<status>invoice</status> -</customer></pre> -</div> -<p>In this example, all tags in the customer -record are qualified to reside in the namespace <em>http://www.my.com/acct-REV10.</em> No -explicit prefix is needed because the default namespace is used. Note that -the default namespace applies to any attributes definitions.</p> -</div> - -<div class="section"><h4 class="sectiontitle">XML schemas and namespaces</h4><p>In the following XML -schema, the default namespace for the schema is defined as the standard XML -schema namespace <em>http://www.w3.org/2001/XMLSchem</em>a; there is also a -schema specific namespace <em>http://www.ibm.com</em>.</p> -<div class="p"><pre><?xml version="1.0"?> -<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:TestSchema="http://www.ibm.com"> - <simpleType name="ZipCodeType"> - <restriction base="integer"> - <minInclusive value="10000"/> - <maxInclusive value="99999"/> -</restriction> - </simpleType> - <!--element definitions skipped --> -</schema> </pre> -</div> -<p>Assuming that the preceding XML schema is -saved as <span class="filepath">C:\temp\TestSchema.xsd</span>, a sample XML file that -validates against this schema is:</p> -<div class="p"><pre><?xml version="1.0"?> -<x:addressList xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com file:///C:/temp/TestSchema.xsd"> - xsi:schemaLocation="http://www.ibm.com file:///C:/temp/TestSchema.xsd"> -<x:address> - <x:street>x:Vangerowstrasse</x:street> - <x:zipCode>69115</x:zipCode> - <x:city>x:Heidelberg</x:city> - </x:address> - <x:address> -<x:street>x:Bernal Road</x:street> -<x:zipCode>90375</x:zipCode> - <x:city>x:San Jose</x:city> - </x:address> -</x:addressList> </pre> -</div> -</div> - -<div class="section"><h4 class="sectiontitle">Target namespace</h4><p> The target namespace serves to -identify the namespace within which the association between the element and -its name exists. In the case of declarations, this association determines -the namespace of the elements in XML files conforming to the schema. An XML -file importing a schema must reference its target namespace in the schemaLocation -attribute. Any mismatches between the target and the actual namespace of an -element are reported as schema validation errors. In our example, the target -namespace is http://www.ibm.com; it is defined in the XML schema file and -referenced twice in the XML file. Any mismatch between these three occurrences -of the namespace lead to validation errors.</p> -<p> The following examples -show how target namespaces and namespace prefixes work in XML schemas and -their corresponding XML instance documents.</p> -</div> - -<div class="section"><h4 class="sectiontitle">Sample 1 - A schema with both a default and target namespace -and unqualified locals</h4><p>The XML schema: </p> -<div class="p"><pre><?xml version="1.0"?> -<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com"> -<complexType name="AddressType"> -<sequence> -<element name="name" type="string"></element> -</sequence> -</complexType> -<element name="MyAddress" type="x:AddressType"></element> -</schema> </pre> - </div> -<p>A valid XML instance document created from -this schema looks like this. Local elements and attributes are <em>unqualified</em>.</p> -<div class="p"><pre><?xml version="1.0"?> -<x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com x.xsd "> -<name>Peter Smith</name> -</x:MyAddress> </pre> -</div> -<p>When local elements (such as the <em>"name"</em> element) -and attributes are unqualified in an XML file, then only the root element -is qualified. So, in this example, the <em>"x"</em> namespace prefix is assigned -to the root element <em>"MyAddress"</em>, associating it with the namespace <em>"http://www.ibm.com",</em> but -the<em>"x"</em> prefix is not assigned to the local element <em>"name"</em>.</p> -</div> - -<div class="section"><h4 class="sectiontitle">Sample 2 - A schema with both a default and target namespace -and qualified locals</h4><div class="p"><pre><?xml version="1.0"?> -<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com" elementFormDefault="qualified"> -<complexType name="AddressType"> -<sequence> -<element name="name" type="string"></element> -</sequence> -</complexType> -<element name="MyAddress" type="x:AddressType"></element> - </schema> </pre> -</div> -<p>A valid XML instance document created from -this schema looks like this. Local elements and attributes are <em>qualified</em> This -is because the elementFormDefault attribute is set to qualified in the XML -schema.</p> -<div class="p"><pre><?xml version="1.0"?> - <x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://www.ibm.com x.xsd "> -<x:name>Peter Smith</x:name> - </x:MyAddress></pre> - </div> -<p>In this example, the <em>"x"</em> namespace -prefix is assigned to both the root element <em>"MyAddress"</em> and the local -element <em>"name"</em>, associating them with the namespace <em>"http://www.ibm.com",</em>.</p> -</div> - -<div class="section"><h4 class="sectiontitle">Sample 3 - Schema with target Namespace, and explicitly defines -xmlns:xsd</h4><p>This XML schema adds this attribute: </p> -<samp class="codeph">xmlns:xsd="http://www.w3.org/2001/XMLSchema </samp><p>What -this means is that each of the constructs that are defined by the XML schema -language will need to be qualified with the <var class="varname">"xsd"</var> prefix. -For example, xsd:complexType and xsd:string</p> -<p>. Note that you can chose -any other prefixes such as <var class="varname">"xs"</var> or <var class="varname">"foobar"</var> in -your declaration and usage.</p> -<p>You can specify this prefix in the XML schema -preferences page. For more information, refer to the related tasks.</p> -<p>All -user defined types belong to the namespace http://www.ibm.com as defined -by the targetNamespace attribute, and the prefix is <em>"x"</em> as defined -by the xmlns:x attribute.</p> -<div class="p"><pre><?xml version="1.0"?> -<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:x="http://www.ibm.com"> -<xsd:complexType name="AddressType"> -<xsd:sequence> - <xsd:element name="name" type="xsd:string"></xsd:element> -</xsd:sequence> - </xsd:complexType> - <xsd:element name="MyAddress" type="x:AddressType"></xsd:element> -</xsd:schema></pre> - </div> -<p>A valid XML instance document created -from this schema looks like this. Local elements and attributes are <em>unqualified</em>. -The semantics of qualification is the same as Sample 1.</p> -<div class="p"><pre><?xml version="1.0"?> - <x:MyAddress xmlns:x="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://www.ibm.com x.xsd "> -<name>Peter Smith</name> - </x:MyAddress></pre> -</div> -</div> - -<div class="section"><h4 class="sectiontitle">Sample 4 - Schema with undeclared target Namespace that explicitly -defines xmlns:xsd</h4><p>This XML schema has no target namespace for itself. -In this case, it is highly recommended that all XML schema constructs be explicitly -qualified with a prefix such as <em>"xsd"</em>. The definitions and declarations -from this schema such as <em>AddressType</em> are referenced without namespace -qualification since there is no namespace prefix. </p> -<div class="p"><pre><?xml version="1.0"?> -<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> -<xsd:complexType name="AddressType"> -<xsd:sequence> -<xsd:element name="name" type="xsd:string"></xsd:element> -<xsd:element name="name" type="xsd:string"></xsd:element> -<xsd:element name="name" type="xsd:string"></xsd:element> -</xsd:sequence> -</xsd:complexType> -<xsd:element name="MyAddress" type="AddressType"></xsd:element> -</xsd:schema> </pre> -</div> -<p>A valid XML instance document created -from the schema looks like this. All elements are <em>unqualified</em>.</p> -<div class="p"><pre><?xml version="1.0"?> -<MyAddress xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="x.xsd"> -<name>name</name> -</MyAddress></pre> - </div> -</div> - -<div class="section"><h4 class="sectiontitle">Sample 5 - A schema where the target namespace is the default -namespace</h4><p>This is an XML schema where the target namespace is the -default namespace. As well, the namespace has no namespace prefix.</p> -<div class="p"><pre><?xml version="1.0"?> - <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns="http://www.ibm.com"> -<xsd:complexType name="AddressType"> -<xsd:sequence> -<xsd:element name="name" type="xsd:string"></xsd:element> -</xsd:sequence> -</xsd:complexType> - <xsd:element name="MyAddress" type="AddressType"></xsd:element> - </xsd:schema> </pre> - </div> -<p>A valid XML instance document created -from the schema looks like this:</p> -<div class="p"><pre><?xml version="1.0" encoding="UTF-8"?> -<MyAddress xmlns="http://www.ibm.com" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com NewXMLSchema.xsd"> -<name>name</name> - </MyAddress> </pre> - </div> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.dita deleted file mode 100644 index 97d9893195..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
-<reference id="rrefintg" xml:lang="en-us">
-<title>Referential integrity in the XML schema editor</title>
-<titlealts>
-<searchtitle>Referential integrity</searchtitle>
-</titlealts>
-<shortdesc>The XML schema editor has a built-in mechanism to handle referential
-integrity issues. When you delete certain nodes, clean up for any nodes affected
-will automatically occur.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>referential integrity</indexterm></indexterm>
-<indexterm>XML schema editor<indexterm>clean up in</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<refbody>
-<section>When you define a complex type, you can add a content model to it
-and reference a global element. <p>For example:<codeblock><schema>
- <element name="comment" type="string">
- <complexType name="Items">
- <sequence>
- <element ref="comment">
- </sequence>
- </complexType>
-</schema></codeblock></p><p>If the global element (comment) was deleted,
-all references to it would be in error. However, when you delete the global
-element, the XML schema editor will clean up using the following algorithm:</p><ul>
-<li>If there are one or more global elements in the schema, it will change
-all existing references to the first global element.</li>
-<li>If there is no global element, then it will delete the element reference
-from the content model.</li>
-</ul></section>
-<section><title>Deleting included and imported schema</title><p>If an included
-or imported schema is deleted, you must manually reset the following type
-references as appropriate: <ul>
-<li>Global element and element's type</li>
-<li>Attribute type</li>
-<li>Complex type derivation</li>
-<li>Simple type derivation </li>
-</ul>They will not automatically be reset if an included or imported schema
-is deleted.</p></section>
-</refbody>
-</reference>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html deleted file mode 100644 index e319a3bdd8..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rrefintg.html +++ /dev/null @@ -1,88 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Referential integrity in the XML schema editor" /> -<meta name="abstract" content="The XML schema editor has a built-in mechanism to handle referential integrity issues. When you delete certain nodes, clean up for any nodes affected will automatically occur." /> -<meta name="description" content="The XML schema editor has a built-in mechanism to handle referential integrity issues. When you delete certain nodes, clean up for any nodes affected will automatically occur." /> -<meta content="XML schema editor, referential integrity, clean up in" name="DC.subject" /> -<meta content="XML schema editor, referential integrity, clean up in" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tdelscmp.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rrefintg" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Referential integrity</title> -</head> -<body id="rrefintg"><a name="rrefintg"><!-- --></a> - - -<h1 class="topictitle1">Referential integrity in the XML schema editor</h1> - - - - -<div><p>The XML schema editor has a built-in mechanism to handle referential -integrity issues. When you delete certain nodes, clean up for any nodes affected -will automatically occur.</p> - -<div class="section">When you define a complex type, you can add a content model to it -and reference a global element. <div class="p">For example:<pre><schema> - <element name="comment" type="string"> - <complexType name="Items"> - <sequence> - <element ref="comment"> - </sequence> - </complexType> -</schema></pre> -</div> -<p>If the global element (comment) was deleted, -all references to it would be in error. However, when you delete the global -element, the XML schema editor will clean up using the following algorithm:</p> -<ul> -<li>If there are one or more global elements in the schema, it will change -all existing references to the first global element.</li> - -<li>If there is no global element, then it will delete the element reference -from the content model.</li> - -</ul> -</div> - -<div class="section"><h4 class="sectiontitle">Deleting included and imported schema</h4><div class="p">If an included -or imported schema is deleted, you must manually reset the following type -references as appropriate: <ul> -<li>Global element and element's type</li> - -<li>Attribute type</li> - -<li>Complex type derivation</li> - -<li>Simple type derivation </li> - -</ul> -They will not automatically be reset if an included or imported schema -is deleted.</div> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div> -<div><a href="../topics/tdelscmp.html" title="If you have created any XML schema components you no longer need, you can delete them.">Deleting XML schema components</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.dita deleted file mode 100644 index 93dea39966..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.dita +++ /dev/null @@ -1,140 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN"
- "reference.dtd">
-<reference id="ricons" xml:lang="en-us">
-<title>Icons used in the XML schema editor</title>
-<titlealts>
-<searchtitle>XML schema editor icons</searchtitle>
-</titlealts>
-<shortdesc>The following XML schema editor icons appear in the Outline, Design,
-and Properties view.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>icons</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<refbody>
-<section></section>
-<table>
-<tgroup cols="2"><colspec colname="COLSPEC0"/><colspec colname="COLSPEC1"/>
-<tbody>
-<row>
-<entry colname="COLSPEC0" valign="bottom"><b>Icon</b></entry>
-<entry colname="COLSPEC1" valign="bottom"><b>Description</b></entry>
-</row>
-<row>
-<entry><image href="../images/XSDAnyAttribute.gif"><alt>This graphic is the
-any attribute icon </alt></image></entry>
-<entry><codeph>any</codeph> attribute</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAny.gif"><alt>This graphic is the any element
-icon </alt></image></entry>
-<entry><codeph>any</codeph> element</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAttribute.gif"><alt>This graphic is the attribute
-icon </alt></image></entry>
-<entry>attribute</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAttributeGroup.gif"><alt>This graphic is
-the attribute group icon </alt></image></entry>
-<entry>attribute group</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAttributeGroupRef.gif"><alt>This graphic
-is the attribute group reference icon </alt></image></entry>
-<entry>attribute group reference</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAttributeRef.gif"><alt>This graphic is the
-attribute reference icon </alt></image></entry>
-<entry>attribute reference</entry>
-</row>
-<row>
-<entry><image href="../images/XSDAll.gif"><alt>This graphic is the content
-model - all icon </alt></image></entry>
-<entry>content model - all</entry>
-</row>
-<row>
-<entry colname="COLSPEC0"><image href="../images/XSDChoice.gif"><alt>This
-graphic is the content model - choice icon </alt></image></entry>
-<entry colname="COLSPEC1">content model - choice</entry>
-</row>
-<row>
-<entry colname="COLSPEC0"><image href="../images/XSDSequence.gif"><alt>This
-graphic is the content model - sequence icon </alt></image></entry>
-<entry colname="COLSPEC1">content model - sequence</entry>
-</row>
-<row>
-<entry><image href="../images/XSDComplexType.gif"><alt>This graphic is the
-any element icon </alt></image></entry>
-<entry>complex type</entry>
-</row>
-<row>
-<entry><image href="../images/XSDElement.gif"><alt>This graphic is the element
-icon </alt></image></entry>
-<entry>element</entry>
-</row>
-<row>
-<entry><image href="../images/XSDElementRef.gif"><alt>This graphic is the
-element reference icon </alt></image></entry>
-<entry>element reference</entry>
-</row>
-<row>
-<entry><image href="../images/XSDSimpleEnum.gif"><alt>This graphic is the
-enumeration icon </alt></image></entry>
-<entry>enumeration</entry>
-</row>
-<row>
-<entry><image href="../images/XSDGlobalAttribute.gif"><alt>This graphic is
-the global attribute icon </alt></image></entry>
-<entry>global attribute</entry>
-</row>
-<row>
-<entry> <image href="../images/XSDGlobalElement.gif"><alt>This graphic is
-the global element icon </alt></image></entry>
-<entry>global element</entry>
-</row>
-<row>
-<entry> <image href="../images/XSDGroup.gif"><alt>This graphic is the group
-icon </alt></image></entry>
-<entry>group</entry>
-</row>
-<row>
-<entry><image href="../images/XSDGroupRef.gif"><alt>This graphic is the group
-reference icon </alt></image></entry>
-<entry>group reference</entry>
-</row>
-<row>
-<entry><image href="../images/XSDImport.gif"><alt>This graphic is the import
-icon </alt></image></entry>
-<entry>import</entry>
-</row>
-<row>
-<entry><image href="../images/XSDInclude.gif"><alt>This graphic is the include
-icon </alt></image></entry>
-<entry>include</entry>
-</row>
-<row>
-<entry><image href="../images/XSDSimplePattern.gif"><alt>This graphic is the
-pattern icon </alt></image></entry>
-<entry>pattern</entry>
-</row>
-<row>
-<entry><image href="../images/XSDRedefine.gif"><alt>This graphic is the redefine
-icon </alt></image></entry>
-<entry>redefine</entry>
-</row>
-<row>
-<entry><image href="../images/XSDSimpleType.gif"><alt>This graphic is the
-simple type icon </alt></image></entry>
-<entry>simple type</entry>
-</row>
-</tbody>
-</tgroup>
-</table>
-</refbody>
-</reference>
-<?Pub *0000004581?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html deleted file mode 100644 index 92f68a6e8b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/rxsdicons.html +++ /dev/null @@ -1,209 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="reference" name="DC.Type" /> -<meta name="DC.Title" content="Icons used in the XML schema editor" /> -<meta name="abstract" content="The following XML schema editor icons appear in the Outline, Design, and Properties view." /> -<meta name="description" content="The following XML schema editor icons appear in the Outline, Design, and Properties view." /> -<meta content="XML schema editor, icons, Icons" name="DC.subject" /> -<meta content="XML schema editor, icons, Icons" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="ricons" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>XML schema editor icons</title> -</head> -<body id="ricons"><a name="ricons"><!-- --></a> - - -<h1 class="topictitle1">Icons used in the XML schema editor</h1> - - - - -<div><p>The following XML schema editor icons appear in the Outline, Design, -and Properties view.</p> - -<div class="section" /> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<tbody> -<tr> -<td valign="bottom"><strong>Icon</strong></td> - -<td valign="bottom"><strong>Description</strong></td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAnyAttribute.gif" alt="This graphic is the any attribute icon " /></td> - -<td valign="top"><samp class="codeph">any</samp> attribute</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAny.gif" alt="This graphic is the any element icon " /></td> - -<td valign="top"><samp class="codeph">any</samp> element</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAttribute.gif" alt="This graphic is the attribute icon " /></td> - -<td valign="top">attribute</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAttributeGroup.gif" alt="This graphic is the attribute group icon " /></td> - -<td valign="top">attribute group</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAttributeGroupRef.gif" alt="This graphic is the attribute group reference icon " /></td> - -<td valign="top">attribute group reference</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAttributeRef.gif" alt="This graphic is the attribute reference icon " /></td> - -<td valign="top">attribute reference</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDAll.gif" alt="This graphic is the content model - all icon " /></td> - -<td valign="top">content model - all</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDChoice.gif" alt="This graphic is the content model - choice icon " /></td> - -<td valign="top">content model - choice</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDSequence.gif" alt="This graphic is the content model - sequence icon " /></td> - -<td valign="top">content model - sequence</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDComplexType.gif" alt="This graphic is the any element icon " /></td> - -<td valign="top">complex type</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDElement.gif" alt="This graphic is the element icon " /></td> - -<td valign="top">element</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDElementRef.gif" alt="This graphic is the element reference icon " /></td> - -<td valign="top">element reference</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDSimpleEnum.gif" alt="This graphic is the enumeration icon " /></td> - -<td valign="top">enumeration</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDGlobalAttribute.gif" alt="This graphic is the global attribute icon " /></td> - -<td valign="top">global attribute</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/XSDGlobalElement.gif" alt="This graphic is the global element icon " /></td> - -<td valign="top">global element</td> - -</tr> - -<tr> -<td valign="top"> <img src="../images/XSDGroup.gif" alt="This graphic is the group icon " /></td> - -<td valign="top">group</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDGroupRef.gif" alt="This graphic is the group reference icon " /></td> - -<td valign="top">group reference</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDImport.gif" alt="This graphic is the import icon " /></td> - -<td valign="top">import</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDInclude.gif" alt="This graphic is the include icon " /></td> - -<td valign="top">include</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDSimplePattern.gif" alt="This graphic is the pattern icon " /></td> - -<td valign="top">pattern</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDRedefine.gif" alt="This graphic is the redefine icon " /></td> - -<td valign="top">redefine</td> - -</tr> - -<tr> -<td valign="top"><img src="../images/XSDSimpleType.gif" alt="This graphic is the simple type icon " /></td> - -<td valign="top">simple type</td> - -</tr> - -</tbody> - -</table> -</div> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.dita deleted file mode 100644 index 336ae4eeab..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.dita +++ /dev/null @@ -1,100 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="taddagrp" xml:lang="en-us">
-<title>Adding attribute groups</title>
-<titlealts>
-<searchtitle>Adding attribute groups</searchtitle>
-</titlealts>
-<shortdesc>An attribute group definition is an association between a name
-and a set of attribute declarations. Named groups of attribute declarations
-can greatly facilitate the maintenance and reuse of common attribute declarations
-in an XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>attribute groups</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>attribute groups</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To add an attribute
-group to an XML schema, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, right-click the <uicontrol>Attribute Groups</uicontrol> folder
-and click <uicontrol>Add Attribute Group</uicontrol>.</cmd><info>It appears
-in the <uicontrol>Attribute Groups</uicontrol> folder.</info></step>
-<step><cmd>Select your new group, and in the Design view, right-click the
-attribute group and select <menucascade><uicontrol>Refactor</uicontrol><uicontrol>Rename</uicontrol>
-</menucascade>. In the <uicontrol>New Name</uicontrol> field, type a name
-for the attribute group.</cmd></step>
-<step><cmd>To add an attribute, right-click your attribute group in the Outline
-view, click <uicontrol>Add Attribute</uicontrol>.</cmd><info>The attribute
-appears below the attribute group in the Outline view.</info>
-<substeps>
-<substep><cmd>Select the attribute, and in the Design view, click the current
-(default) name of the attribute, then type the new <uicontrol>Name</uicontrol>.</cmd>
-</substep>
-<substep><cmd>In the Design view, click the current (default) attribute type
-and select a type from the menu. Alternately, you can select browse to invoke
-the Set Type menu for more options.</cmd><info>The Set Type dialog lists all
-built-in and user-defined types currently available. You can change the <uicontrol>Scope</uicontrol> of
-the list by selecting one of the following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></info></substep>
-</substeps>
-</step>
-<step><cmd>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, in the Design view, right-click the complex
-type containing the element, and click <uicontrol>Add Attribute Ref</uicontrol>.</cmd>
-<info>A declaration that references a global attribute enables the referenced
-attribute to appear in the instance document in the context of the referencing
-declaration. Select the reference, then select the attribute group you want
-it to reference in the Properties view, from the<uicontrol>Ref</uicontrol> menu.</info>
-</step>
-<step><cmd>An attribute group reference provides a reference to an attribute
-group. To add an attribute group reference, in the Design view, right-click
-the complex type containing the element, and click <uicontrol>Add Attribute
-Group Ref</uicontrol>.</cmd><info>A declaration that references a global attribute
-enables the referenced attribute to appear in the instance document in the
-context of the referencing declaration. Select the reference, then select
-the attribute group you want it to reference in the Properties view, from
-the<uicontrol>Ref</uicontrol> menu.</info></step>
-<step><cmd>An <codeph>any</codeph> element enables element content according
-to namespaces, and the corresponding <codeph>any</codeph> attribute element
-enables attributes to appear in elements. To add an <codeph>any</codeph> attribute,
-right-click your attribute group and click <uicontrol>Add Any Attribute</uicontrol>.</cmd>
-<info>The <codeph>any</codeph> appears below the attribute group in the Outline
-view. You can specify the following values for an <codeph>any</codeph> attribute:</info>
-<choices>
-<choice>For a <uicontrol>namespace</uicontrol> value, you can
-select:<ul>
-<li><b>##any</b>. This allows any well-formed XML from any namespace.</li>
-<li><b>##local </b>. This allows any well-formed XML that is not declared
-to be in a namespace.</li>
-<li><b>##other</b>. This allows any well-formed XML that is not from the target
-namespace of the type being defined.</li>
-<li><b>##targetNamespace </b>. This is shorthand for the target namespace
-of the type being defined.</li>
-</ul></choice>
-<choice>For a <uicontrol>processContents</uicontrol> value, you can select:<ul>
-<li><b>skip</b>. The XML processor will not validate the attribute content
-at all.</li>
-<li><b>lax</b>. The XML processor will validate the attribute content as much
-as it can.</li>
-<li><b>strict</b>. The XML processor will validate all the attribute content.</li>
-</ul></choice>
-</choices>
-</step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000005769?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html deleted file mode 100644 index 500b3b01b8..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddagrp.html +++ /dev/null @@ -1,148 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding attribute groups" /> -<meta name="abstract" content="An attribute group definition is an association between a name and a set of attribute declarations. Named groups of attribute declarations can greatly facilitate the maintenance and reuse of common attribute declarations in an XML schema." /> -<meta name="description" content="An attribute group definition is an association between a name and a set of attribute declarations. Named groups of attribute declarations can greatly facilitate the maintenance and reuse of common attribute declarations in an XML schema." /> -<meta content="XML schema editor, adding, attribute groups, attributes groups, XML schema files, attribute groups, XML schema files, attributes groups" name="DC.subject" /> -<meta content="XML schema editor, adding, attribute groups, attributes groups, XML schema files, attribute groups, XML schema files, attributes groups" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddagrp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding attribute groups</title> -</head> -<body id="taddagrp"><a name="taddagrp"><!-- --></a> - - -<h1 class="topictitle1">Adding attribute groups</h1> - - - - -<div><p>An attribute group definition is an association between a name -and a set of attribute declarations. Named groups of attribute declarations -can greatly facilitate the maintenance and reuse of common attribute declarations -in an XML schema.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add an attribute -group to an XML schema, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, right-click the <span class="uicontrol">Attribute Groups</span> folder -and click <span class="uicontrol">Add Attribute Group</span>.</span> It appears -in the <span class="uicontrol">Attribute Groups</span> folder.</li> - -<li class="stepexpand"><span>Select your new group, and in the Design view, right-click the -attribute group and select <span class="menucascade"><span class="uicontrol">Refactor</span> > <span class="uicontrol">Rename</span> -</span>. In the <span class="uicontrol">New Name</span> field, type a name -for the attribute group.</span></li> - -<li class="stepexpand"><span>To add an attribute, right-click your attribute group in the Outline -view, click <span class="uicontrol">Add Attribute</span>.</span> The attribute -appears below the attribute group in the Outline view. -<ol type="a"> -<li class="substepexpand"><span>Select the attribute, and in the Design view, click the current -(default) name of the attribute, then type the new <span class="uicontrol">Name</span>.</span> -</li> - -<li class="substepexpand"><span>In the Design view, click the current (default) attribute type -and select a type from the menu. Alternately, you can select browse to invoke -the Set Type menu for more options.</span> The Set Type dialog lists all -built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of -the list by selecting one of the following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>An attribute reference provides a reference to a global attribute. -To add an attribute reference, in the Design view, right-click the complex -type containing the element, and click <span class="uicontrol">Add Attribute Ref</span>.</span> - A declaration that references a global attribute enables the referenced -attribute to appear in the instance document in the context of the referencing -declaration. Select the reference, then select the attribute group you want -it to reference in the Properties view, from the<span class="uicontrol">Ref</span> menu. -</li> - -<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute -group. To add an attribute group reference, in the Design view, right-click -the complex type containing the element, and click <span class="uicontrol">Add Attribute -Group Ref</span>.</span> A declaration that references a global attribute -enables the referenced attribute to appear in the instance document in the -context of the referencing declaration. Select the reference, then select -the attribute group you want it to reference in the Properties view, from -the<span class="uicontrol">Ref</span> menu.</li> - -<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according -to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element -enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute, -right-click your attribute group and click <span class="uicontrol">Add Any Attribute</span>.</span> - The <samp class="codeph">any</samp> appears below the attribute group in the Outline -view. You can specify the following values for an <samp class="codeph">any</samp> attribute: -<ul> -<li>For a <span class="uicontrol">namespace</span> value, you can -select:<ul> -<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li> - -<li><strong>##local </strong>. This allows any well-formed XML that is not declared -to be in a namespace.</li> - -<li><strong>##other</strong>. This allows any well-formed XML that is not from the target -namespace of the type being defined.</li> - -<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace -of the type being defined.</li> - -</ul> -</li> - -<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul> -<li><strong>skip</strong>. The XML processor will not validate the attribute content -at all.</li> - -<li><strong>lax</strong>. The XML processor will validate the attribute content as much -as it can.</li> - -<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li> - -</ul> -</li> - -</ul> - -</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.dita deleted file mode 100644 index 5b2c285be2..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.dita +++ /dev/null @@ -1,76 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddanye" xml:lang="en-us">
-<title>Adding an any element</title>
-<titlealts>
-<searchtitle>Adding an any element</searchtitle>
-</titlealts>
-<shortdesc>You can use the <codeph>any</codeph> element in a similar way as
-a DTD's ANY content model, however, it must be done in conjunction with namespaces.
-This enables you to include any well-formed XML content, such as an HTML Web
-page that conforms to XHTML 1.0 syntax.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding an any element</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding an any element</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>For example:</p><p><codeblock><element name = "MyWebPage">
-<complexType>
-<any namespace ="http://www.w3.org/1999/xhtml>
- < minOccurs="1" maxOccurs="unbounded" processContents="skip"/>
-</complexType>
-</element></codeblock></p><p>The preceding schema fragment allows a <codeph><MyWebPage></codeph> element
-to contain any well-formed XHTML data that appears in the specified namespace.</p><p>The
-following instructions were written for the Resource perspective, but they
-will also work in many other perspectives.</p><p>To add an <codeph>any</codeph> element:</p></context>
-<steps>
-<step><cmd>In the Outline view, right-click the content model that you want
-to work with and click <uicontrol>Add Any</uicontrol>. </cmd></step>
-<step><cmd>Select the new <codeph>any</codeph> element.</cmd></step>
-<step><cmd>In the Properties view of the schema editor, for a <uicontrol>namespace</uicontrol> value,
-you can select:</cmd>
-<choices>
-<choice><b>##any</b>. This allows any well-formed XML from any namespace.</choice>
-<choice><b>##local </b>. This allows any well-formed XML that is not declared
-to be in a namespace.</choice>
-<choice><b>##other </b>. This allows any well-formed XML that is not from
-the target namespace of the type being defined.</choice>
-<choice><b>##targetNamespace</b>. This is shorthand for the target namespace
-of the type being defined.</choice>
-</choices>
-</step>
-<step><cmd>For a <uicontrol>processContents</uicontrol> value, you can select:</cmd>
-<choices>
-<choice><b>skip</b>. The XML processor will not validate the content at all.</choice>
-<choice><b>lax</b>. The XML processor will validate the content as much as
-it can.</choice>
-<choice><b>strict</b>. The XML processor will validate all the content.</choice>
-</choices>
-</step>
-<step><cmd>The <uicontrol>minOccurs</uicontrol> value is the number of times
-the <codeph>any</codeph> element must appear in an instance document. You
-can select <uicontrol>0</uicontrol> if you want the element to be optional;
-otherwise, select <uicontrol>1</uicontrol>. </cmd></step>
-<step><cmd>The <uicontrol>maxOccurs</uicontrol> value is the maximum number
-of times an <codeph>any</codeph> element can appear in an instance document.
-You can select <uicontrol>0</uicontrol>, <uicontrol>1</uicontrol>, or, to
-indicate there is no maximum number of occurrences, <uicontrol>unbounded</uicontrol>.</cmd>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<postreq><p>(c) Copyright 2001, World Wide Web (Massachusetts Institute of
-Technology, Institut National de Recherche en Informatique et en Automatique,
-Keio University).</p></postreq>
-</taskbody>
-</task>
-<?Pub *0000004291?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html deleted file mode 100644 index 8540ecb118..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddanye.html +++ /dev/null @@ -1,119 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding an any element" /> -<meta name="abstract" content="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax." /> -<meta name="description" content="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax." /> -<meta content="XML schema editor, adding, an any element, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, an any element, XML schema files" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddanye" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding an any element</title> -</head> -<body id="taddanye"><a name="taddanye"><!-- --></a> - - -<h1 class="topictitle1">Adding an any element</h1> - - - - -<div><p>You can use the <samp class="codeph">any</samp> element in a similar way as -a DTD's ANY content model, however, it must be done in conjunction with namespaces. -This enables you to include any well-formed XML content, such as an HTML Web -page that conforms to XHTML 1.0 syntax.</p> - -<div class="section"><p>For example:</p> -<div class="p"><pre><element name = "MyWebPage"> -<complexType> -<any namespace ="http://www.w3.org/1999/xhtml> - < minOccurs="1" maxOccurs="unbounded" processContents="skip"/> -</complexType> -</element></pre> -</div> -<p>The preceding schema fragment allows a <samp class="codeph"><MyWebPage></samp> element -to contain any well-formed XHTML data that appears in the specified namespace.</p> -<p>The -following instructions were written for the Resource perspective, but they -will also work in many other perspectives.</p> -<p>To add an <samp class="codeph">any</samp> element:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Outline view, right-click the content model that you want -to work with and click <span class="uicontrol">Add Any</span>. </span></li> - -<li class="stepexpand"><span>Select the new <samp class="codeph">any</samp> element.</span></li> - -<li class="stepexpand"><span>In the Properties view of the schema editor, for a <span class="uicontrol">namespace</span> value, -you can select:</span> -<ul> -<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li> - -<li><strong>##local </strong>. This allows any well-formed XML that is not declared -to be in a namespace.</li> - -<li><strong>##other </strong>. This allows any well-formed XML that is not from -the target namespace of the type being defined.</li> - -<li><strong>##targetNamespace</strong>. This is shorthand for the target namespace -of the type being defined.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>For a <span class="uicontrol">processContents</span> value, you can select:</span> -<ul> -<li><strong>skip</strong>. The XML processor will not validate the content at all.</li> - -<li><strong>lax</strong>. The XML processor will validate the content as much as -it can.</li> - -<li><strong>strict</strong>. The XML processor will validate all the content.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>The <span class="uicontrol">minOccurs</span> value is the number of times -the <samp class="codeph">any</samp> element must appear in an instance document. You -can select <span class="uicontrol">0</span> if you want the element to be optional; -otherwise, select <span class="uicontrol">1</span>. </span></li> - -<li class="stepexpand"><span>The <span class="uicontrol">maxOccurs</span> value is the maximum number -of times an <samp class="codeph">any</samp> element can appear in an instance document. -You can select <span class="uicontrol">0</span>, <span class="uicontrol">1</span>, or, to -indicate there is no maximum number of occurrences, <span class="uicontrol">unbounded</span>.</span> -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>(c) Copyright 2001, World Wide Web (Massachusetts Institute of -Technology, Institut National de Recherche en Informatique et en Automatique, -Keio University).</p> -</div> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.dita deleted file mode 100644 index f5d45f719c..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.dita +++ /dev/null @@ -1,87 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddcmod" xml:lang="en-us">
-<title>Adding content models</title>
-<titlealts>
-<searchtitle>Adding content models</searchtitle>
-</titlealts>
-<shortdesc>A content model is the representation of any data that can be contained
-inside an element, global element, complex type, or group. It is a formal
-description of the structure and permissible content of an element, global
-element, complex type, or group, which may be used to validate a document
-instance.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>content models</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>content models</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>There are three different kinds of content models:<ul>
-<li><b>Sequence</b>, which means that all the content model's children can
-appear in an instance of the XML schema. They must, however, appear in the
-order they are listed in the content model.</li>
-<li><b>Choice</b>, which means that only one of the content model's children
-can appear in an instance of the XML schema.</li>
-<li><b>All</b>, which means that all of the content model's children can appear
-once or not at all, and they can appear in any order. If you select this option,
-all of the contents model's children must be individual elements and no element
-in the content model can appear more than once.</li>
-</ul></p><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To add a content
-model to an element, global element, complex type, or group, follow these
-steps:</p></context>
-<steps>
-<step><cmd>In the Design view, select your complex type, or group:</cmd>
-<choices>
-<choice>If you selected a complex type, you can right-click it and click <uicontrol>Add
-Sequence</uicontrol>, or <uicontrol>Add Choice</uicontrol> to add the type
-of content model you want to your complex type. If you wish to use the <uicontrol>all</uicontrol> content
-model, you can change the model by clicking the model in the Design view,
-and in properties, select <uicontrol>all</uicontrol> as the <uicontrol>Kind</uicontrol>.
-Your content model is automatically added as a child of your complex type
-- expand in the Outline view to see it. <b>Note:</b> These options will not
-appear if you have set a base type for your complex type. You can either set
-a base type for your complex type, or you add a content model to it, but you
-cannot do both.</choice>
-<choice>Your group is automatically created with a sequence content model
-child. Expand it in the Outline view to see it and select it. In the Properties
-view, you can select to change it to a <uicontrol>choice</uicontrol> or <uicontrol>all</uicontrol> content
-model by selecting these options from the <uicontrol>Kind</uicontrol> menu.</choice>
-</choices>
-</step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MinOccurs</uicontrol> field.</cmd>
-<info>This is the minimum number of times the content model must appear. If
-you want the content model to be optional, select <uicontrol>0</uicontrol>.
-Otherwise, select <uicontrol>1</uicontrol>. </info></step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MaxOccurs</uicontrol> field.</cmd>
-<info>This is the maximum number of times a content model can appear. You
-can select <uicontrol>unbounded</uicontrol> to indicate there is no maximum
-number of occurrences.</info></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this content model.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info>
-</step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<postreq><p>You can add the following items to a content object model. </p><ul>
-<li>Another content model.</li>
-<li>A group reference which enables the referenced group to appear in the
-instance document in the context of the referencing declaration. This menu
-option only appears if there are global groups defined elsewhere in the document
-or if groups are defined in included schemas.</li>
-<li>An element, fundamental building blocks in XML.</li>
-<li>An element reference, which provides a reference to a global element.
-This menu option only appears if there are global elements defined elsewhere
-in the document.</li>
-<li>An <codeph>any</codeph> element. You can use an <codeph>any</codeph> element
-to extend your content model by any elements belonging to a specified namespace.</li>
-</ul></postreq>
-</taskbody>
-</task>
-<?Pub *0000005317?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html deleted file mode 100644 index 1e0afe1e3b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmod.html +++ /dev/null @@ -1,139 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding content models" /> -<meta name="abstract" content="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance." /> -<meta name="description" content="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance." /> -<meta content="XML schema editor, adding, content models, XML schema files, content models, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, content models, XML schema files, content models, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddgrpr.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddcmod" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding content models</title> -</head> -<body id="taddcmod"><a name="taddcmod"><!-- --></a> - - -<h1 class="topictitle1">Adding content models</h1> - - - - -<div><p>A content model is the representation of any data that can be contained -inside an element, global element, complex type, or group. It is a formal -description of the structure and permissible content of an element, global -element, complex type, or group, which may be used to validate a document -instance.</p> - -<div class="section"><div class="p">There are three different kinds of content models:<ul> -<li><strong>Sequence</strong>, which means that all the content model's children can -appear in an instance of the XML schema. They must, however, appear in the -order they are listed in the content model.</li> - -<li><strong>Choice</strong>, which means that only one of the content model's children -can appear in an instance of the XML schema.</li> - -<li><strong>All</strong>, which means that all of the content model's children can appear -once or not at all, and they can appear in any order. If you select this option, -all of the contents model's children must be individual elements and no element -in the content model can appear more than once.</li> - -</ul> -</div> -<p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add a content -model to an element, global element, complex type, or group, follow these -steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, select your complex type, or group:</span> -<ul> -<li>If you selected a complex type, you can right-click it and click <span class="uicontrol">Add -Sequence</span>, or <span class="uicontrol">Add Choice</span> to add the type -of content model you want to your complex type. If you wish to use the <span class="uicontrol">all</span> content -model, you can change the model by clicking the model in the Design view, -and in properties, select <span class="uicontrol">all</span> as the <span class="uicontrol">Kind</span>. -Your content model is automatically added as a child of your complex type -- expand in the Outline view to see it. <strong>Note:</strong> These options will not -appear if you have set a base type for your complex type. You can either set -a base type for your complex type, or you add a content model to it, but you -cannot do both.</li> - -<li>Your group is automatically created with a sequence content model -child. Expand it in the Outline view to see it and select it. In the Properties -view, you can select to change it to a <span class="uicontrol">choice</span> or <span class="uicontrol">all</span> content -model by selecting these options from the <span class="uicontrol">Kind</span> menu.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MinOccurs</span> field.</span> - This is the minimum number of times the content model must appear. If -you want the content model to be optional, select <span class="uicontrol">0</span>. -Otherwise, select <span class="uicontrol">1</span>. </li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span> - This is the maximum number of times a content model can appear. You -can select <span class="uicontrol">unbounded</span> to indicate there is no maximum -number of occurrences.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this content model.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description. -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>You can add the following items to a content object model. </p> -<ul> -<li>Another content model.</li> - -<li>A group reference which enables the referenced group to appear in the -instance document in the context of the referencing declaration. This menu -option only appears if there are global groups defined elsewhere in the document -or if groups are defined in included schemas.</li> - -<li>An element, fundamental building blocks in XML.</li> - -<li>An element reference, which provides a reference to a global element. -This menu option only appears if there are global elements defined elsewhere -in the document.</li> - -<li>An <samp class="codeph">any</samp> element. You can use an <samp class="codeph">any</samp> element -to extend your content model by any elements belonging to a specified namespace.</li> - -</ul> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div> -<div><a href="../topics/taddelm.html" title="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements.">Adding elements</a></div> -<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div> -<div><a href="../topics/taddgrpr.html" title="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration.">Adding group references</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.dita deleted file mode 100644 index ef5c946629..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.dita +++ /dev/null @@ -1,105 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddcmxt" xml:lang="en-us">
-<title>Adding complex types</title>
-<titlealts>
-<searchtitle>Adding complex types</searchtitle>
-</titlealts>
-<shortdesc>A complex type allows elements in its content and can carry attributes.
-Complex types can be used to help determine the appropriate content for any
-instance documents generated from or associated with your XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>complex types</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>complex types</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>You can add as many complex types as you want to an XML schema.</p><p>The
-following instructions were written for the Resource perspective, but they
-will also work in many other perspectives.</p><p>To add a complex type to
-an XML schema, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>Right-click the Types category in the Design view, and click <uicontrol>Add
-Complex Type</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, type a new name for the complex type in
-the <uicontrol>Name</uicontrol> field.</cmd></step>
-<step><cmd>Click <uicontrol>Browse</uicontrol> <image href="../images/Browse.gif">
-<alt>Browse icon</alt></image> to select a base type for your complex type.</cmd>
-<info>You can either set a base type for your complex type, or you can add
-a content model to it (which represents any data that can be contained inside
-an element), but you cannot do both. For more information about content models,
-refer to the related tasks.</info></step>
-<step><cmd>Select <uicontrol>restriction</uicontrol> or <uicontrol>extension</uicontrol> from
-the <uicontrol>Inherited by</uicontrol> list.</cmd><info>This specifies whether
-your type is derived from its base type by restriction or extension.</info>
-</step>
-<step><cmd>The Design view will display the attributes within the complex
-type.</cmd><info>You can also use this view to add attributes to your complex
-type. An attribute associates an attribute name with a specific type and value.</info>
-<choices>
-<choice>To add an attribute, in the Design view, right click your complex
-type and select <uicontrol>Add Attribute</uicontrol>.<ul>
-<li><uicontrol>name</uicontrol>. In the Design view, click the name of the
-attribute to make a change.</li>
-<li><uicontrol>type</uicontrol>. In the Design view, click the type of the
-attribute to make a change. The drop-down menu provides commonly used types.
-For more options, simply select <uicontrol>Browse</uicontrol> from the menu.</li>
-</ul></choice>
-</choices>
-</step>
-<step><cmd>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, in the Design view, right-click the complex
-type containing the element, and click <uicontrol>Add Attribute Ref</uicontrol>.</cmd>
-<info>A declaration that references a global attribute enables the referenced
-attribute to appear in the instance document in the context of the referencing
-declaration. Select the reference, then select the attribute group you want
-it to reference in the Properties view, from the<uicontrol> Ref</uicontrol> menu.</info>
-</step>
-<step><cmd>An attribute group reference provides a reference to an attribute
-group. To add an attribute group reference, in the Design view, right-click
-the complex type containing the element, and click <uicontrol>Add Attribute
-Group Ref</uicontrol>.</cmd><info>A declaration that references an attribute
-group enables the referenced attribute group to appear in the instance document
-in the context of the referencing declaration. Select the reference, then
-select the attribute group you want it to reference in the Properties view,
-from the<uicontrol> Ref</uicontrol> menu.</info></step>
-<step><cmd>An <codeph>any</codeph> element enables element content according
-to namespaces, and the corresponding <codeph>any</codeph> attribute element
-enables attributes to appear in elements. To add an <codeph>any</codeph> attribute,
-right-click in the complex type header, and click <uicontrol>Add Any Attribute</uicontrol>.</cmd>
-<info>You can specify the following values for an <codeph>any</codeph> attribute:</info>
-<choices>
-<choice>For a <uicontrol>namespace</uicontrol> value, you can
-select:<ul>
-<li><b>##any</b>. This allows any well-formed XML from any namespace.</li>
-<li><b>##local </b>. This allows any well-formed XML that is not declared
-to be in a namespace.</li>
-<li><b>##other</b>. This allows any well-formed XML that is not from the target
-namespace of the type being defined.</li>
-<li><b>##targetNamespace </b>. This is shorthand for the target namespace
-of the type being defined.</li>
-</ul></choice>
-<choice>For a <uicontrol>processContents</uicontrol> value, you can select:<ul>
-<li><b>skip</b>. The XML processor will not validate the attribute content
-at all.</li>
-<li><b>lax</b>. The XML processor will validate the attribute content as much
-as it can.</li>
-<li><b>strict</b>. The XML processor will validate all the attribute content.</li>
-</ul></choice>
-</choices>
-<info></info></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this complex type.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000006207?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html deleted file mode 100644 index 6204c408fd..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddcmxt.html +++ /dev/null @@ -1,158 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding complex types" /> -<meta name="abstract" content="A complex type allows elements in its content and can carry attributes. Complex types can be used to help determine the appropriate content for any instance documents generated from or associated with your XML schema." /> -<meta name="description" content="A complex type allows elements in its content and can carry attributes. Complex types can be used to help determine the appropriate content for any instance documents generated from or associated with your XML schema." /> -<meta content="XML schema editor, adding, complex types, XML schema files, complex types, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, complex types, XML schema files, complex types, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddcmxt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding complex types</title> -</head> -<body id="taddcmxt"><a name="taddcmxt"><!-- --></a> - - -<h1 class="topictitle1">Adding complex types</h1> - - - - -<div><p>A complex type allows elements in its content and can carry attributes. -Complex types can be used to help determine the appropriate content for any -instance documents generated from or associated with your XML schema.</p> - -<div class="section"><p>You can add as many complex types as you want to an XML schema.</p> -<p>The -following instructions were written for the Resource perspective, but they -will also work in many other perspectives.</p> -<p>To add a complex type to -an XML schema, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>Right-click the Types category in the Design view, and click <span class="uicontrol">Add -Complex Type</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, type a new name for the complex type in -the <span class="uicontrol">Name</span> field.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="Browse icon" /> to select a base type for your complex type.</span> - You can either set a base type for your complex type, or you can add -a content model to it (which represents any data that can be contained inside -an element), but you cannot do both. For more information about content models, -refer to the related tasks.</li> - -<li class="stepexpand"><span>Select <span class="uicontrol">restriction</span> or <span class="uicontrol">extension</span> from -the <span class="uicontrol">Inherited by</span> list.</span> This specifies whether -your type is derived from its base type by restriction or extension. -</li> - -<li class="stepexpand"><span>The Design view will display the attributes within the complex -type.</span> You can also use this view to add attributes to your complex -type. An attribute associates an attribute name with a specific type and value. -<ul> -<li>To add an attribute, in the Design view, right click your complex -type and select <span class="uicontrol">Add Attribute</span>.<ul> -<li><span class="uicontrol">name</span>. In the Design view, click the name of the -attribute to make a change.</li> - -<li><span class="uicontrol">type</span>. In the Design view, click the type of the -attribute to make a change. The drop-down menu provides commonly used types. -For more options, simply select <span class="uicontrol">Browse</span> from the menu.</li> - -</ul> -</li> - -</ul> - -</li> - -<li class="stepexpand"><span>An attribute reference provides a reference to a global attribute. -To add an attribute reference, in the Design view, right-click the complex -type containing the element, and click <span class="uicontrol">Add Attribute Ref</span>.</span> - A declaration that references a global attribute enables the referenced -attribute to appear in the instance document in the context of the referencing -declaration. Select the reference, then select the attribute group you want -it to reference in the Properties view, from the<span class="uicontrol"> Ref</span> menu. -</li> - -<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute -group. To add an attribute group reference, in the Design view, right-click -the complex type containing the element, and click <span class="uicontrol">Add Attribute -Group Ref</span>.</span> A declaration that references an attribute -group enables the referenced attribute group to appear in the instance document -in the context of the referencing declaration. Select the reference, then -select the attribute group you want it to reference in the Properties view, -from the<span class="uicontrol"> Ref</span> menu.</li> - -<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according -to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element -enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute, -right-click in the complex type header, and click <span class="uicontrol">Add Any Attribute</span>.</span> - You can specify the following values for an <samp class="codeph">any</samp> attribute: -<ul> -<li>For a <span class="uicontrol">namespace</span> value, you can -select:<ul> -<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li> - -<li><strong>##local </strong>. This allows any well-formed XML that is not declared -to be in a namespace.</li> - -<li><strong>##other</strong>. This allows any well-formed XML that is not from the target -namespace of the type being defined.</li> - -<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace -of the type being defined.</li> - -</ul> -</li> - -<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul> -<li><strong>skip</strong>. The XML processor will not validate the attribute content -at all.</li> - -<li><strong>lax</strong>. The XML processor will validate the attribute content as much -as it can.</li> - -<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li> - -</ul> -</li> - -</ul> - - </li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this complex type.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.dita deleted file mode 100644 index 57eeb53ce1..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.dita +++ /dev/null @@ -1,67 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="taddelm" xml:lang="en-us">
-<title>Adding elements</title>
-<titlealts>
-<searchtitle>Adding elements</searchtitle>
-</titlealts>
-<shortdesc>Elements are fundamental building blocks in XML. Element declarations
-provide value constraints, provide a description that can be used for validation,
-establish constraining relationships between related elements and attributes,
-and control the substitution of elements.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>elements</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>elements</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To add an element:</p></context>
-<steps>
-<step><cmd>To add an element, in the Design view, right-click the content
-model you want to work with and click <uicontrol>Add Element</uicontrol>.</cmd>
-<info>The element appears attached to the content model in the Design view.</info>
-<substeps>
-<substep><cmd>In the Design view, select the element, and click the current
-(default) name of the element, which puts you in direct editing mode, then
-type the new <uicontrol>Name</uicontrol> and press enter.</cmd></substep>
-<substep><cmd>In the Design view, click the current (default) element type
-and select a type from the menu. Alternately, you can select browse to invoke
-the Set Type dialog for more options.</cmd><info>The Set Type dialog lists
-all built-in and user-defined types currently available. You can change the <uicontrol>Scope</uicontrol> of
-the list by selecting one of the following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace.</li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file.</li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></info></substep>
-</substeps>
-</step>
-<step><cmd>(Optional) In the Properties view, select the appropriate value
-in the <uicontrol>MinOccurs</uicontrol> field.</cmd><info>This is the number
-of times the element can appear in an instance document. If you want the element
-to be optional, select <uicontrol>0</uicontrol>. Otherwise, select <uicontrol>1</uicontrol>. </info>
-</step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MaxOccurs</uicontrol> field.</cmd>
-<info>This is the maximum number of times the element can appear in an instance
-document. Select <uicontrol>unbounded</uicontrol> to indicate there is no
-maximum number of occurrences.</info></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<postreq>You can add a content model to an element, which is the representation
-of any data that can be contained inside the element. For more information
-about working with content models, refer to the related tasks.</postreq>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html deleted file mode 100644 index a9b3cb7841..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelm.html +++ /dev/null @@ -1,114 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding elements" /> -<meta name="abstract" content="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements." /> -<meta name="description" content="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements." /> -<meta content="XML schema editor, adding, elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddglba.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddelm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding elements</title> -</head> -<body id="taddelm"><a name="taddelm"><!-- --></a> - - -<h1 class="topictitle1">Adding elements</h1> - - - - -<div><p>Elements are fundamental building blocks in XML. Element declarations -provide value constraints, provide a description that can be used for validation, -establish constraining relationships between related elements and attributes, -and control the substitution of elements.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add an element:</p> -</div> - -<ol> -<li class="stepexpand"><span>To add an element, in the Design view, right-click the content -model you want to work with and click <span class="uicontrol">Add Element</span>.</span> - The element appears attached to the content model in the Design view. -<ol type="a"> -<li class="substepexpand"><span>In the Design view, select the element, and click the current -(default) name of the element, which puts you in direct editing mode, then -type the new <span class="uicontrol">Name</span> and press enter.</span></li> - -<li class="substepexpand"><span>In the Design view, click the current (default) element type -and select a type from the menu. Alternately, you can select browse to invoke -the Set Type dialog for more options.</span> The Set Type dialog lists -all built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of -the list by selecting one of the following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace.</li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file.</li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>(Optional) In the Properties view, select the appropriate value -in the <span class="uicontrol">MinOccurs</span> field.</span> This is the number -of times the element can appear in an instance document. If you want the element -to be optional, select <span class="uicontrol">0</span>. Otherwise, select <span class="uicontrol">1</span>. -</li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span> - This is the maximum number of times the element can appear in an instance -document. Select <span class="uicontrol">unbounded</span> to indicate there is no -maximum number of occurrences.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section">You can add a content model to an element, which is the representation -of any data that can be contained inside the element. For more information -about working with content models, refer to the related tasks.</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div> -<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div> -<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div> -<div><a href="../topics/taddglba.html" title="A global attribute is an attribute that can be recognized anywhere in a document. Once declared, a global attribute can be referenced in one or more declarations using an attribute reference.">Adding global attributes</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.dita deleted file mode 100644 index 0a41c6ab0b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.dita +++ /dev/null @@ -1,57 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddelmr" xml:lang="en-us">
-<title>Adding element references</title>
-<titlealts>
-<searchtitle>Adding element references</searchtitle>
-</titlealts>
-<shortdesc>An element reference provides a reference to a global element.
-A declaration that references a global element enables the referenced global
-element to appear in the instance document in the context of the referencing
-declaration.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>element references</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>element references</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To add an element
-reference:</p></context>
-<steps>
-<step><cmd>In the Design view, right-click the content model you want to work
-with and click <uicontrol>Add Element Ref</uicontrol>.</cmd><stepresult>If
-no global element is defined in the document, a new global element is created
-for you, and the element reference will point to it.</stepresult></step>
-<step><cmd>Select the element reference. To specify values for an element
-reference:</cmd>
-<choices>
-<choice>Click the name of the element reference in the Design view. Enter
-the name of the element reference.</choice>
-<choice>Click the element reference type in the Design view.
-Select a type from the menu, or select <uicontrol>Browse</uicontrol> for more
-options.</choice>
-</choices>
-</step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MinOccurs</uicontrol> field.</cmd>
-<info>This is the number of times the global element referenced can appear
-in an instance document. If you want the element to be optional, select <uicontrol>0</uicontrol>.
-Otherwise, select <uicontrol>1</uicontrol>. </info></step>
-<step><cmd>(Optional) Select the appropriate value in the <uicontrol>MaxOccurs</uicontrol> field.</cmd>
-<info>This is the maximum number of times the global element referenced can
-appear. You can select <uicontrol>unbounded</uicontrol> to indicate there
-is no maximum number of occurrences.</info></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this element reference.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000003232?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html deleted file mode 100644 index 40177eb6a0..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddelmr.html +++ /dev/null @@ -1,97 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding element references" /> -<meta name="abstract" content="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration." /> -<meta name="description" content="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration." /> -<meta content="XML schema editor, adding, element references, XML schema files, element references, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, element references, XML schema files, element references, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddglem.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddanye.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddglba.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddelmr" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding element references</title> -</head> -<body id="taddelmr"><a name="taddelmr"><!-- --></a> - - -<h1 class="topictitle1">Adding element references</h1> - - - - -<div><p>An element reference provides a reference to a global element. -A declaration that references a global element enables the referenced global -element to appear in the instance document in the context of the referencing -declaration.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add an element -reference:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click the content model you want to work -with and click <span class="uicontrol">Add Element Ref</span>.</span> If -no global element is defined in the document, a new global element is created -for you, and the element reference will point to it.</li> - -<li class="stepexpand"><span>Select the element reference. To specify values for an element -reference:</span> -<ul> -<li>Click the name of the element reference in the Design view. Enter -the name of the element reference.</li> - -<li>Click the element reference type in the Design view. -Select a type from the menu, or select <span class="uicontrol">Browse</span> for more -options.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MinOccurs</span> field.</span> - This is the number of times the global element referenced can appear -in an instance document. If you want the element to be optional, select <span class="uicontrol">0</span>. -Otherwise, select <span class="uicontrol">1</span>. </li> - -<li class="stepexpand"><span>(Optional) Select the appropriate value in the <span class="uicontrol">MaxOccurs</span> field.</span> - This is the maximum number of times the global element referenced can -appear. You can select <span class="uicontrol">unbounded</span> to indicate there -is no maximum number of occurrences.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this element reference.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddglem.html" title="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a content model.">Adding global elements</a></div> -<div><a href="../topics/taddelm.html" title="Elements are fundamental building blocks in XML. Element declarations provide value constraints, provide a description that can be used for validation, establish constraining relationships between related elements and attributes, and control the substitution of elements.">Adding elements</a></div> -<div><a href="../topics/taddanye.html" title="You can use the any element in a similar way as a DTD's ANY content model, however, it must be done in conjunction with namespaces. This enables you to include any well-formed XML content, such as an HTML Web page that conforms to XHTML 1.0 syntax.">Adding an any element</a></div> -<div><a href="../topics/taddglba.html" title="A global attribute is an attribute that can be recognized anywhere in a document. Once declared, a global attribute can be referenced in one or more declarations using an attribute reference.">Adding global attributes</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.dita deleted file mode 100644 index 719033f32c..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.dita +++ /dev/null @@ -1,55 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddglba" xml:lang="en-us">
-<title>Adding global attributes</title>
-<titlealts>
-<searchtitle>Adding global attributes</searchtitle>
-</titlealts>
-<shortdesc>A global attribute is an attribute that can be recognized anywhere
-in a document. Once declared, a global attribute can be referenced in one
-or more declarations using an attribute reference.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>global attributes</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>global attributes</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To add a global
-attribute:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Design view, right-click in the <b>Attributes</b> section
-and click <uicontrol>Add Attribute</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, enter a name for the attribute in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>In the Properties view, you can select the attribute <uicontrol>Type</uicontrol> from
-the predefined list in the menu next to the <uicontrol>Type</uicontrol> field.</cmd>
-<info><p>Alternatively, you can select <uicontrol>Browse</uicontrol> from
-the list for more options. </p><p>The Set Type dialog will appear, and lists
-all built-in and user-defined types currently available. You can change the <uicontrol>Scope</uicontrol> of
-the list by selecting one of the following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></p><p>Select the type you want in the type list, then click <uicontrol>OK</uicontrol>. </p></info>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this global attribute.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000003230?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html deleted file mode 100644 index 29b0abfecf..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglba.html +++ /dev/null @@ -1,89 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding global attributes" /> -<meta name="abstract" content="A global attribute is an attribute that can be recognized anywhere in a document. Once declared, a global attribute can be referenced in one or more declarations using an attribute reference." /> -<meta name="description" content="A global attribute is an attribute that can be recognized anywhere in a document. Once declared, a global attribute can be referenced in one or more declarations using an attribute reference." /> -<meta content="XML schema editor, adding, global attributes, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, global attributes, XML schema files" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddglba" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding global attributes</title> -</head> -<body id="taddglba"><a name="taddglba"><!-- --></a> - - -<h1 class="topictitle1">Adding global attributes</h1> - - - - -<div><p>A global attribute is an attribute that can be recognized anywhere -in a document. Once declared, a global attribute can be referenced in one -or more declarations using an attribute reference.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add a global -attribute:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Design view, right-click in the <strong>Attributes</strong> section -and click <span class="uicontrol">Add Attribute</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, enter a name for the attribute in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li class="stepexpand"><span>In the Properties view, you can select the attribute <span class="uicontrol">Type</span> from -the predefined list in the menu next to the <span class="uicontrol">Type</span> field.</span> - <p>Alternatively, you can select <span class="uicontrol">Browse</span> from -the list for more options. </p> -<div class="p">The Set Type dialog will appear, and lists -all built-in and user-defined types currently available. You can change the <span class="uicontrol">Scope</span> of -the list by selecting one of the following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</div> -<p>Select the type you want in the type list, then click <span class="uicontrol">OK</span>. </p> - -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this global attribute.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.dita deleted file mode 100644 index 1dfe97d207..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.dita +++ /dev/null @@ -1,157 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddglem" xml:lang="en-us">
-<title>Adding global elements</title>
-<titlealts>
-<searchtitle>Adding global elements</searchtitle>
-</titlealts>
-<shortdesc>A global element is an element with a global scope. It is one that
-has been declared as part of the main schema rather than as part of a content
-model.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>global elements</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>global elements</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To add a global
-element:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, select your schema.</cmd><info>The entire
-schema and its contents are displayed in the Design view.</info></step>
-<step><cmd>In the Design view, right-click in the <b>Elements</b> section
-and click <uicontrol>Add Element</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, click the <uicontrol>General</uicontrol> tab,
-and type a new name for the global element in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>In the Properties view, you can select the attribute type from
-the predefined list in the menu next to the <uicontrol>Type</uicontrol> field.</cmd>
-<info><p>Alternatively, you can select <uicontrol>Browse</uicontrol> from
-the list for more options. </p><p>The <uicontrol>Set Type</uicontrol> dialog
-box appears, and lists all built-in and user-defined types currently available.
-You can change the <uicontrol>Scope</uicontrol> of the list by selecting one
-of the following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></p><p>Select the type you want in the type list, then click <uicontrol>OK</uicontrol>. </p></info>
-</step>
-<step><cmd>(Optional) Click the <uicontrol>Other</uicontrol> tab.</cmd><info>In
-this page, you can specify the following various values for the global element: </info>
-<choices>
-<choice><uicontrol>abstract</uicontrol>. Click <b>true </b>if you want the
-global element to be abstract. When a global element is declared to be abstract,
-it cannot be used in an instance document. Instead, a member of that global
-element's substitution group must appear in the instance document.</choice>
-<choice><uicontrol>block</uicontrol>. This field determines whether the global
-element may be replaced by an element derived from it.</choice>
-<choice><uicontrol>final</uicontrol>. This field determines whether this global
-element may be derived from.</choice>
-<choice><uicontrol>fixed/default</uicontrol>. Click <uicontrol>Browse</uicontrol> and
-select <uicontrol>Fixed</uicontrol> or <uicontrol>Default</uicontrol> and
-specify an appropriate value. If you select <b>Fixed</b>, the global element
-has a fixed value, which cannot be changed. If you select <b>Default</b>,
-the element has a default value.</choice>
-<choice><uicontrol>form</uicontrol>. Use this field to indicate if the appearance
-of this global element in an instance of the XML schema (an XML file associated
-with the XML schema) must be qualified by a namespace.</choice>
-<choice><uicontrol>nillable</uicontrol>. Select <b>true</b> if you do not
-want the global element to be able to have any child elements, only attributes. </choice>
-<choice><uicontrol>substitutionGroup</uicontrol>. A substitution group allows
-elements to be substituted for other elements.</choice>
-</choices>
-</step>
-<step><cmd>Click the <uicontrol>Attributes</uicontrol> tab.</cmd><info>You
-can use this page to add attributes, attribute references, attributes group
-references, and <codeph>any</codeph> attributes to your global element.</info>
-</step>
-<step><cmd>An attribute associates an attribute name with a specific type
-and value. To add an attribute, right-click in the Attributes page, and click <uicontrol>Add
-Attribute</uicontrol>.</cmd><info>You can specify the following values for
-an attribute:</info>
-<choices>
-<choice><uicontrol>fixed/default</uicontrol>. Click <uicontrol>Browse</uicontrol> and
-select <uicontrol>Fixed</uicontrol> or <uicontrol>Default</uicontrol> and
-specify an appropriate value. If you select <b>Fixed</b>, the attribute has
-a fixed value, which cannot be changed. If you select <b>Default</b>, the
-attribute has a default value.</choice>
-<choice><uicontrol>form</uicontrol>. Use this field to indicate if the appearance
-of this attribute in an instance of the XML schema must be qualified by a
-namespace.</choice>
-<choice><uicontrol>name</uicontrol>. Enter the name of the attribute.</choice>
-<choice><uicontrol>type</uicontrol>. Click <uicontrol>Browse</uicontrol> and
-select the type of the attribute. </choice>
-<choice><uicontrol>use</uicontrol>. This field indicates how an attribute
-can be used in an instance document. If you select optional, the attribute
-can appear once, but it does not have to. If you select required, the attribute
-must appear once. If you select prohibited, the attribute must not appear. <b>Note</b>:
-If you selected <uicontrol>Default</uicontrol>, you must select <b>optional</b> in
-this field, otherwise the default value will not be valid.</choice>
-</choices>
-</step>
-<step><cmd>An attribute reference provides a reference to a global attribute.
-To add an attribute reference, right-click in the Attributes page, and click <uicontrol>Add
-Attribute Ref</uicontrol>.</cmd><info>A declaration that references a global
-attribute enables the referenced attribute to appear in the instance document
-in the context of the referencing declaration. The menu option to add an attribute
-reference only appears if there are global attributes defined elsewhere in
-the document. Select the reference, then select the global attribute you want
-it to reference from the <uicontrol>ref</uicontrol> list.</info></step>
-<step><cmd>An attribute group reference provides a reference to an attribute
-group. To add an attribute group reference, right-click in the Attributes
-page, and click <uicontrol>Add Attribute Group Ref</uicontrol>.</cmd><info>A
-declaration that references an attribute group enables the referenced attribute
-group to appear in the instance document in the context of the referencing
-declaration. The menu option to add an attribute group reference only appears
-if there are attribute groups defined elsewhere in the document. Select the
-reference, then select the attribute group you want it to reference from the <uicontrol>ref</uicontrol> list.</info>
-</step>
-<step><cmd>An <codeph>any</codeph> element enables element content according
-to namespaces, and the corresponding <codeph>any</codeph> attribute element
-enables attributes to appear in elements. To add an <codeph>any</codeph> attribute,
-right-click in the Attributes page and click <uicontrol>Add Any Attribute</uicontrol>.</cmd>
-<info>You can specify the following values for an <codeph>any</codeph> attribute:</info>
-<choices>
-<choice>For a <uicontrol>namespace</uicontrol> value, you can
-select:<ul>
-<li><b>##any</b>. This allows any well-formed XML from any namespace.</li>
-<li><b>##local </b>. This allows any well-formed XML that is not declared
-to be in a namespace.</li>
-<li><b>##other</b>. This allows any well-formed XML that is not from the target
-namespace of the type being defined.</li>
-<li><b>##targetNamespace </b>. This is shorthand for the target namespace
-of the type being defined.</li>
-</ul></choice>
-<choice>For a <uicontrol>processContents</uicontrol> value, you can select:<ul>
-<li><b>skip</b>. The XML processor will not validate the attribute content
-at all.</li>
-<li><b>lax</b>. The XML processor will validate the attribute content as much
-as it can.</li>
-<li><b>strict</b>. The XML processor will validate all the attribute content.</li>
-</ul></choice>
-</choices>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this global element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<postreq>You can add a content model to a global element, which is the representation
-of any data that can be contained inside the global element. For more information
-about working with content models, refer to the related tasks.</postreq>
-</taskbody>
-</task>
-<?Pub *0000009579?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html deleted file mode 100644 index f38c0d5eec..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddglem.html +++ /dev/null @@ -1,232 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding global elements" /> -<meta name="abstract" content="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a content model." /> -<meta name="description" content="A global element is an element with a global scope. It is one that has been declared as part of the main schema rather than as part of a content model." /> -<meta content="XML schema editor, adding, global elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, global elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddelmr.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddglem" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding global elements</title> -</head> -<body id="taddglem"><a name="taddglem"><!-- --></a> - - -<h1 class="topictitle1">Adding global elements</h1> - - - - -<div><p>A global element is an element with a global scope. It is one that -has been declared as part of the main schema rather than as part of a content -model.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add a global -element:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire -schema and its contents are displayed in the Design view.</li> - -<li class="stepexpand"><span>In the Design view, right-click in the <strong>Elements</strong> section -and click <span class="uicontrol">Add Element</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab, -and type a new name for the global element in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li class="stepexpand"><span>In the Properties view, you can select the attribute type from -the predefined list in the menu next to the <span class="uicontrol">Type</span> field.</span> - <p>Alternatively, you can select <span class="uicontrol">Browse</span> from -the list for more options. </p> -<div class="p">The <span class="uicontrol">Set Type</span> dialog -box appears, and lists all built-in and user-defined types currently available. -You can change the <span class="uicontrol">Scope</span> of the list by selecting one -of the following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</div> -<p>Select the type you want in the type list, then click <span class="uicontrol">OK</span>. </p> - -</li> - -<li class="stepexpand"><span>(Optional) Click the <span class="uicontrol">Other</span> tab.</span> In -this page, you can specify the following various values for the global element: -<ul> -<li><span class="uicontrol">abstract</span>. Click <strong>true </strong>if you want the -global element to be abstract. When a global element is declared to be abstract, -it cannot be used in an instance document. Instead, a member of that global -element's substitution group must appear in the instance document.</li> - -<li><span class="uicontrol">block</span>. This field determines whether the global -element may be replaced by an element derived from it.</li> - -<li><span class="uicontrol">final</span>. This field determines whether this global -element may be derived from.</li> - -<li><span class="uicontrol">fixed/default</span>. Click <span class="uicontrol">Browse</span> and -select <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> and -specify an appropriate value. If you select <strong>Fixed</strong>, the global element -has a fixed value, which cannot be changed. If you select <strong>Default</strong>, -the element has a default value.</li> - -<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance -of this global element in an instance of the XML schema (an XML file associated -with the XML schema) must be qualified by a namespace.</li> - -<li><span class="uicontrol">nillable</span>. Select <strong>true</strong> if you do not -want the global element to be able to have any child elements, only attributes. </li> - -<li><span class="uicontrol">substitutionGroup</span>. A substitution group allows -elements to be substituted for other elements.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Attributes</span> tab.</span> You -can use this page to add attributes, attribute references, attributes group -references, and <samp class="codeph">any</samp> attributes to your global element. -</li> - -<li class="stepexpand"><span>An attribute associates an attribute name with a specific type -and value. To add an attribute, right-click in the Attributes page, and click <span class="uicontrol">Add -Attribute</span>.</span> You can specify the following values for -an attribute: -<ul> -<li><span class="uicontrol">fixed/default</span>. Click <span class="uicontrol">Browse</span> and -select <span class="uicontrol">Fixed</span> or <span class="uicontrol">Default</span> and -specify an appropriate value. If you select <strong>Fixed</strong>, the attribute has -a fixed value, which cannot be changed. If you select <strong>Default</strong>, the -attribute has a default value.</li> - -<li><span class="uicontrol">form</span>. Use this field to indicate if the appearance -of this attribute in an instance of the XML schema must be qualified by a -namespace.</li> - -<li><span class="uicontrol">name</span>. Enter the name of the attribute.</li> - -<li><span class="uicontrol">type</span>. Click <span class="uicontrol">Browse</span> and -select the type of the attribute. </li> - -<li><span class="uicontrol">use</span>. This field indicates how an attribute -can be used in an instance document. If you select optional, the attribute -can appear once, but it does not have to. If you select required, the attribute -must appear once. If you select prohibited, the attribute must not appear. <strong>Note</strong>: -If you selected <span class="uicontrol">Default</span>, you must select <strong>optional</strong> in -this field, otherwise the default value will not be valid.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>An attribute reference provides a reference to a global attribute. -To add an attribute reference, right-click in the Attributes page, and click <span class="uicontrol">Add -Attribute Ref</span>.</span> A declaration that references a global -attribute enables the referenced attribute to appear in the instance document -in the context of the referencing declaration. The menu option to add an attribute -reference only appears if there are global attributes defined elsewhere in -the document. Select the reference, then select the global attribute you want -it to reference from the <span class="uicontrol">ref</span> list.</li> - -<li class="stepexpand"><span>An attribute group reference provides a reference to an attribute -group. To add an attribute group reference, right-click in the Attributes -page, and click <span class="uicontrol">Add Attribute Group Ref</span>.</span> A -declaration that references an attribute group enables the referenced attribute -group to appear in the instance document in the context of the referencing -declaration. The menu option to add an attribute group reference only appears -if there are attribute groups defined elsewhere in the document. Select the -reference, then select the attribute group you want it to reference from the <span class="uicontrol">ref</span> list. -</li> - -<li class="stepexpand"><span>An <samp class="codeph">any</samp> element enables element content according -to namespaces, and the corresponding <samp class="codeph">any</samp> attribute element -enables attributes to appear in elements. To add an <samp class="codeph">any</samp> attribute, -right-click in the Attributes page and click <span class="uicontrol">Add Any Attribute</span>.</span> - You can specify the following values for an <samp class="codeph">any</samp> attribute: -<ul> -<li>For a <span class="uicontrol">namespace</span> value, you can -select:<ul> -<li><strong>##any</strong>. This allows any well-formed XML from any namespace.</li> - -<li><strong>##local </strong>. This allows any well-formed XML that is not declared -to be in a namespace.</li> - -<li><strong>##other</strong>. This allows any well-formed XML that is not from the target -namespace of the type being defined.</li> - -<li><strong>##targetNamespace </strong>. This is shorthand for the target namespace -of the type being defined.</li> - -</ul> -</li> - -<li>For a <span class="uicontrol">processContents</span> value, you can select:<ul> -<li><strong>skip</strong>. The XML processor will not validate the attribute content -at all.</li> - -<li><strong>lax</strong>. The XML processor will validate the attribute content as much -as it can.</li> - -<li><strong>strict</strong>. The XML processor will validate all the attribute content.</li> - -</ul> -</li> - -</ul> - -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this global element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section">You can add a content model to a global element, which is the representation -of any data that can be contained inside the global element. For more information -about working with content models, refer to the related tasks.</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div> -<div><a href="../topics/taddelmr.html" title="An element reference provides a reference to a global element. A declaration that references a global element enables the referenced global element to appear in the instance document in the context of the referencing declaration.">Adding element references</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.dita deleted file mode 100644 index 3aa051e30b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.dita +++ /dev/null @@ -1,41 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddgrpr" xml:lang="en-us">
-<title>Adding group references</title>
-<titlealts>
-<searchtitle>Adding group references</searchtitle>
-</titlealts>
-<shortdesc>A group reference is a declaration that references a group. It
-enables the referenced group to appear in the instance document in the context
-of the referencing declaration.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>group features</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>group features</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>The menu option to add a group reference only appears if there are
-groups defined elsewhere in the document.<p>The following instructions were
-written for the Resource perspective, but they will also work in many other
-perspectives.</p><p>To add a group reference, follow these steps:</p></context>
-<steps>
-<step><cmd>In the Design view, right-click the content model you want to work
-with and select <uicontrol>Add Group Ref</uicontrol>.</cmd></step>
-<step><cmd>Select the new group reference.</cmd></step>
-<step><cmd>In the Properties view, select the group you want to refer to in
-the <uicontrol>ref</uicontrol> list.</cmd></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this group reference.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info>
-</step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002277?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html deleted file mode 100644 index 130e49adbb..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrpr.html +++ /dev/null @@ -1,71 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding group references" /> -<meta name="abstract" content="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration." /> -<meta name="description" content="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration." /> -<meta content="XML schema editor, adding, group references, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, group references, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddgrup.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddgrpr" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding group references</title> -</head> -<body id="taddgrpr"><a name="taddgrpr"><!-- --></a> - - -<h1 class="topictitle1">Adding group references</h1> - - - - -<div><p>A group reference is a declaration that references a group. It -enables the referenced group to appear in the instance document in the context -of the referencing declaration.</p> - -<div class="section">The menu option to add a group reference only appears if there are -groups defined elsewhere in the document.<p>The following instructions were -written for the Resource perspective, but they will also work in many other -perspectives.</p> -<p>To add a group reference, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, right-click the content model you want to work -with and select <span class="uicontrol">Add Group Ref</span>.</span></li> - -<li class="stepexpand"><span>Select the new group reference.</span></li> - -<li class="stepexpand"><span>In the Properties view, select the group you want to refer to in -the <span class="uicontrol">ref</span> list.</span></li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this group reference.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description. -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddgrup.html" title="When you create a group, it automatically contains a content model. The content model is a representation of any data that can be grouped together by the group, such as elements, element references, and group references.">Adding groups</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.dita deleted file mode 100644 index 5dce7f28ae..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="taddgrup" xml:lang="en-us">
-<title>Adding groups</title>
-<titlealts>
-<searchtitle>Adding groups</searchtitle>
-</titlealts>
-<shortdesc>When you create a group, it automatically contains a content model.
-The content model is a representation of any data that can be grouped together
-by the group, such as elements, element references, and group references.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>groups</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>groups</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p></p><p>The following instructions were written for the Resource
-perspective, but they will also work in many other perspectives.</p><p>To
-add a group, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, right-click <b>Groups</b>, and click <uicontrol>Add
-Group</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, type a new name for the group in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this group element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to
-specify the schema and add XML content to your annotations.</info></step>
-<step><cmd>In the Outline view, expand the <uicontrol>Groups</uicontrol> folder
-and your new group.</cmd></step>
-<step><cmd>Your group automatically contains a content model. </cmd><info>A
-group's content model is the representation of any data that can be contained
-inside the group. For more information about working with content models,
-refer to the related tasks.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002502?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html deleted file mode 100644 index b8141ed975..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddgrup.html +++ /dev/null @@ -1,80 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding groups" /> -<meta name="abstract" content="When you create a group, it automatically contains a content model. The content model is a representation of any data that can be grouped together by the group, such as elements, element references, and group references." /> -<meta name="description" content="When you create a group, it automatically contains a content model. The content model is a representation of any data that can be grouped together by the group, such as elements, element references, and group references." /> -<meta content="XML schema editor, adding, groups, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, groups, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddgrpr.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddcmod.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddgrup" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding groups</title> -</head> -<body id="taddgrup"><a name="taddgrup"><!-- --></a> - - -<h1 class="topictitle1">Adding groups</h1> - - - - -<div><p>When you create a group, it automatically contains a content model. -The content model is a representation of any data that can be grouped together -by the group, such as elements, element references, and group references.</p> - -<div class="section"><p /> -<p>The following instructions were written for the Resource -perspective, but they will also work in many other perspectives.</p> -<p>To -add a group, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, right-click <strong>Groups</strong>, and click <span class="uicontrol">Add -Group</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, type a new name for the group in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this group element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to -specify the schema and add XML content to your annotations.</li> - -<li class="stepexpand"><span>In the Outline view, expand the <span class="uicontrol">Groups</span> folder -and your new group.</span></li> - -<li class="stepexpand"><span>Your group automatically contains a content model. </span> A -group's content model is the representation of any data that can be contained -inside the group. For more information about working with content models, -refer to the related tasks.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddgrpr.html" title="A group reference is a declaration that references a group. It enables the referenced group to appear in the instance document in the context of the referencing declaration.">Adding group references</a></div> -<div><a href="../topics/taddcmod.html" title="A content model is the representation of any data that can be contained inside an element, global element, complex type, or group. It is a formal description of the structure and permissible content of an element, global element, complex type, or group, which may be used to validate a document instance.">Adding content models</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.dita deleted file mode 100644 index 0188c47ae3..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.dita +++ /dev/null @@ -1,76 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddimpt" xml:lang="en-us">
-<title>Adding import elements</title>
-<titlealts>
-<searchtitle>Adding import elements</searchtitle>
-</titlealts>
-<shortdesc>As schemas become larger, it is often desirable to divide their
-content among several schema documents for purposes such as ease of maintenance,
-reuse, and readability. You can use an <codeph>import</codeph> element to
-bring in definitions and declarations from an imported schema into the current
-schema. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>import elements</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>import elements</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The imported schema can come from a different namespace than the
-current schema does.</p><p>You can add multiple import elements to an XML
-schema, however, prefixes and namespaces have to unique amongst the imported
-schemas.</p><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To add an import
-element, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, select your schema.</cmd><info>The entire
-schema and its contents should be displayed in the Design view.</info></step>
-<step><cmd>In the Design view, right click in the <b>Directives</b> section
-and click <uicontrol>Add Import</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, click the <b>General</b> tab and click <uicontrol>Browse</uicontrol> <image
-href="../images/Browse.gif"><alt>This graphic is the Browse button</alt></image> to
-the right of the <uicontrol>Schema location</uicontrol> field.</cmd></step>
-<step><cmd>If you want to import an XML schema located in the workbench:</cmd>
-<substeps>
-<substep><cmd>Select <uicontrol>Workbench projects</uicontrol> and click <uicontrol>Next</uicontrol>. </cmd>
-</substep>
-<substep><cmd>Select the schema you want to import and click <uicontrol>Finish</uicontrol>.</cmd>
-</substep>
-</substeps>
-</step>
-<step><cmd>If you want to import an XML schema located on the Web:</cmd>
-<substeps>
-<substep><cmd>Select <uicontrol>HTTP</uicontrol> and click <uicontrol>Next</uicontrol>.</cmd>
-</substep>
-<substep><cmd>Type the URL of the XML schema and click <uicontrol>Finish</uicontrol>.</cmd>
-<info><note>A local copy of the schema will not be stored in the workbench.
-Every time you validate your schema, the schema's contents will be checked
-from the URL you specify.</note></info></substep>
-</substeps>
-</step>
-<step><cmd>The XML schema editor will retrieve the namespace for the imported
-XML schema file and display it as read-only in the <uicontrol>Namespace</uicontrol> field.</cmd>
-</step>
-<step><cmd>If necessary, type a unique prefix for this namespace in the <uicontrol>Prefix</uicontrol> field.</cmd>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this import element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<result><p>Once you have added an import element to your XML schema, when
-you define new elements, attributes, complex types, or simple types where
-you can specify type information, any declarations from the included schema
-will be available in the <uicontrol>Type</uicontrol> list for the element,
-attribute, complex or simple type.</p></result>
-<postreq></postreq>
-</taskbody>
-</task>
-<?Pub *0000004340?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html deleted file mode 100644 index d6946ec368..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddimpt.html +++ /dev/null @@ -1,128 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding import elements" /> -<meta name="abstract" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema." /> -<meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema." /> -<meta content="XML schema editor, adding, import elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, import elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddrdfn.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddimpt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding import elements</title> -</head> -<body id="taddimpt"><a name="taddimpt"><!-- --></a> - - -<h1 class="topictitle1">Adding import elements</h1> - - - - -<div><p>As schemas become larger, it is often desirable to divide their -content among several schema documents for purposes such as ease of maintenance, -reuse, and readability. You can use an <samp class="codeph">import</samp> element to -bring in definitions and declarations from an imported schema into the current -schema. </p> - -<div class="section"><p>The imported schema can come from a different namespace than the -current schema does.</p> -<p>You can add multiple import elements to an XML -schema, however, prefixes and namespaces have to unique amongst the imported -schemas.</p> -<p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To add an import -element, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire -schema and its contents should be displayed in the Design view.</li> - -<li class="stepexpand"><span>In the Design view, right click in the <strong>Directives</strong> section -and click <span class="uicontrol">Add Import</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to -the right of the <span class="uicontrol">Schema location</span> field.</span></li> - -<li class="stepexpand"><span>If you want to import an XML schema located in the workbench:</span> -<ol type="a"> -<li><span>Select <span class="uicontrol">Workbench projects</span> and click <span class="uicontrol">Next</span>. </span> -</li> - -<li><span>Select the schema you want to import and click <span class="uicontrol">Finish</span>.</span> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>If you want to import an XML schema located on the Web:</span> -<ol type="a"> -<li class="substepexpand"><span>Select <span class="uicontrol">HTTP</span> and click <span class="uicontrol">Next</span>.</span> -</li> - -<li class="substepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span> - <div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench. -Every time you validate your schema, the schema's contents will be checked -from the URL you specify.</div> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>The XML schema editor will retrieve the namespace for the imported -XML schema file and display it as read-only in the <span class="uicontrol">Namespace</span> field.</span> -</li> - -<li class="stepexpand"><span>If necessary, type a unique prefix for this namespace in the <span class="uicontrol">Prefix</span> field.</span> -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this import element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>Once you have added an import element to your XML schema, when -you define new elements, attributes, complex types, or simple types where -you can specify type information, any declarations from the included schema -will be available in the <span class="uicontrol">Type</span> list for the element, -attribute, complex or simple type.</p> -</div> - -<div class="section" /> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div> -<div><a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents.">Adding redefine elements</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.dita deleted file mode 100644 index bdc5924c86..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.dita +++ /dev/null @@ -1,77 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddincl" xml:lang="en-us">
-<title>Adding include elements</title>
-<titlealts>
-<searchtitle>Adding include elements</searchtitle>
-</titlealts>
-<shortdesc>As schemas become larger, it is often desirable to divide their
-content among several schema documents for purposes such as ease of maintenance,
-reuse, and readability. You can use the <codeph>include</codeph> element to
-bring in definitions and declarations from the included schema
-into the current schema. The included schema must be in the same target namespace
-as the including schema. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>include elements</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>include elements</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the XML perspective,
-but they will also work in many other perspectives.</p><p>To add an include
-element, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, select your schema.</cmd><info>The entire
-schema and its contents are displayed in the Design view.</info></step>
-<step><cmd>In the Design view, right-click in the <b>Directives</b> section
-and click <uicontrol>Add Include</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, click the <b>General</b> tab and click <uicontrol>Browse</uicontrol> <image
-href="../images/Browse.gif"><alt>This graphic is the Browse button</alt></image> to
-the right of the <uicontrol>Schema location</uicontrol> field.</cmd><info>The
-XML schema file you select must have the same namespace as the current schema.</info>
-</step>
-<step><cmd>If you want to select an XML schema located in the workbench, select <uicontrol>Workbench
-projects</uicontrol> and click <uicontrol>Next</uicontrol>. </cmd></step>
-<step><cmd>Select the schema you want to include and click <uicontrol>Finish</uicontrol>.</cmd>
-</step>
-<step><cmd>If you want to select an XML schema located on the Web, select <uicontrol>HTTP</uicontrol> and
-click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Type the URL of the XML schema and click <uicontrol>Finish</uicontrol>.</cmd>
-<info><note> A local copy of the schema will not be stored in the workbench.
-Every time you validate your schema, the schema's contents will be checked
-from the URL you specify.</note></info></step>
-<step><cmd>The XML schema editor will retrieve the location of the included
-XML schema file, and display it in the <uicontrol>Schema location</uicontrol> field.
-This field can be edited at any time to reflect the location of the XML schema
-file.</cmd></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this include element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<result><p>Once you have added the include element to your XML schema, when
-you define new elements, attributes, complex types, or simple types where
-you can specify type information, any declarations from the included schema
-will be available in the <uicontrol>Type</uicontrol> list for the element,
-attribute, complex or simple type.</p><p>For example, if Address.xsd has the
-following content:</p><codeblock><complexType name="Address">
- <sequence>
- <element name="name" type="string">
- <element name="street" type="string">
- </sequence>
-</complexType>
-</codeblock>and you have an XML schema called PurchaseOrder.xsd that has added
-an include for Address.xsd, then when defining a new element in PurchaseOrder,
-you can select Address as its type. <p>(c) Copyright 2001, World Wide Web
-Consortium (Massachusetts Institute of Technology, Institut National de Recherche
-en Informatique et en Automatique, Keio University).</p></result>
-</taskbody>
-</task>
-<?Pub *0000004728?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html deleted file mode 100644 index 7abba83f41..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddincl.html +++ /dev/null @@ -1,124 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding include elements" /> -<meta name="abstract" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." /> -<meta name="description" content="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema." /> -<meta content="XML schema editor, adding, include elements, XML schema files, include elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, include elements, XML schema files, include elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddrdfn.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddincl" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding include elements</title> -</head> -<body id="taddincl"><a name="taddincl"><!-- --></a> - - -<h1 class="topictitle1">Adding include elements</h1> - - - - -<div><p>As schemas become larger, it is often desirable to divide their -content among several schema documents for purposes such as ease of maintenance, -reuse, and readability. You can use the <samp class="codeph">include</samp> element to -bring in definitions and declarations from the included schema -into the current schema. The included schema must be in the same target namespace -as the including schema. </p> - -<div class="section"><p>The following instructions were written for the XML perspective, -but they will also work in many other perspectives.</p> -<p>To add an include -element, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire -schema and its contents are displayed in the Design view.</li> - -<li class="stepexpand"><span>In the Design view, right-click in the <strong>Directives</strong> section -and click <span class="uicontrol">Add Include</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to -the right of the <span class="uicontrol">Schema location</span> field.</span> The -XML schema file you select must have the same namespace as the current schema. -</li> - -<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select <span class="uicontrol">Workbench -projects</span> and click <span class="uicontrol">Next</span>. </span></li> - -<li class="stepexpand"><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span> -</li> - -<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select <span class="uicontrol">HTTP</span> and -click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span> - <div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench. -Every time you validate your schema, the schema's contents will be checked -from the URL you specify.</div> -</li> - -<li class="stepexpand"><span>The XML schema editor will retrieve the location of the included -XML schema file, and display it in the <span class="uicontrol">Schema location</span> field. -This field can be edited at any time to reflect the location of the XML schema -file.</span></li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this include element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>Once you have added the include element to your XML schema, when -you define new elements, attributes, complex types, or simple types where -you can specify type information, any declarations from the included schema -will be available in the <span class="uicontrol">Type</span> list for the element, -attribute, complex or simple type.</p> -<p>For example, if Address.xsd has the -following content:</p> -<pre><complexType name="Address"> - <sequence> - <element name="name" type="string"> - <element name="street" type="string"> - </sequence> -</complexType> -</pre> -and you have an XML schema called PurchaseOrder.xsd that has added -an include for Address.xsd, then when defining a new element in PurchaseOrder, -you can select Address as its type. <p>(c) Copyright 2001, World Wide Web -Consortium (Massachusetts Institute of Technology, Institut National de Recherche -en Informatique et en Automatique, Keio University).</p> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div> -<div><a href="../topics/taddrdfn.html" title="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents.">Adding redefine elements</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.dita deleted file mode 100644 index 2728d0512c..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.dita +++ /dev/null @@ -1,51 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddnot" xml:lang="en-us">
-<title>Adding notations</title>
-<titlealts>
-<searchtitle>Adding notations</searchtitle>
-</titlealts>
-<shortdesc>A notation is a means of associating a binary description with
-an entity or attribute. The most common uses of notations are to include familiar
-types of binary references, such as GIFs and JPGs, in an XML file.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>notations</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>notations</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>For example, you are making a catalogue of your clothing and want
-to include an image of one of your shirts. You would have to create a notation
-like this: <userinput><notation name="My_Shirt" system="GIF"></notation></userinput> which
-defines a notation for a GIF image.</p><p>The following instructions were
-written for the Resource perspective, but they will also work in many other
-perspectives.</p><p>To create a notation, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, right-click your XML schema and click <uicontrol>Add
-Notation</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, type the name of the notation in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>Click the <uicontrol>Other</uicontrol> tab.</cmd></step>
-<step><cmd>In the <uicontrol>public</uicontrol> field, type a public identifier.</cmd>
-<info> This is optional if you enter a value in the <uicontrol>system</uicontrol> field.</info>
-</step>
-<step><cmd>In the <uicontrol>system</uicontrol> field, type a URI reference.</cmd>
-<info> This is optional if you enter a value in the <uicontrol>public</uicontrol> field.</info>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this notation.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description. <uicontrol>App
-Info</uicontrol> page can be used to provide information for applications.</info>
-</step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002959?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html deleted file mode 100644 index 75078b0b7f..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddnot.html +++ /dev/null @@ -1,52 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html - PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html> -<head> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" /> -<title>Adding notations</title> -</head> -<body id="taddnot"><a name="taddnot"><!-- --></a> - -<h1 class="topictitle1">Adding notations</h1> -<div><p>A notation is a means of associating a binary description with -an entity or attribute. The most common uses of notations are to include familiar -types of binary references, such as GIFs and JPGs, in an XML file.</p> -<div class="section"><p>For example, you are making a catalogue of your clothing and want -to include an image of one of your shirts. You would have to create a notation -like this: <kbd class="userinput"><notation name="My_Shirt" system="GIF"></notation></kbd> which -defines a notation for a GIF image.</p> -<p>The following instructions were written for the Resource perspective, but -they will also work in many other perspectives.</p> -<p>To -create a notation, follow these steps:</p> -</div> -<ol><li class="skipspace"><span>Open your XML schema in the XML schema editor.</span></li> -<li class="skipspace"><span>In the Outline view, right-click your XML schema and click -<b> <span class="uicontrol">Add -Notation</span></b>.</span></li> -<li class="skipspace"><span>In the Properties view, type the name of the notation in the -<b> <span class="uicontrol">Name</span></b> field.</span></li> -<li class="skipspace"><span>Click the <b> <span class="uicontrol">Other</span></b> tab.</span></li> -<li class="skipspace"><span>In the <b> <span class="uicontrol">public</span></b> field, type a public identifier.</span> This is optional if you enter a value in the -<b> <span class="uicontrol">system</span></b> field.</li> -<li class="skipspace"><span>In the <b> <span class="uicontrol">system</span></b> field, type a URI reference.</span> This is optional if you enter a value in the -<b> <span class="uicontrol">public</span></b> field.</li> -<li class="skipspace"><span>Click the <b> <span class="uicontrol">Documentation</span></b> tab if you want -to provide any information about this notation.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description, and the <span class="uicontrol">App -Info</span> page can be used to provide information for applications.</li> -</ol> -</div> -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.dita deleted file mode 100644 index 78fc3832e7..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.dita +++ /dev/null @@ -1,64 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddrdfn" xml:lang="en-us">
-<title>Adding redefine elements</title>
-<titlealts>
-<searchtitle>Adding redefine elements</searchtitle>
-</titlealts>
-<shortdesc>You can use the <codeph>redefine</codeph> mechanism to redefine
-simple and complex types, groups, and attribute groups obtained from external
-schema files. When you redefine a component, you are modifying its contents.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>adding redefine elements</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>adding redefine elements</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>Like the <codeph>include</codeph> mechanism, <codeph>redefine</codeph> requires
-the external components to be in the same target namespace as the redefining
-schema, although external components from schemas that have no namespace can
-also be redefined.</p><p>The following instructions were written for the Resource
-perspective, but they will also work in many other perspectives.</p><p>To
-add a redefine element:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, select your schema.</cmd><info>The entire
-schema and its contents are displayed in the Design view.</info></step>
-<step><cmd>In the Design view, right-click in the <b>Directives</b> section
-and click <uicontrol>Add Redefine</uicontrol>.</cmd></step>
-<step><cmd>In the Properties view, click the <b>General</b> tab and click <uicontrol>Browse</uicontrol> <image
-href="../images/Browse.gif"><alt>This graphic is the Browse button</alt></image> to
-the right of the <uicontrol>Schema location</uicontrol> field.</cmd>
-<info>The XML schema file you select must have the same namespace as the current
-schema.</info></step>
-<step><cmd>If you want to select an XML schema located in the workbench, select <uicontrol>Workbench
-projects</uicontrol> and click <uicontrol>Next.</uicontrol></cmd></step>
-<step><cmd>Select the schema you want to include and click <uicontrol>Finish</uicontrol>.</cmd>
-</step>
-<step><cmd>If you want to select an XML schema located on the Web, select <uicontrol>HTTP</uicontrol> and
-click <uicontrol>Next</uicontrol>.</cmd></step>
-<step><cmd>Type the URL of the XML schema and click <uicontrol>Finish</uicontrol>.</cmd>
-<info> <note>A local copy of the schema will not be stored in the workbench.
-Every time you validate your schema, the schema's contents will be checked
-from the URL you specify.</note></info></step>
-<step><cmd>The XML schema editor will retrieve the location of the included
-XML schema file, and display it in the <uicontrol>Schema location</uicontrol> field.
-This field can be edited at any time to reflect the location of the XML schema
-file.</cmd></step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this redefine element.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-<result><p>Once you have added the redefine element to your XML schema, you
-can redefine any of the simple and complex types, groups, and attribute groups
-in the XML schema you selected in the redefine element. </p></result>
-</taskbody>
-</task>
-<?Pub *0000004055?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html deleted file mode 100644 index d7820c8d36..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddrdfn.html +++ /dev/null @@ -1,109 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding redefine elements" /> -<meta name="abstract" content="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents." /> -<meta name="description" content="You can use the redefine mechanism to redefine simple and complex types, groups, and attribute groups obtained from external schema files. When you redefine a component, you are modifying its contents." /> -<meta content="XML schema editor, adding, redefine elements, XML schema files, redefine elements, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, redefine elements, XML schema files, redefine elements, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rnmspc.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddrdfn" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding redefine elements</title> -</head> -<body id="taddrdfn"><a name="taddrdfn"><!-- --></a> - - -<h1 class="topictitle1">Adding redefine elements</h1> - - - - -<div><p>You can use the <samp class="codeph">redefine</samp> mechanism to redefine -simple and complex types, groups, and attribute groups obtained from external -schema files. When you redefine a component, you are modifying its contents.</p> - -<div class="section"><p>Like the <samp class="codeph">include</samp> mechanism, <samp class="codeph">redefine</samp> requires -the external components to be in the same target namespace as the redefining -schema, although external components from schemas that have no namespace can -also be redefined.</p> -<p>The following instructions were written for the Resource -perspective, but they will also work in many other perspectives.</p> -<p>To -add a redefine element:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, select your schema.</span> The entire -schema and its contents are displayed in the Design view.</li> - -<li class="stepexpand"><span>In the Design view, right-click in the <strong>Directives</strong> section -and click <span class="uicontrol">Add Redefine</span>.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <strong>General</strong> tab and click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> to -the right of the <span class="uicontrol">Schema location</span> field.</span> - The XML schema file you select must have the same namespace as the current -schema.</li> - -<li class="stepexpand"><span>If you want to select an XML schema located in the workbench, select <span class="uicontrol">Workbench -projects</span> and click <span class="uicontrol">Next.</span></span></li> - -<li class="stepexpand"><span>Select the schema you want to include and click <span class="uicontrol">Finish</span>.</span> -</li> - -<li class="stepexpand"><span>If you want to select an XML schema located on the Web, select <span class="uicontrol">HTTP</span> and -click <span class="uicontrol">Next</span>.</span></li> - -<li class="stepexpand"><span>Type the URL of the XML schema and click <span class="uicontrol">Finish</span>.</span> - <div class="note"><span class="notetitle">Note:</span> A local copy of the schema will not be stored in the workbench. -Every time you validate your schema, the schema's contents will be checked -from the URL you specify.</div> -</li> - -<li class="stepexpand"><span>The XML schema editor will retrieve the location of the included -XML schema file, and display it in the <span class="uicontrol">Schema location</span> field. -This field can be edited at any time to reflect the location of the XML schema -file.</span></li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this redefine element.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -<div class="section"><p>Once you have added the redefine element to your XML schema, you -can redefine any of the simple and complex types, groups, and attribute groups -in the XML schema you selected in the redefine element. </p> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div> -<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div> -</div> -<div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rnmspc.html" title="An XML namespace is a collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.">XML namespaces</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.dita deleted file mode 100644 index 3122220d61..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.dita +++ /dev/null @@ -1,58 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="taddreg" xml:lang="en-us">
-<title>Adding pattern facets to simple types</title>
-<titlealts>
-<searchtitle>Adding pattern facets to simple types</searchtitle>
-</titlealts>
-<shortdesc>A pattern facet can be used to constrain the value of a type's
-lexical space (the set of string literals that represent the values of a type),
-which indirectly constrains the value space.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>pattern facets</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>pattern facets</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p> The value of the pattern is called a regular expression. You
-can specify it using the <uicontrol>Regular Expression</uicontrol> wizard.</p><p>To
-add a pattern to a simple type:</p></context>
-<steps>
-<step><cmd>In the Design view, select the simple type you want to work with.</cmd>
-</step>
-<step><cmd>In the Properties view, click the <uicontrol>Constraints</uicontrol> tab,
-then <uicontrol>Patterns</uicontrol>.</cmd></step>
-<step><cmd>Click <uicontrol>Add</uicontrol>.</cmd><info>The Regular Expression
-wizard opens.</info></step>
-<step><cmd>Select the token you want to add to the expression.</cmd></step>
-<step><cmd>Indicate how often you want the token to appear in order for a
-match to succeed:</cmd>
-<choices>
-<choice>If you want the token to repeat, click <uicontrol>Repeat</uicontrol> and
-specify the number of times the token must appear.</choice>
-</choices>
-<choices>
-<choice> If you want to specify a minimum and maximum number of times the
-token can appear, click <uicontrol>Range</uicontrol> and enter a minimum and
-maximum value.</choice>
-</choices>
-</step>
-<step><cmd>To add the token to the regular expression, click <uicontrol>Add</uicontrol>. </cmd>
-</step>
-<step><cmd>To create the entire expression, repeat steps 4 - 6 as necessary.</cmd>
-</step>
-<step><cmd>When you are finished, click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>(Optional) To test against the regular expression and see if a
-match occurs, enter sample text.</cmd></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd><stepresult> The regular
-expression will appear in the Patterns page. <note type="tip"> To edit an
-existing pattern, select it in the Patterns page and click <uicontrol>Edit</uicontrol>.
-To delete an existing pattern, select it in the Patterns page and click <uicontrol>Delete</uicontrol>. </note></stepresult>
-</step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002952?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html deleted file mode 100644 index 2a0c07aa9e..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddreg.html +++ /dev/null @@ -1,99 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding pattern facets to simple types" /> -<meta name="abstract" content="A pattern facet can be used to constrain the value of a type's lexical space (the set of string literals that represent the values of a type), which indirectly constrains the value space." /> -<meta name="description" content="A pattern facet can be used to constrain the value of a type's lexical space (the set of string literals that represent the values of a type), which indirectly constrains the value space." /> -<meta content="XML schema editor, adding, pattern facets, XML schema files, pattern facets, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, pattern facets, XML schema files, pattern facets, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddsmpt.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddreg" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding pattern facets to simple types</title> -</head> -<body id="taddreg"><a name="taddreg"><!-- --></a> - - -<h1 class="topictitle1">Adding pattern facets to simple types</h1> - - - - -<div><p>A pattern facet can be used to constrain the value of a type's -lexical space (the set of string literals that represent the values of a type), -which indirectly constrains the value space.</p> - -<div class="section"><p> The value of the pattern is called a regular expression. You -can specify it using the <span class="uicontrol">Regular Expression</span> wizard.</p> -<p>To -add a pattern to a simple type:</p> -</div> - -<ol> -<li class="stepexpand"><span>In the Design view, select the simple type you want to work with.</span> -</li> - -<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">Constraints</span> tab, -then <span class="uicontrol">Patterns</span>.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Add</span>.</span> The Regular Expression -wizard opens.</li> - -<li class="stepexpand"><span>Select the token you want to add to the expression.</span></li> - -<li class="stepexpand"><span>Indicate how often you want the token to appear in order for a -match to succeed:</span> -<ul> -<li>If you want the token to repeat, click <span class="uicontrol">Repeat</span> and -specify the number of times the token must appear.</li> - -</ul> - -<ul> -<li> If you want to specify a minimum and maximum number of times the -token can appear, click <span class="uicontrol">Range</span> and enter a minimum and -maximum value.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>To add the token to the regular expression, click <span class="uicontrol">Add</span>. </span> -</li> - -<li class="stepexpand"><span>To create the entire expression, repeat steps 4 - 6 as necessary.</span> -</li> - -<li class="stepexpand"><span>When you are finished, click <span class="uicontrol">Next</span>.</span> -</li> - -<li class="stepexpand"><span>(Optional) To test against the regular expression and see if a -match occurs, enter sample text.</span></li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span> The regular -expression will appear in the Patterns page. <div class="tip"><span class="tiptitle">Tip:</span> To edit an -existing pattern, select it in the Patterns page and click <span class="uicontrol">Edit</span>. -To delete an existing pattern, select it in the Patterns page and click <span class="uicontrol">Delete</span>. </div> - -</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddsmpt.html" title="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype.">Adding simple types</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.dita deleted file mode 100644 index 189a8ac643..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.dita +++ /dev/null @@ -1,132 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="taddsmpt" xml:lang="en-us">
-<title>Adding simple types</title>
-<titlealts>
-<searchtitle>Adding simple types</searchtitle>
-</titlealts>
-<shortdesc>Simple types are used to create derived datatypes.
-They provide a set of constraints on the value space (a set of values) and
-the lexical space (a set of valid literals) of a datatype.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>simple types</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>simple types</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>A simple type cannot have element content and cannot carry attributes.
-Elements that contain numbers (and strings, and dates, and so on) but do not
-contain any sub-elements have a simple type.</p><p>The following instructions
-were written for the Resource perspective, but they will also work in many
-other perspectives.</p><p>To add a simple type:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, right-click <b>Types</b>, and click <uicontrol>Add
-Simple Type</uicontrol>.</cmd></step>
-<step><cmd>In the Outline view, select the new simple type.</cmd></step>
-<step><cmd>In the Properties view, click the <uicontrol>General</uicontrol> tab.</cmd>
-</step>
-<step><cmd>Type a new name for the simple type in the <uicontrol>Name</uicontrol> field.</cmd>
-</step>
-<step><cmd>You can select the following options from the <uicontrol>Variety</uicontrol> list:</cmd>
-<choices>
-<choice><uicontrol>atomic</uicontrol>. Atomic types are all the simple types
-built into the XML schema language.</choice>
-<choice><uicontrol>list</uicontrol>. List types are comprised of sequences
-of atomic types. They have values that are comprised of finite-length sequences
-of atomic values. </choice>
-<choice><uicontrol>union</uicontrol>. A union type enables an element or attribute
-value to be one or more instances of one type drawn from the union of multiple
-atomic and list types.</choice>
-</choices>
-</step>
-<step><cmd>If you selected <uicontrol>atomic</uicontrol> from the <uicontrol>Variety</uicontrol> list,
-click <uicontrol>Browse</uicontrol> <image href="../images/Browse.gif"><alt>This
-graphic is the Browse button</alt></image> next to the <uicontrol>Base type</uicontrol> field
-to specify a base type for the simple type.</cmd><info>The Set Type dialog
-box lists all built-in and user-defined types currently available. You can
-change the <uicontrol>Scope</uicontrol> of the list by selecting one of the
-following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></info></step>
-<step><cmd>If you selected <uicontrol>list</uicontrol> from the <uicontrol>Variety</uicontrol> list,
-click <uicontrol>Browse</uicontrol> <image href="../images/Browse.gif"><alt>This
-graphic is the Browse button</alt></image> next to the <uicontrol>Item type</uicontrol> field
-to specify a item type for the simple type.</cmd><info>The Set Type dialog
-box lists all built-in and user-defined types currently available. You can
-change the <uicontrol>Scope</uicontrol> of the list by selecting one of the
-following options:<ul>
-<li><uicontrol>Workspace</uicontrol>. Lists all of the types available in
-your workspace. </li>
-<li><uicontrol>Enclosing Project</uicontrol>. Lists all of the types available
-in the project that contains your file. </li>
-<li>(Default) <uicontrol>Current Resource</uicontrol>. List all of the types
-available in your current file.</li>
-<li><uicontrol>Working Sets</uicontrol>. List all the types available within
-the selected working set.</li>
-</ul></info></step>
-<step><cmd>If you selected <uicontrol>union</uicontrol> from the <uicontrol>Variety</uicontrol> list,
-click <uicontrol>Browse</uicontrol> <image href="../images/Browse.gif"><alt>This
-graphic is the Browse button</alt></image> next to the <uicontrol>Member types</uicontrol> field
-to specify the member types for the simple type.</cmd><info>You can select
-to add both <uicontrol>Built-in simple types</uicontrol> and <uicontrol>User-defined
-simple types</uicontrol> to the member types value list. </info></step>
-<step><cmd>Click the <uicontrol>Constraints</uicontrol> tab.</cmd><info>From
-here you will be able to set specific constraint values including length constraints,
-enumerations, and patterns. </info>
-<substeps>
-<substep><cmd>Enumerations help you to define a set of valid values for simple
-types. They are the actual values the simple type can take as valid values
-in the instance document. You can either add one enumeration or several enumerations
-at a time:</cmd><info><ul>
-<li>To add one enumeration at a time, under <uicontrol>Specific constraint
-values</uicontrol>, select <uicontrol>Enumerations</uicontrol> and click <uicontrol>Add</uicontrol> and
-specify a value for the enumeration.</li>
-<li>To add several enumerations at one time, follow these steps:<ol>
-<li>Select <uicontrol>Enumerations</uicontrol>.</li>
-<li>Click <uicontrol>Add</uicontrol>.</li>
-<li>Enter the value of each enumeration. Each value must be separated by the <uicontrol>Delimiter
-character</uicontrol>. For example: <codeph>First, Second</codeph> will create
-two enumerations, one with the value "First" and one with the value "Second".</li>
-<li>Select the <uicontrol>Preserve leading and trailing whitespace</uicontrol> check
-box if you want any white space around your enumeration values to be preserved.
-If you select this check box, the values of <codeph>First, Second</codeph> will
-show up as "First" and " Second" (there is a space before Second) because
-you put a space before "Second" when entering the value.</li>
-<li>Click <uicontrol>OK</uicontrol>. Your enumerations will be created and
-appear in the Properties view.</li>
-</ol></li>
-</ul></info></substep>
-<substep><cmd>Patterns help you to place certain constraints regarding allowable
-values.</cmd><info>For example, you could restrict the field to only accept
-input which follows the pattern "five digits followed by two upper-case ASCII
-letters". To set a pattern constraint:<ol>
-<li>Select <uicontrol>Patterns</uicontrol>.</li>
-<li>Click <uicontrol>Add</uicontrol>.</li>
-<li>Create the regular expression pattern you wish to use as your constraint
-using the <uicontrol>Regular Expression</uicontrol> wizard.</li>
-<li>Click <uicontrol>Finish</uicontrol>.</li>
-</ol></info></substep>
-</substeps>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this simple type.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000007829?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html deleted file mode 100644 index f6991670b3..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/taddsmpt.html +++ /dev/null @@ -1,198 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Adding simple types" /> -<meta name="abstract" content="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype." /> -<meta name="description" content="Simple types are used to create derived datatypes. They provide a set of constraints on the value space (a set of values) and the lexical space (a set of valid literals) of a datatype." /> -<meta content="XML schema editor, adding, simple types, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, adding, simple types, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddreg.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="taddsmpt" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Adding simple types</title> -</head> -<body id="taddsmpt"><a name="taddsmpt"><!-- --></a> - - -<h1 class="topictitle1">Adding simple types</h1> - - - - -<div><p>Simple types are used to create derived datatypes. -They provide a set of constraints on the value space (a set of values) and -the lexical space (a set of valid literals) of a datatype.</p> - -<div class="section"><p>A simple type cannot have element content and cannot carry attributes. -Elements that contain numbers (and strings, and dates, and so on) but do not -contain any sub-elements have a simple type.</p> -<p>The following instructions -were written for the Resource perspective, but they will also work in many -other perspectives.</p> -<p>To add a simple type:</p> -</div> - -<ol> -<li class="stepexpand"><span>Open your XML schema in the XML schema editor.</span></li> - -<li class="stepexpand"><span>In the Outline view, right-click <strong>Types</strong>, and click <span class="uicontrol">Add -Simple Type</span>.</span></li> - -<li class="stepexpand"><span>In the Outline view, select the new simple type.</span></li> - -<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab.</span> -</li> - -<li class="stepexpand"><span>Type a new name for the simple type in the <span class="uicontrol">Name</span> field.</span> -</li> - -<li class="stepexpand"><span>You can select the following options from the <span class="uicontrol">Variety</span> list:</span> -<ul> -<li><span class="uicontrol">atomic</span>. Atomic types are all the simple types -built into the XML schema language.</li> - -<li><span class="uicontrol">list</span>. List types are comprised of sequences -of atomic types. They have values that are comprised of finite-length sequences -of atomic values. </li> - -<li><span class="uicontrol">union</span>. A union type enables an element or attribute -value to be one or more instances of one type drawn from the union of multiple -atomic and list types.</li> - -</ul> - -</li> - -<li class="stepexpand"><span>If you selected <span class="uicontrol">atomic</span> from the <span class="uicontrol">Variety</span> list, -click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Base type</span> field -to specify a base type for the simple type.</span> The Set Type dialog -box lists all built-in and user-defined types currently available. You can -change the <span class="uicontrol">Scope</span> of the list by selecting one of the -following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</li> - -<li class="stepexpand"><span>If you selected <span class="uicontrol">list</span> from the <span class="uicontrol">Variety</span> list, -click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Item type</span> field -to specify a item type for the simple type.</span> The Set Type dialog -box lists all built-in and user-defined types currently available. You can -change the <span class="uicontrol">Scope</span> of the list by selecting one of the -following options:<ul> -<li><span class="uicontrol">Workspace</span>. Lists all of the types available in -your workspace. </li> - -<li><span class="uicontrol">Enclosing Project</span>. Lists all of the types available -in the project that contains your file. </li> - -<li>(Default) <span class="uicontrol">Current Resource</span>. List all of the types -available in your current file.</li> - -<li><span class="uicontrol">Working Sets</span>. List all the types available within -the selected working set.</li> - -</ul> -</li> - -<li class="stepexpand"><span>If you selected <span class="uicontrol">union</span> from the <span class="uicontrol">Variety</span> list, -click <span class="uicontrol">Browse</span> <img src="../images/Browse.gif" alt="This graphic is the Browse button" /> next to the <span class="uicontrol">Member types</span> field -to specify the member types for the simple type.</span> You can select -to add both <span class="uicontrol">Built-in simple types</span> and <span class="uicontrol">User-defined -simple types</span> to the member types value list. </li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Constraints</span> tab.</span> From -here you will be able to set specific constraint values including length constraints, -enumerations, and patterns. -<ol type="a"> -<li class="substepexpand"><span>Enumerations help you to define a set of valid values for simple -types. They are the actual values the simple type can take as valid values -in the instance document. You can either add one enumeration or several enumerations -at a time:</span> <ul> -<li>To add one enumeration at a time, under <span class="uicontrol">Specific constraint -values</span>, select <span class="uicontrol">Enumerations</span> and click <span class="uicontrol">Add</span> and -specify a value for the enumeration.</li> - -<li>To add several enumerations at one time, follow these steps:<ol type="i"> -<li>Select <span class="uicontrol">Enumerations</span>.</li> - -<li>Click <span class="uicontrol">Add</span>.</li> - -<li>Enter the value of each enumeration. Each value must be separated by the <span class="uicontrol">Delimiter -character</span>. For example: <samp class="codeph">First, Second</samp> will create -two enumerations, one with the value "First" and one with the value "Second".</li> - -<li>Select the <span class="uicontrol">Preserve leading and trailing whitespace</span> check -box if you want any white space around your enumeration values to be preserved. -If you select this check box, the values of <samp class="codeph">First, Second</samp> will -show up as "First" and " Second" (there is a space before Second) because -you put a space before "Second" when entering the value.</li> - -<li>Click <span class="uicontrol">OK</span>. Your enumerations will be created and -appear in the Properties view.</li> - -</ol> -</li> - -</ul> -</li> - -<li class="substepexpand"><span>Patterns help you to place certain constraints regarding allowable -values.</span> For example, you could restrict the field to only accept -input which follows the pattern "five digits followed by two upper-case ASCII -letters". To set a pattern constraint:<ol type="i"> -<li>Select <span class="uicontrol">Patterns</span>.</li> - -<li>Click <span class="uicontrol">Add</span>.</li> - -<li>Create the regular expression pattern you wish to use as your constraint -using the <span class="uicontrol">Regular Expression</span> wizard.</li> - -<li>Click <span class="uicontrol">Finish</span>.</li> - -</ol> -</li> - -</ol> - -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this simple type.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/taddreg.html" title="A pattern facet can be used to constrain the value of a type's lexical space (the set of string literals that represent the values of a type), which indirectly constrains the value space.">Adding pattern facets to simple types</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.dita deleted file mode 100644 index bde45d16a4..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.dita +++ /dev/null @@ -1,31 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tcxmlsch" xml:lang="en-us">
-<title>Creating XML schemas</title>
-<titlealts>
-<searchtitle>Creating XML schemas</searchtitle>
-</titlealts>
-<shortdesc>You can create an XML schema and then edit it using the XML schema
-editor. Using the XML schema editor, you can specify element names that indicates
-which elements are allowed in an XML file, and in which combinations.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>creating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context>To create an XML schema, follow these steps:</context>
-<steps>
-<step><cmd>Create a project to contain the XML schema.</cmd></step>
-<step><cmd>In the workbench, select <menucascade><uicontrol>File > New >
-Other > XML > XML Schema</uicontrol></menucascade> and click <uicontrol>Next</uicontrol>.</cmd>
-</step>
-<step><cmd>Select the project or folder that will contain the XML schema.
-In the </cmd><info><uicontrol>File name</uicontrol> field, type the name of
-the XML schema, for example <userinput>MyXMLSchema.xsd</userinput>. The name
-of your XML schema must end in <systemoutput>.xsd</systemoutput>.</info></step>
-<step><cmd>Click <uicontrol>Finish</uicontrol>.</cmd></step>
-</steps>
-<result>The XML schema opens in the XML schema editor. </result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html deleted file mode 100644 index 9aec93283d..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tcxmlsch.html +++ /dev/null @@ -1,69 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Creating XML schemas" /> -<meta name="abstract" content="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations." /> -<meta name="description" content="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations." /> -<meta content="XML schema files, creating" name="DC.subject" /> -<meta content="XML schema files, creating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tcxmlsch" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Creating XML schemas</title> -</head> -<body id="tcxmlsch"><a name="tcxmlsch"><!-- --></a> - - -<h1 class="topictitle1">Creating XML schemas</h1> - - - - -<div><p>You can create an XML schema and then edit it using the XML schema -editor. Using the XML schema editor, you can specify element names that indicates -which elements are allowed in an XML file, and in which combinations.</p> - -<div class="section">To create an XML schema, follow these steps:</div> - -<ol> -<li class="stepexpand"><span>Create a project to contain the XML schema.</span></li> - -<li class="stepexpand"><span>In the workbench, select <span class="menucascade"><span class="uicontrol">File > New > -Other > XML > XML Schema</span></span> and click <span class="uicontrol">Next</span>.</span> -</li> - -<li class="stepexpand"><span>Select the project or folder that will contain the XML schema. -In the </span> <span class="uicontrol">File name</span> field, type the name of -the XML schema, for example <kbd class="userinput">MyXMLSchema.xsd</kbd>. The name -of your XML schema must end in <tt class="sysout">.xsd</tt>.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">Finish</span>.</span></li> - -</ol> - -<div class="section">The XML schema opens in the XML schema editor. </div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div> -<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.dita deleted file mode 100644 index 8c1475c212..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.dita +++ /dev/null @@ -1,30 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tdelscmp" xml:lang="en-us">
-<title>Deleting XML schema components</title>
-<titlealts>
-<searchtitle>Deleting XML schema components</searchtitle>
-</titlealts>
-<shortdesc>If you have created any XML schema components you no longer need,
-you can delete them.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>deleting components</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>deleting components</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To delete an XML
-schema component, follow these steps:</p></context>
-<steps>
-<step><cmd>Open your XML schema in the XML schema editor.</cmd></step>
-<step><cmd>In the Outline view, click the item to delete.</cmd></step>
-<step><cmd>Right-click the item, and, from its pop-up menu, click <uicontrol>Delete</uicontrol>.</cmd>
-</step>
-</steps>
-<result><p>The XML schema editor has a built-in mechanism to handle referential
-integrity issues. When you delete certain components, cleanup will automatically
-occur.</p></result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html deleted file mode 100644 index a4cc20057b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tdelscmp.html +++ /dev/null @@ -1,63 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Deleting XML schema components" /> -<meta name="abstract" content="If you have created any XML schema components you no longer need, you can delete them." /> -<meta name="description" content="If you have created any XML schema components you no longer need, you can delete them." /> -<meta content="XML schema editor, deleting, components, XML schema files" name="DC.subject" /> -<meta content="XML schema editor, deleting, components, XML schema files" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/rrefintg.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tdelscmp" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Deleting XML schema components</title> -</head> -<body id="tdelscmp"><a name="tdelscmp"><!-- --></a> - - -<h1 class="topictitle1">Deleting XML schema components</h1> - - - - -<div><p>If you have created any XML schema components you no longer need, -you can delete them.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To delete an XML -schema component, follow these steps:</p> -</div> - -<ol> -<li><span>Open your XML schema in the XML schema editor.</span></li> - -<li><span>In the Outline view, click the item to delete.</span></li> - -<li><span>Right-click the item, and, from its pop-up menu, click <span class="uicontrol">Delete</span>.</span> -</li> - -</ol> - -<div class="section"><p>The XML schema editor has a built-in mechanism to handle referential -integrity issues. When you delete certain components, cleanup will automatically -occur.</p> -</div> - -</div> - -<div><div class="relref"><strong>Related reference</strong><br /> -<div><a href="../topics/rrefintg.html" title="The XML schema editor has a built-in mechanism to handle referential integrity issues. When you delete certain nodes, clean up for any nodes affected will automatically occur.">Referential integrity in the XML schema editor</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.dita deleted file mode 100644 index 62762428c3..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.dita +++ /dev/null @@ -1,42 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tedtpref" xml:lang="en-us">
-<title>Editing XML schema file preferences</title>
-<titlealts>
-<searchtitle>Editing XML schema file preferences</searchtitle>
-</titlealts>
-<shortdesc>You can set various preferences for XML schema files such as the
-default target namespace and XML Schema language constructs prefix used.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>editing preferences</indexterm></indexterm>
-<indexterm>preferences<indexterm>XML schema files</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>To define XML schema file preferences, follow these steps:</p></context>
-<steps>
-<step><cmd>Select <menucascade><uicontrol>Window > Preferences > Web and
-XML > XML Schema Files</uicontrol></menucascade>.</cmd></step>
-<step><cmd>Select the <uicontrol>Qualify XML schema language constructs</uicontrol> check
-box if you want a prefix applied to all XML Schema language constructs in
-your XML schema.</cmd></step>
-<step><cmd>In the <uicontrol>XML schema language constructs prefix</uicontrol> field,
-type the prefix you want applied to XML Schema language constructs in your
-XML schema.</cmd><info> The prefix <uicontrol>xsd</uicontrol> is used by convention
-to denote the XML Schema namespace, but any prefix can be used. The purpose
-of the association is to identify the elements and simple types as belonging
-to the vocabulary of the XML Schema language rather than the vocabulary of
-the schema author. <note>This prefix will not appear in any schemas that
-currently exist - it will only appear in new schemas you create after you
-type the prefix and click <uicontrol>Apply</uicontrol>. Any schemas that already
-exist will have the prefix specified in the schema applied to the XML schema
-language constructs.</note></info></step>
-<step><cmd>You can change the <uicontrol>Default Target Namespace</uicontrol> value.</cmd>
-<info>The value specified in this field will be the default target namespace
-for any new XML schema files created.</info></step>
-<step><cmd>Click <uicontrol>OK</uicontrol>.</cmd></step>
-</steps>
-<result></result>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html deleted file mode 100644 index fe76430875..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtpref.html +++ /dev/null @@ -1,71 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML schema file preferences" /> -<meta name="abstract" content="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used." /> -<meta name="description" content="You can set various preferences for XML schema files such as the default target namespace and XML Schema language constructs prefix used." /> -<meta content="XML schema files, defining, default target namespace, XML schema files, schema prefix" name="DC.subject" /> -<meta content="XML schema files, defining, default target namespace, XML schema files, schema prefix" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtpref" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML schema file preferences</title> -</head> -<body id="tedtpref"><a name="tedtpref"><!-- --></a> - - -<h1 class="topictitle1">Editing XML schema file preferences</h1> - - - - -<div><p>You can set various preferences for XML schema files such as the -default target namespace and XML Schema language constructs prefix used.</p> - -<div class="section"><p>To define XML schema file preferences, follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Select <span class="menucascade"><span class="uicontrol">Window > Preferences > Web and -XML > XML Schema Files</span></span>.</span></li> - -<li class="stepexpand"><span>Select the <span class="uicontrol">Qualify XML schema language constructs</span> check -box if you want a prefix applied to all XML Schema language constructs in -your XML schema.</span></li> - -<li class="stepexpand"><span>In the <span class="uicontrol">XML schema language constructs prefix</span> field, -type the prefix you want applied to XML Schema language constructs in your -XML schema.</span> The prefix <span class="uicontrol">xsd</span> is used by convention -to denote the XML Schema namespace, but any prefix can be used. The purpose -of the association is to identify the elements and simple types as belonging -to the vocabulary of the XML Schema language rather than the vocabulary of -the schema author. <div class="note"><span class="notetitle">Note:</span> This prefix will not appear in any schemas that -currently exist - it will only appear in new schemas you create after you -type the prefix and click <span class="uicontrol">Apply</span>. Any schemas that already -exist will have the prefix specified in the schema applied to the XML schema -language constructs.</div> -</li> - -<li class="stepexpand"><span>You can change the <span class="uicontrol">Default Target Namespace</span> value.</span> - The value specified in this field will be the default target namespace -for any new XML schema files created.</li> - -<li class="stepexpand"><span>Click <span class="uicontrol">OK</span>.</span></li> - -</ol> - -<div class="section" /> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.dita deleted file mode 100644 index 666ecb8e22..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.dita +++ /dev/null @@ -1,47 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<?Pub Inc?>
-<task id="tedtschm" xml:lang="en-us">
-<title>Editing XML schema properties</title>
-<titlealts>
-<searchtitle>Editing XML schema properties</searchtitle>
-</titlealts>
-<shortdesc>After you create an XML schema, you can edit its various properties,
-such as its namespace and prefix.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema editor<indexterm>XML schema properties</indexterm></indexterm>
-<indexterm>XML schema files<indexterm>editing properties</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To edit an XML schema's
-properties follow these steps:</p></context>
-<steps>
-<step><cmd>Create a new XML schema or double-click an existing schema in the
-Navigator view.</cmd><info> It will automatically open in the XML schema editor.</info>
-</step>
-<step><cmd>In the Outline view, click <uicontrol>Directives</uicontrol>.</cmd>
-</step>
-<step><cmd>In the Properties view, click the <uicontrol>General</uicontrol> tab.</cmd>
-</step>
-<step><cmd>You can change the <uicontrol>Prefix</uicontrol> associated with
-the current namespace.</cmd><info>Element and attribute names that are associated
-with this namespace will be prefixed with this value.</info></step>
-<step><cmd>You can also edit the <uicontrol>Target namespace</uicontrol> for
-this schema.</cmd><info> A namespace is a URI that provides a unique name
-to associate with all the elements and type definitions in a schema.</info>
-</step>
-<step><cmd>Click the <uicontrol>Documentation</uicontrol> tab if you want
-to provide any information about this XML schema.</cmd><info>The <uicontrol>Documentation</uicontrol> page
-is used for human readable material, such as a description.</info></step>
-<step><cmd>Click the <uicontrol>Extensions</uicontrol> tab if you want to
-add application information elements to your annotations of schema components.</cmd>
-<info>The <uicontrol>Extensions</uicontrol> page allows you to specify the
-schema and add XML content to your annotations.</info></step>
-</steps>
-</taskbody>
-</task>
-<?Pub *0000002389?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html deleted file mode 100644 index 840ef3a847..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tedtschm.html +++ /dev/null @@ -1,74 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Editing XML schema properties" /> -<meta name="abstract" content="After you create an XML schema, you can edit its various properties, such as its namespace and prefix." /> -<meta name="description" content="After you create an XML schema, you can edit its various properties, such as its namespace and prefix." /> -<meta content="XML schema editor, editing XML schemas, simple types, XML schema files, editing" name="DC.subject" /> -<meta content="XML schema editor, editing XML schemas, simple types, XML schema files, editing" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tedtschm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Editing XML schema properties</title> -</head> -<body id="tedtschm"><a name="tedtschm"><!-- --></a> - - -<h1 class="topictitle1">Editing XML schema properties</h1> - - - - -<div><p>After you create an XML schema, you can edit its various properties, -such as its namespace and prefix.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To edit an XML schema's -properties follow these steps:</p> -</div> - -<ol> -<li class="stepexpand"><span>Create a new XML schema or double-click an existing schema in the -Navigator view.</span> It will automatically open in the XML schema editor. -</li> - -<li class="stepexpand"><span>In the Outline view, click <span class="uicontrol">Directives</span>.</span> -</li> - -<li class="stepexpand"><span>In the Properties view, click the <span class="uicontrol">General</span> tab.</span> -</li> - -<li class="stepexpand"><span>You can change the <span class="uicontrol">Prefix</span> associated with -the current namespace.</span> Element and attribute names that are associated -with this namespace will be prefixed with this value.</li> - -<li class="stepexpand"><span>You can also edit the <span class="uicontrol">Target namespace</span> for -this schema.</span> A namespace is a URI that provides a unique name -to associate with all the elements and type definitions in a schema. -</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Documentation</span> tab if you want -to provide any information about this XML schema.</span> The <span class="uicontrol">Documentation</span> page -is used for human readable material, such as a description.</li> - -<li class="stepexpand"><span>Click the <span class="uicontrol">Extensions</span> tab if you want to -add application information elements to your annotations of schema components.</span> - The <span class="uicontrol">Extensions</span> page allows you to specify the -schema and add XML content to your annotations.</li> - -</ol> - -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.dita deleted file mode 100644 index bc1b82a874..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="timpschm" xml:lang="en-us">
-<title>Importing XML schemas</title>
-<titlealts>
-<searchtitle>Importing XML schemas</searchtitle>
-</titlealts>
-<shortdesc>If you want to work with XML schema files that you created outside
-of the product, you can import them into the workbench and open them in the
-XML schema editor. The XML schema editor provides you with a structured view
-of the XML schema.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>importing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To import an XML
-schema into the workbench:</p></context>
-<steps>
-<step><cmd>Click <menucascade><uicontrol>File > Import</uicontrol></menucascade>.</cmd>
-</step>
-<step><cmd>Select the import source.</cmd><info> Click <uicontrol>Next</uicontrol>.</info>
-</step>
-<step><cmd>Fill in the fields in the Import wizard as necessary.</cmd><info> When
-you are finished, click <uicontrol>Finish</uicontrol>.</info></step>
-</steps>
-<result><p>The imported schema now appears in the Navigator view. Double-click
-it to open it in the XML schema editor.</p></result>
-</taskbody>
-</task>
-<?Pub *0000001448?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html deleted file mode 100644 index 8726a2ce3b..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/timpschm.html +++ /dev/null @@ -1,76 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Importing XML schemas" /> -<meta name="abstract" content="If you want to work with XML schema files that you created outside of the product, you can import them into the workbench and open them in the XML schema editor. The XML schema editor provides you with a structured view of the XML schema." /> -<meta name="description" content="If you want to work with XML schema files that you created outside of the product, you can import them into the workbench and open them in the XML schema editor. The XML schema editor provides you with a structured view of the XML schema." /> -<meta content="XML schema files, importing" name="DC.subject" /> -<meta content="XML schema files, importing" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tedtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tvdtschm.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddimpt.html" /> -<meta scheme="URI" name="DC.Relation" content="../topics/taddincl.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="timpschm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Importing XML schemas</title> -</head> -<body id="timpschm"><a name="timpschm"><!-- --></a> - - -<h1 class="topictitle1">Importing XML schemas</h1> - - - - -<div><p>If you want to work with XML schema files that you created outside -of the product, you can import them into the workbench and open them in the -XML schema editor. The XML schema editor provides you with a structured view -of the XML schema.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To import an XML -schema into the workbench:</p> -</div> - -<ol> -<li class="stepexpand"><span>Click <span class="menucascade"><span class="uicontrol">File > Import</span></span>.</span> -</li> - -<li class="stepexpand"><span>Select the import source.</span> Click <span class="uicontrol">Next</span>. -</li> - -<li class="stepexpand"><span>Fill in the fields in the Import wizard as necessary.</span> When -you are finished, click <span class="uicontrol">Finish</span>.</li> - -</ol> - -<div class="section"><p>The imported schema now appears in the Navigator view. Double-click -it to open it in the XML schema editor.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div> -</div> -<div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tedtschm.html" title="After you create an XML schema, you can edit its various properties, such as its namespace and prefix.">Editing XML schema properties</a></div> -<div><a href="../topics/tvdtschm.html" title="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view.">Validating XML schemas</a></div> -<div><a href="../topics/taddimpt.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use an import element to bring in definitions and declarations from an imported schema into the current schema.">Adding import elements</a></div> -<div><a href="../topics/taddincl.html" title="As schemas become larger, it is often desirable to divide their content among several schema documents for purposes such as ease of maintenance, reuse, and readability. You can use the include element to bring in definitions and declarations from the included schema into the current schema. The included schema must be in the same target namespace as the including schema.">Adding include elements</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.dita deleted file mode 100644 index c4f2a0ffd1..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.dita +++ /dev/null @@ -1,38 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
-<task id="tnavsrc" xml:lang="en-us">
-<title>Navigating XML schemas</title>
-<titlealts>
-<searchtitle>Navigating XML schemas</searchtitle>
-</titlealts>
-<shortdesc>When you are working in the Source view, you can use F3 to navigate
-through the file by placing your cursor in the appropriate item and clicking
-F3 to jump to the item it refers to. </shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>navigating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>You can jump to any of the following items:</p><ul>
-<li>Element or attribute declaration's type</li>
-<li>Element references</li>
-<li>Group references</li>
-<li>Attribute references</li>
-<li>Attribute group references</li>
-<li>Import, include, and redefine element (the external schema will open in
-the XML schema editor. This only works with schemas in the workspace).</li>
-</ul><p>You must place your cursor exactly in the location of the reference
-(for example between the double quotes for <systemoutput>type = " "</systemoutput> or
- <systemoutput>base = " "</systemoutput>).</p><p>For example, if you place
-your cursor anywhere in the following text and click F3:</p><p> <systemoutput><element
-name="shipTo" type="po:USAddress"></element></systemoutput> </p><p>the
-cursor will automatically jump to the location in the file where the type
-USAddress is defined.</p><p>Or, if you place your cursor anywhere in the following
-text and click F3:</p><p> <systemoutput><element ref="po:ContactElement"></element></systemoutput> </p><p>the
-cursor will automatically jump to the location in the file where the global
-element ContactElement is defined.</p><p>This works across files. For example,
-if the type you have selected is defined in another XML schema and you click
-F3, you will automatically be taken to that file.</p></context>
-</taskbody>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html deleted file mode 100644 index 582def5858..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tnavsrc.html +++ /dev/null @@ -1,80 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Navigating XML schemas" /> -<meta name="abstract" content="When you are working in the Source view, you can use F3 to navigate through the file by placing your cursor in the appropriate item and clicking F3 to jump to the item it refers to." /> -<meta name="description" content="When you are working in the Source view, you can use F3 to navigate through the file by placing your cursor in the appropriate item and clicking F3 to jump to the item it refers to." /> -<meta content="XML schema files, navigating" name="DC.subject" /> -<meta content="XML schema files, navigating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/cxmlsced.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tnavsrc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Navigating XML schemas</title> -</head> -<body id="tnavsrc"><a name="tnavsrc"><!-- --></a> - - -<h1 class="topictitle1">Navigating XML schemas</h1> - - - - -<div><p>When you are working in the Source view, you can use F3 to navigate -through the file by placing your cursor in the appropriate item and clicking -F3 to jump to the item it refers to. </p> - -<div class="section"><p>You can jump to any of the following items:</p> -<ul> -<li>Element or attribute declaration's type</li> - -<li>Element references</li> - -<li>Group references</li> - -<li>Attribute references</li> - -<li>Attribute group references</li> - -<li>Import, include, and redefine element (the external schema will open in -the XML schema editor. This only works with schemas in the workspace).</li> - -</ul> -<p>You must place your cursor exactly in the location of the reference -(for example between the double quotes for <tt class="sysout">type = " "</tt> or - <tt class="sysout">base = " "</tt>).</p> -<p>For example, if you place -your cursor anywhere in the following text and click F3:</p> -<p> <tt class="sysout"><element -name="shipTo" type="po:USAddress"></element></tt> </p> -<p>the -cursor will automatically jump to the location in the file where the type -USAddress is defined.</p> -<p>Or, if you place your cursor anywhere in the following -text and click F3:</p> -<p> <tt class="sysout"><element ref="po:ContactElement"></element></tt> </p> -<p>the -cursor will automatically jump to the location in the file where the global -element ContactElement is defined.</p> -<p>This works across files. For example, -if the type you have selected is defined in another XML schema and you click -F3, you will automatically be taken to that file.</p> -</div> - -</div> - -<div><div class="relconcepts"><strong>Related concepts</strong><br /> -<div><a href="../topics/cxmlsced.html" title="This product provides an XML schema editor for creating, viewing, and validating XML schemas. XML schemas are a formal specification of element names that indicates which elements are allowed in an XML file, and in which combinations.">XML schema editor</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.dita deleted file mode 100644 index eea3411bff..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.dita +++ /dev/null @@ -1,97 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2005, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="refactoring" xml:lang="en-us">
-<title>Refactoring in XML Schema Files</title>
-<titlealts>
-<searchtitle>Refactoring in XML Schema Files</searchtitle>
-</titlealts>
-<shortdesc>Within an XML Schema file, refactoring allows authors to make a
-single artifact change, and have that change implemented throughout all other
-dependant artifacts.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>dependent artifacts<indexterm>refactorting XML schema files</indexterm></indexterm>
-<indexterm>refactoring<indexterm>XML schema files</indexterm></indexterm>
-<indexterm>renaming<indexterm>XML schema files</indexterm></indexterm>
-<indexterm>XML schemas<indexterm>editing</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<prereq></prereq>
-<context>Refactoring eliminates the need for the tedious editing necessary
-to recover broken dependencies caused by artifact changes which cause ripple
-effects on other dependant artifacts (such as renaming an XML Schema element).</context>
-<steps>
-<step><cmd>Create a new XML schema or double-click an existing schema in the
-Navigator view.</cmd><info> It will automatically open in the XML schema editor.</info>
-</step>
-<step><cmd>To refactor an artifact, position cursor within the artifact, right-click
-the artifact, click <menucascade><uicontrol>Refactor</uicontrol><uicontrol>Rename</uicontrol>
-</menucascade></cmd><info>A popup dialog will request the entry of a new name
-for that artifact</info>
-<substeps>
-<substep><cmd>Type in the new name of the artifact.</cmd></substep>
-<substep><cmd>(Optional) Click <b>Preview</b>.</cmd><info>A window
-will open indicating all of the changes which will take place due to the refactoring.</info>
-</substep>
-<substep><cmd>Click <uicontrol>OK.</uicontrol></cmd></substep>
-</substeps>
-</step>
-</steps>
-<result>The new name will be entered in the opened XSD source, as well as
-in all dependant artifacts</result>
-<example><b><u>Component References in XML Schema</u></b><simpletable>
-<sthead>
-<stentry>Global named components</stentry>
-<stentry>Reference</stentry>
-</sthead>
-<strow>
-<stentry><ul>
-<li><element name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><element ref="foo"></li>
-<li><element substitutionGroup="foo"</li>
-</ul></stentry>
-</strow>
-<strow>
-<stentry><ul>
-<li><simple/complexType name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><element type="foo"></li>
-<li><attribute type="foo"></li>
-<li><restriction base="foo"></li>
-<li><substitution base="foo"></li>
-</ul></stentry>
-</strow>
-<strow>
-<stentry><ul>
-<li><attribute name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><attribute ref="foo"></li>
-</ul></stentry>
-</strow>
-<strow>
-<stentry><ul>
-<li><attributeGroup name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><attributeGroup ref="foo"></li>
-</ul></stentry>
-</strow>
-<strow>
-<stentry><ul>
-<li><group name="foo"></li>
-</ul></stentry>
-<stentry><ul>
-<li><group ref="foo"></li>
-</ul></stentry>
-</strow>
-</simpletable></example>
-<postreq></postreq>
-</taskbody>
-</task>
-<?Pub *0000003131?>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html deleted file mode 100644 index ceb881d068..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/trefactrXSD.html +++ /dev/null @@ -1,168 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Refactoring in XML Schema Files" /> -<meta name="abstract" content="Within an XML Schema file, refactoring allows authors to make a single artifact change, and have that change implemented throughout all other dependant artifacts." /> -<meta name="description" content="Within an XML Schema file, refactoring allows authors to make a single artifact change, and have that change implemented throughout all other dependant artifacts." /> -<meta content="XML schema files, XML schema editor, refactoring, renaming, editing XML schemas, dependant artifacts" name="DC.subject" /> -<meta content="XML schema files, XML schema editor, refactoring, renaming, editing XML schemas, dependant artifacts" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="refactoring" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Refactoring in XML Schema Files</title> -</head> -<body id="refactoring"><a name="refactoring"><!-- --></a> - - -<h1 class="topictitle1">Refactoring in XML Schema Files</h1> - - - - -<div><p>Within an XML Schema file, refactoring allows authors to make a -single artifact change, and have that change implemented throughout all other -dependant artifacts.</p> - -<div class="p" /> - -<div class="section">Refactoring eliminates the need for the tedious editing necessary -to recover broken dependencies caused by artifact changes which cause ripple -effects on other dependant artifacts (such as renaming an XML Schema element).</div> - -<ol> -<li class="stepexpand"><span>Create a new XML schema or double-click an existing schema in the -Navigator view.</span> It will automatically open in the XML schema editor. -</li> - -<li class="stepexpand"><span>To refactor an artifact, position cursor within the artifact, right-click -the artifact, click <span class="menucascade"><span class="uicontrol">Refactor</span> > <span class="uicontrol">Rename</span> -</span></span> A popup dialog will request the entry of a new name -for that artifact -<ol type="a"> -<li class="substepexpand"><span>Type in the new name of the artifact.</span></li> - -<li class="substepexpand"><span>(Optional) Click <strong>Preview</strong>.</span> A window -will open indicating all of the changes which will take place due to the refactoring. -</li> - -<li class="substepexpand"><span>Click <span class="uicontrol">OK.</span></span></li> - -</ol> - -</li> - -</ol> - -<div class="section">The new name will be entered in the opened XSD source, as well as -in all dependant artifacts</div> - -<div class="example"><strong><u>Component References in XML Schema</u></strong><table summary="" cellspacing="0" cellpadding="4" border="1" class="simpletableborder"> -<tr> -<th valign="bottom" align="left" id="N100EB">Global named components</th> - -<th valign="bottom" align="left" id="N100F1">Reference</th> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><element name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><element ref="foo"></li> - -<li><element substitutionGroup="foo"</li> - -</ul> -</td> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><simple/complexType name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><element type="foo"></li> - -<li><attribute type="foo"></li> - -<li><restriction base="foo"></li> - -<li><substitution base="foo"></li> - -</ul> -</td> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><attribute name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><attribute ref="foo"></li> - -</ul> -</td> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><attributeGroup name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><attributeGroup ref="foo"></li> - -</ul> -</td> - -</tr> - -<tr> -<td valign="top" headers="N100EB"><ul> -<li><group name="foo"></li> - -</ul> -</td> - -<td valign="top" headers="N100F1"><ul> -<li><group ref="foo"></li> - -</ul> -</td> - -</tr> - -</table> -</div> - -<div class="section" /> - -</div> - -<div /> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.dita b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.dita deleted file mode 100644 index 580f90c3d9..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.dita +++ /dev/null @@ -1,59 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?>
-<!--Arbortext, Inc., 1988-2006, v.4002-->
-<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN"
- "task.dtd">
-<task id="tvdtschm" xml:lang="en-us">
-<title>Validating XML schemas</title>
-<titlealts>
-<searchtitle>Validating XML schemas</searchtitle>
-</titlealts>
-<shortdesc>Validating an XML schema determines whether the current state of
-the XML schema file is semantically valid. Any errors will be displayed in
-the Problems view.</shortdesc>
-<prolog><metadata>
-<keywords><indexterm>XML schema files<indexterm>validating</indexterm></indexterm>
-</keywords>
-</metadata></prolog>
-<taskbody>
-<context><p>The following instructions were written for the Resource perspective,
-but they will also work in many other perspectives.</p><p>To validate an XML
-schema:</p></context>
-<steps>
-<step><cmd>Right-click your file in the Navigator view and click <uicontrol>Validate</uicontrol>.</cmd>
-</step>
-<step><cmd> If validation was not successful, you can refer to the Problems
-view to see what problems were logged. </cmd><info> <note>If you receive an
-error message indicating that the Problems view is full, you can increase
-the number of error messages allowed by selecting <menucascade><uicontrol>Properties
-> Validation</uicontrol></menucascade> and specifying the maximum number of
-error messages allowed.</note></info></step>
-</steps>
-<result><p>The XML schema support in the XML schema editor is based on the
-W3C XML Schema Recommendation Specification. The XML Schema specifications
-XML Schema Part 1: Structures and XML Schema Part 2: Datatypes from the W3C
-Web site are used for validation.</p><p>Certain error messages contain a reference
-to the schema constraints listed in Appendix C of the XML Schema Part 1: Structures
-document. Each constraint has a unique name that will be referenced in the
-error message. For example, if you receive an error message with this text:
- <systemoutput>ct-props-correct</systemoutput> and you searched in the Structure
-document for the text, you would find that it is for the section "Schema Component
-Constraint: Complex Type Definition Properties Correct". </p><p>You can set
-up a project's properties so that different types of project resources are
-automatically validated when you save them. From a project's pop-up menu select <uicontrol>Properties</uicontrol>,
-then select <uicontrol>Validation</uicontrol>. Any validators you can run
-against your project will be listed in the Validation page.</p></result>
-</taskbody>
-<related-links>
-<link href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.dita" scope="peer">
-<desc>General validation information</desc>
-</link>
-<link href="http://www.w3.org/TR/xmlschema-1" scope="external"><linktext>XML
-Schema Part 1: Structures</linktext>
-<desc>See the W3C Web site for more information on XML Schema specifications</desc>
-</link>
-<link href="http://www.w3.org/TR/xmlschema-2" scope="external"><linktext>XML
-Schema Part 2: Datatypes</linktext>
-<desc>See the W3C Web site for more information on XML Schema specifications</desc>
-</link>
-</related-links>
-</task>
diff --git a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html b/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html deleted file mode 100644 index f6ef002297..0000000000 --- a/docs/org.eclipse.wst.xsdeditor.doc.user/topics/tvdtschm.html +++ /dev/null @@ -1,91 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="task" name="DC.Type" /> -<meta name="DC.Title" content="Validating XML schemas" /> -<meta name="abstract" content="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view." /> -<meta name="description" content="Validating an XML schema determines whether the current state of the XML schema file is semantically valid. Any errors will be displayed in the Problems view." /> -<meta content="XML schema files, validating" name="DC.subject" /> -<meta content="XML schema files, validating" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../topics/tcxmlsch.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" /> -<meta scheme="URI" name="DC.Relation" content="http://www.w3.org/TR/xmlschema-1" /> -<meta scheme="URI" name="DC.Relation" content="http://www.w3.org/TR/xmlschema-2" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="tvdtschm" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Validating XML schemas</title> -</head> -<body id="tvdtschm"><a name="tvdtschm"><!-- --></a> - - -<h1 class="topictitle1">Validating XML schemas</h1> - - - - -<div><p>Validating an XML schema determines whether the current state of -the XML schema file is semantically valid. Any errors will be displayed in -the Problems view.</p> - -<div class="section"><p>The following instructions were written for the Resource perspective, -but they will also work in many other perspectives.</p> -<p>To validate an XML -schema:</p> -</div> - -<ol> -<li class="stepexpand"><span>Right-click your file in the Navigator view and click <span class="uicontrol">Validate</span>.</span> -</li> - -<li class="stepexpand"><span> If validation was not successful, you can refer to the Problems -view to see what problems were logged. </span> <div class="note"><span class="notetitle">Note:</span> If you receive an -error message indicating that the Problems view is full, you can increase -the number of error messages allowed by selecting <span class="menucascade"><span class="uicontrol">Properties -> Validation</span></span> and specifying the maximum number of -error messages allowed.</div> -</li> - -</ol> - -<div class="section"><p>The XML schema support in the XML schema editor is based on the -W3C XML Schema Recommendation Specification. The XML Schema specifications -XML Schema Part 1: Structures and XML Schema Part 2: Datatypes from the W3C -Web site are used for validation.</p> -<p>Certain error messages contain a reference -to the schema constraints listed in Appendix C of the XML Schema Part 1: Structures -document. Each constraint has a unique name that will be referenced in the -error message. For example, if you receive an error message with this text: - <tt class="sysout">ct-props-correct</tt> and you searched in the Structure -document for the text, you would find that it is for the section "Schema Component -Constraint: Complex Type Definition Properties Correct". </p> -<p>You can set -up a project's properties so that different types of project resources are -automatically validated when you save them. From a project's pop-up menu select <span class="uicontrol">Properties</span>, -then select <span class="uicontrol">Validation</span>. Any validators you can run -against your project will be listed in the Validation page.</p> -</div> - -</div> - -<div><div class="reltasks"><strong>Related tasks</strong><br /> -<div><a href="../topics/tcxmlsch.html" title="You can create an XML schema and then edit it using the XML schema editor. Using the XML schema editor, you can specify element names that indicates which elements are allowed in an XML file, and in which combinations.">Creating XML schemas</a></div> -</div> -<div class="relinfo"><strong>Related information</strong><br /> -<div><a href="../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html" title="General validation information">../../org.eclipse.jst.j2ee.doc.user/topics/tjval.html</a></div> -<div><a href="http://www.w3.org/TR/xmlschema-1" target="_blank" title="See the W3C Web site for more information on XML Schema specifications">XML -Schema Part 1: Structures</a></div> -<div><a href="http://www.w3.org/TR/xmlschema-2" target="_blank" title="See the W3C Web site for more information on XML Schema specifications">XML -Schema Part 2: Datatypes</a></div> -</div> -</div> - -</body> -</html>
\ No newline at end of file |
