my PHP buddy...

I am a Rails dev (Rails 3.2.9 / MySQL / Haml ) working on some pilot projects testing using TDD to get them running fine according to customer requirements. You can compare this work to some ‘story-boards’ describing the main features of the site

Once done, I’ll transfer the code to my good PHP-buddy ( using PHP5-Zen-Symphony / MySQL / HTML5)

He will have to finalize the development ( making the all movie) with his team , rewriting the controller actions in PHP , then adding fancy js things, , adding CSS3 , and nice design)

Is there any good documentation or links to help in better understanding between us ? as we are not foe… but friends

thanks for feedback

I am a Rails dev (Rails 3.2.9 / MySQL / Haml ) working on some pilot projects testing using TDD to get them running fine according to customer requirements. You can compare this work to some 'story-boards' describing the main features of the site

Once done, I'll transfer the code to my good PHP-buddy ( using PHP5-Zen-Symphony / MySQL / HTML5)
He will have to finalize the development ( making the all movie) with his team , rewriting the controller actions in PHP , then adding fancy js things, , adding CSS3 , and nice design)

Is there any good documentation or links to help in better understanding between us ? as we are not foe... but friends

Years ago there was a section to the old Rails Wiki that offered to work in the other direction -- for Rails-curious PHP developers to translate what they knew into the Rails way of thinking. I don't know if that's still available anywhere, but it might be a start.

Walter

Let me get this straight. You are developing a site in Rails and then giving the code to a PHP developer who will rewrite it in PHP?

Why doesn’t the PHP guy develop the site?

Why don’t you just use the Rails site?

Why don’t you learn PHP and develop the site?

Translating from Rails to PHP is probably (I’m no great shakes as a PHP developer here) going to result in some really crappy PHP code. It would be better for the PHP guy to throw the Rails code away and write it from scratch.

You have only one thing in common and that is MySQL and as it is hidden behind ORMs this is will render it moot given that the PHP ORM will be completely different to Active Record.

The best you can hope for is the UI, Use Cases and Database design from the Rails version will give a leg up to the PHP guy.

This is asking for trouble and I wouldn’t want to support it - “why is this part like this? dont know thats how it was in rails. why was it like that in rails? dont know I only know php”