Hi KooBoo

Here's some background to my question :

Been using the HtmlForm module and worked out that you need to create a schema that reflects the properties on your form, then you can create a content folder pointing to that schema. Took me a bit of code digging and experimenting but I got there! I also figured out that on the schema you need to set Visible In List to true so that the new schema's columns appear in the content folder list.

So here's the lead up to my question :

In the various lists in the ExtJS back end you can select which columns you want to be displayed. For example I had to enable the display of VisibleInList in the schema list so that I could set it to true. And in the content folder for my new schema I had to enable the new columns from my schema so that the screen makes sense to users and they see the data they expected (this was a "contact me" form so I didn't need Title, Application, User Name or Published in this case they are just in the way).

And here's my question :

I have to select which columns are visible every time I go in. Can you please change this so that once you have selected which columns are to be displayed for a particular list, they stay set unless they are manually changed again?

I would love this feature, it would make a massive difference for me and the usability of the back end

Thanks

Ideally the solution to this would be a separate table in the database that would be exported/imported along with the rest of the data (I've not looked into that side of KooBoo yet though)

I see your point about cookies and performance, you could use the path of the cookie to be more specific of course. It's only half a solution using cookies or the state data because the settings will still be lost frequently, it's client machine specific (obviously) and the customer would contact me with a complaint when the layout of the lists changes and I'd be regularly connecting to the server to change the columns in the lists!

I don't want the user to have to set this up at all because it isn't a user friendly action. Once the lists' columns have been configured they should stay set and that should be the way that that instance of KooBoo looks. Can this be given more priority?? Please!?

I'm a little while off contributing to KooBoo (at least the core of KooBoo) but it will happen

That's great thanks it's all I can ask for and I'm glad you're going to look at it in the future. A short term workaround would be to write my own UI using the KooBoo api, or perhaps hook in some front end javascript that automatically sets the columns I might look into that (I evaluated ExtJS a few months ago but for our customer base's typical workstations (my day job) it was too slow so opted for JQuery UI)

Am looking forward to the new version