Comments on MyInnoQBlog by Daniel Pietzsch http://www.innoq.com/blog/dp//Comments Visitors of MyInnoQBlog http://www.innoq.com/blog/dp/ webmaster@innoq.com Movable Type http://www.innoq.com/favicon.ico 2008-04-29T18:31:36Z 2008-03-14T20:15:12Z http://www.innoq.com/blog/dp/2007/11/make_textmate_cope_with_rails.html#c269376 Daniel Daniel on "Make TextMate cope with Rails 2.0 filename convention" Maybe one could combine code fragments of the CSS language and the HTML (Rails) language.
But I'm really not sure if this would work...

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

]]> 2008-03-14T05:13:04Z http://www.innoq.com/blog/dp/2007/11/make_textmate_cope_with_rails.html#c268324 Vern Vern on "Make TextMate cope with Rails 2.0 filename convention" I suppose there is no way yet to get ruby syntax in the css.erb file as we do in html.erb?

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.

]]> 2008-03-13T17:47:02Z http://www.innoq.com/blog/dp/2007/11/make_textmate_cope_with_rails.html#c267906 David Flaherty David Flaherty on "Make TextMate cope with Rails 2.0 filename convention" Daniel,

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
]]> 2008-03-12T11:34:03Z http://www.innoq.com/blog/dp/2008/03/more_ermodelling_1.html#c267225 Daniel Daniel on "More ER-Modelling" Hi Phillip,

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.

]]> 2008-03-12T09:12:25Z http://www.innoq.com/blog/dp/2007/11/make_textmate_cope_with_rails.html#c267186 Daniel Daniel on "Make TextMate cope with Rails 2.0 filename convention" Hi David,

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.

]]> 2008-03-11T23:30:32Z http://www.innoq.com/blog/dp/2008/03/more_ermodelling_1.html#c267010 Phillip Ghadir Phillip Ghadir on "More ER-Modelling" In some special cases there might be a need for multiple entries per day for a TimeReport. According to this there might be a better name than DailyReport, although the relationship (TimeReport -> DailyReport) is sufficient, DailyReport.Date is not an suitable identifier.

]]> 2008-03-11T21:16:06Z http://www.innoq.com/blog/dp/2007/11/make_textmate_cope_with_rails.html#c266946 David Flaherty David Flaherty on "Make TextMate cope with Rails 2.0 filename convention" Daniel,

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

]]> 2008-02-27T17:27:56Z http://www.innoq.com/blog/dp/2008/02/second_ui_mockup.html#c252736 Daniel Daniel on "Second UI mockup" The "Stunden"-column was meant to be for a summary of worked hours for each week.
In the current (unpublished) version of this mockup I already removed this column, because I think it's not really necessary due to the fact that you see the sum of all hours of the month in the sidebar.

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... ;-)

]]> 2008-02-27T15:33:16Z http://www.innoq.com/blog/dp/2008/02/second_ui_mockup.html#c252703 Gerald Schenke Gerald Schenke on "Second UI mockup" Looks very nice. What is the "Stunden"-column for?

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!

]]> 2008-02-26T18:18:30Z http://www.innoq.com/blog/dp/2008/02/altered_ermodel_update.html#c251741 Daniel Daniel on "Altered ER-Model [UPDATE]" Thanks for your comment. I really wasn't sure how to store all the working hours. It seemed to much effort to me to add a new database entry for every day, employee and project; and due to the fact that this data is only used in this screens to calculate the complete amount of hours. So far it has no relevance for any other part of the application.

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

]]> 2008-02-26T17:37:36Z http://www.innoq.com/blog/dp/2008/02/altered_ermodel_update.html#c251726 Stefan Tilkov Stefan Tilkov on "Altered ER-Model [UPDATE]" There is absolutely no reason to save space by encoding stuff within database fields -- I would strongly advise against this :-)

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.

]]> 2008-02-21T16:24:12Z http://www.innoq.com/blog/dp/2008/02/first_ui_mockup_1.html#c246846 Daniel Daniel on "First UI mockup" Yes, the notes to the right are for the whole month. So far I think that's enough, because it is intended to be mostly for personal use. And hey: you know when you've been lazy... ;-) And I think this wouldn't add any useful information when it comes to invoices.

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

]]> 2008-02-20T15:12:46Z http://www.innoq.com/blog/dp/2008/02/first_ui_mockup_1.html#c245116 Gerald Schenke Gerald Schenke on "First UI mockup" i guess the notes on the right site are for the whole month. Will it be possible to add notes for every single day? (e.g. "Today i was really lazy and did nothing at all except writing this note!") :D

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

Nice work. Keep going!

]]> 2008-02-20T11:59:22Z http://www.innoq.com/blog/dp/2008/02/first_ui_mockup_1.html#c244938 Daniel Daniel on "First UI mockup" Ok, thanks for your comments.

"Nice. Note that any one employee may be working on two or three
projects simultaneously - not sure how this would be handled with this
UI."

That was one question I had. This is definitely not handled so far.

"Dealing with the many input fields: similarly to iCal, a field could
be created only after the user has clicked into a particular day cell."

That's exactly what I had in mind.

]]> 2008-02-19T14:36:32Z http://www.innoq.com/blog/dp/2008/02/first_ui_mockup_1.html#c243970 Tim Tim on "First UI mockup" I think for your web-app is getting real a good approach. Because is the ui bad the user thinks the whole system is bad :). By the way i like the first mockup.

]]> 2008-02-18T21:43:04Z http://www.innoq.com/blog/dp/2008/02/first_ui_mockup_1.html#c242411 Stefan Tilkov Stefan Tilkov on "First UI mockup" Nice. Note that any one employee may be working on two or three projects simultaneously - not sure how this would be handled with this UI.

Dealing with the many input fields: similarly to iCal, a field could be created only after the user has clicked into a particular day cell.

It's definitely a great idea to start with UI mockups.

]]> 2008-02-05T23:00:49Z http://www.innoq.com/blog/dp/2008/02/years_of_irrelevance.html#c220580 Phillip Ghadir Phillip Ghadir on "Years of irrelevance" Actually, that's why innoQ prefers most to rely on word-of-mouth recommendations by colleagues we know well.

Certificates and diplomas can't tell you about the abilities of applicants. Neither job interviews can.

In my view every job offer describes a need; giving people hints what might be expected. Formalizing these aspects while ignoring its essence is weakness of several HR professionals.

]]> 2007-12-02T17:31:28Z http://www.innoq.com/blog/dp/2007/11/leopard_tech_talk_summary.html#c161842 Daniel Daniel on "Leopard Tech Talk Summary" Hi Robin,

thanks for your comment.
And yes: I know what that means. But I think I didn't post anything that violates this agreement, because it's no super-secret information, that has not been published before (at least the majority of the points). And it's also no in-depth stuff you couldn't figure out by reading apples websites.

]]> 2007-11-29T19:42:48Z http://www.innoq.com/blog/dp/2007/11/leopard_tech_talk_summary.html#c160137 Robin Robin on "Leopard Tech Talk Summary" Hi !

Nice summary, but You know what "IMPORTANT: Remember to bring a photo ID and this registration notice, both are required to enter the event. This event is strictly under ADC NDA and is BY INVITATION ONLY." means ?

That line was in your confirmation email.

greetings Robin

]]> 2007-11-23T19:30:27Z http://www.innoq.com/blog/dp/2007/11/rails_sammelsorium.html#c156333 Daniel Daniel on "Rails Sammelsorium" Freut mich geholfen zu haben!

]]>