On Jan 14, 2008, at 4:34 AM, Malcolm Greene wrote:

> If one is developing Python/Dabo applications, how do you program  
> for OS
> specific issues like:
>
> - screen size and color resolution

        Native functions in wxPython. Use sizers to make display changes  
irrelevant.

> - desktop space available for application (single/multi-monitor  
> setups)

        Again, detectable via wxPython.

> - system metrics (default colors, sounds, fonts, etc)

        There are a bunch of these functions, many of which we wrap in Dabo,  
such as dabo.ui.getAvailableFonts(), which returns a list of all  
installed fonts for a given machine.

> - interface to clipboard
> - printer properties and control

        Via wxPython.

> - available memory and ability to control max memory usage like
> sys(3050)

        Not sure if this applies. Python doesn't do the same "grab all  
available memory" stuff that Fox does.

> - pointing device properties and events (mouse wheel events)
> - common dialogs (file, folder, color, font, messagebox, etc)

        These are all wrapped by Dabo.

> - path related information

        The os.path module.

> - OS event binding

        It would probably depend on the event.

> - timer events, system date/time values

        dabo.ui.dTimer; the datetime module.

> - keyboard events

        wrapped by Dabo.

> - access to environment variables (SET <var>=<value>)

        The os module.

> - network card mac address

        Never checked into this, but it wouldn't surprise me if there was a  
module to do this.

> - guid generation

        Provided by Dabo.

> - name and path of running executable (and is it already running)

        The sys module.

> - list of drives and drive properties (size, free space)

        The os module.

> - access to command line parameters

        The sys module.

> - font discovery

        Didn't you already ask that?

> - number and type of CPUs
> - OS version info
> - starting, enumerating/monitoring, and stopping other processes/tasks
> - returning application exit codes
> - currently logged in user
> - system power status (battery info, etc)
> - pipes, shared memory, mutexes
> - audio, video output
> - scanner based input

        Gotta run, but before I do, just do some simple Googling, and I'll  
bet you'll find the answers to all of these pretty easily.

-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com




_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to