Difference between revisions of "Talk:PC-BSD® 9.1 TODO"

From PC-BSD Wiki
Jump to: navigation, search
(More ideas likely to include for v9.1 or later..)
(consideration for general direction of PC-BSD..)
Line 12: Line 12:
 
** Search - A GUI to Locate would be great, though searching within a file could be added, I suppose.
 
** Search - A GUI to Locate would be great, though searching within a file could be added, I suppose.
  
* Service Manager - add a description of each service that may be stopped/started or enabled/disabled.. Of course, if there is anything dependent upon a service, it may also be prudent to include tailored warnings about what will be affected.
+
* Service Manager - add a description of each service that may be stopped/started or enabled/disabled.. perhaps either display or quote the manpage for the service. Of course, if there is anything dependent upon a service, it may also be prudent to include tailored warnings about what will be affected.
 +
 
 +
----
 +
 
 +
== Painting over the Underbelly? ==
 +
Our focus should be on making things easier and more approachable or accessible. Therefore, in subtle ways, we ought to maintain some visibility of the technical side of BSD. We can GUI-fy the output of a manpage, dmesg, locate, or other cli "ugliness". This would appeal to the tech-inclined without necessarily scaring away neophytes. It would be wrong to go the more extreme route that Apple has chosen, thereby hiding all technical/challenging aspects behind a simplistic (even if powerful) interface.

Revision as of 10:44, 18 November 2011

Further suggested additions

  • WPA/WEP passkey configuration in network setup during install- supposing secured wifi is the sole internet access but a proxy is not needed/desired.
  • Add forensic tools to Live Mode- Scalpel (when ported) and Foremost or similar.
  • Simply offer a PC-BSD 'standard' set of control panel items (which could also be adjusted via cli if possible) for all common System needs. Possible items to include if they do not already exist. Brand these PC-BSD developed items with the fireball logo so they can be easily identified. The additional idea aside from having more control of necessarily configurable OS features and availability of them to the system in general (regardless), is that possibly other DE/WM included versions which may be buggy or resource wasteful could be turned off or deinstalled.
    • Audio - auto-sense headphone connection, dolby/surround, assign specific output/volume to program/device
    • Display - including multi-head
    • Input - keyboard, mouse, touch, tablet/stylus
    • Printer - could include fax
    • Network - wifi, ethernet, pppoe, dialup/modem
    • Scanner
    • Search - A GUI to Locate would be great, though searching within a file could be added, I suppose.
  • Service Manager - add a description of each service that may be stopped/started or enabled/disabled.. perhaps either display or quote the manpage for the service. Of course, if there is anything dependent upon a service, it may also be prudent to include tailored warnings about what will be affected.

Painting over the Underbelly?

Our focus should be on making things easier and more approachable or accessible. Therefore, in subtle ways, we ought to maintain some visibility of the technical side of BSD. We can GUI-fy the output of a manpage, dmesg, locate, or other cli "ugliness". This would appeal to the tech-inclined without necessarily scaring away neophytes. It would be wrong to go the more extreme route that Apple has chosen, thereby hiding all technical/challenging aspects behind a simplistic (even if powerful) interface.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox