Recent Changes

Thursday, March 15

  1. 5:08 am

Wednesday, September 21

  1. page /Lab Portfolio/Portfolio/Atrium Display Mac Setup edited ... The user account has a launcd script in its ~/Library/LaunchAgents folder to keep AtriumDispla…
    ...
    The user account has a launcd script in its ~/Library/LaunchAgents folder to keep AtriumDisplay.app running in the event of crashes.
    The desktop background of the tripplehead monitor is set to crossfade screen shots of the app showing the Intermedia Lab logo and a couple of generic taglines. In the event that the app will not start, this acts as a visual fallback.
    Also the crashreporter is disabled via a terminal command.
    Keeping AtriumDisplay.app running
    Launchd is configured to start and keep AtriumDisplay.app running, in similar fashion as described here: http://hints.macworld.com/article.php?story=20071220095645567
    If the application crashes, Mac OS will simply continue to attempt restarting it.
    AtriumDisplay should not be started by using the 'Start at login' feature from the user account's system preferences or the dock.
    Also the crashreporter is disabled via a terminal command.
    Updating the display machines local mirror of the projects
    The machine runs a copy of BitTorrent Sync that keeps it's local copy of the project repository current.
    (view changes)
    5:27 am
  2. page /Lab Portfolio/Portfolio/Atrium Display Mac Setup edited ... is called atrium-display.local. intermediaAtriumDisplay.local. It has ... user called at…
    ...
    is called atrium-display.local.intermediaAtriumDisplay.local. It has
    ...
    user called atriumdisplayintermedia that runs a set of background tasks and scriptsdaemon to keep
    Hardware
    The Atrium Display runs on a:
    Mac Mini (Late 2009)MacBook Pro
    attached to three HD flat screens using a
    Matrox TrippleHead2Go Digital SE
    ...
    The setup has been formulated with other TrippleHead2Go models. They all failed to work, hardware crashing and configurations missing. The only edition of the Matrox TrippleHead2Go that has worked without failing is the Matrox TrippleHead2Go Digital SE using it's 'automatic configuration based on attached displays' feature.
    Mac Mini configuration
    ...
    account called atriumdisplayintermedia automatically at
    The user account is configured to disable sleeping, power management, screen savers etc.
    The user account has a launcd script in its ~/Library/LaunchAgents folder to keep AtriumDisplay.app running in the event of crashes.
    ...
    If the application crashes, Mac OS will simply continue to attempt restarting it.
    AtriumDisplay should not be started by using the 'Start at login' feature from the user account's system preferences or the dock.
    Also the crashreporter is disabled via a terminal command.
    Updating the display machines local mirror of the projects
    ...
    runs a cron script every 20 minutescopy of BitTorrent Sync that tries to update thekeeps it's local mirrorcopy of the project folder from the intermedia.itu.dk server using rsync. If the script fails, it tries to send a mail to intermedia.itu.dk using the cronic script.
    The public key of the atriumdisplay user is included in the authorized_keys of the sshd at intermedia.itu.dk. This enables the script to use a passwordless ssh-based login for rsyncing.
    repository current.
    Missing: restarting AtriumDisplay.app every night
    The application needs to be restarted to avoid accumulating bugs and leaks. This requires a change to the launchd.plist file (not been implemented yet).
    (view changes)
    5:27 am
  3. page /Lab Portfolio/Portfolio/Atrium Display Application Manual edited ... Here is a screenshot of an example folder: {AtriumDisplay Resouce Files.png} ... current …
    ...
    Here is a screenshot of an example folder:
    {AtriumDisplay Resouce Files.png}
    ...
    current using rsync in a crond script running every ten minutes on the display machine.BitTorrent Sync.
    The original resource folder resides on the intermedia.itu.dk server, andserver also keeps a copy via BitTorrent Sync which is accessible
    Changes to the contents of individual projects are continuously updated and do not require restarting the application.
    However, changes to the list of projects (ie. adding, renaming and removing individual project folders) are not reloaded automatically - as of now the software needs a restart to accommodate new or deleted projects. In fact such changes might trigger a crash. A crash will then trigger a relaunch of the AtriumDisplay.app process by launchd, in effect inadvertently reloading the project list :)
    (view changes)
    5:23 am
  4. page /Lab Portfolio/Portfolio/Portfolio Project Format edited ... Each project has its own sub-folder containing project assets such as images, videos and pdfs …
    ...
    Each project has its own sub-folder containing project assets such as images, videos and pdfs alongside a project.yaml text file containing project metadata.
    Please note that AtriumDisplay.app and the website will show all projects, whose folder name starts with a number and a dot. This follows the publication method of Staceyapp. The convention is to use a date and the project name in the format YYYYMMDD.Project-name as shown in the Resource Folder screenshot above.
    ...
    minutes via cron scripted rsync.BitTorrent Sync.
    Project Metadata
    The project.yaml file in each project folder contains the metadata, that makes the image/video/pdf collection meaningful. The file must be properly formatted YAML to function. The file contains written information about the project, authorship, credits, tags, webiste, license etc.
    ...
    credits:
    Dictionary list
    ...
    the project
    [optional]
    name:
    (view changes)
    5:21 am

Tuesday, June 3

  1. 4:48 am

Friday, March 14

  1. 1:12 am

Friday, December 13

  1. 7:19 am

Friday, December 6

  1. 7:38 am
  2. 7:38 am

More