Re: gnustep on wheezy

2013-12-18 Thread Philippe Roussel
On Wed, Dec 18, 2013 at 06:26:01PM +, Ivan Vučica wrote: > I specifically recommended the curses UI instead of just using CLI, because > you can then play with scenarios that will resolve the conflicts/missing > deps in a nicer UI. > > Obviously libobjcgs, whatever that is, is missing, and the

Re: gnustep on wheezy

2013-12-18 Thread Ivan Vučica
I specifically recommended the curses UI instead of just using CLI, because you can then play with scenarios that will resolve the conflicts/missing deps in a nicer UI. Obviously libobjcgs, whatever that is, is missing, and there are multiple ways to resolve that. Try to use the graphical resolver

Re: Kickstarter was not successful... but it did help things...

2013-12-18 Thread Ivan Vučica
Doc, I would certainly love GNUstep to capitalise on popularity of UIKit. Please contribute your implementation of all required technologies. My contributions were what I perceived as improvements needed to make nicer apps leveraging on OSX and iOS developers' experience. I was far from the best

Re: gnustep on wheezy

2013-12-18 Thread Michael P. Soulier
On 18/12/13 Ivan Vučica said: > Can you try using aptitude curses UI and see what happens? msoulier@cappuccino:~$ sudo aptitude install gnustep The following NEW packages will be installed: charmap.app{a} cynthiune.app{a} gnustep gnustep-back-common{a} gnustep-back0.20{a} gnustep-back0.20-ar

gnustep on wheezy

2013-12-18 Thread Ivan Vučica
Can you try using aptitude curses UI and see what happens? On Wednesday, 18 December 2013 17:03:08, Michael P. Soulier < msoul...@digitaltorque.ca> wrote: > Hey, any idea why this would happen? > > Debian Wheezy > > msoulier@cappuccino:~$ cat /etc/apt/sources.list > deb http://ftp.ca.debian.org/d

Re: memory leak - cairo/x11 backend

2013-12-18 Thread Eric Wasylishen
Hi Riccardo, +Fred +gnustep-dev On Dec 18, 2013, at 7:40 AM, Riccardo Mottola wrote: > Hi, > > Eric Wasylishen wrote: >> >> Hi Riccardo, >> >> As a starting point for debugging I would put NSLog's in >> XGCairoModernSurface -initWithDevice: and -dealloc. This is where we retain >> / releas

gnustep on wheezy

2013-12-18 Thread Michael P. Soulier
Hey, any idea why this would happen? Debian Wheezy msoulier@cappuccino:~$ cat /etc/apt/sources.list deb http://ftp.ca.debian.org/debian/ wheezy main contrib non-free deb-src http://ftp.ca.debian.org/debian/ wheezy main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib

Re: How to reconnect to a new X Server

2013-12-18 Thread Ivan Vučica
Several years ago I worked a bit on a simple login panel which didn't use X11 directly; instead I tried to structure it in a modular fashion. The only useful module that I implemented used SDL to open a window. It's unfinished, but seems to work for basic login. My goal was to, eventually, draw a b

Re: memory leak - cairo/x11 backend

2013-12-18 Thread Riccardo Mottola
Hi, Eric Wasylishen wrote: Hi Riccardo, As a starting point for debugging I would put NSLog's in XGCairoModernSurface -initWithDevice: and -dealloc. This is where we retain / release the Cairo surface that is holding memory in the x server. Also I would put logging in -NSImage set name:, l