From: Grant Edwards <grante@visi.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: ECOS - MIPS
Date: Fri, 24 Jun 2005 16:39:00 -0000 [thread overview]
Message-ID: <20050624163912.9519749B81@rivatek.dnsalias.net> (raw)
In-Reply-To: <200506241750.05216.sinany@beko.com.tr>
In gmane.os.ecos.general, you wrote:
> Cuma 24 Haziran 2005 05:08 ös tarihinde, Grant Edwards ?unlar? yazm??t?:
>> In gmane.os.ecos.general, you wrote:
>> > I just mention that eCOS didnt fullfill my needs. The only
>> > thing eCOS provides is using reusable components like the ones
>> > in visual programming languages.
>>
>> Huh? I've no idea what you mean. What are "visual" programming
>> languages? Things like LabVIEW and IBM Data Explorer?
>
> - I said visual programming languages. Not tools! If you say
> "tools" that means you have an idea. This is a contradiction,
> isn't it ? :P
Sorry, I have no idea what that means.
> Some visual programming environments have component based SW
> development, like VB.
The VB with which I am most familiar is Victoria Bitter. After
googling for "VB" I'm guessing you're talking about Visual
Basic?
> You drag and drop components, use them, change them. I just
> wanted to mean that eCOS components are, in mentality, like
> that. I didn't want to say that "eCOS" is bad.
This is all about the configuration tool's UI design? You want
to drag and drop stuff instead of using the tree widget?
> An advantage of eCOS is its components. It includes many
> components. Having components is not a bad idea.It is not new
> also... Isnt it ? Why do you misunderstand me ? May be your
> english is not so good... Go and take courses. I advice you...
Yea, that's it. My English isn't good enough.
>> You probably find it "more usable" simply because it has so
>> many fewer available features. It includes driver models for
>> no peripherals, no networking, no filesystem, and only one
>> scheduler. You should be comparing uCOS to just the eCos
>> kernel with about half of it's available features removed.
>
> - eCOS is much more bigger, it is still groving. There may be
> many commercial products that uses it. But there are OS'es
> that do the same on the embedded world ( May be you will
> misunderstand me again. Let me explain. I mean kernel, not
> components... ). I just wanted to give an example. uCOS is not
> apple and eCOs is not orange. I am not a child that plays
> operating systems on the afternoons. I am not a uCOS fan or an
> anti-eCOS man. I just tried eCOS and saw that it is not really
> configurable. This is my idea. I wish it changes in the
> future...
You're right. My English must not be up to snuff. I'll bow
out of the discussion and let those with better English handle
it.
--
Grant Edwards grante Yow! This is my WILLIAM
at BENDIX memorial CORNER
visi.com where I worship William
Bendix like a GOD!!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-06-24 16:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <W646741726646371119364845@webmail3>
2005-06-22 7:09 ` [ECOS] " K. Sinan YILDIRIM
2005-06-22 10:21 ` Fabian Scheler
2005-06-22 18:28 ` L D
2005-06-23 6:29 ` K. Sinan YILDIRIM
2005-06-23 7:03 ` Andrew Lunn
[not found] ` <200506231102.17394.sinany@beko.com.tr>
2005-06-23 8:07 ` K. Sinan YILDIRIM
2005-06-23 8:34 ` Jerome Souquieres
2005-06-23 9:02 ` Andrew Lunn
2005-06-23 10:27 ` K. Sinan YILDIRIM
2005-06-23 15:28 ` [ECOS] " Grant Edwards
2005-06-24 6:14 ` K. Sinan YILDIRIM
2005-06-24 9:07 ` Nick Garnett
2005-06-24 14:08 ` Grant Edwards
2005-06-24 14:52 ` K. Sinan YILDIRIM
2005-06-24 16:39 ` Grant Edwards [this message]
2005-06-23 16:19 ` [ECOS] " Richard Forrest
2005-06-24 0:04 ` [ECOS] " Grant Edwards
2005-06-24 7:48 ` Richard Forrest
2005-06-23 15:17 ` Grant Edwards
2005-06-24 15:04 Ali, Khurram
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=20050624163912.9519749B81@rivatek.dnsalias.net \
--to=grante@visi.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).