Vreman, Peter - Acision wrote:
> I don't believe the preferences are really going to be
relevant to the
> CLI, are they?
>
I only implemented the CLI for testing purposes. So you see the saved user preferences
Shouldn't show up in the CLI then, IMHO. There's a constant struggle to
keep things simple and keep the number of options and things visible to
the user down -- especially challenging when
features move ahead quickly, but a goal just the same.
> If the intent is to save common searches, couldn't that be done with
> bash aliases? It seems the Unix way is a lot about not repeating
> things that can be done with other smaller tools.
>
The preferences are generic and not limited to searches. I already added a reports
dictionary to save report settings. The reports to show can then be selected from the CLI
or using a dropdown box from the WebUI.
I think saved CLI reports should be handled with bash aliases for those
that need them. It's one less object type to deal with.
> It also seems to me that shortly we may want to implement userprefs
> instead as a Session cookie, as that would require less overhead. I
> very much like the idea of being able to save filters, but we may not
> need the backend implementation.
>
I agree that the current page is Session based, but the items_per_page and sorting is a
global userpref that you want to have saved between sessions.
I think these could be easily saved in permanent cookies.
> My other question asked yesterday which I still need an answer to is
> what are we planning to do with the search page that currently doesn't
> work except for the first critera now? Do you have a WebUI
> implementation that uses the filters and shows them in the web app? If
> so, I'd like to see that finished before we go on to other things.
>
I'm working on this. I hope to get something finished in the next hours before I
leave for a week holiday.
Good deal -- Though I would like to see the backend change to save these
just as cookies, IMHO, as I think we can eliminate the user object. Each
new object has a lot of touchpoints in the code,
so this would keep things simpler IMHO.
We should be able to save the whole json data for userprefs in the
cookie (using simplejson directly to just stick a hash in there).
Thanks!
--Michael