Alright, let's stop arguing (which doesn't lead anywhere) and starting holes in
the air, but let's instead start some heavy-weight brain-storming for ideas on
how to implement the problems at hand. From the dicussions before we already
know that:
- GNUstep needs somewhat tighter management of it'
On Wed, Oct 26, 2005 at 04:33:37AM +0100, Nicola Pero wrote:
> I'm sure a great flame-fest will follow, please excuse me if I'll drop out
> of this thread at this point. ;-)
Actually, this is exactly the problem. This is how proposing something
on the GNUstep lists works:
1. Email the list.
2. G
Nicola Pero wrote:
Yes, and frankly this is a perfect opportunity to state that rule by
unanimous or even near-unanimous consent is simply not a viable nor
sustainable. People disagree. One cannot make everyone happy, nor should
they try to in all instances. Currently, I feel the GNUstep projec
> Yes, and frankly this is a perfect opportunity to state that rule by
> unanimous or even near-unanimous consent is simply not a viable nor
> sustainable. People disagree. One cannot make everyone happy, nor should
> they try to in all instances. Currently, I feel the GNUstep project is
> try
Alex,
--- Alex Perez <[EMAIL PROTECTED]> wrote:
> Dennis Leeuw wrote:
> > Hi Gregory,
> >
(( SNIP ))
> >
> > I agree with you that the OpenStep spec should not be leading anymore. I
> > think GNUstep already has out grown the spec. It should now stand on its
> > own feet, with own ideas and a
Dennis Leeuw wrote:
Hi Gregory,
To get to 1.0 I think a roadmap is needed. Looking at:
http://savannah.gnu.org/task/?group_id=99
Maybe someone should define which one of those tasks needs to be
completed before GNUstep can be 1.0. And those points should be made
more visible on the website, a
CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch:
Changes by: Adam Fedor <[EMAIL PROTECTED]> 05/10/26 00:36:09
Modified files:
Startup: ChangeLog InstallGNUstep configure configure.ac
Log message:
* configure.ac: Proper use of GNUSTEP_SYSTEM_R
> -Original Message-
> From: David Ayers
>
> Adam Fedor schrieb:
> > Test results for GNUstep as of Tue Oct 25 06:38:06 EDT 2005
> > If a particular system failed compilation, the logs for
> that system will
> > be placed at ftp://ftp.gnustep.org/pub/testfarm
> >
>
> That directory se
CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch:
Changes by: Richard Frith-Macdonald <[EMAIL PROTECTED]> 05/10/25
16:38:49
Modified files:
dev-libs/SQLClient: WebServer.m
Log message:
Send verbose alerts through alert method rather than NSLog() a
IMO that's the wrong thing to do though ... it's a case of throwing the
baby out with the bathwater ... rather than disabling all the
functionality until the problem goes away, you should be fixing the
problem. While some apps may not need cut and paste, drag and drop, to
provide services, to
CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch:
Changes by: Richard Frith-Macdonald <[EMAIL PROTECTED]> 05/10/25
16:15:36
Modified files:
core/base : ChangeLog
core/base/Source: NSPathUtilities.m
Log message:
Try to ensure basic di
On 2005-10-25 14:31:56 +0100 Adrian Robert <[EMAIL PROTECTED]> wrote:
On Oct 25, 2005, at 4:37 AM, Leigh Smith wrote:
...
So my question is the degree to which gdomap and gdnc are indeed
necessary
for an application not requiring explicit use of inter- process comms and
if NSMessagePortN
On Oct 25, 2005, at 7:28 AM, Dennis Leeuw wrote:
To get to 1.0 I think a roadmap is needed. Looking at:
http://savannah.gnu.org/task/?group_id=99
Maybe someone should define which one of those tasks needs to be
completed before GNUstep can be 1.0. And those points should be
made more visible
Richard Frith-Macdonald schrieb:
> On 2005-10-25 09:14:04 +0100 David Ayers <[EMAIL PROTECTED]> wrote:
>
>> 2.) creating the expected user directory layout, and creating it "in
>> time" for such usage as 1.) which I believe implies:
>> a.) We created it when sourcing GNUstep.[csh] (just kidding
Adam Fedor schrieb:
> Test results for GNUstep as of Tue Oct 25 06:38:06 EDT 2005
> If a particular system failed compilation, the logs for that system will
> be placed at ftp://ftp.gnustep.org/pub/testfarm
>
That directory seems to be empty. Could someone have a look at what's
going on?
>
> S
CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch:
Changes by: Richard Frith-Macdonald <[EMAIL PROTECTED]> 05/10/25
13:53:29
Modified files:
core/gui : ChangeLog
core/gui/Source: NSColorList.m
Log message:
Minor fixup for when user's
On Oct 25, 2005, at 4:37 AM, Leigh Smith wrote:
...
So my question is the degree to which gdomap and gdnc are indeed
necessary for an application not requiring explicit use of inter-
process comms and if NSMessagePortNameServer would address this
(since I see NSMessagePorts are explictly
Riccardo,
--- Riccardo <[EMAIL PROTECTED]> wrote:
> Hey,
>
> > They want themeability and they want the freedom to endlessly customize
> > thier
> > desktop. This is something that people have been able to do on Windows
> > for
> > years.
> well.. this is also a risk of making things complex.
On 2005-10-25 09:37:19 +0100 Leigh Smith <[EMAIL PROTECTED]> wrote:
In an application that indeed relies on distributed processes, this would
be
the price to pay, but after some review of the GNUstep base code, it seems
the use of distributed notifications and distributed objects are tightl
> -Original Message-
> From: Andrew Ruder [mailto:[EMAIL PROTECTED]
> automatically. For example, I can make a /modules/dev-apps that
> basically says:
>
> Check out /apps/gorm/trunk into the gorm directory
> Check out /apps/easydiff/trunk into the easydiff directory
>
> and so on. Wh
on 25/10/2005 02:57 Sheldon Gill said the following:
> I think you've mis-diagnosed the behaviour problem. It isn't in
> NSSearchPath() but rather the calling code.
I agree that the code in NSColorList is not robust enough to handle
absent ~/GNUstep/Library directory. It should probably simply ski
On 2005-10-25 09:14:04 +0100 David Ayers <[EMAIL PROTECTED]> wrote:
Sheldon Gill schrieb:
It isn't in
NSSearchPath() but rather the calling code. Creation of a path isn't and
shouldn't be the responsibility of NSSearchPath(). That needs to be
handled elsewhere. Generally it is, by the way.
Hi Gregory,
To get to 1.0 I think a roadmap is needed. Looking at:
http://savannah.gnu.org/task/?group_id=99
Maybe someone should define which one of those tasks needs to be
completed before GNUstep can be 1.0. And those points should be made
more visible on the website, as to get peoples atte
Test results for GNUstep as of Tue Oct 25 06:38:06 EDT 2005
If a particular system failed compilation, the logs for that system will
be placed at ftp://ftp.gnustep.org/pub/testfarm
If you would like to add your machine to this list, set up a cron job
(make sure you set up your PATH and other envir
I've been trying to use GNUstep & MinGW to produce a working Win32
application. One of the goals is to have the application behave as a
first class Windows application, in particular to launch it from the
Start menu without requiring MSYS and openapp to be running. Our
target group of users
Hey,
They want themeability and they want the freedom to endlessly customize
thier
desktop. This is something that people have been able to do on Windows
for
years.
well.. this is also a risk of making things complex. Once I was a fan of
super-configurable environments (I remember being an ea
Sheldon Gill schrieb:
>
> It isn't in
> NSSearchPath() but rather the calling code. Creation of a path isn't and
> shouldn't be the responsibility of NSSearchPath(). That needs to be
> handled elsewhere. Generally it is, by the way.
>
Indeed there are two issues at hand.
1.) NSColorList has to
27 matches
Mail list logo
