WP43 Alternative key layout --> C43

[Jaymos]

There is only one way to know if it will work, and that's to try it.

Send me the files as soon as possible, I'll try to compile them.

I sent source in PM.

Will report back here.

J

[Jaymos]

The last key changes proposed by Dani, and debated extensively today.

R.BR to [g] [CursorUp], REGS
B.BR to [g]CursorDown], FLAG.V
VIEW to [f] [7],
HOME to [g] [7],
CNST to [f] [8].

I think it is well worth the change, even with the best-thus-far "placeholder" labels REGS and FLAG.V.

The "cost" is that HOME does not sit on the prime shift-Dn location any more. I liked that, but this is good, and it does clean up the layout a bit.

Apart from that, I think the two viewers ought to be on prominent places which it is now.

[Dani R.]

I made a printout in the same size as the DM42. Then I put the DM42 next to the printout.


So...

Code: Select all

I like it, I like it, I really like it a lot. 
Nothing to complain about. 
Of course, there might be one or the other exchange, or changing names. 
Even icons may be found or created. 
From this point it would amaze me if there were even bigger deviations.

Good job Jaco!

[Dani R.]

LOOP and TEST are set to [g], STK to [f]. Even if STK were a bit more away from the program group, how would the exchange of ADV and STK affect? ADV and EQN on the same button, PROB and STK on the same button, which is not wrong.

And as working label, FL.VR instead of FLAG.V?

[Jaymos]

STOP PRESS

WP43C Emulator user interface test


Thanks to Patrick, who recently joined the group and offered to compile a snapshot of the emulator on Windows, I have the user interface that we developed, for test.

Linked is the emulator Windows executable that he compiled for us. I call it our pre-pre-pre-alpha version of a new dysfunctional user interface on top of another pre-alpha project's old user interface. All we can guarantee is that it does not work as expected

It loads up the emulator on my Windows 10 laptop, which is not configured as a WP43s development system and should therefore work for everyone.

Let us know if it does not run on a clean Windows machine. Unzip the files into a folder, acknowledge all hiccups of the unknown exe file that is not recognized by your pc, accept that it will break your machine beyond repair as they claim and test it if you are brave.

http://cocoon-creations.com/download/wp ... lpha01.zip

edit:
ps. There is a readme file stating how the underlining/shading of shifted labels can be changed.

[Jaymos]

LOOP and TEST are set to [g], STK to [f]. Even if STK were a bit more away from the program group, how would the exchange of ADV and STK affect? ADV and EQN on the same button, PROB and STK on the same button, which is not wrong.

And as working label, FL.VR instead of FLAG.V?

Hi Dani,

STK:
I do not like this proposal. Yes, I agree that STK is not perfect where it is. But it is close to [R/S] which is the centre for the programming group.

