Author Topic: kArmTI - TI-Nspire emulator with skin (Read 461933 times)

SpiroH · « **Reply #105 on:** June 13, 2012, 03:14:22 pm »

Quote from: cyanophycean314 on June 11, 2012, 09:04:58 pm

I have to say that every time it looks nicer and nicer.

Thanks cyanophycean! Maybe we'll have some more soon.

Quote from: adriweb on June 12, 2012, 04:26:37 am

However, I was wondering : for any update of nspire_emu, will it be "easy" enough for you to adapt your code to use the new nspire_emu ?

Hi, it shouldn't too difficult, unless 'nspire_emu' code suffers a major restructure which i do not anticipate for this type of machine anyway.

Quote from: Wayne on June 13, 2012, 02:05:05 pm

The download link doesn't work

I'm sorry, but for some unknown reason 'filedropper' is either down or refusing people to download?
Pelase, try this link instead: http://www.filefactory.com/file/1kaalg4t0nw5/n/ONspire_v1_rar
BTW Wayne, i've noticed that occasionnaly 'mviewer' does hang! The problem seems to be related to that fact that 'mviewer' doesn't release the stdio. So, sometimes we can't interact with emulator at all, unless the it is restarted. I've been trying to discover why, but so far no luck. Also, this seems to be the ONLY program that from time to time crashes and for which the most of the "image manipulation" key combinations do not work at all (in the emulator)!?. So i do acknowledge that we 'do have a problem' with mviewer...

Regards,

Lionel Debroux · « **Reply #106 on:** June 13, 2012, 03:50:30 pm »

Quote

Hi, it shouldn't too difficult, unless 'nspire_emu' code suffers a major restructure which i do not anticipate for this type of machine anyway.

I think that you should attempt to get the changes integrated to mainline nspire_emu, though

So far, AFAICT, the other third-party GUIs for nspire_emu have bitrotted...

Needless to say, your modified GUI(s, should more than one layout per calculator model be integrated) should be optional. The "programmer" view (raw keyboard representation) should remain available

hoffa · « **Reply #107 on:** June 13, 2012, 04:26:28 pm »

Quote from: fhub on June 13, 2012, 04:20:01 pm

Quote from: Lionel Debroux on June 13, 2012, 03:50:30 pm
The "programmer" view (raw keyboard representation) should remain available
What's the purpose of this raw keyboard representation?

I'd say it's a tiny bit more practical to have a clear tabular view of keys and their status without the eye candy.

hoffa · « **Reply #108 on:** June 13, 2012, 04:58:20 pm »

Quote from: fhub on June 13, 2012, 04:39:27 pm

Quote from: hoffa on June 13, 2012, 04:26:28 pm
I'd say it's a tiny bit more practical to have a clear tabular view of keys and their status without the eye candy.
More practical? What's more practical in this internal layout which neither looks like the original Nspire nor is it a usual QWERTY keyboard that most people use every day.
Ok, if you use the PC keyboard to handle the emulator then it doesn't matter (despite of Nspire keys which have no corresponding PC key), but if you want to use the emulator with the mouse then you have to 'search to death' for every key position.

As far as I'm concerned it's nothing really considerable (hence the "tiny bit"). As long as it is somehow visible what keys are held down I'm be content with it.

SpiroH · « **Reply #109 on:** June 13, 2012, 09:49:01 pm »

Quote from: Lionel Debroux on June 13, 2012, 03:50:30 pm

Needless to say, your modified GUI(...) should be optional. The "programmer" view (raw keyboard representation) should remain available

Salut Lionel,
"Tu veux dire quelque chose comme ça?

Oui, c'est dejá inclus in kArmTI!"

Programmers simply forget about the 'normal' users. They need to have both (or many

) views and not a 'xenophobic' single one! Yep, we could stay all night long discussing which one is best.
Take the one you like most but respect the other's opinion too.

On another key: Here, goes my smallest nspire skin ever (and probably the last one in this series). Has a very small footprint which can be useful for some applications, specially when using together with the keyboard.
The skin can unfold to a view with keys and to a fullblown one with menu too.

ONSpire_V3: http://www.sendspace.com/file/p64sac

Hope some of you will appreciate it,
SpiroH

Jonius7 · « **Reply #110 on:** June 14, 2012, 09:31:18 pm »

Yay! kArmTI has been finally made public! (I was lucky enough to get a pre-release months ago from Spiro

. It has proved immensly useful.

aeTIos · « **Reply #111 on:** June 16, 2012, 09:09:02 am »

Hmm I wonder, why is the key layout upside-down? That can be easily turned imo?

SpiroH · « **Reply #112 on:** June 21, 2012, 12:00:31 pm »

Quote from: Jonius7 on June 14, 2012, 09:31:18 pm

Yay! kArmTI has been finally made public! (I was lucky enough to get a pre-release months ago from Spiro . It has proved immensly useful.

Hi Jonious7, Long time no see, man? Where have you been hanging around? THANKS!

Quote from: fhub on June 16, 2012, 07:57:44 am

After having played around with all your different versions, I'm now back again.

A few comments about your skin proposal:
1. I don't see much use in having a text file (maybe an xml file?) because it implies you need to include the text/xml parser/writer inside your code.
2. Skin-editor: you're bound to have one, unless you want to specify all by hundredths of rects manually yourself.
3. Pc-keys assignments: I don't think they should belong inside the skin. They only depend on the keypad-type really. So, you should handle them independently of the skin. Check my approach.
-----------
Now, about the rest, i'm posting a new release of kArmTI (V1.25).
Gi-nspire:

Some added features:
   1. Support for general skins, i.e. the location of the LCD and of the keys can now be anything. See the included examples.
   2. Facility to specify the calculator-to-pc-keys assignments (at an early stage).
   3. Inclusion of some the 'eye candy' from my already posted simpler versions (SpiroH + OnSpire). Not all of them have been 'ported', though.
   4. Initial Html help
Because I had to make a LOT of modifications to the previous code, this remains a beta-release for people out there to test and be kind-enough to report the bugs and perhaps some positive feedback too

.

kArmTI, v1.25: http://filesave.me/file/18734/kArmTI-v25-rar.html (the download it a bit large (4.5 MB). It includes a few skin examples and the html help. kArmti.exe itself is only 283kb! Hope 'FILESAVE.me' doesn't hang!)

Have some fun,
SpiroH
PS1: New users, please refer to my initial kArmTI post: http://ourl.ca/9360;msg=248808
PS2: I forgot to include the latest skin editor, v1.04. Please find it attached.
PS3: Adding a Simple SkinEditor tutorial, 3rd attachment.

Hayleia · « **Reply #113 on:** June 22, 2012, 02:55:32 pm »

I am sorry in advance if my questions are stupid or if someone already answered, but I really don't know what to do when I launch the exe and this window pops.

I used polydumper and got all the images I need but what do I do with them then ? How do I "give them" to the emulator ?

SpiroH · « **Reply #114 on:** June 22, 2012, 04:06:06 pm »

Quote from: Hayleia on June 22, 2012, 02:55:32 pm

I used polydumper and got all the images I need but what do I do with them then ? How do I "give them" to the emulator ?

Hi Hayleia,
This is my current files layout. Hope it helps. Sytill, if you do not succeed, please scroll back a few posts, other users have had similar problems and have sorted them out.
I'm sure you'll manage it too.

Hayleia · « **Reply #115 on:** June 22, 2012, 04:09:59 pm »

Yay

I managed to make it work. Thanks

But when I do "Save Flash as...", what type of fil is it meant to create ?
I only get one file with no extension and I don't get how to make the emu work without redoing everything

Hayleia · « **Reply #116 on:** June 22, 2012, 04:18:22 pm »

Quote from: fhub on June 22, 2012, 04:15:33 pm

Quote from: Hayleia on June 22, 2012, 04:09:59 pm
Yay
I managed to make it work. Thanks
But when I do "Save Flash as...", what type of fil is it meant to create ?
I only get one file with no extension and I don't get how to make the emu work without redoing everything
The file extension is usually 'bin', so just rename your file XXX to XXX.bin

Ok, but the thing I get is the bin for the OS, right ?
I mean if I rename it to XXX.bin, then when I run karmTI, the line should be the following, is that it ?
/1=Boot1cx.img /F=XXX.bin /K4

SpiroH · « **Reply #117 on:** June 22, 2012, 04:22:33 pm »

Quote from: fhub on June 22, 2012, 01:56:32 pm

Hi SpiroH,
great job your new kArmTI_v25, many thanks for this combinated version including all features of your previous programs.
...

Thanks again Franz.
Skins: I think you are overreacting quite a bit. It's NOT that hard to define a skin. In your case is rather easy really. Just use one of the examples i've provided and drag the rectangles to where you would like. I partially agree that to create one from scratch gives quite a bit of work, but you should be able to use it later as a template. But then again, i guess you seldomly need to that.
Pc-keys: I know what you mean. The question is, is it really worth the time spent? I honestly doubt it (do you a spare mouse?

). Anyway, i'll give it a bit thinking. But using key combinations (e.g. Ctrl+k) will complicate a bit the assignments. Of course it is feasible, no single doubt about that. Do you have any exaustive key-map in mind? Post it, and i'll get back to you when i can.
That's all for the moment,

Hayleia · « **Reply #118 on:** June 22, 2012, 04:24:17 pm »

Yay again, it works perefctly

Thanks both of you for your answers, your patience with me and your hard work on this amazing tool

SpiroH · « **Reply #119 on:** July 02, 2012, 01:53:25 pm »

I'm back with some news:

1. NON-SKIN Keypad (for skin-haters)
. Color markers feedback for keyboard (green) and right-click (blue) and mouse (red).
. Text in blue for the 'right-click (ctrl)' functions: eg. x^2 ==> sqrt

2. QUICKEYS (for keyboard-fans):
A. Improved mapping. It offers quiet a bit more flexibility.

B.I've also tested the 'shift-keys' approach but the gain is very small (only a few extra keys) and most importantly it's much harder to code and debug (this is the main issue).
Anyway, attached is an alpha version of the shift_keys_approach (yet without Quickkeys)

3. GIF IMPROVEMENTS (for movie-lovers

)
. A modless dialog that shows the captured frames progress + preview

. An animated gif preview.

. A new GIF-ColorQuantizer to save GIF pictures without the horrible quantization!

4. A few bugs have been corrected and a few more will surface with time...

SpiroH

Please find attached kArmTI_v26.exe and kArmTI_v27_shift_keys_alpha.exe