feature requests after a season sailing with KIP

[motamman]

These aren't issues so much as requests/ideas after using KIP for one season on the water. I am now working on next season's iteration of my boat brain and a fistful of new sensors.

In no particular order or importance:

1. Import and export buttons for quickly moving design JSON files back and forth between different signal k servers.
2. More color options in general. A custom color palette?
3. A font size override?
4. Center, left, and right; top, bottom, and middle alignment?
5. Remove unitless as a label and make it blank or a custom label.
6. The option for all text and numbers to reflect the corresponding notification zone.
7. The option for the radials and linear gauge bars to reflect the corresponding notification zone.
8. An LED metaphor that can take bool values and turn them on and on (with customizable colors, of course.)

This is a super presentation layer.

Many thanks,
Mo

[EdKok]

1. Is possible via "Configuration" -> "Settings" -> Tab "Storage".
   I'm not completely happy with it, but does work. Not happy because a small mistake can destroy the json file. That is why I make manual backups these days before fiddling with KIP.
   2, 3, 4 I agree
2. Is possible with "Boolean Control Panel" as the widget and "Type = Indicator".
   Nice, but lacks alignment (as in 4.)

May I add:
9. Possibility to Cancel out completely of configuration without writing to json.

[motamman]

Thanks, EdKok. I completely missed the indicator. It is nice but for the aforementioned styling limitations.

I know how to move files back and forth from local to server but not from server to server. I can manually copy files, but it would be nice to click a button and save them to another location (and the inverse at the other end to load a file).

[godind]

Follow up!

1. Import and export config: done.
2. More color options in general: now 9 colours
3. A font size override: to make everything responses, labels are dynamic canvas and not a typical html font.
4. Center, left, and right; top, bottom, and middle alignment? We have to account for units label and all type of widgets. Better to stick all labels at the top. Could do center and right but honestly for the trouble, not sure it's of great value.
5. Remove unitless as a label: units should be fixed in SK meta first.
6. The option for the radials and linear gauge: done
7. N/A
8. Cancel config changes: done

All part of v3. Can we consider this done are more
Points should be considered?

[motamman]

Thanks, David.

Regarding unitless. There are times when units are not available in SK, and sometimes it is not possible (for example, when considering counts of something).

I would much prefer that unassigned units receive no label rather than 'unitless', or at least have the option to ignore the unit label.

Also, I think you need mm and inch as length units, derived from m.

Again, thanks for everything.

[godind]

Good point. I'll do a pass on units and add mm, inch and no unit

[godind]

Not sure I see value for mm and inch. Please reopen with a use case if ever.
Features part of v3.

[motamman]

precipitation, for one

…

On Fri, Apr 18, 2025 at 9:49 AM David G ***@***.***> wrote: Not sure I see value for mm and inch. Please reopen with a use case if ever. Features part of v3. — Reply to this email directly, view it on GitHub <#491 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA27IAPWEGZ6JK3DCBWJQYL22D7GDAVCNFSM6AAAAABUYLYO32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJVGQ4DKMZUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***> *godind* left a comment (mxtommy/Kip#491) <#491 (comment)> Not sure I see value for mm and inch. Please reopen with a use case if ever. Features part of v3. — Reply to this email directly, view it on GitHub <#491 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA27IAPWEGZ6JK3DCBWJQYL22D7GDAVCNFSM6AAAAABUYLYO32VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJVGQ4DKMZUGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>