I have arranged it with [9], [/], [x] & [-] having advanced math functions on shifts. (Recently we move [FIN] away from [-] for good reason, to be in the main CALC group top 3 lines)(The main reason I moved it is I recognized that even though I don't use TVM, it will help many people who do for it to be more visible).

STK is not MATH, but programming, but it is on the left side of [-] closer to [R/S], which is good.

Putting STK next to PROB would not solve a problem, it would just shifts it to [x], which is neither good nor bad.

No advantage, so it can stay I think.

FLAG.V:
I don't like FL.VR as it focuses on "viewer" in the same way that B.BR focuses on the "browser" more than the "flags" part.

I like REGS as it ONLY refers to REGISTERS.
I like FLAG.V as it mainly refers to FLAGS, but I changed it to FLAG, as there already is a FLAGS label on [f][6], and the V makes it look a bit more different to FLAGS.

edited last para

[Dani R.]

Let us know if it does not run on a clean Windows machine. Unzip the files into a folder, acknowledge all hiccups of the unknown exe file that is not recognized by your pc, accept that it will break your machine beyond repair as they claim and test it if you are brave.

I think, GTK3+ has to be installed.
In my case I also have to copy
libpng16-16.dll and
zlib1.dll
from the GTK3+ installation directory into the directory, where wp43s.exe is unzipped.

I've already seen some funny behavior...





Content of the original README.md with the link to GTK3+
==================================================
# Windows 64 bit binaries
This binary is provided for your convenience.

You must install the latest GTK3+ libraries. If you do not already have them: download and install the latest release of the gtk3-runtime (not gtk2-runtime) for win64 here https://github.com/tschoonj/GTK-for-Win ... r/releases

Install or re-install the WP43S_StandardFont.ttf font. The WP43S_NumericFont.ttf font isn't needed.
Copy wp43s.exe in a new or pre-existing directory.
Copy dm42l.png, dm42lshort.png and wp43s_pre.css from the root of this gitlab project to the same directory
If there is a backup.bin file in your already existing directory: delete it

Run wp43s.exe and enjoy.
==================================================

[Dani R.]

LOOP and TEST are set to [g], STK to [f]. Even if STK were a bit more away from the program group, how would the exchange of ADV and STK affect? ADV and EQN on the same button, PROB and STK on the same button, which is not wrong.

...

No advantage, so it can stay I think.

No problem at all, not every try can be a hit.

And as working label, FL.VR instead of FLAG.V?

FLAG.V:
I don't like FL.VR as it focuses on "viewer" in the same way that B.BR focuses on the "browser" more than the "flags" part.

I like REGS as it ONLY refers to REGISTERS.
I like FLAG.V as it mainly refers to FLAGS, but I changed it to FLAG, as there already is a FLAGS label on [f][6], and the V makes it look a bit more different to FLAGS.

edited last para

What I dislike a little is that the yellow icon in the simulator is pressed a little far to the left.

I've tried an icon and I'm sure you can get a graphical solution. But at the moment I don't know what size an icon can be, so that it can be used in a documentation and especially in a template for printing.

[Jaymos]

Let us know if it does not run on a clean Windows machine. Unzip the files into a folder, acknowledge all hiccups of the unknown exe file that is not recognized by your pc, accept that it will break your machine beyond repair as they claim and test it if you are brave.

I think, GTK3+ has to be installed.
In my case I also have to copy
libpng16-16.dll and
zlib1.dll
from the GTK3+ installation directory into the directory, where wp43s.exe is unzipped.

I've already seen some funny behavior...





Content of the original README.md with the link to GTK3+
==================================================
# Windows 64 bit binaries
This binary is provided for your convenience.

You must install the latest GTK3+ libraries. If you do not already have them: download and install the latest release of the gtk3-runtime (not gtk2-runtime) for win64 here https://github.com/tschoonj/GTK-for-Win ... r/releases

Install or re-install the WP43S_StandardFont.ttf font. The WP43S_NumericFont.ttf font isn't needed.
Copy wp43s.exe in a new or pre-existing directory.
Copy dm42l.png, dm42lshort.png and wp43s_pre.css from the root of this gitlab project to the same directory
If there is a backup.bin file in your already existing directory: delete it

Run wp43s.exe and enjoy.
==================================================

Copy dm42l.png, dm42lshort.png and wp43s_pre.css from the root of this gitlab project to the same directory

You must use the dm42l.png and wp43s_pre.css from the emulator distribution zip file. They contain the dots on screen, and the shading instead of underlining on screen. If you use the ones from the standard project, it will look like the WP43S.

[Dani R.]

I think, GTK3+ has to be installed.
In my case I also have to copy
libpng16-16.dll and
zlib1.dll
from the GTK3+ installation directory into the directory, where wp43s.exe is unzipped.





Content of the original README.md with the link to GTK3+
==================================================
# Windows 64 bit binaries
This binary is provided for your convenience.

You must install the latest GTK3+ libraries. If you do not already have them: download and install the latest release of the gtk3-runtime (not gtk2-runtime) for win64 here https://github.com/tschoonj/GTK-for-Win ... r/releases

[...]
==================================================

You must use the dm42l.png and wp43s_pre.css from the emulator distribution zip file. They contain the dots on screen, and the shading instead of underlining on screen. If you use the ones from the standard project, it will look like the WP43S.

The original README.md does not know WP43S.
But it contains the link to GTK3+.

I think the GTK3+ runtime needs to be installed, the wp43s.exe calls to libcairo-2.dll, libgdk-3-0.dll, libgmp-10.dll, libobject-2.0-0.dll and libgtk-3-0.dll.