[Prev][Next][Index][Thread]
Re: Code Warrior?
>>>>> "Ryou Seong-Joon" == Ryou Seong-Joon <stjohn@hnc.co.kr> writes:
In article <31417330.1F1B@red.hnc.co.kr> Ryou Seong-Joon <stjohn@hnc.co.kr> writes:
Ryou Seong-Joon> Clifford T. Matthews wrote:
>> >>>>> "James" == James Yang
>> <jamesy@microcosm.resnet.cornell.edu> writes: In article
>> <slrn4jv55d.5us.jamesy@microcosm.resnet.cornell.edu>
Ryou Seong-Joon> jamesy@microcosm.resnet.cornell.edu (James Yang)
Ryou Seong-Joon> writes:
>>
James> In article <313f5f42.3813807@205.198.114.6>, Jerry Wen
James> wrote:
>> >> Has anyone got this program? If so, does it run under >>
>> Executor? Which ver of code warrior did u use?
>>
James> It installs, but does not start. One of those
James> unimplemented trap errors, I think.
>>
James> CodeWarrior 8.
>> C compilers are low priority before Executor 2 ships, but
>> there's a bit of demand from within ARDI to get CodeWarrior
>> and/or Think C running nicely under Executor for internal use.
>> As such we'll take a good look at them after E2 is in beta.
>>
>> --Cliff ctm@ardi.com
Ryou Seong-Joon> I think the most importance programs to be
Ryou Seong-Joon> supported by executor is development tools. (for
Ryou Seong-Joon> mac and for executor.) This way, executor can
Ryou Seong-Joon> get it's own application and it can be something
Ryou Seong-Joon> that goes beyond mac's application.
We will be supplying some compiler tools after E2 ships.
Ryou Seong-Joon> If there's a development tools and developing
Ryou Seong-Joon> document available for executor, I will expect
Ryou Seong-Joon> some 3rd party(?) developers doing the
Ryou Seong-Joon> followings for executor
Ryou Seong-Joon> 1. type-1 and true-type font drivers for
Ryou Seong-Joon> executor. (Now there's so much information
Ryou Seong-Joon> available for these fonts. Especially public
Ryou Seong-Joon> Type-1 font rasterizer source is all around.) I
Ryou Seong-Joon> really will be happy to use either shareware
Ryou Seong-Joon> version of this kind on executor. (Of course not
Ryou Seong-Joon> needed in real mac) I am sure that ATM will never
Ryou Seong-Joon> run on executor since it touches inner soul of
Ryou Seong-Joon> Operating systems using undocument stuffs.
I suspect ATM will run fairly soon after E2 ships. We have already
spent a bunch of time making sure that our internals look like Mac
internals. I'm sure we've made some mistakes here and there, but I'll
be surprised if we can't get ATM to go.
Ryou Seong-Joon> 2. Some desktop accessories which is never needed
Ryou Seong-Joon> in real mac. But will be happily used with
Ryou Seong-Joon> executor users.
Ryou Seong-Joon> 3. Some Utilities developed solely for executor.
Ryou Seong-Joon> For example, Ram Doubler for Executor/DE! which
Ryou Seong-Joon> will enable my machine more happier. And some
Ryou Seong-Joon> networking drivers that will work with executor.
It's not really that easy. Ram Doubler isn't too useful when only one
app can un at a time and isn't necessary on systems with decent
virtual memory subsystems (Windows NT, OS/2, Linux, NEXTSTEP, maybe
Windows '95). Networking drivers have nothing to connect to until we
implement networking and would be difficult to write without a
thorough knowledge of Executor internals.
Ryou Seong-Joon> Don't forget OS/2's lack of native application.
Ryou Seong-Joon> Although it can run DOS, Windows application so
Ryou Seong-Joon> nicely, it's not very successful in retail
Ryou Seong-Joon> market. I think executor should get some support
Ryou Seong-Joon> for other developers also.
I agree, but in order to do that we have to have enough engineers so
that we can answer developer's questions. Right now we're being run
ragged trying to keep on top of c.e.m.e., bugs@ardi.com,
questions@ardi.com and still get BleedingEdge (and soon the beta)
releases out quickly. When E2 is shipping we'll be able to double our
staff which will actually more than double the amount of engineering
hours we have because right now many engineering hours are spent on
silly things like system configurations, backups, etc.
--Cliff
ctm@ardi.com
References: