discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Discuss-gnustep Digest, Vol 1, Issue 1091


From: Pedro Ortega
Subject: Re: Discuss-gnustep Digest, Vol 1, Issue 1091
Date: Thu, 19 Dec 2002 00:05:27 -0300 (CDT)

Hi,

I'm new in GNUStep, and I'm really impressed with the
beautiful way it is designed. Unfortunately, GNUStep
hasn't many developers working on it. Everybody knows
KDE or Gnome, nobody is even considering to give
GNUStep a try.

I think that one of the main reasons (not considering
that it isn't finished yet) is that the GUI isn't
appealing aesthetically. Just compare GNUMail compiled
under MacOS X and under Linux.

How can the user interface be improved?? How can I
participate, what do you recommend?? I'm new in GNUStep,
and I didn't found very much documentation...

Thanks!!!

Pedro


On Wed, 18 Dec 2002 address@hidden wrote:

> Send Discuss-gnustep mailing list submissions to
>       address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>       http://mail.gnu.org/mailman/listinfo/discuss-gnustep
> or, via email, send a message with subject or body 'help' to
>       address@hidden
>
> You can reach the person managing the list at
>       address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Discuss-gnustep digest..."
>
>
> Today's Topics:
>
>    1. Re: NSThread load balancing (Stefan =?ISO-8859-1?Q?B=F6hringer?=)
>
>
> ----------------------------------------------------------------------
>
> Date: 18 Dec 2002 15:57:11 +0100
> From: Stefan =?ISO-8859-1?Q?B=F6hringer?=
>       <address@hidden>
> To: GNUStep <address@hidden>
> Subject: Re: NSThread load balancing
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1
> MIME-Version: 1.0
> Content-Transfer-Encoding: 8bit
> Precedence: list
> Message: 1
>
> On Tue, 2002-12-17 at 20:03, Philippe C.D.Robert wrote:
> > On Monday, December 16, 2002, at 03:46  Uhr, Stefan Böhringer wrote:
> > > Hello,
> > >
> > > in a DO application I detach many threads for which I need to measure
> > > resource consumption to balance system load.
> > > NSThread unfortunately doesn't supply any information about cpu/mem
> > > usage nor seems there be a possibility to exit a NSThread by force.
> >
> > Use DO to tell a thread to exit...
> As it appears to me the only way to exit a thread is from inside the
> thread via class method NSThread+exit. In my case the thread code is
> (potentially) unknown and most likely without any NSRunLoop (or
> equivalent) being active since those are number crunching threads.
> Therefore, ideally, I would like to exit the tread from the outside.
>
> >
> > > I would propose to add a GNUstep specific function that leaks internal
> > > data structures about the thread on which system calls could be
> > > performed to get the required information.
> > >
> > > Any suggestions/corrections welcome.
> >
> > Why not use the worker thread to collect problem specific information
> > (stats, timers, ...) and let the controller thread (app) decide upon
> > the optimal number of threads and so on?
> This is probably the way to go. The work in the thread is done by
> (unknown) code loaded from a bundle. But before I detach a method in the
> controlling Task which then calls the bundle code. Therefore the bundle
> code can be bracketed by stat collecting (and OS dependend) function
> calls.
> The NSThread API really seems to be a least common denominator of all
> OSs of the last decade. However, extending the NSThread capabilities
> would probably hamper portability given the heterogeneity of target
> platforms of GNUstep/Cocoa.
>
> Thanks,
>       Stefan
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Discuss-gnustep mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/discuss-gnustep
>
>
> End of Discuss-gnustep Digest, Vol 1, Issue 1091
> ************************************************
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]