public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <jld@ecoscentric.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: eCos Configuration Tool
Date: Mon, 19 Sep 2005 15:59:00 -0000	[thread overview]
Message-ID: <432ECD26.4090203@ecoscentric.com> (raw)
In-Reply-To: <432E75B3.1040508@zurich.ibm.com>

Andrew Lunn wrote:

> On Sun, Sep 18, 2005 at 07:59:33PM +0200, Emilio Monti wrote:
>
>> Is there any plan to convert the "eCos Configuration Tool" in Java ?
>> It would also be usefull to better integrate the eCos configuration
>> in Eclipse.

There are no such plans at present. While I would like to see the eCos
Configuration Tool more closely integrated into the Eclipse workbench,
re-implementation of the host tools has never been high on the
maintainers' list of priorities.

> My impression is that none of the maintainers actually use the
> configtool. At least i don't use it, and always give debug
> instructions using ecosconfig. The other maintainers are also mostly
> unix people who like CLI programs and so use ecosconfig all the time.

I, for one, use the eCos Configuration Tool. I find that the GUI offers
a better overview of the configuration space. Many of my colleagues do
prefer ecosconfig. It really is a matter of personal preference.

John Dallaway
eCosCentric Limited

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      parent reply	other threads:[~2005-09-19 14:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18 22:13 [ECOS] " Emilio Monti
2005-09-19  2:32 ` Andrew Lunn
2005-09-19  7:44   ` Emilio Monti
2005-09-19  9:30   ` Andrew Voelkel
2005-09-19 12:54   ` Dirk Husemann
2005-09-19 14:37     ` Andrew Lunn
2005-09-19 15:59     ` John Dallaway [this message]

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=432ECD26.4090203@ecoscentric.com \
    --to=jld@ecoscentric.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).