public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "xconq" <xconq7@sources.redhat.com>
Subject: RE: growth agendas and OO
Date: Thu, 20 Nov 2003 12:05:00 -0000	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDIEBNGMAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <20031120113605.20265.qmail@web40902.mail.yahoo.com>

From: Jakob Ilves [mailto:illvilja@yahoo.com]
>
> (Hodgepodge being offered?  That sounds delicious, maybe I
> should consider returning to earth!)

We serve 'em fresh 'n' tasty.  Of course if you've seen "Spirited Away,"
you know what happens when you eat too many of them!

> Having one developer alone doing the OO work probably is a
> bad idea, IMHO.  That person will be a
> bottleneck for the project and the risk is big that the
> person get's fed up with the task or even
> worse, what must not happens do indeed happen: that the
> developer no longer find it fun to develop
> Xconq.

Yes, having only one guy do OO is not a realistic way for migration to
proceed.  The OO paradigm has to be accepted and used by a lot of
people.  I am hoping that by embedding Python into Xconq, and showing
people how it can be used, people will become willing to use it for
various tasks.  Eventually people become "sold" and "hooked" on Python.

> /IllvilJa  (still in orbit ;-)
>
> Having fun where others will not ;-)  (Sorry could not resist
> that one).

Cheers,                         www.indiegamedesign.com
Brandon Van Every               Seattle, WA

20% of the world is real.
80% is gobbledygook we make up inside our own heads.

  reply	other threads:[~2003-11-20 11:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20  2:15 Xconq UI thoughts Stan Shebs
2003-11-20  2:26 ` Brandon J. Van Every
2003-11-20  2:57   ` Eric McDonald
2003-11-20  9:45     ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:49       ` Bruno Boettcher
2003-11-20 10:59         ` Brandon J. Van Every
2003-11-20 11:51           ` Jakob Ilves
2003-11-20 12:05             ` Brandon J. Van Every [this message]
2003-11-20 17:57             ` Jim Kingdon
2003-11-20 17:24       ` Eric McDonald
2003-11-20 17:51         ` Eric McDonald
2003-11-21  1:59         ` altruistic VS 2003 Solution files Brandon J. Van Every
2003-11-21  4:17           ` Eric McDonald
2003-11-21  9:02             ` So let's get right to the point Brandon J. Van Every
2003-11-21 23:14               ` Lincoln Peters
2003-11-22  0:06                 ` Why Eric doesn't like my personal style Brandon J. Van Every
2003-11-23 11:13                   ` Mark A. Flacy
2003-11-23 14:22                     ` Brandon J. Van Every
2003-11-22  0:07                 ` So let's get right to the point Brandon J. Van Every
2003-11-21  2:01         ` growth agendas and OO Brandon J. Van Every
2003-11-20 10:31   ` Xconq UI thoughts Andreas Bringedal
2003-11-20 10:37     ` keys and menus Brandon J. Van Every
2003-11-20 10:58     ` Xconq UI thoughts Bruno Boettcher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OOEALCJCKEBJBIJHCNJDIEBNGMAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).