Arwinss : Alternative names + logo request

[fred02]

As per chatroom discussion, Sangria, since it's Wine with added stuff.

Ummm, it is more the other way around: an OS with Wine added on top of it. So what are the cocktails with added wine?

[igorko]

Guys. Just pay attention. We don't need new name for OS. We need new name for SYBSYSTEM.

[okktaviuz]

Blackfox

[Black_Fox]

^ That's a nice proposition, but I'd rather you didn't

"hey, I just bought a nice Bragin Cayenne Turbo"

Good for you! But still less awkward than installing Doors on Windows.

[sh4ring4n]

Guys. Just pay attention. We don't need new name for OS. We need new name for SYBSYSTEM.

What about Reactwine? It sounds like a subsystem, like libpurple, or winelib.

[Pisarz]

Maybe something similiar to word "Alternative" like...

"Alternatica"?

[zed260]

yeah blackfox sounds like a cool os name

[Smiley]

I would prefer a name from an animal like... tasmanian devil

[Lone_Rifle]

Why an animal?

[fred02]

Why an animal?

Indeed. If I got this part right, fireball liked the idea of continued beverages allusions.
WineNT

[Smiley]

Why an animal?

Many open source projects use an animal for name or logo. I took the idea for the name from TortoiseSvn

[unxed]

WINX: Winx Is Not X11-based (like Wine Is Not an Emulator in WINE)

As fireball declared, X11 is the worst part of WINE's architecture. ARWINSS does not depend on it, so why not to stress this fact in the project's name? It also contains "WIN" from "WINE" and "WINdows". It also can be interpreted as X(cross)-platform windows api implementation. Other interpretation is WINe eXtended.

Another try: Wintage. English word vintage means the process of picking grapes and making wine. "NT" inside the name represents NT architecture, and "age" shows that the project is not a newborn, but is already stable enough and is based on mature reactos.

=)

[ironek69]

Maybe one day I will be chosen one;)
[ external image ]
[ external image ]

[X512]

As fireball declared, X11 is the worst part of WINE's architecture.

Yes X11 is ancient, huge and slow, but win32k is much worse. It's very unstable and it is hard to debug it, because it lives in kernel. win32k is in development about 10 years without success. I don't offer to use X11 in ReactOS, but move gui in userspace. Development process of gui server much easier, beacuse it is usual application and can be easily debugged. You can start server on stable os(Windows XP for example) and debug it. Gui server haven't serious speed problems. Look for BeOS for example.

Sorry for offtop.

[Smiley]

As fireball declared, X11 is the worst part of WINE's architecture.

Gui server haven't serious speed problems. Look for BeOS for example.

This is incorrect. In NT3 version of windows the whole windows sever lived in csrss but it was decided that such an approach has serious speed problems and that's why in NT4 it was moved in kernel space. If this wasn't done people would whine all over the place about ms oses that are bloated and slow....