Diese Jungs wissen wovon sie reden:

Beim Nerdcore gefunden! Danke!

We are using the asset packager in order to reduce the amount of requests to the server. The other bebefit is, that you can compress one bigger file (packager combines all css files into one big one) better, that e.g. 5 smaller ones. It is a great plugin, but recently we had some trouble with it.

Well, when testing some changes in production mode, the site lookes crappy. In development mode, everything looked fine. After doing some debugging, we found out, that a comment in a css file was the problem.

css line: “… … …;z-index:20000;/*paranoid value!*/}”

After calling “rake asset:packager:build_all”, the combined file looked like this:

“… … …;z-index:20000;”

The “}” was missing, which means, that the packager just searches for a starting comment and kills the rest of the line witout checking the end of the commend.
Just keep that in mind, when you write your css.

If you want to run your Rails application on a Mac OS X environment (either production or development) or deploy it to a Mac OS X machine, this tsoosayLabs-post is maybe worth reading it. There is a lot of information around in the web, but I couldn’t find a website that covered all the little subtleties that I had to go through. So I try to list it here.
Read the rest of this entry »

you just have to know.

After setting up your rails application, you have a default homepage. It is shown, when you call “http://localhost:3000/”. You can change the default homepage in the routes.rb file. Sounds easy. I changed the file and added the following line at the bottom:

map.connect ”, :controller => ‘window’, :action => ‘list’

Quite disappointing: the old start page was still there. After some googling around, I found out what to do. You also have to remove the static index.html in the /public folder.

… you just have to know …

We came to the point that we wanted a file upload without page refresh. With rails it is easy. We are using the “responds to parent” plugin.

You install the “responds_to_parent” plugin.

In your view add the following code :

<form name="upload" id="upload" action="/image/your_action"
enctype="multipart/form-data" method="post"
target="uploader">

don`t forget to add an iframe with the id=”uploader”

In your controller add the following code :

responds_to_parent do
   render :update do |page|
      page.replace_html 'your_id', 'it worked!'
   end
end

voila the upload process is now working and you can communicate with the parent with the responds_to_parent method…

it`s so easy - you just have to know

here is a list of rails - plugins we use

• acts as authenticated (easy to use login) - very easy to use
• acts as state machine (state machine for user) - very easy to use
• asset packager (compresses JS and CSS in one file - will be built in rails 2.0) - very easy to use
• file_column (image uploade plugin - scales your image + several security checks) - a little bit more work

gems we use :

• rmagick (ruby image magick interface) - the install on macs is a little bit complicate
• gettext (localization for rails) - easy to install, easy to use

there are many more “acts as” plugins - these will help you for the most usecases in the web - comments, tags, voting

“Enterprise Emulation” is the best one

Hi,

as we build an international application we need a translation mechanism for ruby on rails. i did some research and found that gettext is supported best and has a nice documentation. GetText Documentation

good :
- translations are not stored in the database
- translation is done with _(’string’) - so it`s easy to implement
- gem install gettext
- there is an editor for editing the translations - poedit
- the catalog can be build from your _(’string’) entries in your model,controller and views

bad :
- po files need to be converted to mo files and then are useable from the system

trap :
- first add gettext to your application.rb and then do the rake tasks

• 2.33GHz Intel Core 2 Duo
• 1440 x 900 pixels
• 2GB memory
• 120GB hard drive¹
• 6x double-layer SuperDrive
• ATI Mobility Radeon X1600 graphics with 256MB SDRAM

yeah…. now i also have a nice shiny laptop and a cool designer mouse…

first thing i will do is install windows and delete mac osx - so i have a cool operating system…

just a joke - i`m just compiling ruby,mysql and “geming” rails… next thing is installing aptana and then subclipse… then i hope we are ready to go… the first prototypes are already checked in and all developers are merging their stuff… the wiki is also beginning to live…

here my first pic with photo booth…

Blondie – One Way or Another

today’s list:

wiki setup

finally team has access and - hopefully - the right permission - with help of

proudly presenting
the true and only
F A L K O

svn setup

finally - thanks to - I have to admit he’s great - sometimes Falko again

ide

easyeclipse for rails installed and first sources of our prototype checked in

So - collaboration on project level can start now - project lead has finally a place to share their slide-ware, xls-spreadsheets, etc. that is not called f***ing fileserver - we only have to tell’em that the wiki is not about sharing binary crap

And yes, for all the hardcore rails-disciples - this means we are not using textmate - not now at least

We think that we need a CMS so i had a lookout for Content Management Systems.

The best source of information is a very nice page in the rails wiki (Ruby on Rails based CMS).

But i also found the sceptic and there is also much truth behind it.  Look at the article “Why Content Management Fails”

I also have no problem to use php Content Management Systems. I know Typo3 and it sucks because of typoscript :).But typo3 sucks less as some other CMS Systems. But it needs url rewriting to get nice SEO Paths so that the google bot can index it perfectly. The worst kind of CMS i used was RedDot. The Interface is a “mouseclick” hell and the templates are managed in a HTML Editor.  (and the interface is a hell having javascript memory leaks and breaking down the IE6)

So i will do some research on the web and look at the CMS Systems mentioned in the article “Ruby on Rails based CMS”.