Search: concept

The standard has a lot of momentum, there are many people who understand how to use plain old SQL where they would be baffled with newer concepts in data storage. Also there are plentiful libraries written for inter-operating with SQL based databases.

* The standard has a lot of momentum, there are many people who understand how to use plain old SQL where they would be baffled with newer concepts in data storage. Also there are plentiful libraries written for inter-operating with SQL based databases

I wonder if we cannot somehow merge the concepts together. I guess I'd need to see some examples for this.

XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

\r\n\r\n## Requirements\r\n* Knowledge of HTML, CSS, Bootstrap, XML, Git\r\n* You will encounter concepts like Data Model, Skins Extensions, Templating engines, Apache Velocity, modular components, etc. but you don't need to be familiar with them in advance\r\n\r\n## Expected Outcome\r\n* Pull Request on the https://github.com/xwiki/xwiki-platform repository with the solution\r\n* The summary of the Pull Request must have a first line matching the JIRA issue following by a colon and then the title of this issue\r\n* Following best practices defined at http://dev.xwiki.org/xwiki/bin/view/Main/WebHome\r\n\r\n## Prerequisites\r\n\r\nBefore starting your task familiarize yourself a bit with XWiki.

XWiki is quite a foreign concept to many people. e.g. people who are not in the tech world; Grandpa/Grandma old generation.

Editing Pages XWiki Syntax Understanding XWiki Basic Concepts Document Lifecycle URL resolution Advanced Usage That is what the second generation wiki means :) Programming in the wiki remark: the name "Developer Guide" is confusing, because the first impression is, it's about developing of the XWiki platform Code Zone User Cookbook Administration Installation Common Configuration Skins Changing Color Theme with default skin Encoding Logging Access Rights User Management Group Management Authentication (LDAP, Database...)

