Weblog

Cookie Consent Widget

Created by Gustaf Neumann, last modified by Gustaf Neumann 22 Dec 2017, at 06:55 PM

Package Specification Summary for Package: cookie-consent

Bug Tracker Summary for Package: cookie-consent

There is no package with the name "cookie-consent" known to bug-tracker.

Code Metrics Summary for Package: cookie-consent

Integration of the Cookie Consent Library into OpenACS

The Cookie Consent Library is and Cookie Consent to be free and open sourced library for for alerting users about the use of cookies on a website.  It is designed to help you comply with the hideous EU Cookie Law and not make you want to kill yourself in the process. So we made it fast, free, and relatively painless.

Details:
    https://cookieconsent.insites.com/
    https://github.com/insites/cookieconsent/

This package integrates the Consent Plugin with OpenACS, in particular with OpenACS subsites.

So far, this package supports on the "inform" type of cookie consent policies. When the "opt-out" or "opt-in" variants of the policies should really include all types of cookies (even session-cookies) the user would not be able to login to the site. However, most countries stick for now to the "inform" policy, and the detailed regulation are still in flux.

Features:

•  Configure the appearance of the cookie consent widget via the following parameter (on acs-subsite):
   

  CookieConsentEnabled	0|1
  CookieConsentPosition	bottom|top|pushdown|left|right
  CookieConsentLayout	block|classic|edgeless|wire
  CookieConsentPalette	oacs|honeybee|mono|neon|corporate
  CookieConsentLearnMoreLink	https://cookiesandyou.com/
  CookieConsentDefaultPalette

   

• Usage from CDN (out-of-the box) or from a local copy (download your local copy via   "Site-Wide Admin" link in /acs-admin/)
• Support for host-node-mapped subsites
• Internationalized with OpenACS message keys

Installation

1.  Install this package via the OpenACS Package Manager
2.  Add this package to the templating system
    
   •  OpenACS 5.10.0d2 or newer:
      The cookie consent widgets uses the "subsite::page_plugin" callback, so no changes on templates are necessary. Make sure, you update also acs-bootstrap-installer to 5.10.0d2 or newer to obtain the updated blank-master
      
   • OpenACS 5.9.1:
     Add to the top of your blank-master.tcl the following snippet:
      ================================================================
     if {[info commands ::cookieconsent::initialize_widget] ne ""} {
           ::cookieconsent::initialize_widget
     }
     ================================================================
3. Configure the CookieConsent* parameters of the subsite (e.g. of the main subsite) in the section "Cookie Consent"

Prerequirements:

The implementation uses nx from the next-scripting framework.

    https://next-scripting.org/xowiki/

which is automatically installed for XOTcl2 via naviserver-openacs

It works best with OpenACS 5.10.0d2 or newer, but works as well with 5.9.1 (see INSTALLATION section above) or earlier versions supporting Content Security Policy (CSP), and probably with  earlier versions as well, when CSP code is commented out.

Richtext CKEditor 5

Created by Gustaf Neumann, last modified by Gustaf Neumann 21 Dec 2017, at 09:28 AM

Package Specification Summary for Package: richtext-ckeditor5

Bug Tracker Summary for Package: richtext-ckeditor5

There is no package with the name "richtext-ckeditor5" known to bug-tracker.

Code Metrics Summary for Package: richtext-ckeditor5

