I’ve been thinking about the new UI for MarcEdit 7. I haven’t decided yet if the main window should have the ribbon or keep the menus (menus seem most appropriate for the MARC Tools and Main Window) – but the main thing I wanted to do with the new UI in MarcEdit 7, is to try and find ways to surface tools based on common questions/actions; as well as push the last used tools up. I’ll keep the user defined buttons (I like those, I use them all the time). One of the other things I’ll likely end up doing, presently I keep the MARCNext toolset framed in the main windows (as well as the about window). I’ll be pushing those into their own windows as the way it currently works – it complicates updates. Also, all fonts will be updated from 8.5 point (the default) to 10.5 pt. I’d like to set the default font to the Google Noto Fonts, but distributing the font is out of the question (the font set is 450 mbs in total — but maybe I can include something in the installer to allow users to select this font for download if they want…I’ll have to think about it). With that, I’ll be improving the accessibility functionality so that users can continue to easily update font sizes. In fact, I’ll be changing the window that shows when you first install to be a series of questions (rather than showing the preferences). The questions will be:
- Preferred Font/Size: I’ll show current settings and sample of typography
- MARC Flavor: You tell me are you using MARC21 or something else
- Default Z39.50/SRU servers (you’ll have a list of known servers to select from this way you have servers in the tool at the beginning)
- Link to the Tutorials/Help
After this, you’ll have the option to select the preferences and update all of the options. But I’m looking for ways to make this easier so when users install MarcEdit 7 for the first time, you don’t have to look for specific settings (specifically fonts).
Feedback is welcome.
- * Note — this wireframe is for the windows/Linux version. Some of these concepts will make it to the MarcEdit Mac version — but I try to keep that development in line with Apples UI recommendations when possible.