Add support for more custom field types

[GoogleCodeExporter]

We want to be able to have custom fields that are:
1. Dates (with calendar dropdown)
2. Times (some sort of dropdown)
3. States (AZ - WY)
4. Countries (all ISO 3 letter abbreviations)
5. Radio buttons (instead of a dropbox)

Original issue reported on code.google.com by fireproofsocks on 14 Feb 2011 at 12:24

[GoogleCodeExporter]

Also consider:

* Multi-Selects 
* Time Durations (e.g. 3 days 26 hours)
* Taxonomies (single item)
* WP Users

Original comment by fireproofsocks on 13 Apr 2011 at 1:43

• Changed state: Started

[GoogleCodeExporter]

Other food for thought:  create "option sets" that can be used to power lists 
for both dropdowns and multi-selects (e.g. US states or all country codes).  
This is how I plan to beef up the dropdowns.

Also: ability to handle PHP code and MySQL queries to power dropdown options.

Original comment by fireproofsocks on 13 Apr 2011 at 1:48

[GoogleCodeExporter]

Issue 51 has been merged into this issue.

Original comment by fireproofsocks on 13 Apr 2011 at 1:49

[GoogleCodeExporter]

Another: email field.  Like a text field, but it would Javascript encode the 
email address on the front-end.

Original comment by fireproofsocks on 13 Apr 2011 at 2:39

[GoogleCodeExporter]

Email should be an output filter.

Date field added in revision 375774.

Original comment by fireproofsocks on 22 Apr 2011 at 3:19

[GoogleCodeExporter]

Output filters added: this handles the email field.

Original comment by fireproofsocks on 23 Apr 2011 at 4:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Add RSS field with display options. Wordpress core already has RSS management 
included.
=> Then, users could build specific link-RSS web directory.

Original comment by viale.fa...@gmail.com on 27 Apr 2011 at 7:06

[GoogleCodeExporter]

A Color Picker would be useful also..

Original comment by mamoun.d...@gmail.com on 27 Apr 2011 at 10:58

[GoogleCodeExporter]

Great ideas!
RSS field: you enter the source of the feed.  The options there would be 
formatting options, yes?

Colorpicker: which one to pick?
This one looks good: http://acko.net/dev/farbtastic
http://www.eyecon.ro/colorpicker/#about

Dropdown field (single select):
I'm planning a set of tabs when you define a dropdown field: basic (current 
implementation), pre-defined (incorporate the value lists), MySQL, and PHP.  
MySQL: you'd be able to enter in your own queries. PHP, you could enter in code 
snippets an they would evaluate to an array of values.
Options here should be 1. dropdown, 2. radio buttons, 3. paginated list (like 
the media selector)

Time Field:
Simple time selector

Multi-Selects:
This could almost work the same as the dropdown, but it would need to store a 
JSON array of values and return a PHP array to the themes.  Output filters 
there should include some list formatting.
Options here would be whether it should display as a series of checkboxes, or 
as a multiselect box.

Original comment by fireproofsocks on 27 Apr 2011 at 12:57

[GoogleCodeExporter]

Well, I personally prefer the latter: http://www.eyecon.ro/colorpicker/#about. 
Some reasons:
(1) The vertical picker is more familiar to anyone has experience with Photoshop
(2) It supports RGB codes and not just Hex
(3) The value fields are more robust, they limit you from entering more than 
the allowed characters, and they update the rest fields' values when you press 
Enter while the first one refreshes the page when you press Enter

Original comment by mamoun.d...@gmail.com on 27 Apr 2011 at 3:05

[GoogleCodeExporter]

Cool, thanks for your input.  

I'm thinking... the RSS field is really a text field with an RSS output filter. 
 So for that one, I gotta just write a customized output filter.

Original comment by fireproofsocks on 27 Apr 2011 at 3:48

[GoogleCodeExporter]

Hmm... that color picker @http://www.eyecon.ro/colorpicker/#about seems 
wonky... you have to click AND DRAG for it to pick up the color.  I thought it 
was broken at first.

There's also this one: http://blog.meta100.com/post/600571131/mcolorpicker
And this one: http://labs.abeautifulsite.net/projects/js/jquery/miniColors/

Thoughts?

Original comment by fireproofsocks on 27 Apr 2011 at 10:18

[GoogleCodeExporter]

