Small tip (especially since you seem to be doing all the work!
Thanks!)
-- For fields that have an obvious name as a primary key, these should
be stored as hashes of hashes, not arrays. This prevents having to loop
through them and it's much easier to handle and read
I suppose it would be fine to save them with the object system, though
we might want to take some extra steps to avoid them showing up in the
command line -- to keep the options down.
I'm not sure we need the idea of expiring or temporary filters... you
could just require all of them to be saved before they are used. Keeps
things simple.
If you used the existing object system you also wouldn't need to do the
save/load_from disk stuff ... it would just work. My main concern with
that was really the extra stuff that would have to go into the CLI and
manpage, and we can simply keep that from showing up in the CLI since
it's web app specific.
Sound good?
I can rework my patch and change the item_filter.py that I have created to store user
configurations instead.
Below is a new draft datamodel:
UserConfig (item_userconfig.py)
- Name (owner/global)
- Filters Hash[what::name] of Hash
MatchType ANY or ALL
Keys Hash[Key]
Value
- WebUIColumns Hash[pagename] of Hash
Limit
Page
FilterName
Columns Hash[name] of Hash
Sort
Width
- Reports Hash[what::name] of Hash
FilterName
Columns Hash[name] of Hash
Sort
Width
Regards,
Peter
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It
may contain proprietary material, confidential information and/or be subject to legal
privilege. It should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.