Stefan :



Anyway, news on TI-Planet is here (french + english) : http://tiplanet.org/forum/viewtopic.php?f=43&t=10379

Yes (for minor reasons grrrrr ).

However, having the computer software 3.2 will not do anything bad as it doesn't have anything to do with your calc's OS.
Just like before, when it asks for updating your calc, decline. (you can even firewall it to block in/out connections )
And it still works the same for installing/upgrading Ndless.

Pretty much the only new thing (except bringing the 3.2 OS's changes) is the Lua SDK built-in.

Anyway, you can actually download TINCS 3.2 and copy the 4 .jar libs needed by nRemote and put everything in a folder of yours (nRemote +libs) so you wouldn't need anything else anyway (except TINC[L]) installed). The libs required are :   commproxy.jar, navnetcommproxy.jar, navnet.jar and upgrade.jar

Would this work on my nspire cx os 3.1.0? nremote never detects my calc

I have never experienced any issues with nRemote (as long as you have TINCS 3.2 installed), for any calc OS. Tested on any model and multiple OS 3.x.

Do you have some error log ? (launch it in terminal :     java -jar [path_to_nRemote.jar]   )

Anyway, once you get nRemote working, yes, the rest would follow

Congratulations !

You did more than me on this side, though, so credits to you for the web browsing \o/

But indeed, I will try to integrate more nice stuff (than calc-to-calc chatting and IRC, which both work well, btw) into nRemote soon
It would be good I guess to have separate versions tho, one "clean" with only the remote one, for teachers probably, and one more community oriented with all kond of fancy stuff

Nice !

Although for Lua scripts the built-in editor is there for that (in TINCS 3.2, I mean)
But for people who don't have it, it's definitely a good job.

By the way, what language is this written in ? Any chance it would compile on other platform ?



EDIT : It looks like there are still some   "   chars here and there ?  (in the example lua file)

This is not good; this provides another reason for TI to lock the Nspires down.

I would have agreed if it were done on production Nspires and as much publicized too but indeed, as critor said, it's only for prototypes, which are extremely rare. So if anything, that would make TI smile, maybe. Hardware protections are on Production models that make the required modifications impossible.

It's platform.window:invalidate(), not platform.window.invalidate()

Here is a cleaner code.
Also, the reason(s) why it's not working the same on-calc is becuase the computer forces the refresh of the screen, but you have to call it yourself by calling [lua]platform.window:invalidate[/lua]
Also, since you want the game to be always running (the AI), call it in a timer. (See code)

I also made the duck images transparent (thanks to http://bwns.be/jim/sprite.html )

Quick note for the optimizations :   when you see stuff like    "a = (b>1) and 3 or 2" it's the same as : "if b>1 then a = 3 else a = 2 end"

And ... I recoded the AI (quickly)

Cleaner Code with properindentations, separations of events and functions, init code at the end.
platform.apilevel = "1.0"

-----------------------
------ Constants ------
-----------------------

inc = 5 -- image movement increment
bg_gap = 50 -- background gap in coord-- X


-----------------------
------   Events  ------
-----------------------

function on.paint(gc)
    -- Paint background
    gc:setColorRGB(0, 0, 0)
    gc:fillRect(0, 0, ww, wh)

    gc:drawImage(img_background, bg_gap, 0)
    if alive then
        gc:drawImage(img_duckAlive, dx, dy)
    else
        if dy + duck.h < 194 then
            gc:drawImage(img_duckDead, dx, dy)
        else
            gc:drawImage(img_dog, dx, dy-duck.h)
        end
    end

    gc:setColorRGB(255, 255, 255)
    gc:drawString(msg, 0, 0, "top")
end

function on.resize(width, height)
    cursor.set("translation")
    cursor.show()
    ww, wh = width, height
    platform.window:invalidate()
end

function on.mouseDown(x, y)
    if between(dx, x, dx + duck.w) and between(dy, y, dy + duck.h) then
        shot()
    else
        miss()
    end
    platform.window:invalidate()
end

function on.escapeKey()
    init()
    platform.window:invalidate()
end

function on.timer()
    AI()
    platform.window:invalidate()
end

-----------------------
------ Functions ------
-----------------------

function init()
    dx = 100
    dy = 50
    dirX = 1
    dirY = 1
    alive = true
    x = 0
    y = 0
    msg = ""
end

function between(a, x, b) -- Checks if "x" is between range [a,b]
    return (a <= x) and (x <= b)
end

function AI()
    if alive then
        dx = dx + dirX*inc
        dy = dy + dirY*inc
    elseif dy + duck.h < 194 then
        dy = dy + inc
    end
    
    if dx <= bg_gap then dirX = 1 end
    if dx >= ww-duck.w then dirX = -1 end
    if dy <= 0 then dirY = 1 end
    if dy >= 170-duck.h then dirY = -1 end
end

function shot()
    alive = false
    msg = "Shot !"
end

function miss()
    -- Determine what happens if you missed a shot
    msg = "Missed !"
end


-----------------------
------   Init:   ------
-----------------------

-- images --

img_dog = image.new(dogSRC)
img_duckAlive = image.new(duckAliveSRC)
img_duckDead = image.new(duckDeadSRC)
img_background = image.new(backSRC)

duck = {
    h = image.height(img_duckAlive), -- 30 px
    w = image.width(img_duckAlive) -- 37 px
}

init()
timer.start(0.05)