[Prev][Next][Index][Thread]

Re: How about this...



>>>>> "Dan" == Dan Guisinger <dan_g@ix.netcom.com> writes:

    Dan> How about add a folder called Start Up on the same drive as
    Dan> the System?  Then we can have it start are most commonly used
    Dan> program right away.

Just make a batch script and you can have that script start up
anything you want.  You can specify a program to run on the command
line, and you can specify documents that such a program should open on
the command line, too.

C:\> executor System:Utilities:Tex-Edit:Tex-Edit "System:Utilities:Tex-Edit:Revision History"

Will fire up Executor and tell it to run Tex-Edit and tell Tex-Edit to
open up the "Revision History" file.

    Dan> And if you don't want it to do that,
    Dan> just hold down Escape.  Also, when is a beta version of the
    Dan> apple editor going to be out.  I know you said at some point
    Dan> that we would be able to edit the apple menu in the future to
    Dan> make it look like what ever we want.

It won't happen until after Hackathon I.  We may not even include that
feature for 2.0 -- it's just a much lower priority task than almost
all the other things we're working on.

    Dan>     Also, are you using a compiler optimized for a pentium?
    Dan> I know it has a vast speed improvement for Pentium based
    Dan> machines, and since the 486 has the same type of pipeline (5
    Dan> stages) it also greatly improves the speed.  I was just
    Dan> thinking that you could really improve the speed of Executor
    Dan> (Hard to beleive to could get any faster than it is :) ).

It wouldn't help us much.  Almost all of Executor's time is spent in
code that Executor itself has created, rather than code created by the
compiler.  Executor dynamically translates 68k to x86 code and also
dynamically builds x86 code to do the blitting to the screen.  The
code that does the translation is already Pentium aware, so there
isn't much to be gained there -- sorry.

	--Cliff
	ctm@ardi.com


References: