And ... well... i have top pay you a compliment for your Application design :-).

Luck and success with your thesis!

  def conditions_from_params
    conditions = nil
    params.reject {|key, value| [:controller, :action, :format].include?(key.to_sym)}.each do |key, value|
      next unless User.column_names.include?(key)
      if value.include?(';')
        value = value.split(';')
        conditions = merge_conditions(conditions, ["#{User.to_s.pluralize}.#{key.to_s} in (?)", value])
      else
        conditions = merge_conditions(conditions, ["#{User.to_s.pluralize}.#{key.to_s} = ?", value])
      end
    end
    conditions
  end

I'm still figuring out how to implement associations in ARes models.

yes, I know that this is not so efficient, but afaik ActiveResource doesn't support selecting a custom amount of records from a remote resource. It's either all or one!

/Daniel

vielen Dank für den Artikel. Genau das was ich im Moment gesucht hab. Und dank deinem Blog auch schnell gefunden hab.

Gruß Jens

And as I don't have that many css.erb files, I haven't tried this myself.

I checked the bundle editor and without knowing much about it can and it looks like it requires a specific language file set up for this.

Has anyone tackled this yet? I don't think I could fake my way through it. I thought maybe there is a way to apply "both" language types to one format.

Well, I thought that I had done that before to no avail, but it seems to have fixed the problem. Thank you so very, very much! Ahhh, TextMate, how I hate you & how I love you!

• D

thanks for replying.
I was aware of the fact that DailyReport.Date is not a suitable identifier. I think I'll have an ID as a primary key or go for a combination of DailyReport.Date and the foreign key Project.ID as a primary key.
Ok, that was not clear when looking at the graphic...so it's my fault. I should have mentioned the primary keys as well.

Concerning the naming of DailyReport, I should really choose a name that is more representative.

so far everything looks alright with your settings. They are exactly the same as mine; and in my case this works fine.

If you didn't already do this:
Maybe you have to explicitly apply the correct syntax highlighting (CSS) for css.erb files once.
You can do this in the status bar at the bottom. Right next to "column" and "line" display, there's the drop-down menu for syntax highlighting. Open a css.erb file and then choose "CSS" in that menu.
TextMate should then remember the settings for these files.

I hope this will work out for you.

Thanks for the helpful post. Still having some problems, though. I've grabbed the latest rails bundle from the TextMate svn respository and followed your directions, but in spite of having deleted the plain '.erb' from HTML (Rails), TextMate still seems to be reading css.erb files with HTML highlighting. I've reloaded the bundles and restarted the program a number of times. Any ideas?

For CSS:

{ scopeName = 'source.css'; comment = ''; fileTypes = ( 'css', 'css.erb' ); etc.

for HTML (Rails): { scopeName = 'text.html.ruby'; fileTypes = ( 'rhtml', 'html.erb' ); foldingStartMarker = '(?x) etc.

Thanks, D

And I also replaced the text-arrows by names of the months. Like this:

<< Januar     Februar     März >>

You'll see all these changes in the next mockup I post...

Thanks for the comment! It seems like you often share my thoughts... ;-)

The Arrows for next/previous month should in line with the name of the actual month. And they should not contain a "=" or be little images, but that are just details.

Good job!

So, ok, I'll make a revision of the model and consider your suggestion.

Having a table with working hours per day, employee and project seems fine to me. You can always keep a redundant total to speed up calculations, and archive old entries after a year or so.

Yes, and I will color the weekends, as I'll still have to style the calendar. So far it's just a fake anyway...

I like the layout so far. Perhaps you should consider to color the weekend-columns?

Nice work. Keep going!