You're right. I had experienced the same CLICK AND DRAG behavior with the color 
picker that Magic Fields plugin provides, which seems to be the same.

Hmm, mColorPicker has transparent color choice, which is nice actually. Also, 
remembering your last color choices is a nice feature, although it isn't 
functioning properly for me in the demo page. On the other hand, I find my-self 
more familiar with the Photoshop-like picker that jQuery miniColors provides. 
The first one is still good though..

Original comment by mamoun.d...@gmail.com on 27 Apr 2011 at 10:37

[GoogleCodeExporter]

Well, hells bells... might as well just put a couple on there and let people 
choose which one they want to use when they define the custom field.

Original comment by fireproofsocks on 27 Apr 2011 at 10:44

[GoogleCodeExporter]

While I like the customization ability in general, I sometimes find that 
simplicity and interface cleanness are more important. If you kept giving the 
ability to the users to customize and fine tune every small detail, you'll come 
up with a complex and crowded interface. 

Just my 2-cents..

Original comment by mamoun.d...@gmail.com on 27 Apr 2011 at 10:56

[GoogleCodeExporter]

That's probably very true... I'm building this out so that users will be able 
to extend the FieldElement class and add their own custom field types... still 
a few releases away, but that's planned for version 1.0.  The hope there is if 
they want to customize, THEY can customize (and I don't have to haha).

But your point is well taken.  So, dear mamoun.d... I give to you this epic 
choice: choose one of the above color pickers (or find another one) that is 
easily compatible with jQuery, and I will implement it in a future release. 

Things to consider: screen real-estate and usability.  
http://acko.net/dev/farbtastic looked very usable, but also big on the screen, 
whereas http://blog.meta100.com/post/600571131/mcolorpicker is very small on 
the screen, but may not be as usable (?).  I'm not a front end guy, so I'll 
rely on your best recommendation.

Original comment by fireproofsocks on 27 Apr 2011 at 11:53

[GoogleCodeExporter]

GOD... I hate decisions making! 
Anyway, thanks for trust. I'll try to study the available options and get back 
to you..

Original comment by mamoun.d...@gmail.com on 28 Apr 2011 at 2:11

[GoogleCodeExporter]

Ok, I've chosen the mColorPicker.  It's live in version 0.9.0.  I don't plan 
more custom fields at this point, only variations on the basics: I still need 
to add PHP and MySQL functionality to the dropdown and multiselect fields, as 
well as an overhaul of all reference fields by integrating with the 
!SummarizePosts plugin.

Original comment by fireproofsocks on 4 May 2011 at 4:18

• Changed state: InProgress

[GoogleCodeExporter]

Please forgive me for the long waiting. I cannot take decisions quickly.. but I 
was starting to be inclined to mColorPicker, although I got impressed by 
another, unlisted one, named jPicker. It's highly customizable and actively 
maintained through a long change log. And as they're honest, it has been 
extensively tested on all major browsers, including IE5.5. Actually, I'm using 
a Mac and I don't care of anything belongs to IE, but it makes me feel good 
since I know that making anything work with IE, especially such old version, 
needs some miracles. It's big on the screen though and maybe more than what 
this plugin users may need.

Anyway, thanks for your work!

Original comment by mamoun.d...@gmail.com on 4 May 2011 at 11:49

[GoogleCodeExporter]

Related: Issue 82

Original comment by mamoun.d...@gmail.com on 11 May 2011 at 6:07

[GoogleCodeExporter]

Is it possible to go back and re-encode all the old email addresses already 
entered, if you switch from 'raw' to 'email encode' on an email field?  

Original comment by mopto...@gmail.com on 8 Jun 2011 at 3:00

[GoogleCodeExporter]

Yes: the email address is stored un-encrypted in the database; if you select 
the "Email" Output Filter, then in your templates, the value will be converted 
to the encrypted value.  It's better encryption if you use the Hivelogic 
Enkoder: http://hivelogic.com/enkoder/

But, you can't encode that on the fly :(

Original comment by fireproofsocks on 8 Jun 2011 at 3:14

[GoogleCodeExporter]

Separate labels/values for dropdowns and multiselects were implemented in issue 
150.  

I'm closing this ticket and it will be reincarnated as requests for specific 
field types -- having one big ticket for a bunch of field types is too daunting.

Original comment by fireproofsocks on 28 Aug 2011 at 6:57

• Changed state: Fixed