Hi
The new logo se does not look like reactos any longer
it is to dark and pixel, the balas and constrast in the new
logo is bad, it does not match at all, and it look not prof
have made it. more like a childer. So please revert
the new logo and keep, the old one.
If u look in ros it does not match the constrast or
any think. A logo should not be pixel or constat
does not match. That is exacly in the new logo
u have done MF.
I know it is alot people reactos user and
devloper dislike the new logo.
if u do not revert it, (restore to the old one)
I will do it this weekend.
Magnus Olsen (GreatLord)
ReactOS Devloper
----- Original Message -----
From: "mf" <mf(a)mufunyo.net>
To: <ros-general(a)reactos.org>
Sent: Thursday, May 18, 2006 11:53 PM
Subject: [ros-general] RE: [ros-diffs] [mflyer] 21918: Sorry Ged,but that's
not the Rea ctOS logo.
> > The ReactOS logo is an ugly design.
> Until you manage to get that wonky off-balance thing you prefer to be
> accepted as the official logo, whether it is ugly or not is not
> relevant. There is a procedure for changing established things. Your
> method of just going ahead and changing things without asking is not
> only rude but wrong. If you want to change things, you will have to go
> through me first. If you have a problem with me, you have a problem
> with changing things. So I suggest you consider your options.
>
> > Also, it's far too complex to be used as a start button image and looks
out
> of place.
> It's a bloody orb with wisps (rings) around it. Complex my eye.
>
> > The official Windows logo isn't used on the start button. A neater
version
> is used in the same way.
>
> A "neater version". You mean the shadow? I have employed a similar way
> to make the icon clear at 16x16:
>
> http://img55.imageshack.us/img55/4972/startthingie3yn.png
>
> As you can see, both with Windows and with ReactOS, it's practically
> the same thing. I'm beginning to get the idea you are making arguments
> up for the sake of having arguments in your offence.
>
> > This logo is the original ReactOS start menu logo and should be kept
IMO.
> It's as much a placeholder as the "original" Everaldo icons were.
>
> mf
>
> _______________________________________________
> Ros-general mailing list
> Ros-general(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-general
Aleksey and I thought it would be a good idea to end rumours and write
up an official stance on the topic, so here is a paste from the website,
for those of you that don't read it:
--
The official letter written by project coordinators of these projects
by fireball on 2006-05-18
ReactOS and TinyKRNL projects' official relationship
Prepared by Aleksey Bragin and Alex Ionescu, Project Coordinators.
There is a little information posted officially about TinyKRNL project
and this provides a base for gossip to appear. This short article is
intended to clear up official relations between these two projects.
TinyKRNL is an educational and documentation project which creates
plug-in replacements for various modules of Windows 2003 SP 1
(ultimately replacing the kernel too) and a series of papers ultimately
combined into a book. The methods used for development of TinyKRNL’s
modules source code involve all possible methods of achieving the end
result of having a 100% compatible (or even identical) result. Reverse
engineering is one of them (mainly so-called ‘dirty’ way, for further
reference see Wikipedia’s article about clean room reverse engineering
vs. dirty room reversing).
Unfortunately, due to copyright laws and other law-related stuff,
ReactOS (which aims at commercial usage too) can not directly utilize
methods of development like dirty reverse engineering, and thus ReactOS
can not share all code with the TinyKRNL project like we are sharing
code with WINE.
However, there are some very useful exceptions:
* Firstly, all interfaces are shared. This gives ReactOS project an
unbeatable level of compatibility and legal freedom too (interfaces can
not be copyrighted).
* Secondly, the great thing is that TinyKRNL will provide the most
complete documentation of the most recent and technically advanced
version of a released NT-famility operating system – Windows 2003 SP1.
ReactOS developers can use this documentation for reference when
creating a clean implementation of functions or improving already
developed code.
* Thirdly, any code in TinyKRNL which respects the ReactOS policies
regarding development can directly be added into ReactOS, as well as any
build tools or 3rd-party files.
For more detailed information regarding TinyKRNL project, please look at
http://www.tinykrnl.org. We also encourage you to signup on the TinyKRNL
. We also encourage you to signup on the TinyKRNL development Mailing
List by sending a blank email to devel-subscribe(a)tinykrnl.org as well as
joining the #tinykrnl channel on the same IRC server as #reactos; many
of the ReactOS developers and users are usually present and discuss
interesting and challenging kernel issues as well as general off-topic chat.
--
mflyer(a)svn.reactos.org wrote:
> Sorry Ged, but that's not the ReactOS logo.
The ReactOS logo is an ugly design.
Also, it's far too complex to be used as a start button image and looks out
of place.
The official Windows logo isn't used on the start button. A neater version
is used in the same way.
This logo is the original ReactOS start menu logo and should be kept IMO.
************************************************************************
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:postmaster@exideuk.co.uk> 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
Can we agree on the following goals for 0.3.1 ?
- NDK
- Cache Manager Rewrite
- VMware Tools
- Ext2
It would mean that we would release 0.3.1 very closely after 0.3.0.
Maarten Bosma
Steven Edwards wrote:
> On 5/11/06, Murphy, Ged (Bolton) <MurphyG(a)cmpbatteries.co.uk> wrote:
> > The Wine syncs aren't quite as simple as Gé made them look.
> I think we took
> > them for granted back when Gé was doing them.
> > IIRC, comctl32 still needs doing. Last time it introduced
> regressions and
> > was reverted.
>
> I have offered to sync up a bunch of changes for the 0.3 cycle. I'm
> going to start doing this Friday evening for the dlls that are a 100%
> drop-in. There are a few other things that could be updated as well in
> advapi32, kernel32, etc as well as new regression tests. I expect its
> going to take me a while to do it all and make sure there is no
> regression.
Gé has a great awk script which automates a vast majority of the process,
including the laborious task of generating the logs/credits.
If he isn't around today, I can forward a copy on to you later.
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:postmaster@exideuk.co.uk> 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
Alex committed the NDK today, so I went ahead and branched 0.3.0 at
the previous revision. Aleskey and I decided that the NDK and CC
patches can go in trunk whenever they are ready, for inclusion into
0.3.1. 0.3.0 is still in need of bugfixing and regression testing.
Therefore, we are going to leave the 0.3.0 branch open to
development for a bit before we release RC1. Please discuss any large
changes on the list before commiting to the branch. I don't care of
the branch stays open for a month, as long as it's a good release in
the end.
Thanks for all your hard work,
WD
--
ReactOS is a hub, follow the spokes and you'll
immediately find absolutely everything you need
to know about Windows. ReactOS is not just
software, it's people.
kjk_hyperion