Day Multi-Status

crutch you should definitely look at the way things are done in the latest release, a lot of changes were made that this code would not necessarily work with.

This could conflict with the work aacraig is doing on configurable status'. We may need to do one or the other first.

I think we should think of a way to do the diagonal box with either css or jQuery rather than images. Reason being that images are more difficult for people to customize and if we ever move configuration of colors into the administration area they wouldn't work.

Let me know if you have questions about how things are changed in latest dev.

I invested a little time into searching for css solutions to diagonally sliced colors and found this:
http://www.infimum.dk/HTML/slantinfo.html
which is ultimately from Eric Meyers (the css god):
http://meyerweb.com/eric/css/edge/slantastic/demo.html

It seems like a solution to a diagonally colored box, but I am not completely sure about positioning text within it. The colored div would likely have to be positioned via relative positioning and a z-index to place it behind the text. I will see if I can get a working example.

Other ideas are welcome.

I was able to accomplish what we need, in testing, with the following:

Example HTML:

<table>
  <tbody>
    <tr>
      <td><div class="cal-slanted-day">31</div><div class="cal-slanted-bg calavail_calnot"></div></td>
    </tr>
  </tbody>
</table>

Example CSS:

.cal-slanted-day, .cal-slanted-bg{position:absolute;}
.cal-slanted-day{font-size:12px;height:15px;padding:2px 0 1px;text-align:center;width:20px;z-index:0;}
.cal-slanted-bg{z-index:-1;float:left;border-width:10px;border-style:solid;width:0px;height:0px;line-height:0px;}
.cal-slanted-bg.calavail_calnot{border-color:#90EE90 #FFB6C1 #FFB6C1 #90EE90;}

Works for me and should be cross-browser compliant as well as easily added to the module.

I have added an initial commit of this feature: http://drupal.org/cvs?commit=473522

It needs to be reviewed and css tested across browsers. The latest dev is stable but definitely requires a run of update.php when upgrading. I do not suggest running the update on a live site since I am the only one who has tested the upgrade path. Please let me know your findings.

Just use dev from Jan 03. That has all my changes. If you are using this on a fresh installation, no availability calendar data has been saved yet you will not need to run update.php.

You will also need to enable the checkbox under admin/settings/availability_calendars to get the extra options.

I fixed the error in the sql statement.http://drupal.org/cvs?commit=474124

For the CSS, I want to attempt to stay only using CSS but this may call for some jQuery to determine the width/height of the surrounding cell. Either that or possibly just doing some aggressive resets on our table's elements. I will have to think about it and look into some possible fixes for the css.

Found a few more things that I didn't consider in the upgrade path, those are fixed now too.
http://drupal.org/cvs?commit=474144

crutch, I think what I would like to do is to do some general theming for some popular base themes and core themes. I am thinking of doing the following since these css changes really are very dependent on the different themes' loaded stylesheets.

Load different css dependent on the theme:

function availability_calendars_init() {
  // base css
  drupal_add_css(drupal_get_path('module', 'availability_calendars') . '/availability_calendars.css');
  // current theme info
  $theme_data = _system_theme_data();
  $theme_key = array_pop(explode('/', path_to_theme()));

  // themes we will perform specific theming on
  $core_themes = array('garland', 'bluemarine', 'chameleon', 'marvin', 'minnelli', 'pushbutton');
  $base_themes = array('fusion', 'tao', 'zen', 'ninesixty');

  // check to see if we are using a core theme
  if (in_array($theme_key, array_merge($core_themes, $base_themes))) $add_css = TRUE;
  // check whether the theme being used is a subtheme of one of our themed base themes
  foreach ($base_themes as $key) {
    if (array_key_exists($key, $theme->base_themes)) {
      $theme_key = $key;
      $add_css = TRUE;
      break;
  }
  if ($add_css) drupal_add_css(drupal_get_path('module', 'availability_calendars') . '/css/' . $theme_key . '.css');
}

Then we can just load up different css dependent on the theme.

Hadn't actually tested the above code before posting, just worked it out in my head. Here is some more definite working code.

function availability_calendars_init() {
  // base css
  drupal_add_css(drupal_get_path('module', 'availability_calendars') . '/availability_calendars.css');
  // current theme info
  $theme_data = _system_theme_data(); // array containing info about all themes
  $theme_key = array_pop(explode('/', path_to_theme())); // get the currently enabled theme's namespace, can't find a better way to do this
  $theme = $theme_data[$theme_key]; // object containing all info about current theme
  $theme_bases = $theme->base_themes; // array of current theme's base themes

  // themes we will perform specific theming on
  $core_themes = array('garland', 'bluemarine', 'chameleon', 'marvin', 'minnelli', 'pushbutton');
  $base_themes = array('fusion_core', 'tao', 'zen', 'ninesixty');

  // check to see if we are using a core theme
  if (in_array($theme_key, array_merge($core_themes, $base_themes))) $add_css = TRUE;
  // check whether the theme being used is a subtheme of one of our themed base themes
  foreach ($base_themes as $key) {
    if (is_array($theme_bases)) {
      if (array_key_exists($key, $theme_bases)) {
        $theme_key = $key; // if the current theme is a subtheme of one of our base themes then use the base theme's namespace instead of our enabled theme's
        $add_css = TRUE;
        break;
      }
    }
  }
  if ($add_css) drupal_add_css(drupal_get_path('module', 'availability_calendars') . '/css/' . $theme_key . '.css');
}

Ok, I have done some testing in multiple themes. I have made a series of commits that should get this styling looking pretty decent in a majority of core and popular base themes.
http://drupal.org/cvs?commit=478886
http://drupal.org/cvs?commit=478888
http://drupal.org/cvs?commit=478890
http://drupal.org/cvs?commit=478892

Please give the changes a try through a cvs checkout of the dev or using latest dev (Jan 10 or later) once it is generated.

Give the latest dev as of today (or cvs checkout) a try.
http://drupal.org/cvs?commit=484022

I think I pinpointed the issues.

marking as fixed and moving my changes into 6.x-1.5

This is going into 6.x-1.5. There will still be some css tweaks in the future, but not enough issues to keep it from releasing.

Day Multi-Status in 7.x version possible? Is there an ability to use this css and configuration in 7.x version of the module?

No, this module is whole day or whole night booking only.