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

From PC-BSD Wiki
Jump to: navigation, search
(Further suggested additions)
(One intermediate revision by one user not shown)
Line 20: Line 20:
 
** '''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.. 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.  
+
* '''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.
 
+
* '''AppCafe{{RM}}'''
 +
** add multiple selection capability for removal or install
 +
** add a ''sets'' function - this would allow for a defined group of apps to be installed, possibly transferable to other systems.
 +
* '''Qt Curve system-wide theme configurator''' - Qt Curve is one of the most configurable themes already available to KDE, but being Qt-based, it should be possible for it to be available to other de/wms. Many de/wms have their own theme capability but few allow for the entire range of configuration to be adjusted and/or saved and recalled/loaded. ''This is necessarily a difficult concept'' especially considering an intention for it to function for all desktops with a theme functionality.
 
----
 
----
  
 
== Painting over the Underbelly? ==
 
== 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.
 
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 22:59, 25 September 2012

Further suggested additions

Acceptably complete items are struck.

  • WPA/WEP passkey configuration in network setup during install - supposing secured wifi is the sole internet access but a proxy is not needed/wanted, yet a network install is desired.
  • Live Mode - Add forensic tools Scalpel and Foremost or similar.
  • PC-BSD® 'standard' control panel items (as a GUI front end to cli configurator where 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 or in some way so they can be clearly and 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
      • Sound Configuration allows for basic control, by making it easier to change the default audio device.
    • Display - including multi-head
      • KDE's display control panel is a good example of what this should become, but accessible regardless of de/wm. Why must we reboot for this change? How does KDE succeed without the reboot?
    • Input - keyboard, mouse, touch, tablet/stylus
      • The capabilities exist and may be configurable but a PC-BSD control panel for them does not.
    • Printer - could include fax
      • This may not be perfect but it is functional. The trouble seems to be where the printer is redefined or re-configured in other programs or control panels.
    • Fax - whether this is a part of another control panel, it should be a consideration for those who need or desire it.
    • Network - wifi, ethernet, pppoe, dialup/modem
      • This is getting closer to what it should be, but as of 9.1rc1, it still seems to need work: It is my understanding that WPA and WPA supplicant configuration is a wifi feature, yet with no discovered wifi devices, the option is available for the network device which happens to be ethernet (em).
    • Scanner - Xsane via Scanner control panel which also checks for the device attached to the system.
    • 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.
  • AppCafe®
    • add multiple selection capability for removal or install
    • add a sets function - this would allow for a defined group of apps to be installed, possibly transferable to other systems.
  • Qt Curve system-wide theme configurator - Qt Curve is one of the most configurable themes already available to KDE, but being Qt-based, it should be possible for it to be available to other de/wms. Many de/wms have their own theme capability but few allow for the entire range of configuration to be adjusted and/or saved and recalled/loaded. This is necessarily a difficult concept especially considering an intention for it to function for all desktops with a theme functionality.

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