I did check HIG before starting this, and again now. According to <a href="http://developer.gnome.org/projects/gup/hig/2.0/">http://developer.gnome.org/projects/gup/hig/2.0/</a> I am following;<br><br><dt><span class="chapter">
<a href="http://developer.gnome.org/projects/gup/hig/2.0/principles.html">1. Usability Principles</a></span></dt><dd><dl><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles.html#principles-people">
Design for People</a></span></dt><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-broad-userbase.html">Don't Limit Your User Base</a></span></dt><dd><dl><dt><span class="sect2">
<a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-broad-userbase.html#accessibility">Accessibility</a></span></dt><dt><span class="sect2"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-broad-userbase.html#internationalization">
Internationalization and Localization</a></span></dt></dl></dd><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-match.html">Create a Match Between Your Application and the Real World
</a></span></dt><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-consistency.html">Make Your Application Consistent</a></span></dt><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-feedback.html">
Keep the User Informed</a></span></dt><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-simplicity.html">Keep It Simple and Pretty</a></span></dt><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-user-control.html">
Put the User in Control</a></span></dt><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-forgiveness.html">Forgive the User</a></span></dt><dt><span class="sect1"><a href="http://developer.gnome.org/projects/gup/hig/2.0/principles-direct-manipulation.html">
Provide Direct Manipulation</a></span></dt></dl></dd><br>I guess it might help if you had an idea of the eventual goal. I'm hoping to create sort of a merge of something like a combination of smart's current gui, and yast/synaptic. I have also presented this to several forums, and everyone else seems to like to idea and the layout.
<br><br>So, I understand you don't like it at all, and like the current gui. That's fine. Is there anything from the current gui that you'd like to see improved, or functionality added? Let me put it another way; how can we improve the current gui? This is the sort of feedback I need.
<br><br><div><span class="gmail_quote">On 8/2/07, <b class="gmail_sendername">Patryk Zawadzki</b> <<a href="mailto:patrys@pld-linux.org">patrys@pld-linux.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 8/2/07, linux_learner <<a href="mailto:linux.learner@gmail.com">linux.learner@gmail.com</a>> wrote:<br>> Currently, the only way to do configurations in smart, is from the command<br>> line. I wish to make this more intuitive.
<br><br>Still, this belongs to Edit / Preferences like the rest of the world has it.<br><br>> As far as the menu, I just renamed it, and clustered like things together.<br><br>Didn't check the menu.<br><br>> As far as the tabbed boxes, again, that's to make things a bit more
<br>> intuitive. So there would be 2 ways. From the menu, or from the tabbed<br>> boxes.<br><br>Haven't seen an application where configuration is a tab in the main<br>window. Doesn't make much sense to me. An average man in the street
<br>does not want to know about configuration. It's the admin's job to<br>configure software and exposing configuration in the main window does<br>everything but enchances the GUI.<br><br>See HIG guidelines.<br><br>
--<br>Patryk Zawadzki<br>Generated Content<br></blockquote></div><br>