Switching Between Applications in Gnome 3

2013-05-30 Thread אנטולי קרסנר
Hello,

I've been using Gnome 3.4.2 for long time. I started using Gnome 3
because I believe in innovation and evolution through trial and error.
But I noticed a problematic recurring pattern in my usage of my laptop
(I don't carry it anywhere, and it's has a large screen, so it can be
considered like a desktop computer).

When I work, especially when I program, I have many windows open:

Gedit for source code (I know, I know, I should start using an IDE)
Devhelp
Epiphany window for programming-related pages
Epiphany window for other pages (webmail, social network, etc.)
Nautilus, with 2-4 several tabs open, maybe also 2 windows
Gnome Terminal window, with the working directory being my git repo
Gnome Terminal window for compiling short experiment programs I write
Evolution
Empathy
Transmission

This is a lot of open windows, so I group them into workspaces. But it
doesn't help, I still feel too inefficient sometimes, and I'd like to
know how I can improve my desktop worflow and usage.

A typical workspace arrangement I use is listed in the bottom of this
message.

The problems I encounter:

1. When I need to switch between windows in the same workspace, I take
the mouse cursor to the corner of the screen, then click on the window I
want to see.

2. When I need to switch between windows in different workspaces, I move
the mouse cursor to the corner of the window, then move it to the
workspace sidebar, click on the one I want, then click on the window I
want.

3. Sometimes using the mouse is faster than thinking, so I have the
following problem with Nautilus and Epiphany: since more than one window
is open, very often I click on an Epiphany or Nautilus window in the
overview, and when it fully appears on the screen I realize it's the
wrong window and go to the other one. It happens because I click before
I start thinking which workspace is the active one... maybe just because
I have many tabs and may pages open.


The question is, how can I improve that? Switching between windows,
especially on different workspaces, becomes very slow. I tried using alt
+tab, but when I hold alt+tab for too long, the marker starts running
through the list of windows and I can't efficiently click on the one I
want.


Oops, wait a second! I just tried the alt+tab keys again, and now it
seems I was rejecting them too easily... I think it can work for me :)

But anyway, is there some workflow you recommend for programming? I have
one 15.6' screen and I need many windows open. Maybe there's some
keyboard-driven approach which I and other people should be more aware
of.

I really think Gnome 3 can be great and more people can find it useful.
It's just a matter of knowing how to use it efficiently. So if you have
any advice for me, it's very welcome :)

Anatoly



Here's a typical workspace setup I use:

* Personal workspace:
Epiphany window for non-programming pages
Nautilus with non-programming folders open as tabs

* Programming workspace 1
Gedit
Devhelp
Epiphany window for programming-related pages
Gnome Terminal window, with the working directory being my git repo
Nautilus with programming related folders open as tabs

* Programming workspace 2
Gnome Terminal window for compiling short experiment programs I write
Sometimes Evince (for PDF files), filer-roller for tarballs

* Network/communication workspace
Evolution
Empathy
Transmission

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Switching Between Applications in Gnome 3

2013-05-30 Thread Maciej Piechotka
On Thu, 2013-05-30 at 18:52 +0300, אנטולי קרסנר wrote:
 Hello,
 

Hi,

 I've been using Gnome 3.4.2 for long time. I started using Gnome 3
 because I believe in innovation and evolution through trial and error.
 But I noticed a problematic recurring pattern in my usage of my laptop
 (I don't carry it anywhere, and it's has a large screen, so it can be
 considered like a desktop computer).
 
 When I work, especially when I program, I have many windows open:
 
 Gedit for source code (I know, I know, I should start using an IDE)
 Devhelp
 Epiphany window for programming-related pages
 Epiphany window for other pages (webmail, social network, etc.)
 Nautilus, with 2-4 several tabs open, maybe also 2 windows
 Gnome Terminal window, with the working directory being my git repo
 Gnome Terminal window for compiling short experiment programs I write
 Evolution
 Empathy
 Transmission
 

I'm not sure why you should start using IDE? Different people use
different tools (I use both gedit and emacs for programming on Gnome).

 This is a lot of open windows, so I group them into workspaces. But it
 doesn't help, I still feel too inefficient sometimes, and I'd like to
 know how I can improve my desktop worflow and usage.
 
 A typical workspace arrangement I use is listed in the bottom of this
 message.
 
 The problems I encounter:
 
 1. When I need to switch between windows in the same workspace, I take
 the mouse cursor to the corner of the screen, then click on the window I
 want to see.
 
 2. When I need to switch between windows in different workspaces, I move
 the mouse cursor to the corner of the window, then move it to the
 workspace sidebar, click on the one I want, then click on the window I
 want.
 

I am not a designer but for me the most convenient way is:

1. Ctrl+Alt+Up/Down to switch between workspaces
2. Use always on top + mutters tiling features to have windows I need to
be opened at the same time. Say terminal window pinned to corner over
documentation (using always on top) or evince and gedit side by side. (I
believe 'always on top' is the killer feature of Linux for power users -
even my friends using Windows/Mac OS X did agreed that it would be
useful add-on).

Best regards

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Travel assistance applications to attend to GUADEC

2013-05-30 Thread Germán Póo-Caamaño
On Tue, 2013-05-28 at 13:20 +0900, Tristan Van Berkom wrote:
 On Tue, May 28, 2013 at 8:23 AM, Germán Póo-Caamaño g...@gnome.org wrote:
  On Mon, 2013-05-27 at 14:47 -0700, Germán Póo-Caamaño wrote:
  The GNOME Foundation provides travel sponsorships to individuals
  that want to attend GUADEC and need financial assistance.
 
  We are happy to announce that the Travel Committee is ready to
  receive applications for sponsorships to attend to GUADEC 2013.
 
  The instructions are detailed at http://live.gnome.org/Travel
  Please read them carefully.
 
  Deadline: May 31, 2013, 19:00 UTC.  You can start sending
  your applications now!
 
  After further consideration the new deadline is: June 3, 2013, 19:00
  UTC.

 I'm a little confused, or perhaps just unfamiliar with this process.
 
 How can the deadline to request sponsorship be on June 3rd
 when the deadline for speakers to confirm their attendance is
 already June 2nd ?

Bad combination of factors.  However, speakers are encouraged to apply
soon.

If the only reason that a speaker has to not confirm yet is the
sponsorship, then you should confirm and say you are applying for
sponsorship.  We will coordinate with the papers committee.

-- 
Germán Poo-Caamaño
http://calcifer.org/


signature.asc
Description: This is a digitally signed message part
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list

gtk:doc: dropping support for legacy return 'markup'

2013-05-30 Thread Stefan Sauer
hi,

while the proper annotation for return values in gtk-doc is:

* ...
* Returns: foo bar
* ...

the tool also looks for lines starting with returns  at the start of a
documentation body block (for legacy reasons). A following proper
Returns: tag would override the legacy returns docs. The tool will
also print a warning if the legacy return docs are used:
  Free-form return value description in $symbol. Use `Returns:' to
avoid ambiguities.

I'd like to simplify the code and drop the support for legacy returns in
the upcomming 1.19 release for gtk-doc (see also #678094). Please take a
look at your docs and make changes if you rely on legacy returns (aka
see the warning).

Please let me know if this would cause troubles for your project.

Stefan
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list