Hi Tyler, I had posted an example of implementing a RIFE component. The example was a simple table that was sortable by clicking on the table's headers.
That was very simple and meant to serve as an example, not as an actual complete reusable table component. However, after posting the example, interest in such a more generic, feature-full table component was expressed. I've thought about it for a while, trying to come up with a good design. I had a couple of ideas on how to approach it but both had certain flaws. Since then I haven't had the time to return to it, because of being busy with other more pressing matters. If you or anyone has ideas on how such a component should be designed (if you think it would be a useful component, that is), it would be interesting to discuss. Here's one way of approaching it: pretend the component is already done and ready to go, and you're using it. What kind of API would you expect to have? Some (but not all) points to consider: 1) How do you display a simple table? (Simple things should be simple). 2) How do you tell the component what your model is? 3) How do you indicate which columns to display? 4) How do you indicate how to format the data? 5) What if you have certain rows that span multiple columns, or certain columns that span multiple rows? How do you "tell" the component about that? etc. Thanks in advance for your input. Cheers, Frederic _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
