I am working on that. I won't be able to actually show that functionality till it's coded, but here is a concept screenshot. <a href="http://downloads.thecompletecomputerresource.com/smart/smart">http://downloads.thecompletecomputerresource.com/smart/smart
</a> gui/screen shots/smart_gui2.jpg<br><br>Well, when I go to add this, during testing, I'd like to make the gui called upon by smart --gui2, this way it wont affect the core. <br><br>I haven't figured out how to lay out the configure tab yet. I'm still working on the layout.
<br><br><div><span class="gmail_quote">On 8/9/07, <b class="gmail_sendername">Richard Hendershot</b> <<a href="mailto:rshendershot@mchsi.com">rshendershot@mchsi.com</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 Thu, 2007-08-02 at 12:08 -0700, linux_learner wrote:<br>> Some great ideas. I am working toward this.<br>><br>> On 8/2/07, Mikus Grinbergs <<a href="mailto:mikus@bga.com">mikus@bga.com</a>> wrote:<br>> > Jop and I have been working on the new smart gui.
<br>> > I am open to suggestions.<br>><br>><br>> Some wishes:<br>><br>> - My biggest simple complaint with the present GUI is that<br>> (probably because of the way I have smart set up) the
<br>> 'Expand<br>> All' in 'View' cannot be checkmarked.<br>><br>> Having done a 'Search", I have to *additionally* request<br>> 'Expand All' - I would like to be able to omit this extra
<br>> step.<br>><br>> - And the "Status Area" needs to be *blanked* every time<br>> that a<br>> click initiates some kind of processing. As it is, the<br>> output
<br>> message "No interesting updates available" from 'Upgrade'<br>> persists inappropriately after other functions are<br>> invoked.<br>><br>> - Also, I wish that the various smart windows would remember
<br>> their<br>> sizes and positions the way I've set them. As it is, I<br>> have to<br>> re-size/re-position them every time I restart 'smart<br>> --GUI'.
<br>><br>> - I believe that with the current implementation, when a<br>> panel<br>> provides a 'Close' button, sometimes when I forget and<br>> click on<br>> the 'X' in the Title Bar - nothing much happens. I wish
<br>> the 'X'<br>> would do the same thing the 'Close' button does.<br>><br>> - A major complaint that is more difficult to fix is that<br>> the<br>> 'Change Summary' panel put up by 'Upgrade all
<br>> packages' (also by<br>> 'Apply marked changes') is __read-only__. There are times<br>> when<br>> I do *not* want a particular package to be upgraded. The
<br>> best<br>> that I can do is to make sure that "changes" are "marked",<br>> then:<br>><br>> As now implemented, I have to separately go to 'View',
<br>> checkmark 'Hide Unmarked' (and in a separate step<br>> request<br>> 'Expand All') -- only in the resulting main panel can I<br>> then "unmark" the changes I do not want applied.
<br>><br>> It would cut out the extra steps if I could "unmark" from<br>> the<br>> 'Change Summary' panel directly.<br>><br>><br>><br>> And a comment:
<br>><br>> - I greatly prefer (from a Human-Factors viewpoint) the<br>> top-level<br>> layout in Ubuntu Synaptic -- there is no need to go to the<br>> 'View'<br>
> drop-down menu -- instead the selection buttons (for what<br>> is to<br>> be displayed in the main panel) are *always* accessible.<br>><br>><br>> mikus<br>><br>
><br><br>I'd like to see the main window to include the Group that a package was<br>from. This is in the Channels hierarchical view. An example is<br>searching on 'rescue'. I see ddrescue. I don't know what group it's
<br>from. It sounds like what I need.<br><br>I also see blobwarz and ballz. They *sound* like games but that is not<br>always so clear. If I chose Group or Channel&Group views then the only<br>thing accomplished is I have to drill down into every repository and
<br>group to see what files they might contain.<br><br>I want just to see the files whose descriptions match and their<br>attributes. Group surely is one.<br><br>When all is said and done, I find smart an irreplaceable tool, so
<br>whatever GUI warts might come along with it I have to acknowledge that<br>it does the job; I'm much more concerned about its handling of all the<br>various repositories, their types, their disparate versions, and<br>
performance than ease of use. Huge, hearty Thanks to the devs.<br><br>But if any GUI effort destabilizes the core then I'm totally against.<br><br>-Rick<br><br></blockquote></div><br>