Sponsored Content
Full Discussion: Intel binaries on PPC
Operating Systems Linux Red Hat Intel binaries on PPC Post 302492473 by Corona688 on Monday 31st of January 2011 02:34:55 PM
Old 01-31-2011
That may or may not work depending on what you're doing. As usual, the more information you give us the better we can help you.
 

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Rogue PPC RPm

Hello, i need to Rogue RPm for PPC, anybody knows where i can get it? Thanks. i am new to Unix, thats why ia m postin here. Thank you! (3 Replies)
Discussion started by: Ro'Taygahn
3 Replies

2. Red Hat

Fedora 12 on PPC

I'm trying to install a linux system on a IBM PowerPC 275 system. I noticed that fedora 12 supports PowerPC. Does anyone have experience with this? I don't want to pay the fee for an enterprise licence for red hat or suse. (3 Replies)
Discussion started by: rein
3 Replies
usual(n)							     [incr Tk]								  usual(n)

NAME
usual - access default option-handling commands for a mega-widget component SYNOPSIS
usual ?tag? ?commands? DESCRIPTION
The usual command is used outside of an [incr Tcl] class definition to define the usual set of option-handling commands for a component widget. Option-handling commands are used when a component is registered with the Archetype base class via the "itk_component add" method. They specify how the component's configuration options should be integrated into the composite option list for the mega-widget. Options can be kept, renamed, or ignored, as described in the Archetype man page. It is tedious to include the same declarations again and again whenever components are added. The usual command allows a standard code fragment to be registered for each widget class, which is used by default to handle the options. All of the standard Tk widgets have usual declarations defined in the [incr Tk] library. Similar usual declarations should be created whenever a new mega-widget class is conceived. Only the most-generic options should be included in the usual declaration. The tag name is usually the name of a widget class, which starts with a capital letter; however, any string registered here can be used later with the usual command described on the Archetype man page. If the commands argument is specified, it is associated with the tag string, and can be accessed later via itk_component add. If only the tag argument is specified, this command looks for an existing tag name and returns the commands associated with it. If there are no commands associated with tag, this command returns the null string. If no arguments are specified, this command returns a list of all tag names previously registered. EXAMPLE
Following is the usual declaration for the standard Tk button widget: usual Button { keep -background -cursor -foreground -font keep -activebackground -activeforeground -disabledforeground keep -highlightcolor -highlightthickness rename -highlightbackground -background background Background } Only the options that would be common to all buttons in a single mega- widget are kept or renamed. Options like "-text" that would be unique to a particular button are ignored. KEYWORDS
itk, Archetype, component, mega-widget itk 3.0 usual(n)
All times are GMT -4. The time now is 06:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy