Search: concept

) This concept is to replace (in a lazy way) initial HTML by a richer HTML. What I mean by richer? In order

, expanding the DocumentName concept) Annotation model changes to store such a reference to a field

? === ==== Solution n°1 : Richer HTML (not used) ==== This concept is to replace (in a lazy way) initial HTML

will be devised (for example, expanding the DocumentName concept) * Annotation model changes to store

architecture using a Component Manager * Each component group (set of components for implementing a concept

:" page : .../xwiki/bin/inline/Blog/Commuter+Train+Morning+Work For not IT users, the Parent concept

:" page : .../xwiki/bin/inline/Blog/Commuter+Train+Morning+Work For not IT users, the Parent concept

Commons and XWiki Rendering. Since these 2 projects contain libraries that are independent of the concept

on the old cache services concepts even all the names changes but the more I'm working with JBoss cache

eviction algorithms concept like JBoss or cache4j do to replace the way restriction like capacity

on the old cache services concepts even all the names changes but the more I'm working with JBoss cache

thinking of introduce eviction algorithms concept like JBoss or cache4j do to replace the way restriction

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

workspace. Users have the possibility to enhance the public graphs locally by adding concepts and relations

on a view concept for the tailoring of ontologies. This view concept turned out to be of additional value

to enhance the public graphs locally by adding concepts and relations that make sense to them, involving

. It is also based on a view concept for the tailoring of ontologies. This view concept turned out

XWiki Help Desk Data Model Proposal of a preliminary data model/ The terms "Issue" and "IssueLog" are used preferably to "Question" and "Answer" since the help desk concepts are very close to the ones of an issue tracker, and using a common data model for both may be handy. Issue Title Description Language

= XWiki Help Desk Data Model = Proposal of a preliminary data model/ The terms "Issue" and "IssueLog" are used preferably to "Question" and "Answer" since the help desk concepts are very close to the ones of an issue tracker, and using a common data model for both may be handy. |=Issue |Title

done for links. Live filtering is a nice concept, but in an already JS-heavy interface it's better

longer, specially for power users, but Laurent defended the whole wizard concept by saying