Apache OpenOffice Wiki - User contributions [en]

DomainDeveloper

2009-07-08T03:24:06Z

Robertzhou: /* Developers */

A mapping of names to OOo accounts.

Abbrev.:

* PL : Project Lead
* CL : Project Co-Lead
* CC : Community Council Member
* ESC : Engineering Steering Committee Member
* CVS : has write access to the OOo CVS repository

----

=== Developers ===

{| class="prettytable sortable"
|-
! Name || CVS || @openoffice.org || [[IRC Communication]] || Notes || Affiliation
|-
| [[User:Agerskov|Claus Agerskov]]|| || cs||Agerskov, cagerskov||PL Project Management Tool ([http://oopm.openoffice.org oopm])||AgerCon
|-
| Volker Ahrendt|| X || va||||||Sun Microsystems
|-
| Kai Ahrens|| X || ka || Kai_Ahrens ||PL Graphic Applications||Sun Microsystems
|-
| Rail Aliev || X || rail || rail || Ru and Tr NL Co-lead || Infra-Resource
|-
| Gene Anaya|| || ganaya||||||
|-
| [[User:JoostAndrae|Joost Andrae]]|| X || ja||ja_||CL qa, release testing en-US builds and releasing/uploading builds and releases||Sun Microsystems
|-
| [[User:ericb|Eric Bachard]] || X || ericb||ericb2|| PL Education, Mac OSX/Linux PPC port and vcl/impress hacker || [http://education.openoffice.org Education project], unaffiliated
|-
| Kai Backman|| || kaib ||KaiB||||
|-
| Sascha Ballach|| X || sab||||||
|-
| Jayant Balraj Madavi|| || jayant_madavi||aZEN_JM||Connectivity / Database||Novell, Inc.
|-
| Jörg Barfurth|| X || jb||JoergB||Configuration Util||Sun Microsystems
|-
| Omer Bar-or|| X || cremlae||cremlae||Mac porting||Google Summer of Code
|-
| Mathias Bauer|| X || mba||||PL Writer, CL Framework, XML||Sun Microsystems
|-
| Thorsten Behrens|| X || thb||thorsten||vcl/impress/toolkit visionary||Novell, Inc.
|-
| Thomas Benisch|| X || tbe||||Scripting framework||Sun Microsystems
|-
| Stephan Bergmann|| X || sb||||CL UDK||Sun Microsystems
|-
| Andreas Bille|| X || abi||||||Sun Microsystems
|-
| Éric Bischoff|| X || ebischoff||ebischoff||KDE A/B driver||Bureau Cornavin
|-
| Nick Blievers|| X || nick||||IRIX||
|-
| Daniel Boelzle|| X || dbo||||UNO core/bridges/packages||Sun Microsystems
|-
| Oliver Bolte|| X || obo||||RE||Sun Microsystems
|-
| Rafaella Braconi|| || coni||Rafaella ||PL l10n, Globalization Program Manager||Sun Microsystems
|-
| Michael Brauer|| X || mib||||PL XML||Sun Microsystems
|-
| Oliver Braun|| X || obr||obr||System Integration/Accessibility Hacker||Sun Microsystems
|-
| Andreas Bregas|| X || ab||||StarBasic||Sun Microsystems
|-
| Jörg Brunsmann|| || jbrunsmann||||UDK||
|-
| Jörg Budischewski|| || jbu||PyUNO hacker||||Sun Microsystems
|-
| Peter Burow|| X || pb||plumbumm||UI||Sun Microsystems
|-
| Aidan Butler|| || aidan||||XML filters||
|-
| Giuseppe Castagno || X || beppec56 || beppec56_ or beppe_c || PDF output
|-
| [[User:ScottCarr|Scott Carr]] || X || kcarr||kcarr||PL Documentation||Progbits
|-
| Colin Charles|| || drbyte||bytee||Malaysian native-lang project||bytebot.net
|-
| Jinhong Chen || || chainchen || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Jian Hong Cheng || X || chengjh || || Writer || IBM Corp.
|-
| Xiuzhi Cheng|| X || xzcheng || xiuzhi|| ESC,Xml,ODF|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Behrend Cornelius|| X || bc||||Wizards||Sun Microsystems
|-
| [[User:jza|Alexandro Colorado]]|| X || jza || jza|| CL [[OOoES|ES]] ||
|-
| Michael Cziebalski|| || mci||||||
|-
| [[User:pdefilippis|Pierre de Filippis]]|| X || pdefilippis||aliscafo||Mac OSX native porting||
|-
| Yuri Dario || || ydario || Paperino || OS/2 Port || Serenity Systems intl
|-
| Andrew Dent|| X ||ace_dent||ace_dent||ui/custom_images||
|-
| Naren Devaiah|| || ||ndev||Performance||Intel Corporation
|-
| Quangang Dong|| || donqg || dongqg || Layout || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Nitin Dongre|| || ||nitin_BITS||||Novell, Inc.(intern)
|-
| Radek Doulik|| || radekdoulik||rodo_||Canvas hacker||Novell, Inc.
|-
| Carsten Driesner|| X || cd|| cd_oo ||PL Framework||Sun Microsystems
|-
| Yunfen Du || X || duyunfen|| dyf|| Base ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-

| Herbert Duerr|| X || hdu||hdu_hh||GSL||Sun Microsystems
|-
| Oliver Düsterhoff|| X || od||Writer||||Sun Microsystems
|-
| [[User:bei|Bernd Eilers]]|| X || bei||rfc821||[[EIS]]||Sun Microsystems
|-
| René Engelhard|| X || rene||_rene_||config_office, Debian packager||Debian
|-
| [[User:Pereriksson|Per Eriksson]] || || pereriksson || || CL, MarCon Sweden ||
|-
| Yaqiong Fang || X || fangyq || fangyq|| Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Hubert Figuière|| X || hub || hub || PPTX || Novell, Inc.
|-
| Claudio F Filho|| || filhocf||filhocf||Brazilian portuguese Localization||BrOffice.org
|-
| Andre Fischer|| X || af||||Impress||Sun Microsystems
|-
| Uwe Fischer || X || ufi || ufiooo || Application Help || Sun Microsystems
|-
| Ken Foskey|| || waratah||waratah||config_office/dmake man||slug.org.au
|-
| Duncan Foster|| || dfoster||||||
|-
| David Fraser|| || davidfraser||davidfraser||South African translations, multilingual builds||translate.org.za
|-
| [[User:Nf|Nils Fuhrmann]]|| || nf||SunNF||||Sun Microsystems
|-
| Martin Gallwey|| X || mtg||marty_||XML/Writer/packaging||
|-
| Pierre-Andre Galmes || || pagalmes || pagalmes || Chart2 ||StarXpert
|-
| Tony Galmiche|| X || tonygalmiche||||CL FR native-lang project||
|-
| Sunil Gandhi|| || ||tyro||||NOSIP
|-
| Peng Gao || || Gao Peng|| Gao Peng || writer|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Zemin Gao || || gaozemin|| gaozm || Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sophie Gautier|| X || sgauti|| sophi || ||.
|-
| Vladimir Glazounov|| X || vg||||RE||Sun Microsystems
|-
| Laurent Godard || X || laurentgodard || lgodard || CC, PL Extensions, Fr Native-lang Project || inDesko/Nuxeo
|-
| Jody Goldberg|| X || jodygoldberg||jody||[[Calc]] spreadsheet-ness||Novell, Inc.
|-
| Dirk Grobler|| X || dg||||Database Access||Sun Microsystems
|-
| [[User:Sg|Steffen Grund]]|| X || sg|| || NetBeans Integration ||Sun Microsystems
|-
| Bettina Haberer|| || bh||||RFEOwner||Sun Microsystems
|-
| Bo Han || X || hanbo || hanbo || VBA Interop || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Ingrid Halama|| X || iha||||Chart||Sun Microsystems
|-
| Chris Halls|| X || haggai||haggai||Debian packager&misc. hacker||Credativ Ltd., Debian
|-
| Gregor Hartmann|| X || gh|| Lachs ||Testtool, gsicheck, buildbot||Sun Microsystems
|-
| Bustamam Harun|| || bustamam||||Malaysian stuff||
|-
| Kevin Hendricks|| X || khendricks||||PL Lingucomponent, PowerPC||
|-
| Con Hennessy|| || cphennessy||cph2 or cph_||hacker & former council person||OpenApp
|-
| Ivo Hinkelmann|| X || ihi||ivo||l10n tooling/general/RE||Sun Microsystems
|-
| Eric Hoch|| X || maveric||mav_eric||Mac Porting||
|-
| [[User:Lutz_Hoeger|Lutz Hoeger]]|| X || lh ||lutzh||||Sun Microsystems
|-
| Ilko Höpping|| X || ih||||||Sun Microsystems
|-
| Jan Holešovský|| X || kendy||kendy||KDE integration||Novell, Inc.
|-
| Martin Hollmichel|| X || mh||Ratte/Nesshof||Build Maestro, PL External, Tools, Porting, CC||Sun Microsystems
|-
| Karl Hong|| X || khong||||i18n, CJK expert||Sun Microsystems
|-
| Matthias Huetsch|| X || mhu||||Performance/strategy, PL UCB, CC, ESC||Sun Microsystems
|-
| Michael Hönnig|| X || mi||||PL API||
|-
| [[User:icobgr|Hristo Hristov]] || || icobgr || icobgr || PL Bulgarian native-lang project ||
|-
| Sven Jacobi|| X || sj||||Escherwizard||Sun Microsystems
|-
| Jörg Jahnke|| || jj||||tooling||Sun Microsystems
|-
| Christian Jansen|| || cj ||||Menu and Toolbar?||Sun Microsystems
|-
| Ocke Janssen|| X || oj||Base||||Sun Microsystems
|-
| Pavel Janík|| X || pjanik||paveljanik||PL Czech native-lang project, CL l10n, CC, ESC, l10n builds||
|-
| Berry Jia|| X || berryjia||||||Sun Microsystems
|-
| Mingfei Jia || X || jiamingfei || || Lotus Smart Suite filter,MS Word encryption || IBM Corp.
|-
| Chuang Jiang || || jiangc || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Jingchuan Kang|| || kangjingchuan || jingchuan || Surrogates in Unicode || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sunil Amitkumar Janki || || sjanki || sjanki || GNU Linux mipsel porter ||
|-
| Pascal Junck|| || pjunck||||||Sun Microsystems
|-
| [[User:pj@openoffice.org|Peter Junge]]|| X || pj|| peter13j|| OOo community contact for my Chinese Employer, QA||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Christian Junker|| || Cyb||christianju||API||Trees For Life
|-
| Etsushi Kato || X || ekato || || Mac OS X Port || Independent
|-
| Hirano Kazunari|| || khirano||||Japanese||
|-
| Dhananjay Keskar|| X || dkeskar ||dkeskar||Performance,Buildbot,cat-herder||Intel Corporation
|-
| Robert Kinsella|| || rkinsella||||||Sun Microsystems
|-
| Volodymyr Khrystynych|| || volody||||XML Filter||
|-
| Matthias Klose|| || doko||doko||Ubuntu, gcc, python packager||Canonical, Inc.
|-
| Laszlo Kovacs|| || lkovacs||||Documentation||
|-
| Tobias Krause|| X || tkr||||ucb||Sun Microsystems
|-
| Martin Kretzschmar|| X || mkretzschmar||martink||Gnome / Debian||Student
|-
| Will Lachance|| || wlach||wlach_||Word Perfect File Filters||Net Integration Technologies, Inc.
|-
| Thomas Lange|| X || tl||tl13||||Sun Microsystems
|-
| Lars Langhans|| X || lla||||||Sun Microsystems
|-
| Hans-Joachim Lankenau|| X || hjs||ause||dmake makefile expert, RE||Sun Microsystems
|-
| Németh László|| X || nemeth||||PL lingucomponent||
|-
| Jakob Lechner|| X || jakob_lechner||||Writer||Fabalabs
|-
| Michael Leibowitz|| X || mikeleib ||mikeleib||performance||Intel Corporation
|-
|Jian Li || || lijian || lijian|| Writer|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Wind Li|| X || windly||||Address books||
|-
| Xing Li || X || lixxing || || Accessibility || IBM Corp.
|-
|Yuan Li || || liyuan || || PyUNO, Async dialogs || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Weike Liang || || liangweike || liangweike || Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Ping Liao|| || pliao||||||
|-
| Tor Lillqvist|| X || tml||tml_||||Novell, Inc.
|-
| Fong Lin || X || pflin || Fong || VBA Interop, Scripting, CJK Enhancement || Novell, Inc.
|-
| Joachim Lingner|| X || jl||||Java, CLI||Sun Microsystems
|-
| Christian Lippka|| X || cl || cl ||Graphic Applications||Sun Microsystems
|-
|Jianli Liu || || liujl|| liujianli || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Mindy Liu|| || mindyliu||||||
|-
|[[User:liutao |Liu Tao ]] || X || liutao || liutao ||PL modularization ,PyUNO, Async dialogs,|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| YiSong Liu|| || Liu YiSong || Liu YiSong|| PYUNO || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|YU Liu || X || ch2000liuy || LiuYU || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yuhua Liu || || liuyuhua|| yuhua|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| [[User:Dl|Dieter Loeschky]]|| X || dl ||||PL: ODF Toolkit||Sun Microsystems
|-
| [[User:fl|Frank Loehmann]]|| X || fl ||frankl||PL [http://ux.openoffice.org User Experience]||Sun Microsystems
|-
| Philipp Lohmann|| X || pl||PhilippL||VCL/X11 (GSL) hacker||Sun Microsystems
|-
| Michel Loiseleur|| || mloiseleur|| coren`|| Bugfixes ||Linagora
|-
| Jackson Low|| X || xxjack12xx||||Porting||
|-
| Patrick Luby|| || pluby||||Mac||
|-
|Jingrong Luo || || Luo Jingrong|| Luo Jingrong|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Xugang Lv || || lvxg || lvxg || XML Writer || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Prasad Madhav || X || pmadhav || pmadhav || Buildbot || Intern@Intel
|-
| Babak Mahbod|| || bmahbod||||||
|-
| Martin Maher|| || mmaher||||Writer & Filter chap||
|-
| Nakata Maho|| X || maho||_maho_||PL QA, PL JA, FreeBSD guy||Independent
|-
|Yonggang Mao || X || maoyonggang|| maoyg|| Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yue Lv || || lvyue || lvyue || Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| John Marmion|| X || jmarmion||||||
|-
| Andreas Martens|| X || ama||||PL Writer||Sun Microsystems
|-
|-|
| Shane M Mathews|| X || smmathews|| smmathews ||[[Impress:_OpenGL_rendered_transitions]]||student
|-
| Frank Mau|| X || fma||||tooling||Sun Microsystems
|-
| [[User:smsm1|Shaun McDonald]] || X || smsm1 || shaunmcdonald || Mac Port, buildbot MacPort1 || Graduate
|-
| Caolán McNamara|| X || cmc||caolan||CL Writer & Filter man|| [http://www.redhat.com Red Hat Inc.]
|-
| Michael Meeks|| X || mmeeks||michael_||ugly hack-er, ESC||Novell, Inc.
|-
| Frank Meies|| X || fme||||Writer||Sun Microsystems
|-
| Federico Mena-Quintero|| || federicomena||federico||perfectionist||Novell, Inc.
|-
| Ismael Merzaq|| X || isma87||ismael_||Mac OSX native porting||Student
|-
| Michael Mi|| || mmi||||||
|-
| Björn Michaelsen|| X || b_michaelsen ||b_michaelsen|| Writer, Bookmarks, Performance, User Feedback Program ||Sun Microsystems
|-
| Björn Milcke|| X || bm||bm_||Chart||Sun Microsystems
|-
| Petr Mladek|| || pmladek||pmladek||SUSE RPMs, ooo-build releases||Novell, Inc.
|-
| Cyrille Moureaux|| X || cyrillem||Cyrille||||Sun Microsystems
|-
| [[User:Mmp|Matthias Müller-Prove]]|| X || mmp|| mprove|| [[User Experience]], http://ux.openoffice.org || Sun Microsystems
|-
| [[User:Bluedwarf|Takashi Nakamoto]]|| || bluedwarf|| || Japanese || Student
|-
| Jan Navrátil || X || jnavrati || jnavrati || || [http://www.redhat.com Red Hat Inc.]
|-
| Niklas Nebel|| X || nn||||PL [[Calc]]||Sun Microsystems
|-
| Christoph Neumann|| X || cn||||[[UnoApiTest]]||Sun Microsystems
|-
| Frank Neumann|| X || fne||||MacPort||Sun Microsystems
|-
| NicelKM|| X || mnicel||nicel||||Novell, Inc.
|-
| Jan Nieuwenhuizen|| X || jcn||janneke||Layout code, hacker ||Novell, Inc.
|-
| [[User:ChristophNoack|Christoph Noack]]|| X || christophnoack ||christoph_n||CL [http://ux.openoffice.org User Experience]||
|-
| Bertram Nolte|| || bnolte||||||
|-
| Tomas O'Connor|| || toconnor||||Scripting Framework||
|-
| Maximilian Odendahl|| X || mod||mod||[[Notes2]] [[SQL_Syntax_Highlighting]]|| Student / SEPT-Solutions
|-
| Takashi Ono || X || tono || || MinGW port || Independent
|-
| Lars Oppermann|| X || lo||||||
|-
| Rakesh Pandit || X || rakeshpandit|| chacha_chaudhry|| Education Project - Starmath/fix module warnings|| Education Project
|-
| Rodrigo Parra Novo|| X || rodarvus||rodarvus||Gnumeric/Abiword OpenDocument Format support and port to Maemo||INdT (Instituto Nokia de Tecnologia)
|-
| Pierre Pasteau|| X || pastea_p || pierrep|| Education Project, SeaMonkey migration || Education Project
|-
| Edward Peterlin|| X || OPENSTEP||||Mac||
|-
| [[User:Fpe|Frank Peters]]|| X || fpe||||CL Documentation||Sun Microsystems
|-
| Christof Pintaske|| X || cp||||||Sun Microsystems
|-
| Ron Piterman|| || rpiterman||||||
|-
| Sebastien Plisson|| X || plipli||plipli||Developer on Aqua port||OO Aqua Port
|-
| Noel Power|| || npower||noelp||VBA Interop, Scripting||Novell, Inc.
|-
| Nikolai Pretzell|| X || np || ||Autodoc, code quality||Sun Microsystems
|-
| Jonathan Pryor|| || jpryor || jonp || || Novell, Inc.
|-
| Canghua Qu|| || quch || Canghua || AutoTest, Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Volker Quetschke|| X || vq||vq||W32-tcsh/bash build environment and dmake Hacker, ESC||Gravity Waves
|-
| Tino Rachui|| X || tra||tinor||GSL/Unix Hacker||Sun Microsystems
|-
| Goran Rakić || X ||goranrakic || || Serbian Native-Lang PL ||
|-
| [[User:Kr|Kay Ramme]]|| X || kr||||PL UDK||Sun Microsystems
|-
| [[User:ErAck|Eike Rathke]]|| X || er||erAck||CL [[Calc]], engine; CL i18n; stricken with number formatter||Sun Microsystems
|-
| Michael Rauch|| X || mrauch||||NetBSD||
|-
| Jens-Heiner Rechtien|| X || hr||blauwal||RE; OOo SCM (CVS, CWS tooling); Porting; Compilers||Sun Microsystems
|-
| Daniel Rentz|| X || dr|| drr ||[[Calc]] Excel filter, UI||Sun Microsystems
|-
| Florian Reuter|| X || flr||||Writer filters||Novell, Inc.
|-
| Georg Richter|| X || grichter||georg||Base, native MySQL driver||MySQL AB
|-
| G. Roderick Singleton|| || grsingleton||grsingleton||Documentation||pathtech.org
|-
| Hennes Rohling|| X || hro||||GSL & Util||Sun Microsystems
|-
| Bibek Sahu|| || Bibek||bibek||Impress pieces||Trees For Life
|-
| Andreas Schlüns|| X || as||||Framework||Sun Microsystems
|-
| Ingo Schmidt|| X || is||||(Native) Installation||Sun Microsystems
|-
| [[User:Jsc|Jürgen Schmidt]]|| X || jsc||jsc||PL API, CL Extensions, UNO, SDK||Sun Microsystems
|-
| [[User:Schmidtm|Matthias Schmidt]] || || schmidtm || schmidtm || Mac OSX Aqua Port || Sun Microsystems
|-
| Stephan Schäfer|| X || ssa||ssa||VCL||Sun Microsystems
|-
| Frank Schönheit|| X || fs||FrankS||Database Access, Forms||Sun Microsystems
|-
| [[User:Sus|Svante Schubert]]|| X || sus||Svante||XML & ODFTOOLKIT co-lead, ODF TC, ODF SC Metadata||Sun Microsystems
|-
| [[User:Sts|Stella Schulze]]|| X || sts||||[http://ui.openoffice.org/nonav/VisualDesign/ Visual Design]||Sun Microsystems
|-
| Julian Seward || || sewardj || || valgrind ||
|-
| Darragh Sherwin|| || dsherwin||darragh||E-Legislation / E-GovSystems||Propylon
|-
|Lei shi || || shilei|| sl || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Wei Guo SHI || X || shiwg || || Accessibility and Smart Suite filter || IBM Corp.
|-
|[[User:Robertzhou | RobertZhou]]|| || robertzhou|| shizhoubo|| [[Framework]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Raul Siddhartha|| || rsiddhartha||raul||GTK File Selector||Novell, Inc.
|-
| Sarah Smith|| || ssmith||||||
|-
| [[User:mox|Mox Soini]] || X || mox || Moxed || Mac Porting ||
|-
| Rajesh Sola|| || rajeshsola||sola||misc.||NOSIP
|-
| Kai Sommerfeld|| X || kso||||manager & hacker||Sun Microsystems
|-
| Oliver Specht|| X || os||||PL UI||Sun Microsystems
|-
| Jörg Spindler|| || jspindler||||||
|-
| [[User:Rescue|Joey Stanford]] || || Rescue/k0fcc || Rinchen || CL [http://eo.openoffice.org/ Esperanto native-lang project] || [http://canonical.com Canonical] ||
|-
| Fridrich Štrba|| X || fridrich_strba||Fridrich||Word Perfect Hacker||Novell, Inc.
|-
| Keith Stribley|| X || kstribley||||Graphite fonts, Myanmar l10n||
|-
| Ulf Stroehler|| || us||||||Sun Microsystems
|-
| [[User:Muthusuba|Muthu Subramanian]]|| X || muthusuba||muthusuba||misc.||
|-
| Louis Suárez-Potts|| || louis||louis||Community Manager||Collab.net
|-
|Quanfa Tang || || tqfa|| tangquanfa|| Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| David Tardon || X || dtardon || dtardon || || [http://www.redhat.com Red Hat Inc.]
|-
| Stefan Taxhet|| X || st||stx12||CC, interpersonal problem fixer||Sun Microsystems
|-
| Armin Theissen|| || armin||||||
|-
| Caio Tiago Oliveira|| X || asrail||asrail||CL QA, release testing pt-BR builds||BrOffice.org
|-
| Jan Tietjens|| || tietjens||||||
|-
| Rüdiger Timm|| X || rt|| rtimm ||RE||Sun Microsystems
|-
| [[User:mt|Malte Timmermann]]|| X || mt|| Malte || Accessibility, Security, Performance||Sun Microsystems
|-
| Gerhard Tonn|| || tonn||||s390||
|-
| Willem van Dorp|| || willem.vandorp||||||
|-
| Tom Verbeek|| X || tv||||Wizards, Art team||Sun Microsystems
|-
| Sander Vesik|| || svesik||||||
|-
| Daniel Vogelheim|| X || dvo||||XML||
|-
| Mikhail Voitenko|| X || mav||mav||Framework||Sun Microsystems
|-
| Robert Vojta|| X || rvojta||rvojta||Mac OS X related issue||
|-
| Dirk Völzke|| X || dv||||Installation||Sun Microsystems
|-
| [[User:Sparcmoz|Jim Watson]]|| X || sparcmoz|| sparcmoz||GNU Linux sparc porter||clug.org.au
|-
| [[User:Weiz |Zhao Wei ]] || || weiz || weiz || Chart2 || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Armin Weiss|| X || aw||||||Sun Microsystems
|-
| Gerd Weiss|| X || gm||||RE||Sun Microsystems
|-
| Dan Williams|| X || fa||dcbw||Mac et. al. hacker|| [http://www.redhat.com Red Hat Inc.]
|-
|[[User:wuy|Yan Wu]] || X || wuy || ||Framework || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Stephan Wunderlich|| X || sw||||||
|-
| Antonio Xu|| X || antoxu || antoxu || Async dialogs, PRC improvements || Intel Corporation
|-
|Dehua Xu || || xudehua || xudh || Release || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Steve Yin || X || steve_yin || steve_yin || Microsoft Office file format, PDF, Accessibility, ODF || IBM Corp.
|-
| Kohei Yoshida|| X || kohei||kohei_||[[Calc]] hacker, Calc optimization solver developer||Novell, Inc.
|-
| Guoqiang Yu|| X || yugq || yugq|| Performance || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Xiaoyang Yu|| || || ||Disk block reordering||Intel Corporation
|-
| George Zahopoulos|| X || georgez||||||
|-
| Kurt Zenker|| X || kz||smoketester||RE||Sun Microsystems
|-
|Huajun Zhang || || zhanghuajun|| zhanghj|| SW ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|[[User:Zhangxiaofei|Xiaofei Zhang]]|| || Zhangxiaofei || zhangxiaofei/FelixZ || [[Framework]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Jianwei Zhao || || zhaojianwei || zhaojianwei || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sheng zhao|| X || jacky23 || ||OdfToolKit_odf4j || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Jeremy Zheng|| X || zhiming || Jeremy || Async dialogs, PRC improvements || Intel Corporation
|-
|[[User:majun|Jun Ma]]|| ||majun || || writer || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|}

=== QA Engineers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name ||CVS||@openoffice.org || [[IRC Communication]] || Interested modules || Notes || Affiliation
|-
| Stefan Baltzer||||sba||||writer||||Sun Microsystems
|-
| Thorsten Bosbach||X||tbo||||framework, testautomation||framework test automation||Sun Microsystems
|-
| Oliver Craemer||X||oc||||[[Calc]], testautomation||calc test automation||Sun Microsystems
|-
| Helge Delfs||X||hde||||testautomation, writer||Test automation||Sun Microsystems
|-
| Fredrik Haegg||X||fha||||writer, testautomation||Writer test automation||Sun Microsystems
|-
| Hasan Ilter||||hi||||writer, printing, pdf export||||Sun Microsystems
|-
| Michael Rüß||||mru||||writer, word im/export||||Sun Microsystems
|-
| Éric Savary||||es||||writer, accessibility||||Sun Microsystems
|-
| [[User:jsi|Joerg Sievers]]||X||jsi||jsi_sun||chart, xml, testautomation||Chart2, XML test automation||Sun Microsystems
|-
| Joerg Skottke||X||jsk||skotti||framework, qa/qatesttool||Framework test automation||Sun Microsystems
|-
| Marc Neumann||X||msc||||database, testautomation||Database access test automation||Sun Microsystems
|-
| Chris Lukasiak||||clu||||database||||Sun Microsystems
|-
| Frank Stecher||||fst||||[[Calc]]||||Sun Microsystems
|-
| Jack Warchold|||| jw||||writer, import/export filters||||Sun Microsystems
|-
| Uwe Luebbers||||ul||||framework||||Sun Microsystems
|-
| Thorsten Martens||||tm||||framework||||Sun Microsystems
|-
| Olaf Felka|||| of||of_sun||framework, installation||||Sun Microsystems
|-
| Thomas Klarhoefer||||kla||||chart||||Sun Microsystems
|-
| Wolfram Garten||X|| wg||||draw, impress||draw, impress test automation||Sun Microsystems
|-
| Christian Guenther||||cgu||||draw, impress||||Sun Microsystems
|-
| [[User:Thorsten_Ziehm|Thorsten Ziehm]]||||| thorstenziehm||||||QA lead||Sun Microsystems
|-
|}

We are tracking pending JCAs in the document [[Pending JCAs]].

== Related Pages ==
* [[Commit Rights]]
* [[Contributing Patches]]
* [[User_Experience/Community|User Experience Team]]
* A map of OOo developers around the world is available at http://www.frappr.com/ooodev, please add yourself to the map if you're involved in OOo development. It's just fun to see who's where :-)

[[Category:Development]]

DomainDeveloper

2009-07-08T03:19:48Z

Robertzhou: /* Developers */

A mapping of names to OOo accounts.

Abbrev.:

* PL : Project Lead
* CL : Project Co-Lead
* CC : Community Council Member
* ESC : Engineering Steering Committee Member
* CVS : has write access to the OOo CVS repository

----

=== Developers ===

{| class="prettytable sortable"
|-
! Name || CVS || @openoffice.org || [[IRC Communication]] || Notes || Affiliation
|-
| [[User:Agerskov|Claus Agerskov]]|| || cs||Agerskov, cagerskov||PL Project Management Tool ([http://oopm.openoffice.org oopm])||AgerCon
|-
| Volker Ahrendt|| X || va||||||Sun Microsystems
|-
| Kai Ahrens|| X || ka || Kai_Ahrens ||PL Graphic Applications||Sun Microsystems
|-
| Rail Aliev || X || rail || rail || Ru and Tr NL Co-lead || Infra-Resource
|-
| Gene Anaya|| || ganaya||||||
|-
| [[User:JoostAndrae|Joost Andrae]]|| X || ja||ja_||CL qa, release testing en-US builds and releasing/uploading builds and releases||Sun Microsystems
|-
| [[User:ericb|Eric Bachard]] || X || ericb||ericb2|| PL Education, Mac OSX/Linux PPC port and vcl/impress hacker || [http://education.openoffice.org Education project], unaffiliated
|-
| Kai Backman|| || kaib ||KaiB||||
|-
| Sascha Ballach|| X || sab||||||
|-
| Jayant Balraj Madavi|| || jayant_madavi||aZEN_JM||Connectivity / Database||Novell, Inc.
|-
| Jörg Barfurth|| X || jb||JoergB||Configuration Util||Sun Microsystems
|-
| Omer Bar-or|| X || cremlae||cremlae||Mac porting||Google Summer of Code
|-
| Mathias Bauer|| X || mba||||PL Writer, CL Framework, XML||Sun Microsystems
|-
| Thorsten Behrens|| X || thb||thorsten||vcl/impress/toolkit visionary||Novell, Inc.
|-
| Thomas Benisch|| X || tbe||||Scripting framework||Sun Microsystems
|-
| Stephan Bergmann|| X || sb||||CL UDK||Sun Microsystems
|-
| Andreas Bille|| X || abi||||||Sun Microsystems
|-
| Éric Bischoff|| X || ebischoff||ebischoff||KDE A/B driver||Bureau Cornavin
|-
| Nick Blievers|| X || nick||||IRIX||
|-
| Daniel Boelzle|| X || dbo||||UNO core/bridges/packages||Sun Microsystems
|-
| Oliver Bolte|| X || obo||||RE||Sun Microsystems
|-
| Rafaella Braconi|| || coni||Rafaella ||PL l10n, Globalization Program Manager||Sun Microsystems
|-
| Michael Brauer|| X || mib||||PL XML||Sun Microsystems
|-
| Oliver Braun|| X || obr||obr||System Integration/Accessibility Hacker||Sun Microsystems
|-
| Andreas Bregas|| X || ab||||StarBasic||Sun Microsystems
|-
| Jörg Brunsmann|| || jbrunsmann||||UDK||
|-
| Jörg Budischewski|| || jbu||PyUNO hacker||||Sun Microsystems
|-
| Peter Burow|| X || pb||plumbumm||UI||Sun Microsystems
|-
| Aidan Butler|| || aidan||||XML filters||
|-
| Giuseppe Castagno || X || beppec56 || beppec56_ or beppe_c || PDF output
|-
| [[User:ScottCarr|Scott Carr]] || X || kcarr||kcarr||PL Documentation||Progbits
|-
| Colin Charles|| || drbyte||bytee||Malaysian native-lang project||bytebot.net
|-
| Jinhong Chen || || chainchen || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Jian Hong Cheng || X || chengjh || || Writer || IBM Corp.
|-
| Xiuzhi Cheng|| X || xzcheng || xiuzhi|| ESC,Xml,ODF|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Behrend Cornelius|| X || bc||||Wizards||Sun Microsystems
|-
| [[User:jza|Alexandro Colorado]]|| X || jza || jza|| CL [[OOoES|ES]] ||
|-
| Michael Cziebalski|| || mci||||||
|-
| [[User:pdefilippis|Pierre de Filippis]]|| X || pdefilippis||aliscafo||Mac OSX native porting||
|-
| Yuri Dario || || ydario || Paperino || OS/2 Port || Serenity Systems intl
|-
| Andrew Dent|| X ||ace_dent||ace_dent||ui/custom_images||
|-
| Naren Devaiah|| || ||ndev||Performance||Intel Corporation
|-
| Quangang Dong|| || donqg || dongqg || Layout || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Nitin Dongre|| || ||nitin_BITS||||Novell, Inc.(intern)
|-
| Radek Doulik|| || radekdoulik||rodo_||Canvas hacker||Novell, Inc.
|-
| Carsten Driesner|| X || cd|| cd_oo ||PL Framework||Sun Microsystems
|-
| Yunfen Du || X || duyunfen|| dyf|| Base ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-

| Herbert Duerr|| X || hdu||hdu_hh||GSL||Sun Microsystems
|-
| Oliver Düsterhoff|| X || od||Writer||||Sun Microsystems
|-
| [[User:bei|Bernd Eilers]]|| X || bei||rfc821||[[EIS]]||Sun Microsystems
|-
| René Engelhard|| X || rene||_rene_||config_office, Debian packager||Debian
|-
| [[User:Pereriksson|Per Eriksson]] || || pereriksson || || CL, MarCon Sweden ||
|-
| Yaqiong Fang || X || fangyq || fangyq|| Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Hubert Figuière|| X || hub || hub || PPTX || Novell, Inc.
|-
| Claudio F Filho|| || filhocf||filhocf||Brazilian portuguese Localization||BrOffice.org
|-
| Andre Fischer|| X || af||||Impress||Sun Microsystems
|-
| Uwe Fischer || X || ufi || ufiooo || Application Help || Sun Microsystems
|-
| Ken Foskey|| || waratah||waratah||config_office/dmake man||slug.org.au
|-
| Duncan Foster|| || dfoster||||||
|-
| David Fraser|| || davidfraser||davidfraser||South African translations, multilingual builds||translate.org.za
|-
| [[User:Nf|Nils Fuhrmann]]|| || nf||SunNF||||Sun Microsystems
|-
| Martin Gallwey|| X || mtg||marty_||XML/Writer/packaging||
|-
| Pierre-Andre Galmes || || pagalmes || pagalmes || Chart2 ||StarXpert
|-
| Tony Galmiche|| X || tonygalmiche||||CL FR native-lang project||
|-
| Sunil Gandhi|| || ||tyro||||NOSIP
|-
| Peng Gao || || Gao Peng|| Gao Peng || writer|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Zemin Gao || || gaozemin|| gaozm || Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sophie Gautier|| X || sgauti|| sophi || ||.
|-
| Vladimir Glazounov|| X || vg||||RE||Sun Microsystems
|-
| Laurent Godard || X || laurentgodard || lgodard || CC, PL Extensions, Fr Native-lang Project || inDesko/Nuxeo
|-
| Jody Goldberg|| X || jodygoldberg||jody||[[Calc]] spreadsheet-ness||Novell, Inc.
|-
| Dirk Grobler|| X || dg||||Database Access||Sun Microsystems
|-
| [[User:Sg|Steffen Grund]]|| X || sg|| || NetBeans Integration ||Sun Microsystems
|-
| Bettina Haberer|| || bh||||RFEOwner||Sun Microsystems
|-
| Bo Han || X || hanbo || hanbo || VBA Interop || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Ingrid Halama|| X || iha||||Chart||Sun Microsystems
|-
| Chris Halls|| X || haggai||haggai||Debian packager&misc. hacker||Credativ Ltd., Debian
|-
| Gregor Hartmann|| X || gh|| Lachs ||Testtool, gsicheck, buildbot||Sun Microsystems
|-
| Bustamam Harun|| || bustamam||||Malaysian stuff||
|-
| Kevin Hendricks|| X || khendricks||||PL Lingucomponent, PowerPC||
|-
| Con Hennessy|| || cphennessy||cph2 or cph_||hacker & former council person||OpenApp
|-
| Ivo Hinkelmann|| X || ihi||ivo||l10n tooling/general/RE||Sun Microsystems
|-
| Eric Hoch|| X || maveric||mav_eric||Mac Porting||
|-
| [[User:Lutz_Hoeger|Lutz Hoeger]]|| X || lh ||lutzh||||Sun Microsystems
|-
| Ilko Höpping|| X || ih||||||Sun Microsystems
|-
| Jan Holešovský|| X || kendy||kendy||KDE integration||Novell, Inc.
|-
| Martin Hollmichel|| X || mh||Ratte/Nesshof||Build Maestro, PL External, Tools, Porting, CC||Sun Microsystems
|-
| Karl Hong|| X || khong||||i18n, CJK expert||Sun Microsystems
|-
| Matthias Huetsch|| X || mhu||||Performance/strategy, PL UCB, CC, ESC||Sun Microsystems
|-
| Michael Hönnig|| X || mi||||PL API||
|-
| [[User:icobgr|Hristo Hristov]] || || icobgr || icobgr || PL Bulgarian native-lang project ||
|-
| Sven Jacobi|| X || sj||||Escherwizard||Sun Microsystems
|-
| Jörg Jahnke|| || jj||||tooling||Sun Microsystems
|-
| Christian Jansen|| || cj ||||Menu and Toolbar?||Sun Microsystems
|-
| Ocke Janssen|| X || oj||Base||||Sun Microsystems
|-
| Pavel Janík|| X || pjanik||paveljanik||PL Czech native-lang project, CL l10n, CC, ESC, l10n builds||
|-
| Berry Jia|| X || berryjia||||||Sun Microsystems
|-
| Mingfei Jia || X || jiamingfei || || Lotus Smart Suite filter,MS Word encryption || IBM Corp.
|-
| Chuang Jiang || || jiangc || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Jingchuan Kang|| || kangjingchuan || jingchuan || Surrogates in Unicode || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sunil Amitkumar Janki || || sjanki || sjanki || GNU Linux mipsel porter ||
|-
| Pascal Junck|| || pjunck||||||Sun Microsystems
|-
| [[User:pj@openoffice.org|Peter Junge]]|| X || pj|| peter13j|| OOo community contact for my Chinese Employer, QA||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Christian Junker|| || Cyb||christianju||API||Trees For Life
|-
| Etsushi Kato || X || ekato || || Mac OS X Port || Independent
|-
| Hirano Kazunari|| || khirano||||Japanese||
|-
| Dhananjay Keskar|| X || dkeskar ||dkeskar||Performance,Buildbot,cat-herder||Intel Corporation
|-
| Robert Kinsella|| || rkinsella||||||Sun Microsystems
|-
| Volodymyr Khrystynych|| || volody||||XML Filter||
|-
| Matthias Klose|| || doko||doko||Ubuntu, gcc, python packager||Canonical, Inc.
|-
| Laszlo Kovacs|| || lkovacs||||Documentation||
|-
| Tobias Krause|| X || tkr||||ucb||Sun Microsystems
|-
| Martin Kretzschmar|| X || mkretzschmar||martink||Gnome / Debian||Student
|-
| Will Lachance|| || wlach||wlach_||Word Perfect File Filters||Net Integration Technologies, Inc.
|-
| Thomas Lange|| X || tl||tl13||||Sun Microsystems
|-
| Lars Langhans|| X || lla||||||Sun Microsystems
|-
| Hans-Joachim Lankenau|| X || hjs||ause||dmake makefile expert, RE||Sun Microsystems
|-
| Németh László|| X || nemeth||||PL lingucomponent||
|-
| Jakob Lechner|| X || jakob_lechner||||Writer||Fabalabs
|-
| Michael Leibowitz|| X || mikeleib ||mikeleib||performance||Intel Corporation
|-
|Jian Li || || lijian || lijian|| Writer|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Wind Li|| X || windly||||Address books||
|-
| Xing Li || X || lixxing || || Accessibility || IBM Corp.
|-
|Yuan Li || || liyuan || || PyUNO, Async dialogs || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Weike Liang || || liangweike || liangweike || Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Ping Liao|| || pliao||||||
|-
| Tor Lillqvist|| X || tml||tml_||||Novell, Inc.
|-
| Fong Lin || X || pflin || Fong || VBA Interop, Scripting, CJK Enhancement || Novell, Inc.
|-
| Joachim Lingner|| X || jl||||Java, CLI||Sun Microsystems
|-
| Christian Lippka|| X || cl || cl ||Graphic Applications||Sun Microsystems
|-
|Jianli Liu || || liujl|| liujianli || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Mindy Liu|| || mindyliu||||||
|-
|[[User:liutao |Liu Tao ]] || X || liutao || liutao ||PL modularization ,PyUNO, Async dialogs,|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| YiSong Liu|| || Liu YiSong || Liu YiSong|| PYUNO || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|YU Liu || X || ch2000liuy || LiuYU || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yuhua Liu || || liuyuhua|| yuhua|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| [[User:Dl|Dieter Loeschky]]|| X || dl ||||PL: ODF Toolkit||Sun Microsystems
|-
| [[User:fl|Frank Loehmann]]|| X || fl ||frankl||PL [http://ux.openoffice.org User Experience]||Sun Microsystems
|-
| Philipp Lohmann|| X || pl||PhilippL||VCL/X11 (GSL) hacker||Sun Microsystems
|-
| Michel Loiseleur|| || mloiseleur|| coren`|| Bugfixes ||Linagora
|-
| Jackson Low|| X || xxjack12xx||||Porting||
|-
| Patrick Luby|| || pluby||||Mac||
|-
|Jingrong Luo || || Luo Jingrong|| Luo Jingrong|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Xugang Lv || || lvxg || lvxg || XML Writer || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Prasad Madhav || X || pmadhav || pmadhav || Buildbot || Intern@Intel
|-
| Babak Mahbod|| || bmahbod||||||
|-
| Martin Maher|| || mmaher||||Writer & Filter chap||
|-
| Nakata Maho|| X || maho||_maho_||PL QA, PL JA, FreeBSD guy||Independent
|-
|Yonggang Mao || X || maoyonggang|| maoyg|| Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yue Lv || || lvyue || lvyue || Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| John Marmion|| X || jmarmion||||||
|-
| Andreas Martens|| X || ama||||PL Writer||Sun Microsystems
|-
|-|
| Shane M Mathews|| X || smmathews|| smmathews ||[[Impress:_OpenGL_rendered_transitions]]||student
|-
| Frank Mau|| X || fma||||tooling||Sun Microsystems
|-
| [[User:smsm1|Shaun McDonald]] || X || smsm1 || shaunmcdonald || Mac Port, buildbot MacPort1 || Graduate
|-
| Caolán McNamara|| X || cmc||caolan||CL Writer & Filter man|| [http://www.redhat.com Red Hat Inc.]
|-
| Michael Meeks|| X || mmeeks||michael_||ugly hack-er, ESC||Novell, Inc.
|-
| Frank Meies|| X || fme||||Writer||Sun Microsystems
|-
| Federico Mena-Quintero|| || federicomena||federico||perfectionist||Novell, Inc.
|-
| Ismael Merzaq|| X || isma87||ismael_||Mac OSX native porting||Student
|-
| Michael Mi|| || mmi||||||
|-
| Björn Michaelsen|| X || b_michaelsen ||b_michaelsen|| Writer, Bookmarks, Performance, User Feedback Program ||Sun Microsystems
|-
| Björn Milcke|| X || bm||bm_||Chart||Sun Microsystems
|-
| Petr Mladek|| || pmladek||pmladek||SUSE RPMs, ooo-build releases||Novell, Inc.
|-
| Cyrille Moureaux|| X || cyrillem||Cyrille||||Sun Microsystems
|-
| [[User:Mmp|Matthias Müller-Prove]]|| X || mmp|| mprove|| [[User Experience]], http://ux.openoffice.org || Sun Microsystems
|-
| [[User:Bluedwarf|Takashi Nakamoto]]|| || bluedwarf|| || Japanese || Student
|-
| Jan Navrátil || X || jnavrati || jnavrati || || [http://www.redhat.com Red Hat Inc.]
|-
| Niklas Nebel|| X || nn||||PL [[Calc]]||Sun Microsystems
|-
| Christoph Neumann|| X || cn||||[[UnoApiTest]]||Sun Microsystems
|-
| Frank Neumann|| X || fne||||MacPort||Sun Microsystems
|-
| NicelKM|| X || mnicel||nicel||||Novell, Inc.
|-
| Jan Nieuwenhuizen|| X || jcn||janneke||Layout code, hacker ||Novell, Inc.
|-
| [[User:ChristophNoack|Christoph Noack]]|| X || christophnoack ||christoph_n||CL [http://ux.openoffice.org User Experience]||
|-
| Bertram Nolte|| || bnolte||||||
|-
| Tomas O'Connor|| || toconnor||||Scripting Framework||
|-
| Maximilian Odendahl|| X || mod||mod||[[Notes2]] [[SQL_Syntax_Highlighting]]|| Student / SEPT-Solutions
|-
| Takashi Ono || X || tono || || MinGW port || Independent
|-
| Lars Oppermann|| X || lo||||||
|-
| Rakesh Pandit || X || rakeshpandit|| chacha_chaudhry|| Education Project - Starmath/fix module warnings|| Education Project
|-
| Rodrigo Parra Novo|| X || rodarvus||rodarvus||Gnumeric/Abiword OpenDocument Format support and port to Maemo||INdT (Instituto Nokia de Tecnologia)
|-
| Pierre Pasteau|| X || pastea_p || pierrep|| Education Project, SeaMonkey migration || Education Project
|-
| Edward Peterlin|| X || OPENSTEP||||Mac||
|-
| [[User:Fpe|Frank Peters]]|| X || fpe||||CL Documentation||Sun Microsystems
|-
| Christof Pintaske|| X || cp||||||Sun Microsystems
|-
| Ron Piterman|| || rpiterman||||||
|-
| Sebastien Plisson|| X || plipli||plipli||Developer on Aqua port||OO Aqua Port
|-
| Noel Power|| || npower||noelp||VBA Interop, Scripting||Novell, Inc.
|-
| Nikolai Pretzell|| X || np || ||Autodoc, code quality||Sun Microsystems
|-
| Jonathan Pryor|| || jpryor || jonp || || Novell, Inc.
|-
| Canghua Qu|| || quch || Canghua || AutoTest, Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Volker Quetschke|| X || vq||vq||W32-tcsh/bash build environment and dmake Hacker, ESC||Gravity Waves
|-
| Tino Rachui|| X || tra||tinor||GSL/Unix Hacker||Sun Microsystems
|-
| Goran Rakić || X ||goranrakic || || Serbian Native-Lang PL ||
|-
| [[User:Kr|Kay Ramme]]|| X || kr||||PL UDK||Sun Microsystems
|-
| [[User:ErAck|Eike Rathke]]|| X || er||erAck||CL [[Calc]], engine; CL i18n; stricken with number formatter||Sun Microsystems
|-
| Michael Rauch|| X || mrauch||||NetBSD||
|-
| Jens-Heiner Rechtien|| X || hr||blauwal||RE; OOo SCM (CVS, CWS tooling); Porting; Compilers||Sun Microsystems
|-
| Daniel Rentz|| X || dr|| drr ||[[Calc]] Excel filter, UI||Sun Microsystems
|-
| Florian Reuter|| X || flr||||Writer filters||Novell, Inc.
|-
| Georg Richter|| X || grichter||georg||Base, native MySQL driver||MySQL AB
|-
| G. Roderick Singleton|| || grsingleton||grsingleton||Documentation||pathtech.org
|-
| Hennes Rohling|| X || hro||||GSL & Util||Sun Microsystems
|-
| Bibek Sahu|| || Bibek||bibek||Impress pieces||Trees For Life
|-
| Andreas Schlüns|| X || as||||Framework||Sun Microsystems
|-
| Ingo Schmidt|| X || is||||(Native) Installation||Sun Microsystems
|-
| [[User:Jsc|Jürgen Schmidt]]|| X || jsc||jsc||PL API, CL Extensions, UNO, SDK||Sun Microsystems
|-
| [[User:Schmidtm|Matthias Schmidt]] || || schmidtm || schmidtm || Mac OSX Aqua Port || Sun Microsystems
|-
| Stephan Schäfer|| X || ssa||ssa||VCL||Sun Microsystems
|-
| Frank Schönheit|| X || fs||FrankS||Database Access, Forms||Sun Microsystems
|-
| [[User:Sus|Svante Schubert]]|| X || sus||Svante||XML & ODFTOOLKIT co-lead, ODF TC, ODF SC Metadata||Sun Microsystems
|-
| [[User:Sts|Stella Schulze]]|| X || sts||||[http://ui.openoffice.org/nonav/VisualDesign/ Visual Design]||Sun Microsystems
|-
| Julian Seward || || sewardj || || valgrind ||
|-
| Darragh Sherwin|| || dsherwin||darragh||E-Legislation / E-GovSystems||Propylon
|-
|Lei shi || || shilei|| sl || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Wei Guo SHI || X || shiwg || || Accessibility and Smart Suite filter || IBM Corp.
|-
|[[User:Robertzhou|zhoubo Shi]]|| || robertzhou|| shizhoubo|| [[Framework]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Raul Siddhartha|| || rsiddhartha||raul||GTK File Selector||Novell, Inc.
|-
| Sarah Smith|| || ssmith||||||
|-
| [[User:mox|Mox Soini]] || X || mox || Moxed || Mac Porting ||
|-
| Rajesh Sola|| || rajeshsola||sola||misc.||NOSIP
|-
| Kai Sommerfeld|| X || kso||||manager & hacker||Sun Microsystems
|-
| Oliver Specht|| X || os||||PL UI||Sun Microsystems
|-
| Jörg Spindler|| || jspindler||||||
|-
| [[User:Rescue|Joey Stanford]] || || Rescue/k0fcc || Rinchen || CL [http://eo.openoffice.org/ Esperanto native-lang project] || [http://canonical.com Canonical] ||
|-
| Fridrich Štrba|| X || fridrich_strba||Fridrich||Word Perfect Hacker||Novell, Inc.
|-
| Keith Stribley|| X || kstribley||||Graphite fonts, Myanmar l10n||
|-
| Ulf Stroehler|| || us||||||Sun Microsystems
|-
| [[User:Muthusuba|Muthu Subramanian]]|| X || muthusuba||muthusuba||misc.||
|-
| Louis Suárez-Potts|| || louis||louis||Community Manager||Collab.net
|-
|Quanfa Tang || || tqfa|| tangquanfa|| Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| David Tardon || X || dtardon || dtardon || || [http://www.redhat.com Red Hat Inc.]
|-
| Stefan Taxhet|| X || st||stx12||CC, interpersonal problem fixer||Sun Microsystems
|-
| Armin Theissen|| || armin||||||
|-
| Caio Tiago Oliveira|| X || asrail||asrail||CL QA, release testing pt-BR builds||BrOffice.org
|-
| Jan Tietjens|| || tietjens||||||
|-
| Rüdiger Timm|| X || rt|| rtimm ||RE||Sun Microsystems
|-
| [[User:mt|Malte Timmermann]]|| X || mt|| Malte || Accessibility, Security, Performance||Sun Microsystems
|-
| Gerhard Tonn|| || tonn||||s390||
|-
| Willem van Dorp|| || willem.vandorp||||||
|-
| Tom Verbeek|| X || tv||||Wizards, Art team||Sun Microsystems
|-
| Sander Vesik|| || svesik||||||
|-
| Daniel Vogelheim|| X || dvo||||XML||
|-
| Mikhail Voitenko|| X || mav||mav||Framework||Sun Microsystems
|-
| Robert Vojta|| X || rvojta||rvojta||Mac OS X related issue||
|-
| Dirk Völzke|| X || dv||||Installation||Sun Microsystems
|-
| [[User:Sparcmoz|Jim Watson]]|| X || sparcmoz|| sparcmoz||GNU Linux sparc porter||clug.org.au
|-
| [[User:Weiz |Zhao Wei ]] || || weiz || weiz || Chart2 || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Armin Weiss|| X || aw||||||Sun Microsystems
|-
| Gerd Weiss|| X || gm||||RE||Sun Microsystems
|-
| Dan Williams|| X || fa||dcbw||Mac et. al. hacker|| [http://www.redhat.com Red Hat Inc.]
|-
|[[User:wuy|Yan Wu]] || X || wuy || ||Framework || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Stephan Wunderlich|| X || sw||||||
|-
| Antonio Xu|| X || antoxu || antoxu || Async dialogs, PRC improvements || Intel Corporation
|-
|Dehua Xu || || xudehua || xudh || Release || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Steve Yin || X || steve_yin || steve_yin || Microsoft Office file format, PDF, Accessibility, ODF || IBM Corp.
|-
| Kohei Yoshida|| X || kohei||kohei_||[[Calc]] hacker, Calc optimization solver developer||Novell, Inc.
|-
| Guoqiang Yu|| X || yugq || yugq|| Performance || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Xiaoyang Yu|| || || ||Disk block reordering||Intel Corporation
|-
| George Zahopoulos|| X || georgez||||||
|-
| Kurt Zenker|| X || kz||smoketester||RE||Sun Microsystems
|-
|Huajun Zhang || || zhanghuajun|| zhanghj|| SW ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|[[User:Zhangxiaofei|Xiaofei Zhang]]|| || Zhangxiaofei || zhangxiaofei/FelixZ || [[Framework]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Jianwei Zhao || || zhaojianwei || zhaojianwei || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sheng zhao|| X || jacky23 || ||OdfToolKit_odf4j || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Jeremy Zheng|| X || zhiming || Jeremy || Async dialogs, PRC improvements || Intel Corporation
|-
|[[User:majun|Jun Ma]]|| ||majun || || writer || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|}

=== QA Engineers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name ||CVS||@openoffice.org || [[IRC Communication]] || Interested modules || Notes || Affiliation
|-
| Stefan Baltzer||||sba||||writer||||Sun Microsystems
|-
| Thorsten Bosbach||X||tbo||||framework, testautomation||framework test automation||Sun Microsystems
|-
| Oliver Craemer||X||oc||||[[Calc]], testautomation||calc test automation||Sun Microsystems
|-
| Helge Delfs||X||hde||||testautomation, writer||Test automation||Sun Microsystems
|-
| Fredrik Haegg||X||fha||||writer, testautomation||Writer test automation||Sun Microsystems
|-
| Hasan Ilter||||hi||||writer, printing, pdf export||||Sun Microsystems
|-
| Michael Rüß||||mru||||writer, word im/export||||Sun Microsystems
|-
| Éric Savary||||es||||writer, accessibility||||Sun Microsystems
|-
| [[User:jsi|Joerg Sievers]]||X||jsi||jsi_sun||chart, xml, testautomation||Chart2, XML test automation||Sun Microsystems
|-
| Joerg Skottke||X||jsk||skotti||framework, qa/qatesttool||Framework test automation||Sun Microsystems
|-
| Marc Neumann||X||msc||||database, testautomation||Database access test automation||Sun Microsystems
|-
| Chris Lukasiak||||clu||||database||||Sun Microsystems
|-
| Frank Stecher||||fst||||[[Calc]]||||Sun Microsystems
|-
| Jack Warchold|||| jw||||writer, import/export filters||||Sun Microsystems
|-
| Uwe Luebbers||||ul||||framework||||Sun Microsystems
|-
| Thorsten Martens||||tm||||framework||||Sun Microsystems
|-
| Olaf Felka|||| of||of_sun||framework, installation||||Sun Microsystems
|-
| Thomas Klarhoefer||||kla||||chart||||Sun Microsystems
|-
| Wolfram Garten||X|| wg||||draw, impress||draw, impress test automation||Sun Microsystems
|-
| Christian Guenther||||cgu||||draw, impress||||Sun Microsystems
|-
| [[User:Thorsten_Ziehm|Thorsten Ziehm]]||||| thorstenziehm||||||QA lead||Sun Microsystems
|-
|}

We are tracking pending JCAs in the document [[Pending JCAs]].

== Related Pages ==
* [[Commit Rights]]
* [[Contributing Patches]]
* [[User_Experience/Community|User Experience Team]]
* A map of OOo developers around the world is available at http://www.frappr.com/ooodev, please add yourself to the map if you're involved in OOo development. It's just fun to see who's where :-)

[[Category:Development]]

DomainDeveloper

2009-07-08T03:13:21Z

Robertzhou: /* Developers */

A mapping of names to OOo accounts.

Abbrev.:

* PL : Project Lead
* CL : Project Co-Lead
* CC : Community Council Member
* ESC : Engineering Steering Committee Member
* CVS : has write access to the OOo CVS repository

----

=== Developers ===

{| class="prettytable sortable"
|-
! Name || CVS || @openoffice.org || [[IRC Communication]] || Notes || Affiliation
|-
| [[User:Agerskov|Claus Agerskov]]|| || cs||Agerskov, cagerskov||PL Project Management Tool ([http://oopm.openoffice.org oopm])||AgerCon
|-
| Volker Ahrendt|| X || va||||||Sun Microsystems
|-
| Kai Ahrens|| X || ka || Kai_Ahrens ||PL Graphic Applications||Sun Microsystems
|-
| Rail Aliev || X || rail || rail || Ru and Tr NL Co-lead || Infra-Resource
|-
| Gene Anaya|| || ganaya||||||
|-
| [[User:JoostAndrae|Joost Andrae]]|| X || ja||ja_||CL qa, release testing en-US builds and releasing/uploading builds and releases||Sun Microsystems
|-
| [[User:ericb|Eric Bachard]] || X || ericb||ericb2|| PL Education, Mac OSX/Linux PPC port and vcl/impress hacker || [http://education.openoffice.org Education project], unaffiliated
|-
| Kai Backman|| || kaib ||KaiB||||
|-
| Sascha Ballach|| X || sab||||||
|-
| Jayant Balraj Madavi|| || jayant_madavi||aZEN_JM||Connectivity / Database||Novell, Inc.
|-
| Jörg Barfurth|| X || jb||JoergB||Configuration Util||Sun Microsystems
|-
| Omer Bar-or|| X || cremlae||cremlae||Mac porting||Google Summer of Code
|-
| Mathias Bauer|| X || mba||||PL Writer, CL Framework, XML||Sun Microsystems
|-
| Thorsten Behrens|| X || thb||thorsten||vcl/impress/toolkit visionary||Novell, Inc.
|-
| Thomas Benisch|| X || tbe||||Scripting framework||Sun Microsystems
|-
| Stephan Bergmann|| X || sb||||CL UDK||Sun Microsystems
|-
| Andreas Bille|| X || abi||||||Sun Microsystems
|-
| Éric Bischoff|| X || ebischoff||ebischoff||KDE A/B driver||Bureau Cornavin
|-
| Nick Blievers|| X || nick||||IRIX||
|-
| Daniel Boelzle|| X || dbo||||UNO core/bridges/packages||Sun Microsystems
|-
| Oliver Bolte|| X || obo||||RE||Sun Microsystems
|-
| Rafaella Braconi|| || coni||Rafaella ||PL l10n, Globalization Program Manager||Sun Microsystems
|-
| Michael Brauer|| X || mib||||PL XML||Sun Microsystems
|-
| Oliver Braun|| X || obr||obr||System Integration/Accessibility Hacker||Sun Microsystems
|-
| Andreas Bregas|| X || ab||||StarBasic||Sun Microsystems
|-
| Jörg Brunsmann|| || jbrunsmann||||UDK||
|-
| Jörg Budischewski|| || jbu||PyUNO hacker||||Sun Microsystems
|-
| Peter Burow|| X || pb||plumbumm||UI||Sun Microsystems
|-
| Aidan Butler|| || aidan||||XML filters||
|-
| Giuseppe Castagno || X || beppec56 || beppec56_ or beppe_c || PDF output
|-
| [[User:ScottCarr|Scott Carr]] || X || kcarr||kcarr||PL Documentation||Progbits
|-
| Colin Charles|| || drbyte||bytee||Malaysian native-lang project||bytebot.net
|-
| Jinhong Chen || || chainchen || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Jian Hong Cheng || X || chengjh || || Writer || IBM Corp.
|-
| Xiuzhi Cheng|| X || xzcheng || xiuzhi|| ESC,Xml,ODF|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Behrend Cornelius|| X || bc||||Wizards||Sun Microsystems
|-
| [[User:jza|Alexandro Colorado]]|| X || jza || jza|| CL [[OOoES|ES]] ||
|-
| Michael Cziebalski|| || mci||||||
|-
| [[User:pdefilippis|Pierre de Filippis]]|| X || pdefilippis||aliscafo||Mac OSX native porting||
|-
| Yuri Dario || || ydario || Paperino || OS/2 Port || Serenity Systems intl
|-
| Andrew Dent|| X ||ace_dent||ace_dent||ui/custom_images||
|-
| Naren Devaiah|| || ||ndev||Performance||Intel Corporation
|-
| Quangang Dong|| || donqg || dongqg || Layout || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Nitin Dongre|| || ||nitin_BITS||||Novell, Inc.(intern)
|-
| Radek Doulik|| || radekdoulik||rodo_||Canvas hacker||Novell, Inc.
|-
| Carsten Driesner|| X || cd|| cd_oo ||PL Framework||Sun Microsystems
|-
| Yunfen Du || X || duyunfen|| dyf|| Base ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-

| Herbert Duerr|| X || hdu||hdu_hh||GSL||Sun Microsystems
|-
| Oliver Düsterhoff|| X || od||Writer||||Sun Microsystems
|-
| [[User:bei|Bernd Eilers]]|| X || bei||rfc821||[[EIS]]||Sun Microsystems
|-
| René Engelhard|| X || rene||_rene_||config_office, Debian packager||Debian
|-
| [[User:Pereriksson|Per Eriksson]] || || pereriksson || || CL, MarCon Sweden ||
|-
| Yaqiong Fang || X || fangyq || fangyq|| Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Hubert Figuière|| X || hub || hub || PPTX || Novell, Inc.
|-
| Claudio F Filho|| || filhocf||filhocf||Brazilian portuguese Localization||BrOffice.org
|-
| Andre Fischer|| X || af||||Impress||Sun Microsystems
|-
| Uwe Fischer || X || ufi || ufiooo || Application Help || Sun Microsystems
|-
| Ken Foskey|| || waratah||waratah||config_office/dmake man||slug.org.au
|-
| Duncan Foster|| || dfoster||||||
|-
| David Fraser|| || davidfraser||davidfraser||South African translations, multilingual builds||translate.org.za
|-
| [[User:Nf|Nils Fuhrmann]]|| || nf||SunNF||||Sun Microsystems
|-
| Martin Gallwey|| X || mtg||marty_||XML/Writer/packaging||
|-
| Pierre-Andre Galmes || || pagalmes || pagalmes || Chart2 ||StarXpert
|-
| Tony Galmiche|| X || tonygalmiche||||CL FR native-lang project||
|-
| Sunil Gandhi|| || ||tyro||||NOSIP
|-
| Peng Gao || || Gao Peng|| Gao Peng || writer|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Zemin Gao || || gaozemin|| gaozm || Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sophie Gautier|| X || sgauti|| sophi || ||.
|-
| Vladimir Glazounov|| X || vg||||RE||Sun Microsystems
|-
| Laurent Godard || X || laurentgodard || lgodard || CC, PL Extensions, Fr Native-lang Project || inDesko/Nuxeo
|-
| Jody Goldberg|| X || jodygoldberg||jody||[[Calc]] spreadsheet-ness||Novell, Inc.
|-
| Dirk Grobler|| X || dg||||Database Access||Sun Microsystems
|-
| [[User:Sg|Steffen Grund]]|| X || sg|| || NetBeans Integration ||Sun Microsystems
|-
| Bettina Haberer|| || bh||||RFEOwner||Sun Microsystems
|-
| Bo Han || X || hanbo || hanbo || VBA Interop || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Ingrid Halama|| X || iha||||Chart||Sun Microsystems
|-
| Chris Halls|| X || haggai||haggai||Debian packager&misc. hacker||Credativ Ltd., Debian
|-
| Gregor Hartmann|| X || gh|| Lachs ||Testtool, gsicheck, buildbot||Sun Microsystems
|-
| Bustamam Harun|| || bustamam||||Malaysian stuff||
|-
| Kevin Hendricks|| X || khendricks||||PL Lingucomponent, PowerPC||
|-
| Con Hennessy|| || cphennessy||cph2 or cph_||hacker & former council person||OpenApp
|-
| Ivo Hinkelmann|| X || ihi||ivo||l10n tooling/general/RE||Sun Microsystems
|-
| Eric Hoch|| X || maveric||mav_eric||Mac Porting||
|-
| [[User:Lutz_Hoeger|Lutz Hoeger]]|| X || lh ||lutzh||||Sun Microsystems
|-
| Ilko Höpping|| X || ih||||||Sun Microsystems
|-
| Jan Holešovský|| X || kendy||kendy||KDE integration||Novell, Inc.
|-
| Martin Hollmichel|| X || mh||Ratte/Nesshof||Build Maestro, PL External, Tools, Porting, CC||Sun Microsystems
|-
| Karl Hong|| X || khong||||i18n, CJK expert||Sun Microsystems
|-
| Matthias Huetsch|| X || mhu||||Performance/strategy, PL UCB, CC, ESC||Sun Microsystems
|-
| Michael Hönnig|| X || mi||||PL API||
|-
| [[User:icobgr|Hristo Hristov]] || || icobgr || icobgr || PL Bulgarian native-lang project ||
|-
| Sven Jacobi|| X || sj||||Escherwizard||Sun Microsystems
|-
| Jörg Jahnke|| || jj||||tooling||Sun Microsystems
|-
| Christian Jansen|| || cj ||||Menu and Toolbar?||Sun Microsystems
|-
| Ocke Janssen|| X || oj||Base||||Sun Microsystems
|-
| Pavel Janík|| X || pjanik||paveljanik||PL Czech native-lang project, CL l10n, CC, ESC, l10n builds||
|-
| Berry Jia|| X || berryjia||||||Sun Microsystems
|-
| Mingfei Jia || X || jiamingfei || || Lotus Smart Suite filter,MS Word encryption || IBM Corp.
|-
| Chuang Jiang || || jiangc || || || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Jingchuan Kang|| || kangjingchuan || jingchuan || Surrogates in Unicode || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sunil Amitkumar Janki || || sjanki || sjanki || GNU Linux mipsel porter ||
|-
| Pascal Junck|| || pjunck||||||Sun Microsystems
|-
| [[User:pj@openoffice.org|Peter Junge]]|| X || pj|| peter13j|| OOo community contact for my Chinese Employer, QA||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Christian Junker|| || Cyb||christianju||API||Trees For Life
|-
| Etsushi Kato || X || ekato || || Mac OS X Port || Independent
|-
| Hirano Kazunari|| || khirano||||Japanese||
|-
| Dhananjay Keskar|| X || dkeskar ||dkeskar||Performance,Buildbot,cat-herder||Intel Corporation
|-
| Robert Kinsella|| || rkinsella||||||Sun Microsystems
|-
| Volodymyr Khrystynych|| || volody||||XML Filter||
|-
| Matthias Klose|| || doko||doko||Ubuntu, gcc, python packager||Canonical, Inc.
|-
| Laszlo Kovacs|| || lkovacs||||Documentation||
|-
| Tobias Krause|| X || tkr||||ucb||Sun Microsystems
|-
| Martin Kretzschmar|| X || mkretzschmar||martink||Gnome / Debian||Student
|-
| Will Lachance|| || wlach||wlach_||Word Perfect File Filters||Net Integration Technologies, Inc.
|-
| Thomas Lange|| X || tl||tl13||||Sun Microsystems
|-
| Lars Langhans|| X || lla||||||Sun Microsystems
|-
| Hans-Joachim Lankenau|| X || hjs||ause||dmake makefile expert, RE||Sun Microsystems
|-
| Németh László|| X || nemeth||||PL lingucomponent||
|-
| Jakob Lechner|| X || jakob_lechner||||Writer||Fabalabs
|-
| Michael Leibowitz|| X || mikeleib ||mikeleib||performance||Intel Corporation
|-
|Jian Li || || lijian || lijian|| Writer|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Wind Li|| X || windly||||Address books||
|-
| Xing Li || X || lixxing || || Accessibility || IBM Corp.
|-
|Yuan Li || || liyuan || || PyUNO, Async dialogs || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Weike Liang || || liangweike || liangweike || Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Ping Liao|| || pliao||||||
|-
| Tor Lillqvist|| X || tml||tml_||||Novell, Inc.
|-
| Fong Lin || X || pflin || Fong || VBA Interop, Scripting, CJK Enhancement || Novell, Inc.
|-
| Joachim Lingner|| X || jl||||Java, CLI||Sun Microsystems
|-
| Christian Lippka|| X || cl || cl ||Graphic Applications||Sun Microsystems
|-
|Jianli Liu || || liujl|| liujianli || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Mindy Liu|| || mindyliu||||||
|-
|[[User:liutao |Liu Tao ]] || X || liutao || liutao ||PL modularization ,PyUNO, Async dialogs,|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| YiSong Liu|| || Liu YiSong || Liu YiSong|| PYUNO || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|YU Liu || X || ch2000liuy || LiuYU || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yuhua Liu || || liuyuhua|| yuhua|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| [[User:Dl|Dieter Loeschky]]|| X || dl ||||PL: ODF Toolkit||Sun Microsystems
|-
| [[User:fl|Frank Loehmann]]|| X || fl ||frankl||PL [http://ux.openoffice.org User Experience]||Sun Microsystems
|-
| Philipp Lohmann|| X || pl||PhilippL||VCL/X11 (GSL) hacker||Sun Microsystems
|-
| Michel Loiseleur|| || mloiseleur|| coren`|| Bugfixes ||Linagora
|-
| Jackson Low|| X || xxjack12xx||||Porting||
|-
| Patrick Luby|| || pluby||||Mac||
|-
|Jingrong Luo || || Luo Jingrong|| Luo Jingrong|| ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Xugang Lv || || lvxg || lvxg || XML Writer || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Prasad Madhav || X || pmadhav || pmadhav || Buildbot || Intern@Intel
|-
| Babak Mahbod|| || bmahbod||||||
|-
| Martin Maher|| || mmaher||||Writer & Filter chap||
|-
| Nakata Maho|| X || maho||_maho_||PL QA, PL JA, FreeBSD guy||Independent
|-
|Yonggang Mao || X || maoyonggang|| maoyg|| Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Yue Lv || || lvyue || lvyue || Calc ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| John Marmion|| X || jmarmion||||||
|-
| Andreas Martens|| X || ama||||PL Writer||Sun Microsystems
|-
|-|
| Shane M Mathews|| X || smmathews|| smmathews ||[[Impress:_OpenGL_rendered_transitions]]||student
|-
| Frank Mau|| X || fma||||tooling||Sun Microsystems
|-
| [[User:smsm1|Shaun McDonald]] || X || smsm1 || shaunmcdonald || Mac Port, buildbot MacPort1 || Graduate
|-
| Caolán McNamara|| X || cmc||caolan||CL Writer & Filter man|| [http://www.redhat.com Red Hat Inc.]
|-
| Michael Meeks|| X || mmeeks||michael_||ugly hack-er, ESC||Novell, Inc.
|-
| Frank Meies|| X || fme||||Writer||Sun Microsystems
|-
| Federico Mena-Quintero|| || federicomena||federico||perfectionist||Novell, Inc.
|-
| Ismael Merzaq|| X || isma87||ismael_||Mac OSX native porting||Student
|-
| Michael Mi|| || mmi||||||
|-
| Björn Michaelsen|| X || b_michaelsen ||b_michaelsen|| Writer, Bookmarks, Performance, User Feedback Program ||Sun Microsystems
|-
| Björn Milcke|| X || bm||bm_||Chart||Sun Microsystems
|-
| Petr Mladek|| || pmladek||pmladek||SUSE RPMs, ooo-build releases||Novell, Inc.
|-
| Cyrille Moureaux|| X || cyrillem||Cyrille||||Sun Microsystems
|-
| [[User:Mmp|Matthias Müller-Prove]]|| X || mmp|| mprove|| [[User Experience]], http://ux.openoffice.org || Sun Microsystems
|-
| [[User:Bluedwarf|Takashi Nakamoto]]|| || bluedwarf|| || Japanese || Student
|-
| Jan Navrátil || X || jnavrati || jnavrati || || [http://www.redhat.com Red Hat Inc.]
|-
| Niklas Nebel|| X || nn||||PL [[Calc]]||Sun Microsystems
|-
| Christoph Neumann|| X || cn||||[[UnoApiTest]]||Sun Microsystems
|-
| Frank Neumann|| X || fne||||MacPort||Sun Microsystems
|-
| NicelKM|| X || mnicel||nicel||||Novell, Inc.
|-
| Jan Nieuwenhuizen|| X || jcn||janneke||Layout code, hacker ||Novell, Inc.
|-
| [[User:ChristophNoack|Christoph Noack]]|| X || christophnoack ||christoph_n||CL [http://ux.openoffice.org User Experience]||
|-
| Bertram Nolte|| || bnolte||||||
|-
| Tomas O'Connor|| || toconnor||||Scripting Framework||
|-
| Maximilian Odendahl|| X || mod||mod||[[Notes2]] [[SQL_Syntax_Highlighting]]|| Student / SEPT-Solutions
|-
| Takashi Ono || X || tono || || MinGW port || Independent
|-
| Lars Oppermann|| X || lo||||||
|-
| Rakesh Pandit || X || rakeshpandit|| chacha_chaudhry|| Education Project - Starmath/fix module warnings|| Education Project
|-
| Rodrigo Parra Novo|| X || rodarvus||rodarvus||Gnumeric/Abiword OpenDocument Format support and port to Maemo||INdT (Instituto Nokia de Tecnologia)
|-
| Pierre Pasteau|| X || pastea_p || pierrep|| Education Project, SeaMonkey migration || Education Project
|-
| Edward Peterlin|| X || OPENSTEP||||Mac||
|-
| [[User:Fpe|Frank Peters]]|| X || fpe||||CL Documentation||Sun Microsystems
|-
| Christof Pintaske|| X || cp||||||Sun Microsystems
|-
| Ron Piterman|| || rpiterman||||||
|-
| Sebastien Plisson|| X || plipli||plipli||Developer on Aqua port||OO Aqua Port
|-
| Noel Power|| || npower||noelp||VBA Interop, Scripting||Novell, Inc.
|-
| Nikolai Pretzell|| X || np || ||Autodoc, code quality||Sun Microsystems
|-
| Jonathan Pryor|| || jpryor || jonp || || Novell, Inc.
|-
| Canghua Qu|| || quch || Canghua || AutoTest, Graphics || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Volker Quetschke|| X || vq||vq||W32-tcsh/bash build environment and dmake Hacker, ESC||Gravity Waves
|-
| Tino Rachui|| X || tra||tinor||GSL/Unix Hacker||Sun Microsystems
|-
| Goran Rakić || X ||goranrakic || || Serbian Native-Lang PL ||
|-
| [[User:Kr|Kay Ramme]]|| X || kr||||PL UDK||Sun Microsystems
|-
| [[User:ErAck|Eike Rathke]]|| X || er||erAck||CL [[Calc]], engine; CL i18n; stricken with number formatter||Sun Microsystems
|-
| Michael Rauch|| X || mrauch||||NetBSD||
|-
| Jens-Heiner Rechtien|| X || hr||blauwal||RE; OOo SCM (CVS, CWS tooling); Porting; Compilers||Sun Microsystems
|-
| Daniel Rentz|| X || dr|| drr ||[[Calc]] Excel filter, UI||Sun Microsystems
|-
| Florian Reuter|| X || flr||||Writer filters||Novell, Inc.
|-
| Georg Richter|| X || grichter||georg||Base, native MySQL driver||MySQL AB
|-
| G. Roderick Singleton|| || grsingleton||grsingleton||Documentation||pathtech.org
|-
| Hennes Rohling|| X || hro||||GSL & Util||Sun Microsystems
|-
| Bibek Sahu|| || Bibek||bibek||Impress pieces||Trees For Life
|-
| Andreas Schlüns|| X || as||||Framework||Sun Microsystems
|-
| Ingo Schmidt|| X || is||||(Native) Installation||Sun Microsystems
|-
| [[User:Jsc|Jürgen Schmidt]]|| X || jsc||jsc||PL API, CL Extensions, UNO, SDK||Sun Microsystems
|-
| [[User:Schmidtm|Matthias Schmidt]] || || schmidtm || schmidtm || Mac OSX Aqua Port || Sun Microsystems
|-
| Stephan Schäfer|| X || ssa||ssa||VCL||Sun Microsystems
|-
| Frank Schönheit|| X || fs||FrankS||Database Access, Forms||Sun Microsystems
|-
| [[User:Sus|Svante Schubert]]|| X || sus||Svante||XML & ODFTOOLKIT co-lead, ODF TC, ODF SC Metadata||Sun Microsystems
|-
| [[User:Sts|Stella Schulze]]|| X || sts||||[http://ui.openoffice.org/nonav/VisualDesign/ Visual Design]||Sun Microsystems
|-
| Julian Seward || || sewardj || || valgrind ||
|-
| Darragh Sherwin|| || dsherwin||darragh||E-Legislation / E-GovSystems||Propylon
|-
|Lei shi || || shilei|| sl || Graphics|| [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Wei Guo SHI || X || shiwg || || Accessibility and Smart Suite filter || IBM Corp.
|-
|[[User:shizhoubo|zhoubo Shi]]|| || shizhoubo|| shizhoubo/robertzhou|| [[Framework]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Raul Siddhartha|| || rsiddhartha||raul||GTK File Selector||Novell, Inc.
|-
| Sarah Smith|| || ssmith||||||
|-
| [[User:mox|Mox Soini]] || X || mox || Moxed || Mac Porting ||
|-
| Rajesh Sola|| || rajeshsola||sola||misc.||NOSIP
|-
| Kai Sommerfeld|| X || kso||||manager & hacker||Sun Microsystems
|-
| Oliver Specht|| X || os||||PL UI||Sun Microsystems
|-
| Jörg Spindler|| || jspindler||||||
|-
| [[User:Rescue|Joey Stanford]] || || Rescue/k0fcc || Rinchen || CL [http://eo.openoffice.org/ Esperanto native-lang project] || [http://canonical.com Canonical] ||
|-
| Fridrich Štrba|| X || fridrich_strba||Fridrich||Word Perfect Hacker||Novell, Inc.
|-
| Keith Stribley|| X || kstribley||||Graphite fonts, Myanmar l10n||
|-
| Ulf Stroehler|| || us||||||Sun Microsystems
|-
| [[User:Muthusuba|Muthu Subramanian]]|| X || muthusuba||muthusuba||misc.||
|-
| Louis Suárez-Potts|| || louis||louis||Community Manager||Collab.net
|-
|Quanfa Tang || || tqfa|| tangquanfa|| Calc || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| David Tardon || X || dtardon || dtardon || || [http://www.redhat.com Red Hat Inc.]
|-
| Stefan Taxhet|| X || st||stx12||CC, interpersonal problem fixer||Sun Microsystems
|-
| Armin Theissen|| || armin||||||
|-
| Caio Tiago Oliveira|| X || asrail||asrail||CL QA, release testing pt-BR builds||BrOffice.org
|-
| Jan Tietjens|| || tietjens||||||
|-
| Rüdiger Timm|| X || rt|| rtimm ||RE||Sun Microsystems
|-
| [[User:mt|Malte Timmermann]]|| X || mt|| Malte || Accessibility, Security, Performance||Sun Microsystems
|-
| Gerhard Tonn|| || tonn||||s390||
|-
| Willem van Dorp|| || willem.vandorp||||||
|-
| Tom Verbeek|| X || tv||||Wizards, Art team||Sun Microsystems
|-
| Sander Vesik|| || svesik||||||
|-
| Daniel Vogelheim|| X || dvo||||XML||
|-
| Mikhail Voitenko|| X || mav||mav||Framework||Sun Microsystems
|-
| Robert Vojta|| X || rvojta||rvojta||Mac OS X related issue||
|-
| Dirk Völzke|| X || dv||||Installation||Sun Microsystems
|-
| [[User:Sparcmoz|Jim Watson]]|| X || sparcmoz|| sparcmoz||GNU Linux sparc porter||clug.org.au
|-
| [[User:Weiz |Zhao Wei ]] || || weiz || weiz || Chart2 || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Armin Weiss|| X || aw||||||Sun Microsystems
|-
| Gerd Weiss|| X || gm||||RE||Sun Microsystems
|-
| Dan Williams|| X || fa||dcbw||Mac et. al. hacker|| [http://www.redhat.com Red Hat Inc.]
|-
|[[User:wuy|Yan Wu]] || X || wuy || ||Framework || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Stephan Wunderlich|| X || sw||||||
|-
| Antonio Xu|| X || antoxu || antoxu || Async dialogs, PRC improvements || Intel Corporation
|-
|Dehua Xu || || xudehua || xudh || Release || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Steve Yin || X || steve_yin || steve_yin || Microsoft Office file format, PDF, Accessibility, ODF || IBM Corp.
|-
| Kohei Yoshida|| X || kohei||kohei_||[[Calc]] hacker, Calc optimization solver developer||Novell, Inc.
|-
| Guoqiang Yu|| X || yugq || yugq|| Performance || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Xiaoyang Yu|| || || ||Disk block reordering||Intel Corporation
|-
| George Zahopoulos|| X || georgez||||||
|-
| Kurt Zenker|| X || kz||smoketester||RE||Sun Microsystems
|-
|Huajun Zhang || || zhanghuajun|| zhanghj|| SW ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|[[User:Zhangxiaofei|Xiaofei Zhang]]|| || Zhangxiaofei || zhangxiaofei/FelixZ || [[Framework]] ||[[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|Jianwei Zhao || || zhaojianwei || zhaojianwei || Swriter || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Sheng zhao|| X || jacky23 || ||OdfToolKit_odf4j || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
| Jeremy Zheng|| X || zhiming || Jeremy || Async dialogs, PRC improvements || Intel Corporation
|-
|[[User:majun|Jun Ma]]|| ||majun || || writer || [[Beijing Redflag Chinese 2000 Software Co., Ltd.|Beijing Redflag CH2000]]
|-
|}

=== QA Engineers ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #f9f9f9; border: 1px #aaa solid; border-collapse: collapse;"
|-
! Name ||CVS||@openoffice.org || [[IRC Communication]] || Interested modules || Notes || Affiliation
|-
| Stefan Baltzer||||sba||||writer||||Sun Microsystems
|-
| Thorsten Bosbach||X||tbo||||framework, testautomation||framework test automation||Sun Microsystems
|-
| Oliver Craemer||X||oc||||[[Calc]], testautomation||calc test automation||Sun Microsystems
|-
| Helge Delfs||X||hde||||testautomation, writer||Test automation||Sun Microsystems
|-
| Fredrik Haegg||X||fha||||writer, testautomation||Writer test automation||Sun Microsystems
|-
| Hasan Ilter||||hi||||writer, printing, pdf export||||Sun Microsystems
|-
| Michael Rüß||||mru||||writer, word im/export||||Sun Microsystems
|-
| Éric Savary||||es||||writer, accessibility||||Sun Microsystems
|-
| [[User:jsi|Joerg Sievers]]||X||jsi||jsi_sun||chart, xml, testautomation||Chart2, XML test automation||Sun Microsystems
|-
| Joerg Skottke||X||jsk||skotti||framework, qa/qatesttool||Framework test automation||Sun Microsystems
|-
| Marc Neumann||X||msc||||database, testautomation||Database access test automation||Sun Microsystems
|-
| Chris Lukasiak||||clu||||database||||Sun Microsystems
|-
| Frank Stecher||||fst||||[[Calc]]||||Sun Microsystems
|-
| Jack Warchold|||| jw||||writer, import/export filters||||Sun Microsystems
|-
| Uwe Luebbers||||ul||||framework||||Sun Microsystems
|-
| Thorsten Martens||||tm||||framework||||Sun Microsystems
|-
| Olaf Felka|||| of||of_sun||framework, installation||||Sun Microsystems
|-
| Thomas Klarhoefer||||kla||||chart||||Sun Microsystems
|-
| Wolfram Garten||X|| wg||||draw, impress||draw, impress test automation||Sun Microsystems
|-
| Christian Guenther||||cgu||||draw, impress||||Sun Microsystems
|-
| [[User:Thorsten_Ziehm|Thorsten Ziehm]]||||| thorstenziehm||||||QA lead||Sun Microsystems
|-
|}

We are tracking pending JCAs in the document [[Pending JCAs]].

== Related Pages ==
* [[Commit Rights]]
* [[Contributing Patches]]
* [[User_Experience/Community|User Experience Team]]
* A map of OOo developers around the world is available at http://www.frappr.com/ooodev, please add yourself to the map if you're involved in OOo development. It's just fun to see who's where :-)

[[Category:Development]]

Specification search toolbar

2009-04-28T01:43:43Z

Robertzhou: /* i-Team Members (The specification owner is part of the i-Team) */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| Li Meiying,Zhu Lihua
| limeiying@redoffice.com,zhulihua@redoffice.com
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information.

=== 8. "Count information" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Show count information of the searching text in the current document
| <Comment>
|}

The "Count Message" label is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the "Count information" Label will be shown , and tell user count of the searching text in the current document.

=== 9. "feedback" Label ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| None, it is dynamic stirng, it show different message according to result of searching text
|
|}

The feedback is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the 9."feedback " Label and 8."Count information" Label would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
The current searching dialog in the OOo.
The search toolbar of the Mozilla firefox.
[[Category:Features]]

Specification search toolbar

2009-04-24T03:10:17Z

Robertzhou: /* References */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information.

=== 8. "Count information" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Show count information of the searching text in the current document
| <Comment>
|}

The "Count Message" label is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the "Count information" Label will be shown , and tell user count of the searching text in the current document.

=== 9. "feedback" Label ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| None, it is dynamic stirng, it show different message according to result of searching text
|
|}

The feedback is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the 9."feedback " Label and 8."Count information" Label would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
The current searching dialog in the OOo.
The search toolbar of the Mozilla firefox.
[[Category:Features]]

Specification search toolbar

2009-04-24T03:08:41Z

Robertzhou: /* 8. "Count information" Label */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information.

=== 8. "Count information" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Show count information of the searching text in the current document
| <Comment>
|}

The "Count Message" label is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the "Count information" Label will be shown , and tell user count of the searching text in the current document.

=== 9. "feedback" Label ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| None, it is dynamic stirng, it show different message according to result of searching text
|
|}

The feedback is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the 9."feedback " Label and 8."Count information" Label would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T03:07:28Z

Robertzhou: /* Dynamic Text Info2 */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information.

=== 8. "Count information" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Show count information of the searching text in the current document
| <Comment>
|}

The "Count Message" label is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the "Count information" Label will be shown , and tell user count of the searching text in the current document.

=== 9. " feedback " Label> ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| None, it is dynamic stirng, it show different message according to result of searching text
|
|}

The feedback is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the 9. " feedback " Label and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T03:01:18Z

Robertzhou: /* 8. Dynamic Text Info1 */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information.

=== 8. "Count information" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Show count information of the searching text in the current document
| <Comment>
|}

The "Count Message" label is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the "Count information" Label will be shown , and tell user count of the searching text in the current document.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:58:28Z

Robertzhou: /* Dynamic Text Info1 */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information.

=== 8. Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info1 will be shown , and tell user count of the searching text in the current document.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:57:50Z

Robertzhou: /* Dynamic Text Info1 */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info1 will be shown , and tell user count of the searching text in the current document.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:56:02Z

Robertzhou: /* 7. "Whole Word" CheckBox */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:54:51Z

Robertzhou: /* Whole Word Button */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== 7. "Whole Word" CheckBox===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the searching toolbar is opening. it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
| None
|
|-
| '''Checked:'''
| searching text will match the whole word to find in the current document.
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Whole Word Cis a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:51:25Z

Robertzhou: /* 6. "Match Case" CheckBox */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case CheckBox is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:50:57Z

Robertzhou: /* Match Case Button */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== 6. "Match Case" CheckBox ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During the search toolbar is open, it is always enabled
|
|-
| '''Disabled:'''
| None
|
|-
| '''Tristate:'''
|
|
|-
| '''Checked:'''
| Searching text will match case to find in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''CheckBox Label:'''
| <EN-US>
|
|}

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:46:32Z

Robertzhou: /* 5. "Search All" Button */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== Match Case Button ===

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:45:41Z

Robertzhou: /* 4. "Previous" Button */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the 2.TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the 2.TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During one of documents is opening, it is always enabled
|
|-
| '''Disabled:'''
| If the 2. TextField has nothing, it is disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== Match Case Button ===

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:43:27Z

Robertzhou: /* Search All Button */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During one of the documents, it is always enabled
|
|-
| '''Disabled:'''
| If the 2.TextField has only nothing, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== 5. "Search All" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During one of documents is opening, it is always enabled
|
|-
| '''Disabled:'''
| If the 2. TextField has nothing, it is disabled
|
|-
| '''On Click:'''
| The all searching text will be shown hightlight and selected in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected. The “search all button” need not changed states.

=== Match Case Button ===

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:39:34Z

Robertzhou: /* Previous Button */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== 4. "Previous" Button ===
{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| During one of the documents, it is always enabled
|
|-
| '''Disabled:'''
| If the 2.TextField has only nothing, it will be disabled
|
|-
| '''On Click:'''
| Find forwards searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information.

=== Search All Button ===

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected(like following Figure7 image). The “search all button” need not changed states.

=== Match Case Button ===

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:29:49Z

Robertzhou: /* Next Button */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== 3. "Next" Button ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| if there is any text content in the TextField Controller, it will be always enabled
|
|-
| '''Disabled:'''
| if there is nothing text content in the TextField Controller, it will be disabled
|
|-
| '''On Click:'''
| find backward searching text in the current document
|
|-
| '''Other:'''
| None
|
|-
|'''Button Label:'''
| <EN-US>
|
|}

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information.

=== Previous Button ===

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information like following red line mark.

=== Search All Button ===

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected(like following Figure7 image). The “search all button” need not changed states.

=== Match Case Button ===

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:23:03Z

Robertzhou: /* Input for searching TextField */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== 2. Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is TextField Controller, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text.

=== Next Button ===

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information like following red line mark.

=== Previous Button ===

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information like following red line mark.

=== Search All Button ===

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected(like following Figure7 image). The “search all button” need not changed states.

=== Match Case Button ===

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:21:30Z

Robertzhou: /* Input for searching TextField */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| Here is "Find" label
|}

The Edit Controller is Edit Text, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text. Like following image of red line mark.

=== Next Button ===

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information like following red line mark.

=== Previous Button ===

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information like following red line mark.

=== Search All Button ===

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected(like following Figure7 image). The “search all button” need not changed states.

=== Match Case Button ===

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T02:20:49Z

Robertzhou:

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
In current OpenOffice.org ,users use the search dialog to search text, when the users want to see content which the search dialog hid, the uses have to move the search dialog via mouse,because the search dialog always display.

== Goals ==
The goal for OpenOffice.org 3.x is to provide a tool bar which gives uses the possibility to apply frequently uesed for searching text. The search tool bar will provide a simple, shortcut way to searching text, without the users not have to open the search dialog.

== Requirements and Dependencies ==

=== Requirements ===
Provide a tool bar which gives users the possibility to apply frequently used commands without the opening search dialog.

=== Technical Dependencies ===
Implementation of the search tool bar depend on these searching codes which the current search dialog is using the searching codes , but it has nothing to do with the search dialog.

== Competitive Analyses ==
=== Google Chrome Browser===
The Google Chrome Search tool bar (Figure 1,marked by the redline). it is located on the below of the address Tool bar and can't be moved. The Search tool bar can made visible by pressing Ctrl+F. The search toolbar is very simple , it only provide searching text and not match Match Case. It includes backwards searching , forwards searching text and count of the searching text. The Search tool bar organized into a number of buttons or lable which are arranged from the left to the right with it.
[[Image:Chrome_Browser_1.JPG]]

=== Mozilla Firefox Browser ===

Mozillas Search Tool bar(Figure 2) , It is located at the above of the staus bar and can't be moved .The Search tool bar can made visible by pressing Ctrl+F.
The Search tool bar organized into a number of buttons which are arranged from the left to the right with it. The mouse can opterator any button and every button has states.
[[Image:Mozilla_browser_1.JPG]]

== Detailed Specification ==
The OpenOffice Search Tool Bar(Figure3) shall be located at the above of the status bar. And it can't be moved. It can made visible by pressing Ctrl+F1. It is make up of the tool bar item , of course , these tool bar item can be BUTTON_SYMBOLTEXT or BUTTON_SYMBOL.

[[Image:SpecSearc_Toolbar1.JPG]]

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| rowspan="2" | '''Toolbar Name:'''
| Search toolbar
|-
| 搜索工具栏
|
|-
| '''Has Closer:'''
| No
|
|-
| '''Style:'''
| Icon/Text
|
|-
| '''Initial State:'''
| Docked
|
|-
| '''Initial Docking Position:'''
| Bottom, above the status bar
|
|-
| '''Initial Floating Position:'''
| None
|
|-
| '''List in "View/Toolbars":'''
| Yes
|
|-
| '''Is Context Sensitive:'''
| No
|
|-
| colspan="3" bgcolor="#eeeeee" |'''Toolbar Items:'''
|-
| rowspan="2" | '''Item Name:'''
| <EN-US>
|-
| <Other Language (Optional)>
|
|-
| '''Item Icon:'''
| <Link to Image here>
|
|-
| '''Action:'''
| <Specify action here. E.g. Finding>
|
|-
| '''Other Properties:'''
| <Specify properties here>
|
|}

=== 1. "Find" Label ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''Label''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Label:'''
| Find
| EN-US
|}

The static text info only describe information to explain what the edit controller input. It name “Find”, it only is static text and showed in the searching tool bar. It should support multilingual property.

=== Input for searching TextField ===

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; border: 1px #cccccc solid; border-collapse: collapse; width: 100%"
|-
| width="200" bgcolor="#dddddd" | '''Property''' || bgcolor="#dddddd" | '''State''' || bgcolor="#dddddd" | '''Comment'''
|-
| '''Enabled:'''
| during one of documents is opening
| these documents is only swriter,scalc,impress or drawing
|-
| '''Disabled:'''
| None
|
|-
| '''Read Only:'''
| No
|
|-
| '''Initial String:'''
| Blank space string
|
|-
| '''String Preselected:'''
| Yes
|
|-
| '''Caret Position:'''
| <0>
|
|-
| '''Characters Not Allowed'''
| None
|
|-
| '''Echo characters (Password Field)'''
| None
|
|-
|''' TextField Label:'''
| <EN-US>
| <Comment>
|}

The Edit Controller is Edit Text, users can input searching text in the edit Text, and it always is showed in the searching tool bar. When users did not find searching text in current document, the edit text background color should be set gray which mean not find searching text. Like following image of red line mark.

=== Next Button ===

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find backward searching text in the current document. When the searching text is showed at end of the document, the The Dynamic Text Info2 will shown “ reached end of document,continue form top” information like following red line mark.

=== Previous Button ===

The is a simple tool bar item with BUTTON_SYMBOLTEXT type. Users can use to find forwards searching text in the current document. When the searching text is showed at top of the document, the The Dynamic Text Info2 will shown “ reached top of document,continue form end” information like following red line mark.

=== Search All Button ===

The Button is a tool bar item with BUTTON_SYMBOLTEXT type,when users click it, the searching text will be shown hightlight and selected(like following Figure7 image). The “search all button” need not changed states.

=== Match Case Button ===

The Match Case Button is a check box button, after the check box is selected, searching text will match case to find in the current document, when searching text may not exist, The Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Whole Word Button ===

The Whole Word Button is a check box button, after it is selected , searching text will match the whole word to find in the current document. When the whole word searching text not exist , he Dynamic Text Info2 will shown “ phrase not found” information. Like following red line mark.

=== Dynamic Text Info1 ===

The Dynamic Text info1 is a dynamic string, is show information which means to show count of searching text in the current documents. When user use only “Search all” to find string, the Dynamic Text info2 will be shown , and tell user count of the searching text in the current document. Like following image of red line mark.

=== Dynamic Text Info2 ===

The Dynamic Text info2 is a dynamic string, is show information which remain following informations to users. “phrase not found “, “ reached top of document,continue form end”, “reached end of document,continue form top” . What the dynamic text is depend to result of searching text.

But the Dynamic Text Info1 and Info2 would support multilingual property.

=== Close Button ===

The is tool bar item with only BUTTON_SYMBOL type, it can close the search tool bar.

== Future Tasks ==
None at this time.

== Notes ==

None

== References ==
none
[[Category:Features]]

Specification search toolbar

2009-04-24T01:56:45Z

Robertzhou: /* Static Text info */

Specification search toolbar

2009-04-24T01:54:33Z

Robertzhou: /* Detailed Specification */

Specification search toolbar

2009-04-24T01:42:57Z

Robertzhou: /* Detailed Specification */

Specification search toolbar

2009-04-24T01:39:44Z

Robertzhou: /* Detailed Specification */

Specification search toolbar

2009-04-23T09:22:13Z

Robertzhou: /* References */

Specification search toolbar

2009-04-23T09:21:51Z

Robertzhou: /* Notes */

Specification search toolbar

2009-04-23T09:20:13Z

Robertzhou: /* Detailed Specification */

Specification search toolbar

2009-04-23T09:16:18Z

Robertzhou: /* Static Text info */

Specification search toolbar

2009-04-23T09:15:24Z

Robertzhou: /* Detailed Specification */

Specification search toolbar

2009-04-23T09:08:56Z

Robertzhou: /* Mozilla Firefox Browser */

Specification search toolbar

2009-04-23T09:08:20Z

Robertzhou: /* Mozilla Firefox Browser */

File:Mozilla browser 1.JPG

2009-04-23T09:07:02Z

Robertzhou:

Specification search toolbar

2009-04-23T09:01:59Z

Robertzhou: /* Google Chrome Browser */

File:Chrome Browser 1.JPG

2009-04-23T08:59:37Z

Robertzhou:

Specification search toolbar

2009-04-23T08:52:29Z

Robertzhou: /* Competitive Analyses */

Specification search toolbar

2009-04-23T08:47:44Z

Robertzhou: /* Technical Dependencies */

Specification search toolbar

2009-04-23T08:46:17Z

Robertzhou: /* Requirements */

Specification search toolbar

2009-04-23T08:45:27Z

Robertzhou: /* Goals */

Specification search toolbar

2009-04-23T08:44:17Z

Robertzhou: /* User Scenarios */

Specification search toolbar

2009-04-23T08:41:45Z

Robertzhou: /* Motivation */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
The motivation for this feature is to enhance the speed of searching text ,and the search tool bar does not hid the content of the document.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Would need to specify the exact layout and functionality of the presenter view. Then would require implementation of that mode in Impress.

=== Technical Dependencies ===
Requires the implementation of the [[Impress simple multiple display specification]].

== Competitive Analyses ==
[[http://office.microsoft.com/en-us/powerpoint/HA010565471033.aspx MS PowerPoint]] has a presenter view and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

[[http://www.apple.com/iwork/keynote/features/presentertools.html Apple's iWork Keynote has a presenter view]].

== Detailed Specification ==
In the Impress options, there should be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
Nothing known.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==

I think it would be useful to have a mode in which Impress does not rely on any X11 server information for the layout of the presenter screen. For example, I might not want the presentation window to be full screen, or I might be sharing a subrectangle of my desktop with VNC. To specify what the presentation layout should be, maybe there could be a mode similar to Apple's Keynote design screen, except that in addition to all the presenter tools, the absolute position and size of the slide that the audience sees could also be chosen. Of course, "full screen on the second display" is a special case of this. In some other presentations, I might want to have the slide window and an editable notes window up on the audience screen.

== References ==
http://qa.openoffice.org/issues/show_bug.cgi?id=71505
Issue 71505 Add a presenter view

http://www.openoffice.org/issues/show_bug.cgi?id=12719
Bug 12719 Support for multiscreen displays (dual monitors)

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
Other forum posts requesting feature

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
Temporary Linux workaround

http://www.apple.com/iwork/keynote/features/presentertools.html
Apple's implementation

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
Article describing Microsoft's implementation

[[Category:Impress issues]]
[[Category:Features]]

Specification search toolbar

2009-04-23T08:40:37Z

Robertzhou: /* Glossary */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
|
|
|}

== Motivation ==
Many applications for presentation software such as Impress involve multiple displays. Being able to support a separate control display and presentation display, would allow Impress to function as a replacement for PowerPoint in these applications.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Would need to specify the exact layout and functionality of the presenter view. Then would require implementation of that mode in Impress.

=== Technical Dependencies ===
Requires the implementation of the [[Impress simple multiple display specification]].

== Competitive Analyses ==
[[http://office.microsoft.com/en-us/powerpoint/HA010565471033.aspx MS PowerPoint]] has a presenter view and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

[[http://www.apple.com/iwork/keynote/features/presentertools.html Apple's iWork Keynote has a presenter view]].

== Detailed Specification ==
In the Impress options, there should be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
Nothing known.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==

I think it would be useful to have a mode in which Impress does not rely on any X11 server information for the layout of the presenter screen. For example, I might not want the presentation window to be full screen, or I might be sharing a subrectangle of my desktop with VNC. To specify what the presentation layout should be, maybe there could be a mode similar to Apple's Keynote design screen, except that in addition to all the presenter tools, the absolute position and size of the slide that the audience sees could also be chosen. Of course, "full screen on the second display" is a special case of this. In some other presentations, I might want to have the slide window and an editable notes window up on the audience screen.

== References ==
http://qa.openoffice.org/issues/show_bug.cgi?id=71505
Issue 71505 Add a presenter view

http://www.openoffice.org/issues/show_bug.cgi?id=12719
Bug 12719 Support for multiscreen displays (dual monitors)

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
Other forum posts requesting feature

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
Temporary Linux workaround

http://www.apple.com/iwork/keynote/features/presentertools.html
Apple's implementation

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
Article describing Microsoft's implementation

[[Category:Impress issues]]
[[Category:Features]]

Specification search toolbar

2009-04-23T08:39:22Z

Robertzhou: /* Swriter Scalc Impress Drawing */

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| Shizhoubo
| 2009-04-22
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| Swriter, Scalc, Impress, Drawing
|
|
|-
| Task ID(s)
| None
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
The Search tool bar is tool bar which will provider search quickly text feature(like fireforx toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Jaron Kuppers (Jaron),Philip Ganchev(Philip)
| jaronbaron@gmail.com, phil.ganchev@gmail.com
|-
| Development
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| shizhoubo(robertzhou)
| shizhoubo@redoffice.com
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2009-04-23

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Many applications for presentation software such as Impress involve multiple displays. Being able to support a separate control display and presentation display, would allow Impress to function as a replacement for PowerPoint in these applications.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Would need to specify the exact layout and functionality of the presenter view. Then would require implementation of that mode in Impress.

=== Technical Dependencies ===
Requires the implementation of the [[Impress simple multiple display specification]].

== Competitive Analyses ==
[[http://office.microsoft.com/en-us/powerpoint/HA010565471033.aspx MS PowerPoint]] has a presenter view and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

[[http://www.apple.com/iwork/keynote/features/presentertools.html Apple's iWork Keynote has a presenter view]].

== Detailed Specification ==
In the Impress options, there should be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
Nothing known.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==

I think it would be useful to have a mode in which Impress does not rely on any X11 server information for the layout of the presenter screen. For example, I might not want the presentation window to be full screen, or I might be sharing a subrectangle of my desktop with VNC. To specify what the presentation layout should be, maybe there could be a mode similar to Apple's Keynote design screen, except that in addition to all the presenter tools, the absolute position and size of the slide that the audience sees could also be chosen. Of course, "full screen on the second display" is a special case of this. In some other presentations, I might want to have the slide window and an editable notes window up on the audience screen.

== References ==
http://qa.openoffice.org/issues/show_bug.cgi?id=71505
Issue 71505 Add a presenter view

http://www.openoffice.org/issues/show_bug.cgi?id=12719
Bug 12719 Support for multiscreen displays (dual monitors)

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
Other forum posts requesting feature

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
Temporary Linux workaround

http://www.apple.com/iwork/keynote/features/presentertools.html
Apple's implementation

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
Article describing Microsoft's implementation

[[Category:Impress issues]]
[[Category:Features]]

Specification search toolbar

2009-04-23T08:19:20Z

Robertzhou: New page: This page exists to implemente a search toolbar for OOo. (The specifications can be created using the Specification template) The Search tool bar is tool bar which will provider searc...

This page exists to implemente a search toolbar for OOo. (The specifications can be created using the [[Specification template]])

The Search tool bar is tool bar which will provider search quickly text feature(like firfox search toolbar), it includes searching text, backwards searching, forward searching, Match of lowercase or uppercase, Match the Whole word and Closer button. It can be closed by mouse or pressing a Keyboard shortcut.

Any discussion of the specification should happen in the maillist(discuss@ux.openoffice.org), or on the discussion pages.

= Search toolbar =

= Swriter Scalc Impress Drawing =
{| border=1 cellspacing=0 cellpadding=5
| Document - ID
| Specification Owner
| Last Change
| Status
|-
|
| DavidFraser
| 2005-12-15
| Draft
|-
| Conforms to
|
|
|
|-
| Applies to
| sd, vcl
|
|
|-
| Task ID(s)
| 12179
|
|
|-
| Category
| Feature
|
|
|}

=== Abstract ===
More and more graphics cards support more than one monitor simultaneously. These can either be configured as one large screen (which on X11 is called Xinerama mode) or multiple independent screens. When displaying presentations on video projectors or alternate displays it would be preferable for the user to be able to include a separate display for the presenter to see and control what is being displayed, along with ancillary (but important) information.

=== i-Team Members (The specification owner is part of the i-Team) ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Name
| E-mail Address
|-
| User Experience
| Mathis Dirksen-Thedens (MDT)
| ooo@jesusfan.de
|-
| Development
| <Name + Initials>
|
|-
| Quality Assurance
| <Name + Initials>
|
|-
| Documentation
| <Name + Initials>
|
|}

=== Approved for Implementation ===

{| border=1 cellspacing=0 cellpadding=5
|-
|
| Approved by
| Date
|-
| User Experience
| <Name>
| <Date>
|-
| Development
| <Name>
| <Date>
|-
| Quality Assurance
| <Name>
| <Date>
|-
| Documentation
| <Name>
| <Date>
|-
| String Review
| <Name>
| <Date>
|}

=== Document Change History ===

{| border=1 cellspacing=0 cellpadding=5
|-
| Rev. Level
| Change
| Initials
| Date
|-
| 1.0
| initial version
|
| 2005-06-10
|-
| 1.01
| added many texts
| MDT
| 2005-06-28
|-
| 1.1
| Added more detail about presenter view, and possible improvements to it. Mike Dark - khelmar@gmail.com
| MJD
| 2005-08-26
|-
| 1.11
| ported to this new wiki (pre-split)
| JWP
| 2005-12-02
|-
| 1.2
| split into simple and presenter mode specs
| DF
| 2005-12-15
|-
| 1.3
| add this feature to the specification [http://specs.openoffice.org/impress/slideshow/ControllingSlideShow.odt Controlling Slide Show]; target is OOo 2.1; thanks for the great effort at this point
| MMP
| 2006-09-13

|}

== Glossary ==

{| border=1 cellspacing=0 cellpadding=5
|-
| Term
| Description
|-
| dual head
| the ability to have two separate display devices configured (which together form the desktop)
|}

== Motivation ==
Many applications for presentation software such as Impress involve multiple displays. Being able to support a separate control display and presentation display, would allow Impress to function as a replacement for PowerPoint in these applications.

== User Scenarios ==
User has a projection system, with a dual graphics card. One output is connected to a monitor that is visible only to the presenter. The other output is connected to a video projector. The user will display the actual presentation on the video projector, while simultaneously being able to view and access the control window on the monitor. One example is during church worship services, where it is desirable for the operator to search through the slides of the presentation without disrupting the display of the current slide to the congregation.

Another example is for those giving a talk at a scientific conference; it's very useful to know what slide is being displayed, while being able to look out over the audience. Ideally, this would be similar to the Presenter View in Powerpoint, which has a timer, navigation buttons, and an area at the bottom of the screen for notes about each slide (which would, ideally, come from the notes page). Notes are VERY useful for keeping track of important points, specific numbers or ratios, etc., and making sure points aren't missed.

The timer is useful for keeping track of how long you're running, especially for practice and monitoring presentations that are time-limited. If someone wanted to get really fancy, it'd be great to setup a time limit and have a separate slide counter; i.e., this presentation lasts 10 minutes, and I have 20 slides, so each slide has a countdown timer of 30 seconds. Then, if one slide goes long, the timer on the remaining slides is decremented, or if one slide takes less time, each additional slide gets more time. That would be fantastic to keep track of how a presentation is going.

http://images.apple.com/iwork/keynote/images/present_window20050111.jpg
For an idea of what this should look like, see the above (from Apple's website, listed in the references) - the view on the left would be the output hooked to the projector, while the view on the right would be the laptop / desktop the presenter is viewing. However, it would be nice to have something similar to the "Slides" toolbar showing upcoming slides. Ideally, it would be great to edit slides elsewhere in the presentation while showing another, but that's not a requirement.

== Goals ==
Provide a robust and easy-to-use dialog, to allow those with multiple-monitor setups to have a separate presenter view that provides additional information (notes, timing, upcoming slides, and the current slide).

== Requirements and Dependencies ==

=== Requirements ===
Would need to specify the exact layout and functionality of the presenter view. Then would require implementation of that mode in Impress.

=== Technical Dependencies ===
Requires the implementation of the [[Impress simple multiple display specification]].

== Competitive Analyses ==
[[http://office.microsoft.com/en-us/powerpoint/HA010565471033.aspx MS PowerPoint]] has a presenter view and in many forums it is named as the key reason why people can't use OOo instead.

Virtually every professor and scientist I know uses Powerpoint's "Presenter View" to lecture or give talks, and most are unwilling to switch without similar functionality.

[[http://www.apple.com/iwork/keynote/features/presentertools.html Apple's iWork Keynote has a presenter view]].

== Detailed Specification ==
In the Impress options, there should be a check-box or separate tab for "Presenter View", allowing enabling of ther presenter view on another monitor. When checked, various options should be presented, such as:

Drop-down box
Screen to show the view on - this should include all screens attached to the computer with the exception of the screen selected to show the full-screen presentation on.

A series of check-boxes

Show:
* Current Slide - shows the slide displayed on the fullscreen view on the presenter's view
* Next Slide - Shows a large view of the next slide on the presenter's view
* Slide thumbnails - Shows a view similar to the "Slides" toolbar to see multiple upcoming slides on the presenter's view
* Navigation buttons - Add "back", "next", and "blank screen" buttons to the presenter's view
* Notes - Show the "notes" section for the current slide on the presenter's view
* Clock - Shows the current time on the presenter's view
* Timer - Adds a timer to the presenter's view

While the timer could be a simple count-up timer, ideally selecting this checkbox should enable other options:

- Count-up: makes the timer function as a simple stopwatch (starts at 0:00:00 when the presentation starts and counts up from there).
- Count-down (with an associated scroll-box to set the values): Starts counting down from the value entered by the user when the presentation starts; perhaps with color changes (i.e., green -> yellow and yellow -> red) at user-specified values (yellow -> red at 1 minute remaining).
- Individual slide timing - Asks the user to enter the desired presentation length. From that, it divides by the number of slides in the current presentation to determine the amount of time per slide. i.e., a 10 minute presentation with 5 slides means each slide should take 2 minutes. The number of time per slide would be automatically updated with navigation, based on the actual time taken per slide. i.e., if slide #2 in the 10 minute presentation takes 3 minutes, then there would only be 1 minute 40 seconds for the remaining slides (3 slides remaining * 2 minutes per slide = 6 minutes; 6 minutes - 1 minute overrun = 5 minutes remaining; 5 minutes / 3 slides = 1 minute 40 seconds per slide.)

==== String list ====

{| border=1 cellspacing=0 cellpadding=5
|-
| Item
| English
| German
| Swedish
| Comments
|-
| Dropdown Element
| Screen 1
| Bildschirm 1
| Skärm 1
|
|}

==== Tab Order ====
Not of any importance.

==== Key Board Shortcuts ====
It would be handy, if you could map a Shorcut (e.g. F5 which is used by many presenting devices)

=== G11n ===
Nothing known.

=== Error Conditions ===
Nothing known.

=== Migration ===
Not needed.

== Future Tasks ==
None at this time.

== Notes ==

I think it would be useful to have a mode in which Impress does not rely on any X11 server information for the layout of the presenter screen. For example, I might not want the presentation window to be full screen, or I might be sharing a subrectangle of my desktop with VNC. To specify what the presentation layout should be, maybe there could be a mode similar to Apple's Keynote design screen, except that in addition to all the presenter tools, the absolute position and size of the slide that the audience sees could also be chosen. Of course, "full screen on the second display" is a special case of this. In some other presentations, I might want to have the slide window and an editable notes window up on the audience screen.

== References ==
http://qa.openoffice.org/issues/show_bug.cgi?id=71505
Issue 71505 Add a presenter view

http://www.openoffice.org/issues/show_bug.cgi?id=12719
Bug 12719 Support for multiscreen displays (dual monitors)

http://www.oooforum.org/forum/viewtopic.phtml?t=19080
Other forum posts requesting feature

http://www.oooforum.org/forum/viewtopic.phtml?p=86445#86445
Temporary Linux workaround

http://www.apple.com/iwork/keynote/features/presentertools.html
Apple's implementation

http://michaelhyatt.blogs.com/workingsmart/2005/01/powerpoints_pre.html
Article describing Microsoft's implementation

[[Category:Impress issues]]
[[Category:Features]]

File:Diagonal Table Header Specification.odt

2007-07-31T09:37:18Z

Robertzhou:

Diagonal Table Header

2007-07-31T09:19:42Z

Robertzhou: /* This function can be described as follows: */

==About adding a new feature that "insert diagonal table header in the Writer" ==
===This function can be described as follows:===
Allowing a diagonal header be inserted into the first Cell of a table in OOo Writer. A new menu item named 'diagonal table header' is added in the "Insert" menu to open a dialog which provides the diagonal style and word size selected by user.<br>
[[Image:Diagonal_Table_Header_Specification.odt]]
[[Category:Development]]

Diagonal Table Header

2007-07-31T09:11:12Z

Robertzhou:

User talk:Robertzhou

2007-07-31T09:09:32Z

Robertzhou:

== Diagonal Table Header ==
==About adding a new feature that "insert diagonal table header in the Writer" ==
===This function can be described as follows:===
Allowing a diagonal header be inserted into the first Cell of a table in OOo Writer. A new menu item named 'diagonal table header' is added in the "Insert" menu to open a dialog which provides the diagonal style and word size selected by user.
[[Category:Development]]

User talk:Robertzhou

2007-07-31T08:43:26Z

Robertzhou: Diagonal table header

== Diagonal table header ==

==About adding a new feature that "insert diagonal table header in the Writer" ==
===This function can be described as follows:===
==About adding a new feature that "insert diagonal table header in the word processor program" ==
===This function can be described as follows:===
OOo does not provide the feature of inserting diagonal table header, the user will<br>
meet the following problems when they use drawing tool to draw diagonal line in<br> the cells to achieve that feature, the diagonal line won't be changed if the size of the cell changes, if the user wanna input word at the part of diagonal line he can only do so by using self chosen text frame to input word which will be very inconvenient, so we can meet user's need by inserting diagonal line table header that is to combine inserting diagonal line with inputing word to fulfill the function of inserting diagonal line table header, we can add "insert diagonal line table header " menu item in the main menu “Insert" and at the same time we can build a box called" inserting clined line table header". the box of " inserting clined line table header is used to provide the customer with the function of choosing clined line table header format, inputing word and choosing the font size of the word.
[[Category:Development]]