Cone3D Programming - SDL, OpenGL and C++ Tutorials

http://72.14.253.104/search?q=cache:Pxi5imWF9Yo...

clipped by pingpong Dec 02, 2006

ode Pile - OGL Screenshotta

You may use this piece of code freely for any purpose (commercial/non), as long as you leave the original comments. You can download shotta.cpp here or copy/paste the following code block.

typedef unsigned char uchar;

//////////////////////////////////////////////////
// Grab the OpenGL screen and save it as a .tga //
// Copyright (C) Marius Andra 2001              //
// http://cone3d.gz.ee  EMAIL: cone3d@hot.ee    //
//////////////////////////////////////////////////
int screenShot()
{
  // we will store the image data here
  uchar *pixels;
  // the thingy we use to write files
  FILE * shot;
  // we get the width/height of the screen into this array
  int screenStats[4];

  // get the width/height of the window
  glGetIntegerv(GL_VIEWPORT, screenStats);

  // generate an array large enough to hold the pixel data 
  // (width*height*bytesPerPixel)
  pixels = new unsigned char[screenStats[2]*screenStats[3]*3];
  // read in the pixel data, TGA's pixels are BGR aligned
  glReadPixels(0, 0, screenStats[2], screenStats[3], GL_BGR, 
                                   GL_UNSIGNED_BYTE, pixels);

  // open the file for writing. If unsucessful, return 1
  if((shot=fopen("shot.tga", "wb"))==NULL) return 1;

  // this is the tga header it must be in the beginning of 
  // every (uncompressed) .tga
  uchar TGAheader[12]={0,0,2,0,0,0,0,0,0,0,0,0};
  // the header that is used to get the dimensions of the .tga
  // header[1]*256+header[0] - width
  // header[3]*256+header[2] - height
  // header[4] - bits per pixel
  // header[5] - ?
  uchar header[6]={((int)(screenStats[2]%256)),
                   ((int)(screenStats[2]/256)),
                   ((int)(screenStats[3]%256)),
                   ((int)(screenStats[3]/256)),24,0};

  // write out the TGA header
  fwrite(TGAheader, sizeof(uchar), 12, shot);
  // write out the header
  fwrite(header, sizeof(uchar), 6, shot);
  // write the pixels
  fwrite(pixels, sizeof(uchar), 
                 screenStats[2]*screenStats[3]*3, shot);

  // close the file
  fclose(shot);
  // free the memory
  delete [] pixels;

  // return success
  return 0;
}

Quicktime export as RGB instead of ARGB

http://www.archivesat.com/QuickTime_Development...

clipped by pingpong Nov 22, 2006

c++ of quicktime

Show Clip

Email lists > QuickTime Development

List Info

Thread: Quicktime export as RGB instead of ARGB

Search this list only Search all lists
Quicktime export as RGB instead of ARGB
	2006-11-02 23:58:57
