-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 31 March 2002 16:04, you wrote:
OK. I'll wait... a little impatiently, but I'll wait.
Some commentary, though, on the subject of a logo.
As I understand it, Palm purchased BeOS. Therefore, they own BeOS, lock,
stock and barrel... this includes the trade name BeOS. I wonder where we
stand on legal issues? This is something we ought to settle before someone
designs a logo using the BeOS trade name that we cannot use.
One other item. This is only my opinion, but I really hate Tux, the penguin
logo for Linux.. I also hate Abby the ant, the logo for Abiword word
processor. I could go on ad nauseum, but you get the idea.
What is it about stuffed animal type cartoon animal's? Take a look at
Microsoft's logos... none of them are cute little critters. Few of the more
successful software packages use anything like that. They are generally
simple graphic designs
Not to toot my own horn, but take a look at my own efforts on the opening
page of my webzine: http:www.thegreenbayweb.com. I used the Intel 386
processor and the 387 co-processor in my logo because it was the first true
multi-processor in general circulation... also, incidently, the lowest level
processor that Linux can run on. Linux was then the only viable alternative
to Windows 95 available... at least as far as I knew. I chose the color
green, again, as a retro attempt. Those of you here who are old like me may
rember the old green monitors that things like the Televideo 608 generally
came with. I used an Old-English type font to emulate the printed newspaper
titles that I hope to replace with my webzine concept. My hope is to expand,
change the format a bit and put the Green Bay Press Gazette out of
business.... hey, I can dream, can't I?
A logo should say something about the item or company it represents. If we
use a cute little cartoon bee, what are we saying about Open BeOS?
I guess I am a proponant of more serious-looking logos. Open BeOS should be
sharp, efficient, and businesslike. If we are going to challenge Microsoft
as well as LInux and BSD, our OS must be all that and more. The logo should
reflect that.
Now, if I offended anyone's efforts, please remember that I have yet to see
any of your work due to server problems... but let the flaming begin anyway,
I invited it!
Dale
> The forum is now on a free webhost, but soon it'll move to a pay one... So
> i guess the problems will (or should) be solved.
>
> debro
> ----- Original Message -----
> From: "Dale Raby" <daleraby@xxxxxxxxxxxx>
> To: <openbeos-cdt@xxxxxxxxxxxxx>
> Sent: Sunday, March 31, 2002 6:56 PM
> Subject: [openbeos-cdt] Re: Design Stuff ... and more
>
> > debro@xxxxxxxxxxxxxxx wrote:
> > >http://openbetalk.host.sk
> > >
> > >Check out the forum!
> > >
> > >debro
> > >
> > >----- Original Message -----
> > >From: "David Goodrich" <goodrich@xxxxxxxxxxx>
> > >To: <openbeos-cdt@xxxxxxxxxxxxx>
> > >Sent: Friday, March 29, 2002 8:24 PM
> > >Subject: [openbeos-cdt] Re: Design Stuff ... and more
> >
> > I have been unable to register, login, or view any of the topics on the
> > CDT forum. It takes about five minutes just to load the index page with
> > a 56K modem, and when I try to view any of the topics or hit any link
> > within this page, my browser simply times out.
> >
> > Is this a common problem?
> >
> > If it is, I may have a solution:
> >
> > http://www.thegreenbayweb.com/forums
> >
> > This is my domain. There are two other websites there in addition to
> > mine, and, so far as I am aware, no other forums. The server has a
> > broadband cable connection and the other tennants don't seem to be
> > drawing large numbers of visitors... or at least I seldom seem to have
> > problems logging in.
> >
> > I don't know how this would work or if there are requirements I am
> > unaware of, but if it would help, I will be happy to create an Open BeOS
> > forum on this BBS for us.
> >
> > Any comments?
> >
> > [dale's signature]
> >
> > Dale A. Raby
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8p5FF+fFNwqPnDWERAtwzAJ4whzXwM+13m+FE8VnEykgoFmajdACgqDV2
5wqjhm73ybBAYO3L/CTQAz4=
=nAdC
-----END PGP SIGNATURE-----
