|
Tuesday 16 September 2003 1:32:00 am
You don't need to alter the standard admin classes for your use. You may want to if you need to change the admin but i don't think you need to at this stage. Consider the following. If i read you right you could make a class with these attributes (essentials for now, but you can add more). Magazine:
- name (textline)
- category (multi-line enum)
- libraries (multi-line enum) The name will be a simple textline. The category i've classes as a multi line enumeration since some of your magazines may fall into two categories but you can class it as a single if your categories are distinct. The libraries are a multi line enumeration. When you create an object for this class you can decide which libraries the magazines are in. If another library gets the magazine then just update the object. This means you could just have a single folder within the admin to hold all of magazine objects. On your user side you can present the information in any way you want, sort by category, whatever. However, you may choose to use your idea of a folder per category. In this case i suggest maybe keeping the category field just to handle the cases where the magazine is in more than one category, and note it when displaying the objects in your folder category. But you can get rid of it if you wish. I've tried to show the flexibility you have for your problem. Again, it is a standard use of ez and once you begin to use it you should start to see of other ways to present your data. When i started my designs changed by the hour. Now im a little better, i change them every few days ;) Well, when im designing that is! Paul
|