Since Delta blocks has been broken out into it's own module I suggest that this module be deprecated.

While Delta Blocks comes with Delta, it is not dependent on the API and can be enabled on it's own.. The module is pretty much identical in source, has a more active issue queue and seems to work better. Is there a reason these two modules need to co-exist?

http://drupal.org/project/delta

Comments

KrisBulman’s picture

Issue summary:View changes

better wording

KrisBulman’s picture

Another solution I suppose would be to maybe absorb the code entirely from Delta blocks into this module, and deprecate that.. depends on if the Delta module couples with Delta blocks so well it would be pointless to separate it out.

ordermind’s picture

In the event that Delta Blocks and Blockify are merged together, I suggest that you also incorporate functionality from Logo Block to allow for more customization: http://drupal.org/project/logo_block

Kyle Skrinak’s picture

Hrm. Blockify works better with custom breadcrumb than delta blocks (not at all) but I like the configuration options for blockify. I agree with your essential premise, however, that these two modules be merged into a single module.

KrisBulman’s picture

Title:deprecate this module in favor of delta blocks» merge blockify with delta blocks

I've tested this and agree, both have benefits (or bugs?) but are essentially the same module.. merging the two seems logical. Updated Issue title.

dww’s picture

+1 to merging the two. I have a preference for keeping it in a separate project (e.g. here in blockify) since on a project I just inherited, we're using delta_blocks but have no need for the rest of Delta itself. It'd be nicer to not carry around all that code just for the stand-alone delta_blocks piece. Maybe I can just migrate to using blockify. Anyway, it does seem unfortunate to have both of these modules doing almost exactly the same thing.

Thanks,
-Derek

mengi’s picture

Merging the two seems to be the best option.

Delta is likely to be abandoned (correct me if I am wrong please) since Omega 4 isn't going to use it.

I suggest Blockify 2.x branch if we do go that route.

dww’s picture

Sounds great. Maintainers? Any input?

Thanks,
-Derek

kclarkson’s picture

+1

kclarkson’s picture

Issue summary:View changes

better wording

jpoesen’s picture

Issue summary:View changes

Fair enough. I;ll take a look at delta an set up a 7.x-2.x-dev branch.

dcmouyard’s picture

Another +1 on merging the two modules. I’d prefer the merged module to use the blockify name.