make Code::Blocks a remote IDE

[uniwin]

sometimes we may need to develop programs on UNIX but still want IDEs based on Windows. Uniwin is the tool for this purpose. It is a small toolset to make a IDE to be a remote develop environment seemlessly. Uniwin can be downloaded from http://sourceforge.net/projects/uniwin. Uniwin has been tested for Code::Blocks already.

[Michael]

Hello,

It seems an interesting tool . Thanks for the info.

You said that "Uniwin has been tested for Code::Blocks already", but which are the conclusions?

Best wishes,
Michael

[MortenMacFly]

The embedded PDF document says:
"Dev-Cpp, Relo, Code::Blocks, Vide and ...
Maybe you prefer some other IDEs on windows, such as Dev-Cpp, Code::Blocks, Relo, Vide
and so on. Uniwin can make them remote development environments seamlessly. What you
need to do is just modifying the names of gccs and g++s built-in with them for example
Dev-Cpp or providing them with the pseudo toolchains of Uniwin, such as Relo,
Code::Blocks, Vide."
...it really sounds interesting anyway...
Morten.

[takeshimiya]

Great!

If the data is separated enough from the GUI (and uses standard C++) it shouldn't be difficult to make a Code::Blocks plugin, which will be integrated better.

Also I wonder how difficult could be to add support for the inverse, let's say, using Code::Blocks on linux, and compiling remotely on a Windows box, using a MSVC 2003 Free Compiler or even Digital Mars D compiler.

[mandrav]

Nice work uniwin

But I wonder...
Am I supposed to make sense out of this?



[attachment deleted by admin]

[MortenMacFly]

If the data is separated enough from the GUI (and uses standard C++) it shouldn't be difficult to make a Code::Blocks plugin, which will be integrated better.

There is no need fo an integration. Theses are wrapper programs (g++, gcc...). You only need to make a copy of the GCC compiler in C::B and adjust the path's accordingly. 

[takeshimiya]

If the data is separated enough from the GUI (and uses standard C++) it shouldn't be difficult to make a Code::Blocks plugin, which will be integrated better.

There is no need fo an integration. Theses are wrapper programs (g++, gcc...). You only need to make a copy of the GCC compiler in C::B and adjust the path's accordingly. 

I'm talking about the little GUI:

You know, without having it more integrated it could have the same luck as cbDragScroll () before going to contrib: no users use it, because no users knows it.
Same goes for nice tools like STL GDB,  STLFilt, or c++filt, they aren't more widespread here because they aren't "GUI user friendly" integrated.

[killerbot]

You know, without having it more integrated it could have the same luck as cbDragScroll (Smile) before going to contrib: no users use it, because no users knows it.

wait and see ...

[uniwin]

I'm talking about the little GUI:

You know, without having it more integrated it could have the same luck as cbDragScroll () before going to contrib: no users use it, because no users knows it.
Same goes for nice tools like STL GDB,  STLFilt, or c++filt, they aren't more widespread here because they aren't "GUI user friendly" integrated.

I changed it to XP style now, it looks a little better.