Steve, >>>>> When writing out a Quicktime file, how do we create the >>>>> Quicktime file as an RGB-only file? All of our quicktimes >>>>> currently end up being exported as RGBA (depth = 32). >>>> >>>> Besides setting the 'depth' to 32, you should also set the >>>> 'cmpCount' to 3. >>> >>> Where do I need to set that? ... >>> >>> i.e. the rough sequence of calls is: >>> ... >>> QTNewGWorld(&lWorld, k32ARGBPixelFormat, ...) >> >> PixMapHandle lPixelMap = GetGWorldPixMap(lWorld); >> (**lPixelMap).cmpCount = 3; > > Are you saying that you can just change cmpCount on the PixMap of a > 32-bit GWorld (and I'd assume rowBytes) and DecompressImage will > still work? On a Mac? QuickTime on the Mac does not properly handle 24-bit pixels, although frrom the tests I've done, it looks like it'd be trivial for the QuickTime team to get it to work. Instead, on the Mac, QuickTime allocates 32 bits (= 4 bytes) per pixel whether it's ARGB or just _RGB. So definitely don't adjust 'rowBytes' on the Mac. On the Mac, setting 'cmpCount' to 3 is a signal to QuickTime that the alpha channel is not preserved; setting 'cmpCount' to 4 is a signal that the alpha channel is preserved. > On a related note, is it (relativly) safe to swap out the > PixMapBaseAddr on a GWorldPixmap from under a DecompressSequence? > Given the deprecated state of the GWorld APIs, I would expect > anything that currently works to continue working. In general, no, since the address may be controlled by hardware using a cache, or may be purgeable. The PixMapBaseAddr is no longer supposed to be accessed directly; instead we're supposed to use the 'GetPixBaseAddr()' function, for which there is no corresponding 'SetPixBaseAddr()'. If your application creates the GWorld, then you can prevent it from being cached with the 'keepLocal' flag. I believe that if you change it, you should call 'UpdateGWorld()'. I would recommend testing this. > In this context, I'm returning (32-bit) RGB from a video digitizer > using the compressed source API after some processing and could > save a copy of all of the data if I could decompress directly into > the output buffers. > > (I might try calling QTNewGWorldFromPtr for each frame if the > overhead is low enough) Sounds like a good idea. Andreas Wittenstein BitJazz Inc. http://www.bitjazz.com/sheervideo/ _______________________________________________ Do not post admin requests to the list. They will be ignored. QuickTime-API mailing list (QuickTime-APIlists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quicktime-api/bond%40yahoo.com This email sent to bondyahoo.com

[1]

about | contact Other archives ( Real Estate discussion Medical topics )

Mailing lists

Newsgroups

RFC archive

Subversion Instructions - iFolder

http://www.ifolder.com/index.php/Subversion_Ins...

clipped by pingpong Nov 21, 2006

subversion trac

Show Clip

Subversion Instructions

From iFolder

iFolder and Simias are now contained in their own SVN repositories. Please take care when adding new projects to add them in the appropriate repository.

Table of contents [ hide ]

1 Browse SVN Online

2 Available Versions

3 Anonymous Subversion Access

4 Developer Subversion Access

5 Subversion on Windows with TortoiseSVN

6 Subversion on OS X

[edit]

Browse SVN Online

iFolder SVN (https://forgesvn1.novell.com/viewsvn/ifolder)

Simias SVN (https://forgesvn1.novell.com/viewsvn/simias)

[edit]

Available Versions

Version	Url	Comment(s)
simias 3.4	https://forgesvn1.novell.com/svn/simias/branches/ifolder_3_4	works with the Open Source Server
ifolder 3.4	https://forgesvn1.novell.com/svn/ifolder/branches/ifolder_3_4	works with the Open Source Server
simias 3.6	https://forgesvn1.novell.com/svn/simias/trunk/	current development version
ifolder 3.6	https://forgesvn1.novell.com/svn/ifolder/trunk/	current development version

[edit]

Anonymous Subversion Access

To view the contents of the iFolder and Simias subversion repositories you can use the ls command.

svn ls https://forgesvn1.novell.com/svn/ifolder/
svn ls https://forgesvn1.novell.com/svn/simias/

If you have not been given commit access to the projects, you can still check-out all of the files in the Subversion repositories for these projects through anonymous access. This can be done with the following commands:

svn checkout https://forgesvn1.novell.com/svn/ifolder/trunk
svn checkout https://forgesvn1.novell.com/svn/simias/trunk

The user name and password are both anonymous.

The subverson repository has moved. You can now access the subversion server using the https protocol instead of ssh. The repositories now reside on a new server as well. You can check out your code from this server (forgesvn2.novell.com), or you will need to run the following command (or somthing similar to it, based on what you have checked out) to align your local repository to the new location.

svn switch --relocate svn+ssh://your-user-name@forgesvn1.novell.com/svn/simias/trunk/ https://forgesvn2.novell.com/svn/simias/trunk

[edit]

Developer Subversion Access

If you have been given commit access to the ifolder or simias repositories, you may use all of the functionality provided by Subversion. For the full documentation on Subversion, you can visit their website at http://subversion.tigris.org.

The most common things you will be doing with Subversion are importing your project, checking it out, updating your local copy with the repository and checking in changes.

If your project's files are not yet in Subversion, you must start by importing your files into the repository. To do this, you should change to the topmost directory of your project's files and enter something like the following:

svn import local_dir svn+ssh://your-user-name@forgesvn1.novell.com/svn/ifolder/trunk/repo_dir

In the above command, we are telling Subversion to recursively copy everything in the local_dir directory into repo_dir directory in your repository. If repo_dir does not exist it will be created.

Once the project has been imported, you can do the check-out, update and check-in operations anytime you deem it appropriate.

Now you can get your own private copy of all the project files in Subversion by giving the checkout command. You can do this with the following command:

svn co svn+ssh://your-user-name@forgesvn1.novell.com/svn/ifolder/trunk/repo_dir

repo_dir would be replaced with any valid directory in the repository.

The Subversion update command is used for downloading all changes that have been made to files in the Subversion repository to your local copy. If another developer has changed a file that you have also changed in your local copy, the changes will be merged together. Sometimes a merge is required but cannot be completed. This condition produces a conflict. If there are any conflicts during the update process, they will appear in the output of the command. Under almost all conditions, an update operation must be performed before a check-in operation. If you check-in before doing an update, you run the risk of overwriting someone else's changes! To perform a Subversion update, you should change to the root directory of your local copy of the project files and issue the following command:

svn update

At some point in time, you will want to commit the changes that you have made to your local copy of the project files. This is a multi-phased process that should be as follows:

Execute a Subversion update operation (described above).
Fix any problems that may have surfaced from the update, such as failed merges(conflicts), etc...
Execute the actual Subversion commit operation

When you are ready to commit your changes to the repository , change to any directory in your local copy of the project files and issue the following command:

svn commit --message "My list of changes"

This will commit all changes in the current directory and any of it's sub-directories to the remote repository.

Again, Subversion has much more functionality than what is described here. We encorage you to read the documentation on their site, http://subversion.tigris.org/.

[edit]

Subversion on Windows with TortoiseSVN

TortoiseSVN gives you the ability to perform Subversion functions directly from Windows Explorer. You can check out, update, commit, see diffs and so forth by right clicking on the file or folder. You can download TortoiseSVN from their website as http://tortoisesvn.tigris.org/. It is easy to install and use, and it works very well.

[edit]

Subversion on OS X

You can download OS X packages for subversion from Metissian (http://metissian.com/projects/macosx/subversion). If you want a gui subversion client, svnX (http://www.lachoseinteractive.net/en/community/subversion/svnx/features) by la chose interactive is really nice.

Retrieved from "http://www.ifolder.com/index.php/Subversion_Instructions"

Views

Personal tools

Create an account or log in

Navigation

Search

Toolbox

Natmaster.com - Installing Trac

http://natmaster.com/articles/installing_trac.php

clipped by pingpong Nov 19, 2006

of trac

Show Clip

July 22, 2006

Introduction

Assumptions

This guide was made primarily to help DreamHost customers setup Trac. However, the setup is generic enough, that with only little modification, this guide can be applied to any shared-hosting setup running the Apache webserver. To work, you will need access to shell, and have basic understanding of text editing in shell. Dreamhost provides python2.3, and easy subversion setup - so these are assumed to already be in place.

Also, because I do not like the login hack described on the DreamHost Trac Wiki, I have assumed that you will install one of the login plugins. However, if you have access to the Apache setup file and do not wish to use a login manager, you can use the account setup method outlined in the Trac wiki.

Python

I found installing a local copy of python to be unnecessary, as the extra modules can be installed in the trac's lib path. To assure access to these libs, the PYTHONPATH environment variable must reference the aforementioned path.

Environmental Variables

Add this to ~/.bash_profile:
export PYTHONPATH="$HOME/packages/lib/python2.3/site-packages" export LD_LIBRARY_PATH="$HOME/packages/lib" export PATH="$HOME/packages/bin:$PATH"
source ~/.bash_profile

Installation

Setup

I recommend making a special directory for the install files and packages; this makes it easier to manage, and you can delete the entire directory of install files at the end. I used ~/packages and ~/install_files personally, and will be using them throughout these instructions - so if you want to use another directory, just replace all references.

cd
mkdir install_files
mkdir packages
mkdir trac_sites

Install Trac (0.9.6)

cd ~/install_files
wget http://ftp.edgewall.com/pub/trac/trac-0.9.6.tar.gz
tar zxf trac-0.9.6.tar.gz
cd trac-0.9.6
python setup.py install --prefix=$HOME/packages

Install Clearsilver (0.10.3)

cd ~/install_files
wget http://www.clearsilver.net/downloads/clearsilver-0.10.3.tar.gz
tar zxf clearsilver-0.10.3.tar.gz
cd clearsilver-0.10.3
sed -i "s@/usr/local/bin/python@/usr/bin/env python@g" \ scripts/document.py PYTHON_SITE=`/home/{username}/packages/bin/python -c \ "import sys; print [path for path in sys.path if \ path.find('site-packages') != -1][0]"` \ ./configure --with-python=/home/{username}/packages/bin/python \ --prefix=$HOME/packages \ --disable-ruby --disable-java --disable-apache --disable-csharp --disable-perl
make
make install

Install SQLite (3.3.6)

cd ~/install_files
wget http://www.sqlite.org/sqlite-3.3.6.tar.gz
tar zxf sqlite-3.3.6.tar.gz
cd sqlite-3.3.6
./configure --prefix=$HOME/packages
make
make install
ln -s $HOME/packages/bin/sqlite3 $HOME/packages/bin/sqlite

Install PySQLite (2.3.2)

cd ~/install_files
wget http://initd.org/pub/software/pysqlite/releases/2.3/2.3.2/pysqlite-2.3.2.tar.gz
tar zxf pysqlite-2.3.2.tar.gz
cd pysqlite-2.3.2
In setup.py, change
include_dirs = [] to include_dirs = ['$HOME/packages/include']
and
library_dirs = [] to library_dirs = ['$HOME/packages/lib']
python setup.py build
python setup.py install --prefix=$HOME/packages

Install SWIG (1.3.29)

cd ~/install_files
Get http://easynews.dl.sourceforge.net/sourceforge/swig/swig-1.3.29.tar.gz into your home directory.
tar zxf swig-1.3.29.tar.gz
cd swig-1.3.29
./configure --prefix=$HOME/packages --with-python=/usr/bin/python
make
make install

Install Subversion (1.3.2)

cd ~/install_files
wget http://subversion.tigris.org/downloads/subversion-1.3.2.tar.gz
tar zxf subversion-1.3.2.tar.gz
cd subversion-1.3.2
./configure PYTHON=/usr/bin/python --prefix=$HOME/packages \ --with-swig=$HOME/packages/bin/swig --without-berkeley-db \ --with-ssl --with-zlib
make
make install
make swig-py
make install-swig-py
cd ~/packages/lib/python2.3/site-packages
echo $HOME/packages/lib/svn-python > subversion.pth
ln -s ~/packages/lib/svn-python/libsvn
ln -s ~/packages/lib/svn-python/svn
Test it with python -c "from svn import client" (No errors should result.)

Setup Trac Environment

trac-admin $HOME/trac_sites/{your trac project id} initenv
("{your trac project id}" can be anything you like. Putting all your Trac environments in your trac_sites directory allows for simpler backup!)

You will be asked for
- Project Name: {Whatever you want}
- Database connection string: {Accept the default (just hit return)}
- Path to repository: /home/{yourusername}/svn/{your svn project id}
- Templates directory: {Accept the default (just hit return)}
trac-admin $HOME/trac_sites/{your trac project id} will put you into interactive mode. You can issue a simple help at the prompt to see what you can do. There are lots of administrative actions in interactive mode that can make your life a little easier than it would be if you always had to go through the WebAdmin interface.

You should add at least one user with admin powers. To do this, in interactive mode:
- permission add admins TRAC_ADMIN
- permission add {username} admins
- exit (to quit interactive mode)
During interactive mode, permission list should show the new users on the list.

Make Trac Web Accessible

cd ~/{my.domain.name}
Make index.cgi (make sure to set the permissions so the webserver can read it - 775):
#!/bin/bash export HOME="/home/{username}" export TRAC_ENV="$HOME/trac_sites/{your trac project id}" export PYTHONPATH="$HOME/packages/lib/python2.3/site-packages" export PATH="$HOME/packages/bin:$PATH" export LD_LIBRARY_PATH="$HOME/packages/lib" exec $HOME/packages/share/trac/cgi-bin/trac.cgi
and index.fcgi (make sure to set the permissions so the webserver can read it - 775):
#!/bin/bash export HOME="/home/{username}" export TRAC_ENV="$HOME/trac_sites/{your trac project id}" export PYTHONPATH="$HOME/packages/lib/python2.3/site-packages" export PATH="$HOME/packages/bin:$PATH" export LD_LIBRARY_PATH="$HOME/packages/lib" exec $HOME/packages/share/trac/cgi-bin/trac.fcgi
Then set the default by editing .htaccess:
DirectoryIndex index.cgi You can change this to index.fcgi once you have everything setup. (Fcgi is faster, but you won't notice changes until a day later.)

Prettiness

Pretty URLs

Setup static mapping

This allows the common static files (images, CSS, javascript, etc) to be accessed directly, rather than mapping through the cgi script. (This makes Trac faster, while providing compatibility with the prettiness.)

cd ~/{domain name}
mkdir chrome
ln -s $HOME/packages/share/trac/htdocs ./chrome/common

Setup Rewrite Rule

Edit .htaccess located in the {domain name} directory DirectoryIndex index.cgi Options ExecCGI FollowSymLinks <IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /index.cgi/$1 [L] </IfModule> This will prefix any failed request with index.cgi (to run it through Trac).

Hack the Trac base_url

This sets any links Trac generates to start from the base, rather than the file that processed the generation. (/whatever, instead of index.cgi/whatever)

cd $HOME/packages/lib/python2.3/site-packages/trac/web
Backup the original cgi_frontend.py in case you want to revert. cp cgi_frontend.py cgi_frontend.py.backup
Edit cgi_frontend.py, change
self.cgi_location = self.__environ.get('SCRIPT_NAME')
to
self.cgi_location = os.path.dirname(self.__environ.get('SCRIPT_NAME'))

Plugins

Setup Tools

We'll be using this to install the other plugins; so it is necessary to install this to follow my steps.

cd ~/install_files
wget http://peak.telecommunity.com/dist/ez_setup.py
python ez_setup.py --prefix=$HOME/packages

WebAdmin Plugin

cd ~/install_files
wget http://trac.edgewall.org/attachment/wiki/WebAdmin/TracWebAdmin-0.1.1dev_r2765-py2.3.egg.zip?format=raw
easy_install --prefix=$HOME/packages TracWebAdmin*
Now tell trac to load the plugin by editing $HOME/trac_sites/{your trac project id}/conf/trac.ini and adding to the components section: [components] webadmin.* = enabled

AccountManager Plugin

NOT COMPATIBLE WITH DbAuth

This will make the htpasswd login method much more pleasing. New users can register on their own using the site, and they can change their passwords if necessary. This also allows login via form, rather than the HTTP authentication.

cd ~/install_files
svn co http://trac-hacks.org/svn/accountmanagerplugin/0.9
mv 0.9 accountmanagerplugin
cd accountmanagerplugin
python setup.py bdist_egg
cd dist
easy_install --prefix=$HOME/packages *.egg
You must add an initial user, to create the initial trac.htpasswd file:
htpasswd -c ~/trac_sites/trac.htpasswd {username}
You'll then enter the password twice.
Now tell trac to load the plugin by editing $HOME/trac_sites/{your trac project id}/conf/trac.ini and adding to the components section: [components] trac.web.auth.LoginModule = disabled acct_mgr.* = enabled [account-manager] password_format = htpasswd password_file = /home/{your username}/trac_sites/trac.htpasswd

DbAuth Plugin

NOT COMPATIBLE WITH AccountManager

Makes more sense than the normal login method. However it does not support new user registration like AccountManager, rather, you are required to enter all users in manually using sqlite. Because of this, I use AccountManager instead.

cd ~/install_files
svn co http://www.trac-hacks.org/browser/dbauthplugin
cd ./dbauthplugin/0.9
python setup.py bdist_egg
cd dist
easy_install --prefix=$HOME/packages *.egg
cd ../install
cp dbauth.db ~/trac_sites
chmod 775 ~/trac_sites/dbauth.db
Now you need to add some users; you'll have to do this manually. You'll probably want to add the same username(s) as you setup earlier.
- sqlite ~/trac_sites/dbauth.db
- INSERT INTO trac_users VALUES ('all', 'username', 'passwd', 'email@email.com'); INSERT INTO trac_permissions VALUES ('all', 'username', 'admins');
- .quit
Now tell trac to load the plugin by editing $HOME/trac_sites/{your trac project id}/conf/trac.ini and adding to the components section: [components] trac.web.auth.* = disabled dbauth.* = enabled #trac.userdir.* = enabled # only if you want to use this [central] database = /home/{your username}/trac_sites/dbauth.db envroot = /home/{your username}/trac_sites/{your trac project id}

Cleanup

Now that you have everything setup the way you want, you can go ahead and delete all those setup files, and switch to fast_cgi

Delete setup files

Since you won't be using those setup files after you're done, if you don't want all those setup files to take up hard drive space, you can delete them.

cd
rm -rf install_files

Switch to fcgi

If you are using 'Pretty URLs'

Change .htaccess to direct to index.fcgi, rather than index.cgi: DirectoryIndex index.fcgi Options ExecCGI FollowSymLinks <IfModule mod_rewrite.c> RewriteEngine On RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /index.fcgi/$1 [L] </IfModule>

Otherwise

Just change the .htaccess DirectoryIndex to index.fcgi DirectoryIndex index.fcgi

References

Official Trac Site
Trac Installation Guide
Trac Plugins Guide - guide to plugins in Trac
Trac Hacks - various plugins and the like to customize Trac
Dreamhost Trac wiki

Page generated in 0.0091 seconds.

Johan Viberg : Installing Trac on DreamHost

http://johan.org/articles/2006/08/16/installing...

clipped by pingpong Nov 19, 2006

of trac

Show Clip

Installing Trac on DreamHost

Posted by Johan on 08/17/2006

One of the things I really liked at TextDrive was the built-in support for Trac. Alas, DreamHost does not have Trac support by default. After reviewing the Trac section of the DreamHost wiki, I found an awesome tutorial by Nathaniel Tucker on installing Trac from scratch on DreamHost.

Overall, the tutorial is very straightforward, but there were a couple of glitches here and there that I thought I would highlight in this post. I decided to only install the WebAdmin Trac plugin and enable pretty URLs (both optional steps). It shouldn’t matter much, but I’m on bazooka.dreamhost.com and it has Python 2.3 installed by default.

Please note that you may want to allocate a block of about 2 hours to complete this process, since compilation times for e.g. Subversion tend to be rather long, at least on bazooka.dreamhost.com.

Clearsilver

Replace:

sed -i "s@/usr/local/bin/python@/usr/bin/env python@g" \
scripts/document.py

PYTHON_SITE=`/home/{username}/packages/bin/python -c \
"import sys; print [path for path in sys.path if \
path.find('site-packages') != -1][0]"` \
./configure --with-python=/home/{username}/packages/bin/python \
--prefix=$HOME/packages \
--disable-ruby --disable-java --disable-apache --disable-csharp --disable-perl

With:

sed -i "s@/usr/local/bin/python@/usr/bin/env python@g" \
scripts/document.py

PYTHON_SITE=`/usr/bin/python -c \
"import sys; print [path for path in sys.path if \
path.find('site-packages') != -1][0]"` \
./configure --with-python=/usr/bin/python \
--prefix=$HOME/packages \
--disable-ruby --disable-java --disable-apache --disable-csharp --disable-perl

Update [August 30, 2006]: ~~Note: the {username} part above is to be replaced with your DreamHost shell user, e.g. jsmith.~~ (Thank you, Natmaster)

SWIG

A quicker way of downloading the required SWIG tar ball.

Replace:

Get http://easynews.dl.sourceforge.net/sourceforge/swig/swig-1.3.29.tar.gz into your home directory.

With:

wget http://internap.dl.sourceforge.net/sourceforge/swig/swig-1.3.29.tar.gz

WebAdmin Plugin

The easy_install script did not work unless the Egg package ended with .egg (i.e. not .zip). So, I just renamed the zip file to have a .egg extension.

wget http://trac.edgewall.org/attachment/wiki/WebAdmin/TracWebAdmin-0.1.1dev_r2765-py2.3.egg.zip?format=raw
mv http://trac.edgewall.org/attachment/wiki/WebAdmin/TracWebAdmin-0.1.1dev_r2765-py2.3.egg.zip?format=raw  TracWebAdmin-0.1.1dev_r2765-py2.3.egg.zip?format=raw TracWebAdmin-0.1.1dev_r2765-py2.3.egg

Note: Once installed, this plugin will appear as an “Admin” tab in the Trac UI for all users who have been given admin rights (see trac-admin section of the original tutorial).

Other Gottchas

File Permissions

If something isn’t working, go through all relevant files and directories nand make sure your file permissions are set to be readable by the web server, also double-check that the Trac user you are using has Trac admin rights, if you’re using the WebAdmin plugin.

Quick permission changing example:

cd target_directory
find . -perm 700 -print|xargs chmod 755

Setting Trac user permissions (from original tutorial):

trac-admin $HOME/trac_sites/{your trac project id}
permission add admins TRAC_ADMIN
permission add {username} admins

Note: In this case, you would repeat this process for each Trac project.

Typos

I started off by using the CGI version over FCGI to not complicate things. Although, because I did so, I forgot to update parts of the .htaccess file in each project directory. So, make sure you’re referencing “fcgi” and not “cgi” if you decide to use FGCI.

Note that if you’re using FCGI, you would want to enable it in the DreamHost control panel for the Trac domain you’re configuring, e.g. projects.domain.com.

It’s also easy to forget to change project name references in e.g. the index.cgi and index.fcgi files for each project, which can lead to some interesting results : )

Multiple Projects

Since I manage multiple projects, I ended up setting up a simple .htaccess file in my $HOME/projects.domain.com directory (using the DreamHost control panel or just manually). I used the same username as the one specified in the trac-admin tool with admin rights. I then created a sub-directory for each Trac project, resulting in project.domain.com/project1 etc.

Good luck with your Trac installation on DreamHost : )

Posted in Software Development | Tags dreamhost, trac, tutorial | 3 comments

Comments

Leave a response

nuke edit
natmaster.com said 14 days later:

Hello, this is natmaster, the author of the guide you reference here. I am curious as to the reasoning behind your Clearsilver installation changes. You explain what {username} means, but you instruct users to get rid of those references?

I would like to fix any issues with my guide, so users do not have to look through many pages when they run into troubles. Thanks for posting your ideas to the web. :)
nuke edit
Johan said 14 days later:

Ah; I see my mistake. I’m not sure how it slipped in there :-) I’ve removed the reference to replacing the {username}. The reasoning behind the ClearSilver change in the first place was that I found relying on the default system installation of Python easier and more appropriate, at least on bazooka.dreamhost.com. Thank you for the correction!
nuke edit
natmaster.com said 16 days later:

I also rely on the python installation to run. However, as I am not root, I cannot install necessary modules - which is why I reference my bin directory in some instances, so they can be installed in a place easily accessible.

RSS feed for this post

Tutorial: persistent camera settings (was Re: Checking, no rush, on my open questions)

http://mailman.ioxperts.com/pipermail/video-dev...

clipped by pingpong Nov 14, 2006

cv quicktime

Show Clip

Tutorial: persistent camera settings (was Re: Checking, no rush, on my open questions)

Julien Letessier lists at mezis.net
Mon Mar 21 23:23:21 GMT 2005

Next message: Tutorial: persistent camera settings
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 6 Sep 2004, at 20:50, Hank Roberts wrote:

> Unibrain cameras:
>   Their support (finally) told me their  "fire-i" camera settings last 
> only as long as the application changing them is open.  Unibrain makes 
> a Windows app that supposedly saves and reloads settings, but again 
> the settings are lost when that app closes.  No other app can save 
> settings and reapply them.

Hi all,

This seems to be a recurrent question, and the aforementioned lack of 
persistence is true for several other cameras in addition to the fire-i 
(e.g. some Sonys and Marlins, and at least one of my ToUcams).

So here's a rough sketch the solution I use for persistence of camera 
settings.

I'm not saying that this is the one way to go, as this obviously works 
only if you're using the SG (as I don't really dig VDigs), like in the 
minimung, mungrab, sonofmungrab examples.

