Re: Widget alignment

2013-06-04 Thread Kip Warner
On Thu, 2013-05-30 at 20:45 -0700, Kip Warner wrote:
 On Mon, 2013-05-27 at 01:01 -0700, Kip Warner wrote:
  Ok, I think I've got it. I put all the widgets and boxes in a page into
  a single vertical oriented GtkBox with its contents vertically centred
  and the box set to expand. Then I insert the banner widget into the
  parent box. It seems to work.
 
 It seems as though I may have spoke too soon. The image widget is placed
 correctly and the image inside of it automatically rescales to fit the
 maximum space that it can. 
 
 However, when maximized, the scrollbars on the GtkScrolledWindow, parent
 widget to the GtkImage widget, become visible which I do not want.
 Perhaps I am using the wrong parent widgets, or they are just configured
 wrong.
 
   http://pastebin.com/ywRtGGY3
 
 Suggestions welcome.

Hey John. I wonder if you have any suggestions?

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: VTE questions

2013-06-04 Thread Kip Warner
On Wed, 2013-05-29 at 22:41 -0700, Kip Warner wrote:
 On Wed, 2013-05-29 at 18:58 +0800, Arnel A. Borja wrote:
  Remove GtkScrolledWindow (right-click the recoveryTerminal in the right
  sidebar then select Remove Parent in the popup menu) then add a GtkScrollbar
  to box31. Make sure that the terminal is set to expand horizontally, and the
  terminal and the scrollbar has the same (vertical) adjustment.
 
 Something else I noticed. The scrollbar automatically scrolls down as
 the VTE widget's output fills up, as I expected it to. However, when I
 maximize the window, the VTE stops automatically scrolling unless I
 manually drag the scroll thumb down to the bottom.

Hey Arnel. I'm still having this issue and if you could spare a minute,
it would be really appreciated.  I'm also still not seeing the sunken
border either. I tried setting the frame's border to etched in, but
still no luck.

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list


Re: Filechooser bug day/weekend/week/month idea

2013-06-04 Thread Matthias Clasen
On Mon, Jun 3, 2013 at 6:02 PM, Timothy Arceri t_arc...@yahoo.com.au wrote:



 Anyway I'm keen to see what people think of my idea? Or if I'm just wasting 
 my time.

Far from it. I've been meaning to thank you for all the effort you've
put into filechooser bug triage lately. I'm sure you're making a lot
of people happy with this initiative. I'm one of then.
___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: [E-devel] Announce: Wayland Functional Integration Test Suite

2013-06-04 Thread Tom Hacohen

On 22/05/13 14:56, Eoff, Ullysses A wrote:

I wanted to announce that a new open source project called
wayland-fits is now available on 01.org https://01.org/wayland.

The Wayland Functional Integration Test Suite (wayland-fits) is a fully
automated test suite.  Its purpose is to validate the functionality and
integration between Wayland client software and Wayland server
software.  It provides a test framework and test suites for multiple
Wayland-enabled toolkits and the Wayland core.  The test framework
allows tests to emit input events from the bottom of the software stack.
That is, [input system]-server-client-toolkit-test-app.  This
enables full input pipeline validation.  It also includes its own Wayland
test protocol that enables tests to cross-validate client and server
states.

Currently there are tests for Wayland Core and Wayland EFL.  And just
recently, I have started adding tests for Wayland Gtk+ (I'm already
finding several trivial bugs).  There are plans to start adding tests for
Wayland Clutter and Wayland Qt, too.  Also, a server-side
implementation of the wayland-fits protocol is essential for every test
to execute.  Right now, there is only an implementation for Weston
included that supports drm, x11, and headless backends (caution: the
headless backend will only run the software/shm based tests).  It's
absolutely plausible, however, that there will be implementations for
other Wayland compositors that have a plugin architecture, too.

I am currently the maintainer of this project with contributions
coming in from one or two other people on occasion.  I would be
oh-so-grateful to have more contributors from the enthusiastic Wayland
community.  So start sending your patches!  I only develop and
test on Intel hardware and Fedora... so if there are issues on other
hardware/OS flavors, feel free to submit fixes; tested, of course ;-).
There is still a lot of Wayland functionality that is not tested by this suite
and design decisions that could be made...and I could use as much help
as I can get.  If nothing else, I hope it's a useful test suite for those
that use it.  It has already detected many regressions and bugs.

The source repository is on github at:

https://github.com/01org/wayland-fits

There is more information in the README about contributing, building,
running, etc...  Also, we can start using the wiki in the github project to
share more info (and such) as needed.

If you have any questions, feel free to drop me a line.  I generally hang out
in the #wayland and #wayland-efl IRC channels on freenode as some of
you already know (nick: uartie).  I am travelling this week so expect a
delayed response.

Oh, and P.S. the project is written in C++ ;-)



We don't test in EFL, we just assume things work.

--
Tom.

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


Re: Filechooser bug day/weekend/week/month idea

2013-06-04 Thread Timothy Arceri
Re: John
I use GTK+ on Windows and I can confirm that GtkFileChooser has been
one of the least reliable components :-( I'd be willing to provide some
assistance but I'm still on Gtk+ version 2, as opposed to 3.

John

Thanks John. I have attached a document with all the Windows bugs. Broken down 
into three categories.
1. Testing needed (old bugs that need to be confirmed still exist)
2. Bugs that someone can probably start work on right away.
3. Bugs needing some design work.

---
Re: Matthias
Far from it. I've been meaning to thank you for all the effort you've
put into filechooser bug triage lately. I'm sure you're making a lot
of people happy with this initiative. I'm one of then.

Good to know. Thanks.



windows_bugs.odt
Description: application/vnd.oasis.opendocument.text
___
gtk-devel-list mailing list
gtk-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-devel-list


Re: Filechooser bug day/weekend/week/month idea

2013-06-04 Thread Federico Mena Quintero
On Mon, 2013-06-03 at 15:02 -0700, Timothy Arceri wrote:

 I have managed to help get the count down from 359 only a couple of
 weeks ago through a combination of patches, making duplicates and
 bumping old bugs and patches. I have even found a couple of unreported
 issue along the way. However I've come to the conclusion that if I
 want to make a serious dent to these bugs I need some help. So... 

For the record, I want to publically thank Timothy for the stellar work
he has been doing in weeding the file chooser's bug list.  Closing old
bugs, filing patches, what more would one want? :)

 I have started working my way through all the outstanding bugs and
 categorising them into groups based on the next action that should (in
 my opinion, I'm open to corrections) be taken.

This is the right way to go!

 Once a complete list of these issues has been created we could
 advertise a bug day/week/etc for these to be worked on retested etc. 

For me a month-long fixing spree would work well, I think.  Of course
I'll gladly guide people through the code if needed.

 I upload the Libre Office documents I've used to categories these bugs
 here:
 http://www.itsqueeze.com/wp-content/uploads/2013/06/Filechooser-bugs.tar.gz 
 but I would like to put all this on the Gnome wiki somewhere if that's 
 possible??

This is really good!  Thanks so much for compiling the list of
categorized bugs!

By now the list I had in https://live.gnome.org/GtkFileChooser is highly
obsolete.  Feel free to replace it with your list of bugs.  An
alternative is to put little strings in the Status Whiteboard field of
each bug (filechooser-easy, filechooser-crash, filechooser-retest,
etc.) and put URLs for the corresponding bug queries in the wiki.

  Federico

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