Accessible AccessibleAction for setting application/window focus?

If I have a Accessible* to a child of a desktop (i.e. an application), 
is there some way I can (through the at-spi interfaces) cause that 
application to "raise", or "get focus", or "become active"?

If so, is this to be done via an AccessibleAction?  Or is there a method 
of Accessible?

If not, any suggestions on the best platform neutral(ish) way to do this?

thanks,

~~David

Re: Accessible AccessibleAction for setting application/window focus?

David,

I think Bill is the person to answer this but he is on holidays for a few days.

Padraig

> If I have a Accessible* to a child of a desktop (i.e. an application), 
> is there some way I can (through the at-spi interfaces) cause that 
> application to "raise", or "get focus", or "become active"?
> 
> If so, is this to be done via an AccessibleAction?  Or is there a method 
> of Accessible?
> 
> If not, any suggestions on the best platform neutral(ish) way to do this?
> 
> thanks,
> 
> ~~David
> 
> _______________________________________________
> Gnome-accessibility-devel mailing list
> Gnome-accessibility-devel <at> gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel

Re: Accessible AccessibleAction for setting application/window focus?

Hi David,

On Wed, 2002-08-07 at 15:03, David Bolter wrote:
> If I have a Accessible* to a child of a desktop (i.e. an application), 
> is there some way I can (through the at-spi interfaces) cause that 
> application to "raise", or "get focus", or "become active"?

	In a word 'no', at least not yet I think. It's likely we'll need to add
a new interface for this; indeed the interfaces are under-developed in
that area - mainly because a lot of effort has gone into 'atk' / 'gail'
[ I imagine since that is what was needed before the freeze ] and less
into the inter-app / window manager sort of interfaces.

	HTH,

		Michael.

--

-- 
 mmeeks <at> gnu.org  <><, Pseudo Engineer, itinerant idiot

Re: Accessible AccessibleAction for setting application/window focus?

Michael Meeks wrote:

>Hi David,
>
>On Wed, 2002-08-07 at 15:03, David Bolter wrote:
>
>>If I have a Accessible* to a child of a desktop (i.e. an application), 
>>is there some way I can (through the at-spi interfaces) cause that 
>>application to "raise", or "get focus", or "become active"?
>>
>
>	In a word 'no', at least not yet I think. It's likely we'll need to add
>a new interface for this; indeed the interfaces are under-developed in
>that area - mainly because a lot of effort has gone into 'atk' / 'gail'
>[ I imagine since that is what was needed before the freeze ] and less
>into the inter-app / window manager sort of interfaces.
>
>	HTH,
>
>		Michael.
>
Thanks Michael (and Padraig) for your speedy replies -- I love open 
source dev!

This is something that will be important to gok users, so I hope we can 
revisit it soon.  Do you agree this is something that does belong in the 
at-spi?  If not, then I should start a non at-spi solution.

cheers,

Re: Accessible AccessibleAction for setting application/window focus?

Hi David,

On Thu, 2002-08-08 at 12:44, David Bolter wrote:
> This is something that will be important to gok users, so I hope we can 
> revisit it soon.  Do you agree this is something that does belong in the 
> at-spi?  If not, then I should start a non at-spi solution.

	It belongs in at-spi I believe, but it's also going to need
co-operation from the window manager [ most likely ], so that leaves us
in a rather interesting position - it remains to be seen what will
happen.

	It's well worth you writing down your requirements and posting them to
the list though.

	Regards,

		Michael.

--

-- 
 mmeeks <at> gnu.org  <><, Pseudo Engineer, itinerant idiot

Build sheriff permission ...

Hi you guys,

	If you're reading this, you own a module that is not playing ball well
[ probably by accident ] with the rest of the project. To be fair I just
fixed 'at-poke' as well. It seems word of this sort of thing hasn't
spread to the a11y community.

	Anyhow; to facilitate a wider adoption of A11y code - and to enable it
