Incorrect use of hook_hook_info()

Oh god, this is really sad actually :( We did some experiments with Field group & Display Suite today and this was working out fine untill I actually merged now and the delete callback of field group is broken - man this is really really sad.

Why doesn't core use this hook by default - this would made it really easy to split up code more, now you really need some entry points in your .module file again. Urg, back to the drawing board for field group and DS :(

When reading the documentation of this hook, i thought it was a very nice sollution to the problem of having to load only the files when you want them to, instead of hard including the file you want to delegate it too.

So what you say, is that this is totally wrong? (it works like a charm though).
So basically what i did not know, is that the hook defines groups and not what i thought it was doing : mapping a hook to a file (which is the group).

/**
 * Implements hook_hook_info().
 */
function field_group_hook_info() {
  $hooks = array(
    'menu' => array(
      'group' => 'field_ui'
    ),
    'field_info_max_weight' => array(
      'group' => 'field_ui'
    ),
    'form_field_ui_field_overview_form_alter' => array(
      'group' => 'field_ui'
    ),
    'form_field_ui_display_overview_form_alter' => array(
      'group' => 'field_ui'
    ),
    'features_api' => array(
      'group' => 'features'
    ),
    'field_attach_form' => array(
      'group' => 'form'
    ),
  );
  return $hooks;
}

So i have a funny feeling now. Do you have any suggestions on how to achieve the same purpose?
If it is only the menu, then i can live with the fact that it just has to stay in the .module file. If the other ones need to go, then i am looking for a sollution.

Crell, can you pm me on IRC for this, to discuss it a bit (i persume, as i read this, ... ) it will be mostly you explaining me what i don't get from the documenation. This is a bit important since we already put this in other contribs as well.

Conclusion: i thought this was helping us to get the feature "hey drupal, that hook can be found there and you only have to load it if the implementation is asked for".

@swentel sorry, was typing , did not see your posting then.

After reading the documentation again, i think i got it and the conclusion is indeed unbelievably sad. I cannot use this hook in field_group as well, as the field_group implementations are not that long and i like them in the module file. The incredible ugly form_alter functions will have to go to the .module file or do a hard include there to delegate it to the feature group.

Well i will stop wining and start refactoring in another way. Any tips would greatly be appreciated to achieve the effect of not having to include a group.inc file yourself, but only when a hook implementation is fired.

Well thx for telling us to hold our horses. Refactored and Fixed

the field_group_hook_info() was still left over - removed and commited.