Thank you everybody for your useful advices; especially Brian for the link.
(I hadn't seen that page before!)

I guess I found my answer: ROS covers our particular needs (moderated
autonomous mobile manipulation in rough terrain) far more than Player. But
first we should start feasibility study!

Thank you again!

- Amir

============================
Amir Hossein Soltanzadeh
ME @ R&D Dep. in ISOP Int. Co.
RA @ Robotics lab in IAUCTB
Fax: +98 (21) 883 19 902
Tel: +98 (21) 888 10 817
Cel: +98 (912) 20 60 429
ICQ: 434884650
Skype: amirhst
email: amirhst@isop-co.com
web: www.isop-co.com
blog: amirhst.blogspot.com
============================


On Mon, Dec 13, 2010 at 12:35 AM, Brian Gerkey <gerkey@willowgarage.com>wrote:

> On Sat, Dec 11, 2010 at 9:54 AM, Dejan Pangercic
> <dejan.pangercic@gmail.com> wrote:
> > I believe that Brian will better answer your question. Until then you
> > can browse the archive of this mailing list (keywords: player ros
> > migration) as this issue has been already discussed couple of times. I
> > see also that Brian has actually set up a wiki page dedicated to it
> > too: http://www.ros.org/wiki/ROS/PlayerIntegration.
>
> This page may also help:  http://www.ros.org/wiki/ROS/Introduction#Goals.
>
> > @Brian: Is Player actually still being actively developed?
>
> Player is in the capable hands of Rich Mattes, who released v3.0.2 in
> July.  There hasn't been much change in the middleware for some time
> now.  These days it's mostly driver improvements and portability fixes
> (e.g., you can get a Windows installer for Player 3.0.2; can't say
> that for ROS, yet...).
>
>        brian.
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>