Menu
▾
▴
[Cobricks-cvscommit] cobricks2/docs Project_wiki.html Projects.html Wikibild.png Wikilanguage.html Activities.html CWall_MeetingView.html CWall_RFID_Component.html CWall_doc.html Category_doc.html Cobricks2_doc.html Cobricks_Mailinglist_Howto.html Comparable.html Context_doc.html Core_doc.html Course_UnivISSync.html Course_doc.html Current_events.html Docs.html Einstieg_TUM.html Env_doc.html Env_doc_TUM.html INSTALL.html Ideas.html Item_BSCW_doc.html Item_RSS.html Item_Search.html Item_display_doc.html Item_doc.html Item_storage.html LogBrowser.html Main_Page.html Meeting_Mirror.html Meeting_Mirror_related.html Message_doc.html Migration_doc.html Portal_Jetspeed.html Portal_doc.html UML_Class_Diagramm_of_UserCard.html UML_class_diagramm_for_CircleControllButton.html UML_class_diagramm_of_CategoryBar.html UML_class_diagramm_of_CategoryIcon.html UML_class_diagramm_of_CategorySourceWS.html UML_class_diagramm_of_CommunityView.html UML_class_diagramm_of_both_PositioningStrategies.html User_FOAF.html User_doc.html Voting_doc.html index.html
Update of /cvsroot/cobricks/cobricks2/docs In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19169 Modified Files: Activities.html CWall_MeetingView.html CWall_RFID_Component.html CWall_doc.html Category_doc.html Cobricks2_doc.html Cobricks_Mailinglist_Howto.html Comparable.html Context_doc.html Core_doc.html Course_UnivISSync.html Course_doc.html Current_events.html Docs.html Einstieg_TUM.html Env_doc.html Env_doc_TUM.html INSTALL.html Ideas.html Item_BSCW_doc.html Item_RSS.html Item_Search.html Item_display_doc.html Item_doc.html Item_storage.html LogBrowser.html Main_Page.html Meeting_Mirror.html Meeting_Mirror_related.html Message_doc.html Migration_doc.html Portal_Jetspeed.html Portal_doc.html UML_Class_Diagramm_of_UserCard.html UML_class_diagramm_for_CircleControllButton.html UML_class_diagramm_of_CategoryBar.html UML_class_diagramm_of_CategoryIcon.html UML_class_diagramm_of_CategorySourceWS.html UML_class_diagramm_of_CommunityView.html UML_class_diagramm_of_both_PositioningStrategies.html User_FOAF.html User_doc.html Voting_doc.html index.html Added Files: Project_wiki.html Projects.html Wikibild.png Wikilanguage.html Log Message: Index: CWall_MeetingView.html =================================================================== RCS file: /cvsroot/cobricks/cobricks2/docs/CWall_MeetingView.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- CWall_MeetingView.html 13 Dec 2005 09:08:50 -0000 1.4 +++ CWall_MeetingView.html 10 Feb 2006 12:00:01 -0000 1.5 @@ -1,39 +1,11 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr"> - <head> - <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> - <meta name="KEYWORDS" content="CWall MeetingView,CWall doc,Meeting Mirror,UML Class Diagramm of UserCard,UML class diagramm of CategoryBar,UML class diagramm of CategoryIcon,UML class diagramm for CircleControllButton,UML class diagramm of CategorySourceWS,UML class diagramm of both PositioningStrategies,UML class diagramm of CommunityView" /> -<meta name="robots" content="index,follow" /> -<link rel="shortcut icon" href="http://131.159.24.138/favicon.ico" /> -<link title="Creative Commons" type="application/rdf+xml" href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=creativecommons" rel="meta" /> -<link rel="copyright" href="http://www.gnu.org/copyleft/fdl.html" /> - - <title>CWall MeetingView - CobricksWiki</title> - <style type="text/css" media="screen,projection">/*<![CDATA[*/ @import "/wiki/mw/stylesheets/monobook/main.css"; /*]]>*/</style> - <link rel="stylesheet" type="text/css" media="print" href="commonPrint.css"/> - <!--[if IE]><style type="text/css" media="all">@import "/wiki/mw/stylesheets/monobook/IEFixes.css";</style> - <script type="text/javascript" src="/wiki/mw/stylesheets/IEFixes.js"></script> - <meta http-equiv="imagetoolbar" content="no" /><![endif]--> - <script src="http://131.159.24.138/wiki/mw/index.php?title=-&action=raw&gen=js" type="text/javascript"></script> - <script type="text/javascript" src="wikibits.js"></script> - <style type="text/css">/*<![CDATA[*/ @import "/wiki/mw/index.php?title=-&action=raw&gen=css"; - /*]]>*/</style> - - </head> - <body class="ns-0"> - <div id="globalWrapper"> - <div id="column-content"> - <div id="content"> - - <a name="top" id="contentTop"></a> - <h1 class="firstHeading">CWall MeetingView</h1> - <div id="bodyContent"> - <h3 id="siteSub">From CobricksWiki</h3> - <div id="contentSub"></div> - - - - <!-- start content --> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> +<title>CobricksWiki</title> +<link rel="stylesheet" type="text/css" href="style.css"/> +</head> +<body class="ns-0"> +<!-- start content --> <p><strong> Meeting View </strong> </p><p>View for CWall implemented in package org.cobricks.cwall.meeting </p><p>(also see <a href="CWall_doc.html" title ="CWall doc">CWall documentation</a>) @@ -124,16 +96,16 @@ </p> </div> </td></tr></table> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=1" title ="CWall MeetingView">edit</a>]</div><a name="Screen_Layout"></a><h2> Screen Layout </h2> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=2" title ="CWall MeetingView">edit</a>]</div><a name="CommunityView"></a><h3> CommunityView </h3> +<a name="Screen_Layout"></a><h2> Screen Layout </h2> +<a name="CommunityView"></a><h3> CommunityView </h3> <p>The CommunityView class is the very center of the meetingmirror. If you want to understand how the meetingmirror is working you need to understand this class. It Controlls most interactionevents like MouseEvents, and holds the informations about the states (like if the view is in searchmode, or if it has a CategoryBar, which UserIcons are displayed and so on) </p><p><a href="UML_class_diagramm_of_CommunityView.html" title ="UML class diagramm of CommunityView">UML class diagramm of CommunityView</a> </p><p><br /> If an RFID Reader is connected look here for further information how the CommunityView/MeetingMirror works: <a href="CWall_MeetingView.html#Modifications_of_the_meeting_mirror" title ="CWall MeetingView">Modifications of the meeting mirror</a> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=3" title ="CWall MeetingView">edit</a>]</div><a name="User_icons"></a><h3> User icons </h3> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=4" title ="CWall MeetingView">edit</a>]</div><a name="User_Card"></a><h3> User Card </h3> +<a name="User_icons"></a><h3> User icons </h3> +<a name="User_Card"></a><h3> User Card </h3> <p>The UserCard is responsible for displaying the information about an User on the screen and to allow the User in front of it to interact with it. At the moment every User can change the Category membership of any user. But this can be changed if the Methode UserCard.isUserRegistered() has been implemented with i.e. RFID. </p><p><a href="UML_Class_Diagramm_of_UserCard.html" title ="UML Class Diagramm of UserCard">UML Class Diagramm of UserCard</a> </p><p>To change the appeareance of the UserCard you can use the following settings in the properties.txt file. @@ -169,7 +141,7 @@ </p><p><br /> </p><p>While an RFID reader is connected, look here for more information: <a href="CWall_MeetingView.html#UserCard_RFID" title ="CWall MeetingView">UserCard RFID</a> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=5" title ="CWall MeetingView">edit</a>]</div><a name="Category_Bar"></a><h3> Category Bar </h3> +<a name="Category_Bar"></a><h3> Category Bar </h3> <p>The CategoryBar contains certain Categorys defined in the properties.txt and displays them on the screen. The User can interact with it, by searching for a certain Category, or highlighting the Users currently displayed on the screed which are members of the selected Category. </p><p><a href="UML_class_diagramm_of_CategoryBar.html" title ="UML class diagramm of CategoryBar">UML class diagramm of CategoryBar</a> </p><p><a href="UML_class_diagramm_of_CategoryIcon.html" title ="UML class diagramm of CategoryIcon">UML class diagramm of CategoryIcon</a> @@ -236,7 +208,7 @@ </pre> <p>searchicon is the small icon displayed within an activated (clicked) CategoryIcon which will start a search for that Category if clicked. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=6" title ="CWall MeetingView">edit</a>]</div><a name="CircleControllButton"></a><h3> CircleControllButton </h3> +<a name="CircleControllButton"></a><h3> CircleControllButton </h3> <p>The CircleControllButton is controlling the speed and direction of the searchresult circle. It also displays the numbers of searchresults and the name of the initiated search. </p><p><a href="UML_class_diagramm_for_CircleControllButton.html" title ="UML class diagramm for CircleControllButton">UML class diagramm for CircleControllButton</a> </p><p>To change the appeareance of the CircleControllButton you can use the following settings in the properties.txt file. @@ -321,24 +293,24 @@ </pre> <p>String which is used to display the Results </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=7" title ="CWall MeetingView">edit</a>]</div><a name="Search_Dialog"></a><h3> Search Dialog </h3> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=8" title ="CWall MeetingView">edit</a>]</div><a name="Search_mode_.2F_results"></a><h3> Search mode / results </h3> +<a name="Search_Dialog"></a><h3> Search Dialog </h3> +<a name="Search_mode_.2F_results"></a><h3> Search mode / results </h3> <p>Kurz: Bedienung </p><p>Konfiguration </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=9" title ="CWall MeetingView">edit</a>]</div><a name="Implementation"></a><h2> Implementation </h2> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=10" title ="CWall MeetingView">edit</a>]</div><a name="Category_Source"></a><h3> Category Source </h3> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=11" title ="CWall MeetingView">edit</a>]</div><a name="CateorySourceWS"></a><h4> CateorySourceWS </h4> +<a name="Implementation"></a><h2> Implementation </h2> +<a name="Category_Source"></a><h3> Category Source </h3> +<a name="CateorySourceWS"></a><h4> CateorySourceWS </h4> <p>CategorySourceWS is an so far uncomplete implementation of the CategorySource interface, which handles the data of Categorys using the WebService. To complete the implementation, a block of code needs to be uncommented which tries to initiate the CategoryManagerStub, which is not working correctly at the moment. </p><p><a href="UML_class_diagramm_of_CategorySourceWS.html" title ="UML class diagramm of CategorySourceWS">UML class diagramm of CategorySourceWS</a> </p><p><br /> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=12" title ="CWall MeetingView">edit</a>]</div><a name="Positioning_Strategies"></a><h3> Positioning Strategies </h3> +<a name="Positioning_Strategies"></a><h3> Positioning Strategies </h3> <p><a href="UML_class_diagramm_of_both_PositioningStrategies.html" title ="UML class diagramm of both PositioningStrategies">UML class diagramm of both PositioningStrategies</a> </p><p>Positioning Strategy for RFID identified Icons: <a href="CWall_MeetingView.html#Online_users_-_new_positioning_strategy" title ="">Online users - new positioning strategy</a> </p><p><br /> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=13" title ="CWall MeetingView">edit</a>]</div><a name="RandomizedPositioningStrategy"></a><h4> RandomizedPositioningStrategy </h4> +<a name="RandomizedPositioningStrategy"></a><h4> RandomizedPositioningStrategy </h4> <p>Calculates the random points for the given number of icons on the given screen without overlapping. </p><p>First the space around the already placed icons gets devided into rectangles. @@ -378,11 +350,11 @@ <p>However, not always all the icons can be placed using real randomization, because it places the icons too inefficient. In case of a 3 time failure to place all icons with this strategy, it calls the SpaceSavingPositioningStrategy class </p><p><br /> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=14" title ="CWall MeetingView">edit</a>]</div><a name="RandomizedPositioningStrategy_-_RFID_Reader_connected"></a><h5> RandomizedPositioningStrategy - RFID Reader connected </h5> +<a name="RandomizedPositioningStrategy_-_RFID_Reader_connected"></a><h5> RandomizedPositioningStrategy - RFID Reader connected </h5> <p>In case of an connected RFID reader there is an additional check in this strategy. The new calculated coordinates of the icons to be displayed are not allowed to lie within the given rfid dimension! </p><p>In case they do, new coordinates will be calculated. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=15" title ="CWall MeetingView">edit</a>]</div><a name="SpaceSavingPositioningStrategy"></a><h4> SpaceSavingPositioningStrategy </h4> +<a name="SpaceSavingPositioningStrategy"></a><h4> SpaceSavingPositioningStrategy </h4> <p>Devides the display into equal rectangles in number higher or equal to the number of icons to display. Then randomly assings each icon to one of the rectangles. After that each icon gets randomly placed within his assinged @@ -390,7 +362,7 @@ that can fit into the screen without overlapping by keeping maximum possible randomization </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=16" title ="CWall MeetingView">edit</a>]</div><a name="Source_Definitions"></a><h2> Source Definitions </h2> +<a name="Source_Definitions"></a><h2> Source Definitions </h2> <p>The Meeting View retrieves its data using Source interfaces. Currently, there is an interface named org.cobricks.cwall.meeting.UserSource for retrieving user data. A class implementing the UserSource interface has to be specified in the view properties. </p><p>Currently, the following implementations of UserSource are available: </p> @@ -398,13 +370,13 @@ </li><li> org.cobricks.cwall.meeting.UserSourceWS - get the user data from a Cobricks server (via SOAP/WebServices) </li><li> org.cobricks.cwall.meeting.UserSourceBSCW - get the user data from a BSCW server </li></ul> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=17" title ="CWall MeetingView">edit</a>]</div><a name="UserSourceDB"></a><h3> UserSourceDB </h3> +<a name="UserSourceDB"></a><h3> UserSourceDB </h3> <p>TBD </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=18" title ="CWall MeetingView">edit</a>]</div><a name="UserSourceWS"></a><h3> UserSourceWS </h3> +<a name="UserSourceWS"></a><h3> UserSourceWS </h3> <p>TBD </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=19" title ="CWall MeetingView">edit</a>]</div><a name="UserSourceBSCW"></a><h3> UserSourceBSCW </h3> +<a name="UserSourceBSCW"></a><h3> UserSourceBSCW </h3> <p>Get the user data from a BSCW workspace using the X-BSCW API. See <a href="http://www.bscw.de/" class='external' title="http://www.bscw.de/">http://www.bscw.de/</a> for more information on BSCW and <a href="http://bscw.fit.fraunhofer.de/api/" class='external' title="http://bscw.fit.fraunhofer.de/api/">http://bscw.fit.fraunhofer.de/api/</a> for more information on the X-BSCW API. </p><p>Currently, the following user attributes are loaded from BSCW: </p> @@ -432,7 +404,7 @@ cwall.view.mm.bscw.user=USER cwall.view.mm.bscw.pw=PW </pre> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=20" title ="CWall MeetingView">edit</a>]</div><a name="Usage"></a><h4> Usage </h4> +<a name="Usage"></a><h4> Usage </h4> <p>You can start the MeetingMirror client with a BSCW UserSource from the command line version easily by typing </p> <pre> @@ -441,11 +413,11 @@ </pre> <p><br /> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=21" title ="CWall MeetingView">edit</a>]</div><a name="CWall_PDA"></a><h2> CWall PDA </h2> +<a name="CWall_PDA"></a><h2> CWall PDA </h2> <p>The CWall PDA client is a stand-alone C# application. Itâs implemented for use in a Windows CE environment. </p><p>CWall PDA loads user information from Cobricks-2 platform and saves these information in an own database. The PDA user can search for other users by specifying several search attributes and bookmark them in a special list. In addition to displaying information it is also possible to interact with the CWall to influence which users are displayed in details view or to bookmark the currently shown users of the CWall. It is also possible to edit the own data and update the Cobricks-2 platform. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=22" title ="CWall MeetingView">edit</a>]</div><a name="Installation"></a><h3> Installation </h3> +<a name="Installation"></a><h3> Installation </h3> <p>You have to install the Cobricks-2 Platform, the Meeting Mirror IRDA-Server and the CWall PDA application. </p><p><strong>Cobricks-2 Platform</strong> </p><p>Please go to <a href="http://www.cobricks.de" class='external' title="http://www.cobricks.de">http://www.cobricks.de</a> and use the Link to Wiki to read more about the installation of the Cobricks-2 platform. @@ -628,7 +600,7 @@ <p>server: The Cobricks-2 platform server name. </p><p>port: The Cobricks-2 platform server port. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=23" title ="CWall MeetingView">edit</a>]</div><a name="CWall_PDA_packages"></a><h3>CWall PDA packages</h3> +<a name="CWall_PDA_packages"></a><h3>CWall PDA packages</h3> <p>See the following sections for information how the application is implemented. </p><p>The program is realized with the MVC pattern. The form component and all supported views act as the View. The user database represents the Model. The Controller is integrated in the views because of the small business logic. </p><p>The C# classes are grouped into several packages. @@ -802,7 +774,7 @@ </p><p><small ><strong>UML class diagramm: CobricksUser</strong></small > </p><p><a href="http://131.159.24.138/wiki/mw/index.php/Image:Classdiagram_cobuser.jpg" class="image" title="Image:Classdiagram_cobuser.jpg"><img src="Classdiagram_cobuser.jpg" alt="Image:Classdiagram_cobuser.jpg" /></a> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=24" title ="CWall MeetingView">edit</a>]</div><a name="Future_Work.2FExtentions"></a><h3>Future Work/Extentions</h3> +<a name="Future_Work.2FExtentions"></a><h3>Future Work/Extentions</h3> <p>In this chapter we want to list some further steps and future extentions for the CWall PDA project . </p> <ul><li> Synchronisation via Bluetooth: an option to enable synchronisation with the Cobricks2 database for pocket pc users without wireless lan. @@ -815,7 +787,7 @@ </li></ul> <p><br /> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=25" title ="CWall MeetingView">edit</a>]</div><a name="User_Manual"></a><h3>User Manual</h3> +<a name="User_Manual"></a><h3>User Manual</h3> <p><strong>Starting the Application</strong> </p><p>Start the application by using the shortcut which is created in the menu âProgrammeâ or go the directory â/Programme/PDACobricksâ and start from there the application. </p><p>After having started the application you will see the Welcome-View(see figure 1). @@ -892,15 +864,15 @@ When you are satisfied with your new profile you can send it to the Cobricks-2 platform by pushing the âUpdateâ button. With the âZurückâ button you will go back to the previous View. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=26" title ="CWall MeetingView">edit</a>]</div><a name="CWall_RFID"></a><h2> CWall RFID </h2> +<a name="CWall_RFID"></a><h2> CWall RFID </h2> <p><em>As soon as we finished the RFID Project, we will document the whole project. Until this time, this chapter will continually be changed.</em> </p><p>This part of the Meeting Mirror was implemented to work with RFID reader of the German company FEIG ELECTRONIC GmbH. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=27" title ="CWall MeetingView">edit</a>]</div><a name="Motivation"></a><h3> Motivation </h3> +<a name="Motivation"></a><h3> Motivation </h3> <p>This component of the Meeting Mirror is an option for users to identify themselves by rfid (radio frequency identification). The identification is used to get interesting information by users. Therefore a simple matching is implemented. Results of the matching are displayed like the anomynous search on the wide screen. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=28" title ="CWall MeetingView">edit</a>]</div><a name="Installation_2"></a><h3> Installation </h3> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=29" title ="CWall MeetingView">edit</a>]</div><a name="Connecting_the_RFID-Reader"></a><h4> Connecting the RFID-Reader </h4> +<a name="Installation_2"></a><h3> Installation </h3> +<a name="Connecting_the_RFID-Reader"></a><h4> Connecting the RFID-Reader </h4> <p>The Java class library ID OBIDISC4J from FEIG ELECTRONIC GmbH represents yet another component for simplifying the development of application programs in Java for OBID i-scan and OBID classic-pro readers. </p><p>The Java class library ID OBIDISC4J currently supports Windows and Linux (for x86 oricessors only). The library is based on the C++ class library ID FEDM as we´ll as the native function libraries ID FECOM, ID FEUSB(for Windos Versions only), ID FETCP and IC FEISC. </p><p>For further information please read the dokumentation of the reader software. @@ -951,7 +923,7 @@ </li></ul> <p>Copy the OBID4ISCJ.jar file to the directory: <JAVA_HOME>\jre\lib\ext. Alternately you can select any other directory, as long as you tell this to the Java Classpath. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=30" title ="CWall MeetingView">edit</a>]</div><a name="Settings"></a><h4> Settings </h4> +<a name="Settings"></a><h4> Settings </h4> <p>The following settings have to be done in localproperties.txt, to configure the rfid-reader interface, if they should be different to the following: </p> <pre> @@ -977,7 +949,7 @@ <p>Next settings describe the maximum tablesize, the reader tries to read from tags (it should be two to the power of minimum seven; 2^7) and the time, an user will be kept online, after his tag was lastly recognized by the reader. The sleeptime is the intervall, the reading-thread will be restarted. If your setting shell be different, you have to change them in your localproperties.txt. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=31" title ="CWall MeetingView">edit</a>]</div><a name="Eclipse.2C_ANT.2C_build.xml_and_build.properties"></a><h4> Eclipse, ANT, build.xml and build.properties </h4> +<a name="Eclipse.2C_ANT.2C_build.xml_and_build.properties"></a><h4> Eclipse, ANT, build.xml and build.properties </h4> <p>In order to show ant, where it can find the driver of the rfid reader, you have to set the parameter 'rfid.home' in the build.properties: </p> <pre> @@ -999,28 +971,28 @@ </pre> <p>Please do not delete the classes from cvs! </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=32" title ="CWall MeetingView">edit</a>]</div><a name="RFID_component"></a><h3> RFID component </h3> +<a name="RFID_component"></a><h3> RFID component </h3> <p>The rfid component is an extension of the meeting mirror to get a list of users, standing actually in front of it. The rfid module (org.cobricks.cwall.meeting.rfid.*) is a thread, which sends requests to a rfid-reader in certain time intervals. The rfid reader answers to these requests with a list of perceived tags/rfids. The rfid thread compares the list of tags with the list of users, got from the cobricks database. After that the thread creates a new list of users, which are online and makes it available for the meeting mirror application. </p><p>The rfid reader is connected to either a serial RS232-interface, an USB or a TCP/IP interface (Up to now only the serial interface was tested with a LongRange reader of FEIG Electronics GmbH (www.feig.de), model ID ISC.LR200). </p><p>The exact functionality shell be shown in the following sections. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=33" title ="CWall MeetingView">edit</a>]</div><a name="UML_class_diagram"></a><h4> UML class diagram </h4> +<a name="UML_class_diagram"></a><h4> UML class diagram </h4> <p>tbd </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=34" title ="CWall MeetingView">edit</a>]</div><a name="Reader_thread"></a><h4> Reader thread </h4> +<a name="Reader_thread"></a><h4> Reader thread </h4> <p>tbd </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=35" title ="CWall MeetingView">edit</a>]</div><a name="Modification_of_the_database"></a><h4> Modification of the database </h4> +<a name="Modification_of_the_database"></a><h4> Modification of the database </h4> <p>tbd </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=36" title ="CWall MeetingView">edit</a>]</div><a name="Modifications_of_the_meeting_mirror"></a><h3> Modifications of the meeting mirror </h3> +<a name="Modifications_of_the_meeting_mirror"></a><h3> Modifications of the meeting mirror </h3> <p>The connection of an rfid reader causes some changes in the meetingmirror: </p><p>In the properties you can define, if the reader should be activated or not. </p> <pre> cwall.view.mm.rfid.activate=false </pre> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=37" title ="CWall MeetingView">edit</a>]</div><a name="Community_view"></a><h4> Community view </h4> +<a name="Community_view"></a><h4> Community view </h4> <p>As you know, the CommunityView is the point of controll of most interactionevents. </p><p>There is something new, if an reader is connected: </p> @@ -1032,7 +1004,7 @@ </li><li> ClickEvent on not-identified User: <a href="CWall_MeetingView.html#UserCard_RFID" title ="CWall MeetingView">UserCard RFID</a> </li></ul> </li></ul> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=38" title ="CWall MeetingView">edit</a>]</div><a name="Online_users_-_new_positioning_strategy"></a><h4> Online users - new positioning strategy </h4> +<a name="Online_users_-_new_positioning_strategy"></a><h4> Online users - new positioning strategy </h4> <p>The new strategy positions the icons of the online users (identified by RFID Reader) on a given rfid dimension. The strategy calculates, knowing the dimension of the icons, how many icons fit into rfid_home_dim.width and into rfid_home_dim.height. So we know how many icons fit into the dimension at all. If there are too many users online, the dimension of the icons will be reduced. </p><p>The strategy takes the coordinates so that the icons will be placed one after another. @@ -1055,10 +1027,10 @@ </pre> <p>These icons, which are displayed in that seperate area, are not in the permanent change of all displayed icons. This is guaranteed by a function in the PrioritySchedulingStrategy. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=39" title ="CWall MeetingView">edit</a>]</div><a name="UserCard_RFID"></a><h4> UserCard RFID </h4> +<a name="UserCard_RFID"></a><h4> UserCard RFID </h4> <p>The UserCard now also shows the lastseenDate of the User. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit&section=40" title ="CWall MeetingView">edit</a>]</div><a name="Automatic_Matching"></a><h3> Automatic Matching </h3> +<a name="Automatic_Matching"></a><h3> Automatic Matching </h3> <p>While there is an ClickEvent on an rfid-identifed UserIcon, the Automatic Matching starts. </p><p>So the user standing infront of the screen is able to look for other useres, who have for example the same interests. </p><p><br /> @@ -1073,82 +1045,5 @@ Retrieved from "<a href="CWall_MeetingView.html">http://131.159.24.138/wiki/mw/index.php/CWall_MeetingView</a>"</div> - <!-- end content --> - <div class="visualClear"></div> - </div> - </div> - </div> - <div id="column-one"> - <div id="p-cactions" class="portlet"> - <h5>Views</h5> - <ul> - <li id="ca-nstab-main" class="selected"><a href="CWall_MeetingView.html">Article</a></li><li id="ca-talk" class="new"><a href="http://131.159.24.138/wiki/mw/index.php?title=Talk:CWall_MeetingView&action=edit">Discussion</a></li><li id="ca-edit" class=""><a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=edit">Edit</a></li><li id="ca-history"><a href="http://131.159.24.138/wiki/mw/index.php?title=CWall_MeetingView&action=history">History</a></li> - </ul> - </div> - <div class="portlet" id="p-personal"> - <h5>Personal tools</h5> - <div class="pBody"> - <ul> - <li id="pt-login"><a href="http://131.159.24.138/wiki/mw/index.php?title=Special:Userlogin&returnto=CWall_MeetingView">Log in</a></li> - </ul> - </div> - </div> - <div class="portlet" id="p-logo"> - <a title="Main Page" style="background-image: url(/wiki/mw/stylesheets/images/wiki.png);" href="Main_Page.html"></a> - </div> - <div class="portlet" id="p-nav"> - <h5>Navigation</h5> - <div class="pBody"> - <ul> - <li id="n-mainpage"><a href="Main_Page.html">Main Page</a></li> - <li id="n-portal"><a href="http://131.159.24.138/wiki/mw/index.php/CobricksWiki:Community_Portal">Community portal</a></li> - <li id="n-currentevents"><a href="Current_events.html">Current events</a></li> - <li id="n-recentchanges"><a href="http://131.159.24.138/wiki/mw/index.php/Special:Recentchanges">Recent changes</a></li> - <li id="n-randompage"><a href="http://131.159.24.138/wiki/mw/index.php/Special:Randompage">Random page</a></li> - <li id="n-help"><a href="http://131.159.24.138/wiki/mw/index.php/Help:Contents">Help</a></li> - - </ul> - </div> - </div> - <div id="p-search" class="portlet"> - <h5>Search</h5> - <div class="pBody"> - <form name="searchform" action="http://131.159.24.138/wiki/mw/index.php/Special:Search" id="searchform"> - <input accesskey="f" id="searchInput" name="search" type="text" /> - <input value="Go" type="submit" name="go" class="searchButton" /> <input value="Search" type="submit" name="fulltext" class="searchButton" /> - </form> - </div> - </div> - <div class="portlet" id="p-tb"> - <h5>Toolbox</h5> - <div class="pBody"> - <ul> - <li id="t-whatlinkshere"><a href="http://131.159.24.138/wiki/mw/index.php?title=Special:Whatlinkshere&target=CWall_MeetingView">What links here</a></li> - <li id="t-recentchangeslinked"><a href="http://131.159.24.138/wiki/mw/index.php?title=Special:Recentchangeslinked&target=CWall_MeetingView">Related changes</a></li> - - - - - <li id="t-specialpages"><a href="http://131.159.24.138/wiki/mw/index.php/Special:Specialpages">Special pages</a></li> - </ul> - </div> - </div> - - </div><!-- end of the left (by default at least) column --> - <div class="visualClear"></div> - <div id="footer"> - <div id="f-poweredbyico"><a href="http://www.mediawiki.org/"><img src="poweredby_mediawiki_88x31.png" alt="MediaWiki" /></a></div> - <div id="f-copyrightico"><a href="http://www.gnu.org/copyleft/fdl.html"><img src="gnu-fdl.png" alt='GNU Free Documentation License 1.2' /></a></div> - <ul id="f-list"> - <li id="f-lastmod"> This page was last modified 09:26, 4 Nov 2005.</li> - <li id="f-viewcount">This page has been accessed 895 times.</li> - - <li id="f-copyright">Content is available under <a href="http://www.gnu.org/copyleft/fdl.html" class='external' title="http://www.gnu.org/copyleft/fdl.html">GNU Free Documentation License 1.2</a>.</li> - <li id="f-about"><a href="http://131.159.24.138/wiki/mw/index.php/CobricksWiki:About" title ="CobricksWiki:About">About CobricksWiki</a></li> - <li id="f-disclaimer"><a href="http://131.159.24.138/wiki/mw/index.php/CobricksWiki:General_disclaimer" title ="CobricksWiki:General disclaimer">Disclaimers</a></li> - </ul> - </div> - </div> - <!-- Served by atschlichter43 in 1.06 secs. --> - </body> -</html> +<!-- end content --> +</body></html> Index: Cobricks2_doc.html =================================================================== RCS file: /cvsroot/cobricks/cobricks2/docs/Cobricks2_doc.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -d -r1.6 -r1.7 --- Cobricks2_doc.html 13 Dec 2005 09:08:50 -0000 1.6 +++ Cobricks2_doc.html 10 Feb 2006 12:00:02 -0000 1.7 @@ -1,39 +1,11 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr"> - <head> - <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> - <meta name="KEYWORDS" content="Cobricks2 doc" /> -<meta name="robots" content="index,follow" /> -<link rel="shortcut icon" href="http://131.159.24.138/favicon.ico" /> -<link title="Creative Commons" type="application/rdf+xml" href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=creativecommons" rel="meta" /> -<link rel="copyright" href="http://www.gnu.org/copyleft/fdl.html" /> - - <title>Cobricks2 doc - CobricksWiki</title> - <style type="text/css" media="screen,projection">/*<![CDATA[*/ @import "/wiki/mw/stylesheets/monobook/main.css"; /*]]>*/</style> - <link rel="stylesheet" type="text/css" media="print" href="commonPrint.css"/> - <!--[if IE]><style type="text/css" media="all">@import "/wiki/mw/stylesheets/monobook/IEFixes.css";</style> - <script type="text/javascript" src="/wiki/mw/stylesheets/IEFixes.js"></script> - <meta http-equiv="imagetoolbar" content="no" /><![endif]--> - <script src="http://131.159.24.138/wiki/mw/index.php?title=-&action=raw&gen=js" type="text/javascript"></script> - <script type="text/javascript" src="wikibits.js"></script> - <style type="text/css">/*<![CDATA[*/ @import "/wiki/mw/index.php?title=-&action=raw&gen=css"; - /*]]>*/</style> - - </head> - <body class="ns-0"> - <div id="globalWrapper"> - <div id="column-content"> - <div id="content"> - - <a name="top" id="contentTop"></a> - <h1 class="firstHeading">Cobricks2 doc</h1> - <div id="bodyContent"> - <h3 id="siteSub">From CobricksWiki</h3> - <div id="contentSub"></div> - - - - <!-- start content --> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> +<head> +<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> +<title>CobricksWiki</title> +<link rel="stylesheet" type="text/css" href="style.css"/> +</head> +<body class="ns-0"> +<!-- start content --> <p><strong>Cobricks-2 Community Bricks and Web Application Server Overview</strong> </p> <table border="0" id="toc"><tr id="toctitle"><td align="center"> @@ -150,11 +122,11 @@ </div> </div> </td></tr></table> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=1" title ="Cobricks2 doc">edit</a>]</div><a name="Overview_and_Basic_Requirements"></a><h2> Overview and Basic Requirements </h2> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=2" title ="Cobricks2 doc">edit</a>]</div><a name="Purpose"></a><h3> Purpose </h3> +<a name="Overview_and_Basic_Requirements"></a><h2> Overview and Basic Requirements </h2> +<a name="Purpose"></a><h3> Purpose </h3> <p>Cobricks-2 is a modular and extensible toolkit for building and operating platforms for (virtual) communities. A platform for virtual communities is a software installation configured and prepared to serve the needs of a particular community, i.e. an instantiation of a generic software product. The toolkit comes with a Web based user interface and a content management functionality and portal container for managing the user interface. In the basic setup the core platform is executed as a Web application in a Web application server. In addition to the Web user interface Cobricks-2 supports a Web Services interface to the functionality and data of the platform. Via this interface it is possible to access the platform from clients and (external) agents, to integrate the platform with other applications, and to connect different Cobricks-2 platforms. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=3" title ="Cobricks2 doc">edit</a>]</div><a name="Communities"></a><h4> Communities </h4> +<a name="Communities"></a><h4> Communities </h4> <p>In general a community is a group of people who share some interest, identify with a common idea or more generally belong to a common context. Thus, a community can be seen as a descriptive identity for a set of people. </p><p>Early sociological work points out, that communities always need a locality and interaction [Hillery 1955]. While the demand for a common physical locality is no longer seen necessary (due to electronic communication and virtual places), the demand for interaction or possibility to interact is still valid. In practical terms this possibility to interact implies the existence of a common communication medium, of common protocols and awareness of the existence and of the membership in the community. </p><p>The interaction in communities is said to serve a goal that is characteristic for communities: collaboration towards common goals or mutual support. A community is not just a set of people who have something in common and who have the possibility to communicate, but of people who are willing to help each other, who are collaborating to the advantage of all. This collaboration is often presented as a will to exchange knowledge â which leads us to communities of practice â but can also be found in collaboration to maintain sport facilities and set up sports events in sport clubs. @@ -169,16 +141,16 @@ To achieve the (spontaneous, unorganized) mutual collaboration, the main activities in communities are communication among members and finding people to communicate with. Communication includes exchange of information (indirect communication) and generating and sharing of knowledge. Hence, community support can be seen as âcommunication and matchmaking supportâ. </p><p>For more information on the characterisation of community and on community support see for example <a href="http://www.communixx.de/" class='external' title="http://www.communixx.de/">http://www.communixx.de/</a> or the additional material at <a href="http://www.cobricks.org/" class='external' title="http://www.cobricks.org/">http://www.cobricks.org/</a> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=4" title ="Cobricks2 doc">edit</a>]</div><a name="Community_Support"></a><h4> Community Support </h4> +<a name="Community_Support"></a><h4> Community Support </h4> <p>Community support systems are software applications with functionality to support the information flow between the community members (providing a communication medium), and to support finding other members (matchmaking support). </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=5" title ="Cobricks2 doc">edit</a>]</div><a name="Community.2C_Community_Support_System.2C_Community_Platform"></a><h5> Community, Community Support System, Community Platform </h5> +<a name="Community.2C_Community_Support_System.2C_Community_Platform"></a><h5> Community, Community Support System, Community Platform </h5> <p>A community is a descriptive identity for a set of people and usually stands for this set of people. Hence, a community is a group of people with a commonality who interact to collaborate in the context of this commonality. An online community is a community whose members mainly interact through electronic communication. </p><p>A community support system is software with functionality to support communities. </p><p>A community platform is a particular instance of a community support system, installed and configured to support a particular community or set of communities. Community platform are usually realized as client server systems with Web browsers as client software. Client computers and client software are usually not considered part of the community platform. An exception from this is, if proprietary client software or hardware is used. </p><p>Hence, Cobricks-2 is a community support system that can be used to set up community platforms for supporting (online) communities. However, you will often find that the term (online) community is used synonymous with the term community platform. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=6" title ="Cobricks2 doc">edit</a>]</div><a name="Basic_Support_Concepts_.E2.80.93_Users_and_Context"></a><h5> Basic Support Concepts â Users and Context </h5> +<a name="Basic_Support_Concepts_.E2.80.93_Users_and_Context"></a><h5> Basic Support Concepts â Users and Context </h5> <p>While providing means for publishing and categorizing information is important for community support, this is not the most characteristic concept. The core of a community support medium is to draw attention to users, by capturing and visualizing electronic user representations, and by capturing and visualizing links between users and between users and content, messages or categorizing concepts. A central issue in community support systems therefore is the user representation and the representation of relations between users and other data concepts on the platform. </p><p>In [Koch 2003]1 we argue that for modular and customizable community support only a very small number of different data concepts are needed on a platform: @@ -191,7 +163,7 @@ </li></ul> <p>The Cobricks-2 platform follows this approach. See Section 1.3.1 for more information. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=7" title ="Cobricks2 doc">edit</a>]</div><a name="Tool_vs._Medium"></a><h5> Tool vs. Medium </h5> +<a name="Tool_vs._Medium"></a><h5> Tool vs. Medium </h5> <p>Current community support solutions mainly encapsulate data structures in (support) tools and provide the user with tool specific user interfaces. These tools and their user interfaces often predefine how the basic support medium can and should be used. </p><p>In contrast to the tool centric approach, Cobricks-2 follows a medium centric approach. The basic support medium (data concepts and channels/processes that distribute the data) is not hidden inside tools but provided in the open. </p><p>This approach has several advantages @@ -199,7 +171,7 @@ <ul><li> it allows us to focus on core concepts/media of community support </li><li> it provides a platform that later can easily be (deeply) integrated with existing tools (like portals, content management systems, identity management solutions, or in the way of contextual collaboration with productivity applications) </li></ul> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=8" title ="Cobricks2 doc">edit</a>]</div><a name="Community_Management"></a><h5> Community Management </h5> +<a name="Community_Management"></a><h5> Community Management </h5> <p>In addition to the medium centric functional focus on users and on relations, community support also has to provide means for community management. </p><p>Communities usually are rather unstructured and unorganized sets of people. Making a community / community platform work involves several prerequisites, the technology for the communication medium only being one. Explicit moderation and different means for supporting intrinsic and extrinsic motivation are needed in addition to the basic functionality. </p><p>Support for community management includes @@ -211,8 +183,8 @@ <p>The Cobricks-2 system provides means for community management already built into the core of the system. </p><p><br /> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=9" title ="Cobricks2 doc">edit</a>]</div><a name="Cobricks-2_Use_Cases"></a><h4> Cobricks-2 Use Cases </h4> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=10" title ="Cobricks2 doc">edit</a>]</div><a name="Use_Cases"></a><h5> Use Cases </h5> +<a name="Cobricks-2_Use_Cases"></a><h4> Cobricks-2 Use Cases </h4> +<a name="Use_Cases"></a><h5> Use Cases </h5> <p>Following the motivation in the previous section, the main purpose of Cobricks-2 is to provide means for supporting direct and indirect communication in communities (of practice) - direct exchange of messages, indirect exchange of information and user representation in the system (for matchmaking) focus on user presentation and relations @@ -220,7 +192,7 @@ </p><p>The functionality is mainly directed towards authenticated users (community members). Other user classes are anonymous users (mainly for browsing in a sub-set of the information), community administrators and platform administrators. Finally, a platform build from Cobricks-2 should also be accessible by user agents or other Cobricks-2 platforms. </p><p><a href="http://131.159.24.138/wiki/mw/index.php/Image:Cobricks2_doc_usecases.jpg" class="image" title="Cobricks-2 Use Cases"><img src="Cobricks2_doc_usecases.jpg" alt="Cobricks-2 Use Cases" /></a> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=11" title ="Cobricks2 doc">edit</a>]</div><a name="Target_Scenarios"></a><h5> Target Scenarios </h5> +<a name="Target_Scenarios"></a><h5> Target Scenarios </h5> <p>Cobricks-2 can be used to build: </p> <ul><li> individual (interactive) web sites for companies or departments @@ -230,8 +202,8 @@ <p>The product can be used out of the box but is mainly targeted to be customized for a special usage scenario. </p><p><br /> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=12" title ="Cobricks2 doc">edit</a>]</div><a name="Requirements"></a><h3> Requirements </h3> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=13" title ="Cobricks2 doc">edit</a>]</div><a name="Functional_Requirements"></a><h4> Functional Requirements </h4> +<a name="Requirements"></a><h3> Requirements </h3> +<a name="Functional_Requirements"></a><h4> Functional Requirements </h4> <p>One source for the functional requirements is the discussion of community support functionality in Section 1.1. This leads to requirements for particular functionality: </p> <ul><li> User Representation and Context / Relationship support: The platform provides basic support for user representation and for handling and presenting relationship of users with other users and content @@ -258,7 +230,7 @@ </li></ul> <ul><li> Connecting platforms: Different Cobricks-2 platforms can be connected for exchanging community content and for reusing user profile information. Especially the integration of external user directories (identity management solutions) should be very strong and support different directories (LDAP, Liberty Alliance, IDRepository). </li></ul> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=14" title ="Cobricks2 doc">edit</a>]</div><a name="Interface_.26_Software_Requirements"></a><h4> Interface & Software Requirements </h4> +<a name="Interface_.26_Software_Requirements"></a><h4> Interface & Software Requirements </h4> <p>In addition to the functional requirements listed above we have defined some additional (non functional) requirements: </p> <ul><li> The platform should be usable out-of-the-box, i.e. after installing and initializing the software (and the databases for persistent storage) the user interface of a default platform should be available. @@ -274,8 +246,8 @@ <p>More details on these interface and software requirements, together with some design constraints and documentation requirements can be found in the documentation of the Development Environment of Cobricks-2 (separate document). </p><p><br /> </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=15" title ="Cobricks2 doc">edit</a>]</div><a name="Toolkit_Overview"></a><h3> Toolkit Overview </h3> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=16" title ="Cobricks2 doc">edit</a>]</div><a name="Data_Concepts"></a><h4> Data Concepts </h4> +<a name="Toolkit_Overview"></a><h3> Toolkit Overview </h3> +<a name="Data_Concepts"></a><h4> Data Concepts </h4> <p>Following the discussion in the section on community support, the Cobricks-2 platform is based on simple but extensible and customizable data concepts providing a community support medium: </p> <ul><li> user @@ -288,15 +260,15 @@ </p><p>Detailed information on the data concepts can be found in the chapters on the components covering each concept. We will just give a brief overview here. </p><p>In general the data concepts are modelled as frames with slots (objects with (object) attributes). Sometimes we also describe the data objects as set of attribute value pairs. The models (classes) for the data objects are described in ontologies, i.e. the attribute names and the possible values for the attributes. Objects are identified via (concept specific) integer identifiers or via global URIs. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=17" title ="Cobricks2 doc">edit</a>]</div><a name="User"></a><h5> User </h5> +<a name="User"></a><h5> User </h5> <p>The concept of a âuserâ describes digital user representations. This is a set of attribute value pairs identified by a (local) identifier, a user login. As with all other data concepts there can be different classes of users which are defined in an ontology. The ontology does not only define the user classes and the relationships among user classes, but also defines which attributes can be set for a user, and what (data) type the values of the attributes have. (As with all other data concepts it is possible to use attributes with names not defined in the model in user objects of any class â however, there is no special support for these additional attributes and they default to string values.) </p><p>Attributes of user objects can define relationships with other users or other data concepts of the platform. An example for this is a buddy list attribute that stores a set of references to other user objects. Relations like this are (at least virtually) modelled as context objects (see next section), but can still be accessed from the user object directly. See the chapter on the Context Component for more information about how this is handled in the platform. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=18" title ="Cobricks2 doc">edit</a>]</div><a name="Context_.28Relation.29"></a><h5> Context (Relation) </h5> +<a name="Context_.28Relation.29"></a><h5> Context (Relation) </h5> <p>The core concepts of community support are users and contexts. Thereby, contexts are relations of users (or other data concepts) to 1) other users, 2) content (items or messages), 3) categorizing concepts (categories), or 4) external resources (identified by URIs). Since context is of major importance for community support, it is modelled as a separate data concept. As with users, contexts are sets of attribute value pairs that are grouped into context classes. The context classes describe the actual type of relationship and define which attributes (and attribute value types) the context will have. </p><p>It is possible to completely separate the management of context from the management of users and other data concepts. However, it is more intuitive to manage some contexts with the concepts they are mainly bound to. Therefore, the context management will not explicitly store all contexts but derive some dynamically from other contents with the help of other components. That is why we speak of virtual context information sometimes. In addition to this it is also possible to derive context information in a really dynamic manner based on rules. See description of the Context Component for more information on this issue. </p> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=19" title ="Cobricks2 doc">edit</a>]</div><a name="Item"></a><h5> Item </h5> +<a name="Item"></a><h5> Item </h5> <p>Items are content objects that are published by users. As users, item entities are basically built from a set of attribute value pairs identified by a local or a global entifier. There are several (hierarchically structured) item classes available, that define what attributes an item should have and what type the attribute values have. An item instance is associated to one of these item classes or item types. </p><p>The core attribute of an item is the âcontentâ. This attribute get special handling and can be of four different types: text, xml, binary, URI. </p><p>Items can have attachments and simple annotations/ratings. Additionally, it is possible to relate items to each other. Item to user relations are usually done using item attributes with value type user â or in the other direction by using user attributes with value type item. @@ -305,7 +277,7 @@ <ul><li> Item classes: announcement, project, publication, web-page </li><li> Item instances: a particular announcement, project, publication, web-page </li></ul> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=20" title ="Cobricks2 doc">edit</a>]</div><a name="Category"></a><h5> Category </h5> +<a name="Category"></a><h5> Category </h5> <p>Categories are focal points to cluster entities of users or items. Hence, the main task of a category is to hold a set of items (item references since items may belong to a set of categories at once) or to be associated to a set of users (users are said to select categories as interests or to be member of a category â there are different classes of membership). </p><p>Since it is a very generic clustering object, there might be several classes of categories. For the beginning categories again are defined as attribute value pairs. In the most simple version there is just a title and an entifier attribute. For more complex versions additional attributes (defining how a category reacts) can be defined. </p><p>Examples: @@ -313,11 +285,11 @@ <ul><li> Category classes: InterestCategories (no members possible), SharedBuddyLists (interestCategories with members and admin roles), PrivateFolders (no members), WebFolder </li><li> Category objects: âcourse.program.informaticsâ, âteaching-staffâ, âkochm-publicationsâ, â/course/info/â </li></ul> -<div class="editsection" style="float:right;margin-left:5px;">[<a href="http://131.159.24.138/wiki/mw/index.php?title=Cobricks2_doc&action=edit&section=21" title ="Cobricks2 doc">edit</a>]</div><a name="Messages"></a><h5> Messages </h5> +<a name="Messages"></a><h5> Messages </h5> <p>Messages are the second type of content objects on the platform. Messages are published (sent) by users with the intention to deliver them to a specified set of other users. This set of recipients can be defined explicitly (by a set of recipient addresses) or implicitly (by a set of attributes the recipients must match). Whil... [truncated message content] |