to be snapshotted easily, it is really important to add the following
lines to a 'HACKING' file in your cvs module:

"	Build sheriff commits are welcome - in accordance with the
relevant build sheriff constraints. "

	That is - if you agree with the guidelines, which are these:

http://mail.gnome.org/archives/gnome-hackers-readonly/2002-March/msg00051.html

	[ They should be on developer.gnome.org too, but it seems some 
	  mis-management somewhere made that not happen. ]

	It'd be really great to see this in:

	gail, at-spi, gok, gnopernocis, gnome-mag

	As at the time of inititation of this process, there is still only 1
build sheriff who is Jacob Berkman, a man of taste, discretion etc. who
knows more of autotools than the average maintainer will ever know 

at-spi event crack smoking ...

Hi Bill,

	I was somewhat appalled to look at the at-spi/cspi/spi_main.c code and
see what has been done to it.

	This:

	/*
	 * must ref before doing "direct pointer" identity comparisons,
	 * e.g. "accessible == a".
	 * Alternatively, one can use cspi_object_equal (a, b)
	 */
	Accessible_ref (event->source); 
		
	Is just rubbish.

	The way cspi_object_new is used is extraordinarly nasty; there are far
easier, more efficient and transparent ways to do all of this, how did
this get done this way with no review ? how about this:

      ref = malloc (sizeof (Accessible));
//    ref->objref = CORBA_Object_duplicate (corba_object, cspi_ev ());

	A C++ style comment ?

	Glancing at cspi-bonobo-listener.c (cspi_event), out of interest, how
is the source, allocated by cspi_object_new ever freed ? I could go on
and on ...

	Basically, I look back at this code after a month or so away, and I

Re: at-spi event crack smoking ...

Sigh,

	In this instance I was not going to send this mail until I calmed down
a bit; but it went somehow anyway.

	Apologies in advance; patches will follow,

	Regards,

		Michael.

--

-- 
 mmeeks <at> gnu.org  <><, Pseudo Engineer, itinerant idiot

Need Info on Gnome Panel Theme Bug 89063

Hi, 
The existing Panel menu icons are not themable and the proposed solution
for this is to use GtkIconFactory to render the panel icons.

We have some issues/queries on using GtkIconFactory for panels and am
quoting Mark Mc's comments on this,

a)How do we theme the icons associated with `.desktop files' in a rc
file ?

b)For all the standard panel icons, like the ones in the Actions menu,
should we register these with the default icon factory and use
gtk_image_new_from_stock there too ?

c)The panel uses GnomeIconLoader to search for icons. This implements
the 'Icon Theme Specification' from www.freedesktop.org. Does it not
make more sense to replace the icon selected at runtime using icon
themes ? Admittedly, the RC file is the best place to specify the
required icon size.

Pls. pour in your comments...

Regards,
Raj.

**************************Disclaimer************************************************

Information contained in this E-MAIL being proprietary to Wipro Limited is 
'privileged' and 'confidential' and intended for use only by the individual

Need Info on Gnome Panel Theme Bug 89063

[Sorry my previous mail had a wrong mailing list id for
desktop-devel-list, pls. ignore it]

Hi, 
The existing Panel menu icons are not themable and the proposed solution
for this is to use GtkIconFactory to render the panel icons.

We have some issues/queries on using GtkIconFactory for panels and am
quoting Mark Mc's comments on this,

a)How do we theme the icons associated with `.desktop files' in a rc
file ?

b)For all the standard panel icons, like the ones in the Actions menu,
should we register these with the default icon factory and use
gtk_image_new_from_stock there too ?

c)The panel uses GnomeIconLoader to search for icons. This implements
the 'Icon Theme Specification' from www.freedesktop.org. Does it not
make more sense to replace the icon selected at runtime using icon
themes ? Admittedly, the RC file is the best place to specify the
required icon size.

Pls. pour in your comments...

Regards,
Raj.

**************************Disclaimer************************************************