logo

New Response

« Return to the main article

You are replying to:

    • avatar
    • Dweeb
    • Posted on Thu 26 Feb 2004

    Typical really. You come up with a neat piece of code and some smart arse pokes faults in it:

    - Its slow to load - It won't cope with large amounts of data

    The environment we've chosen to work within is always prone to these problems. Indeed anything Domino view based is always going to perform 'badly'.

    I downloaded dTree and ruthlessly pulled it apart to serve my own meek needs, added xml functionality along the lines of xTree and came across all the same problems. But for me it didn't matter. My goal was to build a non-scalable tree of a known size but not a known content.

    In order to acheive the holy grail though what we need is a set of basic building blocks:

    - Virtually scrolling interface so that top level we can fetch data on demand and only download enough to fill the visible region. - Fetch data on demand using xml to populate all levels of the tree/view - Build all icons and images using best practice methods to avoid caching

    Of course doing all of the above cross browser, modular and configurable will indeed be challenging and perhaps costly.

Your Comments

Name:
E-mail:
(optional)
Website:
(optional)
Comment: