Carrot2

More scalable input tabs

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0
  • Fix Version/s: 2.1
  • Component/s: Web Application
  • Description:
    Hide

    Currently, the number of input tabs we can have in the webapp is limited by the width of the tabs space – it's not possible to have more than about 7-8 tabs because they wouldn't fit on the screen.

    One idea to solve this problem is to have a "more..." tab, shown always at the rightmost position, which would show all the inputs emphasizing those that are currently not available on tabs. After the user clicks one of such inputs, the selected input would replace the rightmost regular tab (not the "more..." tab), the new tab would be automatically activated and the cursor placed in the query text field.

    In a more sophisticated scenario, each input on the "more..." tab could have a combo box. Entries with the combo box checked would appear as tabs. In this way, users could have as many tabs as they can fit on their screens. One problem with this is the order/ordering of tabs – alphabetical?

    Another important factor is to remember user preferences (last added tab, set of selected tabs depending on the scenario) in a persistent cookie.

    Show
    Currently, the number of input tabs we can have in the webapp is limited by the width of the tabs space – it's not possible to have more than about 7-8 tabs because they wouldn't fit on the screen. One idea to solve this problem is to have a "more..." tab, shown always at the rightmost position, which would show all the inputs emphasizing those that are currently not available on tabs. After the user clicks one of such inputs, the selected input would replace the rightmost regular tab (not the "more..." tab), the new tab would be automatically activated and the cursor placed in the query text field. In a more sophisticated scenario, each input on the "more..." tab could have a combo box. Entries with the combo box checked would appear as tabs. In this way, users could have as many tabs as they can fit on their screens. One problem with this is the order/ordering of tabs – alphabetical? Another important factor is to remember user preferences (last added tab, set of selected tabs depending on the scenario) in a persistent cookie.

Activity

Hide
Stanisław Osiński added a comment - 14/Jun/07 06:21 PM

Available in trunk and at http://demo.carrot2.org/demo-head/main

Show
Stanisław Osiński added a comment - 14/Jun/07 06:21 PM Available in trunk and at http://demo.carrot2.org/demo-head/main
Hide
Stanisław Osiński added a comment - 18/Jun/07 10:26 AM

Some weird behaviour described by Dawid:

  • open http://demo.carrot2.org/demo-head/main
  • click 'more' and leave only "Web" selected
  • click 'more demos'
  • use the browser's back button and you'll get back to a page will all tabs
  • enter query and click enter and you get a page only with the "Web" tab
  • use the browser's back button and you'll get back to a page will all tabs
Show
Stanisław Osiński added a comment - 18/Jun/07 10:26 AM Some weird behaviour described by Dawid:
  • open http://demo.carrot2.org/demo-head/main
  • click 'more' and leave only "Web" selected
  • click 'more demos'
  • use the browser's back button and you'll get back to a page will all tabs
  • enter query and click enter and you get a page only with the "Web" tab
  • use the browser's back button and you'll get back to a page will all tabs
Hide
Stanisław Osiński added a comment - 20/Jun/07 08:22 AM

Now the weird behaviour should be gone, tough the solution is not perfect.

One problem that persists on FF2.0 is that after navigating to a page with tabs using the Back button, the tabs will not respond to mouse clicks until clicking anywhere else on the page. This is really weird and happens only on FF, so I'll file a separate lower priority bug for that for the next release.

Show
Stanisław Osiński added a comment - 20/Jun/07 08:22 AM Now the weird behaviour should be gone, tough the solution is not perfect. One problem that persists on FF2.0 is that after navigating to a page with tabs using the Back button, the tabs will not respond to mouse clicks until clicking anywhere else on the page. This is really weird and happens only on FF, so I'll file a separate lower priority bug for that for the next release.
Hide
Stanisław Osiński added a comment - 20/Jun/07 08:35 AM

Nope – still have problems with flickering tabs when executing queries, reopening.

Show
Stanisław Osiński added a comment - 20/Jun/07 08:35 AM Nope – still have problems with flickering tabs when executing queries, reopening.
Hide
Stanisław Osiński added a comment - 20/Jun/07 11:54 AM

False alarm, it turns out. Firefox somehow confused cookies stored for localhost and demo.carrot2.org (though it should not matter anyway).

Show
Stanisław Osiński added a comment - 20/Jun/07 11:54 AM False alarm, it turns out. Firefox somehow confused cookies stored for localhost and demo.carrot2.org (though it should not matter anyway).

People

Dates

  • Created:
    26/Jan/07 03:43 PM
    Updated:
    12/Aug/07 02:33 PM
    Resolved:
    20/Jun/07 11:54 AM