website

[phpwiki]
Working on web applications for the @lab or UABgrid will require some web development skills. You can gain the basics with the material available on the web. Understanding HTML, CSS and how to lay out a page is useful for effective communication.

* An [HTML tutorial|http://www.tizag.com/htmlT/index.php]. Good for the basics and as a reference.
* Some [insight into the process of design|http://www.stopdesign.com/articles/design_process/]. It works much like other creative processes, just different tools and materials.
* An important [overview of the CSS layout model|http://www.brainjar.com/css/positioning/]. You won't be able to control web layout without this one.

Well I've done the groundwork to get the development environment going using eclipse and drupal. It was a bit of a struggle, but I think I have a handle on it now. I just happen to stumble upon an easier way to get another development environment up and running with much less headache and mess. The secret?? Xampp!! You go to that site and see a groovy chic having fun on the page! She's probably happy because xampp is soooo easy! Basically, you download the xampp package, install it, and start it. That's it! It's simple instructions for anybody from Linux to Windows.

[phpwiki]
been looking into the updates that would be needed to support folksonomy in drupal, known as free tagging. i like the idea of letting the end user determine the vocabulary for entries. I looked at the [drupal support for tagging|http://drupal.org/node/20936]. it really needs it to allow end-user control over vocab. from the description of the features, though, it seems like it needs some work to add features. i'd like to get the [wordpress features jim described|https://mywebspace.wisc.edu/jamesphelps/web/WordPress/wordpress_folksonomy.html] because in order to use tags in a meaningful way, you really need to have a list of popular tags to choose from or reference.

[phpwiki]
Looks like tagging support has been added to drupal 4.6 (and provides more
motivation to upgrade the @lab site). This is a logical extension to
durpal's already strong taxonomy support. The major enhancement is that
it makes term creation an end-user feature rather than restricting it to
admins.

http://drupal.org/node/20936

i don't understand why drupal separates comments out as a distinct
content type. it seems like it would be better to consider everything as
a node, ie. inherited from a node type. this would potentially enable
a common display framework with different renders. it also seems like
having all node type be identically defined, that is no second class
types, would help make the content rendering easier. eg. the node table
types would be anything defined by the taxonomy and the base set could
be the standard story, blog, page, etc. types. the legit content would
the simply be defined by the type tag. additional tables could be used

there are a ton of elements that make up a good site. the main pages (drupal, phpwebsite), special function services like documentation (latex2html), faq (phpMyFAQ), images (gallery), file store (read-only via apache, read-write via zope or webdav), search, maillist, the list goes on.

it's clear for this little list that in order for the user experience to be uniform across the applications there needs to be a common definition of users, groups for identities and authorizations.

this is nothing new, really. it is worth being explicit about it, though. that helps bring these elements to the fore front of the system. knowing what they are and how they can be accessed within the system.

[phpwiki]
review how to deal with lab-subscribed groups by individuals

a few problems with this: I want a forum block to tie in specific forum to
a project page; don't seem to be able to restrict no comments on such
forums to prevent responses (or posts) from anyone but the gateway, eg.
must post to mailling list not forum; would be nice to just have a web
interface to news groups, eg. don't delete the messages out of a backend
subscribers folder. don't take them to the web, show them on the web.

[phpwiki]
If you trying to test the bugzilla system to see how it works and play with assigning bugs to yourself and tracking changes but you're not getting an email alerts (as you would when others assign bugs to you or update bugs assigned to you) you probably need to check your account email preferences.

* Click on your account "Prefs" link in Bugzilla pages.
* Choose the "Email Settings" tab
* Make sure the ''Only email me reports of changes made by other people '' setting is unchecked.
* Save your changes

You should now receive bug reports and modifications you make to bugs assi

[phpwiki]
By default Apache 2.0 wraps the ssl server portion of it's configuration file in and directive. The IfDefined directive checks for values set by the -D command line option when apache was started. This means that "SSL" must be set on the command line when apache is started, otherwise the server will skip the ssl section of the configuration file and not listen on port 443.

The default way to start apache (or otherwise control apache) is with the apachectl command. This command is found in the directory $PREFIX/bin, where $PREFIX is the install prefix defined at compile time. When building from the source tarball, this is usually /usr/local/apache2/bin.

spent the day doing more layout changes on the uabgrid site. it's looking
good. will be able to move this over in the next few days, set up the new
db and get going on the ca work.

the xtemeplate theme is proving its worth. also shows ways in which all
manner of folk can participate in uabgrid. graphics artist can submit new
themes. and it's nice for us non graphic folks to have themes to shift
around a bit with minor color mods. also see how you could have an end
user select-a-theme feature for vo maintainers.