* saving settings:

        - call SGSettingsDialog() or anything you use to modify the settings
        - use SGGetChannelSettings() to put all settings into a UserData
        - use PutUserDataIntoHandle() to serialize the UserData into a Handle
        - use CFDataCreate() to transform you memory chunk into a CFDataRef
        - use CFPreferencesSetAppValue(theKey, theCFSettings, 
kCFPreferencesCurrentApplication)
          to associate theKey to your settings [1], for the current application
        - don't forget to CFPreferencesAppSynchronize()
          to save to the .plist file

        The tasks of locking/unlocking handles, and CFRelease'ing the right 
stuff, if left as an exercice to the reader ;)

        Once all's done settings are stored in the dictionary entry you 
specified (theKey), in the application's [2] preferences file (that's 
something like $HOME/Library/Preferences/com.gizmo.MyNiftyApp.plist)

* restoring settings

        Basically it's the same, the other way around.

        - CFPreferencesCopyAppValue(theKey, kCFPreferencesCurrentApplication)
          fetches back your binary data from the .plist preferences file
        - PtrToHand(CFDataGetBytePtr((CFDataRef)theCFSettings)
          turns it back into a handle
        - NewUserDataFromHandle() gives you the UserData
        - finally, SGSetChannelSettings() restores the settings

        This should be done pretty soon after calling SGNewChannel(), while 
the SG isn't previewing/recording (yet).

[1] I recommend you use a key built from the DeviceName and the 
InputName. Otherwise you're going to obtain very weird, mixed up 
settings when plugging in a different camera, possible even ruining a 
sensitive CCD. Don't laugh.

[2] This means each { user, application, camera } combination gets 
unique persistent settings. This may or may not be what you're looking 
for; in the latter case, tinkering with the options of 
CFPreferencesSetAppValue() / CFPreferencesCopyAppValue() may provide 
other combinations (e.g. user / host / camera).

Pixelache festival » Submission form for Pixelache 2007 events

http://www.pixelache.ac/2007/pixelache-submission/

clipped by pingpong Nov 13, 2006

apply newmedia

Show Clip

Mediengestaltungs Blog » Blog Archive » Festival:Open Fader

http://www.khm.de/mg/blog/?p=317#more-317

clipped by pingpong Nov 13, 2006

apply newmedia

Show Clip

Festival:Open Fader

Call for works: the Sonorities Festival in Belfast invites composers and artists
working with sound to submit works to be presented during Sonorities
2007. We are especially interested in works that challenge or expand
the current vocabulary and practice of digital audio performance and
composition. http://qub.ac.uk

Important Dates
Deadline for Submissions: 17th December 2006
Festival Dates: 21 April - 25 April 2007

We encourage two types of submission (maximum of 1 work per category):

1. Live Performances

This includes laptop improv, VJ, audio-visual, live-electronics,
sound poetry, circuit-bending, hacktivism. Please submit the work in
a documentary format that reflects the nature of the performance
(e.g. video on DVD, audio on CD, software for Mac/PC, photographs).

2. Fixed Media Works (from mono to a maximum of 24 channels)

This includes works for live diffusion, multi-channel works with
predetermined spatial placement, and works with video. All submissions
must be on DAT, audio CD, data CD-R or DA88. Submissions of
multi-channel works on data CD-R must be accompanied by an audio CD
containing a stereo reduction, along with diagrammatic instructions
for mapping of mono audio sources to destination speakers, along with
a ProTools session, MaxMSP or Pd patch to accomplish the
mapping. Works with video must be on DVD.

Selected works will be featured in four special concerts during the
festival. These events will take place in the Sonic Arts Research
Centre Sonic Lab performance space. This unique environment for the
performance of electroacoustic music includes facilities for sound
projection in a full 3D environment through loudspeakers located above
and below the audience area. The special nature of the space makes it
essential that selected artists attend the Festival to perform their
pieces. The Sonic Lab allows diffusion to a maximum of 48 speakers.
(Please see http://www.sarc.qub.ac.uk/pages/soniclab.htm for more
information.)

Please include a title and program notes as well as a short biography
with the submission. Contact information should include a phone
number, address, and an email address. A stamped, self-addressed
envelope is required for the return of your materials. Materials that
are not required to be returned will become part of SARC’s media
library and may be considered for future events.

Artists are expected to finance their participation. Sonorities will
be able to provide letters of support, which can aid in seeking
funding. Please include a title, program notes as well as a short
biography with the submission. Contact information should include a
phone number, address, and an email address.

Post works to
OPEN FADER
Sonorities 2007
Sonic Arts Research Centre
Queen’s University Belfast
Belfast BT7 1NN
Northern Ireland

Contact
Eric Lyon (Artistic Director)
e.lyon at qub.ac.uk

This entry was posted on Tuesday, October 17th, 2006 at 12:48 pm and is filed under Themen, Gelegenheiten, Festival, sound design/creation. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

E-Flux : NEW MEDIA ART AWARDS - (2006-10-20)

http://www.e-flux.com/displayshow.php?file=mess...

clipped by pingpong Nov 13, 2006

apply newmedia

Show Clip

News:
e-flux video rental
opens in 3 new locations

10/20/06

ARCO/BEEP

ARCO/BEEP NEW MEDIA ART AWARDS
2nd edition
Conceded by BEEP, in collaboration with ARCO
Worth 8.000 euros and 6.000 euros

http://www.arco.beep.es

The goal of these awards is to advance the production and exhibition of New Media Art, and art linked to new technologies. Its purpose is to promote new high-tech art, and to foster communication between the manufacturers/creators of this new technology and those who create art. A natural collaboration, which will benefit and enrich both sides.

There are two ACQUISITION PRIZES:

1) @ARCO Prize: worth 8.000 euros. To be eligible, an artwork must be shown by a gallery at the 26th edition of ARCO, the International Contemporary Art Fair, in Madrid (15-19 February 2007), and must have a significant component involving new technology or electronic media.

2) OFF-ARCO Prize: worth 6.000 euros. Artworks presented by individual artists or collectives.

The prizes will be awarded by an international jury of prestigious specialists.
Registration form will be available from the 30th of October on the ARCO/BEEP NEW MEDIA ART Prize website http://www.arco.beep.es

email to a friend contact subscribe

electronic flux corporation / www.e-flux.com
295 greenwich street #532, nyc ny 10007

to unsubscribe click / here

site design

CVonline: Vision Geometry and Mathematics

http://homepages.inf.ed.ac.uk/rbf/CVonline/geom...

clipped by pingpong Nov 06, 2006

cv

Show Clip

Your name	(leave url/email »)
Your blog
Your email
Your message
Comment Markup Help Preview comment

Old Beta Users

Related Tags

pingpong's Inbox

Quicktime export as RGB instead of ARGB

Thread: Quicktime export as RGB instead of ARGB

Subversion Instructions

From iFolder

Browse SVN Online

Available Versions

Anonymous Subversion Access

Developer Subversion Access

Subversion on Windows with TortoiseSVN

Subversion on OS X

Views

Personal tools

Navigation

Search

Toolbox

The Natmaster - Natmaster.com

Introduction

Assumptions

Python

Environmental Variables

Installation

Setup

Install Trac (0.9.6)

