Showing 1 - 10 of 827 Postings (summary
Created by Maurizio Martignano, last modified by Maurizio Martignano 16 Aug 2016, at 10:39 PM
Windows-OpenACS (vers. 3.1.5 - August 2016) is a Windows 64 port of OpenACS 5.9.0 and the latest snapshot of NaviServer and is available here.
This port installs and runs on the following systems:
- Windows 8.1,
- Windows 10,
- Windows Server 2012 R2, and
- Windows Server 2016 TP.
Created by Ryan Gallimore, last modified by Ryan Gallimore 16 Aug 2016, at 11:37 AM
OpenACS has a proven suite of collaboration tools that are in current use by nonprofits, educational institutions and commercial companies worldwide. Internationalization (I18n) is currently being completed by Heidelberg University. Building on the strength of OpenACS, this project can focus on making the tools work effectively for NGOs rather than tool creation. New features or feature enhancement will be developed when needed, but emphasis will be placed on using existing code and resources.
This project will customize the user interface and information architecture of existing OpenACS functionality to support multi-national grassroots communication. It will also create an easy to install version of OpenACS based on these customizations. Combined with enhanced and specific documentation it will make a very sophisticated multi-lingual community system available and accessible to XXX and other NGOs alike. Finally, the project will also create educational marketing material aimed at multi-national grassroots NGOs to make them aware of this new resource.
On-line collaboration typically uses a variety of tools. A well-constructed application uses them efficiently. The figure below was created for marketing purpose to educational institutions; nonetheless it is a good image for understanding existing and planned OpenACS functionalities.
Modularity is wonderful for quickly assembling exactly the application you need. Maintainability is enhanced in OpenACS when similar modules share the same basic functionality. Thus, from a more technical perspective OpenACS is a layered architecture with many packages that provide diverse functionality to end users; it relies on common underlying structural packages such as the content repository, notifications, date-time space, authentication, and context search. This structured approach allows the easy creation of specialized, yet unified, new functionality with a minimum of separate and new code.
OpenACS traces its roots back to Philip Greenspun, a Computer Science Professor at MIT, and his work on Photo.net starting in 1995 and Philip and Alex’s Guide to Web Publishing in 1998. The code base has always emphasized collaboration and management of geographically diverse online communities. The underlying engineering was supported by millions of dollars of venture capital spent on hiring PhDs in Computer Science from MIT, CalTech and other major universities across the Atlantic.
OpenACS has proven its durability and utility by surviving the death of its parent company (ArsDigita) to grow into a vibrant grassroots collection of independent consultants and small companies implementing diverse and complex web solutions around the globe for fun, philanthropy, and profit.
dotLRN is an application built on top of OpenACS specifically targeted for universities. A consortium lead by the Sloan School of Management at MIT and Heidelberg University has significantly improved enhanced OpenACS. In many ways this project will be philosophically modeled after dotLRN. It will create an application built on top of OpenACS that is specifically targeted to NGOs needing web based community tools in a multi-lingual environment.
This project will also build directly upon functionality implemented by dotLRN. Especially important for this project is the strong emphasis on groups, subgroups and distributed administration. In Learning Management Systems (LMS) it is very important that instructors have extensive control over membership, content and presentation. Designated XXX leaders will reuse this functionality extensively to allow the project to have self-managing geographically diverse and common-interest groups and subgroups that can be managed locally without extensive time commitment from the parent organization.
One goal of this project is to deliver a code base that has significant overlap with dotLRN. This is desirable from a sustainability and maintenance point of view because enhancements and bug fixes made to the dotLRN community will be available to the NGO community as well. OpenACS’ layered package system is designed to support this type of code reuse and make it possible to have specialized code easily segregated from customized code for enhanced maintainability.
Case studies on dotLRN can be found at: http://dotlrn.org/case-studies/
OpenACS is continually being improved, often in ways that will be useful to nonprofits and NGOs. Currently there is active development of the following features.
- E-Commerce G2
Although many of these features will not be immediately used in the XXX site, they will be vital for the future sustainability and expandability of this project, giving the project the ability to be quickly extended to meet the needs of a multitude of NGOs.
The product produced will be a custom installation of OpenACS that any OpenACS company or developer would be able to support. Currently, there are consultants and companies that provide support for OpenACS in the following countries: Australia, Belgium, Brazil, Canada Denmark, Finland, Germany, Guatemala, India, Israel, Italy, Netherlands, Norway, Philippines, Spain, Sweden, Switzerland, UK, US,.
OpenACS has strong and continuing support of standards that will enable this project and future extensions to share content and interoperate with other systems.
The Simple Object Access Protocol (SOAP) web services – a way to create widely distributed, complex applications that run over the Internet, has already been incorporated into some OpenACS packages and research is underway at the University of Sydney into further uses of Web Services.
OpenACS also includes a RSS Support Design Module to support the RDF Site Summary (RSS), an XML-based, lightweight multipurpose extensible metadata description and syndication format. RSS support positions OpenACS for future functionality requiring accepting and distributing syndicated news feeds and other RSS-compliant content.
The OpenACS WAP module supports the wireless access protocol (WAP), thus allowing easy deliver of content to WAP-enabled devices such as cell phones, PDAs, etc., as well as regular desktop browsers. In fact, the simplicity of the OpenACS interface means it is well suited for use on mobile clients.
OpenACS and its dotLRN consortium are committed to implementing the Sharable Content Object Reference Model (SCORM), Instructional Management System (IMS) and Open Knowledge Initiative (OKI) standards, all among the most widely used standards for learning object interoperability.
Created by Rocael Hernández Rizzardini, last modified by Caroline Meeks 16 Aug 2016, at 11:37 AM
.LRN Consortium: Membership Benefits
.LRN is, and aspires to continue to be, a serious platform for major organizations to commit to and build on, not simply a hobbyist project as many other more loosely-governed and managed efforts are. To this end, the health of the project depends on the coordination of its development and promotion. Even the legal existence of the consortium contributes to both of these things, by facilitating contracting and by signaling the seriousness of our enterprise. Members who contribute to funding these common efforts get a voice and a vote in where we go and how we get there. Specifically, members are eligible to serve on our Board of Directors and its various Committees. Members are entitled to private notice and consultation about major matters affecting the project before broader decisions and policies are announced.
Created by OpenACS community, last modified by Torben Brosten 16 Aug 2016, at 11:35 AM
The managing of OpenACS documentation has evolved through a few phases. This is a draft plan for the current phase that we are beginning. Please direct any comments about this plan to the OpenACS Development forum (or in context with the appropriate wiki page ;)
to write superb documentation, so that users, developers and administrators of OpenACS installations can enjoy working with and using the system (with fewer headaches! =)
API Documentation: there are no plans to move the API docs to XoWiki. That ought to remain as is.
DocBook docs at: http://openacs.org/doc/index.html
need significant work done.
Requirements is about setting specifications and milestones we can verify, and includes exploration of scenarios, use cases etc.
Here are documentation requirements for:
volunteers dedicated to regularly managing and updating the documentation
other volunteers who contribute arguably more valuable documentation less frequently (such as magazine articles ;) (and may need some assistance etc. to have their work fit into docs well.)
openacs.org website, including use of xowiki
open-source software, text editors, spell checkers, html code validators etc.
Approaches in docs management explored
Strategy is about creating an approach to doing work. It guides behavior and tactical decisions on the work effort.
Shape ongoing documentation efforts by using principles of continual improvement to re-engineer documentation production and management.
OpenACS documentation development is subject to the constraints of the software project development and release methods and cycles (the section called “Using CVS with OpenACS”). Essentially, all phases of work may be active to accommodate the asynchronous nature of multiple subprojects evolving by the efforts of a global base of participants with culturally diverse time references and scheduling idiosyncrasies.
The documentation strategy is to use project methods to involve others by collaborating or obtaining guidance or feedback (peer review) to distribute the workload and increase the overall value of output for the OpenACS project.
Work Breakdown Structure
Is about explicitly stating the way to implement the strategy as a set of milestones and the methods to use.
Status: this is a draft document, so there is no consensus on a WBS at this time. See en:Documentation_Project_Discussion for current activity.
This is where we measure how well this plan was implemented. Success is measured by A) verifying if the project has met the established goals and requirements, and B) reviewing for ongoing problem areas etc. Observations then help to modify the plan for the next documentation revision.
OpenACS follows verification through different means on different projects, but in all cases, the OpenACS community verifies the project as a success through feedback including bug reports, user and administrator comments, and code changes.
Related links and sources
Created by Benjamin Brink, last modified by Benjamin Brink 16 Aug 2016, at 10:50 AM
For the latest updates to this readme file, see: http://openacs.org/xowiki/q-wiki
The lastest version of the code is available at the development site: http://github.com/tekbasse/q-wiki
Q-Wiki is an OpenACS wiki using a templating system. It allows tcl procedures to be used in a web-based publishing environment. It is not tied to vertical web applications, such as OpenACS ecommerce package.
Q-Wiki is derived from OpenACS' ecommerce package. Administrators have voiced interest in having some kind of strictly filtered ACS developer support dynamics for user content.
Q-Wiki is open source and published under the GNU General Public License v2, consistent with the OpenACS system:http://www.gnu.org/licenses/gpl.html A local copy is available at q-wiki/www/doc/LICENSE.html
Pages automatically have revisioning.
Pages must be trashed before being deleted. Trashed pages can be untrashed.
Trashed pages are not published.
Users with create permission can also trash their own creations.
Tcl procedures pass through two filters: 1. a list of glob expressions stating which procedures are allowed to be used 2. a list of specifically banned procedures
A package parameter can switch the TCL/ADP rendering of content on or off.
This web-app is easily modifiable for custom applications. It consists of a single q-wiki tcl/adp page pair and an extra unused "flags" field.
This app is ready for web-based publishing SEO optimization. Besides content, pages include comments, keywords, and page description fields.
Created by Gustaf Neumann, last modified by Gustaf Neumann 23 Jul 2016, at 09:47 AM
The probably easiest way to upgrade between PostgreSQL versions is as follows (described here from 9.4 to 9.5, based on the directory structure as provided by Mac Ports)
# Dump all databases from pg 9.4
sudo -u postgres $PGBIN/pg_dumpall | gzip -9 > ~/pg-dump-all-$DATE.gz
Then stop pg 9.4, start pg 9.5, then reload the dump:
# Restore all databases and roles from dump into pg 9.5
gunzip < ~/pg-dump-all-$DATE.gz | $PGBIN/psql -U postgres
voilà, start OpenACS, and everything works fine.
In case there is a problem with restoring the dump in PostgreSQL 9.5 due to the "=>" operator of hstore, one has to update the version of hstore at least to 1.1 before dump/restore (the current version of hstore is 1.4; for details see hstore-upgrade ).
Created by Nick Carroll, last modified by Torben Brosten 16 Jul 2016, at 07:43 PM
Package specification Summary for package acs-service-contract
Bug Tracker Summary for package acs-service-contract
Code Metrics Summary for package acs-service-contract
|# Tcl Procs
|# Tcl Lines
|# Automated Tests
|# Stored Procedures
||PG: 0 ORA: 0
|# SQL Lines
||PG: 0 ORA: 0
|# ADP pages
|# ADP lines
|# Include pages (acs-service-contract/lib/)
|# Documentation pages
|# Documentation lines
Created by Gustaf Neumann, last modified by Antonio Pisano 16 Jul 2016, at 07:42 PM
XoWiki is a wiki implementation for
OpenACS implemented based on xotcl-core. Instead of trying to implement the full set of wiki markup commands
in systems like MediaWiki, XoWiki is based on a rich text editor
and focuses more on integration with OpenACS (e.g. categories,
general comments, adp-includes, ad-substitution of template
variables). XoWiki combines aspects of wikis (ease of
page-creation) with aspects of a content management system
(revisions, reusable content, multiple languages, page
XoWiki provides functionalities of enterprise wiki systems (such as combining structured with unstructured information, providing security policies, etc.). XoWiki is reused in several other packages such as XoWiki Content flow, S5 or the Learning Content Tool.
Package specification Summary for package xowiki
||A xotcl-based enterprise wiki system with multiple object types
XoWiki is a Wiki implementation for OpenACS in XOTcl. Instead of
trying to implement the full set of Wiki markup commands of systems
like MediaWiki, XoWiki is based on a rich text editor and focuses more
on integration with OpenACS (e.g categories, general comments,
ADP-includes). XoWiki combines aspects of wikis (ease of
page-creation) with aspects of a content management system (revisions,
re-usable items, multiple languages). Furthermore, XoWiki allows to
define different types of links such one could define book-structures
(where a navigation structure could be built on the fly) or glossaries
with different kind of word relationships (like synonyms,
etc.). XoWiki supports pages in multiple languages and is localized.
- cross language links
- inclusion of ADP pages
- nesting of Wiki-pages
- large set of includeable content (includelets)
- web 2.0 gadgets (digg, delicious, my yahoo)
- audio embedding
- different appearances (template_file)
- prototype pages
- virtual presence
- analysis of collaboration networks
- named/unnamed pages
- various security policies
|This package depends on:
||acs-datetime acs-kernel acs-tcl acs-subsite richtext-xinha categories file-storage general-comments xotcl-core
|Packages that depend on xowiki:
||content-portlet eduwiki learning-content learning-content-portlet pages s5 xolirc xowf xowiki-includelet xowiki-portlet
Bug Tracker Summary for package xowiki
Code Metrics Summary for package xowiki
|# Tcl Procs
|# Tcl Lines
|# Automated Tests
|# Stored Procedures
||PG: 0 ORA: 0
|# SQL Lines
||PG: 0 ORA: 0
|# ADP pages
|# ADP lines
|# Include pages (xowiki/lib/)
|# Documentation pages
|# Documentation lines
Created by Gustaf Neumann, last modified by Monika Andergassen 15 Jul 2016, at 03:55 PM
OpenACS provides theming functionality, i.e. the customization of the site layout through so-called theme packages with customized CSS and HTML layout.
Each subsite in OpenACS can have its own theme.
By default, the "Openacs-Default-Theme" is activated when installing OpenACS. The "Openacs-Default-Theme" package contains a "tabbed" navigation theme and a "plain" navigation theme (without tabs in main navigation).
OpenACS comes now with a new theme package, the "Openacs-Bootstrap3-Theme" Package, which is based on the Twitter Bootstrap Library . This new package is used on the openacs.org site and available form the openacs repository. The package (and the description below) requires at least OpenACS 5.9.0. In the following section you find some hints on how to use and customize this theme and how the theming can be customized in newer versions of OpenACS.
Step-by-Step Installation of a Theme Package
Installing theme packages and switching between themes can be easily done in a few steps:
- Obtain the theme package (e.g. from CVS or github) and install it under the package directory. You can as well "install from the respository", which makes step 2 below unnecessary.
- Go to /acs-admin/install and install the package
- Navigate to the subsite whose theme you would like to change and go to the "Configure"-Page. If you only have the default subsite set up, this is located at /admin/configure. Choose the theme you want. Klick Ok. You should see the new theme now.
Note that a theme package can contain a number of different themes. For instance, the "Openacs-Default-Theme" Package contains a "tabbed" and a "plain" theme; the "Openacs-Bootstrap3-Theme" Package contains a "tabbed" theme in OpenACS style and a "tabbed" theme in turquoise color.
Understanding the Basic Settings of Theme Packages
Where are the themes of a theme package defined?
Open /packages/openacs-bootstrap3-theme/tcl/apm-callback-procs.tcl in your editor. You see that 2 themes are defined here (subsite::new_subsite_theme), with all relevant parameters including css and js files and definition of template files.
You could add another subsite theme here. In order to get it listed on the "Configure"-Page of your subsite, you need to de-install and re-install the Theme Package.
The Theming Parameters allow you to specify, how elements of your page such as forms or lists should be rendered. If the resource which you have defned in your theme is not found, the default is taken from /packages/acs-templating/resources/ as a fallback.
The Theming Parameters
Have a look at the parameter page of your subsite. If you only have the default subsite set up, this is located at /shared/parameters.
In the "Theming"-Section of the subsite parameter page, you find the parameters which you have defined in the apm-callback-procs.tcl file of your theme package. You can modify the parameters here, however it is recommended that you define them in the apm-callback-procs. Why? If you switch the theme or re-install it, the settings of the parameter page are lost!
- Defines layout of the filter options in a dimensional list. You can find an example at the Download Page of the OpenACS Website.
- Defines the layout of form templates
- Defines the layout of list templates
- Defines the general page layout. The master usually sets the framing for the page layout and places elements such as header, navigation, content area, footer.
- The directory, from which the resources of acs-templating are loaded. The resources include the template files for dimensionals, forms, lists, masters, templates, widgets. If not set, or the required resource is not found, the default is taken from /packages/acs-templating/resources/.
If for instance, the ResourceDir is set to /packages/openacs-bootstrap3-theme/resources, and you have a dimensional template defined in "Openacs-Bootstrap3-Theme" Package, you only need to specify the name of the -dimensional_template without giving the entire path.
- Master used for streaming content
- List of CSS files used in the theme
Additional Tools to Layout in a Theme Package
Starting with OpenACS 5.9, so-called widgets can be defined. <widget> is very similar to <include>, but uses widget specific name resolution based on themes. If the theme package contains resources/widgets/$specifiedName it is used from there. Otherwise it behaves exactly like <include> (without the resources/templates/theming).
In the "Openacs-Bootstrap3-Theme" Package, widgets are defined e.g. for the main navigation bar and the login area.
Sometimes, you might want a specific page or include to have a special design or layout which differs from the standard layout defined in that package. For instance, you might want to give the notification widget a new look&feel. You could go to the notification package and edit the correspondend tcl/adp files there. However, when upgrading the package, you always would have to merge your local changes with the upgraded files.
Starting with OpenACS 5.9, you can customize your local templates in your Theme Package. These files "overrule" the tcl/adp files in the corresponding packages. This makes it easier for you to keep the overview of all your layout changes, and also to upgrade your packages with less effort.
How does it work?
Let's take the example from above: you want to change the lokk&feel of the notification widget. The tcl/adp files are situated in /packages/notifications/lib/notification-widget.tcl and /packages/notifications/lib/notification-widget.adp.
Go to the "Openacs-Bootstrap3-Theme" Package. You see a folder resources/templates. Now construct a folder structure in the templates folder, just like this: resources/templates/notifications/lib and create the 2 files notification-widget.tcl/adp. Change the layout as desired.
The "Openacs-Bootstrap3-Theme" Package contains a few such template files by default; feel free to change or complement them.
Understanding the Openacs-Bootstrap3-Theme Package
Different master files
The "Openacs-Bootstrap3-Theme" Package comes with a set of master files, which are shortly explained here.
- The "base master" is the plain-master.tcl/adp. It defines the general page layout.
- The tabbed-master.tcl/adp is the addition for a tabbed navigation, i.e. navigation tabs in the header bar which are defined in the parameter page. Tabs can be defined for admins (AdminNavbarTabsList), for members (MembersViewNavbarTabsList), for users (UserNavbarTabsList). You can check if you want the applications to be shown as tabs in the navigation bar.
- The tabbed-master-turquois.tcl/adp is similar tp the tabbed-master.tcl/adp. The difference is in the logo image defined in the .tcl file. In the OpenACS website, it is currently applied in the subsite for the .LRN project .
- The plain-streaming-head.tcl/adp, tabbed-streaming-head.tcl/adp, and tabbed-streaming-head-turquois.tcl/adp files are the corresponding master files for streaming content.
"Openacs-Bootstrap3-Theme" Package contains a "tabbed" theme in OpenACS style and a "tabbed" theme in turquoise color. The color stylesheets are defined in the apm-callback-procs.tcl file and located at /packages/openacs-bootstrap3-theme/www/resources/css/color/. This makes it very easy to change the color design of the theme. You could either modify one of the color stylesheets "blue.css" or "turquois.css"; or you could add your own color stylesheet and link it in the apm-callback-procs.tcl-file. In the latter case, you should de-activate and re-activate the theme in the "Configure"-Page (see above) to activate the setting.
Much has ben written about this library. However, here are a few links which should help you to make yourself familiar with the Library in case you are new to Bootstrap:
Designing your own Theme
The following guideline helps you to create your own theme. The easiest approach to develop your own theme is to build up on an existing one. For instance, you could modify the "Openacs-Bootstrap3-Theme" Package as a starting point.
- Make a local copy of the "Openacs-Bootstrap3-Theme" Package
- Rename the package.
- Take particular care of the .info file. Rename all the places where you find "openacs-bootstrap3-theme", and give a unique package key.
- Take particular care of the tcl/apm-callback-procs.tcl file. The subsites defined here through subsite::new_subsite_theme need to have a unique key, so give all the subsites you create here a unique key. Also, take care of the namespace.
- Before starting to modify the package, it is best to try to install and de-install the package on a test instance to make sure that you have all the naming right.
- Now feel free to modify the design as you like.
Themes in .LRN
When installing .LRN, the theme-zen is installed and activated by default.
.LRN comes now with a new theme package, the "Dotlrn-Bootstrap3-Theme" Package (as of July 2016, it is in proof-of-concept state!).
The "Dotlrn-Bootstrap3-Theme" Package builds on the "Openacs-Bootstrap3-Theme" Package and depends on both the "Openacs-Bootstrap3-Theme" Package and the "Theme-Zen" Package.
The Theming specifics described above also apply to .LRN theming, but additionally you should consider the following points:
Portal Pages Design
The Design of a Portal Page is defined on 3 levels:
- The subsite theme (which can be chosen on the "Configure"- Page, as described above)
- The page layout: It defines whether the page has, for instance, a 1-column, 2-column or 3-column layout. In the "Dotlrn-Bootstrap3-Theme" Package, the layouts are defined at lib/layouts.
- The portlet theme: It defines the look&feel of the single portlet. In the "Dotlrn-Bootstrap3-Theme" Package, the themes are defined at lib/themes.
Since every portal which is created, stores the portlet theme ID in the database, and since every portal page that is created, stores the page layout ID in the database, changing a theme in .LRN requires an upgrade of the affected database tables. This is done by the tcl/theme-procs.tcl/xql in the "Dotlrn-Bootstrap3-Theme" Package.
!!!!!! Attention: If you switch to the .LRN-bootstrap3-theme, all the portal pages are updated to the bootstrap3 layout !!!!!!
Installing and De-Installing the "Dotlrn-Bootstrap3-Theme" Package
If the "Dotlrn-Bootstrap3-Theme" Package is de-installed, the above described portal pages design falls back to the theme-zen design. This should make sure that the portal pages are always provided with a working layout.
Created by Gustaf Neumann, last modified by Gustaf Neumann 15 Jul 2016, at 06:48 AM
Fixed validity of the following (mostly admin) pages:
/admin/groups/ (elements-by-group-type, elements-by-group-type)
/admin/site-map (folder add, rename)
- double "id":
- developer-support breaks validation (adds "div" immediately after "ul" due to include):
Solved, by adding ability to suppress div wrapper via <include ds=0 src=...>