Created by Carl Robert Blesius, last modified by Gustaf Neumann 26 Sep 2019, at 08:36 PM
- Accessible and semantic layout/design (first priority)
- Layout for screen reader readability
- Consistent CSS for all packages with inheritance where possible
- Package specific CSS only where absolutely necessary
- Remove as many images as possible
- Totally simplified CSS scheme
- Consistent deprecation
- Support for 4 font sizes without UI breakup
- File path re-factoring so designers can easily skin a local installation and upload zip file with local styles for sharing accross installations
- A theme page that includes as many existing adp chunks and form templates as possible.
- Theme manager that allows a designer to upload a css file and immediately test it against the theme page.
- One style for screen, one for print, and one for mobile
Discussion
0. Why not OpenACS Zen? I think this needs to apply across the toolkit for any package, not just .LRN ones, or there will forever be problems as new applications come out for OpenACS, and are later adopted for .LRN. DaveB, we are going to start with .LRN b/c it contains a limited number of packages and also because there is an accessibility push in the project. A big portion of this will also be defining best practices. CarlB
1. I agree with Carl. I have been working through some of this on our own generic OpenACS installs here but would love to co-ordinate with others. Robert.
2. I also will help out. I have several tools available and will look at what is redundant and post soon. Jon Griffin
3. Please consider expanding the scope of the guidelines to include OpenACS and similar efforts underway at Interface / CSS Coding Guidelines. Accessibility etc. is important for the entire toolkit and long overdue. -Torben
Created by Ryan Gallimore, last modified by Gustaf Neumann 26 Sep 2019, at 08:34 PM
not to be confused with messages
Preliminary Specs for private-messaging package
Send a message or invite any online user from a textbox located at the top of every screen.
- User/Subsite Group selection widget.
- AJAX filter-as-you-type search "Smart Search"
- Confirmation for sending to entire subsite group.
- Message textbox
- Audio alert upon incoming message
"User is now online" messages.
- Incoming messages field with history (dropdown window)
- Send message to new online user via a link in history window
Users can block unwanted users or ignore all messages.
- "Block User" button
- "Unblock User" button
- "Ignore all messages"
- "Accept all messages" (except those from blocked users)
Created by Ryan Gallimore, last modified by Gustaf Neumann 26 Sep 2019, at 08:27 PM
As root:
OPENACS_SERVICE_NAME=service1 # Name your service
export $OPENACS_SERVICE_NAME
groupadd web
useradd -g web $OPENACS_SERVICE_NAME mkdir /var/lib/aolserver
cd /var/lib/aolserver
# Download latest tarball:
>> wget [URL to latest tarball]
>> tar xzvf [tarball.tar.gz]
>> mv [tarball_dir] $OPENACS_SERVICE_NAME
# OR, checkout from CVS. Replace oacs-5-4 with the branch of your choice.
>> cvs -d:pserver:anonymous@cvs.openacs.org/cvsroot checkout -r oacs-5-4 acs-core
>> mv openacs-4 $OPENACS_SERVICE_NAME
chown -R $OPENACS_SERVICE_NAME.web /var/lib/aolserver/$OPENACS_SERVICE_NAME chmod -R 770 /var/lib/aolserver/$OPENACS_SERVICE_NAME
# PostgreSQL 8.x
service postgresql stop yum -y remove postgresql # Download the PG rpm
# Initialize the Cluster
service postgresql initdb
# Start the service
service postgresql start
# Start pg on boot
chkconfig postgresql on
# Change postgresql.conf
# AOLServer
Try the AOLServer 4.5 page. The archive download works well
(but uses sources from 2006).
# Daemontools should now be installed, so let's set it up to start, stop and restart AOLServer
cd /service
ln -s /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/daemontools $OPENACS_SERVICE_NAME
# Daemontools will no scan the etc/daemontools directory and find the run script.
Read this for more information on Daemontools commands
# Modify the etc/daemontools/run script for your ip, user and group. Note the -b IP:PORT flag that # must be added for privileged ports.
# Modify etc/config.tcl to match your hostname and IP. aolserver director should be /usr/local/aolserver
# avoid pid not found errors in the log
chown -R $OPENACS_SERVICE_NAME.web /usr/local/aolserver/log
chmod -R 775 /usr/local/aolserver/log
# Start the server!
svc -u /service/$OPENACS_SERVICE_NAME
# Watch the log for errors:
tail -f /var/lib/aolserver/$OPENACS_SERVICE_NAME/log/error.log
If successful, call up the site URL and install the data model.
# Done!
Created by Adrian Catalan, last modified by Gustaf Neumann 26 Sep 2019, at 08:20 PM
Tools required for the development
The following packages come with the standard Debian installation, so you probably have them already. Still, you should check with `dpkg -s <package>`.
-
make
usually creation of a program takes several steps, so rather than having to type out the same commands over and over again, you can use this program to automate the process, creating `Makefile's.
You'll probably want to install the following packages, too:
Initial debianization
Please note that you should run dh_make only once, and that it won't behave correctly if you run it again in the same, already "debianized", directory.
Make sure you're in the program source directory, and issue this:
dh_make -e your.maintainer@address -f ../openacs-5.1.5.tar.gz
Of course, replace the string "your.maintainer@address" with your e-mail address for inclusion in the changelog entry and other files.
Some information will come up. It will ask you what sort of package you want to create. Gentoo is a single binary package - it creates only one binary, and thus one .deb file - so we will select the first option, with the `s' key, check the information on the screen and confirm by pressing <enter>.
After this execution of dh_make, a copy of the upstream tarball is created as openacs-5.1.5.orig.tar.gz in the parent directory to accommodate the creation of the non-native Debian source package with the diff.gz
Debian release
Let's say that a bug report was filed against your package and it describes a problem that you can solve. To create a new Debian revision of the package, you need to:
- Correct the problem in the package source, of course.
- Add a new revision at the top of the Debian changelog file, for example with `dch -i`, or explicitly with `dch -v <version>-<revision>' and then insert the comments using your preferred editor.
Tip: how to easily get the date in required format? Use `822-date', or `date -R'.
Include a short description of the bug and the solution in the changelog entry.
- Repeat a complete rebuild of the package.
New upstream release
Let's consider a different, slightly more complicated situation - a new upstream version was released, and of course you want it packaged. You need to do the following:
- Download the new sources and put the tarball (e.g. named `openacs.5.2.1.tar.gz') in the directory above the old source tree (e.g. ~/openacs/).
- Enter the old source directory, and run:
uupdate -u openacs.5.2.1.tar.gz
uupdate will properly rename that tarball, try to apply all the changes from your previous .diff.gz file, and update the new debian/changelog file.
- Change directory to `../openacs.5.2.1', the new package source tree, and repeat a complete rebuild of the package
Complete rebuild
Enter the program's main directory and then issue this command:
dpkg-buildpackage -rfakeroot
This will do everything for you. It will:
- clean the source tree (debian/rules clean), using fakeroot
- build the source package (dpkg-source -b)
- build the program (debian/rules build)
- build the binary package (debian/rules binary), using fakeroot
- sign the source .dsc file, using gnupg
- create and sign the upload .changes file, using dpkg-genchanges and gnupg
The only input that will be required of you is your GPG key secret pass phrase, twice.
After all this is done, you will see the following files in the directory above (~/openacs/):
- openacs_5.1.5.orig.tar.gz
This is the original source code tarball, merely renamed to the above so that it adheres to the Debian standard. Note that this was created using the `-f' option to dh_make when we initially ran it.
This is a summary of the contents of the source code. The file is generated from your `control' file, and is used when unpacking the source with dpkg-source. This file is GPG signed, so that people can be sure that it's really yours.
This compressed file contains each and every addition you made to the original source code, in the form known as "unified diff". It is made and used by dpkg-source. Warning: if you don't name the original tarball packagename_version.orig.tar.gz, dpkg-source will fail to generate the .diff.gz file properly!
If someone else wants to re-create your package from scratch, they can easily do so using the above three files. The extraction procedure is trivial: just copy the three files somewhere else and run dpkg-source -x openacs_5.1.5.dsc.
This is your completed binary package. You can use dpkg to install and remove this just like any other package.
- openacs_5.1.5_i386.changes
This file describes all the changes made in the current package revision, and it is used by the Debian FTP archive maintenance programs to install the binary and source packages in it. It is partly generated from the `changelog' file and the .dsc file. This file is GPG signed, so that people can be sure that it's really yours.
Trivial repository construction
Trivial repositories consist of one root directory and of as many subdirectories as you wish. As the users have to specify the path to the root of the repository and the relative path between the root and the directory with the index files in it, you are free to do whatever you want (even to put everything into the root of the repository; then, the relative path will be simply “/”)
We'll create a trivial repository with two subdirectories
(your repository root)
|
|-binary
+-source
Creating Index Files
dpkg-scanpackages generates the Packages file and dpkg-scansources the Sources file.
They both send their output to stdout; thus, to generate compressed files, you can use a command chain like this one: dpkg-scanpackages arguments | gzip -9c > Packages.gz.
The two tools work the same way; they both take two arguments (in reality there are more, but I won't go into that here; you can read the manpages if you want to know more); the first the directory under which the packages are, and the second is the override file. We don't need override files for simple repositories, but as it is a required argument, we simply pass /dev/null.
dpkg-scanpackages scans the .deb packages; dpkg-scansources scans the .dsc files. It is thus necessary to put the .orig.gz, .diff.gz and .dsc files together. The .changes files are not needed.
$ cd my-repository
$ dpkg-scanpackages binary /dev/null | gzip -9c > binary/Packages.gz
$ dpkg-scansources source /dev/null | gzip -9c > source/Sources.gz
From Debian Maintainers' Guide, installer developed by Otto Solares updated by Adrián Catalán at Galileo University as a part of the E-LANE project
Related instructions for installing at:
