A New Hope - KDE 4 multiplatform
Moderator: Moderator Team
Are you crazy? we are talk about opensource software!!Reacter wrote:Linux is Linux. MenuetOS is MenuetOS. Windows is Windows. ROS is ROS. ROS shares interface with Windows. Let Unix branches keep their GUI. KDE can be downloaded later.
ROS share code with Linux and this is right! I say NO to protectionism!
initially, i think ROS could use kde 4... this let the developer more time and resources for the frameworks.... and after this they could work on a dedicated GUI
it will be released in october 2007. now it's in alpha stageMadWolf wrote:hi all
what year 07 / 08 / 09 /and upKDE 4 will be released in october
i fink it may be interesting to have a look at it when it is released
What part of code does ReactOS share with Linux??meg112 wrote: Are you crazy? we are talk about opensource software!!
ROS share code with Linux and this is right! I say NO to protectionism!
Even if using it would be a good idea, it`s still not mature enough.meg112 wrote: initially, i think ROS could use kde 4... this let the developer more time and resources for the frameworks.... and after this they could work on a dedicated GUI
look this http://www.reactos.org/wiki/index.php/LinksWhat part of code does ReactOS share with Linux??
related projects section near Wine project
WINE isn't Linux specific. Several of its components can be used to replace DLLs in Windows. That may change if WINE actually does decide to break Windows compatibility, at which point we'd basically have forked off the code we'd need if it messes with our work.
The only thing we got from Linux itself would be USB support, and that's incomplete anyways. It's not like anything else from Linux would be useful to us, since they're built using a completely different architecture.
The only thing we got from Linux itself would be USB support, and that's incomplete anyways. It's not like anything else from Linux would be useful to us, since they're built using a completely different architecture.
Re: A New Hope - KDE 4 multiplatform
Even though this isn't on topic, I would use KDE for Windows anytime. That's just SOOOO awesome...meg112 wrote:KDE 4 will be released in october. it's new because runs on windows and OSX (multiplatform).
may be a good idea using it on ReactOS, because KDE is free.
It could be helpful for developers. they can concentrate their efforts in frameworks, because the windows manager already exists.
it is no use developing 20 times the same things!
what do you think about?
I stand corrected. The current USB code is from a non-Linux source.
People assume that just because we're GPL means we can or should make use of Linux code. Absolutely no. We're based off a completely different architecture, making a lot of their work useless. Everything they've implemented, we basically have to reimplement ourselves anyways. Sometimes their code is useful to look at, just to examine their drivers to see how hardware works. But all we need are the basics anyways, and we could just as easily examine BSD code.
It's far easier from a theoretical standpoint for the BSDs, Linux, and even Solaris to share code, barring the licensing issues, because they're all trying to create a UNIX like system. We are not. As such, we cannot use their code directly if we wish to create an NT-compatible system. This was one area where Alex was really helpful on, because he forced out all the code hacked in from Linux and reimplemented it properly.
And as a final word on KDE4, from our viewpoint, it differs greatly from the default Windows shell. As such, it is unsuitable as our default shell, as our objective is also to duplicate the look and feel of NT.
People assume that just because we're GPL means we can or should make use of Linux code. Absolutely no. We're based off a completely different architecture, making a lot of their work useless. Everything they've implemented, we basically have to reimplement ourselves anyways. Sometimes their code is useful to look at, just to examine their drivers to see how hardware works. But all we need are the basics anyways, and we could just as easily examine BSD code.
It's far easier from a theoretical standpoint for the BSDs, Linux, and even Solaris to share code, barring the licensing issues, because they're all trying to create a UNIX like system. We are not. As such, we cannot use their code directly if we wish to create an NT-compatible system. This was one area where Alex was really helpful on, because he forced out all the code hacked in from Linux and reimplemented it properly.
And as a final word on KDE4, from our viewpoint, it differs greatly from the default Windows shell. As such, it is unsuitable as our default shell, as our objective is also to duplicate the look and feel of NT.
What pages exactly???
AFAIK, the previous USB driver may have been based on Linux version, but this doesn`t mean that Linux and ROS share code!
Linux is Posix-alike on Linux kernel, ROS is Win32 on NT kernel. You could try to share solutions, but not code!
WINE works on Linux, but it doesn`t mean WINE IS LINUX. WINE IS a Linux based Win32 compatibility layer. We cooperate in DirectX develompent and use their Win32 dlls.
Still, our ReactX is more alike Directx than WINE`s (our`s a real clone, whereas theit Dx is being emulated over OpenGL), Dll`s that we use, are Win32 dlls (not Linux)!
I still can't think how anyone could get the impression of Linux and ROS sharing code.
ROS is not Linux! ROS is NT!
AFAIK, the previous USB driver may have been based on Linux version, but this doesn`t mean that Linux and ROS share code!
Linux is Posix-alike on Linux kernel, ROS is Win32 on NT kernel. You could try to share solutions, but not code!
WINE works on Linux, but it doesn`t mean WINE IS LINUX. WINE IS a Linux based Win32 compatibility layer. We cooperate in DirectX develompent and use their Win32 dlls.
Still, our ReactX is more alike Directx than WINE`s (our`s a real clone, whereas theit Dx is being emulated over OpenGL), Dll`s that we use, are Win32 dlls (not Linux)!
I still can't think how anyone could get the impression of Linux and ROS sharing code.
ROS is not Linux! ROS is NT!
Why is everyone going on about replacing stuff that you can actually download and install yourself later on? It's no rocket science, and if regular windows users are gonna feel comfortable, it must look and act as closely to windows as possible.
I am currently the main developer of bbClean, a bb4win branch (actually a bbLean branch, which is a branch of bb4win), and I of coarse use bbClean on all my systems. Still, those who want to use bbClean should install it themself. It shouldn't be bundled by default with the official ReactOS install. Neither should LiteStep, KDE4, or any other shell. Since it will be fully open, anyone will be welcome to make their own install CDs with the favorite shell bundled.
Just my 5 cents.
I am currently the main developer of bbClean, a bb4win branch (actually a bbLean branch, which is a branch of bb4win), and I of coarse use bbClean on all my systems. Still, those who want to use bbClean should install it themself. It shouldn't be bundled by default with the official ReactOS install. Neither should LiteStep, KDE4, or any other shell. Since it will be fully open, anyone will be welcome to make their own install CDs with the favorite shell bundled.
Just my 5 cents.
-
- Posts: 549
- Joined: Thu May 03, 2007 6:44 am
- Location: behind you.
- Contact:
Who is online
Users browsing this forum: jesse628wallick and 34 guests