Simon, I agree that we should not use wxGrid for such a dialog. Other wx classes are somewhat harder to use but provide a much better interface (once you get them right).
On Sun, Nov 12, 2017 at 11:46 AM, Simon Wells <swel...@gmail.com> wrote: > would it not be better to use one of the types that uses native tables > rather than wxgrid? what is wxgrid giving you that the native tables aren't? > > > On 12/11/2017, at 13:44, Oliver Walters <oliver.henry.walt...@gmail.com> > wrote: > > Hi Tom, > > This is a fantastic idea, I think that your mock up has a lot of good UX > improvements. > > In particular I like the idea of "active" for each library. You then do > not have to find a library once you have removed it from the table, only > tick "active". Brilliant. > > Regarding the "advanced options" button, why not have an extra button > (next to Add / Remove / etc) which says "Edit". Clicking on this brings up > a dialog for the selected library with all extra options... > > Should the footprints / symbols / etc / all appear in the same list? I > like the idea of a single library preferences dialog, but what if the > various library types were separated by a panel on the left hand side, as > is common in many preferences windows? I'm thinking of Eclipse as an > example. > > Here is an example of something I have in a development branch (that has > been wanting my attention for some time). The core code to make this dialog > style is pretty solid, so I could share that part with you if you think > this is a good idea. > > > <image.png> > > I'm thinking that the window above would be adapted to have in the left > column: > > "Library Options" > "Symbol Libraries" > "Footprint Libraries" > > Overall I am really behind your idea :) > > On Sun, Nov 12, 2017 at 11:01 AM, Tomasz Wlostowski < > tomasz.wlostow...@cern.ch> wrote: > >> Dear colleagues, >> >> Now that we have the new library table system in the schematic editor >> (may thanks Wayne!), we also have the library table dialog to configure >> the tables. >> >> For many users - including myself - these dialogs are a bit too complex. >> A few days ago I asked the Polish Kicad community of what users find >> annoying and the complexity of the library manager window was heavily >> criticized. The main points were exposing too many advanced functions >> straight away (such as special configuration options for each plugin) >> and requiring the user to type in the library paths by hand or paste >> them instead of selecting the files with a browser. Currently I prefer >> editing the lib-table files by hand instead of using the GUI. >> >> I believe that the introduction of the new library system into eeschema >> is a good chance to consolidate the library management UI and improve >> Kicad's User Experience. In the attachment, you'll find the example >> design of simplified library setup dialog, with some remarks and >> comments. Your feedback will be greatly appreciated! >> >> Tom >> >> PS1. I haven't started coding yet - this is just a mockup. >> PS2. The current library table dialog will remain accessible if the user >> selects the 'show advanced options' checkbox - so if some of you prefer >> the current UI, it's not going to disappear :) >> >> >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> >> > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > > >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp