Re: Scripple ][

[BLuRry <brendan.robert@gmail.com>]

On Jun 23, 12:12 pm, BLuRry <brendan.rob...@gmail.com> wrote:
> On Jun 23, 11:38 am, sicklittlemonkey <nick.westg...@gmail.com> wrote:
>
> > Well, somebody had to do it ... Apple ][ emulation in Javascript.
> > It's a bit of a hack, and buggy, and not really useful either.
> > Nevertheless, thanks to the magic of Google Web Toolkit:http://scripple-2.appspot.com/
>
> Hey, ? "Hello" was working again!  Cool!  I noticed that inverse video
> doesn't yet though.
>
>
>
> > Notes:
> > - Type in the input box indicated - and hit enter a few times first
> > - Unfortunately I'd have to recommend IE at this stage
>
> Noooooooooooooo!!!  :-D
>
> > - Firefox and Chrome work but there is a scrolling (table) bug to
> > squash
>
> Chrome is going to have the best JS performance of the bunch, so I've
> read.
>
> > - It's 48k, text-only, no disk or other hardware, just the DO-F8 ROMs
>
> E000G goes back to basic alright...  No softswitches other than
> keyboard though, is that right?
>
> > - Entering the monitor with call-151 is probably the most fun
>
> > If anyone wants the source, email me. It's a Java project in Eclipse.
> > I'll get around to uploading it somewhere eventually.
>
> > Cheers,
> > Nick.
>
> Side note, I was able to crunch the javascript with Memtronic's
> cruncher down to 28kb using the "hardcore" setting.  You might only
> have to break the JS into two parts if you want to go that route.
>
> Neat stuff, Nick!  Let me know if you need any ideas of how to
> implement graphics with a canvas object (or just cheat and make a
> table with 280x140 pixels in it...)  Javascript is too slow to have a
> full screen refresh in higher graphics modes, you might want to borrow
> the JACE listener-based approach for updating graphics -- such as
> having 4 divs that you flip between depending on what graphics mode is
> active.  I'd be happy to mock that up in a few weeks, time
> permitting.  I'm pretty okay at DHTML.
>
> -Brendan

On another one of the javascripts, I got 63% compression -- took 16
minutes in firefox, only 6 minutes in Chrome, but Chrome needed a lot
of babysitting to keep the javascript running (freeze warnings).
Still didn't test the compressed code to see if it worked or not, but
I've had pretty good luck with Memtronic's cruncher before against
some relatively complex code.

-Brendan