Repeatable Regions, i.e.: collections

[geertbrit]

Brwosing the code I see a collections object which currently doesn't do anything.
Is this here for some future functionality to incorporate repeatable regions?

If so, what's your idea on this?

[joshontheweb]

Thats just how I typically stub out my namespaces when using backbone. It may not end up being used. I've got some new features in the pipeline, after those drop I can see if it makes sense to yank.

I'm not exactly sure what you mean by incorporating repeatable regions.

[geertbrit]

Consider a list page with a photogallery of multiple thumbnails each containing a caption (editable) and an image (editable). I'd consider the photogallery a repeatable region, with the ability to add new thumbnails.

functionality:

• The ability to add / remove uniform items to a repeatable region (backed by a backbone collection)
• the ability to detect the type of items in the repeatable region by either
  • having an explicit notion of type
  • of in absence of that, use the first item in the repeatable region as template.

This notion of type starts to become really powerful, when the ability of combining multiple editables in one type would be added. In this example probably: image (editable) + caption (editable) -> thumbnail (type)

Love to discuss / help out where I can.

What do you think?