Bug Tracker

#1636 closed enhancement (invalid)

Opened September 17, 2007 09:45AM UTC

Closed December 27, 2007 03:35PM UTC

icky of jquery UI vs. interface elements

Reported by: florianb Owned by: paul
Priority: major Milestone: 1.2.1
Component: ui Version: 1.2
Keywords: Cc:
Blocked by: Blocking:
Description

I've noticed that jquery UI with the fisheye and the list sortable demos are a bit icky.

  • machine: Intel Core2 Duo 2.13 MHz, 2GB ram (1Gb free), Nvidia 5900 Ultra 256mb
  • operating system: ubuntu feisty (with desktop effects enabled)
  • browser: firefox 2.0.0.6

fisheye

sortable nested list

Attachments (4)

Interface Elements drag&drop sortable list

  • interface_elements_fisheye.ogg (154.3 KB) - added by florianb September 17, 2007 09:49AM UTC.

    Interface Elements fisheye menu

  • jquery_ui_dragdrop_list.ogg (70.3 KB) - added by florianb September 17, 2007 09:50AM UTC.

    jquery UI drag&drop sortable nested list

  • jquery_ui_fisheye.ogg (132.5 KB) - added by florianb September 17, 2007 09:50AM UTC.

    jquery UI fisheye menu

    • Change History (6)

    Changed September 17, 2007 11:02AM UTC by florianb comment:1

    I tested on the same system with opera, and it's nice and fluid. However on opera interface elements still feels a tick better.

    Changed September 17, 2007 12:06PM UTC by florianb comment:2

    I tested with konqueror and there the effect is much amplified. Interface Elements runs smooth and normal, but jquery UI is extremely icky (much more then on mozilla)

    Changed September 20, 2007 01:43PM UTC by paul comment:3

    resolution: → invalid
    status: new → closed

    Hi, these performance issues cannot easily be grouped into a single task. As for sortables, I have already plans for speeding them up, but I don't know yet for magnifier. Thanks for your information!

    Changed September 21, 2007 06:40AM UTC by florianb comment:4

    If you're going to split this ticket in multiple please include the ticket URLs you've opened for it.

    Changed November 09, 2007 09:29AM UTC by florianb comment:5

    resolution: invalid
    status: closed → reopened

    This issue hasn't been addressed so far, there was no comment that other tickets would address this. I researched the issue and showed in the most clarity that the issue is real and problematic. I rechecked with the current demo, it is still an issue.

    Please don't dismiss valuable input.

    Changed December 27, 2007 03:35PM UTC by paul comment:6

    resolution: → invalid
    status: reopened → closed

    What is still real and problematic? Where is the issue? I will happily close all tickets related loosely to performance/ickyness, because it's absolutely not possible to fix them this way.

    I'm thankful for all input, but please don't go against the project lead's decision to close the issue and to create separate tickets for specific cases. If you really need to reopen the ticket, attach valid information. Thank you.