public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Emilio Monti <emilmont@gmail.com>
To: Emilio Monti <emilmont@gmail.com>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] eCos Configuration Tool
Date: Mon, 19 Sep 2005 07:44:00 -0000	[thread overview]
Message-ID: <68b1f76405091815136c4440b@mail.gmail.com> (raw)
In-Reply-To: <20050918184248.GA8421@lunn.ch>

Thank you for the information.
First I will give a closer look to ecosconfig.
Emilio


2005/9/18, Andrew Lunn <andrew@lunn.ch>:
> 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 plenty of "open source" projects for "Parser Generator" and
> > "Code Generator" in Java that could form a good basis for a project
> > like that.
> >
> > It could be an advantage also for the GUI.
> > Java mantains portability, like wxWindows, but enances graphics.
> >
> > For the manage of makefiles and cygwin/unix tools there is a good code
> > basis in the eclipse CDT plugins.
> >
> > If there's any project like that I would be happy to help.
> 
> There is no project that i know of.
> 
> 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 think the configtool is more to keep the commercial clients happy
> where the management people have a percieved need for a "friendly GUI"
> when they buy eCos from the companies that give commercial support. I
> don't remember anybody actually contributing patches for the
> configtool, so from an open source perspective, the configtool is
> dead. The RTOS is what people are interested in, not the tools needed
> to configure it.
> 
> I suspect that a java version would similar be dead unless it got a
> maintainer who had a passion to write and maintain it and i also
> suspect there would be little help from the eCos community. However i
> could be wrong, so don't let me put you off from trying....
> 
>         Andrew
>

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

  reply	other threads:[~2005-09-18 22:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-18 22:13 Emilio Monti
2005-09-19  2:32 ` Andrew Lunn
2005-09-19  7:44   ` Emilio Monti [this message]
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     ` [ECOS] " John Dallaway
  -- strict thread matches above, loose matches on Subject: below --
2001-07-19  8:45 [ECOS] " diem.b.dang
2001-07-19 12:10 ` Jonathan Larmour

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=68b1f76405091815136c4440b@mail.gmail.com \
    --to=emilmont@gmail.com \
    --cc=ecos-discuss@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).