Would you like to merge with the mean module? Both modules use a very similar plugin process.

Working on #1308830: Spaces module Integration would give it all of the functionality of boxes right?

Comments

mrfelton’s picture

mrfelton commented
Version: » 7.x-1.x-dev

+1

febbraro’s picture

febbraro commented

Neil, we are definitely interested in working together, Bean/Boxes/Entity Boxes seem like they are targeting very similar things and a combined effort to kill Blocks once and for all would be a great idea.

Are you still open to it? If so we should arrange a call or at least meet up in IRC to talk about it.

indytechcook’s picture

indytechcook commented

Hey Josh, I mean Frank. I'd love for us to work together on this. I'll be at drupalcon, we can talk then also.

febbraro’s picture

febbraro commented

Hahaha, very funny. :p

I'll send you an email about coordination, but if all else fails lets talk/drink in Denver about this. Any BoFs around Bean yet?

indytechcook’s picture

indytechcook commented

Yep: http://denver2012.drupal.org/forum/building-custom-block-entities-beans

Yeah for drinking!

brad.bulger’s picture

brad.bulger commented

The Bean module developers seem pretty adamant that actual "beans" - instances of a type - should *not* be exportable. That's a fundamental difference to this module, isn't it?

jec006’s picture

jec006 commented

This is true - indytechcook and I, along with many of our colleagues have been talking about this quite a bit. Entity boxes really only supports placeholders for the instances at this point, as the entity_box entity itself is not exportable. We both think this is actually the preferred behavior, and everyone seems to agree that building placeholders for beans - i.e. an item that denotes that a bean of type x is placed here - is a useful concept.

brad.bulger’s picture

brad.bulger commented

"placed here" in what context? or should i say Context perhaps...

this seems like a worldview difference. contractors that use Features to deliver a website to a client might not want to export actual blocks ("beans"). but i can definitely tell you that as an internal tech development group for an organization's website, we constantly blur the line between configuration and content, if there is one to begin with: we build the initial version, push to the live site, where it gets updated by users, the updates are backported to development where further changes are applied by developers, a new version is pushed out, repeat.

but maybe i misunderstand: since Boxes supports export of an actual individual box, as long as you are building on that module, would that apply to fielded box types built with any future combined version of this module?

jonhattan’s picture

jonhattan
Primary language Spanish
Location Plasencia
commented

FYI, Bean has uuid support, and content may be exportable with deploy. See #1785626: Add deploy support