SNEAK PEAK: Combined Snippets + Chunks = Snippets

Quote from: infoclipper at Aug 17, 2005, 02:41 PM

Thanks, Raymond.

I assume, then, that the first element is always the selected?  We don’t store a default index, right?

You mean in the list input type? If so, yes but you can specify another option using the fourth part of the string

example
&mylist=List1;list,1,2,3,4;2

Here the default index would be 2

Attached is a preview Flash movie of the new Snippet Properties. I’m hoping it is self explanatory. Due to the low framerate and the reduced color palettes, some of the visual effects look funny. For instance, the confirmation screens don’t actually turn fruity colors, they simply fade away.

Aside from that issue, does anyone have any feedback? Figured I’d go ahead and show this example to get some early feedback before I move on.

Thanks, guys!

http://www.infoclipper.com/test.htm

Very cool, Travis! Definitely gonig to be a big improvement.

Wow.

(and that Wink is impressive, too...I may have to refurbish my Windows machine and dual-boot it.)

Quote from: infoclipper at Aug 17, 2005, 10:54 PM

Aside from that issue, does anyone have any feedback?  Figured I’d go ahead and show this example to get some early feedback before I move on.

Thanks, guys!

It’s looking very nice. Great going man.

One thing that I would recommend is that after entering the a new key (e.g. color), the desciption for the key should be automatically capitalized (e,g, Color). In so doing the user would not have to alter the description is it’s the same as the key.

Quote from: xwisdom at Aug 18, 2005, 02:28 AM

One thing that I would recommend is that after entering the a new key (e.g. color), the desciption for the key should be automatically capitalized (e,g, Color). In so doing the user would not have to alter the description is it’s the same as the key.

Good point. I’ll make it so.

Thanks!

I will throw one thing out that I think could be a potential issue. It appears that there is no way to add items to lists unless you change the data type to a string, add the element and then change it back to a list.

I’ve been thinking about the best way to handle adding/deleting/editing items in lists but haven’t come up with anything brilliant. It might just be best to keep list values as strings while in edit mode and only show them as actual lists in view mode, but I suppose we’d still have to have a list for choosing the default value.

Maybe I’m just being picky, but I can just imagine someone installing a snippet, wanting to add an option and not being able to figure out how.

Anybody have any great ideas?

If it’s not instantly intuitive, or pretty close thereto, we need to consider making it moreso. Then again, most average users won’t be using these "developer-type" features. (As an aside tangent...) perhaps we can have the new permissions limit access to these in a more granular format.

I don’t see a problem with keeping it as a string, then having a little link next to the string labelled "preview". This link would then build the assocated input box underneath the input text field.

Re:Adam’s suggession for options to add or remove items from list boxes.

IMO I think we can add two small images/icons ( + and - ) beside the <select> box.
The plus (+) would be used to add items while the - would be used to remove items.

When the "+" is click the user will be given a javascript input box in which to enter a new list item. When the "-" is click then the item is removed from the list.

Once Travis is finished with this cool property builder I think we can create variants of it to easily construct or build other configuration settings for the CMS. For example, we can use it to allow users to create custom RTE icons for FCK, TinyMCE and the Xihna toolbar.

It can also be used in the construction of Widget properties