Well, if you're not allowed to branch the project, and can only contribute to the main branch, it's not really free code, since the code has restrictions on it. I hope the Cairo team decides to eventually distribute it under a free software license. Has the team considered releasing Cairo under a free software license? Maybe some kind of compromise could be reached, such as releasing the last release under an free software license whenever a new version comes out? That could draw developers to develop for the most up-to-date branch, but still allow for some measure of software freedom so it doesn't look like Cairo is using free software developers as free labor for a non-free software project. I think the MIT license might allow something like this.
I do plan to keep track of Cairo, because it looks like it has the potential to become the best alternate shell for Windows that I've seen yet. I just hope they eventually come to fully embrace the meaning of free software.
I will see if I can get more clarity on this. I think what the original Cairoshell are talking about is using the original brandname / or rebranding the project. I am confident that since the source is open, anyone is free to contribute, share and modify the source.[/quote]
Ill get in contact with Sam and I will give you an update on this. Im pretty sure though that its fine since the updated branch is from Element Software, otherwise they would not allow us to do this.
FORCE wrote:horrible .NET bloat, they should rewrite it in QT4 (king of toolkits) then it can be considered for explorer.
The issue is that it's not written in C/C++, and we also want to stick with a Windows 2000/XP-based Explorer. Cairo couldn't be the default GUI because it doesn't meet the interface guidelines, if you will. If we were to implement Cairo as the default GUI, people would think this was Wine, Linux, or both, and those familiar with using Windows would be confused. Not that Cairo isn't a good program, or that I won't use it when ReactOS and/or Cairo are more stable, but Cairo isn't the path forward for ReactOS.
FORCE wrote:horrible .NET bloat, they should rewrite it in QT4 (king of toolkits) then it can be considered for explorer.
The issue is that it's not written in C/C++, and we also want to stick with a Windows 2000/XP-based Explorer. Cairo couldn't be the default GUI because it doesn't meet the interface guidelines, if you will. If we were to implement Cairo as the default GUI, people would think this was Wine, Linux, or both, and those familiar with using Windows would be confused. Not that Cairo isn't a good program, or that I won't use it when ReactOS and/or Cairo are more stable, but Cairo isn't the path forward for ReactOS.
i agree with you, normal c++ explorer is all we need like on XP
I'm using Cairo as a Aquais Default theme for Aquais OS. (Built in an ROS Technology). I'll release a Beta in July, or August, 2011. and Release in July, 2012. ok.
I'm using Cairo as a Aquais Default theme for Aquais OS. (Built in an ROS Technology). I'll release a Beta in July, or August, 2011. and Release in July, 2012. ok.
I'd like to know how because Cairo doesn't even work without WPF and .NET 3.5, both which do not run on ReactOS.