In general, the CKEditor 5 can be used via CDN (zero configuration, default) or via local files. One can use /acs-admin/ (section Site-wide Service Administration to download a version to your local site to reduce latency or to use local modifications.

So far, CKeditor 5 is not released yet, this integration is just minimal, no xowiki formfield support is included yet.

Ajax Helper

Created by Hamilton Chua, last modified by Gustaf Neumann 25 Oct 2017, at 08:32 AM

Package Specification Summary for Package: ajaxhelper

Bug Tracker Summary for Package: ajaxhelper

There is no package with the name "ajaxhelper" known to bug-tracker.

Code Metrics Summary for Package: ajaxhelper

Ajax Helper is a package created to assist OpenACS developers incorporate Ajax into their web applications. It is composed of helper procs that wrap javascript functions that perform DHTML effects and Ajax. 

Ajax Helper incorporates javascript from Thomas Fuch's Scriptaculous Javascript Library (http://script.aculo.us) and Yahoo's User Interface Library or YUI ( http://developer.yahoo.com/yui/ ).

Tutorials on how to use Ajax Helper :

Introduction to Ajax Helper with Simple Effects
http://web.archive.org/web/20111221205659/http://www.solutiongrove.com/blogger//one-entry?entry%5fid=266153

Using Ajax
http://web.archive.org/web/20060715115103/http://www.solutiongrove.com:80/blogger/one-entry?entry%5fid=268010

Simple Drag and Drop
http://web.archive.org/web/20060715115051/http://www.solutiongrove.com:80/blogger/one-entry?entry%5fid=266155

Current Release on CVS HEAD : AjaxHelper 0.87d
includes Scriptaculous v.1.7.3 Beta, YUI v. 2.3.0 and ExtJs 1.1.1
 

Quota

Created by Gustaf Neumann, last modified by Benjamin Brink 07 Jul 2017, at 07:34 AM

Package Specification Summary for Package: quota

Bug Tracker Summary for Package: quota

There is no package with the name "quota" known to bug-tracker.

Code Metrics Summary for Package: quota

Quota 

Package to control the expense of space in users' disc and communities.

The module quota allows to control the space used by users and communities in the module filestorage, this is controlled by the manager of the system and for it it he can modify the global parameters and to establish particular values of these parameters for communities and even users.

The available parameters are:

MaxQuotaByCommunity - > maximum Quota for community (in KB)

MaxQuotaByUser - > maximum Quota for user (in KB)

MaxQuotaByUserFolder - > maximum Quota of the personal directoryof the user (in KB)

MaxQuotaByUserComm - > maximum Quota for user in a community (in KB)

MaxFilesByCommunity - > N º maximum of files for community

MaxFilesByUser - > N º maximum of files for user

MaxFilesByUserFolder - > N º maximum of files for personal directory

MaxFilesByUserComm - > N º maximum of files for user in a community

Wikipedia

Created by Gustaf Neumann, last modified by Benjamin Brink 07 Jul 2017, at 07:32 AM

Package Specification Summary for Package: wikipedia

Bug Tracker Summary for Package: wikipedia

There is no package with the name "wikipedia" known to bug-tracker.

Code Metrics Summary for Package: wikipedia

Integration of the encyclopedia Wikipedia in dotLRN. 

Accomplishment of a module integrated to the platform dotLRN, that allows to realize searches in the encyclopedia wikipedia, without need to go out of the platform.

The consultations turn out to be integrated to the course or community and can be realized in different languages.

xolirc

Created by Gustaf Neumann, last modified by Gustaf Neumann 20 Jun 2017, at 10:18 AM

Package developed by Victor Guerra to collect IRC data in wiki pages, running on OpenACS.org

Dynamic Object Type

Created by Lee Denison, last modified by Gustaf Neumann 15 Jun 2017, at 02:58 PM

Package Specification Summary for Package: dynamic-types

Bug Tracker Summary for Package: dynamic-types

There is no package with the name "dynamic-types" known to bug-tracker.

Code Metrics Summary for Package: dynamic-types

cvs head version of project-manager requires dynamic-types

What does dynamic-types do?
Dynamic types allows you to create new OpenACS Object Types and add attributes to them through a Tcl API.

When should I use dynamic-types?
Dynamic types supports several use cases:

• Container Applications - meta-applications which define the necessary data model and code to perform a useful function but the extended data is decided by the administrator.
• Extending existing packages with dynamic data. As an example project manager has dynamic types support which allow third packages to add attributes to projects and tasks which can be edited using the standard interface for project manager.

Creating a Dynamic Type (Declaration)
There are three main ways to create dynamic types:

• As a user, through an application user interface.
• As a system administrator, through install.xml actions.
• As a programmer, through the Tcl API.

notes:

a 2005 implementation example

Running Applications built on dynamic-types

The project manager package (latest version in HEAD) relies on dynamic types to allow custom applications and other packages (like invoices, logger) to extend the basic attributes of a project and a task. This is in use by three clients of cognovís.

Solution Grove has been exploring helping clients build dynamic data models with dynamic types.

Two examples we have are about bulk data collection, aggregation, and analysis. In both cases, data is uploaded to the system, where a web user interface is providing for viewing and aggregating the data.

In the first case, there is an administrative user interface to define a new type, and arbitrarily many types can be created. Each new type of data collection gets a different table/dynamic type in the database. Here we are mainly using the dynamic type system to programatically build new tables for collection. We also use the dynamic type definitions to build the user interface to explore the data after it has been uploaded. Storing all the data in a specific table, instead of generic storage, makes the reporting and dynamic analysis of the data much easier to code for. Doing sum, average, etc calculations on the data is greatly simplified. In this case we are collection many different types of data, and doing unique analysis on each type, so the ability to create the types, and build a user interface to it, on the fly is very helpful. The data collection is done through transfer of XML files with an external application. Using the dynamic-type attribute info we are able to map the XML structure to the various dynamic data collection types.

For another client, we are using dynamic types to give the site administrators more flexibility in developing their application. The client wants to allow users to upload specialized data files, but then to organize these files in ways that make sense to the client and their users. So, we developed 4 dynamic-type objects (institution, ward, glucose_file and glucose). An institution can have multiple wards, which can have multiple glucose_files which can have multiple glucoses. The attributes of each object is set by the site-administrator, and the plan is to adjust them over time as the site's needs change. Because everything is done with the Web UI, the administrator can make changes as they need to. The add-edit pages respond automatically to any changes in the attributes - there's no need to recode them when you add an attribute to an object.

A third application we have developed is a generic resource database, where a form can be generated to collect information such as a list of businesses, or other resources. The dynamic UI here can be integrated with categories to build a dynamic form for data entry. We also built a dynamic UI to view lists and individual entries.

Xarg Examples 

Xarg have developed two 'products' which are installed for multiple clients. In each case we used dynamic types to handle sections of data which are expected to be different for each client installation. Dynamic types allowed the system to handle the different data sets without needing to modify the code for each client.

dotCommunity: In our dotCommunity product users are able to create community websites by filling in an application form.  The system supports multiple community 'types'.  Dynamic types allows each clients to collect and display different data for each community type on a per installation basis.

dotConsult: This is our e-consultation product which uses dynamic types to store a flexible set of demographics information for the users taking part in the consultation.

Future Directions

The current APIs of dynamic-types are under revision, a much more consistent, and less abstract API is under development. It does not appear an upgrade from the older API will be easy to write.  In the long run support for "lists" as AMS has them would be a nice feature in addition to the option to store the additional types and attributes in a meta database (as AMS does) or in the primary tables (as dynamic types does currently). Dynfield (an application from Project Open) supposedly does exactly that, but for reasons unknown to me (MS) it has never made it into proper OpenACS and therefore any of it's packages.

Difference to AMS

The AMS package allows you to extend any object_type with additional attributes. These attributes are stored in a meta table, allowing you to quickly change the makeup of you objects without the need to change anything in the database. Additionally, through the support of "lists" for object_types, you can compose the entry forms for objects in multiple different ways, thereby allowing many different views on the same object_type.

Anonymous Evaluation

Created by Gustaf Neumann, last modified by Gustaf Neumann 14 Apr 2017, at 10:16 AM

Package Specification Summary for Package: anon-eval

Bug Tracker Summary for Package: anon-eval

There is no package with the name "anon-eval" known to bug-tracker.

Code Metrics Summary for Package: anon-eval

XO Learning Performance

Created by Gustaf Neumann, last modified by Gustaf Neumann 10 Apr 2017, at 09:39 AM

Package Specification Summary for Package: xolp

Bug Tracker Summary for Package: xolp

There is no package with the name "xolp" known to bug-tracker.

Code Metrics Summary for Package: xolp

Chat Includelet

Created by Gustaf Neumann, last modified by Gustaf Neumann 29 Nov 2016, at 08:20 AM

Package Specification Summary for Package: chat-includelet

Bug Tracker Summary for Package: chat-includelet

There is no package with the name "chat-includelet" known to bug-tracker.

Code Metrics Summary for Package: chat-includelet