RE: [ros-dev] Visual IDE for ROS

[Murphy, Ged (Bolton)]

Joseph Miller wrote:

>   So I am currently working on making my Visual GWin++ 
>  project work under ReactOS.   
If it works under windows, it should work under ROS.
If it doesn't, it's likely there is some missing functionality or bugs in
ROS at the moment.
You shouldn't modify your program to work under ROS if it breaks Windows
functionality, as it's likely to be fixed in the future.

If it works under Windows but not ROS, try to establish why and report it.
This would be a more productive way for both projects.

Regards,
Ged.



************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk 
<mailto:[e-mail]> and then delete this message. 

Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com

[calcmaster.NET]

I will continue to develop Visual GWin++ for Windows, but then I will make the 
modifications so that it will work with ROS.  I do expect that in the near 
future, it will work with ROS without any modifications, and I may try to 
work with the ROS source code to add the functionality and fix the bugs that 
I need.  At this point it was just easier to do it backwards.

In my original email, I did mention the problems that I was having with some 
of the messages.  One thing that I did leave out is that I could not get 
Visual GWin++ to interact with Scite on ROS.  I'm assuming that the problem 
most likely comes from lack of implementation of RegisterWindowMessage(), but 
that's just a guess.  Maybe you guys would know more about that.  Still, any 
help for where to look to begin making the modifications for those messages 
would be helpful.  Thanks.

-Joseph

On Monday 13 June 2005 3:23 am, Murphy,  Ged (Bolton) wrote:
>   Joseph Miller wrote:
> >   So I am currently working on making my Visual
> > GWin++
> >  project work under ReactOS. 
>  If it works under windows, it should work under ROS.
>  If it doesn't, it's likely there is some missing functionality or bugs in
>  ROS at the moment.
>  You shouldn't modify your program to work under ROS if it breaks Windows
>  functionality, as it's likely to be fixed in the future.
>
>  If it works under Windows but not ROS, try to establish why and report it.
>  This would be a more productive way for both projects.
>
>  Regards,
>  Ged.
>
>
>
>  ************************************************************************
>  The information contained in this message or any of its
>  attachments is confidential and is intended for the exclusive
>  use of the addressee. The information may also be legally
>  privileged. The views expressed may not be company policy,
>  but the personal views of the originator. If you are not the
>  addressee, any disclosure, reproduction, distribution or other
>  dissemination or use of this communication is strictly prohibited.
>  If you have received this message in error, please contact
>  postmaster(a)exideuk.co.uk
>  <mailto:[e-mail]> and then delete this message.
>
>  Exide Technologies is an industrial and transportation battery
>  producer and recycler with operations in 89 countries.
>  Further information can be found at www.exide.com
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev

[Ge van Geldorp]

>   From: calcmaster.NET
>  
>  One thing that I did leave out is that I could not get
>  Visual GWin++ to interact with Scite on ROS.  I'm
>  assuming that the problem most likely comes from lack
>  of implementation of RegisterWindowMessage(), 
>  but that's just a guess.  Maybe you guys would know more 
>  about that. 
AFAIK, our implementation of RegisterWindowMessage() is complete.

Gé van Geldorp.