Install Clearsilver (0.10.3)

Install SQLite (3.3.6)

Install PySQLite (2.3.2)

Install SWIG (1.3.29)

Install Subversion (1.3.2)

Setup Trac Environment

Make Trac Web Accessible

Prettiness

Pretty URLs

Setup static mapping

Setup Rewrite Rule

Hack the Trac base_url

Plugins

WebAdmin Plugin

AccountManager Plugin

DbAuth Plugin

Cleanup

Delete setup files

Switch to fcgi

If you are using 'Pretty URLs'

Otherwise

References

“Imagination is everything. It is the preview of life's coming attractions.” -- Albert Einstein

Installing Trac on DreamHost

Clearsilver

SWIG

WebAdmin Plugin

Other Gottchas

File Permissions

Typos

Multiple Projects

Comments

Topics of Interest

Tags

Categories

JohanV's Photos (flickr)

People

Sponsored Content

Community

Archives

Tutorial: persistent camera settings (was Re: Checking, no rush, on my open questions)

Submission form for Pixelache 2007 events

Pikseliähky 2007

Mal au Pixel 2007

Pixelazo & Selvatorium 2007

Call for projects / participants

Recent events

Pikseliähky 2006

Mal au Pixel 2006

Register to blog and submit posts for review

Thanks for latest comments

Contents

50 links from the road

Feeds

“Imagination is everything. It is the preview of life's coming attractions.”
-- Albert Einstein