New QMK Configurator Beta - Need your help!

[merlin64]

QMK Configurator Updates 1/22/19



Friends, geekhackers, and fellow keeb lovers, lend me your ears! QMK Configurator is undergoing a minor visual update, with a few bigger updates under the hood. We need your help in evaluating our beta before officially pushing it over to config.qmk.fm.

Click here: https://yanfali.github.io/qmk_configurator

Beta Features:

- Keycodes have been arranged in tabular format for easier navigation. No need to scroll up a down hunting for the keycode you need!

- Buttons have biggernd bolder fonts for easier readability.

- Added some color by utilizing some of the community’s favorite keysets! Keyset will show as you populate your keymap. Click on the keysetame to cycle through available keysets.

- Tired of downloading 100 MB+ Source every time you want to edit your keymap.cThere's a button to download just that!

- Last but not the least, when compiling your firmware file, there is a quirky little potato animation showing compile progress.

Things under the hood that have changed
- All new vue2 base configurator application

- component based architecture

- modern javascript

- no dependencies on jQuery

- fast load times, less than 1 second typical

- HTML5 based drag and drop

Things the Beta does not cover
- rules.mk where features such as rgb, backlight, audio reside is still not toggleable.
- Macros


Things you might have missed in the last 6 months
- Support for ARM boards
- Support for boards such as the Tada68 which take .bin firmware files


We now have groundwork done to implement some great new features. Please check it out and let us know what you think by commenting down below. Thank you everyone![/list]

[YiZZo]

wow the new look is awesome. the downloading of the keymap only is a huge plus! Keep up the good work. I'll be sure to test this out when I get home from work later.

are there plans to include modifications to the rules.mk file in the future?

[BlindAssassin111]

Question: Is this supposed to be fully functional as it sits or are they some big things still needed for the beta to function 100%? I was trying to mess with an ARM M0 based board and was met with an error that the M0 isn't supported yet, when I am pretty sure it works with the current configurator(can't check atm as the firmware is having some issue being fixed atm).

Also is there a way to delete layers as a whole? I know if you click on a layer it is enabled and then creates errors during compiling(if you click a layer accidentally and there are empty layers inbetween them Ex. 0 is used, click on 3 and error for 1 and 2)

[merlin64]

wow the new look is awesome. the downloading of the keymap only is a huge plus! Keep up the good work. I'll be sure to test this out when I get home from work later.

are there plans to include modifications to the rules.mk file in the future?

For sure! But it's gonna be a Soon TM kinda thing.

[merlin64]

Question: Is this supposed to be fully functional as it sits or are they some big things still needed for the beta to function 100%? I was trying to mess with an ARM M0 based board and was met with an error that the M0 isn't supported yet, when I am pretty sure it works with the current configurator(can't check atm as the firmware is having some issue being fixed atm).

Also is there a way to delete layers as a whole? I know if you click on a layer it is enabled and then creates errors during compiling(if you click a layer accidentally and there are empty layers inbetween them Ex. 0 is used, click on 3 and error for 1 and 2)

Which M0 board are you talking about? And that layer thing is a good idea, that's tripped me up a few times.

[drashna]

Question: Is this supposed to be fully functional as it sits or are they some big things still needed for the beta to function 100%? I was trying to mess with an ARM M0 based board and was met with an error that the M0 isn't supported yet, when I am pretty sure it works with the current configurator(can't check atm as the firmware is having some issue being fixed atm).

Also is there a way to delete layers as a whole? I know if you click on a layer it is enabled and then creates errors during compiling(if you click a layer accidentally and there are empty layers inbetween them Ex. 0 is used, click on 3 and error for 1 and 2)

I'm guessing that this is for the Ergodox Infinity or Whitefox board. 

If so, the issues with the uGFX libraries, and I believe it's a licensing issue.

[BlindAssassin111]

Which M0 board are you talking about? And that layer thing is a good idea, that's tripped me up a few times.

The upcoming TKC CandyBar, was trying to play with the firmware but it wouldn't work on the new configurator at all but I am pretty sure I used it recently without issue. I said I wasn't able to test be cause there was a small error that showed up in a later commit of the firmware so I can't test until that is fixed.

And please add the layer feature, makes life easier if you accidentally click the wrong layer and especially if you are nearly done with a multi-layer layout and then accidentally click the wrong layer and you now have an error preventing the firmware from compiling and either have to start all over again, or do the work locally(which makes it impossible for those who don't know how or are scared to try it on their own).

[drashna]

The upcoming TKC CandyBar, was trying to play with the firmware but it wouldn't work on the new configurator at all but I am pretty sure I used it recently without issue. I said I wasn't able to test be cause there was a small error that showed up in a later commit of the firmware so I can't test until that is fixed.

Do you mean the "(Firmware size check does not yet support cortex-m0 microprocessors; skipping.)" message?

If so, that's normal. It can't check the firmware size, but it has compiled fine, if you see that.

Otherwise, could you post the error?

[BlindAssassin111]

The upcoming TKC CandyBar, was trying to play with the firmware but it wouldn't work on the new configurator at all but I am pretty sure I used it recently without issue. I said I wasn't able to test be cause there was a small error that showed up in a later commit of the firmware so I can't test until that is fixed.

Do you mean the "(Firmware size check does not yet support cortex-m0 microprocessors; skipping.)" message?

If so, that's normal. It can't check the firmware size, but it has compiled fine, if you see that.

Otherwise, could you post the error?

Hmm...Just tried it again and it compiled without issue, but before it happened 3 or 4 times in a row. I can't remember the exact error at the moment, the message you listed was also there but that doesn't prevent the compiling, all I can remember is it was a different error than what the current configurator showed. So I guess ignore me for now, lol, somehow it doesn't happen anymore and I have no idea why.

[drashna]

Do you mean the "(Firmware size check does not yet support cortex-m0 microprocessors; skipping.)" message?

If so, that's normal. It can't check the firmware size, but it has compiled fine, if you see that.

Otherwise, could you post the error?

Hmm...Just tried it again and it compiled without issue, but before it happened 3 or 4 times in a row. I can't remember the exact error at the moment, the message you listed was also there but that doesn't prevent the compiling, all I can remember is it was a different error than what the current configurator showed. So I guess ignore me for now, lol, somehow it doesn't happen anymore and I have no idea why.
[/quote]

Ah, it was likely an intermittent error, or a bug that was already patched, then.

but feel free to bug any of the qmk staff if you see errors like this.