On Jan 10, 6:59=A0pm, Jonno Downes  wrote:
> On Jan 11, 10:40=A0am, BLuRry  wrote:
>
> > (totally possible to do in the Jace emulator, just requires writing a
> > class that represents that card)
>
> So I've got d/led the code from sourceforge - what do I need to build
> it? It's been about 10 years since I did any java, so I have no dev
> environment set up at all. That's one of the nice things about ruby
> btw - since there's no compile & link stage, all you need on a machine
> to do development is the ruby runtime (which is a one-click install)
> and the text editor of your choice. But if you give some clues I'll
> see if I can get a build working.

Easiest way to play with it is to grab a copy of Netbeans or Eclipse
(I prefer the former, Nick prefers the later)

The source tree structure is a netbeans project, so all you'd have to
do is open the project in netbeans and press F6 (or right-click the
project and select Run) to run the emulator.  You can also set
breakpoints and run it in debug mode if you need to do some low-level
hacking or performance profiling.  I can't (and at not yet want to)
advertise it as a complete emulator until some issues are worked out
-- but as for hacking custom firmware and implementing cards, it's got
that down.

As for your request about the different signals sent on the real
hardware, some of these things are implemented in a very simplified
way in the emulator -- some things are not implemented at all due to
lack of current need.  But that's not to say it would require
rewriting significant portions of the emulator to add such features.

Happy hacking!
-B
--- SBBSecho 2.12-Win32