Filters in the config option?

I don't understand what you're asking.

That was how Homebox 1.x handled the filters. I found some big issues with that and removed it.

1) Exposed filters were being duplicated in the view, and in the config section.
2) The filters that showed in the view couldn't submit; only the filters in the config section would.
3) Some cookie was used to save the state of the filter for each user and that didn't seem to work.

What do you think should be done here? I don't like the idea of relying on a cookie to save a filter state. And I don't like the idea of putting it in the config section if the filters can't be saved permanently.

?

how would users know that filters are inside the settings panel? I could see people easily not assuming that's the case..

i don't know about that...the last thing i want to do is hinder the functionality of a view to people who are more aware..

gotta think about this one

Personnaly this is a big lost for me. I think the settings with the filter added a lot of possibility, we use it for some view charts displayed in a homebox and our user are really use to manipulate it, igoogle do something similar...

For a test I modified the homebox-block.tpl.php

    <div class="portlet-config">
      <?php if ($page->settings['color']): ?>
        <div class="homebox-colors">
          <span class="homebox-color-message"><?php print t('Select a color') . ':'; ?></span>
          <?php for ($i=0; $i < HOMEBOX_NUMBER_OF_COLOURS; $i++): ?>
            <span class="homebox-color-selector" style="background-color: <?php print $page->settings['colors'][$i] ?>;">&nbsp;</span>
          <?php endfor ?>
        </div>
      <?php endif; ?>
	  
++	  <?php if($block->module == 'views' && $filter = module_invoke('views', 'block', 'view', "-exp-".$block->delta)): ?>
++	    <div class="homebox-view-filter">
++  			<?php print $filter['content']; ?>
++		</div>	  
++	  <?php endif; ?>

      <?php if ($block->module == 'homebox'): ?>
        <button id="delete-<?php print $block->module . '_' . $block->delta; ?>" class="homebox-delete-custom-link"><?php print t('Delete'); ?></button>
        <button id="edit-<?php print $block->module . '_' . $block->delta; ?>" class="homebox-edit-custom-link"><?php print t('Edit'); ?></button>
      <?php endif; ?>
      <?php if ($page->settings['color'] || $block->module == 'views' && !is_null($filters)): ?>
        <div class="clear-block"></div>
      <?php endif ?>

It's works, I will see if we met any problems but it's simlar to how homebox v1 do it

I tested but it seems ok. In my test homebox I have 2 views to displays nodes. They both have Node type filter exposed. And I can filter each view with different type.
Is it what you mean ?

The drupal.org dashboard exposes some filters (and other settings, like number of posts) through the settings button... Is anything like that doable with homebox?

Drupal.org is using homebox for the dashboard. I am not sure how they are making that happen, though.

Bumping version since 6.x-2.x is no longer being developed.

Hi,

I was hoping that the positioning of exposed filters would be handled the way which drupal.org does so, in the settings button, however this doesn't seem to be the case.

Is this being looked at for 6.3 and 7.2?

I would have thought that in the spirit of open source, if drupal.org have managed it do it, it would be available as standard on homebox!

Happy to donate to the development of this otherwise.

It's handled partly in Drupal's 'drupalorg' module if I recall. I've looked into it briefly, and have been offered access to the code. However, this is not a feature I have the time nor the use case to implement at this point.

That said, I am happy to accept patches.

Drupal 6 is no longer supported. If this can be reproduced with Drupal 7, please re-open with details.