xpage=print]] = Understanding XWiki = * [[Basic Concepts >> http://enterprise.xwiki.org/xwiki/bin/view/GettingStarted/XWikiEnterpriseBasicConcepts]] * [[Document Lifecycle >> http://platform.xwiki.org/xwiki/bin/view/Features/DocumentLifecycle]] * [[URL resolution >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/URL+resolution]] = Advanced Usage = That is what the [[second generation wiki>>platform:Main.SecondGenerationWiki]] means :) * [[Programming in the wiki >> http://platform.xwiki.org/xwiki/bin/view/DevGuide/]] //remark: the name "Developer Guide" is confusing, because the first impression is, it's about developing of the XWiki platform// * [[Code Zone >> http://code.xwiki.org/xwiki/bin/view/Main/]] * [[User Cookbook >> Drafts.XEDocUserCookbook]] = Administration = * [[Installation >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation]] * [[Common Configuration >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Configuration]] ** [[Skins>>platform:AdminGuide.Skins]] ** [[Changing Color Theme with default skin >>http://code.xwiki.org/xwiki/bin/view/Skins/ColibriSkin]] ** [[Encoding>>platform:AdminGuide.Encoding]] ** [[Logging >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Logging]] * [[Access Rights >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Access+Rights]] ** [[User Management >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/User+Management]] ** [[Group Management>>platform:AdminGuide.Group Management]] ** [[Authentication (LDAP, Database...) >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication]] * [[Backup/Restore >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Backup]] ** [[Import/Export pages >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/ImportExport]] * [[Security tuning >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Security]] * [[Performance tuning >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Security]] * [[Virtual Wikis >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualization]] * [[Clustering >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Clustering]] * [[Administrator Cookbook >> Drafts.XEDocAdminCookbook]] = Further information = * [[User mailing list >>Community.MailingLists]] * [[JIRA (planned features, reported bugs, workarounds) >> https://jira.xwiki.org/secure/Dashboard.jspa]] {{warning}} You shouldn't write your questions as comments to the documentation pages, because in this way these will remain unanswered!

profile : * Java proficiency * Familiar with unit testing concepts and best practices * Familiar with functional testing concepts and best practices ** Experience with Selenium and the [[Page Objects>>url:https://code.google.com/p/selenium/wiki/PageObjects]] pattern is preferred * Familiar with web technologies: HTML/CSS/JavaScript * Experience in (unit/functional) testing a previous open source project is a big plus * Willingness to learn and to improve both him/herself and the project

We hope to discover new talented contributors that share the same faith we have in the wiki concept and want to build on top of it. What would your org consider to be a successful GSoC program?

We hope to discover new talented contributors that share the same faith we have in the wiki concept and want to build on top of it. How many potential mentors do you have for this year's program?

We hope to discover new talented contributors that share the same faith we have in the wiki concept and want to build on top of it. === What would your org consider to be a successful GSoC program?

We hope to discover new talented contributors that share the same faith we have in the wiki concept and want to build on top of it. == How many potential mentors do you have for this year's program?

Concept This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model.

{{box cssClass="floatinginfobox" title="**Contents**"}} {{toc/}} {{/box}} = Concept = This is about writing "unit" tests for code generated by the server-side for the "View" of the MVC model.

{{/version}} = Examples = == Full Examples == * {{scm path="xwiki-platform-core/xwiki-platform-menu/xwiki-platform-menu-test/xwiki-platform-menu-test-docker/src/test/it/org/xwiki/menu/test/ui/MenuIT.java"}}MenuIT{{/scm}} * {{scm path="xwiki-platform-core/xwiki-platform-mail/xwiki-platform-mail-test/xwiki-platform-mail-test-docker/src/test/it/org/xwiki/mail/test/ui/MailIT.java"}}MailIT{{/scm}} == Example 1: Basic test == {{code language="java"}} @UITest public class SeleniumTest { @Test public void test(XWikiWebDriver driver, TestUtils setup) { driver.get("http://xwiki.org"); assertThat(driver.getTitle(), containsString("XWiki - The Advanced Open Source Enterprise and Application Wiki")); driver.findElement(By.linkText("XWiki's concept")).click(); } } {{/code}} == Example 2: Choosing Container + DB + Browser and versions == {{code language="java"}} @UITest(database = Database.MYSQL, databaseTag = "5", servletEngine = ServletEngine.TOMCAT, servletEngineTag = "8", browser = Browser.CHROME) public class MenuIT ...

The Java Portlet Specification allows coordination on the UI layer with different means, such as events, application sessions, and public render parameters, in order to provide a deep and seamless integration between the different services. Portlet Concepts a portal is a web based application that commonly provides personalization, authentication, content aggregation from different sources and hosts the presentation layer of information systems a portlet is an application that provides a specific piece of content (information or service) to be included as part of a portal page web clients interact with portlets via a request/response paradigm implemented by the portal a portlet container runs portlets and provides them with the required runtime environment manages the life cycle of portlets provides persistent storage for portlet preferences a portlet mode indicates the function a portlet is performing in the render method standard portlet modes are: view, edit and help view: generate markup reflecting the current state of the portlet edit: customize the behavior of the portlet help: provide help information about the portlet a portlet window is the visual component used to display the content generated by a portlet within portal pages a window state is an indicator of the amount of portal page space that will be assigned to the content generated by a portlet via the render method possible window states are: normal, maximized and minimized Portlet Life Cycle The life cycle of a portlet is expressed through the init, processAction, render and destroy methods of the Portlet interface.

The Java Portlet Specification allows coordination on the UI layer with different means, such as events, application sessions, and public render parameters, in order to provide a deep and seamless integration between the different services. == Portlet Concepts == image:portalPageCreation.png * a **portal** is a web based application that commonly provides personalization, authentication, content aggregation from different sources and hosts the presentation layer of information systems * a **portlet** is an application that provides a specific piece of content (information or service) to be included as part of a portal page ** web clients interact with portlets via a request/response paradigm implemented by the portal * a **portlet container** runs portlets and provides them with the required runtime environment ** manages the life cycle of portlets ** provides persistent storage for portlet preferences image:elementsOfAPortalPage.png * a **portlet mode** indicates the function a portlet is performing in the render method ** standard portlet modes are: view, edit and help ** view: generate markup reflecting the current state of the portlet ** edit: customize the behavior of the portlet ** help: provide help information about the portlet * a **portlet window** is the visual component used to display the content generated by a portlet within portal pages * a **window state** is an indicator of the amount of portal page space that will be assigned to the content generated by a portlet via the render method ** possible window states are: normal, maximized and minimized == Portlet Life Cycle == The life cycle of a portlet is expressed through the ##init##, ##processAction##, ##render## and ##destroy## methods of the ##Portlet## interface.

Analyzing the topics that are covered in different documents of a wiki can help organizing the wiki by, e.g., assigning tags to documents of a topic or grouping documents of a topic in a space (a concept in XWiki that is similar to a directory in a filesystem).