Code Keys : Are you using them ?

[Pebble]

Hi plug-in makers!

I'm just knocking up a code that has an option to remember a preference between page loads.

I've used a cookie which is no big deal but had me wondering if other plug-in developers are using the keys. As there are only 10 available to each user it seems strange to ask the user to choose between codes because they haven't got any left.

If no-one (or not many) are using the keys, then I'll use a key! But if people are using them then I'm quite happy to leave my cookie doing the business!

Thoughts and views very welcome.

[Chris]

Last I checked, PB will not allow plugins to use cookies. It causes issues with the EU Cookie policy.

[Pebble]

Nov 10, 2012 14:34:37 GMT -8 Chris said:

Last I checked, PB will not allow plugins to use cookies. It causes issues with the EU Cookie policy.

Cheers for the info Chris! Nice to know.... A key it is!

[Chris]

Nov 10, 2012 15:50:05 GMT -8 Pebble said:

Nov 10, 2012 14:34:37 GMT -8 Chris said:

Last I checked, PB will not allow plugins to use cookies. It causes issues with the EU Cookie policy.

Cheers for the info Chris! Nice to know.... A key it is!

200 should hopefully be plenty. And if not, I'm talking about including a one-key system using Yootil to maximize the usage of keys... so, if you just need to store a boolean, Yootil will maximize key usage by combining boolean sets.

[Pebble]

Yep it's just a boolean, 2 actually, which is why I thought it a waste to use a key.

200 ? I thought each forum was limited to 10 ?
I'll have a look at yootil and see...... And another look at how the heys work in case i'm missing something pbvios! lol

[Chris]

Nov 10, 2012 16:03:21 GMT -8 Pebble said:

Yep it's just a boolean, 2 actually, which is why I thought it a waste to use a key.

200 ? I thought each forum was limited to 10 ?
I'll have a look at yootil and see...... And another look at how the heys work in case i'm missing something pbvios! lol

Ok, you're right. I was told it was 200 at some point (may have been earlier in the spec.) Gonna have to bring this up.... 10 is not enough unfortunately when you can't communicate key usage between plugins.

[Peter]

Nov 10, 2012 15:56:41 GMT -8 Chris said:

Nov 10, 2012 15:50:05 GMT -8 Pebble said:

Cheers for the info Chris! Nice to know.... A key it is!

200 should hopefully be plenty. And if not, I'm talking about including a one-key system using Yootil to maximize the usage of keys... so, if you just need to store a boolean, Yootil will maximize key usage by combining boolean sets.

Funny you bought that up, was going to discuss it with you. It seems pointless creating keys for doing 1 thing (i.e a user preference), so was going to add support to Yootil to easily allow them to set a key value pair, and we store it in the 1 key.

I thought it was 200 as well, hmm.

[Chris]

Nov 10, 2012 16:25:29 GMT -8 Peter said:

Nov 10, 2012 15:56:41 GMT -8 Chris said:

200 should hopefully be plenty. And if not, I'm talking about including a one-key system using Yootil to maximize the usage of keys... so, if you just need to store a boolean, Yootil will maximize key usage by combining boolean sets.

Funny you bought that up, was going to discuss it with you. It seems pointless creating keys for doing 1 thing (i.e a user preference), so was going to add support to Yootil to easily allow them to set a key value pair, and we store it in the 1 key.

I thought it was 200 as well, hmm.

LET'S DO THIS.

Peter: We'll fill up the space real quick though with allowing any kind of long IDs... Ideas? We can't just use an auto-increment strategy because removing a code will make it inconsistent.

[Pebble]

Glad I brought this up! Keep me posted please. A nice 'little' project you've got going there. Looking forward to the updates.