diff options
Diffstat (limited to 'tde-i18n-fr/docs/tdewebdev/quanta')
17 files changed, 7586 insertions, 0 deletions
diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/Makefile.am b/tde-i18n-fr/docs/tdewebdev/quanta/Makefile.am new file mode 100644 index 00000000000..b6361414814 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/Makefile.am @@ -0,0 +1,4 @@ +KDE_LANG = fr +SUBDIRS = $(AUTODIRS) +KDE_DOCS = AUTO +KDE_MANS = AUTO diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/Makefile.in b/tde-i18n-fr/docs/tdewebdev/quanta/Makefile.in new file mode 100644 index 00000000000..25cddc8a8fd --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/Makefile.in @@ -0,0 +1,635 @@ +# Makefile.in generated by automake 1.10.1 from Makefile.am. +# KDE tags expanded automatically by am_edit - $Revision: 483858 $ +# @configure_input@ + +# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, +# 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc. +# This Makefile.in is free software; the Free Software Foundation +# gives unlimited permission to copy and/or distribute it, +# with or without modifications, as long as this notice is preserved. + +# This program is distributed in the hope that it will be useful, +# but WITHOUT ANY WARRANTY, to the extent permitted by law; without +# even the implied warranty of MERCHANTABILITY or FITNESS FOR A +# PARTICULAR PURPOSE. + +@SET_MAKE@ +VPATH = @srcdir@ +pkgdatadir = $(datadir)/@PACKAGE@ +pkglibdir = $(libdir)/@PACKAGE@ +pkgincludedir = $(includedir)/@PACKAGE@ +am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd +install_sh_DATA = $(install_sh) -c -m 644 +install_sh_PROGRAM = $(install_sh) -c +install_sh_SCRIPT = $(install_sh) -c +INSTALL_HEADER = $(INSTALL_DATA) +transform = $(program_transform_name) +NORMAL_INSTALL = : +PRE_INSTALL = : +POST_INSTALL = : +NORMAL_UNINSTALL = : +PRE_UNINSTALL = : +POST_UNINSTALL = : +subdir = docs/tdewebdev/quanta +DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in +ACLOCAL_M4 = $(top_srcdir)/aclocal.m4 +am__aclocal_m4_deps = $(top_srcdir)/acinclude.m4 \ + $(top_srcdir)/configure.in +am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \ + $(ACLOCAL_M4) +mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs +CONFIG_HEADER = $(top_builddir)/config.h +CONFIG_CLEAN_FILES = +SOURCES = +DIST_SOURCES = +#>- RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \ +#>- html-recursive info-recursive install-data-recursive \ +#>- install-dvi-recursive install-exec-recursive \ +#>- install-html-recursive install-info-recursive \ +#>- install-pdf-recursive install-ps-recursive install-recursive \ +#>- installcheck-recursive installdirs-recursive pdf-recursive \ +#>- ps-recursive uninstall-recursive +#>+ 7 +RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \ + html-recursive info-recursive install-data-recursive \ + install-dvi-recursive install-exec-recursive \ + install-html-recursive install-info-recursive \ + install-pdf-recursive install-ps-recursive install-recursive \ + installcheck-recursive installdirs-recursive pdf-recursive \ + ps-recursive uninstall-recursive nmcheck-recursive bcheck-recursive +RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \ + distclean-recursive maintainer-clean-recursive +ETAGS = etags +CTAGS = ctags +DIST_SUBDIRS = $(SUBDIRS) +#>- DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) +#>+ 1 +DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) $(KDE_DIST) +ACLOCAL = @ACLOCAL@ +AMTAR = @AMTAR@ +ARTSCCONFIG = @ARTSCCONFIG@ +AUTOCONF = @AUTOCONF@ +AUTODIRS = @AUTODIRS@ +AUTOHEADER = @AUTOHEADER@ +AUTOMAKE = @AUTOMAKE@ +AWK = @AWK@ +CONF_FILES = @CONF_FILES@ +CYGPATH_W = @CYGPATH_W@ +DCOPIDL = @DCOPIDL@ +DCOPIDL2CPP = @DCOPIDL2CPP@ +DCOPIDLNG = @DCOPIDLNG@ +DCOP_DEPENDENCIES = @DCOP_DEPENDENCIES@ +DEFS = @DEFS@ +ECHO_C = @ECHO_C@ +ECHO_N = @ECHO_N@ +ECHO_T = @ECHO_T@ +GMSGFMT = @GMSGFMT@ +INSTALL = @INSTALL@ +INSTALL_DATA = @INSTALL_DATA@ +INSTALL_PROGRAM = @INSTALL_PROGRAM@ +INSTALL_SCRIPT = @INSTALL_SCRIPT@ +INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@ +KCFG_DEPENDENCIES = @KCFG_DEPENDENCIES@ +KCONFIG_COMPILER = @KCONFIG_COMPILER@ +KDECONFIG = @KDECONFIG@ +KDE_EXTRA_RPATH = @KDE_EXTRA_RPATH@ +KDE_RPATH = @KDE_RPATH@ +KDE_XSL_STYLESHEET = @KDE_XSL_STYLESHEET@ +LIBOBJS = @LIBOBJS@ +LIBS = @LIBS@ +LN_S = @LN_S@ +LTLIBOBJS = @LTLIBOBJS@ +MAKEINFO = @MAKEINFO@ +MAKEKDEWIDGETS = @MAKEKDEWIDGETS@ +MCOPIDL = @MCOPIDL@ +MEINPROC = @MEINPROC@ +MKDIR_P = @MKDIR_P@ +MSGFMT = @MSGFMT@ +PACKAGE = @PACKAGE@ +PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@ +PACKAGE_NAME = @PACKAGE_NAME@ +PACKAGE_STRING = @PACKAGE_STRING@ +PACKAGE_TARNAME = @PACKAGE_TARNAME@ +PACKAGE_VERSION = @PACKAGE_VERSION@ +PATH_SEPARATOR = @PATH_SEPARATOR@ +SET_MAKE = @SET_MAKE@ +SHELL = @SHELL@ +STRIP = @STRIP@ +TOPSUBDIRS = @TOPSUBDIRS@ +VERSION = @VERSION@ +XGETTEXT = @XGETTEXT@ +XMLLINT = @XMLLINT@ +X_RPATH = @X_RPATH@ +abs_builddir = @abs_builddir@ +abs_srcdir = @abs_srcdir@ +abs_top_builddir = @abs_top_builddir@ +abs_top_srcdir = @abs_top_srcdir@ +am__leading_dot = @am__leading_dot@ +am__tar = @am__tar@ +am__untar = @am__untar@ +#>- bindir = @bindir@ +#>+ 2 +DEPDIR = .deps +bindir = @bindir@ +build_alias = @build_alias@ +builddir = @builddir@ +datadir = @datadir@ +datarootdir = @datarootdir@ +docdir = @docdir@ +dvidir = @dvidir@ +exec_prefix = @exec_prefix@ +host_alias = @host_alias@ +htmldir = @htmldir@ +includedir = @includedir@ +infodir = @infodir@ +install_sh = @install_sh@ +kde_appsdir = @kde_appsdir@ +kde_bindir = @kde_bindir@ +kde_confdir = @kde_confdir@ +kde_datadir = @kde_datadir@ +kde_htmldir = @kde_htmldir@ +kde_icondir = @kde_icondir@ +kde_kcfgdir = @kde_kcfgdir@ +kde_libs_htmldir = @kde_libs_htmldir@ +kde_libs_prefix = @kde_libs_prefix@ +kde_locale = @kde_locale@ +kde_mimedir = @kde_mimedir@ +kde_moduledir = @kde_moduledir@ +kde_servicesdir = @kde_servicesdir@ +kde_servicetypesdir = @kde_servicetypesdir@ +kde_sounddir = @kde_sounddir@ +kde_styledir = @kde_styledir@ +kde_templatesdir = @kde_templatesdir@ +kde_wallpaperdir = @kde_wallpaperdir@ +kde_widgetdir = @kde_widgetdir@ +tdeinitdir = @tdeinitdir@ +libdir = @libdir@ +libexecdir = @libexecdir@ +localedir = @localedir@ +localstatedir = @localstatedir@ +mandir = @mandir@ +mkdir_p = @mkdir_p@ +oldincludedir = @oldincludedir@ +pdfdir = @pdfdir@ +prefix = @prefix@ +program_transform_name = @program_transform_name@ +psdir = @psdir@ +sbindir = @sbindir@ +sharedstatedir = @sharedstatedir@ +srcdir = @srcdir@ +sysconfdir = @sysconfdir@ +target_alias = @target_alias@ +top_builddir = @top_builddir@ +top_srcdir = @top_srcdir@ +xdg_appsdir = @xdg_appsdir@ +xdg_directorydir = @xdg_directorydir@ +xdg_menudir = @xdg_menudir@ +KDE_LANG = fr +#>- SUBDIRS = $(AUTODIRS) +#>+ 1 +SUBDIRS =. +KDE_DOCS = AUTO +KDE_MANS = AUTO +#>- all: all-recursive +#>+ 1 +all: docs-am all-recursive + +.SUFFIXES: +$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps) +#>- @for dep in $?; do \ +#>- case '$(am__configure_deps)' in \ +#>- *$$dep*) \ +#>- cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ +#>- && exit 0; \ +#>- exit 1;; \ +#>- esac; \ +#>- done; \ +#>- echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu docs/tdewebdev/quanta/Makefile'; \ +#>- cd $(top_srcdir) && \ +#>- $(AUTOMAKE) --gnu docs/tdewebdev/quanta/Makefile +#>+ 12 + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ + && exit 0; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu docs/tdewebdev/quanta/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/tdewebdev/quanta/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdewebdev/quanta/Makefile.in +.PRECIOUS: Makefile +Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status + @case '$?' in \ + *config.status*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \ + *) \ + echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe)'; \ + cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@ $(am__depfiles_maybe);; \ + esac; + +$(top_builddir)/config.status: $(top_srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +$(top_srcdir)/configure: $(am__configure_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh +$(ACLOCAL_M4): $(am__aclocal_m4_deps) + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh + +# This directory's subdirectories are mostly independent; you can cd +# into them and run `make' without going through this Makefile. +# To change the values of `make' variables: instead of editing Makefiles, +# (1) if the variable is set in `config.status', edit `config.status' +# (which will cause the Makefiles to be regenerated when you run `make'); +# (2) otherwise, pass the desired values on the `make' command line. +$(RECURSIVE_TARGETS): + @failcom='exit 1'; \ + for f in x $$MAKEFLAGS; do \ + case $$f in \ + *=* | --[!k]*);; \ + *k*) failcom='fail=yes';; \ + esac; \ + done; \ + dot_seen=no; \ + target=`echo $@ | sed s/-recursive//`; \ + list='$(SUBDIRS)'; for subdir in $$list; do \ + echo "Making $$target in $$subdir"; \ + if test "$$subdir" = "."; then \ + dot_seen=yes; \ + local_target="$$target-am"; \ + else \ + local_target="$$target"; \ + fi; \ + (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + || eval $$failcom; \ + done; \ + if test "$$dot_seen" = "no"; then \ + $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \ + fi; test -z "$$fail" + +$(RECURSIVE_CLEAN_TARGETS): + @failcom='exit 1'; \ + for f in x $$MAKEFLAGS; do \ + case $$f in \ + *=* | --[!k]*);; \ + *k*) failcom='fail=yes';; \ + esac; \ + done; \ + dot_seen=no; \ + case "$@" in \ + distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \ + *) list='$(SUBDIRS)' ;; \ + esac; \ + rev=''; for subdir in $$list; do \ + if test "$$subdir" = "."; then :; else \ + rev="$$subdir $$rev"; \ + fi; \ + done; \ + rev="$$rev ."; \ + target=`echo $@ | sed s/-recursive//`; \ + for subdir in $$rev; do \ + echo "Making $$target in $$subdir"; \ + if test "$$subdir" = "."; then \ + local_target="$$target-am"; \ + else \ + local_target="$$target"; \ + fi; \ + (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \ + || eval $$failcom; \ + done && test -z "$$fail" +tags-recursive: + list='$(SUBDIRS)'; for subdir in $$list; do \ + test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) tags); \ + done +ctags-recursive: + list='$(SUBDIRS)'; for subdir in $$list; do \ + test "$$subdir" = . || (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS) ctags); \ + done + +ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES) + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonemtpy = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + mkid -fID $$unique +tags: TAGS + +TAGS: tags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ + $(TAGS_FILES) $(LISP) + tags=; \ + here=`pwd`; \ + if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \ + include_option=--etags-include; \ + empty_fix=.; \ + else \ + include_option=--include; \ + empty_fix=; \ + fi; \ + list='$(SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + test ! -f $$subdir/TAGS || \ + tags="$$tags $$include_option=$$here/$$subdir/TAGS"; \ + fi; \ + done; \ + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + if test -z "$(ETAGS_ARGS)$$tags$$unique"; then :; else \ + test -n "$$unique" || unique=$$empty_fix; \ + $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \ + $$tags $$unique; \ + fi +ctags: CTAGS +CTAGS: ctags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \ + $(TAGS_FILES) $(LISP) + tags=; \ + list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \ + unique=`for i in $$list; do \ + if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \ + done | \ + $(AWK) '{ files[$$0] = 1; nonempty = 1; } \ + END { if (nonempty) { for (i in files) print i; }; }'`; \ + test -z "$(CTAGS_ARGS)$$tags$$unique" \ + || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \ + $$tags $$unique + +GTAGS: + here=`$(am__cd) $(top_builddir) && pwd` \ + && cd $(top_srcdir) \ + && gtags -i $(GTAGS_ARGS) $$here + +distclean-tags: + -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags + +#>- distdir: $(DISTFILES) +#>+ 1 +distdir: distdir-nls $(DISTFILES) + @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \ + list='$(DISTFILES)'; \ + dist_files=`for file in $$list; do echo $$file; done | \ + sed -e "s|^$$srcdirstrip/||;t" \ + -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \ + case $$dist_files in \ + */*) $(MKDIR_P) `echo "$$dist_files" | \ + sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \ + sort -u` ;; \ + esac; \ + for file in $$dist_files; do \ + if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \ + if test -d $$d/$$file; then \ + dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \ + if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \ + cp -pR $(srcdir)/$$file $(distdir)$$dir || exit 1; \ + fi; \ + cp -pR $$d/$$file $(distdir)$$dir || exit 1; \ + else \ + test -f $(distdir)/$$file \ + || cp -p $$d/$$file $(distdir)/$$file \ + || exit 1; \ + fi; \ + done + list='$(DIST_SUBDIRS)'; for subdir in $$list; do \ + if test "$$subdir" = .; then :; else \ + test -d "$(distdir)/$$subdir" \ + || $(MKDIR_P) "$(distdir)/$$subdir" \ + || exit 1; \ + distdir=`$(am__cd) $(distdir) && pwd`; \ + top_distdir=`$(am__cd) $(top_distdir) && pwd`; \ + (cd $$subdir && \ + $(MAKE) $(AM_MAKEFLAGS) \ + top_distdir="$$top_distdir" \ + distdir="$$distdir/$$subdir" \ + am__remove_distdir=: \ + am__skip_length_check=: \ + distdir) \ + || exit 1; \ + fi; \ + done +check-am: all-am +check: check-recursive +all-am: Makefile +installdirs: installdirs-recursive +installdirs-am: +install: install-recursive +install-exec: install-exec-recursive +install-data: install-data-recursive +#>- uninstall: uninstall-recursive +#>+ 1 +uninstall: uninstall-docs uninstall-nls uninstall-recursive + +install-am: all-am + @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am + +installcheck: installcheck-recursive +install-strip: + $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \ + install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \ + `test -z '$(STRIP)' || \ + echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install +mostlyclean-generic: + +clean-generic: + +distclean-generic: + -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES) + +maintainer-clean-generic: + @echo "This command is intended for maintainers to use" + @echo "it deletes files that may require special tools to rebuild." +#>- clean: clean-recursive +#>+ 1 +clean: kde-rpo-clean clean-recursive + +#>- clean-am: clean-generic mostlyclean-am +#>+ 1 +clean-am: clean-docs clean-bcheck clean-generic mostlyclean-am + +distclean: distclean-recursive + -rm -f Makefile +distclean-am: clean-am distclean-generic distclean-tags + +dvi: dvi-recursive + +dvi-am: + +html: html-recursive + +info: info-recursive + +info-am: + +#>- install-data-am: +#>+ 1 +install-data-am: install-docs install-nls + +install-dvi: install-dvi-recursive + +install-exec-am: + +install-html: install-html-recursive + +install-info: install-info-recursive + +install-man: + +install-pdf: install-pdf-recursive + +install-ps: install-ps-recursive + +installcheck-am: + +maintainer-clean: maintainer-clean-recursive + -rm -f Makefile +maintainer-clean-am: distclean-am maintainer-clean-generic + +mostlyclean: mostlyclean-recursive + +mostlyclean-am: mostlyclean-generic + +pdf: pdf-recursive + +pdf-am: + +ps: ps-recursive + +ps-am: + +uninstall-am: + +.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) install-am \ + install-strip + +.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \ + all all-am check check-am clean clean-generic ctags \ + ctags-recursive distclean distclean-generic distclean-tags \ + distdir dvi dvi-am html html-am info info-am install \ + install-am install-data install-data-am install-dvi \ + install-dvi-am install-exec install-exec-am install-html \ + install-html-am install-info install-info-am install-man \ + install-pdf install-pdf-am install-ps install-ps-am \ + install-strip installcheck installcheck-am installdirs \ + installdirs-am maintainer-clean maintainer-clean-generic \ + mostlyclean mostlyclean-generic pdf pdf-am ps ps-am tags \ + tags-recursive uninstall uninstall-am + +# Tell versions [3.59,3.63) of GNU make to not export all variables. +# Otherwise a system limit (for SysV at least) may be exceeded. +.NOEXPORT: + +#>+ 2 +KDE_DIST=installation.docbook config-quanta.docbook quanta-projects.docbook index.docbook working-with-quanta.docbook credits-license.docbook glossary.docbook debugging-quanta.docbook index.cache.bz2 quanta-menus.docbook fundamentals.docbook Makefile.in extending-quanta.docbook introduction.docbook adv-quanta.docbook Makefile.am q-and-a.docbook + +#>+ 24 +index.cache.bz2: $(srcdir)/index.docbook $(KDE_XSL_STYLESHEET) glossary.docbook config-quanta.docbook quanta-menus.docbook credits-license.docbook index.docbook adv-quanta.docbook fundamentals.docbook introduction.docbook working-with-quanta.docbook q-and-a.docbook installation.docbook quanta-projects.docbook extending-quanta.docbook debugging-quanta.docbook + @if test -n "$(MEINPROC)"; then echo $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; $(MEINPROC) --check --cache index.cache.bz2 $(srcdir)/index.docbook; fi + +docs-am: index.cache.bz2 + +install-docs: docs-am install-nls + $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta + @if test -f index.cache.bz2; then \ + echo $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/; \ + $(INSTALL_DATA) index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/; \ + elif test -f $(srcdir)/index.cache.bz2; then \ + echo $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/; \ + $(INSTALL_DATA) $(srcdir)/index.cache.bz2 $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/; \ + fi + -rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/common + $(LN_S) $(kde_libs_htmldir)/$(KDE_LANG)/common $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/common + +uninstall-docs: + -rm -rf $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta + +clean-docs: + -rm -f index.cache.bz2 + + +#>+ 13 +install-nls: + $(mkinstalldirs) $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta + @for base in glossary.docbook config-quanta.docbook quanta-menus.docbook credits-license.docbook index.docbook adv-quanta.docbook fundamentals.docbook introduction.docbook working-with-quanta.docbook q-and-a.docbook installation.docbook quanta-projects.docbook extending-quanta.docbook debugging-quanta.docbook ; do \ + echo $(INSTALL_DATA) $$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/$$base ;\ + $(INSTALL_DATA) $(srcdir)/$$base $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/$$base ;\ + done + +uninstall-nls: + for base in glossary.docbook config-quanta.docbook quanta-menus.docbook credits-license.docbook index.docbook adv-quanta.docbook fundamentals.docbook introduction.docbook working-with-quanta.docbook q-and-a.docbook installation.docbook quanta-projects.docbook extending-quanta.docbook debugging-quanta.docbook ; do \ + rm -f $(DESTDIR)$(kde_htmldir)/$(KDE_LANG)/quanta/$$base ;\ + done + + +#>+ 5 +distdir-nls: + for file in glossary.docbook config-quanta.docbook quanta-menus.docbook credits-license.docbook index.docbook adv-quanta.docbook fundamentals.docbook introduction.docbook working-with-quanta.docbook q-and-a.docbook installation.docbook quanta-projects.docbook extending-quanta.docbook debugging-quanta.docbook ; do \ + cp $(srcdir)/$$file $(distdir); \ + done + +#>+ 15 +force-reedit: + @for dep in $?; do \ + case '$(am__configure_deps)' in \ + *$$dep*) \ + cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh \ + && exit 0; \ + exit 1;; \ + esac; \ + done; \ + echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu docs/tdewebdev/quanta/Makefile'; \ + cd $(top_srcdir) && \ + $(AUTOMAKE) --gnu docs/tdewebdev/quanta/Makefile + cd $(top_srcdir) && perl ../scripts/admin/am_edit -p../scripts/admin docs/tdewebdev/quanta/Makefile.in + + +#>+ 21 +clean-bcheck: + rm -f *.bchecktest.cc *.bchecktest.cc.class a.out + +bcheck: bcheck-recursive + +bcheck-am: + @for i in ; do \ + if test $(srcdir)/$$i -nt $$i.bchecktest.cc; then \ + echo "int main() {return 0;}" > $$i.bchecktest.cc ; \ + echo "#include \"$$i\"" >> $$i.bchecktest.cc ; \ + echo "$$i"; \ + if ! $(CXX) $(DEFS) -I. -I$(srcdir) -I$(top_builddir) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(CXXFLAGS) $(KDE_CXXFLAGS) --dump-class-hierarchy -c $$i.bchecktest.cc; then \ + rm -f $$i.bchecktest.cc; exit 1; \ + fi ; \ + echo "" >> $$i.bchecktest.cc.class; \ + perl $(top_srcdir)/admin/bcheck.pl $$i.bchecktest.cc.class || { rm -f $$i.bchecktest.cc; exit 1; }; \ + rm -f a.out; \ + fi ; \ + done + + +#>+ 3 +final: + $(MAKE) all-am + +#>+ 3 +final-install: + $(MAKE) install-am + +#>+ 3 +no-final: + $(MAKE) all-am + +#>+ 3 +no-final-install: + $(MAKE) install-am + +#>+ 3 +kde-rpo-clean: + -rm -f *.rpo + +#>+ 3 +nmcheck: +nmcheck-am: nmcheck diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/adv-quanta.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/adv-quanta.docbook new file mode 100644 index 00000000000..83687254760 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/adv-quanta.docbook @@ -0,0 +1,469 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="advanced-quanta-3-2"> +<chapterinfo> +<title +>Fonctions avancées</title> +<authorgroup> +<author +><firstname +>Christopher</firstname +> <surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> + +</author> + +&traducteurPatrickMichelon; + +</authorgroup> +</chapterinfo> + +<title +>Fonctions avancées</title> + +<para +>Ce chapitre décrit les fonctions avancées de &quantaplus; et comment les utiliser. </para> + +<sect1 id="xml-tools-3-2"> +<title +>Outils &XML;</title> + +<para +>La version 3.2 de &quantaplus; amène avec elle de nombreux nouveaux outils et fonctions &XML;. Les outils sont uniques dans leur intégration avec &quantaplus;. Tous ces outils utilisent <application +>Kommander</application +> comme interface et <application +>libxml2</application +> et <application +>libxslt</application +> comme dorsal. La combinaison de ces outils en fait des outils rapides, efficaces, productifs et complets. </para> + +<sect2 id="kde-db-3-2"> +<title +>Outils de documentation de &kde;</title> + +<para +>&quantaplus; gère les deux principaux outils de documentation de &kde; : <command +>meinproc</command +> et <command +>checkXML</command +>. </para> + +<sect3 id="meinproc-3-2"> +<title +><command +>meinproc</command +></title> + +<para +>Toute personne qui a travaillé avec la documentation de &kde; sait à quel point <command +>meinproc</command +> est brillant. C'est un très bon outil avec une superbe interface graphique. Vous n'avez plus besoin de passer par un shell, il suffit de cliquer sur l'icône qui ressemble à un processeur et c'est fini ! </para> + +<variablelist> +<varlistentry> +<term +><guilabel +>Dossier de travail courant</guilabel +></term> +<listitem> +<para +>Cette application attend qu'un fichier <filename +>index.docbook</filename +> soit présent dans un dossier. Si <filename +>index.docbook</filename +> est dans le dossier de travail courant, laissez simplement <guilabel +>Dossier de travail courant</guilabel +> coché. S'il n'est pas présent, décochez <guilabel +>Dossier de travail courant</guilabel +> et entrez dans le dossier que vous souhaitez traiter dans le champ <guilabel +>Autre dossier</guilabel +>. </para> +</listitem> +</varlistentry> +</variablelist> + +<note> +<para +>Les fichiers en sortie sont placés dans le même dossier que les fichiers source. Tous les fichiers &HTML; sont enlevés à chaque fois que <command +>meinproc</command +> est utilisé. </para> +</note> + +</sect3> + +<sect3 id="checkxml-3-2"> +<title +><command +>checkXML</command +></title> + +<para +>Encore une fois, toute personne qui a travaillé avec la documentation de &kde; connaît cette application utile. Là encore, &quantaplus; lui fournit une petite interface graphique. </para> + +<variablelist> +<varlistentry> +<term +><guilabel +>Dossier de travail courant</guilabel +></term> +<listitem> +<para +>Si le fichier couramment ouvert est le fichier <filename +>index.docbook</filename +>, laissez simplement <guilabel +>Dossier de travail courant</guilabel +> coché. S'il n'est pas ouvert, décochez <guilabel +>Dossier de travail courant</guilabel +> et entrez dans le dossier dans lequel <filename +>index.docbook</filename +> peut etre trouvé. </para> +</listitem> +</varlistentry> +</variablelist> + +<note> +<title +>Sortie</title> +<para +>S'il y a une sortie, votre fichier est alors invalide. Corrigez alors les erreurs, et essayez de nouveau. </para> +</note> +</sect3> +</sect2> + +<sect2 id="xmlval-3-2"> +<title +>Validation &XML; </title> + +<para +>&quantaplus; possède un très bon outil de validation &XML; qui utilise le dorsal <command +>xmllint</command +>. </para> + +<variablelist> +<varlistentry> +<term +><guilabel +>Fichier courant</guilabel +></term> +<listitem> +<para +>Si le fichier à valider est actuellement ouvert dans &quantaplus;, laissez simplement <guilabel +>Fichier courant</guilabel +> coché. S'il ne l'est pas, décochez alors <guilabel +>Fichier courant</guilabel +> et sélectionnez le fichier à valider à partir du sélecteur Autre fichier. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Vérification de la conformité</guilabel +></term> +<listitem> +<para +>Si vous souhaitez seulement savoir si un fichier est conforme, cliquez sur la case à cocher <guilabel +>Vérification de la conformité seule</guilabel +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>URI de définition</guilabel +></term> +<listitem> +<para +>Si vous utilisez une &DTD;, et qu'elle est spécifiée dans le fichier &XML;, sélectionnez alors &DTD; (interne)(défaut). Autrement, sélectionnez &DTD; (externe) et localisez la &DTD; avec le sélecteur de fichiers définition &URI;. La validation &W3C; &XML; Schema et RelaxNG est requise pour être définie en externe via le sélecteur de fichiers <guilabel +>Definition &URI;</guilabel +>. </para> +</listitem> +</varlistentry> +</variablelist> +</sect2> + +<sect2 id="xsltproc-3-2"> +<title +>Traitement &XSL;</title> + +<para +>Oui, &quantaplus; possède un outil de traitement &XSL;. Celui-ci utilise l'outil <command +>xsltproc</command +> fourni avec <application +>libxml2</application +>. </para> + +<variablelist> +<varlistentry> +<term +><guilabel +>Fichier courant</guilabel +></term> +<listitem> +<para +>Si le fichier à traiter est actuellement ouvert dans &quantaplus;, laissez simplement <guilabel +>Fichier courant</guilabel +> coché. S'il ne l'est pas, décochez alors <guilabel +>Fichier courant</guilabel +> et sélectionnez le fichier à traiter à partir du sélecteur Autre fichier. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +>Feuille de style</term> +<listitem> +<para +>Sélectionnez le fichier &XSL; que vous souhaitez faire utiliser. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Nom du fichier de sortie</guilabel +></term> +<listitem> +<para +>Donnez le nom du fichier que vous souhaitez pour le fichier de sortie. Le fichier est sorti par défaut dans votre dossier personnel. </para> +</listitem> +</varlistentry> +</variablelist> + +<note> +<para +>Cette application manque de flexibilité. Cela sera amélioré. </para> +</note> +</sect2> + +</sect1> + +<!-- <sect1 id="kfilereplace-3-2"> +<title +>KFileReplace</title> + +<para> +KFileReplace is a terrific new addition to &quantaplus;. It allows one to +quickly replace strings over multiple files in only a few clicks of the +mouse. Imagine you have converted all your GIF images to PNG images +(hasn't everyone done this already?), only the extension has changed, and +you have the <img /> tag scattered throughout 50 XHTML files. Are you +going to do a Find & Replace on every file? Surely not when you can do +them all at the same time! This is only one of the many situations where +you will find KFileReplace a seriously helpful tool. This section will show +you how to use this wonderful feature. +</para> + +<sect2 id="using-kfr-3-2"> +<title +>Using KFileReplace</title> + +<para> +With all these wonderful features KFileReplace has, surely you are +incredibly interested in how to use it! Well, make sure your swim suit +is on tight, because we are about to dive in! +</para> + +<sect3 id="start-kfr-3-2"> +<title +>Starting KFileReplace</title> + +<para> +You will find KFileReplace in two places: &quantaplus;' main toolbar and the +menubar (Plugins -> KFileReplace). It is represented by this icon: +<inlinemediaobject> +<imageobject> +<imagedata fileref="kfr-icon.png" format="PNG"/> +</imageobject> +</inlinemediaobject +>. +By executing it from either location, you will be presented with the New +Search & Replace Project dialog. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="kfr-new-dialog.png" format="PNG"/> +</imageobject> +<caption +><para +>KFileReplace's New Search & Replace Project dialog.</para +></caption> +</mediaobject> + +</sect3> + +<sect3 id="replace-string-kfr-3-2"> +<title +>Replacing Strings in Files Over Multiple Folders</title> + + +<para> +Your boss just gave word that: + +<orderedlist numeration="arabic"> +<listitem> +<para +>all image formats will be PNG from now on;</para> +</listitem> +<listitem> +<para +>all current images must be converted to PNG;</para> +</listitem> +<listitem> +<para +>and it all needs to be done in one hour.</para> +</listitem> +</orderedlist> + +<quote +>One hour!?!?</quote +> you think to yourself. <quote +>It'll take at +least 45 minutes to convert the images!</quote +> Calm down. Convert +the images, load up your project, and fire up KFileReplace. Filter for +only the file types you want to change. Press the <inlinemediaobject> +<imageobject +><imagedata format="PNG" fileref=""/></imageobject> +</inlinemediaobject +> and for, say GIF images, .gif for the string to +replace and .png for the replacement string. +</para> + +</sect3> +</sect2> +</sect1 +> --> + +<sect1 id="kparts-3-2"> +<sect1info> +<title +>Utilisation de modules externes</title> +<authorgroup> +<author +><firstname +>Mathieu</firstname +> <surname +>Kooiman</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +&traducteurPatrickMichelon; + +</authorgroup> +</sect1info> + +<title +>Utilisation de modules externes</title> + +<sect2 id="what-is-a-plugin-3-2"> +<title +>Qu'est-ce qu'un module externe ?</title> + +<para +>&quantaplus; est capable de charger des modules externes, qui sont des KParts. La structure KPart est une autre structure très puissante de &kde;. Un KPart est un conteneur de fonctionnalités réutilisable et relativement petit. Il permet aux développeurs &kde; de construire sur le travail d'autres programmeurs. Un exemple de ceci est &quantaplus; lui-même. L'éditeur de &quantaplus; utilise le KPart &kate;. Le KPart &kate; avait déjà tout un groupe de fonctionnalités dont &quantaplus; avait besoin comme la mise en surbrillance de la syntaxe. L'intégration dans &quantaplus; a permis aux développeurs de &quantaplus; de se concentrer sur ce que &quantaplus; devait faire, plutôt que de faire face aux nombreux problèmes qu'aurait amené la réalisation d'un éditeur à partir de rien. </para> + +<para +>Les modules externes qui sont chargés par &quantaplus; peuvent ne rien avoir à faire avec &quantaplus; lui-même. Ceci en fait un système de modules externes très puissant. Vous pouvez bénéficier de fonctionnalités additionnelles et ne pas avoir à attendre que quelqu'un l'intègre dans &quantaplus; ! Les modules externes peuvent être chargés dans nombre d'éléments d'interface graphique. Plus sur ce sujet ci-dessous. </para> + +</sect2> + +<sect2 id="plugin-dialog-3-2"> +<title +>Comprendre la boîte de dialogue d'édition de module externe</title> + +<para +>Pour installer un module externe ou un Kpart, nous partons du menu <menuchoice +> <guimenu +>Édition</guimenu +> <guimenuitem +>Modules externes</guimenuitem +> </menuchoice +>. Ceci fait apparaître la boîte de dialogue suivante : </para> + +<mediaobject> +<imageobject> +<imagedata format="PNG" fileref="plugin-edit.png"/> +</imageobject> +<caption +><para +>La boîte de dialogue d'édition de module externe</para +></caption> +</mediaobject> + +<para +>Cette boîte de dialogue vous laisse gérer tous les modules externes définis et vous laisse en ajouter de nouveaux. Nous allons décrire chacun des éléments d'interface graphique ci-dessous : <variablelist> +<varlistentry> +<term +><guilabel +>Dossier de recherche</guilabel +></term> +<listitem> +<para +>Vous pouvez donner ici un chemin de recherche. Lorsque vous ajoutez un module externe sans <guilabel +>emplacement</guilabel +>, &quantaplus; cherche selon ces chemins pour trouver le module. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Ajouter...</guilabel +></term> +<listitem> +<para +>Ceci fait apparaître une boîte de dialogue qui vous permet d'ajouter un nouveau module externe. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Configurer...</guilabel +></term> +<listitem> +<para +>Ceci vous permet de changer les réglages d'un module externe donné. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Supprimer</guilabel +></term> +<listitem> +<para +>Enlève le module externe sélectionné. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><guilabel +>Rafraîchir</guilabel +></term> +<listitem> +<para +>Rafraîchit le contenu de la boîte de dialogue. </para> +</listitem> +</varlistentry> +</variablelist> +</para> +</sect2> +</sect1> +&debugging-quanta; </chapter> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/config-quanta.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/config-quanta.docbook new file mode 100644 index 00000000000..7e0fc8a994e --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/config-quanta.docbook @@ -0,0 +1,9 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="config-quanta-3-2"> +<title +>Configurer &quantaplus;</title> + +<para +>Reste a écrire </para> +</chapter> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/credits-license.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/credits-license.docbook new file mode 100644 index 00000000000..6025d9af269 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/credits-license.docbook @@ -0,0 +1,260 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="credits-license-3-2"> +<chapterinfo> +<title +>Remerciements et licence</title> +<authorgroup> +<author +><firstname +>Christopher</firstname +> <surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +&traducteurPatrickMichelon; + +</authorgroup> +</chapterinfo> + +<title +>Remerciements et licence</title> + +<note> +<para +>Nos excuses à toute personne oubliée ou dont le nom a mal été orthographié. </para> +</note> + +<para +>Remerciements à tous ceux qui ont passé du temps à contribuer. </para> + +<variablelist> +<title +>L'équipe de développement de &quantaplus;.</title> + +<varlistentry> +<term +>Bergia, Andrea</term> +<listitem +><para +>Éditeur original de &CSS;.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Britton, Marc</term> +<listitem +><para +><application +>Kommander</application +>, diverses fonctions et correction de bogues.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Colton, Matthew</term> +<listitem +><para +>Écran d'accueil pour beaucoup de versions</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Deschildre, Nicolas</term> +<listitem +><para +><application +>Disposition visuelle de la page</application +> et système annuler / refaire.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Dmitrienko, Dmitri</term> +<listitem +><para +>Débogage de &PHP;4</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Gulmini, Luciano</term> +<listitem +><para +><application +>Guide de cadre</application +></para +></listitem> +</varlistentry> +<varlistentry> +<term +>Hanley, Jason P.</term> +<listitem +><para +>Différentes corrections, code de base pour la validation de &DTD; et autre travail relatif à la &DTD;.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Hindsgaul, Claus</term> +<listitem +><para +>Traduction danoise</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Hornbaker, Christopher</term> +<listitem +><para +>Documentation &XML;</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Isdale, Keith</term> +<listitem +><para +>&XSL; 1.0 &DTEP;, <application +>&kxsl;</application +></para +></listitem> +</varlistentry> +<varlistentry> +<term +>Kooiman, Mathieu</term> +<listitem +><para +>Documentation, correction de bogues et débogage &PHP;.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Laffoon, Eric</term> +<listitem +><para +>Gestionnaire de projet et administrateur du site internet</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Mantia, András</term> +<listitem +><para +>Développeur</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Moore, Richard</term> +<listitem +><para +>Encodage, documentation des balises XML originales, et plus encore.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Mous, Fabrice</term> +<listitem +><para +>Documentation</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Nickel, Robert C.</term> +<listitem +><para +>Documentation</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Pibil, Ted</term> +<listitem +><para +>Ajout et maintenance des &DTD;.</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Poplavsky, Dmitry</term> +<listitem +><para +>ex développeur de base, parti pour la version commerciale</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Vilches, George</term> +<listitem +><para +>Boîte de dialogue de publication fondée sur l'arborescence</para +></listitem> +</varlistentry> +<varlistentry> +<term +>Yakovlev, Alexander</term> +<listitem +><para +>ex développeur de base, parti pour la version commerciale</para +></listitem> +</varlistentry> +<!-- +<varlistentry> +<term +>Firstname Surname</term> +<listitem +><para +>Function</para +></listitem> +</varlistentry> +--> + +</variablelist> + +<variablelist> +<title +>Remerciements spéciaux à :</title> + +<varlistentry> +<term +>xmlsoft.org</term> +<listitem +><para +>Les rédacteurs de <application +>libxml2</application +> et <application +>libxslt</application +>.</para +></listitem> +</varlistentry> +<!-- +<varlistentry> +<term +>Name</term> +<listitem +><para +>Function</para +></listitem> +</varlistentry> +--> + +</variablelist> + +<para +>&quantaplus; <trademark class="copyright" +></trademark +>Équipe de développement de &quantaplus; 2000, 2001, 2002, 2003. </para> + +<para +>Manuel de l'utilisateur de &quantaplus; <trademark class="copyright" +></trademark +> Équipe de développement de &quantaplus; 2000, 2001, 2002, 2003. </para> +&underFDL; &underGPL; </chapter> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/debugging-quanta.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/debugging-quanta.docbook new file mode 100644 index 00000000000..9b066d97348 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/debugging-quanta.docbook @@ -0,0 +1,58 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<sect1 id="debugging-3-2"> +<sect1info> +<title +>Débogage dans &quantaplus;.</title> +<authorgroup> +<author +><firstname +>Christopher</firstname +> <surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +&traducteurPatrickMichelon; + +</authorgroup> +</sect1info> + +<title +>Débogage dans &quantaplus;.</title> + +<sect2 id="php-debugging-3-2"> +<title +>Utilisation du débogueur &PHP;.</title> + +<para +>Le débogueur &PHP; courant fourni avec &quantaplus; est très peu utilisable. Il sera enlevé de &quantaplus; dans la prochaine version (3.3) et a été désactivé par défaut dans la version courante (3.2). Vous pouvez compter sur un nouveau débogueur pour la version 3.3. </para> +</sect2> + +<sect2 id="kxsldbg-debugging-3-2"> +<title +>Utiliser &kxsl;, le débogueur &XSL;.</title> + +<para +>&kxsl; est la création de Keith Isdale, comme l'est cette section de la documentation. &kxsl; est une interface graphique &kde; et un Kpart à <command +>xsldbg</command +> que vous pouvez trouver sur http://xsldbg.sf.net, de même que beaucoup d'autres travaux de Keith. </para> + +<para +>Pour lancer &kxsl;, sélectionnez <menuchoice +> <guimenu +>Modules externes</guimenu +> <guimenuitem +>&kxsl;</guimenuitem +> </menuchoice +>. </para> + +<para +>Reportez-vous à la documentation de &kxsl; pour plus d'informations concernant son utilisation. </para> +</sect2> +</sect1> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/extending-quanta.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/extending-quanta.docbook new file mode 100644 index 00000000000..c3a9c0c9782 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/extending-quanta.docbook @@ -0,0 +1,1625 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="extending-quanta-3-2"> +<chapterinfo> +<title>Extending &quantaplus;</title> +<authorgroup> +<author> +<firstname>Christopher</firstname> +<surname>Hornbaker</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +</author> + +<!-- TRANS:ROLES_OF_TRANSLATORS --> + +</authorgroup> +</chapterinfo> + +<title>Extending &quantaplus;</title> + +<para> +This chapter describes how to customize &quantaplus; to your particular +needs and how you can help &quantaplus; become better. +</para> + +<!--<sect1 id="kommander-3-2"> +<title>Using Kommander With &quantaplus;</title> + +<para> +Kommander, by Marc Britton. +</para> +</sect1> --> + +<sect1 id="dtep-intro-3-2"> +<title>Document Type Editing Package (&DTEP;)</title> + +<para> +Document Type Editing Packages (&DTEP;s) are used in &quantaplus; to add +support for markup, scripting languages, and &CSS;. They allow +&quantaplus; to provide features like auto-completion and node trees. +Their simplicity and flexibility are what make &quantaplus; a fast, +developer friendly &IDE; for web developers. They are what make &quantaplus; +an easy-to-use, productive environment. +</para> + +<para> +&DTEP;s come in two flavors, Family 1, which are markups, and Family 2, +which are scripting and &CSS;. &DTEP;s are made up of two parts, the Tag +Folder and the Toolbars. Tag Folders are composed of two types of files, +the description.rc and TagXML files, which carry the extension .tag. +Toolbars are the handy, icon-oriented tabs of buttons (above the editing +window) which place text into a document faster than the user can type. +</para> + +<para> +This document describes how to make TagXML files, the description.rc, and +toolbars. In short, a &DTEP;. +</para> + +<para> +TagXML files (.tag) define both the attributes specific to a tag and the +layout and contents of the properties dialog &quantaplus; shows for the tag. +The description.rc file provides rules and information on the &DTEP; +itself. Toolbars provide a quick means for adding tags into a document +without worry of mis-spellings and such. +</para> + +<sect2 id="dtep-packaging-3-2"> +<title>Packaging</title> + +<para> +Tag Folders are just that, folders. They are composed only of the +description.rc and TagXML files. Tag Folders carry the name of the mark-up +language and version, if applicable. (For example, html-4.01-strict) +</para> +</sect2> + +<sect2 id="tagxml-3-2"> +<title>TagXML</title> + +<para> +The table below lists the elements defined in TagXML and declares whether +they are required or not. While not all are required, it is recommended +that you use as many as you can so that other users can have a better +experience and more information to work with. +</para> + +<informaltable> +<tgroup cols="3"> +<thead> +<row> +<entry>Element</entry> +<entry>Default Usage</entry> +<entry>Case Usage</entry> +</row> +</thead> +<tbody> +<row> +<entry>TAGS</entry> +<entry>required</entry> +<entry>always</entry> +</row> +<row> +<entry>tag</entry> +<entry>required</entry> +<entry>always</entry> +</row> +<row> +<entry>label</entry> +<entry>optional</entry> +<entry>required to create a properties dialog</entry> +</row> +<row> +<entry>attr</entry> +<entry>optional</entry> +<entry>required to define an attribute</entry> +</row> +<row> +<entry>tooltip</entry> +<entry>optional</entry> +<entry>required to have the properties dialog display a tooltip</entry> +</row> +<row> +<entry>whatsthis</entry> +<entry>optional</entry> +<entry>required to have the properties dialog display a <quote>What's This +</quote></entry> +</row> +<row> +<entry>list</entry> +<entry>optional</entry> +<entry>required when an attr is of the type <quote>list</quote></entry> +</row> +<row> +<entry>item</entry> +<entry>optional</entry> +<entry>required when <list> is used</entry> +</row> +<row> +<entry>textlocation</entry> +<entry>optional</entry> +<entry>always</entry> +</row> +<row> +<entry>location</entry> +<entry>optional</entry> +<entry>required when label is used</entry> +</row> +<row> +<entry>text</entry> +<entry>optional</entry> +<entry>required when label is used</entry> +</row> +<row> +<entry>children</entry> +<entry>optional</entry> +<entry>list of tags that can appear within the tag being defined</entry> +</row> +<row> +<entry>child</entry> +<entry>required</entry> +<entry>a children entry</entry> +</row> +<row> +<entry>stoppingtags</entry> +<entry>optional</entry> +<entry>list of tags that tell another tag to end</entry> +</row> +<row> +<entry>stoppingtag</entry> +<entry>required</entry> +<entry>a stoppingtags entry</entry> +</row> +</tbody> +</tgroup> +</informaltable> + + +<sect3 id="dtep-element-descriptions-3-2"> +<title>TagXML Element Descriptions</title> + +<para> +The following sections will describe, in detail, each element. Everything +from where they can go to what goes in them is layed out in an +easy-to-follow manner. +</para> + +<sect4 id="TAGS-3-2"> +<title>TAGS</title> + +<para> +This is the root element of a TagXML document. It may appear in a document +only once. It can contain the definition of multiple tags. This is an +element-only type element. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry><emphasis>NONE</emphasis></entry> +<entry>tag</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="tag-3-2"> +<title>tag</title> + +<para> +Wrapper for tag being defined. This is an element-only type element. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>TAGS</entry> +<entry>label, attr, stoppingtags</entry> +</row> +</tbody> +</tgroup> +</informaltable> + +<informaltable> +<tgroup cols="6"> +<thead> +<row> +<entry>Attribute</entry><entry>Type</entry><entry>Values</entry> +<entry>Default</entry><entry>Use</entry><entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>name</entry><entry>string</entry><entry></entry><entry></entry> +<entry>required</entry><entry>Specifies the name of the tag being defined.</entry> +</row> +<row> +<entry>single</entry><entry>boolean</entry><entry></entry><entry></entry> +<entry>optional</entry><entry>Specifies whether or not the tag requires a +closing tag </(tagname)>.</entry> +</row> +<row> +<entry>type</entry><entry>string</entry><entry></entry><entry>xmltag</entry> +<entry>optional</entry><entry>Specifies the type of tag being defined.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>xmltag</entry><entry></entry> +<entry></entry><entry>Type of tag is XML-based. (Family 1 only.)</entry> +</row> +<row> +<entry></entry><entry></entry><entry>property</entry><entry></entry> +<entry></entry><entry>Type of tag is &CSS; related. (Family 2 only.)</entry> +</row> +<row> +<entry></entry><entry></entry><entry>function</entry><entry></entry> +<entry></entry><entry>Type of tag is a script function. When used, +<attr> becomes arguments of the function. (Family 2 only.)</entry> +</row> +<row> +<entry></entry><entry></entry><entry>class</entry><entry></entry> +<entry></entry><entry>Type of tag is a script class. (Family 2 only.)</entry> +</row> +<row> +<entry>returnType</entry><entry>string</entry><entry></entry><entry>void +</entry> +<entry>optional</entry><entry>Specifies the return type of tag being +defined. (Family 2 only.)</entry> +</row> +<row> +<entry></entry><entry></entry><entry>void</entry><entry></entry> +<entry></entry><entry>Type of tag returns void.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>int</entry><entry></entry> +<entry></entry><entry>Type of tag returns int.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>float</entry><entry></entry> +<entry></entry><entry>Type of tag returns float.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>long</entry><entry></entry> +<entry></entry><entry>Type of tag returns long.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>string</entry><entry></entry> +<entry></entry><entry>Type of tag returns string.</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="label-3-2"> +<title>label</title> + +<para> +Place a label in the dialog. The text is specified by the <text> tag. +This is an element-only type element. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>tag</entry> +<entry>text, location</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="attr-3-2"> +<title>attr</title> + +<para> +Defines an attribute of the tag. This element occurs once for each +attribute. It defines the name and type of attribute. It also contains +additional tags that specify how this attribute should be displayed, et cetera. +This is an element-only type element. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>tag</entry> +<entry>location, list, tooltip, whatsthis, textlocation</entry> +</row> +</tbody> +</tgroup> +</informaltable> + +<informaltable> +<tgroup cols="6"> +<thead> +<row> +<entry>Attribute</entry><entry>Type</entry><entry>Values</entry> +<entry>Default</entry><entry>Use</entry><entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>name</entry><entry>string</entry><entry></entry><entry></entry> +<entry>required</entry><entry>Specifies the name of the attribute being +defined.</entry> +</row> +<row> +<entry>type</entry><entry>string</entry><entry></entry><entry>input</entry> +<entry>required</entry><entry>Specifies the type of the attribute being +defined.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>input</entry><entry></entry> +<entry></entry><entry>Field supports free text entries (text field).</entry> +</row> +<row> +<entry></entry><entry></entry><entry>check</entry><entry></entry> +<entry></entry><entry>Field value is boolean (check box).</entry> +</row> +<row> +<entry></entry><entry></entry><entry>color</entry><entry></entry> +<entry></entry><entry>Field value is a color.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>url</entry><entry></entry> +<entry></entry><entry>Field value is a &URL;. (Local file to refer to.)</entry> +</row> +<row> +<entry></entry><entry></entry><entry>list</entry><entry></entry> +<entry></entry><entry>Field value is an item from a specified list.</entry> +</row> +<row> +<entry>status</entry><entry>string</entry><entry></entry><entry>optional</entry> +<entry>required</entry><entry>Specifies whether or not the argument is +required. (Family 2 only.)</entry> +</row> +<row> +<entry></entry><entry></entry><entry>optional</entry><entry></entry> +<entry></entry><entry>Argument is optional.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>required</entry><entry></entry> +<entry></entry><entry>Argument is required.</entry> +</row> +<row> +<entry></entry><entry></entry><entry>implied</entry><entry></entry> +<entry></entry><entry>Argument is implied.</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="tooltip-3-2"> +<title>tooltip</title> + +<para> +Defines the tooltip for a field in the dialog. This element is text-only. +</para> + +<note> +<para> +Currently only plain text is supported (you cannot use any markup). +</para> +</note> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>attr</entry> +<entry><emphasis>NONE</emphasis></entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="whatsthis-3-2"> +<title>whatsthis</title> + +<para> +Defines the 'What's This' help for a field in the dialog. This element is +text-only. +</para> + +<note> +<para> +Currently only plain text is supported (you cannot use any markup). +</para> +</note> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>attr</entry> +<entry><emphasis>NONE</emphasis></entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="list-3-2"> +<title>list</title> + +<para> +A container tag that groups together the items in a list. It may appear +only once for each attribute description. This is an element-only type +element. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>attr</entry> +<entry>item</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="item-3-2"> +<title>item</title> + +<para> +Defines an item in a list. This element is text-only. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>list</entry> +<entry><emphasis>NONE</emphasis></entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="textlocation-3-2"> +<title>textlocation</title> + +<para> +Specifies the position of a tag's attribute text within a dialog. This tag +can only occur once for each attribute in the dialog (&cad; one for each +<attr> tag). This element is empty. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry> +<entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>attr</entry> +<entry><emphasis>NONE</emphasis></entry> +</row> +</tbody> +</tgroup> +</informaltable> + +<informaltable> +<tgroup cols="4"> +<thead> +<row> +<entry>Attribute</entry><entry>Type</entry> +<entry>Use</entry><entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>row</entry><entry>nonNegativeInteger</entry> +<entry>required</entry><entry>Specifies the row in the dialog layout of a +field or label.</entry> +</row> +<row> +<entry>col</entry><entry>nonNegativeInteger</entry> +<entry>required</entry><entry>Specifies the column in the dialog layout of +a field or label.</entry> +</row> +<row> +<entry>rowspan</entry><entry>nonNegativeInteger</entry> +<entry>optional</entry><entry>Specifies the number of rows a field should +span.</entry> +</row> +<row> +<entry>colspan</entry><entry>nonNegativeInteger</entry> +<entry>optional</entry><entry>Specifies the number of columns a field +should span.</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="location-3-2"> +<title>location</title> + +<para> +Specifies the position and size of a field in the dialog. This tag should +occur once for each field in the dialog (&cad; one for each <attr> and +<label> tag). This element is empty. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry><entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>label, attr</entry><entry><emphasis>NONE</emphasis></entry> +</row> +</tbody> +</tgroup> +</informaltable> + +<informaltable> +<tgroup cols="4"> +<thead> +<row> +<entry>Attribute</entry><entry>Type</entry> +<entry>Use</entry><entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>row</entry><entry>nonNegativeInteger</entry> +<entry>required</entry><entry>Specifies the row in the dialog layout of a +field or label.</entry> +</row> +<row> +<entry>col</entry><entry>nonNegativeInteger</entry> +<entry>required</entry><entry>Specifies the column in the dialog layout of +a field or label.</entry> +</row> +<row> +<entry>rowspan</entry><entry>nonNegativeInteger</entry> +<entry>optional</entry><entry>Specifies the number of rows a field should +span.</entry> +</row> +<row> +<entry>colspan</entry><entry>nonNegativeInteger</entry> +<entry>optional</entry><entry>Specifies the number of columns a field +should span.</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="text-3-2"> +<title>text</title> + +<para> +Define the text for a label or check box. This element is text-only. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry><entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>label, attr</entry><entry><emphasis>NONE</emphasis></entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="children-3-2"> +<title>children</title> + +<para> +Defines a list of elements that can appear within the tag being specified. +This element is an element-only type element. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry><entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>tag</entry><entry>child</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="child-3-2"> +<title>child</title> + +<para> +Defines a child tag. This element is empty. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry><entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>children</entry><entry><emphasis>NONE</emphasis></entry> +</row> +</tbody> +</tgroup> +</informaltable> + +<informaltable> +<tgroup cols="4"> +<thead> +<row> +<entry>Attribute</entry><entry>Type</entry> +<entry>Use</entry><entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>name</entry><entry>string</entry> +<entry>required</entry><entry>Specifies a tag that can appear within the a +certain tag.</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="stoppingtags-3-2"> +<title>stoppingtags</title> + +<para> +Defines a list of elements that force a tag to end. This element is an +element-only type element. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry><entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>tag</entry><entry>stoppingtag</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> + +<sect4 id="stoppingtag-3-2"> +<title>stoppingtag</title> + +<para> +Defines a stopping tag. This element is empty. +</para> + +<informaltable> +<tgroup cols="2"> +<thead> +<row> +<entry>Parent(s)</entry><entry>Children</entry> +</row> +</thead> +<tbody> +<row> +<entry>stoppingtags</entry><entry><emphasis>NONE</emphasis></entry> +</row> +</tbody> +</tgroup> +</informaltable> + +<informaltable> +<tgroup cols="4"> +<thead> +<row> +<entry>Attribute</entry><entry>Type</entry> +<entry>Use</entry><entry>Description</entry> +</row> +</thead> +<tbody> +<row> +<entry>name</entry><entry>string</entry> +<entry>required</entry><entry>Specifies which tags force the ending of +another tag.</entry> +</row> +</tbody> +</tgroup> +</informaltable> +</sect4> +</sect3> + +<sect3 id="tagxml-usage-3-2"> +<title>TagXML Usage</title> + +<para> +All TagXML files must begin with the &XML; declaration: <?xml +version="1.0" encoding="UTF-8"?> and must be properly nested and closed. +</para> + +<important> +<para> +White space does not adversely affect anything, but watch out for & and +< characters. These should likely be replaced with an &amp; and +&lt;, respectively, in elements such as <tooltip>, <whatsthis>, +and <text>. Not doing so will not cause a crash, but you will have +chunks of your work disappear if you do not. +</para> +</important> +</sect3> + +<sect3 id="tagxml-validation-3-2"> +<title>TagXML Validation</title> + +<para> +To validate your TagXML files, simply click the <quote>Tools</quote> +pop-up dialog at the top of &quantaplus; and select <quote>Validate +TagXML.</quote> A dialog will present itself and you need only to follow +the simple directions. +</para> + +<note> +<para> +This feature is currently not present. Currently validation occurs when +the TagXML files are loaded into &quantaplus;. +</para> +</note> +</sect3> + +<sect3 id="tagxml-examples-3-2"> +<title>TagXML Examples</title> + +<sect4 id="family-one-3-2"> +<title>Family 1</title> + +<para> +The following will show you a valid Family 1 TagXML file. This file +happens to describe &W3C; &XML; Schema's <schema> element. The file name +for this TagXML file would be schema.tag. Simple, eh? +</para> + +<informalexample> +<literallayout> +<markup> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE TAGS> +<TAGS> + <tag name="schema"> + <label> + <text>id</text> + <location col="0" row="0"/> + </label> + <attr name="id" type="input"> + <tooltip>A unique ID for the element.</tooltip> + <whatsthis>A unique ID for the element.</whatsthis> + <location col="1" row="0"/> + </attr> + + <label> + <text>version</text> + <location col="0" row="1"/> + </label> + <attr name="version" type="input"> + <tooltip>Version of the schema.</tooltip> + <whatsthis>Version of the schema.</whatsthis> + <location col="1" row="1"/> + </attr> + + <label> + <text>targetNamespace</text> + <location col="0" row="2"/> + </label> + <attr name="targetNamespace" type="input"> + <tooltip>&URI; reference of the namespace of this schema.</tooltip> + <whatsthis>&URI; reference of the namespace of this schema.</whatsthis> + <location col="1" row="2"/> + </attr> + + <label> + <text>xmlns</text> + <location col="0" row="3"/> + </label> + <attr name="xmlns" type="input"> + <tooltip>&URI; reference for one or more namespaces for use in this schema. + If no prefix is used, then components of that namespace may be used unqualified.</tooltip> + <whatsthis>&URI; reference for one or more namespaces for use in this schema. + If no prefix is used, then components of that namespace may be used unqualified.</whatsthis> + <location col="1" row="3"/> + </attr> + + <label> + <text>attributeFormDefault</text> + <location col="0" row="4"/> + </label> + <attr name="attributeFormDefault" type="list"> + <items> + <item>qualified</item> + <item>unqualified</item> + </items> + <tooltip>Default form for all attributes within this schema.</tooltip> + <whatsthis>Default form for all attributes within this schema.</whatsthis> + <location col="1" row="4"/> + </attr> + + <label> + <text>elementFormDefault</text> + <location col="0" row="5"/> + </label> + <attr name="elementFormDefault" type="list"> + <items> + <item>qualified</item> + <item>unqualified</item> + </items> + <tooltip>Default form for all elements within this schema.</tooltip> + <whatsthis>Default form for all elements within this schema.</whatsthis> + <location col="1" row="5"/> + </attr> + + <label> + <text>blockDefault</text> + <location col="0" row="6"/> + </label> + <attr name="blockDefault" type="input"> + <location col="1" row="6"/> + </attr> + + <label> + <text>finalDefault</text> + <location col="0" row="7"/> + </label> + <attr name="finalDefault" type="input"> + <location col="1" row="7"/> + </attr> + </tag> +</TAGS> +</markup> +</literallayout> +</informalexample> +</sect4> + +<sect4 id="family-two-3-2"> +<title>Family 2</title> + +<para> +The following will show you a valid Family 2 TagXML file. This file +happens to describe &PHP;'s overload function. The file name for this +TagXML file would be overload.tag. +</para> + +<informalexample> +<literallayout> +<markup> +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE tags> +<tags> + <tag name="overload" type="function" returnType="void"> +<attr name="class_name" type="string" status="optional"/> + </tag> +</tags> +</markup> +</literallayout> +</informalexample> +</sect4> +</sect3> +</sect2> + +<sect2 id="descriptionrc-3-2"> +<title>description.rc</title> + +<para> +The description.rc file is, also, quite simple. Not all of the following +need be used. The basic structure of the description.rc file is as +follows. +</para> + +<sect3 id="family-one-structure-3-2"> +<title>Family 1 Structure</title> + +<informalexample> +<literallayout> +<markup> +[General] - Generic information. +Version = Use 1 for &quantaplus; version <=3.1.2 and 2 for any version greater. +Name = DTD definition string. (-//&W3C;//DTD HTML 4.01 Transitional//EN) +NickName = The beautified name of the DTD. (HTML 4.01 Transitional). If not defined, Name is +used as NickName. +&URL; = &URL; pointing to the DTD definition. (http://www.w3.org/TR/html4/loose.dtd) +DoctypeString = The string that should appear in the !DOCTYPE declaration. +(HTML PUBLIC "-//&W3C;//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd") +Inherits = The name of the DTD from where this DTD inherits its tags. (-//&W3C;//DTD HTML 4.01//EN) +DefaultExtension = New files are created with this extension. (html) +Groups = The list of common attribute groups, which may be present in more than one tag. +(Core, I18n, Script) See below. (Group1, Group2...) +NumOfPages = How many pages does a tag dialog have, aside of the page containing the +attributes defined in the tag file? See below. (Page1,...) +CaseSensitive = Case-sensitiveness of the DTD. (true|false) +Family = 1This type of DTEP is of family 1, since it is a markup. + +[Toolbars] - Information about DTEP toolbars. +Location = The folder name inside $KDEDIR($KDEHOME)/share/apps/quanta/toolbars +where the toolbars for this DTEP are. +Names = The list of toolbar file names, minus the .toolbar.tgz extension, that +are loaded for this DTEP from the above folder. + +[Group1] - Replace with one of the Groups listed below. +Attributes = The list of attributes for this group. Currently, all of the listed attributes are + treated as strings. +Example: +[Core] +Attributes = id, class, style, title + +[Page1] - Description of a tag editor page. +Title = The title of this page in the tag editing dialog. +Groups = List of groups appearing on this page. (Core, I18n) + +[Extra rules] - Some rules not fitted in other places. +BooleanAttributes = (simple|complex) +Example for simple: <tag booleanAttr>. +Example for complex: <tag booleanAttr="1"> or <tag booleanAttr="true"> +Single Tag Style = (html|XML) +Example for html: <single_tag> +Example for XML: <single_tag /> +StructGroupsCount = The number of structure groups. See below. +MinusAllowedInWords = If true "this-is-a-word" is treated like a word. Otherwise, +it is treated like 4 words. +TagAutoCompleteAfter = CHAR. The auto-completion box is brought up automatically +once this CHAR is entered or SPACE is pressed after this CHAR. For DTEP family 1, +it is usually "<" The text "none" instead of a CHAR specifies that the tag +completion box should not be brought up automatically, only if the user requests it. +AttributeSeparator = CHAR. This CHAR means that the attribute name has ended. +It is " for XML DTEPs. +TagSeparator = CHAR. Similar to the above. + +[StructGroup_1] - Definition of structure group 1. +Name = The text that appears if there are tags matching this group settings. +No_Name = The text that appears if there are NO tags matching this group settings. +Icon = The name of the icon appearing before the above texts. +Tag = tagname(attribute1, attribute2, ...). Tags with name tagname will appear +under this group. The item text will be "attribute1_value | attribute2_value | ..." +Currently only one tag may be listed here. +HasFileName = (true|false) True, if the item text (above attribute values) contains a file name. +FileNameRx = Regular expression used to remove the unnecessary chars from the item text. + +[Parsing rules] - Rules used when parsing the document. +SpecialAreas = The beginning and ending string of special areas, separatted by a comma. +Special areas are not parsed according to this DTEP's rules, but as their own rules. +A special area can be a DTEP of another family, a comment, or something to that effect. +Eg. <!-- --> +SpecialAreaNames = Comma separated list of the above special area names. Eg. comment +SpecialTags = tagname(attributename) - Specifies a tag which defines the start of a special area. +MayContain = Comma separated list of family 2 DTEPs that can be present in the document. +(php, css) +</markup> +</literallayout> +</informalexample> +</sect3> + +<sect3 id="family-two-structure-3-2"> +<title>Family 2 Structure</title> + +<informalexample> +<literallayout> +<markup> +[General] - Generic information. +Version = Use 1 for &quantaplus; version <=3.1.2 and 2 for any version greater. +Name = Proper name +NickName = What every calls it. If not defined, Name is used as NickName. +Inherits = The name of the DTEP from where this DTEP inherits tags. (The Name, not NickName) +DefaultExtension = New files are created with this extension. (php) +NumOfPages = 0 Always zero because there is not a tag editing dialog for +Family 2 DTEPs. +CaseSensitive = Case-sensitiveness of the DTEP. (true|false) +Family = 2This type of DTEP is of family 2, since it is not markup. + +[Toolbars] - Information about DTEP toolbars. +Location = The folder name inside $KDEDIR($KDEHOME)/share/apps/quanta/toolbars +where the toolbars for this DTEP are. +Names = The list of toolbar file names, minus the .toolbar.tgz extension, that +are loaded for this DTEP from the above folder. + +[Extra rules] - Some rules not fitted in other places. +BooleanAttributes = (simple|complex) +Example for simple: <tag booleanAttr>. +Example for complex: <tag booleanAttr="1"> or <tag booleanAttr="true"> +StructGroupsCount = The number of structure groups. See below. +MinusAllowedInWords = If true "this-is-a-word" is treated like a word. Otherwise, +it is treated like 4 words. +TagAutoCompleteAfter = CHAR. The auto-completion box is brought up automatically +once this CHAR is entered or SPACE is pressed after this CHAR. For DTEP family 1, +it is usually "<" The text "none" instead of a CHAR specifies that the tag +completion box should not be brought up automatically, only if the user requests it. +AttributeSeparator = CHAR. This CHAR means that the attribute name has ended. +It is " for XML DTEPs. +TagSeparator = CHAR. Similar to the above. +AttributeAutoCompletionAfter = CHAR. Similar to the TagAutoCompletionAfter, but +for tag attributes. It is "(" by default and ":" for CSS. + +[StructGroup_1] - Definition of structure group 1. +Name = The text that appears if there are tags matching this group settings. +No_Name = The text that appears if there are NO tags matching this group settings. +Icon = The name of the icon appearing before the above texts. +Tag = tagname(attribute1, attribute2, ...). Tags with name tagname will appear +under this group. The item text will be "attribute1_value | attribute2_value | ..." +Currently only one tag may be listed here. +HasFileName = (true|false) True, if the item text (above attribute values) contains a file name. +FileNameRx = Regular expression used to remove the unnecessary chars from the item text. +SearchRx = regular expression used to find text areas in the Family 2 DTEP, which +will belong to this group +ClearRx = regular expression used to clear unwanted text/chars from the above +search result. The cleaned string will appear in the structure tree. + +[Parsing rules] - Rules used when parsing the document. +SpecialAreas = The beginning and ending string of special areas, separated by a comma. +Special areas are not parsed according to this DTEP's rules, but as their own rules. +A special area can be a DTEP of another family, a comment, or something to that effect. +Eg. <!-- --> +SpecialAreaNames = Comma separated list of the above special area names. Eg. comment +SpecialTags = tagname(attributename) - Specifies a tag which defines the start of a special area. +AreaBorders = Comma separated list of the area borders encapsulating this Family 2 DTEP. In the +case of PHP, it is: <? ?>, <* *>, <% %> +Tags = tagname(attribute). If the parent(real) DTD has a tag with tagname and +the attribute value of this tag is equal with the DTD name, the tag area +is parsed according to the rules of this DTD. +Comments = comma separated list of area borders for comments. EOL means end-of-line. +Eg: // EOL, /* */ +StructKeywords = Semicolon separated list of structure keywords. Structures are treated +as new nodes in the structure tree. +StructBeginStr = A string specifying the beginning of a structure (like {) +StructEndStr = A string specifying the beginning of a structure (like }) +StructRx = Regular expression containing the beginning or the end of the structure +area. Eg. \\{ | \\} (structure area border can be { or }) +</markup> +</literallayout> +</informalexample> +</sect3> +</sect2> +</sect1> + +<sect1 id="creating-toolbars-3-2"> +<title>Creating Toolbars</title> + +<para> +The following will show you how to create toolbars for a &DTEP;. Toolbars +are graphical elements that are assigned to actions. Actions, in +&quantaplus;, are the basis for nearly all the extensions that +&quantaplus; has and will acquire in the future. The same mechanism that +defines an action in &quantaplus; also enables auto-completion and tag +dialogs. With actions, the limit of what you can do is virtually +limitless. For means of an example, we will use <ulink +url="http://tidy.sf.net">&HTML; tidy</ulink> on our web pages. +</para> + +<sect2 id="from-scratch-to-complete-3-2"> +<title>From Scratch to Complete</title> + +<para> +To begin, you will need to create a user toolbar. Select +<menuchoice> +<guimenu>Toolbars</guimenu> +<guimenuitem>Add User Toolbar</guimenuitem> +</menuchoice>. +</para> + +<para> +If there are many tags for the markup language, it is recommended that you +split up the tags into logical groups. You will need to create a new user +toolbar for each group. In this case, there are not many, so we will be +making one toolbar and naming it with the name of the markup. +</para> + +<para> +Once all your toolbars are created, you must add and configure the +actions. To do this, select +<menuchoice> +<guimenu>Settings</guimenu> +<guimenuitem>Configure Actions</guimenuitem> +</menuchoice> +<emphasis> +</emphasis>. +</para> + +<para> +The parts of this window are pretty straight forward. Press the +<guibutton>New action</guibutton> button at the bottom of the window to +enter the editing mode. +</para> + +<para> +Fill in all of the necessary fields and add the tag to the appropriate +toolbar(s). +</para> + +<para> +Complete the rest and, if the tag has attributes and you always plan to +use them, check the <guilabel>Run "Edit tag" dialog if available +</guilabel> box so that you will be prompted every time the action is used. +</para> + +<para> +You should now have something much like the following. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img7.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Press the <guibutton>Apply</guibutton> button and you will see the action +added to the toolbar(s) you have selected. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img8.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Egad! That's an awful icon. How will yourself and others remember that +icon goes with that action? Let's replace it before trouble arises. +</para> + +<para> +To create an icon that more accurately describes that action, we will be +using &kiconedit;. Select it from the &menuk;, <menuchoice> +<guisubmenu>Graphics</guisubmenu> +<guisubmenu>More Programs</guisubmenu> +</menuchoice> (or where ever your distribution placed it). +</para> + +<para> +&kiconedit; defaults to the size 32x32 pixels, but we need 22x22. To +change this, select +<menuchoice> +<guimenu>Edit</guimenu> +<guimenuitem>Resize</guimenuitem> +</menuchoice>. +</para> + +<para> +Keep in mind that you are creating an icon that will assist in helping not +only yourself to remember which action does what, but also other users of +the &DTEP;. +</para> + +<para> +Since the tag I am creating the icon for is called <quote>start,</quote> +I have decided to create a <quote>Start sign.</quote> Using the color green +(green often interpreted as <quote>go,</quote> <quote>start,</quote> or +<quote>proceed</quote>) will, or, at least, should, convey a message +to the user that clicking this action will place the <start> tag in the +current document. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img15.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Now that I am finished with the creation of the icon, I will save it. +</para> + +<para> +Once you are done with creating the icon(s), you must associate the icon +with the action. To do this, open +<menuchoice> +<guimenu>Settings</guimenu> +<guimenuitem>Configure Actions</guimenuitem> +</menuchoice> again (in &quantaplus;) and select the action you made +the icon for. Beside the <guilabel>Text</guilabel> field, you will see a +button, click it. +</para> + +<para> +Select <guilabel>Other Icons</guilabel> and then click the <guibutton> +Browse</guibutton> button. +</para> + +<para> +Goto the folder in which you saved the icon, select the icon, and click +<guibutton>OK</guibutton>. +</para> + +<para> +Press the <guibutton>Apply</guibutton> button and either continue to do the +same with the other tags, if any, or click <guibutton>OK</guibutton> to +finish. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img18.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Let us say you would like to add some common &quantaplus; functions to your +toolbar or maybe you think the toolbar would be better off organized in a +different manner with some separators to group the actions. Open the +<guilabel>Configure Toolbars</guilabel> dialog by going +<menuchoice> +<guimenu>Settings</guimenu> +<guimenuitem>Configure Toolbars</guimenuitem> +</menuchoice>. Make sure your toolbar is selected. +</para> + +<para> +I will be choosing the separator (top of the left column) for my toolbar. +Once you have selected the item you wish to add to your toolbar, press the +right arrow button. This will add it to your toolbar. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img21.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +I think I would like a quick way to access the <guilabel>Konqueror +Preview</guilabel>. I will select it and add it to the toolbar. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img22.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Note how the separator helps in grouping. Someone new to my toolbar might +have thought that the &konqueror; button was like or the opposite of the +start button. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img23.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Apply your changes and, when you are done, press <guibutton>OK</guibutton> +to finish. +</para> + +<para> +Ah, look at the fantastic new toolbar! Much more handy now. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img24.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Remember to test your toolbar, by clicking all the buttons, so that you +know the output is correct. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="dtep_doc_img25.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Now to save the toolbar, we will select +<menuchoice> +<guimenu>Toolbars</guimenu> +<guisubmenu>Save Toolbars</guisubmenu> +<guimenuitem>Save as Local Toolbar</guimenuitem> +</menuchoice>. +</para> + +<para> +Save it to the correct folder. Since NeXML does not exist, I will just +have it to the top-level folder, but your toolbar(s) should be saved to +the correct folder. Make sure to adjust your description.rc to have it +load your toolbar(s) when a new file of that type is created. +</para> +</sect2> +</sect1> + + +<sect1 id="creating-quanta-docs-3-2"> +<sect1info> +<title>Creating Your Own Documentation</title> +<authorgroup> +<author> +<firstname>Robert</firstname> +<surname>Nickel</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +</author> + +<!-- TRANS:ROLES_OF_TRANSLATORS --> + +</authorgroup> +</sect1info> + +<title>Creating Your Own Documentation</title> + +<para> +Probably the most notable additions to &quantaplus; for the general user +will be the addition of documentation for the markup or scripting language +that you like best. To that end, this chapter will explain how I create +the &PHP; documentation tree for my personal use. +</para> + +<para> +Before starting on creating your own documentation, you may wish to check +out the <ulink url="http://quanta.sf.net/main1.php?contfile=resource"> +&quantaplus; repository</ulink> to see if someone else has already done +this set. +</para> + +<para> +There are two parts to this process. First, you must obtain the existing +documentation for the markup/scripting/&etc; language that you are after. +Second, you have to create the <filename>docrc</filename> file. The first +is up to you, the second is what we will cover here. +</para> + +<para> +The general form of the docrc file is as follows: +</para> + +<informalexample> +<literallayout> +#KDE Config File +[Tree] +Doc dir=<replaceable>path, relative to this file, of the documentation html files</replaceable> &pex; php42/ +#top level elements +Top Element=<replaceable>Your description for these documentation</replaceable> &pex; &PHP; 4.2 documentation + +Section 1=Section1.html +Section 2=#Sec2.1,#Sec2.2,#Sec2.3 +Sec2.1=Sec2.1.html +Sec2.2=Sec2.2.html +Sec2.3=Sec2.3.html +... + +[Context] +ContextList=func1,func2,tag1,tag2,tag3 +func1=func1.html +func2=func2.html +tag1=tag1.html +tag2=tag2.html +tag3=tag3.html +</literallayout> +</informalexample> + +<para> +The <filename>docrc</filename> is broken down into two sections: Tree and +Context. +</para> + +<para> +The Tree section defines the presentation aspect of the documentation in +the documentation tab. For example, you will see that in the &PHP; +documentation you have something akin to this: +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="doc-view1.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +Relating this to the above, my &PHP; <filename>docrc</filename> looks like +this: +</para> + +<informalexample> +<literallayout> +#KDE Config File + +[Tree] + +Doc dir=php42/ + +#top level elements +Top Element=PHP 4.2 documentation + +PHP 4.2 documentation=Table of Contents,#Getting Started,#Language Reference + +Table of Contents=index.html + +Getting Started=Introduction, ... +Introduction=introduction.html +... + +Language Reference=Basic syntax, ... +Basic syntax=language.basic-syntax.html +... + +</literallayout> +</informalexample> + +<para> +Notice the <literal>#</literal> in front of <quote>Getting Started</quote> +and <quote>Language Reference</quote>. This indicates that these are sub +containers in the tree and have content of their own. I do not believe that +there is a set limit to the depth here (other than that driven by sanity) +— use your judgment. +</para> + +<para> +For the Table of Contents, you will notice that it is referenced directly to +a file (and consequently shows up at the bottom of the tree view — +folders first!). +</para> + +<important> +<para> +Spaces do not adversely affect anything, but watch out for & and < +characters. These should likely be replaced by &amp; and &lt; +respectively in all of the &XML; based &quantaplus; resource files. +</para> +</important> + +<para> +The Context section is the section of the docrc file that is used to +facilitate context sensitive help. For example, you are writing a &PHP; +script and you would like to see the documentation for the +<function>mysql_fetch_array</function> function. You simply highlight the +function and then press <keycombo action="simul">&Ctrl;<keycap>H</keycap> +</keycombo> for context help. The documentation on +<function>mysql_fetch_array</function> will immediately display. There are +only two entry types here: the ContextList and the file association lines. +</para> + +<variablelist> +<varlistentry> +<term>ContextList</term> +<listitem> +<para> +Really simple, this is just a comma separated list of the context items +you wish to have available (for &PHP;, these are the functions for &PHP;). +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>File association lines</term> +<listitem> +<para> +These are of the form context item=html doc page. &pex; +acos=function.acos.html +</para> +</listitem> +</varlistentry> +</variablelist> + +<para> +A pared down version of my <filename>docrc</filename> Context section is +as follows: +</para> + +<informalexample> +<literallayout> +#Keywords for context help +[Context] +ContextList=abs,acos,acosh,addcslashes,addslashes,... + +abs=function.abs.html +acos=function.acos.html +acosh=function.acosh.html +addcslashes=function.addcslashes.html +addslashes=function.addslashes.html +... +</literallayout> +</informalexample> + +<para> +Now you can just save your <filename>docrc</filename> file, save it in +<filename class="directory">$<envar>HOME</envar>/.kde/share/apps/quanta/doc</filename> +or <filename class="directory">$<envar>KDEDIR</envar>/share/apps/quatna/doc</filename> +for local or global use respectively. Then create a folder (the one +specified in your <filename>docrc</filename> file) in the same folder +as your <filename>docrc</filename> file and copy your &HTML; pages in +there. +</para> + +<para> +You will need to restart &quantaplus; to see your documentation. +</para> + +<para> +Once you are sure that they are good and worth sharing, send the <filename> +docrc</filename> file along with a description of any pertinent +information on what documentation you used to the +<ulink url="http://quanta.sf.net/main1.php?contfile=resource">&quantaplus; +repository</ulink> for use by the &quantaplus; community. You will not get +rich, but you will feel great knowing that you contributed to the best web +development platform around. +</para> + +</sect1> +</chapter> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/fundamentals.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/fundamentals.docbook new file mode 100644 index 00000000000..65038145f67 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/fundamentals.docbook @@ -0,0 +1,371 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="fundamentals-3-2"> +<chapterinfo> +<title>The Fundamentals of &quantaplus;</title> +<authorgroup> +<author> +<firstname>Robert</firstname> +<surname>Nickel</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +</author> + +<othercredit role="reviewer"> +<firstname>Christopher</firstname> +<surname>Hornbaker</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +<contrib>Reviewer</contrib> +</othercredit> + +<othercredit role="reviewer"> +<firstname>Fabrice</firstname> +<surname>Mous</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +<contrib>Reviewer</contrib> +</othercredit> + +<!-- TRANS:ROLES_OF_TRANSLATORS --> + +</authorgroup> +</chapterinfo> + +<title>The Fundamentals of &quantaplus;</title> + +<para> +Within &quantaplus; there are serveral key concepts. To understand and +take advantage of &quantaplus;, you must first learn these concepts, the +fundamentals. This chapter will explain and show you these concepts, without +which &quantaplus; would be primative. +</para> + +<sect1 id="quanta-workspaces-3-2"> +<title>The Workspace</title> + +<para> +&quantaplus; divides the workspace into three scopes: Global, Local, and +Project. These distinctions affect various components in &quantaplus;. +</para> + +<variablelist> +<varlistentry> +<term>Global</term> +<listitem> +<para> +Global items are available to anyone that uses &quantaplus;. From toolbars +to actions, everything marked as global is stored in the common +&quantaplus; folder structure. This has the effect of allowing a group +of admins to save certain toolbars, actions, and templates in the global +tree, which can then be used to keep a multi-user installation of +&quantaplus; common to everyone on the system. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term>Local</term> +<listitem> +<para> +Local items make up a single user's personal collection of web development +resources. These items are made up of a user's templates and toolbars. +Local items are stored in a user's home folder. This makes all of the +user's Local items available for personal use at instance. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term>Project</term> +<listitem> +<para> +Project items are are only available to a particular project. These can +be anything from a &CSS; template to a toolbar with custom actions +which perform a special task on a project's files. Simply put, this is +the most limited scope. All of the items saved in the project workspace +will be saved in the project's folder tree, allowing you to share your +specialized tools and templates with whomever else you share your +project with. +</para> +</listitem> +</varlistentry> +</variablelist> + +</sect1> + +<sect1 id="mdi-interface-3-2"> +<title>The Multi-Document Interface</title> + +<mediaobject> +<imageobject> +<imagedata fileref="quantamdi.png" format="PNG" /> +</imageobject> +<caption><para>&quantaplus; editing the document you are now reading.</para></caption> +</mediaobject> + +<para> +&quantaplus;' &MDI; is broken down to three main parts: the editor window, +the Quick Info Tabs, and the toolbars. Please see <xref linkend="editor-3-2" />, +<xref linkend="qit-3-2" />, and <xref linkend="toolbars-3-2" /> for more +information on these parts. +</para> + +<sect2 id="editor-3-2"> +<title>The Editor Window</title> + +<para> +<mediaobject> +<imageobject> +<imagedata fileref="quantamdi-editor.png" format="PNG" /> +</imageobject> +<caption><para>&quantaplus;' editor window.</para></caption> +</mediaobject> +</para> + +<para> +&quantaplus;' editor window allows for multiple files to be opened at the +same time. When just one file is open, the document fills the entire +editor window. As soon as a second document is opened, a small amount of +space is taken from the bottom of the editor window to allow for tabs to +be displayed with the filenames and a status icon. (The above picture shows +a <guiicon>floppy</guiicon> icon beside the filename, indicating that the +file has been modified and should be saved.) +</para> + +<para> +At the top of the editor window is the editor toolbar set. Currently, +&quantaplus; defaults to &HTML; 4.01 Transitional, which has a default set +of toolbars that are loaded. As &quantaplus; progresses, the toolbars will +be updated to meet the needs of users and to make use of newer features. +</para> + +<para> +Toolbar usage is pretty straight forward. If you want to insert a basic +tag, like <u>, into your document, then you can click on the icon that +represents the tag. Now you can insert your data for the tag you have just +inserted. If you wish to insert a tag that requires certain attributes +(like an anchor), then you will get a dialog box with the various fields for +you to fill in. + +<mediaobject> +<imageobject> +<imagedata fileref="taginputex.png" format="PNG" /> +</imageobject> +<caption><para>The anchor (<a>) dialog.</para></caption> +</mediaobject> +</para> +</sect2> + +<sect2 id="qit-3-2"> +<title>The Quick Info Trees</title> + +<mediaobject> +<imageobject> +<imagedata fileref="quantamdi-treeview.png" format="PNG" /> +</imageobject> +<caption><para>The Quick Info Trees.</para></caption> +</mediaobject> + +<para> +The Quick Info Trees (&QIT;) allow you to navigate, open, and gather +information in &quantaplus;. Its tabbed format presents you with the Files, Project, +Templates, Document Structure, Scripts, Attribute, and Documentation Trees. +</para> + +<variablelist id="qit-parts"> +<title>&QIT; Explained</title> + +<varlistentry> +<term> +Files Tree +<inlinemediaobject> +<imageobject> +<imagedata fileref="ftab.png" format="PNG" /> +</imageobject> +</inlinemediaobject> +</term> +<listitem> +<para> +This is where you can browse your entire file system. You are presented +with two top-level roots of the file system. The first is your home folder +and the second is /. Use these to find existing files on your machine that +you would like to edit or add to an active project. &BDS; clicking on a file +in this view gives you several options for managing the selected file and, +also, allows you to insert the file into an active project, if any, or +toggle the view between tree and list. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term>Project Tree +<inlinemediaobject> +<imageobject> +<imagedata fileref="ptab.png" format="PNG" /> +</imageobject> +</inlinemediaobject> +</term> +<listitem> +<para> +<link linkend="quanta-projects-3-2">Project management</link> is one of the +many powerful tools that &quantaplus; offers. This tab displays all files +within your project and allows you to manage the files within the project +through the use of &BDS; clicking. Actions, such as add, remove, upload, +or delete files entirely from the disk, can be performed through this menu. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term>Templates Tree +<inlinemediaobject> +<imageobject> +<imagedata fileref="ttab.png" format="PNG" /> +</imageobject> +</inlinemediaobject> +</term> +<listitem> +<para> +Another feature of &quantaplus; is templates. Templates can be anything +you would like. Images, code snippets, an entire web page, et cetera. It +is entirely up to you. +</para> + +<para> +Templates are sorted into three categories, which are based on their scope +and the context they are being used. These scopes are carried over from +&quantaplus;' workspace. Global templates are usable all times, local +templates are usable to the current user, and project templates +are usable only within their specified project. More on templates can be +found in <xref linkend="templates-3-2" />. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term>Scripts Tree +<inlinemediaobject> +<imageobject> +<imagedata fileref="exec.png" format="PNG" /> +</imageobject> +</inlinemediaobject> +</term> +<listitem> +<para> +Here you will find information about the various scripts available for use +by you. The Global, Local, and Project concept allows here as well. By +&BGS; clicking the entries, you gain access to all the available +information about the script. And &BDS; clicking allows you to perform a +few actions, such as running the script, editing the script, and emailing +the script, for example. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term>Document Structure Tree +<inlinemediaobject> +<imageobject> +<imagedata fileref="view_sidetree.png" format="PNG" /> +</imageobject> +</inlinemediaobject> +</term> +<listitem> +<para> +This tab displays the parser's internal representation of your document. +By &BGS; clicking on a element, your cursor will taken to the element's +position in the document. By &BDS; clicking on an element, you are +presented with a number of actions that deal with navigating and updating +the tree. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term>Attribute Tree +<inlinemediaobject> +<imageobject> +<imagedata fileref="tag_misc.png" format="PNG" /> +</imageobject> +</inlinemediaobject> +</term> +<listitem> +<para> +This tree appears below all the other &QIT;s. Within it you can quickly +edit attributes and namespaces. The content-focused entry system +allows you to modify all the available attributes with little more than a +few clicks of the mouse. +<mediaobject> +<imageobject> +<imagedata fileref="attribute_tree.png" format="PNG" /> +</imageobject> +<caption><para>Attribute Tree</para></caption> +</mediaobject> +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term>Documentation Tree +<inlinemediaobject> +<imageobject> +<imagedata fileref="contents2.png" format="PNG" /> +</imageobject> +</inlinemediaobject> +</term> +<listitem> +<para> +Here you can find complete documentation on web technologies to aid your +development. You can download pre-packaged documentation for &quantaplus; +at <ulink url="http://quanta.sourceforge.net/docs.html">&quantaplus;' +documentation site</ulink>, you can <link +linkend="creating-quanta-docs-3-2">create your own documentation</link>, +and, by adding a folder named "doc" to a project, you can add, edit, +and view project-specific documentation. +</para> +</listitem> +</varlistentry> +</variablelist> +</sect2> + +<sect2 id="toolbars-3-2"> +<title>The Toolbars</title> + +<mediaobject> +<imageobject> +<imagedata fileref="toolbars.png" format="PNG" /> +</imageobject> +<caption><para>&quantaplus;' &HTML; toolbars.</para></caption> +</mediaobject> + +<para> +&quantaplus;' toolbars have been extended greatly and are easy to +understand. You click on the button and you get an associated action from +that button. The beautiful part about toolbars is that you can define your +own actions graphically within &quantaplus;. +</para> + +<para> +Managing toolbars in &quantaplus; is easy. By selecting the <guimenu> +Toolbars</guimenu> menu, you have the options to load, save, add, and +email toolbars. When you choose to load a toolbar, you may choose from one +of the three <link linkend="quanta-workspaces-3-2">workspaces</link> in +&quantaplus;. When saving a newly created toolbar, you can save it in the +local scope or within a project's scope. If you would like to make a new +toolbar available in the global scope, ask your admin to place it in +&quantaplus;' global toolbar folder. +</para> + +<para> +Another feature of &quantaplus; is the ability to email your toolbars. +&quantaplus; sends the toolbar as a gzipped tar archive through &kmail;. +If you receive a toolbar in email, then you can save (and load) it into +&quantaplus; like any other toolbar! +</para> +</sect2> +</sect1> +</chapter> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/glossary.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/glossary.docbook new file mode 100644 index 00000000000..bc1839c9f9a --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/glossary.docbook @@ -0,0 +1,76 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<glossary id="quanta-glossary-3-2"> + +<glossaryinfo> +<authorgroup> +<author +><firstname +>Keith</firstname +> <surname +>Isdale</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +<othercredit role="reviewer" +><firstname +>Christopher</firstname +> <surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Relecteur</contrib> +</othercredit> + +&traducteurGoneriLeBouder; + +</authorgroup> +</glossaryinfo> + +<glossdiv> +<title +>Mots clefs</title> +<glossentry id="xsldbg-glosref"> +<glossterm +>xsldbg</glossterm> +<glossdef> +<para +>Consultez <ulink url="http://xsldbg.sourceforge.net" +></ulink +></para> +</glossdef> +</glossentry> +<glossentry> +<glossterm +>XPath</glossterm> +<glossdef> +<para +>Une expression valide qui définit quel type d'information est requis. Consultez <ulink url="http://www.w3.org" +>le site du &W3C;</ulink +> </para> +</glossdef> +</glossentry> +<glossentry> +<glossterm +>QName</glossterm> +<glossdef> +<para +>Un nom pleinement qualifié. Par exemple <emphasis +>xsl:mavariable</emphasis +>. Consultez le <ulink url="http://www.w3.org" +>site du &W3C;</ulink +> </para> +</glossdef> +</glossentry> +</glossdiv> +</glossary> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/index.cache.bz2 b/tde-i18n-fr/docs/tdewebdev/quanta/index.cache.bz2 Binary files differnew file mode 100644 index 00000000000..109be56d231 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/index.cache.bz2 diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/index.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/index.docbook new file mode 100644 index 00000000000..e36f67e34a0 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/index.docbook @@ -0,0 +1,294 @@ +<?xml version="1.0" encoding="UTF-8" ?> +<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [ + <!ENTITY package "tdewebdev"> + <!ENTITY advanced-quanta SYSTEM "adv-quanta.docbook"> + <!ENTITY config-quanta SYSTEM "config-quanta.docbook"> + <!ENTITY credits-license SYSTEM "credits-license.docbook"> + <!ENTITY debugging-quanta SYSTEM "debugging-quanta.docbook"> + <!ENTITY extending-quanta SYSTEM "extending-quanta.docbook"> + <!ENTITY fundamentals SYSTEM "fundamentals.docbook"> + <!ENTITY glossary SYSTEM "glossary.docbook"> + <!ENTITY installation SYSTEM "installation.docbook"> + <!ENTITY introduction SYSTEM "introduction.docbook"> + <!ENTITY q-and-a SYSTEM "q-and-a.docbook"> + <!ENTITY quanta-menus SYSTEM "quanta-menus.docbook"> + <!ENTITY quanta-projects SYSTEM "quanta-projects.docbook"> + <!ENTITY working-with-quanta SYSTEM "working-with-quanta.docbook"> + <!ENTITY CGI "<acronym +>CGI</acronym +>"> + <!ENTITY DTD "<acronym +>DTD</acronym +>"> + <!ENTITY DTEP "<acronym +>DTEP</acronym +>"> + <!ENTITY HTML "<acronym +>HTML</acronym +>"> + <!ENTITY IDE "<acronym +>IDE</acronym +>"> + <!ENTITY PHP "<acronym +>PHP</acronym +>"> + <!ENTITY PDF "<acronym +>PDF</acronym +>"> + <!ENTITY SGML "<acronym +>SGML</acronym +>"> + <!ENTITY XSD "<acronym +>XSD</acronym +>"> + <!ENTITY W3C '<trademark class="registered" +>W3C</trademark +>'> + <!ENTITY QIT "<acronym +>QIT</acronym +>"> + <!ENTITY MDI "<acronym +>MDI</acronym +>"> + <!ENTITY gubed "<application +>Gubed PHP Debugger</application +>"> + <!ENTITY kxsl "<application +>KXsldbg</application +>"> + <!ENTITY VPL "<acronym +>VPL</acronym +>"> + <!ENTITY % addindex "IGNORE"> + <!ENTITY % French "INCLUDE"> + <!ENTITY descriptionrc '<link linkend="descriptionrc-3-2" +>description.rc</link +>'> +]> + +<book lang="&language;"> +<title +>Manuel de l'utilisateur de &quantaplus;</title> + +<bookinfo> + +<authorgroup> + +<author +><firstname +>Christopher</firstname +><surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +<author +><firstname +>Fabrice</firstname +><surname +>Mous</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +<author +><firstname +>Robert</firstname +><surname +>Nickel</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +<author +><firstname +>András</firstname +> <surname +>Mantia</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +<othercredit role="developer" +><firstname +>Eric</firstname +><surname +>Laffoon</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Développeur</contrib> +</othercredit> + +<othercredit role="developer" +><firstname +>András</firstname +> <surname +>Mantia</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Développeur</contrib> +</othercredit> + +<othercredit role="developer" +><firstname +>Dmitry</firstname +><surname +>Poplavsky</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Développeur jusqu'à la version 2.0</contrib> +</othercredit> + +<othercredit role="developer" +><firstname +>Alexander</firstname +><surname +>Yackovlev</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Développeur jusqu'à la version 2.0</contrib> +</othercredit> + +&traducteurEquipeKDE; + +</authorgroup> + +<copyright> +<year +>2002</year +><year +>2003</year +><year +>2004</year +><year +>2005</year> +<holder +>équipe de développement de &quantaplus;</holder> +</copyright> + +<legalnotice> +<para +>&FDLNotice; </para> +</legalnotice> + +<date +>2005-08-24</date> +<releaseinfo +>3.4.90</releaseinfo> + +<abstract> +<para +>&quantaplus; est &IDE; WEB qui s'efforce d'être neutre et transparent à tous les langages de balises alors qu'il gère les langages de script populaires basés sur le web, &CSS;, ainsi que des autres recommandations émergentes du &W3C;. </para> +</abstract> + +<keywordset> +<keyword +>KDE</keyword> +<keyword +>Quanta</keyword> +<keyword +>texte</keyword> +<keyword +>éditeur</keyword> +<keyword +>Web</keyword> +<keyword +>programmeur</keyword> +<keyword +>programmation</keyword> +<keyword +>Développement</keyword> +<keyword +>Commandeur</keyword> +<keyword +>xsldbg</keyword> +<keyword +>libxslt</keyword> +<keyword +>débogueur</keyword> +<keyword +>projets</keyword> +<keyword +>SGML</keyword> +<keyword +>JSS</keyword> +<keyword +>DTD</keyword> +<keyword +>XML</keyword> +<keyword +>XSD</keyword> +<keyword +>W3C</keyword> +<keyword +>CSS</keyword> +<keyword +>Schéma</keyword> +<keyword +>Livre de documentation</keyword> +<keyword +>HTML</keyword> +<keyword +>XHTML</keyword> +<keyword +>CGI</keyword> +<keyword +>PHP</keyword> +<keyword +>Java</keyword> +<keyword +>JavaScript</keyword> +<keyword +>ColdFusion</keyword> +</keywordset> +</bookinfo> +&introduction; +&fundamentals; +&working-with-quanta; +<!-- &config-quanta; --> +&quanta-menus; +&config-quanta; +&advanced-quanta; +&extending-quanta; +&q-and-a; +&credits-license; +&installation; +&glossary; +</book> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/installation.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/installation.docbook new file mode 100644 index 00000000000..1474b8eee98 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/installation.docbook @@ -0,0 +1,41 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<appendix id="installation-3-2"> +<title +>Installation</title> + +<sect1 id="acquiring-qunata-3-2"> +<title +>Acquérir &quantaplus;</title> +&install.intro.documentation; </sect1> + +<sect1 id="source-code-building-3-2"> +<title +>Construire le source</title> +&install.compile.documentation; <sect2 id="source-code-building-considerations-3-2"> +<title +>Considérations lors de la construction</title> + +<para +>Il est raisonnable que vous souhaitiez personnaliser l'emplacement des fichiers de &quantaplus; sur votre système. À cette fin, <command +>autoconf</command +> possède de nombreuses options qui peuvent être passées au script <command +>configure</command +> pour contrôler cette installation. Pour obtenir une liste complète de ces options, saisissez <command +>./configure</command +><option +> --help</option +>. Ces options sont évidentes et ne seront pas couvertes ici. </para> + +<para +>Si vous avez des difficultés pour faire fonctionner &quantaplus; correctement, vous devez vérifier votre chemin pour vous assurer que le dossier <filename class="directory" +>bin</filename +> de &kde; 3 est présent. Soyez également sûr qu'il n'y a pas d'anciennes versions de &kde; qui apparaissent dans le <envar +>PATH</envar +> avant votre dossier <filename class="directory" +>bin</filename +> de &kde;3. Ceci s'applique pareillement à &Qt;. </para> + +</sect2> +</sect1> +</appendix> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/introduction.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/introduction.docbook new file mode 100644 index 00000000000..f57b33e69ad --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/introduction.docbook @@ -0,0 +1,137 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="introduction-3-2"> +<title +>Introduction</title> + +<sect1 id="what-is-quanta-3-2" +><sect1info +> <title +>Qu'est-ce qu'est &quantaplus; ?</title +> <authorgroup +> <author +> <firstname +>Eric</firstname +> <surname +>Laffoon</surname +> <affiliation +> <address +><email +>[email protected]</email +></address +> </affiliation +> </author +> <othercredit role="reviewer" +> <firstname +>Christopher</firstname +> <surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address +> </affiliation +> <contrib +>Reviewer</contrib +> </othercredit +> <othercredit role="reviewer" +> <firstname +>Fabrice</firstname +> <surname +>Mous</surname +> <affiliation +> <address +><email +>[email protected]</email +></address +> </affiliation +> <contrib +>Reviewer</contrib +> </othercredit +> &traducteurGoneriLeBouder; </authorgroup +> </sect1info +> <title +>Qu'est-ce qu'est &quantaplus; ?</title +> <blockquote +> <attribution +> Eric Laffoon de http://quanta.sourceforge.net </attribution +> <para +> &quantaplus; est un outil de développement Web pour l'Environnement de Bureau KDE. &quantaplus; a été conçu pour le développement rapide de site et est vite devenu un éditeur mature avec de nombreuses options avancées. </para +> <para +>Notre objectif est toujours de créer la meilleure application possible pour le développement de site internet. Nous réalisons que nous aurions besoin de l'aide de beaucoup plus de personnes actives pour réaliser cela, donc actuellement nous travaillons pour que les développeurs de sites Internet puissent personnaliser, étendre et améliorer &quantaplus;. Ainsi nous vous demanderons à vous, les développeurs de sites, de contribuer aux amélioration. Nous allons organiser cela afin que les développeurs utilisant l'outil de développement &quantaplus; puissent trouver les ressources, les extensions ainsi que les modules optimisés dont ils ont besoin pour être les développeurs les plus rapide possibles.</para +> </blockquote +> </sect1> + +<sect1 id="quanta-intro-3-2"> +<sect1info> +<title +>&quantaplus; : où il était et où il va</title> +<authorgroup> +<author +><firstname +>Robert</firstname +> <surname +>Nickel</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +<othercredit role="reviewer" +><firstname +>Christopher</firstname +> <surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Relecteur</contrib> +</othercredit> + +<othercredit role="reviewer" +><firstname +>Fabrice</firstname +> <surname +>Mous</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Relecteur</contrib> +</othercredit> + +&traducteurGoneriLeBouder; + +</authorgroup> +</sect1info> + +<title +>&quantaplus; : où il était et où il va</title> + +<para +>Alors qu'ils s'efforçaient d'avoir le meilleur éditeur &HTML; possible, les développeurs de &quantaplus; commencèrent a penser à une idée plus intéressante : « Et si &quantaplus; devenait un éditeur générique et extensible pour la majorité des langages ? ». Ainsi cela ferait de lui le plus grand environment de développement Internet pour &kde; ! C'est ce qui a été fait. </para> + +<para +>Désormais non lié au &HTML;, &quantaplus; est maintenant bien parti dans sa voie pour devenir un environment de développement Internet à tout faire. Particulièrement, si vous travaillez en &XML;, &quantaplus; peut vous servir d'environment de développement intégré. </para> + +<para +>Maintenant, comme il est dit au-dessus, il doit être noté que le développement de &quantaplus; est basé sur celui réalisé par l'ensemble de la communauté des développeurs &kde;. &quantaplus;, ainsi que le mouvement Libre, se base sur l'idée suivante : « Pourquoi écrire quelque chose déjà fait ? ». Grâce a l'architecture de &kde;, non seulement, c'est possible, mais cela permet aux utilisateurs et développeurs d'étendre &quantaplus; comme ils l'entendent. </para> + +<para +>&quantaplus; fournit aux développeurs Internet une interface multidocument (&MDI;) puissante et intuitive. Il peut augmenter votre productivité de façon importante. À travers divers actions habituelles, script ou barres outils, vous pouvez automatiser pratiquement toutes les tâches. Avec l'utilisation de <application +> Kommander</application +>, vous pouvez étendre &quantaplus; dans plus jamais avoir à retenir la syntaxe des commandes utilisées dans les scripts (vous trouverez plus d'information sur ce sujet ici <xref linkend="extending-quanta-3-2"/>). </para> +</sect1> + +</chapter> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/q-and-a.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/q-and-a.docbook new file mode 100644 index 00000000000..b2ef55e4ac8 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/q-and-a.docbook @@ -0,0 +1,53 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="faq-3-2"> +<chapterinfo> +<title +>Questions et Réponses</title> +<authorgroup> +<author +><firstname +>Eric</firstname +> <surname +>Laffoon</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +&traducteurGoneriLeBouder; + +</authorgroup> +</chapterinfo> + +<title +>Questions et Réponses</title> + +<qandaset> +<qandaentry> +<question> +<para +>Comment puis-je participer au développement de &quantaplus; ? </para> +</question> +<answer> +<para +>Nous vous rappelons que &quantaplus; est développé par des bénévoles. Beaucoup de personnes pensent qu'elles ne peuvent pas contribuer aux logiciels libres pour une raison ou une autre. La plus courante est probablement le sentiment de ne pas avoir un niveau suffisant. &quantaplus; a été développé de façon à ce que les développeurs et non-développeurs puissent aider à améliorer &quantaplus;.Il y a déjà le problème de la documentation. Les logiciels, qu'ils soient propriétaires ou libres, sont meilleurs s'ils sont bien documentés. Nous sommes sûrs qu'il y a une partie de &quantaplus; pour laquelle le temps que vous y passerez sera le plus bénéfique. </para> +</answer> +</qandaentry> + +<qandaentry> +<question> +<para +>Dans quelle direction avance &quantaplus; ? </para> +</question> +<answer> +<para +>Nous avons publié &quantaplus; 3.2 et sommes actuellement en train de préparer la prochaine version. Notre objectif reste de créer le meilleur environnement de développement pour Internet possible. Nous nous rendons compte que nous allons avoir besoin de bien plus de monde actifs autour de &quantaplus; pour arriver à cela. Nous sommes donc en train de développer des changements afin de rendre plus simple la réalisation d'améliorations et extensions de la part des utilisateurs. Une grosse partie de ce travail a été accomplie dans la version 3.2. Donc nous allons demander à vous, les utilisateurs, de contribuer aux perfectionnements. Nous comptons organiser cela de façon a ce que les utilisateurs de &quantaplus; puissent trouver facilement les ressources, extensions et les modules dont ils ont besoin pour être les développeurs de site Internet les plus performants possible ! </para> +</answer> +</qandaentry> + +</qandaset> +</chapter> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/quanta-menus.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/quanta-menus.docbook new file mode 100644 index 00000000000..595946b7b35 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/quanta-menus.docbook @@ -0,0 +1,2365 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="quantas-menus-3-2"> +<chapterinfo> +<title +>La barre de menu</title> +<authorgroup> +<author +><firstname +>Robert</firstname +> <surname +>Nickel</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> + +<othercredit role="reviewer" +><firstname +>Christopher</firstname +> <surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Relecteur</contrib> +</othercredit> + +<othercredit role="reviewer" +><firstname +>Fabrice</firstname +> <surname +>Mous</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +<contrib +>Relecteur</contrib> +</othercredit> + +&traducteurPatrickMichelon; + +</authorgroup> +</chapterinfo> + +<title +>La barre de menu</title> + +<para +>Ce chapitre explique toutes les diverses fonctions qui peuvent être trouvées dans la barre de menu. </para> + +<sect1 id="file-menu-3-2"> +<title +>Le menu <guimenu +>Fichier</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>N</keycap +></keycombo +> </shortcut +> <guimenu +>Fichier</guimenu +> <guimenuitem +>Nouveau</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Crée un nouveau fichier vide. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>O</keycap +></keycombo +> </shortcut +> <guimenu +>Fichier</guimenu +> <guimenuitem +>Ouvrir...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Recherche dans le système de fichiers pour ouvrir un fichier existant. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Fichier</guimenu +> <guimenuitem +>Récemment ouvert(s)</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Liste les derniers fichiers que vous avez ouverts. Cette liste changera chaque fois que vous ouvrez un fichier qui ne figure pas dessus en éjectant le fichier le plus ancien de la liste en premier. </para> +</listitem> + +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>S</keycap +></keycombo +> </shortcut +> <guimenu +>Fichier</guimenu +> <guimenuitem +>Enregistrer</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Enregistre les modifications du fichier actif. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Fichier</guimenu +> <guimenuitem +>Enregistrer sous...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Enregistre le fichier actif sous un autre nom. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Fichier</guimenu +> <guisubmenu +>Enregistrer en tant que modèle</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Ceci vous permet d'enregistrer des bouts de code et des fichiers entiers comme modèles pour un usage ultérieur. Voir la section <link linkend="templates-3-2" +>modèles</link +>. Si vous essayez d'enregistrer le texte/fichier sauvegardé en dehors du répertoire de modèles local/projet vous recevrez un message d'erreur. </para> +<variablelist> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Fichier</guimenu +> <guisubmenu +>Enregistrer en tant que modèle...</guisubmenu +> <guisubmenu +>Enregistrer en tant que modèle local...</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Vous permet d'enregistrer un fichier comme modèle à l'intérieur de la portée locale. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Fichier</guimenu +> <guisubmenu +>Enregistrer en tant que modèle...</guisubmenu +> <guisubmenu +>Enregistrer en tant que modèle de projet...</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Vous permet d'enregistrer un fichier comme modèle à l'intérieur de la portée d'un projet. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Fichier</guimenu +> <guisubmenu +>Enregistrer en tant que modèle...</guisubmenu +> <guisubmenu +>Enregistrer la sélection dans un fichier de modèle local...</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Vous permet d'enregistrer le texte sélectionné (&pex; un bout de code) dans un fichier de modèle local. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Fichier</guimenu +> <guisubmenu +>Enregistrer en tant que modèle...</guisubmenu +> <guisubmenu +>Enregistrer la sélection dans un fichier de modèle de projet...</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Vous permet d'enregistrer le texte sélectionné (&pex; un bout de code) dans un fichier de modèle de projet. </para> +</listitem> +</varlistentry> + +</variablelist> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Maj;<keycap +>S</keycap +></keycombo +> </shortcut +> <guimenu +>Fichier</guimenu +> <guimenuitem +>Enregistrer tout...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Enregistre tous les fichiers modifiés dans l'éditeur. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>F5</keycap +></keycombo +> </shortcut +> <guimenu +>Fichier</guimenu +> <guimenuitem +>Recharger</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Recharge le document courant. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>P</keycap +></keycombo +> </shortcut +> <guimenu +>Fichier</guimenu +> <guimenuitem +>Imprimer...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Vous pouvez imprimer vos documents. Utilise l'interface <application +>kprinter</application +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>W</keycap +></keycombo +> </shortcut +> <guimenu +>Fichier</guimenu +> <guimenuitem +>Fermer</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Ferme le fichier en cours d'affichage. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Fichier</guimenu +> <guimenuitem +>Tout fermer</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Ferme tous les fichiers ouverts. Vous propose d'enregistrer si des fichiers ont été modifiés. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>Q</keycap +></keycombo +> </shortcut +> <guimenu +>Fichier</guimenu +> <guimenuitem +>Quitter</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Sort de &quantaplus;. </para> +</listitem> +</varlistentry> +</variablelist> + +</sect1> + +<sect1 id="edit-menu-3-2"> +<title +>Le menu <guimenu +>Édition</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>Z</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Annuler</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Annule la dernière action accomplie. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Maj;<keycap +>Z</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Refaire</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Refait la dernière action annulée. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>X</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Couper</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Coupe le bloc de texte courant et place son contenu dans le presse-papiers. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>C</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Copier</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Copie le bloc de texte courant dans le presse-papiers. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>V</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Coller</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Colle le contenu du presse-papiers à la position courante du curseur. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Édition</guimenu +> <guisubmenu +>Collage spécial</guisubmenu +> </menuchoice> +</term> +<listitem> +<para> +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Édition</guimenu +> <guisubmenu +>Collage spécial</guisubmenu +> <guimenuitem +>Coller du HTML cité</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Convertit les caractères spéciaux du texte &HTML; du presse-papiers en entités &HTML; avant de le coller dans le corps de texte, de telle manière qu'ils apparaissent correctement lorsqu'ils sont visualisés et ne sont pas interprétés comme des balises par le navigateur client. </para> +</listitem> +</varlistentry> +<varlistentry> +<term> +<menuchoice +><guimenu +>Édition</guimenu +> <guisubmenu +>Collage spécial</guisubmenu +> <guimenuitem +>Coller une &URL; encodée</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Convertit le texte du presse-papiers en encodage &URL;, qui est la manière correcte d'inclure des caractères spéciaux et des espaces dans les &URL;. Utilisé principalement lors du collage d'une &URL; dans une balise ancre. </para> +</listitem> +</varlistentry> +</variablelist> +</para +></listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>A</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Tout sélectionner</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Sélectionne tout le texte dans le document courant. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Maj;<keycap +>A</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Désélectionner</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Désélectionne tout le texte dans le document courant. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F4</keycap +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Mode de sélection par bloc</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Active/désactive le surlignage de bloc. Vous permet de sélectionner des blocs de texte avec votre clavier sans appuyer sur la touche majuscule. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>Inser</keycap +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Mode d'écrasement</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Annule la touche Inser. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>F</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Chercher...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Cherche une chaîne de caractères ou expression régulière dans le texte du document courant. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F3</keycap +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Poursuivre la recherche</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Répète la recherche dans le document vers le bas à partir de l'emplacement actuel. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Maj;<keycap +>F3</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Chercher en arrière</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Répète la recherche vers le haut dans le document à partir de la position actuelle. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>R</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Remplacer...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Remplace une chaîne de caractères ou une expression régulière de texte dans le document courant. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Alt;&Ctrl;<keycap +>F</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Chercher dans les fichiers...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Trouve une chaîne de caractères ou une expression dans les fichiers du dossier sélectionné. C'est une sorte de <command +>grep</command +> ou <command +>sed</command +> en mode graphique avec certains styles d'espaces prédéfinis pour vous aider. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>I</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Indenter</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Déplace le bloc de texte sélectionné d'une largeur de tabulation vers la droite. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Maj;<keycap +>I</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Désintenter</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Déplace le bloc de texte sélectionné d'une largeur de tabulation vers la gauche. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Édition</guimenu +> <guimenuitem +>Supprimer l'indentation</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Supprime toutes les indentations. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>#</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Commenter</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Met le texte sélectionné en commentaire. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Maj;<keycap +>#</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Décommenter</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Décommente le texte sélectionné. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>J</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Développer les abréviations</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Développe les abréviations. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Édition</guimenu +> <guimenuitem +>Effectuer les retours à la ligne dans le document</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Coupe le texte dans la fenêtre courante à une largeur prédéfinie. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>G</keycap +></keycombo +> </shortcut +> <guimenu +>Édition</guimenu +> <guimenuitem +>Aller à la ligne...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Va directement à une ligne donnée. Ceci est très utile quand votre script &PHP; bloque sans prévenir. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Édition</guimenu +> <guimenuitem +>Orthographe...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Vérifie l'orthographe dans le document courant. </para> +</listitem> +</varlistentry> +</variablelist> + +</sect1> + +<sect1 id="view-menu-3-2"> +<title +>Le menu <guimenu +>Affichage</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +> <guisubmenu +>Vues en arborescence</guisubmenu +> </menuchoice> +</term> +<listitem> +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +> <guisubmenu +>Vues en arborescence</guisubmenu +> <guimenuitem +>Afficher l'arborescence des fichiers</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de l'arborescence des fichiers. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +> <guisubmenu +>Vues en arborescence</guisubmenu +> <guimenuitem +>Afficher l'arborescence du projet</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de l'arborescence du projet. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +><guisubmenu +>Vues en arborescence</guisubmenu +> <guimenuitem +>Afficher l'arborescence des modèles</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de l'arborescence des modèles. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +><guisubmenu +>Vues en arborescence</guisubmenu +> <guimenuitem +>Afficher l'arborescence des scripts</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de l'arborescence des scripts. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +><guisubmenu +>Vues en arborescence</guisubmenu +> <guimenuitem +>Afficher l'arborescence de structure</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de l'arborescence de structure du document. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +><guisubmenu +>Vues en arborescence</guisubmenu +> <guimenuitem +>Afficher l'arborescence des attributs</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de l'arborescence des attributs. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +><guisubmenu +>Vues en arborescence</guisubmenu +> <guimenuitem +>Afficher l'arborescence de documentation</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de l'arborescence de documentation. </para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher la barre d'outils</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule entre activé et désactivé l'affichage de la barre d'outil. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher la barre d'outils DTD</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule entre activé et désactivé l'affichage de la barre d'outils spécifique à la &DTD;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher la barre d'état</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule entre activé et désactivé l'affichage de la barre d'état au bas de la fenêtre principale de &quantaplus;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term +><menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>M</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher les messages</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de la fenêtre de messages. Il s'agit de la fenêtre où vous voyez la sortie de toute action de script et du débogueur. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher le rapporteur de problèmes</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage du <guilabel +>Rapporteur de problèmes</guilabel +> en bas de la fenêtre principale de &quantaplus;. Le <guilabel +>Rapporteur de problèmes</guilabel +> est activé lorsque vous basculez vers <guilabel +>L'arborescence de structure</guilabel +> . </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Maj;<keycap +>F9</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher la bordure d'icônes</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage de la bordure d'icônes à la gauche de la fenêtre principale de l'éditeur. Cette barre permet le basculement par clic des signets. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F11</keycap +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher les numéros de lignes</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule l'affichage du numéro des lignes sur le côté de la fenêtre principale de l'éditeur. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F10</keycap +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Retour à la ligne dynamique</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule entre activé et désactivé le reformatage de texte jusqu'à une largeur donnée au cours de la saisie. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Alt;<keycap +>F9</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Éditeur de source</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule vers la source d'un document à éditer. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Maj;<keycap +>F9</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Éditeur &VPL;</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule vers l'<guilabel +>éditeur &VPL;</guilabel +> pour éditer le document. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F9</keycap +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Éditeurs &VPL; et source</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Bascule vers un mode écran partagé pour éditer un document. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F6</keycap +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Aperçu</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Prévisualise le document actif. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Alt;<keycap +>Gauche</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Précédent</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Navigue d'un pas en arrière dans la prévisualisation. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Alt;<keycap +>Droite</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Suivant</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Navigue un pas en avant dans l'aperçu après être retourné en arrière dans l'aperçu. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F5</keycap +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Rafraîchir l'aperçu</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Recharge la prévisualisation à partir du disque. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>F6</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher dans &konqueror;</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Visualise le fichier actif avec &konqueror;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Alt;<keycap +>F6</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Visualiser avec Mozilla</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Visualise le fichier actif avec <trademark class="registered" +>Mozilla</trademark +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Alt;&Ctrl;<keycap +>F6</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Visualiser avec &Netscape;</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Visualise le fichier actif avec &Netscape; </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;&Maj;<keycap +>F6</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Visualiser avec Opéra</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Visualise le fichier actif avec <application +>Opéra</application +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Maj;<keycap +>F6</keycap +></keycombo +> </shortcut +> <guimenu +>Affichage</guimenu +> <guimenuitem +>Afficher dans Lynx</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Visualise le fichier actif avec <application +>Lynx</application +> (un navigateur en mode texte). </para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="bookmarks-menu-3-2"> +<title +>Le menu <guimenu +>Signets</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>B</keycap +></keycombo +> </shortcut +> <guimenu +>Signets</guimenu +> <guimenuitem +>Définir un signets</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Définit un signet à l'emplacement de la ligne active dans le fichier actif. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Signets</guimenu +> <guimenuitem +>Effacer tous les signets</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Supprime tous les signets enregistrés. </para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="project-menu-3-2"> +<title +>Le menu <guimenu +>Projet</guimenu +></title> + +<para +>La manière d'utiliser les projets dans &quantaplus; est décrit dans <xref linkend="quanta-projects-3-2"/>. </para> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Nouveau projet...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Lance l'assistant de création de projet. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Ouvrir un projet...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Ouvre un fichier de projet existant à partir du disque. Les projets de &quantaplus; sont enregistrés avec l'extension .webprj. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guisubmenu +>Récemment ouvert(s)</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Vous donne une liste des projets les plus récemment ouverts pour un accès rapide. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Fermer le projet</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Ferme le projet actif. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Ouvrir une vue du projet...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Ouvre une « Vue », une combinaison spécifique de fichiers ouverts que vous avez au préalable enregistrés. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Enregistrer la vue du projet</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Enregistre le groupe de fichiers ouverts comme « Vue ». </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Enregistrer la vue de projet sous...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Enregistre le groupe de fichiers ouverts actif comme « Vue » sous un autre nom. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Effacer la vue de projet...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Supprime une « Vue ». </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Insérer des fichiers...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Vous affiche une boîte de dialogue qui vous permet de sélectionner des fichiers à ajouter à votre projet courant (actif). Ces fichiers sont ensuite copiés dans le dossier du projet pour l'édition. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Insérer un dossier...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Insère un dossier et tout son contenu dans le projet actif. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Projet</guimenu +> <guimenuitem +>Vérifier le dossier du projet...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Examine le dossier projet pour tout nouveau fichier qui peut s'y trouver. Ceci vous permet de copier des graphiques dans votre dossier projet ou un sous-dossier puis de les ajouter au projet. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F8</keycap +> </shortcut +> <guimenu +>Projet</guimenu +> <guimenuitem +>Envoyer le projet...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Publie les fichiers de votre projet vers le serveur hôte. La liste des transports disponibles dépend de la version de &kde; que vous utilisez et si vous avez téléchargé ou non des modules KIO supplémentaires. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycap +>F7</keycap +> </shortcut +> <guimenu +>Projet</guimenu +> <guimenuitem +>Propriétés du projet</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Réglages qui affectent la manière dont &quantaplus; gère votre projet. Se reporter à la section <link linkend="quanta-projects-3-2" +>&quantaplus; projets</link +> pour plus de détails. </para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="toolbars-menu-3-2"> +<title +>Le menu <guimenu +>Barres d'outils</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guisubmenu +>Charger les barres d'outils</guisubmenu +> </menuchoice> +</term> +<listitem> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guisubmenu +>Charger les barres d'outils</guisubmenu +> <guimenuitem +>Charger une barre d'outils globale...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Charge une barre d'outils définie globalement. Celles-ci sont gardées par défaut dans <filename class="directory" +>$<envar +>KDEDIR</envar +>/share/apps/quanta/toolbars</filename +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guisubmenu +>Charger les barres d'outils</guisubmenu +> <guimenuitem +>Charger une barre d'outils locale...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Charge une barre d'outils définie localement. Celles-ci sont gardées par défaut dans <filename class="directory" +>$<envar +>HOME</envar +>/.kde/share/apps/quanta/toolbars</filename +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guisubmenu +>Charger les barres d'outils</guisubmenu +> <guimenuitem +>Charger une barre d'outils du projet</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Charge une barre d'outils de projet. Celles-ci sont gardées dans <filename class="directory" +><replaceable +>ProjectDir</replaceable +>/toolbars</filename +> et ne sont disponibles dans ce menu que si elles ont été assignées à ce projet. </para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guisubmenu +>Enregistrer les barres d'outils</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Boîte de dialogue pour enregistrer vos barres d'outils. Vous permet de choisir le type de barre d'outils Local ou Projet. </para> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guisubmenu +>Enregistrer les barres d'outils</guisubmenu +> <guimenuitem +>Enregistrer en tant que barre d'outils locale...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Enregistre comme barre d'outils locale vers le dossier <filename class="directory" +>$<envar +>HOME</envar +>/.kde/share/apps/quanta/toolbars</filename +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guisubmenu +>Enregistrer les barres d'outils</guisubmenu +> <guimenuitem +>Enregistrer en tant que barre d'outils du projet...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Enregistre comme barre d'outil de projet dans <filename class="directory" +><replaceable +>ProjectDir</replaceable +>/toolbars</filename +> </para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guimenuitem +>Ajouter une barre d'outils d'utilisateur</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Fait apparaître une boîte de dialogue pour créer une nouvelle barre d'outils. Ceci crée seulement le nom. Les actions doivent être ajoutées à partir de <menuchoice +> <guimenu +>Configuration</guimenu +> <guimenuitem +>Configurer les actions</guimenuitem +> </menuchoice +>. Les barres d'outils sont enregistrées grâce au menu <menuchoice +> <guimenu +>Barres d'outils</guimenu +> <guimenuitem +>Enregistrer les barres d'outils</guimenuitem +> </menuchoice +>, ou à la fermeture des barres d'outils non enregistrées, une boîte de dialogue vous avertira de les enregistrer. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guimenuitem +>Enlever la barre d'outils d'utilisateur...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Supprime une barre d'outils de l'utilisation. Ceci ne l'enlève pas du disque. Si vous n'avez pas enregistré la barre d'outils que vous enlevez, une boîte de dialogue vous demande de le faire. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guimenuitem +>Renommer la barre d'outils utilisateur...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Vous permet de renommer une barre d'outils. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Barres d'outils</guimenu +> <guimenuitem +>Envoyer la barre d'outils par message électronique</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>C'est un moyen d'envoyer par courrier électronique vos barres d'outils personnalisées à quelqu'un (peut être l'équipe de &quantaplus; pour l'inclusion dans la prochaine version !) pour leur utilisation. Cela engendre une fenêtre de courrier et y joint automatiquement votre fichier de barre d'outils. </para> +</listitem> +</varlistentry> + +</variablelist> +</sect1> + +<sect1 id="tags-menu-3-2"> +<title +>Le menu <guimenu +>Balises</guimenu +></title> + +<para +>Ce menu contient une liste d'éléments qui sont dans les barres actives. Si vous avez la barre standard (&HTML;) active, le menu <guimenu +> Balises</guimenu +> contient un sous-menu <guisubmenu +>Standard </guisubmenu +> qui contient la liste des balises/actions sur cette barre d'outils. </para> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>E</keycap +></keycombo +> </shortcut +> <guimenu +>Balises</guimenu +> <guimenuitem +>Modifier la balise courante...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Vous permet d'accéder à la boîte de dialogue de réglages de la balise s'il en existe une. Cette entrée est toujours présente, suivie par les sous-menus spécifiques à la &DTD;. </para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="DTD-menu-3-2"> +<sect1info> +<title +>Le menu <guimenu +>&DTD;</guimenu +></title> +<authorgroup> +<author +><firstname +>Christopher</firstname +> <surname +>Hornbaker</surname +> <affiliation +> <address +><email +>[email protected]</email +></address> +</affiliation> +</author> +</authorgroup> +</sect1info> + +<title +>Le menu <guimenu +>&DTD;</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>&DTD;</guimenu +> <guimenuitem +>Changer la &DTD;...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Fait apparaître une boîte de dialogue qui vous permet de changer la &DTD; des documents courants. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>&DTD;</guimenu +> <guimenuitem +>Charger et convertir une &DTD;...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Charge une &DTD; que vous ou quelqu'un d'autre a écrit et la convertit dans le format de description natif de &quantaplus;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>&DTD;</guimenu +> <guimenuitem +>Charger un paquetage de &DTD; (&DTEP;)...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Charge votre propre &DTEP;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>&DTD;</guimenu +> <guimenuitem +>Envoyer un paquetage de &DTD; (&DTEP;) par message électronique...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Envoie votre &DTEP; à un ami via &kmail;. </para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="plugins-menu-3-2"> +<title +>Le menu <guimenu +>Modules</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Modules</guimenu +> <guimenuitem +>Édition</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Fait apparaître une boîte de dialogue qui vous permet de charger des modules (KParts) dans &quantaplus;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Modules</guimenu +> <guimenuitem +>Valider</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Valide que &quantaplus; est en mesure de charger les modules que l'utilisateur a entrés. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Modules</guimenu +> <guimenuitem +><replaceable +>Module</replaceable +></guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Le menu <menuchoice +><guimenu +>Modules</guimenu +></menuchoice +> liste les modules disponibles sous les entrées des menus. Cliquer dessus les active. Cliquer sur un module activé le désactive. </para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="tools-menu-3-2"> +<title +>Le menu <guimenu +>Outils</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Outils</guimenu +> <guimenuitem +>Propriétés du document</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Édite les propriétés spécifiques d'un document actif lors de l'utilisation de <guilabel +>l'éditeur &VPL;</guilabel +>. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Outils</guimenu +> <guimenuitem +>Convertir la casse de la balise et de ses attributs...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Convertit la casse de tous les caractères des balises et/ou attributs. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Alt;<keycap +>0</keycap +></keycombo +> </shortcut +> <guimenu +>Outils</guimenu +> <guimenuitem +>Liste des fichiers ouverts...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Ouvre une boîte de dialogue qui met en surbrillance tous les fichiers ouverts. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Alt;&Ctrl;<keycap +>T</keycap +></keycombo +> </shortcut +> <guimenu +>Outils </guimenu +> <guimenuitem +> Vérification de la syntaxe HTML avec Tidy</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Vérifie la syntaxe du document actif par rapport à la &DTD;. </para> +</listitem> +</varlistentry> +</variablelist> +</sect1> + +<sect1 id="settings-menu-3-2"> +<title +>Le menu <guimenu +>Configuration</guimenu +></title> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><guimenu +>Configuration</guimenu +> <guimenuitem +>Configurer Quanta...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Configure le comportement de &quantaplus;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Configuration</guimenu +> <guimenuitem +>Configurer l'éditeur...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Configure le comportement de la fenêtre de l'éditeur. Se reporter à la documentation sur &kate; pour plus de détails. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Configuration</guimenu +> <guimenuitem +>Configurer les actions...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Ceci est l'endroit où vous configurez les actions pour l'utilisation avec les barres d'outils. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Configuration</guimenu +> <guimenuitem +>Configurer les barres d'outils...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Boîte de dialogue qui vous permet d'ajouter/de supprimer des entrées vers/à partir des barres d'outils et de changer l'ordre dans lequel apparaissent les icônes. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Configuration</guimenu +> <guimenuitem +>Configurer les raccourcis clavier...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Vous permet de configurer les nombreux raccourcis de l'éditeur disponibles dans &quantaplus;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Configuration</guimenu +> <guisubmenu +>Mode de coloration syntaxique</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Choisit le mode de surbrillance pour le fichier actif. La liste des variantes de mise en surbrillance change en fonction de votre version de &kate;. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Configuration</guimenu +> <guisubmenu +>Fin de ligne</guisubmenu +> </menuchoice> +</term> +<listitem> +<para +>Sélectionne l'encodage de fin de ligne. Utile si vous avez des amis qui développent sous d'autres plates-formes. Choisissez parmi <guimenuitem +>Unix</guimenuitem +>, <guimenuitem +>Windows/DOS</guimenuitem +> ou <guimenuitem +>Macintosh</guimenuitem +>. </para> +</listitem> +</varlistentry> + +</variablelist> +</sect1> + +<sect1 id="help-menu-3-2"> +<title +>Le menu <guimenu +>Aide</guimenu +></title> + +<para +>&quantaplus; contient un menu d'<guimenu +>Aide</guimenu +> standard de &kde; avec en plus ces articles : </para> + +<variablelist> +<varlistentry> +<term> +<menuchoice +><shortcut +> <keycombo action="simul" +>&Ctrl;<keycap +>H</keycap +></keycombo +> </shortcut +> <guimenu +>Aide</guimenu +> <guimenuitem +>Aide contextuelle...</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>Ceci doit produire une aide fondée sur le contexte courant du pointeur. À l'heure de cette rédaction, cette fonction n'est pas encore implémentée. </para> +</listitem> +</varlistentry> + +<varlistentry> +<term> +<menuchoice +><guimenu +>Aide</guimenu +> <guimenuitem +>Faire un don</guimenuitem +> </menuchoice> +</term> +<listitem> +<para +>&quantaplus; est un produit de haute qualité qui est librement disponible et est sous licence libre, mais comme tout projet à source ouverte, ses développeurs peuvent toujours utiliser de l'aide. Si vous souhaitez soutenir le développement de &quantaplus; d'une manière financière, vous pouvez trouver comment ici. </para> +</listitem> +</varlistentry> + +</variablelist> + +<para +>Les éléments du menu d'aide standard de &kde; sont comme suit : </para> +&help.menu.documentation; </sect1> +</chapter> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/quanta-projects.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/quanta-projects.docbook new file mode 100644 index 00000000000..04622854997 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/quanta-projects.docbook @@ -0,0 +1,624 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<sect1 id="quanta-projects-3-2"> +<sect1info> +<title>Projects</title> +<authorgroup> +<author> +<firstname>Robert</firstname> +<surname>Nickel</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +</author> + +<othercredit role="reviewer"> +<firstname>Christopher</firstname> +<surname>Hornbaker</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +<contrib>Reviewer</contrib> +</othercredit> + +<othercredit role="reviewer"> +<firstname>Fabrice</firstname> +<surname>Mous</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +<contrib>Reviewer</contrib> +</othercredit> + +<!-- TRANS:ROLES_OF_TRANSLATORS --> + +</authorgroup> +</sect1info> + +<title>Projects</title> + +<sect2 id="create-new-project-3-2"> +<title>New Projects</title> + +<para> +The &quantaplus; project wizard +(<menuchoice> +<guimenu>Project</guimenu> +<guimenuitem>New Project</guimenuitem> +</menuchoice>) makes project creation an easy task. +</para> + +<mediaobject> +<imageobject> +<imagedata format="PNG" fileref="project-1.png" /> +</imageobject> +<caption><para>The Project Wizard.</para></caption> +</mediaobject> + +<para> +The fields are pretty straight forward. It is best to fill them in from +top to bottom. Filling in a project name will autocomplete all the +folder structure for the rest of the project. All of the paths and +author information fields can be configured later on clicking +<menuchoice> +<shortcut> +<keycap>F7</keycap> +</shortcut> +<guimenu>Project</guimenu> +<guimenuitem>Project Options</guimenuitem> +</menuchoice>. +</para> + +<variablelist> +<title>General Project Settings</title> +<varlistentry> +<term><guilabel>Name</guilabel></term> +<listitem> +<para> +Here you fill in the name for your project. For example, we will call ours +<quote><literal>foo</literal>.</quote> When you fill in +<guilabel>Name</guilabel>, <guilabel>File</guilabel> is filled out for +you automatically. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guilabel>File</guilabel></term> +<listitem> +<para> +This is the name of the &quantaplus; project file. By default, it is the +name of your project, but in lowercase letters and without spaces. It +uses the extension <literal role="extension">webprj</literal> (&pex; +<filename>foo.webprj</filename>). This file is stored in the root of the +project's Main Folder. +</para> +</listitem> +</varlistentry> +</variablelist> + +<variablelist> +<varlistentry> +<term>Server Settings</term> +<listitem> +<variablelist> +<varlistentry> +<term>Protocol</term> +<listitem> +<para> +Here you select the protocol you will be using to access you project. If +your project is on the same machine that you are using Quanta Plus on, +then leave the value at Local. The list of protocols shown here is +dependant of your system setup. Available protocols include SSH, FTP, NFS, +SMB, WebDAV, and many others. The protocol list is powered by &kde;'s +powerful KIOSlave architecture. This framework allows every &kde; +application to easily access remote information as if it is local to the +machine. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>Host</term> +<listitem> +<para> +Here you fill in the server address of the machine you want to access, +unless you are working through the Local protocol. Either a hostname +(hostname.example.com) or an IP address (127.0.0.1) can go here. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>User</term> +<listitem> +<para> +User name for logging onto the remote machine. This is case-sensitive. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>Password</term> +<listitem> +<para> +Password for logging onto the remote machine. This is case-sensitive +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>Port</term> +<listitem> +<para> +Leave this field blank to use the default port for the protocol you are +using. You may need to change this depending on your server's +configuration. +</para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> +</variablelist> + + +<variablelist> +<varlistentry> +<term>Folder Settings</term> +<listitem> +<variablelist> +<varlistentry> +<term>Main Folder</term> +<listitem> +<para> +This is the root folder where all of the project files and folders +will be stored. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Templates Folder</guilabel></term> +<listitem> +<para> +This is where the templates for this project will be stored. By default, +its path is: <filename class="directory"><replaceable>Main +Folder</replaceable>/templates</filename>; for example <filename +class="directory">/home/johndoe/projects/example_project/templates. +</filename> If you have a common set of files that you use for several +projects, then it may be useful to point this field to it, instead of to +the default. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Toolbars Folder</guilabel></term> +<listitem> +<para> +This is where the toolbars for this project will be stored. By default, +it is <filename class="directory"><replaceable>Project destination +</replaceable>/toolbars</filename>. If you have a common set of toolbars +that you use for several projects, it may be useful to point this there +instead of the default. +</para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> +</variablelist> + + +<variablelist> +<varlistentry> +<term>Project Sources</term> +<listitem> +<variablelist> +<varlistentry> +<term><guilabel>Add local or remote files</guilabel></term> +<listitem> +<para> +This allows you to get files from the local file system. You can choose +multiple files or entire folders. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Use wget to download files from site</guilabel></term> +<listitem> +<para> +This option is great if you have static web content that you wish to +download and modify. For server side scripting (&pex; &PHP;, Python, +&etc;.) you will have to get the files another way. +</para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> +</variablelist> + +<variablelist> +<title>Insert Files in Project</title> +<varlistentry> +<term>Insert file from</term> +<listitem> +<para> +Check this if you wish to include files found in the path of the Main +Folder. Leave unchecked when starting a project from scratch. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>Filters</term> +<listitem> +<variablelist> +<varlistentry> +<term>Insert only markup, script, and image files</term> +<listitem> +<para> +Choosing this option will only insert markup, script, and image files into +your project. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>Insert files with the following mask</term> +<listitem> +<para> +Choosing this option will display all files and folders within the +Main Folder and allow you to be more specific with your choices. +</para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> +<varlistentry> +<term>Included files</term> +<listitem> +<para> +This displays a list of the files in the Main Folder. You can choose +the desired files for inclusion, by checking, or exclusion, by unchecking, +in your project. +</para> +</listitem> +</varlistentry> +</variablelist> + +<variablelist> +<title>More Project Settings</title> +<varlistentry> +<term><guilabel>Author</guilabel></term> +<listitem> +<para> +Insert your name (or alias) here. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Email</guilabel></term> +<listitem> +<para> +The address where you would like email regarding this project to go. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>Project Defaults</term> +<listitem> +<variablelist> +<varlistentry> +<term>Default DTD</term> +<listitem> +<para> +Choose the markup language you will be working with the most within this +project. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>Default encoding</term> +<listitem> +<para> +Choose the character encoding you wish the files in your project to be +opened and saved with. +</para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Use preview prefix</guilabel></term> +<listitem> +<para> +Check this to use a prefix for your previews. This allows you to set the +path prefix to something other than your local file system. This is most +useful for pages that contain dynamic content and are dependent on server +processing (like &PHP;, <acronym>JSS</acronym>, Python, &etc;). Simply +type in the first portion of the address as it exists on that server and +the filepath at the end will be complete by &quantaplus;. For example, if +you have the domain <literal>bar.com</literal> and you are editing the +<filename>index.html</filename> page, you could edit it on your remote +machine (<systemitem>foo.bar.com</systemitem>), upload it to the server +and press <keycap>F6</keycap> to see the results from +<systemitem>www.bar.com</systemitem> instead of your local file system. +</para> +<variablelist> +<varlistentry> +<term>Prefix</term> +<listitem> +<para> +Enter the prefix you wish to use here. +</para> +</listitem> +</varlistentry> +</variablelist> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Insert global templates</guilabel></term> +<listitem> +<para> +This makes a copy of the global templates in your projects folder tree. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Insert local templates</guilabel></term> +<listitem> +<para> +This makes a copy of the local templates in your projects folder tree. +</para> +</listitem> +</varlistentry> +</variablelist> + +<para> +The last screen of the new project wizard has 3 settings that can make +your life easier. These settings are available for change from the +<menuchoice> +<guimenu>Project</guimenu> +<guimenuitem>Project Options</guimenuitem> +</menuchoice> + menu tree on the Network Tab or with the keyboard shortcut +<keycap>F7</keycap>. +</para> + +</sect2> + +<sect2 id="using-projects-3-2"> +<title>Using Projects</title> + +<sect3 id="project-files-3-2"> +<title>Project Files</title> + +<para> +By default &quantaplus; will open the last project accessed when launched. +This behavior is not currently configurable. +</para> + +<para> +To open another project, select <guimenuitem>Open</guimenuitem> from the +<guimenu>Project</guimenu> menu or the <guiicon>Open Project</guiicon> +icon on the toolbar. The open project dialog will pop up and allow you to +choose the project you wish. Projects have a <literal +role="extension">webprj</literal> extension. +</para> + +<para> +When closing &quantaplus;, your project file will be saved automatically. +You will be asked to save any changes before exiting if &quantaplus; +detects any changed files. This same behavior occurs if you load a new +project. +</para> + +</sect3> + +<sect3 id="project-tree-view-3-2"> +<title>The Project Tree View</title> + +<para> +The project tree view gives you uncluttered access to the files in your +project. This is where you manage the files in the current project. +</para> + +<para>For files, a &BDS; click brings up the following menu:</para> + +<mediaobject> +<imageobject> +<imagedata fileref="project-tree-view-file-rmb-menu.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +These items are fairly self-explanatory and will be left to the reader +for exploration. +</para> + +<para> +Folders are similar but do not contain the <guimenuitem>Open With +</guimenuitem> and <guimenuitem>Open in &quantaplus;</guimenuitem> &BDS; +menu items: +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="project-tree-view-dir-rmb-menu.png" format="PNG" /> +</imageobject> +</mediaobject> + +<para> +These items are left to the reader for exploration as well. +</para> + +</sect3> + +<sect3 id="upload-project-3-2"> +<title>Uploading Projects</title> + +<para> +The Upload Projects dialog: +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="project-upload-dialog.png" format="PNG" /> +</imageobject> +<caption><para>The Upload Projects dialog.</para></caption> +</mediaobject> + +<variablelist> +<varlistentry> +<term><guilabel>Host</guilabel></term> +<listitem> +<para> +This is the hostname of the server your copying the files to. Either fully +qualified domain name, or an IP address will work. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guilabel>Protocol</guilabel></term> +<listitem> +<para> +Transfer protocol to use for this upload. Depending on your version of +&kde; this list will vary. At the very least you should be able to choose +from &FTP;, file (&cad; local) and <acronym>NFS</acronym>. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guilabel>Port</guilabel></term> +<listitem> +<para> +Port for the transfer. Usually this will not need to be changed unless your +network administrator is hosting a service on a port other than its well +known port. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guilabel>User</guilabel></term> +<listitem> +<para> +User name to use for authentication. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guilabel>Password</guilabel></term> +<listitem> +<para> +Password to use for authentication. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guilabel>Keep Password</guilabel></term> +<listitem> +<para> +Depending on your level of paranoia, this is a time saving feature, or a +danger. Use it at your discretion. The password is kept on disk in plain text. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guilabel>Path</guilabel></term> +<listitem> +<para> +This is the base path on the remote host that you will be copying files +to. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>Upload</guibutton></term> +<listitem> +<para> +Start the upload +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>Cancel</guibutton></term> +<listitem> +<para> +This will abort your transfer in progress or just exit out of the dialog +if you change your mind before starting the upload. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>All</guibutton></term> +<listitem> +<para> +Select all files in your project for upload. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>Modified</guibutton></term> +<listitem> +<para> +Select all modified files for upload. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>None</guibutton></term> +<listitem> +<para> +Unselects all files in the list. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>Invert</guibutton></term> +<listitem> +<para> +Selects/Unselects all files in the list. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>Expand All</guibutton></term> +<listitem> +<para> +Expands all folders. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>Collaspe All</guibutton></term> +<listitem> +<para> +Collaspes all folders. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guibutton>Update All</guibutton></term> +<listitem> +<para> +Refreshes list. +</para> +</listitem> +</varlistentry> + +</variablelist> +</sect3> +</sect2> +</sect1> diff --git a/tde-i18n-fr/docs/tdewebdev/quanta/working-with-quanta.docbook b/tde-i18n-fr/docs/tdewebdev/quanta/working-with-quanta.docbook new file mode 100644 index 00000000000..c1393fb1a75 --- /dev/null +++ b/tde-i18n-fr/docs/tdewebdev/quanta/working-with-quanta.docbook @@ -0,0 +1,565 @@ +<?xml version="1.0" encoding="UTF-8" ?> + +<chapter id="using-quanta-3-2"> +<chapterinfo> +<title>Working With...</title> +<authorgroup> +<author> +<firstname>Robert</firstname> +<surname>Nickel</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +</author> + +<othercredit role="reviewer"> +<firstname>Christopher</firstname> +<surname>Hornbaker</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +<contrib>Reviewer</contrib> +</othercredit> + +<othercredit role="reviewer"> +<firstname>Fabrice</firstname> +<surname>Mous</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +<contrib>Reviewer</contrib> +</othercredit> + +<!-- TRANS:ROLES_OF_TRANSLATORS --> + +</authorgroup> +</chapterinfo> + +<title>Working With...</title> + +<para> +This chapter describes the parts of &quantaplus; that you will be +interacting with mostly. These not only make your more productive, but +they also allow you to customize &quantaplus; to your work-flow. +</para> + +<sect1 id="toolbars-howto-3-2"> +<title>Toolbars</title> + +<para> +As previously mentioned, toolbars in &quantaplus; are primarily managed +through the <guimenu>Toolbars</guimenu> menu. Usability and creation are +somewhat different. The creation of toolbars is discussed in a later +section entitled <quote><link linkend="creating-toolbars-3-2">Creating +Toolbars</link>.</quote> +</para> + +<para> +Using toolbars is quite simple. When you click on an icon for a desired +element or action, one of three possibilities occur: the element is +inserted (optionally with a closing element); or an element dialog is +activated, allowing you to fill in the attributes in a dialog box; or, +lastly, an action is activated and does something nifty for your current +file or project. If you find yourself doing tedious and redundant typing +for a particular element, that is not in &quantaplus;, then you can add it. +See <xref linkend="dtep-intro-3-2" /> for more information. +</para> + +<para> +A tag dialog looks just like the following: + +<mediaobject> +<imageobject> +<imagedata fileref="taginputex.png" format="PNG" /> +</imageobject> +<caption><para>An example of a tag dialog.</para></caption> +</mediaobject> +</para> + +<para> +The above image is the dialog for the anchor tag. If you know &XHTML;, +then you should have noticed that all the attributes that you can use, in +an anchor element, are available. Notice the tabs above for +<guilabel>Main</guilabel>, <guilabel>Core and i18n</guilabel>, +<guilabel>Events</guilabel>, and <guilabel>Focus</guilabel>, they hold +all of the other attributes, according to their purpose, available to the +anchor element. All you need do is: fill in the blanks for the attributes +you want in your anchor, omit the attributes you do not want, and click OK. +You now have a well formed anchor set down at the current cursor position. +</para> +</sect1> + +&quanta-projects; + +<sect1 id="templates-3-2"> +<title>Templates</title> + +<para> +Templates are basically skeleton documents, code snippets and files to +link to. &quantaplus; uses templates fundamentally as a standard file +system with enhanced organization and interfacing. You can copy, move or +link any repository currently on your system into the templates tree. +Think of &quantaplus; templates as having roughly the limitations to your +imagination that your file system has. +</para> + +<para> +Templates exist in nested folders. There is no limit to how deep you +can nest them however within any given folder &quantaplus; expects a +consistent action for the base template type described below. Additionally +templates allow for pre and post text to be concatenated to non document +type templates. This facilitates tag creation. The next update after the +introduction is scheduled to add the ability to pass variables to the text +such as image size information to assist in tag creation. +</para> + +<para> +Our goal with templates is to extend them to include multi file <quote> +concept</quote> templates useful for things like placing an order or +creating an about section, Ideally this will be a tool for making your +work more productive and dynamic. An eventual goal is to have a structural +template design mode to deal with site layout and structure which you +could use to design and interactively update your sites. If you would like +to be involved, check out our +<ulink url="http://quanta.sourceforge.net/main1.php?contfile=needs">help +wanted</ulink> page. +</para> + +<important> +<para> +Some of the templates that ship with &quantaplus; have conditions for +their usage. Please read carefully the usage statement of conditions at +the top of each template before you use it. +</para> +</important> + +<sect2 id="template-types-3-2"> +<title>Template Types</title> + +<para> +Currently templates are limited to being one of the following types of +objects: +</para> + +<simplelist> +<member>Document</member> +<member>Text to insert in a document</member> +<member>A file to link to form a document</member> +</simplelist> + +<para> +Documents can be any type of document. Generally you would want to nest +more specific or diverse documents in subfolders. Here you can make a +basic framework for what you do and deliver it to your work in an +organized fashion and realize much better efficiency. Text insertion could +be anything from a snippet of code to a script or whatever you might wish +to use. This overlaps the ability to insert text blocks as an action which +can be triggered from the toolbar. Linked files can be binary, &PHP; class +libraries or whatever you like. +</para> + +</sect2> + +<sect2 id="template-scope-3-2"> +<title>Template Scopes</title> + +<para> +Templates are accessible based upon their established +<link linkend="quanta-workspaces-3-2">workspace</link> in &quantaplus; +</para> + +</sect2> + +<sect2 id="creating-templates-3-2"> +<title>Creating Templates</title> + +<para> +Create a document structure that you love (&XML;, &HTML;, DocBook, &etc;.) +and click on +<menuchoice> +<guimenu>File</guimenu> +<guimenuitem>Save as Template</guimenuitem> +<guimenuitem>Save as Local/Project Template</guimenuitem> +</menuchoice>. +</para> + +<para> +Once this is done, you will notice that (even if it is saved as a Project +template) the template does <emphasis>not</emphasis> show in the project +tab view. Look into the templates view to find your template under the +Project templates tab. +</para> + +<para> +Additionally if you look at your options with the &BDS; you will see +complete file management tools for creating folders or copying and +pasting templates from one location to another. +</para> + +</sect2> + +<sect2 id="using-templates-with-projects-3-2"> +<title>Using Templates With Projects</title> + +<para> +Project templates allow you to be more tightly focused. You can create +headers, footers or go dynamic with &PHP; include files and link them. +Additionally there are some very cool things we took into consideration +when using templates in projects. +</para> + +<para> +When creating a project you can opt to copy to your local project all the +existing global and user templates. Legacy project get default templating +abilities so nothing is lost You can choose where to locate your template +files so they can be in your server root and easy to upload or you can +make them secure to link to below server root which is a very cool trick. +When linking to a file not in the project templates you will be prompted +to copy the file to the project templates prior to linking. This will prevent +broken links on upload. You always have control where you place your +templates so you can choose to move them. However &quantaplus; does not +track this so you will need to change links. +</para> + +</sect2> + +<sect2 id="managing-templates-3-2"> +<title>Managing Template Behavior</title> + +<para> +Template structure on the template tab is based on the files found in +<filename class="directory"> +$<envar>KDEDIR</envar>/share/apps/quanta/templates</filename> and +<filename class="directory"> +$<envar>HOME</envar>/.kde/share/apps/quanta/templates</filename>. Each of +these folders is specified as one of three types of container: +</para> + +<variablelist> +<varlistentry> +<term>files/all</term> +<listitem> +<para> +Binaries and such things that get inserted by their &URL; (&cad; images as +an <sgmltag class="starttag">img src=/src/url</sgmltag>). +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>text/all</term> +<listitem> +<para> +Text that you can insert into the current &quantaplus; document, such as +repetitive blocks. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term>template/all</term> +<listitem> +<para> +Document templates which you can create new documents from. These open a +new window in &quantaplus;. +</para> +</listitem> +</varlistentry> +</variablelist> + +<para> +To set the behavior of each folder, &BDS; click in the template view on +the folder and choose <guimenuitem>Properties</guimenuitem>. The +following dialog will come up: + +<mediaobject> +<imageobject> +<imagedata fileref="template-rmb.png" format="PNG" /> +</imageobject> +<caption><para>Properties dialog.</para></caption> +</mediaobject> +</para> + +<variablelist> +<varlistentry> +<term><guilabel>Type</guilabel></term> + +<listitem> +<para> +Drop down box with the three types discussed previously; files, text, +template. This box will be grayed out if you have the <guilabel>inherit +parent attribute box</guilabel> checked. +</para> +</listitem> +</varlistentry> + +<varlistentry> +<term><guilabel>Inherit parent attribute</guilabel> (<sgmltag +class="starttag">foo</sgmltag>)</term> +<listitem> +<para> +This is checked by default and is fine for all but the top level +folders in your templates tree. If the top level folder has this +checked, it will basically deactivate templates for that folder and all +that aren't explicitly set below it. If this is not a top level folder, +then the <sgmltag class="starttag">blah</sgmltag> will say something like +<literal>text/all</literal>. If it says nothing, then chances are that +you are on a top level folder. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Use pre/post text</guilabel></term> +<listitem> +<para> +Enables pre and post text for templates in this folder. This could be a +common header/footer for all of your templates for a given project and +then you copy content templates into that folder and have a complete +page with the custom header/footer as a starting point. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Pre-text</guilabel></term> +<listitem> +<para> +The actual text to insert before your templates content. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Post-text</guilabel></term> +<listitem> +<para> +The actual text to insert after your templates content. +</para> +</listitem> +</varlistentry> +</variablelist> + +</sect2> +</sect1> + +<sect1 id="vpl-3-2"> +<sect1info> +<title><application>Visual Page Layout</application></title> +<authorgroup> +<author> +<firstname>Nicolas</firstname> +<surname>Deschildre</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +</author> + +<othercredit role="reviewer"> +<firstname>Christopher</firstname> +<surname>Hornbaker</surname> +<affiliation> +<address><email>[email protected]</email></address> +</affiliation> +<contrib>Reviewer</contrib> +</othercredit> + +<!-- TRANS:ROLES_OF_TRANSLATORS --> + +</authorgroup> +</sect1info> + +<title><application>Visual Page Layout</application></title> + +<sect2 id="vpl-views-3-2"> +<title>&VPL; Modes</title> + +<para> +The <application>Visual Page Layout</application> (&VPL;) editor (also known +as <acronym>WYSIWYG</acronym> (What You See Is What You Get)) allows you +to edit a &HTML; or &XHTML; document while seeing the changes on-the-fly. +Just like your favorite wordprocessor, you can click on your document and +a cursor will appear, thus enabling you to enter text, insert images, +apply text decorations, &etc;. &VPL;'s aim is to allow you to create great, +valid web pages without any knowledge of Internet markup languages. +</para> + +<para> +&quantaplus; offers two modes: <guilabel>&VPL; Editor</guilabel> and +<guilabel>&VPL; & Source Editor</guilabel>, which are accesible from +the <guimenu>View</guimenu> menu. The first replaces the <guilabel>Source +Editor</guilabel> with the <guilabel>&VPL; Editor</guilabel>, and the +second splits the editor window into two parts: the <guilabel>Source +Editor</guilabel> and the <guilabel>&VPL; Editor</guilabel>. +</para> + +<para> +The <guilabel>&VPL; Editor</guilabel> works like so: It loads a document +like a normal &HTML; or &XHTML; page and a cursor appears. Then you can +edit it, and switching back to <guilabel>Source Editor</guilabel>, you see +that the changes you made on the <guilabel>&VPL; Editor</guilabel> have +been merged in the <guilabel>Source Editor</guilabel>. +</para> + +<note> +<para> +When working in the <guilabel>&VPL; Editor</guilabel> with a document that +contains &PHP;, you will see a small green icon representing the &PHP; +code. You cannot directly edit it with the <guilabel>&VPL; +Editor</guilabel>. To edit &PHP;, you will still need to use the +<guilabel>Source Editor</guilabel>. There are no plans to change this +functionility. +</para> +</note> + +<para> +The second mode behaves exactly like the first, except that you instantely +see the impact that your changes have made, either in the <guilabel>Source +Editor</guilabel> or in the <guilabel>&VPL; Editor</guilabel>, and the +cursors of the source editor and of the <guilabel>&VPL; Editor</guilabel> +are synchronized. Pressing <keycap>F9</keycap> loads this mode, but, if +it is already loaded, it will move the focus from one view to the other, +while keeping you at the same location of the document. +</para> + +<para> +The refresh intervals between the <guilabel>&VPL; Editor</guilabel> and +the <guilabel>Source Editor</guilabel> are configurable. Go to +<menuchoice> +<guimenu>Settings</guimenu> +<guimenuitem>Configure Quanta...</guimenuitem> +</menuchoice>. Select the <guimenu>&VPL; View</guimenu> tab. You can +choose whether you want to refresh a view only when you click on it or +automatically. If you choose automatically, then you can choose a refresh +interval. The general recommendation is: A smaller number for fast +computers and a bigger number for slower ones. +</para> + +<mediaobject> +<imageobject> +<imagedata fileref="vplsourceview.png" format="PNG" /> +</imageobject> +<caption><para>The <guilabel>&VPL; & Source Editor</guilabel> mode.</para></caption> +</mediaobject> +</sect2> + +<sect2 id="vpl-editing-3-2"> +<title>&VPL; Editing</title> + +<sect3 id="doc-prop-dia-3-2"> +<title>The <guilabel>Document Properties</guilabel> Dialog</title> + +<para> +Now, let's say you want to edit the title of your web page. How do you do +it? Simply launch +<menuchoice> +<guimenu>Tools</guimenu> +<guimenuitem>Document Properties</guimenuitem> +</menuchoice>. This tool allows the edition of <quote>invisible</quote> +tags when using the <guilabel>&VPL; Editor</guilabel>. The +<guilabel>Document Properties</guilabel> dialog is also launched when you +create a new document while in the <guilabel>&VPL; Editor</guilabel>. This +is in order to lessen the amount of hand coding you need to perform. With +it, you can edit: +</para> + +<variablelist> +<varlistentry> +<term><guilabel>Title</guilabel></term> +<listitem> +<para> +The title of the document. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Meta items</guilabel></term> +<listitem> +<para> +Meta tags allow you to store informations about the document itself +&pex; keywords for the Internet search engines. You can add or remove +<guilabel>Meta items</guilabel> by pressing the two buttons below, +and edit them by clicking on the list &pex; put <quote>keywords</quote> on +the <quote>name</quote> column and <quote>keyword1 keyword2</quote> on the +<quote>content</quote> column. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>CSS Rules</guilabel></term> +<listitem> +<para> +<guilabel>CSS Rules</guilabel> are the new way to tell your web browser +how to present the page. You can add or delete the <guilabel>CSS +Rules</guilabel> by pressing the buttons below. You can also fill the +fields like the <guilabel>Meta items</guilabel>. The edition of +<guilabel>CSS Rules</guilabel> is not yet supported. +</para> +</listitem> +</varlistentry> +<varlistentry> +<term><guilabel>Link CSS Stylesheet</guilabel></term> +<listitem> +<para> +You can also link an external CSS stylesheet. Simply click on the +<guilabel>Browse</guilabel> button and select your file. +</para> +</listitem> +</varlistentry> +</variablelist> + +</sect3> + +<sect3 id="vpl-editor-3-2"> +<title>The <guilabel>&VPL; Editor</guilabel></title> + +<para> +You can use your cursor like you do in a wordprocessor, moving with the +arrows. It may come that the cursor does not want to go where you want it +to go (a pesky bug). Selection also works as usual. You can insert text by +typing and remove text by pressing the &Correction; or delete key. +</para> + +<para> +Now we come to tag insertion. You can insert images, applets, text +decorations such as bold and so on by using the same toolbars you use in +the source editor. Note that the insertion of tags does not remove previous +identical tags &pex; if you insert an anchor tag around some text, then you +must remove any other anchor tag around it. +</para> + +<note> +<para> +Some toolbar items will be disabled, such as the <guilabel>Table +Wizard</guilabel> or <guilabel>Quick List Wizard</guilabel>. They will +work later in &VPL;, but, for this release, you should use the +<guilabel>Tables</guilabel> or <guilabel>Lists</guilabel> toolbars. +</para> +</note> + +<para> +To edit a tag (be it an image, an applet, or whatever), switch to the +<guilabel>Attribute Tree</guilabel>, accessible via +<menuchoice> +<guimenu>View</guimenu> +<guisubmenu>Tree views</guisubmenu> +</menuchoice>. Click on the tag you wish to edit, or, if you cannot access +it, click on an object contained by it. The <guilabel>Attribute +Tree</guilabel> will show the current tag name as well as a list of all its +parents and attributes. Currently &VPL; does not support, say, +&XHTML;+<acronym>MathML</acronym>, but you will see that you can edit +namespaces via this view. You can simply click on the +<guilabel>Value</guilabel> field and modify whatever you want. If you want +to access a parent of the current tag, then select it and the +<guilabel>Attribute Tree</guilabel> will load it. +</para> + +<para> +To delete a tag, we will use the <guilabel>Attribute Tree</guilabel>. Have +you noticed the two little red crosses at the top-right corner? The first one +deletes only the currently selected tag and, if the &HTML;/&XHTML; +specification does not allow some childs of the deleted tag to be child of +the parent tag of the tag set to be deleted, then they are also deleted, +and so on. The second cross will delete the selected tag as well as all of +its children, so be careful! +</para> + +</sect3> +</sect2> +</sect1> +</chapter> |