Nabble - GNUstep - General

Re: synchronized

2009-12-13T05:48:35Z

Yes, it's usable. No caveats. I believe people are using it now.

On Sun, Dec 13, 2009 at 7:53 AM, <icicle@...> wrote:

>
> Hi!
>
> I would like to know if @synchronized support is in a sane state so that I
> can actually use it. Anybody already using it? Any caveats?
>
> Thanks
> TOM
>
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@...
> http://lists.gnu.org/mailman/listinfo/discuss-gnustep
>

--
Gregory Casamento
Open Logic Corporation, Principal Consultant
## GNUstep Chief Maintainer
yahoo/skype: greg_casamento, aol: gjcasa
(240)274-9630 (Cell), (301)362-9640 (Home)

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

synchronized

2009-12-13T04:53:38Z

Hi!

I would like to know if @synchronized support is in a sane state so
that I can actually use it. Anybody already using it? Any caveats?

Thanks
TOM

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Call for talks at our FOSDEM 2010 devroom (deadline 2010-01-03)

2009-12-07T14:04:19Z

Hi Fred,

thank you very much for your offer. I've added it to http://
wiki.gnustep.org/index.php/FOSDEM_2010#List_of_submitted_talk.
2Fdiscussion.2Fsession_proposals . Just two questions: Do you have a
preference for the time of your discussion (morning, noon or
afternoon) and can you estimate how long it will be (30, 45 or 60
minutes)?

To everybody else and especially to the people who are still unsure
whether to actively participate in our devroom activities: Of course
discussions, hands on or hacking sessions are also welcome. Feel free
to come up with some idea / concept.

regards,

Lars

Am 05.12.2009 um 15:51 schrieb Fred Kiefer:

> I don't want to give a talk, but rather lead a discussion. The title
> could be "Towards GNUsep gui 1.0" and it will be about what we need to
> get there and how to achieve this within the next year. I will
> prepare a
> few opening statements and the rest will be up to the audience.
>
> Fred
>
> Lars Sonchocky-Helldorf schrieb:
>> FOSDEM is up in just 63 days and we have time until Sunday
>> 2010-01-10 to
>> finally submit the talks in our devroom to the FOSDEM organizers.
>> So I'd
>> say we preferably finish our schedule until 2010-01-03 so that the
>> presenters have some time to turn in their abstracts, picture and
>> (optionally) bio for the presentation at the FOSDEM website. Until
>> the
>> 3rd of January only 29 days are left.
>>
>>
>> I have set up a list of proposed talks the talks schedule at our
>> wiki:
>> http://wiki.gnustep.org/index.php/FOSDEM_2010#Dev-
>> Room_Presentations_and_Events
>> . I think we first should collect all talk offers and then start
>> scheduling.
>>
>>
>> So please send your proposals to the list or - even better - enter
>> them
>> on the wiki page above. At first a title, a short summary, proposed
>> duration and a preffered time slot would do, so we can start
>> scheduling
>> as soon as possible. The FOSDEM organizers strongly recommend a
>> granularity of 15 minute blocks. So if a talk is just 15 (lightning
>> talk), 30 or 45 minutes long - fine!
>>
>> As an advice: experience tells that 15 minutes are really short
>> (hence
>> the moniker "lightning talk"). Usually such a lightning talk is only
>> sufficient when you want to put a single new feature into the
>> spotlight
>> - let me give an example here: "There's now a GNOME theme
>> available for
>> GNUstep" (hint for a talk!) or something along those lines. 30 to 45
>> minutes are a good time for a full featured talk and don't
>> underestimate
>> the time needed for a discussion afterwards.
>>
>>
>> Later I would need the following from the presenters for
>> forwarding it
>> to the FOSDEM organizers (they put it on the FOSDEM web site):
>>
>> * activity title (please try to be descriptive, there are ~250
>> talks at
>> FOSDEM during the week-end ;)),
>> * a short abstract (1-2 paragraphs),
>> * a longer description if appropriate,
>> * optionally a list of links to the project website or similar
>> * for each speaker:
>> * the speaker's real name,
>> * a short overview of her bio in a couple of lines,
>> * optionally also a longer bio,
>> * optionally a picture (please send it to us as 128x128 PNG),
>> * optionally links to her website, blog, ...
>>
>> For examples, see:
>> * http://archive.fosdem.org/2009/schedule/devrooms/freejava
>> * http://archive.fosdem.org/2009/schedule/events/java_state_icedtea
>> * http://archive.fosdem.org/2009/schedule/speakers/mark+reinhold

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Call for talks at our FOSDEM 2010 devroom (deadline 2010-01-03)

2009-12-05T06:51:01Z

I don't want to give a talk, but rather lead a discussion. The title
could be "Towards GNUsep gui 1.0" and it will be about what we need to
get there and how to achieve this within the next year. I will prepare a
few opening statements and the rest will be up to the audience.

Fred

Lars Sonchocky-Helldorf schrieb:

> FOSDEM is up in just 63 days and we have time until Sunday 2010-01-10 to
> finally submit the talks in our devroom to the FOSDEM organizers. So I'd
> say we preferably finish our schedule until 2010-01-03 so that the
> presenters have some time to turn in their abstracts, picture and
> (optionally) bio for the presentation at the FOSDEM website. Until the
> 3rd of January only 29 days are left.
>
>
> I have set up a list of proposed talks the talks schedule at our wiki:
> http://wiki.gnustep.org/index.php/FOSDEM_2010#Dev-Room_Presentations_and_Events
> . I think we first should collect all talk offers and then start
> scheduling.
>
>
> So please send your proposals to the list or - even better - enter them
> on the wiki page above. At first a title, a short summary, proposed
> duration and a preffered time slot would do, so we can start scheduling
> as soon as possible. The FOSDEM organizers strongly recommend a
> granularity of 15 minute blocks. So if a talk is just 15 (lightning
> talk), 30 or 45 minutes long - fine!
>
> As an advice: experience tells that 15 minutes are really short (hence
> the moniker "lightning talk"). Usually such a lightning talk is only
> sufficient when you want to put a single new feature into the spotlight
> - let me give an example here: "There's now a GNOME theme available for
> GNUstep" (hint for a talk!) or something along those lines. 30 to 45
> minutes are a good time for a full featured talk and don't underestimate
> the time needed for a discussion afterwards.
>
>
> Later I would need the following from the presenters for forwarding it
> to the FOSDEM organizers (they put it on the FOSDEM web site):
>
> * activity title (please try to be descriptive, there are ~250 talks at
> FOSDEM during the week-end ;)),
> * a short abstract (1-2 paragraphs),
> * a longer description if appropriate,
> * optionally a list of links to the project website or similar
> * for each speaker:
> * the speaker's real name,
> * a short overview of her bio in a couple of lines,
> * optionally also a longer bio,
> * optionally a picture (please send it to us as 128x128 PNG),
> * optionally links to her website, blog, ...
>
> For examples, see:
> * http://archive.fosdem.org/2009/schedule/devrooms/freejava
> * http://archive.fosdem.org/2009/schedule/events/java_state_icedtea
> * http://archive.fosdem.org/2009/schedule/speakers/mark+reinhold

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Call for talks at our FOSDEM 2010 devroom (deadline 2010-01-03)

2009-12-04T16:09:05Z

Hi List,

FOSDEM is up in just 63 days and we have time until Sunday 2010-01-10
to finally submit the talks in our devroom to the FOSDEM organizers.
So I'd say we preferably finish our schedule until 2010-01-03 so that
the presenters have some time to turn in their abstracts, picture and
(optionally) bio for the presentation at the FOSDEM website. Until
the 3rd of January only 29 days are left.

I have set up a list of proposed talks the talks schedule at our
wiki: http://wiki.gnustep.org/index.php/FOSDEM_2010#Dev-
Room_Presentations_and_Events . I think we first should collect all
talk offers and then start scheduling.

So please send your proposals to the list or - even better - enter
them on the wiki page above. At first a title, a short summary,
proposed duration and a preffered time slot would do, so we can start
scheduling as soon as possible. The FOSDEM organizers strongly
recommend a granularity of 15 minute blocks. So if a talk is just 15
(lightning talk), 30 or 45 minutes long - fine!

As an advice: experience tells that 15 minutes are really short
(hence the moniker "lightning talk"). Usually such a lightning talk
is only sufficient when you want to put a single new feature into the
spotlight - let me give an example here: "There's now a GNOME theme
available for GNUstep" (hint for a talk!) or something along those
lines. 30 to 45 minutes are a good time for a full featured talk and
don't underestimate the time needed for a discussion afterwards.

Later I would need the following from the presenters for forwarding
it to the FOSDEM organizers (they put it on the FOSDEM web site):

* activity title (please try to be descriptive, there are ~250 talks at
FOSDEM during the week-end ;)),
* a short abstract (1-2 paragraphs),
* a longer description if appropriate,
* optionally a list of links to the project website or similar
* for each speaker:
* the speaker's real name,
* a short overview of her bio in a couple of lines,
* optionally also a longer bio,
* optionally a picture (please send it to us as 128x128 PNG),
* optionally links to her website, blog, ...

For examples, see:
* http://archive.fosdem.org/2009/schedule/devrooms/freejava
* http://archive.fosdem.org/2009/schedule/events/java_state_icedtea
* http://archive.fosdem.org/2009/schedule/speakers/mark+reinhold

regards,

Lars

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: So fast things can change - we got a FOSDEM devroom now! (was: Fwd: FOSDEM devroom request (GNUstep))

2009-12-04T15:49:49Z

Hi David,

I've added your proposals to http://wiki.gnustep.org/index.php/
FOSDEM_2010#List_of_submitted_talk_proposals

Am 04.12.2009 um 15:30 schrieb David Chisnall:

> On 2 Dec 2009, at 00:36, Lars Sonchocky-Helldorf wrote:
>
>> Great! all those are very interesting topics (for me at least but
>> I guess for others too).
>
> Well, probably other people get to speak too...
>
>> I already have prepared the talks schedule at our wiki: http://
>> wiki.gnustep.org/index.php/FOSDEM_2010#Dev-
>> Room_Presentations_and_Events . Currently I am a little bit unsure
>> if we first should collect all talk offers and then start
>> scheduling or if we start scheduling right away on a first come
>> first serve practice. I tend to collecting first and then
>> selecting and scheduling given the limited time (just one day or
>> eight hours) we have at our disposal.
>
> Can I have an afternoon slot? I might be awake in the morning, but
> I won't be coherent...

when does afternoon start for you? ;-)

I this will be posible of course but I can't give you final times as
of now.

>
> What sort of duration were you thinking for talks? I would imagine
> people will want to be dropping in and out a lot, so long talks
> probably won't work. Maybe 15 minutes + 5 for questions?

15 Minutes is a bit short I think. Experience from the years ago
shows that 30 to 45 minutes is a decent time for a talk, actually 15
Minutes talks are considered "lightning talks" at conferences (also
at fosdem: http://www.fosdem.org/2010/call_for_lightningtalks ) and
usually speakers have a hard time to make their points within those
15 minutes. I think your proposals would make good 30 to 45 minutes
talks (discussion time included). And People usually didn't drop out
of talks (they only did so if the presenter was unexperienced and
took to long to catch the peoples attention - like it happened to me).

>
> David
>
> -- Sent from my IBM 1620

regards,

Lars

Sent from my abacus ;-)

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: So fast things can change - we got a FOSDEM devroom now! (was: Fwd: FOSDEM devroom request (GNUstep))

2009-12-04T06:30:02Z

On 2 Dec 2009, at 00:36, Lars Sonchocky-Helldorf wrote:

> Great! all those are very interesting topics (for me at least but I
> guess for others too).

Well, probably other people get to speak too...

> I already have prepared the talks schedule at our wiki: http://wiki.gnustep.org/index.php/FOSDEM_2010#Dev-Room_Presentations_and_Events
> . Currently I am a little bit unsure if we first should collect all
> talk offers and then start scheduling or if we start scheduling
> right away on a first come first serve practice. I tend to
> collecting first and then selecting and scheduling given the limited
> time (just one day or eight hours) we have at our disposal.

Can I have an afternoon slot? I might be awake in the morning, but I
won't be coherent...

What sort of duration were you thinking for talks? I would imagine
people will want to be dropping in and out a lot, so long talks
probably won't work. Maybe 15 minutes + 5 for questions?

David

-- Sent from my IBM 1620

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Debugging GNUstep app

2009-12-04T05:16:27Z

Hi David,

>> I only see that the run loop catched an exception. This does not help
>> me a bit. I guess the exception was raised in a subthread.
>
> It shouldn't be. Exceptions should be caught in the thread that they
> are thrown. I'm not sure how they'd be moved between threads. If you
> want to see where an exception is thrown, add a breakpoint on
> -[NSException raise].

OK, I am receiving data on a socket in a subthread, then create a
NSNotification and teleport that to the main thread using
performSelectorOnMainThread:

NSNotification *notification = [NSNotification
notificationWithName:SRFileHandleReadCompletionNotification object:self
userInfo:((data) ? [NSDictionary dictionaryWithObject:data
forKey:SRFileHandleNotificationDataItem] : nil)];
[[NSNotificationCenter defaultCenter]
performSelectorOnMainThread:@selector(postNotification:)
withObject:notification waitUntilDone:YES];

gdb then gives me the following:

Thread 1 (process 84361 ):
#0 0xfe05a0b7 in _lwp_kill () from /lib/libc.so.1
#1 0xfe055814 in thr_kill () from /lib/libc.so.1
#2 0xfe001df3 in raise () from /lib/libc.so.1
#3 0xfdfe1c3d in abort () from /lib/libc.so.1
#4 0xfe308979 in _terminate () at NSException.m:686
#5 0xfe308b44 in _NSFoundationUncaughtExceptionHandler
(exception=0xae91bc8) at NSException.m:710
#6 0xfe3091db in -[NSException raise] (self=0xae91bc8,
_cmd=0xfef2f1a8) at NSException.m:841
#7 0xfecacaab in _NSAppKitUncaughtExceptionHandler
(exception=0xae91bc8) at NSApplication.m:142
#8 0xfe3091cd in -[NSException raise] (self=0xae91bc8,
_cmd=0xfe56cc68) at NSException.m:832
#9 0xfe3787d1 in -[NSRunLoop acceptInputForMode:beforeDate:]
(self=0x83536f8, _cmd=0xfe56ccd8, mode=0xfe56cd68, limit_date=0x94aca30)
at NSRunLoop.m:991
#10 0xfe378a46 in -[NSRunLoop runMode:beforeDate:] (self=0x83536f8,
_cmd=0xfef6f858, mode=0xfe56cd68, date=0x8366f70) at NSRunLoop.m:1043
#11 0xfee1b27f in -[GSDisplayServer(EventOps)
getEventMatchingMask:beforeDate:inMode:dequeue:] (self=0x8207528,
_cmd=0xfd9fbc60,
mask=4294967295, limit=0x8366f70, mode=0xfe56cd68, flag=1 '\001')
at GSDisplayServer.m:971
#12 0xfd9909b5 in -[XGServer(X11Ops)
getEventMatchingMask:beforeDate:inMode:dequeue:] (self=0x8207528,
_cmd=0xfef2f178, mask=4294967295,
limit=0x8366f70, mode=0xfe56cd68, flag=1 '\001') at
XGServerEvent.m:2354
#13 0xfecb255e in DPSGetEvent (ctxt=0x8207528, mask=4294967295,
limit=0x8366f70, mode=0xfe56cd68) at GSDisplayServer.h:180
#14 0xfecb2db5 in -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] (self=0x81fc3f8,
_cmd=0xfef2f3c8, mask=4294967295,
expiration=0x8366f70, mode=0xfe56cd68, flag=1 '\001') at
NSApplication.m:2008
#15 0xfecb171d in -[NSApplication run] (self=0x81fc3f8,
_cmd=0xfef2a968) at NSApplication.m:1452
#16 0xfec96648 in NSApplicationMain (argc=1, argv=0x8047738) at
Functions.m:72
#17 0x08052242 in main (argc=1, argv=0x8047738, env=0x8047740) at
SOObjectBrowser_main.m:35

The exception is raised in NSData::subdataWithRange due to an invalid
specified range. Unfortunatelly the above back trace gives me no hint
where exactly the error is raised, not even that is was in NSData.m. I
only know that from NSException::reason. No clue, who is sending this
invalid data packet and posts it to the main thread!?

The other thread looks like so:

Thread 2 (process 80431497 ):
#0 0xfe05738b in __lwp_park () from /lib/libc.so.1
#1 0xfe0519d3 in cond_sleep_queue () from /lib/libc.so.1
#2 0xfe051b8c in cond_wait_queue () from /lib/libc.so.1
#3 0xfe052060 in _cond_wait () from /lib/libc.so.1
#4 0xfe0520a2 in cond_wait () from /lib/libc.so.1
#5 0xfe0520db in pthread_cond_wait () from /lib/libc.so.1
#6 0xfe59ef63 in __objc_condition_wait (condition=0x4, mutex=0x4) at
../gcc/gthr-posix.h:426
#7 0xfe59e826 in objc_condition_wait (condition=0x8a955b8,
mutex=0xbf48308) at /usr/share/src/gcc-3.4.4/libobjc/thr.c:493
#8 0xfe333757 in -[NSConditionLock lockWhenCondition:]
(self=0xaebac00, _cmd=0xfe571fb0, value=1) at NSLock.m:348
#9 0xfe3a1093 in -[NSObject(NSMainThreadPerformAdditions)
performSelectorOnMainThread:withObject:waitUntilDone:modes:]
(self=0x80cb288,
_cmd=0xfe571fc0, aSelector=0xfe931948, anObject=0xaee42c8, aFlag=1
'\001', anArray=0x8319478) at NSThread.m:1075
#10 0xfe3a1160 in -[NSObject(NSMainThreadPerformAdditions)
performSelectorOnMainThread:withObject:waitUntilDone:] (self=0x80cb288,
_cmd=0xfe931958, aSelector=0xfe931948, anObject=0xaee42c8, aFlag=1
'\001') at NSThread.m:1093
#11 0xfe8dff24 in -[SRFileHandle _readInBackgroundAndNotifyThread]
(self=0x8b5dad8, _cmd=0xfe931980) at SRFileHandle.m:612
#12 0xfe3477db in -[NSObject performSelector:withObject:]
(self=0x8b5dad8, _cmd=0xfe571f00, aSelector=0xfe931980, anObject=0x0)
at NSObject.m:1947
#13 0xfe3a0492 in -[NSThread _sendThreadMethod] (self=0xa471040,
_cmd=0xfe571ee0) at NSThread.m:780
#14 0xfe59e67c in __objc_thread_detach_function (istate=0x4) at
/usr/share/src/gcc-3.4.4/libobjc/thr.c:106
#15 0xfe057045 in _thr_setup () from /lib/libc.so.1
#16 0xfe057330 in L3_doit () from /lib/libc.so.1
#17 0xfd580a00 in ?? ()
#18 0x00000000 in ?? ()

I learn that -[SRFileHandle _readInBackgroundAndNotifyThread] sends
then notification to the mainthread that causes trouble. But the
problem happens only in 1 of 100 times and the above traces give me no
further clue!

>> Any chance I can get a backtrace from a subthread in gdb? This might
>> be a dummy/newbie question but I have never done that and figured out
>> how this would work. Is that possible?
>
> If it is related to threads, then 'info threads' will list the
> currently running threads and then thread {number} will switch gdb to
> showing the numbered thread.

I have a clue what went wrong ...

Thanks for your "swithing thread" hint!

Regards,

Andreas

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Debugging GNUstep app

2009-12-04T05:01:58Z

On 4 Dec 2009, at 10:41, Andreas Höschler wrote:

> Hi all,
>
> my app core dumps under certain circumstances. When I open the core
> file with gdb and enter
>
> bt
>
> I only see that the run loop catched an exception. This does not
> help me a bit. I guess the exception was raised in a subthread.

It shouldn't be. Exceptions should be caught in the thread that they
are thrown. I'm not sure how they'd be moved between threads. If you
want to see where an exception is thrown, add a breakpoint on -
[NSException raise].

> Any chance I can get a backtrace from a subthread in gdb? This might
> be a dummy/newbie question but I have never done that and figured
> out how this would work. Is that possible?

If it is related to threads, then 'info threads' will list the
currently running threads and then thread {number} will switch gdb to
showing the numbered thread.

David

-- Sent from my Cray X1

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Debugging GNUstep app

2009-12-04T03:33:53Z

Hi all,

> my app core dumps under certain circumstances. When I open the core
> file with gdb and enter
>
> bt
>
> I only see that the run loop catched an exception. This does not help
> me a bit. I guess the exception was raised in a subthread. Any chance
> I can get a backtrace from a subthread in gdb? This might be a
> dummy/newbie question but I have never done that and figured out how
> this would work. Is that possible?

Sorry for the noise:

thread apply all bt

It did not help me in my case, but may be next time.

Thanks,

Andreas

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Debugging GNUstep app

2009-12-04T02:41:12Z

Hi all,

my app core dumps under certain circumstances. When I open the core
file with gdb and enter

bt

I only see that the run loop catched an exception. This does not help
me a bit. I guess the exception was raised in a subthread. Any chance I
can get a backtrace from a subthread in gdb? This might be a
dummy/newbie question but I have never done that and figured out how
this would work. Is that possible?

Thanks a lot,

Andreas

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Standard Framework Locations

2009-12-03T11:21:45Z

Hi,

I'm not very well versed in GNUStep but I do have a problem trying to
implement some software that uses it. Here's the environment:

OS......: NetBSD 5 Stable (i386)
PACKAGES:
gnustep-base-1.18.0 GNUstep foundation classes
gnustep-make-2.0.8nb3 GNUstep makefile package
gnustep-objc-1.6.0nb2 Objective-C runtime
gnustep-gui-0.16.0nb1 GNUstep AppKit Implementation

These packages were build from "pkgsrc" on NetBSD. I'm trying to get the
"SOGo" (scalable open groupware) system to work properly. Upon starting
the daemon, I get the following message...

2009-12-03 14:11:22.859 sogod[12662] File NSBundle.m: 672. In [NSBundle
+_addFrameworkFromClass:] Could not find framework SOGo in any standard
location

... So the big question is: What are the "standard locations" for
frameworks and how can they be configured?

The missing framework is in /usr/pkg/lib/GNUstep/SOGo/SOGo.framework.

Below are the settings from /etc/GNUstep.conf (which is sourced before
starting the daemon in question). Please let me know if I can provide
more information. Thanks!

Louis

$ grep "^[^\#$]" /etc/GNUstep.conf

GNUSTEP_SYSTEM_ROOT=/usr/pkg/System
GNUSTEP_LOCAL_ROOT=/usr/pkg/Local
GNUSTEP_NETWORK_ROOT=/usr/pkg/Network
GNUSTEP_USER_CONFIG_FILE=.GNUstep.conf
GNUSTEP_USER_DIR=GNUstep
GNUSTEP_USER_DEFAULTS_DIR=GNUstep/Defaults
GNUSTEP_MAKEFILES=/usr/pkg/share/GNUstep/Makefiles
GNUSTEP_SYSTEM_USERS_DIR=/home
GNUSTEP_NETWORK_USERS_DIR=/home
GNUSTEP_LOCAL_USERS_DIR=/home
GNUSTEP_SYSTEM_APPS=/usr/pkg/lib/GNUstep/Applications
GNUSTEP_SYSTEM_ADMIN_APPS=/usr/pkg/lib/GNUstep/Applications
GNUSTEP_SYSTEM_WEB_APPS=/usr/pkg/lib/GNUstep/WebApplications
GNUSTEP_SYSTEM_TOOLS=/usr/pkg/bin
GNUSTEP_SYSTEM_ADMIN_TOOLS=/usr/pkg/sbin
GNUSTEP_SYSTEM_LIBRARY=/usr/pkg/lib/GNUstep
GNUSTEP_SYSTEM_HEADERS=/usr/pkg/include
GNUSTEP_SYSTEM_LIBRARIES=/usr/pkg/lib
GNUSTEP_SYSTEM_DOC=/usr/pkg/share/GNUstep/Documentation
GNUSTEP_SYSTEM_DOC_MAN=/usr/pkg/man
GNUSTEP_SYSTEM_DOC_INFO=/usr/pkg/info
GNUSTEP_NETWORK_APPS=/usr/pkg/lib/GNUstep/Applications
GNUSTEP_NETWORK_ADMIN_APPS=/usr/pkg/lib/GNUstep/Applications
GNUSTEP_NETWORK_WEB_APPS=/usr/pkg/lib/GNUstep/WebApplications
GNUSTEP_NETWORK_TOOLS=/usr/pkg/bin
GNUSTEP_NETWORK_ADMIN_TOOLS=/usr/pkg/sbin
GNUSTEP_NETWORK_LIBRARY=/usr/pkg/lib/GNUstep
GNUSTEP_NETWORK_HEADERS=/usr/pkg/include
GNUSTEP_NETWORK_LIBRARIES=/usr/pkg/lib
GNUSTEP_NETWORK_DOC=/usr/pkg/share/GNUstep/Documentation
GNUSTEP_NETWORK_DOC_MAN=/usr/pkg/man
GNUSTEP_NETWORK_DOC_INFO=/usr/pkg/info
GNUSTEP_LOCAL_APPS=/usr/pkg/lib/GNUstep/Applications
GNUSTEP_LOCAL_ADMIN_APPS=/usr/pkg/lib/GNUstep/Applications
GNUSTEP_LOCAL_WEB_APPS=/usr/pkg/lib/GNUstep/WebApplications
GNUSTEP_LOCAL_TOOLS=/usr/pkg/bin
GNUSTEP_LOCAL_ADMIN_TOOLS=/usr/pkg/sbin
GNUSTEP_LOCAL_LIBRARY=/usr/pkg/lib/GNUstep
GNUSTEP_LOCAL_HEADERS=/usr/pkg/include
GNUSTEP_LOCAL_LIBRARIES=/usr/pkg/lib
GNUSTEP_LOCAL_DOC=/usr/pkg/share/GNUstep/Documentation
GNUSTEP_LOCAL_DOC_MAN=/usr/pkg/man
GNUSTEP_LOCAL_DOC_INFO=/usr/pkg/info
GNUSTEP_USER_DIR_APPS=GNUstep/Applications
GNUSTEP_USER_DIR_ADMIN_APPS=GNUstep/Applications/Admin
GNUSTEP_USER_DIR_WEB_APPS=GNUstep/WebApplications
GNUSTEP_USER_DIR_TOOLS=GNUstep/Tools
GNUSTEP_USER_DIR_ADMIN_TOOLS=GNUstep/Tools/Admin
GNUSTEP_USER_DIR_LIBRARY=GNUstep/Library
GNUSTEP_USER_DIR_HEADERS=GNUstep/Library/Headers
GNUSTEP_USER_DIR_LIBRARIES=GNUstep/Library/Libraries
GNUSTEP_USER_DIR_DOC=GNUstep/Library/Documentation
GNUSTEP_USER_DIR_DOC_MAN=GNUstep/Library/Documentation/man
GNUSTEP_USER_DIR_DOC_INFO=GNUstep/Library/Documentation/info

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: What is needed to run a tool like a daemon?

2009-12-03T00:23:43Z

On 3 Dec 2009, at 08:04, Saso Kiselkov wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sure it's unportable, which is why I always include a custom
> implementation of daemon() with my code which works on most *nixes :-).

Using NSTask works on ms-windows as well. Of course, you can implement your own daemon using NSTask.

> After reading the message though I realize I misunderstood it.
>
> What's most likely screwing up is that the process doesn't de-register
> from the name server. Maybe a simple atexit() or signal() handler would
> do the trick.

That shouldn't really matter ... the nameserver code is designed to handle the case where something kills a process and prevents it from deregistering its name.

> German: you do try this as a test whether the name is being unregistered:

Unfortunately testing that is not useful ... what needs to be determined is why the name can't be registered.

Normally the directory to look at is /tmp/GNUstepXXX/NSMessagePort where XXX is your user ID

There is a subdirectory 'names' containing files for registered names ... the name of each file is a base64 encoded port name. The content of each file is the port identifier.

There is a subdirectory 'ports' containing named pipes for each port. The port names are of the port pid.sequence where pid is a process id and sequence is a sequence number for when a process uses multiple ports.

For registration to fail, the name file must point to a port file which has a process listening on it (ie the port must still be in use).

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: What is needed to run a tool like a daemon?

2009-12-03T00:04:48Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sure it's unportable, which is why I always include a custom
implementation of daemon() with my code which works on most *nixes :-).
After reading the message though I realize I misunderstood it.

What's most likely screwing up is that the process doesn't de-register
from the name server. Maybe a simple atexit() or signal() handler would
do the trick.

German: you do try this as a test whether the name is being unregistered:

void
dereg_name (void)
{
// deregistration code here
...

// to make sure we know that deregistration succeeded
// even when we have no controlling terminal
FILE *fp = fopen ("/tmp/test_dereg", "wb");
fprintf (fp, "Deregistered name\n");
fclose (fp);
}

void
handle_sig (int signum)
{
exit (EXIT_SUCCESS);
}

int
main (int argc, char *argv[])
{
...
signal (SIGINT, handle_sig);
signal (SIGTERM, handle_sig);
atexit (dereg_name);
...
}

I hope I'm not completely missing the point again...

BR,
- --
Saso

Richard Frith-Macdonald wrote:

> On 3 Dec 2009, at 07:34, Saso Kiselkov wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> And what's stopping you from simply forking into the background? Like
>> with the following:
>>
>> if (daemon (0, 0) == -1)
>> {
>> NSLog (@"Error daemonizing: %s", strerror (errno));
>> exit (EXIT_FAILURE);
>> }
>
> I don't think that addresses the issue of registering a name.
>
> Perhaps more importantly though, the code above has the problem of 'daemon()' being severely unportable.
>
> In GNUstep you should use NSTask to portably create a subprocess.
>
> The gdnc tool (base/Tools/gdnc.m) provides an example of a process which makes itsself be a daemon in a portable manner.
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksXcSAACgkQRO8UcfzpOHD8MwCeMSjpTYs2gCCTMaAvB2OlJlha
vPAAoL3mHpd/LnAHFyqmrKX0BEReKxmo
=7c/V
-----END PGP SIGNATURE-----

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: What is needed to run a tool like a daemon?

2009-12-02T23:55:17Z

On 3 Dec 2009, at 07:34, Saso Kiselkov wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> And what's stopping you from simply forking into the background? Like
> with the following:
>
> if (daemon (0, 0) == -1)
> {
> NSLog (@"Error daemonizing: %s", strerror (errno));
> exit (EXIT_FAILURE);
> }

I don't think that addresses the issue of registering a name.

Perhaps more importantly though, the code above has the problem of 'daemon()' being severely unportable.

In GNUstep you should use NSTask to portably create a subprocess.

The gdnc tool (base/Tools/gdnc.m) provides an example of a process which makes itsself be a daemon in a portable manner.

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: What is needed to run a tool like a daemon?

2009-12-02T23:36:43Z

On 3 Dec 2009, at 06:35, Germán Arias wrote:

> As you know I'm working on GSTaskBar. Until now I run GSTB from a
> terminal. But when I try start this tool in my .profile file (where I
> start gbps and gdnc) I can not start my session. The error occurs
> because GSTB can't register with the name GSTaskBar.

I know of three reasons for failure to register a name:

1. the name is already registered to another connection.
2. the temporary files used for name registration have had their ownership or access permissions changed so that your process can't access them.
3. the app is using inter-host connections, and the nameserver (gdomap) is not running and can't be auto-started for some reason (eg access permissions).
4. the app is using inter-host connections, and gdomap has the name registered to another process (A) which died without unregistering, and another process (B) is running which happens to have the same process ID that A had (in this case gdomap can't tell that the name is no longer in use by A, because it will check the running process IDs and think that A is still running because it sees a process with the ID its expecting).

I guess 3 and 4 should not be the case (your code sample shows you have not chosen to use inter-host connections). Reason 2 would seem almost impossible to happen without you knowing you had reprotected the files.

> I need to delete
> the file /tmp/.X0-lock and type: startx. This start my session. After
> this, the process GSTB is running and work fine. Then, why I get this
> error?

That sounds like you have some X issue, then ... nothing to do with registering the name.

> Basically I have something like
>
> NSAutoreleasePool *pool;
> GSTaskBar *gsbar;
> NSConnection *conn;
>
> pool = [NSAutoreleasePool new];
> gsbar = [GSTaskBar new];
> conn = [NSConnection defaultConnection];
> [conn setRootObject: gsbar];
>
> if (![conn registerName: @"GSTaskBar"])
> {
> NSLog (@"Could not register us as GSTaskBar");
> exit (1);
> }

You can run with -GNU-Debug=NSMessagePort to get some debug output about registering the name for the port.
If that's not helpful,probably you should try adding a load of NSLog statements to your code (and in the libraries) to try to see what's going on.

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: What is needed to run a tool like a daemon?

2009-12-02T23:34:22Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

And what's stopping you from simply forking into the background? Like
with the following:

if (daemon (0, 0) == -1)
{
NSLog (@"Error daemonizing: %s", strerror (errno));
exit (EXIT_FAILURE);
}

BR,
- --
Saso

Germán Arias wrote:

> As you know I'm working on GSTaskBar. Until now I run GSTB from a
> terminal. But when I try start this tool in my .profile file (where I
> start gbps and gdnc) I can not start my session. The error occurs
> because GSTB can't register with the name GSTaskBar. I need to delete
> the file /tmp/.X0-lock and type: startx. This start my session. After
> this, the process GSTB is running and work fine. Then, why I get this
> error? Basically I have something like
>
> NSAutoreleasePool *pool;
> GSTaskBar *gsbar;
> NSConnection *conn;
>
> pool = [NSAutoreleasePool new];
> gsbar = [GSTaskBar new];
> conn = [NSConnection defaultConnection];
> [conn setRootObject: gsbar];
>
> if (![conn registerName: @"GSTaskBar"])
> {
> NSLog (@"Could not register us as GSTaskBar");
> exit (1);
> }
>
> NSLog (@"Server registered - waiting for connections...");
> [[NSRunLoop currentRunLoop] run];
>
> if I start this tool at the beginning of my session (with the tool of
> gnome to do this) this work fine. But... I would like start this
> together gpbs and gdnc. Greetings.
>
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@...
> http://lists.gnu.org/mailman/listinfo/discuss-gnustep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAksXaf0ACgkQRO8UcfzpOHBSkQCdHNExYRyabwlvRPhB7T0nw+iJ
woIAn0dEokvR/zcnuQknulnhMp9eouyJ
=PkZP
-----END PGP SIGNATURE-----

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

What is needed to run a tool like a daemon?

2009-12-02T22:35:08Z

As you know I'm working on GSTaskBar. Until now I run GSTB from a
terminal. But when I try start this tool in my .profile file (where I
start gbps and gdnc) I can not start my session. The error occurs
because GSTB can't register with the name GSTaskBar. I need to delete
the file /tmp/.X0-lock and type: startx. This start my session. After
this, the process GSTB is running and work fine. Then, why I get this
error? Basically I have something like

NSAutoreleasePool *pool;
GSTaskBar *gsbar;
NSConnection *conn;

pool = [NSAutoreleasePool new];
gsbar = [GSTaskBar new];
conn = [NSConnection defaultConnection];
[conn setRootObject: gsbar];

if (![conn registerName: @"GSTaskBar"])
{
NSLog (@"Could not register us as GSTaskBar");
exit (1);
}

NSLog (@"Server registered - waiting for connections...");
[[NSRunLoop currentRunLoop] run];

if I start this tool at the beginning of my session (with the tool of
gnome to do this) this work fine. But... I would like start this
together gpbs and gdnc. Greetings.

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: So fast things can change - we got a FOSDEM devroom now! (was: Fwd: FOSDEM devroom request (GNUstep))

2009-12-01T23:09:03Z

On 1 Dez., 23:05, Lars Sonchocky-Helldorf <lars.sonchocky-
helld...@...> wrote:

> Hi list,
>
> I received the attached e-mail some minutes ago. Whatever magic
> happened here - we suddenly got a devroom - yay!
>
> It's just for one day (Sunday 7th February from 09:00 to 17:00) but
> that's way better than nothing. And our devroom is now also listed here:
>
> http://www.fosdem.org/2010/list-devrooms-their-call-talks
>
> So sorry for all the turmoil caused and many thanks to the unknown
> person who made this possible finally.
>
> We can (should) start thinking about our schedule (the deadline for
> the full schedule submission is 2010-01-10) and I am a happy camper now.
>
> regards,
>
> Lars
>
> Anfang der weitergeleiteten E-Mail:
>
>
>
> > Von: Mattias 'Tias' Guns <mg...@...>
> > Datum: 1. Dezember 2009 22:18:15 MEZ
> > An: Lars Sonchocky-Helldorf <lars.sonchocky-helld...@...>
> > Kopie: Fosdem Developer Rooms <devro...@...>
> > Betreff: Re: FOSDEM devroom request (GNUstep)
>
> > Hello Lars,
>
> > Yeah, there are quite some notifications to sent around ; )
>
> > But we have good news for you: your request has been accepted !
>
> > We will put the following at your disposal:
> > - room AW1.117 with 31 seats,
> > - a video projector with VGA cable,
> > - wireless internet,
> > for 1 day, on Sunday 7th February from 09:00 to 17:00
>
> > If you prefer to decline this offer, please inform us as soon as
> > possible.
>
> > The hours listed above are the schedulable hours. We recommend to plan
> > the first 15min or so with a little welcome talk so you can prepare
> > the
> > first "real" speaker (network, connect to video projector, etc...). We
> > can also open the room a bit earlier for preparations. We expect the
> > rooms to be empty 30 minutes after the last talk.
>
> > For stocking material overnight, we have a large room that will be
> > locked from Saturday 18:00 to Sunday 09:00. However, there is no
> > insurance whatsoever and we take no responsibility for stolen or
> > damaged
> > goods, even though there is a security team at the venue, including
> > during the night.
>
> > Devroom schedule:
> > ~~~~~~~~~~~~~~~~~
> > You are free to manage the schedule inside your devroom as you wish
> > and
> > plan talks, hacking sessions, BoF discussions, whatever. But always
> > keep
> > in mind that FOSDEM is a FOSS community event, organized by the
> > community
> > for the community. We're a non-profit organization and don't accept
> > vendor talks. So make sure that the stuff that will take place in your
> > room is strongly related to FOSS projects and communities. (I guess
> > that's obvious for everyone but well.. ;)
>
> > We're asking you to send us the following information about your
> > schedule, in order for us to add it to our website and for visitors
> > to see.
>
> > For every session, we will need:
> > * start time and duration (in 15 minute blocks -- please stick with
> > that granularity, as it will make the schedule somewhat easier to
> > follow for visitors),
> > * activity title (please try to be descriptive, there are ~250
> > talks at
> > FOSDEM during the week-end ;)),
> > * a short abstract (1-2 paragraphs),
> > * a longer description if appropriate,
> > * optionally a list of links to the project website or similar
> > * for each speaker:
> > * the speaker's real name,
> > * a short overview of her bio in a couple of lines,
> > * optionally also a longer bio,
> > * optionally a picture (please send it to us as 128x128 PNG),
> > * optionally links to her website, blog, ...
>
> > For examples, see:
> > *http://archive.fosdem.org/2009/schedule/devrooms/freejava
> > *http://archive.fosdem.org/2009/schedule/events/java_state_icedtea
> > *http://archive.fosdem.org/2009/schedule/speakers/mark+reinhold
>
> > Send that information either in a plain text email or with a text file
> > attached to an email. The easiest for us is to have that data in the
> > following form, e.g.:
> > --->8----------------------------------------------------------------
> > John Doe
> > john....@...
>
> > John is currently working as a freelancer and spends most of his free
> > time contributing to various opensource projects, most prominently on
> > libjohndoe.
>
> > John currently lives in England with his wife, 2 kids and a bunch of
> > kitten. He loves spending his time walking around in the woods, and
> > of course kitten. He has a masters degree in kitten science, which
> > helps him a lot with coding.
>
> > blog:http://johndoe.example.org/blog/
> > attached: john_doe.png
>
> > ---
>
> > Kitten cooking with libjohndoe
>
> > libjohndoe is a high performance library that can be used for various
> > purposes, and most prominently to cook kitten.
>
> > John will present the internals of his pet project, libjohndoe, and
> > how its API has evolved from a kitten shop into a cantonese
> > restaurant management platform along the years.
> > He will also make a demo of its newest feature.
>
> >http://johndoe.example.org/libjohndoe/
> >http://johndoe.example.org/blog/tags/libjohndoe
>
> > --------------------------------------------------
>
> > Jane Hackerton
> > miss.j...@...
> > ...
> > --->8----------------------------------------------------------------
> > (the number of dashes and such doesn't matter, it isn't automated, but
> > a format like the above would be perfect for us)
>
> > Please, pretty please, try to stick to what we are asking above, as
> > it will make our life a lot easier when we will have to hack 250 talks
> > into our content management system.
>
> > Note that the information above will be available both on our website
> > and in the free program folder we distribute to the visitors.
>
> > Call for talks:
> > ~~~~~~~~~~~~~~~
> > We want to host a list of all accepted devrooms with links to their
> > call for talks on our site. We believe this can help potential
> > speakers
> > find the way to the most relevant devroom. We (FOSDEM) also organize
> > lightning talks (15 min talks) and as every year, we will forward talk
> > requests that better fit your devroom to you.
> > Please send us a link to your call for talks as soon you publish it
> > on your project's website.
>
> > Deadlines:
> > ~~~~~~~~~~
> > The deadline for the full schedule submission is 2010-01-10
>
> > The earlier you send us the data, even if incomplete, the easier it is
> > for us, and the earlier it will be online on our site.
> > We would recommend you to send talk acceptance notifications before
> > 2009-12-31 to the contributors of your project -- that would leave you
> > with plenty of time to poke speakers again and again for sending you
> > the required data ;)
> > As an example, the lightningtalk request deadline is 2009-12-20 with
> > acceptance notification on 2009-12-28.
>
> > Some conditions we need to agree on:
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > For us, you are the devroom responsible. This means that we will
> > communicate everything through you, and you will be the one we will
> > poke for information ;)
>
> > Also, during the weekend, we want you to do good housekeeping of the
> > room:
> > - we will offer trash bags for the garbage, there should not be any
> > garbage lying around in the room when you leave,
> > - there is a limit on the room capacity that can not be exceeded (by
> > much).
>
> > Please understand that we are a non for profit association, and that
> > every single organization team member works on FOSDEM during her
> > spare time. As such, it would be very nice if we didn't have to spend
> > several hours cleaning up the devrooms, and it is just a very small
> > amount of work for the attendees to put their garbage into the trash
> > bags.
>
> > Two years ago there were some rooms that were extremely overcrowded,
> > and apart from the obvious risks regarding the security of the
> > attendees, doing so is the most effective way of killing the event as
> > any inspection by the university and/or the fire department would get
> > us thrown out for good.
>
> > We cannot provide every single project with large rooms and over-
> > abundent seating, so if the room has reached its full capacity, please
> > ask additional people to stay out and enjoy another talk -- there are
> > plenty to choose from.
> > As last year, we will provide you with signs to put on the doors of
> > the
> > devrooms to signify that the room is full (or not).
>
> > And, of course, if you have any questions, please contact us at
> > devro...@...
>
> > On behalf of the FOSDEM devroom team,
> > Tias
>
> > Lars Sonchocky-Helldorf wrote:
> >> I didn't receive any notification as of now. Has our request been
> >> accepted or rejected?
> >> thanks,
> >> Lars
> >> Am 21.11.2009 um 15:44 schrieb Mattias 'Tias' Guns:
> >>> Hello Lars,
>
> >>> Thank you for your devroom request. We received it well and it
> >>> has been added to the pool of candidates.
> >>> The acceptance notification will be sent around on 2009-11-29.
>
> >>> Kind regards,
> >>> Tias
> >>> FOSDEM organizer
>
> >>> Planet GNUstep - a collaboration of GNUstep related projects wrote:
> >>>> Submitted on 11/21/2009 - 02:40
> >>>> Submitted by anonymous user: [213.9.34.100]
> >>>> Submitted values are:
> >>>> Developer Room:
> >>>> devroom name: Planet GNUstep - a collaboration of GNUstep
> >>>> related projects
> >>>> devroom description:
> >>>> participating projects:
> >>>> - GNUstep
> >>>> GNUstep is a free, object-oriented, cross-platform, OpenStep/
> >>>> Cocoa API compatible framework and development environment.
> >>>> - Étoilé
> >>>> Étoilé is an innovative GNUstep based user environment
> >>>> designed from the ground up around the things people do with
> >>>> computers: create, collaborate, and learn.
> >>>> - GAP - the GNUstep Application Project
> >>>> The GNUstep Application Project provides a comprehensive set
> >>>> of administration and user level tools to make using GNUstep
> >>>> based environments a very pleasant experience. Part of the
> >>>> charter of this project is not only to write new tools, but also
> >>>> to port existing NeXTSTEP/OPENSTEP/Cocoa applications to GNUstep
> >>>> as well.
> >>>> - QuantumSTEP / mySTEP
> >>>> QuantumSTEP is a Mac-like Application Platform that can be
> >>>> installed on existing mobile Linux devices (Openmoko, Zaurus,
> >>>> Letux, ...)
>
> ...
>

Great news!

Nikolaus
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: FOSDEM 2010 devroom list is available

2009-12-01T23:07:31Z

On 1 Dez., 22:54, David Chisnall <thera...@...> wrote:

> On 1 Dec 2009, at 18:52, h...@... wrote:
>
> > I think it is not well known that there is also an offer from Mike
> > Dexter fromwww.linuxfund.orgto sponsor GNUstep to reach more
> > stability and visibility. Unfortunately the discussion has ceased.
> > IMHO, this is a great opportunity to really invite (i.e. subsidize
> > some travel expenses and hotel cost) to a series of Hacking meetings.
> > And by having a series of such meetings, we could set up a "to do
> > list", assign tasks and report progress (to Linux Funds and the
> > public). It will be a little painful to go through this initially
> > since we all are individualistic volunteers, but IMHO it will help the
> > whole project especially if we don't have the FOSDEM devroom&stand any
> > more.
>
> That's the first I've heard of this, but I'd be interested in
> applying. Are the conditions and procedures for applying documented
> somewhere?

I had met Michael several times during FOSDEM and last time at
LinuxTag 2009. I think he is now in contact with Gregory.

Nikolaus
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

New SystemPreferences and Gorm installers to Windows

2009-12-01T17:37:52Z

Available the installers of SystemPreferences-1.1.0 and Gorm-1.2.10 to
Windows (0.23.x series)

http://www.gnustep.org/experience/Windows.html

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: So fast things can change - we got a FOSDEM devroom now! (was: Fwd: FOSDEM devroom request (GNUstep))

2009-12-01T16:36:18Z

Am 02.12.2009 um 00:53 schrieb David Chisnall:

> On 1 Dec 2009, at 22:05, Lars Sonchocky-Helldorf wrote:
>
>> We can (should) start thinking about our schedule (the deadline
>> for the full schedule submission is 2010-01-10) and I am a happy
>> camper now.
>
>
> I plan on being there and could give a talk (or more than one if
> people aren't too bored by the first one). Things I could talk about:
>
> - Objective-C 2: libobjc2 and Clang, current status, plans for the
> future.
>
> - Étoilé: Where it is, where it's going, why it isn't there yet.
>
> - LanguageKit: Supporting other dynamic languages on the ObjC runtime.
>
> I could also do a more general talk on porting Cocoa apps to other
> platforms - what works, what doesn't, what to do to make porting
> easier.

Great! all those are very interesting topics (for me at least but I
guess for others too).

I already have prepared the talks schedule at our wiki: http://
wiki.gnustep.org/index.php/FOSDEM_2010#Dev-
Room_Presentations_and_Events . Currently I am a little bit unsure if
we first should collect all talk offers and then start scheduling or
if we start scheduling right away on a first come first serve
practice. I tend to collecting first and then selecting and
scheduling given the limited time (just one day or eight hours) we
have at our disposal.

>
> David
>
> -- Send from my Jacquard Loom

greetings,

Lars

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: So fast things can change - we got a FOSDEM devroom now! (was: Fwd: FOSDEM devroom request (GNUstep))

2009-12-01T15:53:06Z

On 1 Dec 2009, at 22:05, Lars Sonchocky-Helldorf wrote:

> We can (should) start thinking about our schedule (the deadline for
> the full schedule submission is 2010-01-10) and I am a happy camper
> now.

I plan on being there and could give a talk (or more than one if
people aren't too bored by the first one). Things I could talk about:

- Objective-C 2: libobjc2 and Clang, current status, plans for the
future.

- Étoilé: Where it is, where it's going, why it isn't there yet.

- LanguageKit: Supporting other dynamic languages on the ObjC runtime.

I could also do a more general talk on porting Cocoa apps to other
platforms - what works, what doesn't, what to do to make porting easier.

David

-- Send from my Jacquard Loom

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Need help about autogsdoc messages

2009-12-01T14:58:49Z

Hallo Jochen,

I do not fully understand your problem. What you post are non-fatal
warnings. I get some of them too when I build the base documentaiton,
but the documentation gets built fine.
Do you have any hard error (like pieces missing or being wrong) or are
you just worried about that output.

Furthermore I do not follow your comment about "gnustep-base" was not
installed.
Do you refer as building the rpm for a first time and getting those
errors compared to building it, installing it and rebuilding it a second
time and seeing less errors/warnings?

I do maintain a set of RPMs myself. I do not build the documentation,
but for the rest I do not have any particular problem.

Thank you,
Riccardo

Jochen Schmitt wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> <cut>
>

> This kinds of error seems only occurs, if gnustep-base was not
> installed on the
> build machine. So I want to ask, how I can solve this issue.
>
> The full build log you may find at
>
> http://www.herr-schmitt.de/pub/gnustep-base/output
>
> Best Regards:
>
> Jochen Schmitt
>

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

So fast things can change - we got a FOSDEM devroom now! (was: Fwd: FOSDEM devroom request (GNUstep))

2009-12-01T14:05:55Z

Hi list,

I received the attached e-mail some minutes ago. Whatever magic
happened here - we suddenly got a devroom - yay!

It's just for one day (Sunday 7th February from 09:00 to 17:00) but
that's way better than nothing. And our devroom is now also listed here:

http://www.fosdem.org/2010/list-devrooms-their-call-talks

So sorry for all the turmoil caused and many thanks to the unknown
person who made this possible finally.

We can (should) start thinking about our schedule (the deadline for
the full schedule submission is 2010-01-10) and I am a happy camper now.

regards,

Lars

Anfang der weitergeleiteten E-Mail:

> Von: Mattias 'Tias' Guns <mguns@...>
> Datum: 1. Dezember 2009 22:18:15 MEZ
> An: Lars Sonchocky-Helldorf <lars.sonchocky-helldorf@...>
> Kopie: Fosdem Developer Rooms <devrooms@...>
> Betreff: Re: FOSDEM devroom request (GNUstep)
>
> Hello Lars,
>
> Yeah, there are quite some notifications to sent around ; )
>
> But we have good news for you: your request has been accepted !
>
> We will put the following at your disposal:
> - room AW1.117 with 31 seats,
> - a video projector with VGA cable,
> - wireless internet,
> for 1 day, on Sunday 7th February from 09:00 to 17:00
>
> If you prefer to decline this offer, please inform us as soon as
> possible.
>
> The hours listed above are the schedulable hours. We recommend to plan
> the first 15min or so with a little welcome talk so you can prepare
> the
> first "real" speaker (network, connect to video projector, etc...). We
> can also open the room a bit earlier for preparations. We expect the
> rooms to be empty 30 minutes after the last talk.
>
> For stocking material overnight, we have a large room that will be
> locked from Saturday 18:00 to Sunday 09:00. However, there is no
> insurance whatsoever and we take no responsibility for stolen or
> damaged
> goods, even though there is a security team at the venue, including
> during the night.
>
> Devroom schedule:
> ~~~~~~~~~~~~~~~~~
> You are free to manage the schedule inside your devroom as you wish
> and
> plan talks, hacking sessions, BoF discussions, whatever. But always
> keep
> in mind that FOSDEM is a FOSS community event, organized by the
> community
> for the community. We're a non-profit organization and don't accept
> vendor talks. So make sure that the stuff that will take place in your
> room is strongly related to FOSS projects and communities. (I guess
> that's obvious for everyone but well.. ;)
>
> We're asking you to send us the following information about your
> schedule, in order for us to add it to our website and for visitors
> to see.
>
> For every session, we will need:
> * start time and duration (in 15 minute blocks -- please stick with
> that granularity, as it will make the schedule somewhat easier to
> follow for visitors),
> * activity title (please try to be descriptive, there are ~250
> talks at
> FOSDEM during the week-end ;)),
> * a short abstract (1-2 paragraphs),
> * a longer description if appropriate,
> * optionally a list of links to the project website or similar
> * for each speaker:
> * the speaker's real name,
> * a short overview of her bio in a couple of lines,
> * optionally also a longer bio,
> * optionally a picture (please send it to us as 128x128 PNG),
> * optionally links to her website, blog, ...
>
> For examples, see:
> * http://archive.fosdem.org/2009/schedule/devrooms/freejava
> * http://archive.fosdem.org/2009/schedule/events/java_state_icedtea
> * http://archive.fosdem.org/2009/schedule/speakers/mark+reinhold
>
> Send that information either in a plain text email or with a text file
> attached to an email. The easiest for us is to have that data in the
> following form, e.g.:
> --->8----------------------------------------------------------------
> John Doe
> john.doe@...
>
> John is currently working as a freelancer and spends most of his free
> time contributing to various opensource projects, most prominently on
> libjohndoe.
>
> John currently lives in England with his wife, 2 kids and a bunch of
> kitten. He loves spending his time walking around in the woods, and
> of course kitten. He has a masters degree in kitten science, which
> helps him a lot with coding.
>
> blog: http://johndoe.example.org/blog/
> attached: john_doe.png
>
> ---
>
> Kitten cooking with libjohndoe
>
> libjohndoe is a high performance library that can be used for various
> purposes, and most prominently to cook kitten.
>
> John will present the internals of his pet project, libjohndoe, and
> how its API has evolved from a kitten shop into a cantonese
> restaurant management platform along the years.
> He will also make a demo of its newest feature.
>
> http://johndoe.example.org/libjohndoe/
> http://johndoe.example.org/blog/tags/libjohndoe
>
> --------------------------------------------------
>
> Jane Hackerton
> miss.jane@...
> ...
> --->8----------------------------------------------------------------
> (the number of dashes and such doesn't matter, it isn't automated, but
> a format like the above would be perfect for us)
>
> Please, pretty please, try to stick to what we are asking above, as
> it will make our life a lot easier when we will have to hack 250 talks
> into our content management system.
>
> Note that the information above will be available both on our website
> and in the free program folder we distribute to the visitors.
>
> Call for talks:
> ~~~~~~~~~~~~~~~
> We want to host a list of all accepted devrooms with links to their
> call for talks on our site. We believe this can help potential
> speakers
> find the way to the most relevant devroom. We (FOSDEM) also organize
> lightning talks (15 min talks) and as every year, we will forward talk
> requests that better fit your devroom to you.
> Please send us a link to your call for talks as soon you publish it
> on your project's website.
>
> Deadlines:
> ~~~~~~~~~~
> The deadline for the full schedule submission is 2010-01-10
>
> The earlier you send us the data, even if incomplete, the easier it is
> for us, and the earlier it will be online on our site.
> We would recommend you to send talk acceptance notifications before
> 2009-12-31 to the contributors of your project -- that would leave you
> with plenty of time to poke speakers again and again for sending you
> the required data ;)
> As an example, the lightningtalk request deadline is 2009-12-20 with
> acceptance notification on 2009-12-28.
>
> Some conditions we need to agree on:
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> For us, you are the devroom responsible. This means that we will
> communicate everything through you, and you will be the one we will
> poke for information ;)
>
> Also, during the weekend, we want you to do good housekeeping of the
> room:
> - we will offer trash bags for the garbage, there should not be any
> garbage lying around in the room when you leave,
> - there is a limit on the room capacity that can not be exceeded (by
> much).
>
> Please understand that we are a non for profit association, and that
> every single organization team member works on FOSDEM during her
> spare time. As such, it would be very nice if we didn't have to spend
> several hours cleaning up the devrooms, and it is just a very small
> amount of work for the attendees to put their garbage into the trash
> bags.
>
> Two years ago there were some rooms that were extremely overcrowded,
> and apart from the obvious risks regarding the security of the
> attendees, doing so is the most effective way of killing the event as
> any inspection by the university and/or the fire department would get
> us thrown out for good.
>
> We cannot provide every single project with large rooms and over-
> abundent seating, so if the room has reached its full capacity, please
> ask additional people to stay out and enjoy another talk -- there are
> plenty to choose from.
> As last year, we will provide you with signs to put on the doors of
> the
> devrooms to signify that the room is full (or not).
>
>
> And, of course, if you have any questions, please contact us at
> devrooms@...
>
> On behalf of the FOSDEM devroom team,
> Tias
>
>
> Lars Sonchocky-Helldorf wrote:
>> I didn't receive any notification as of now. Has our request been
>> accepted or rejected?
>> thanks,
>> Lars
>> Am 21.11.2009 um 15:44 schrieb Mattias 'Tias' Guns:
>>> Hello Lars,
>>>
>>> Thank you for your devroom request. We received it well and it
>>> has been added to the pool of candidates.
>>> The acceptance notification will be sent around on 2009-11-29.
>>>
>>>
>>> Kind regards,
>>> Tias
>>> FOSDEM organizer
>>>
>>> Planet GNUstep - a collaboration of GNUstep related projects wrote:
>>>> Submitted on 11/21/2009 - 02:40
>>>> Submitted by anonymous user: [213.9.34.100]
>>>> Submitted values are:
>>>> Developer Room:
>>>> devroom name: Planet GNUstep - a collaboration of GNUstep
>>>> related projects
>>>> devroom description:
>>>> participating projects:
>>>> - GNUstep
>>>> GNUstep is a free, object-oriented, cross-platform, OpenStep/
>>>> Cocoa API compatible framework and development environment.
>>>> - Étoilé
>>>> Étoilé is an innovative GNUstep based user environment
>>>> designed from the ground up around the things people do with
>>>> computers: create, collaborate, and learn.
>>>> - GAP - the GNUstep Application Project
>>>> The GNUstep Application Project provides a comprehensive set
>>>> of administration and user level tools to make using GNUstep
>>>> based environments a very pleasant experience. Part of the
>>>> charter of this project is not only to write new tools, but also
>>>> to port existing NeXTSTEP/OPENSTEP/Cocoa applications to GNUstep
>>>> as well.
>>>> - QuantumSTEP / mySTEP
>>>> QuantumSTEP is a Mac-like Application Platform that can be
>>>> installed on existing mobile Linux devices (Openmoko, Zaurus,
>>>> Letux, ...) aiming at highest level of useage, data and
>>>> application source code compatibility (to the Macintosh
>>>> platform) prepared for perfect data exchange and sync.
>>>> goals/topics:
>>>> - teach interested developers how to write cross platform
>>>> applications or port Cocoa applications to Linux BSD and Windows
>>>> using GNUstep
>>>> - share news about the latest development and plans on GNUstep
>>>> - improve collaboration between the several GNUstep related
>>>> projects
>>>> - using GNUstep to write applications for mobile devices ((e.g.
>>>> Openmoko, Beagleboard)
>>>> - GNUstep cross-platform integration
>>>> - code sprints, hacking, discussing
>>>> devroom related URLs:
>>>> http://gnustep.org/
>>>> http://etoileos.com/
>>>> http://gap.nongnu.org/
>>>> http://www.quantum-step.com/wiki.php?page=About
>>>> http://www.quantum-step.com/wiki.php?page=mySTEP
>>>> devroom day(s):
>>>> - Saturday from 12:00 to 18:00
>>>> - Sunday from 10:00 to 17:00
>>>> Contact Info:
>>>> name of the responsible: Lars Sonchocky-Helldorf and Richard
>>>> Frith-Macdonald
>>>> email: lars.sonchocky-helldorf@...
>>>> relation to the topic: Lars Sonchocky-Helldorf is a
>>>> community manager for GNUstep, Richard Frith-Macdonald is a
>>>> GNUstep core team member/developer
>>>> Optional:
>>>> comments/remarks:
>>>> GNUstep is a good match for FOSDEM since the target audience of
>>>> GNUstep are developers who want to develop cross platform (Unix,
>>>> Windows, Mac) GUI or server side applications or command line
>>>> tools using state of the art object oriented Frameworks.
>>>> Although we are jointly applying for four projects, a smaller
>>>> room (about 30 seats) should be sufficient (the last years room
>>>> was perfect).
>>>> The results of this submission may be viewed at:http://
>>>> fosdem.org/2010/node/19/submission/121
>>>
>

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: FOSDEM 2010 devroom list is available

2009-12-01T13:54:52Z

On 1 Dec 2009, at 18:52, hns@... wrote:

> I think it is not well known that there is also an offer from Mike
> Dexter from www.linuxfund.org to sponsor GNUstep to reach more
> stability and visibility. Unfortunately the discussion has ceased.
> IMHO, this is a great opportunity to really invite (i.e. subsidize
> some travel expenses and hotel cost) to a series of Hacking meetings.
> And by having a series of such meetings, we could set up a "to do
> list", assign tasks and report progress (to Linux Funds and the
> public). It will be a little painful to go through this initially
> since we all are individualistic volunteers, but IMHO it will help the
> whole project especially if we don't have the FOSDEM devroom&stand any
> more.

That's the first I've heard of this, but I'd be interested in
applying. Are the conditions and procedures for applying documented
somewhere?

David

-- Sent from my PDP-11

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: FOSDEM 2010 devroom list is available

2009-12-01T13:47:40Z

Le 1 déc. 2009 à 19:52, hns@... a écrit :

> On 1 Dez., 18:42, Lars Sonchocky-Helldorf <lars.sonchocky-
> helld...@...> wrote:
>>
>>
>> So I guess there's no devroom at FOSDEM 2010 for us. Sorry folks,
>> projects like Jabber/XMPP and NoSQL seem to be more important than
>> us. Why there's Crossdesktop (a collaboration across, but not limited
>> to, KDE, GNOME and XFCE) and still a single room for each KDE and
>> GNOME I also don't know.
>
> When looking through the list I get the impression that the organizers
> have more or less sorted the requests by project size and novelty.
> I.e. either novel or "big". Unfortunately, GNUstep wouldn't make a
> good position in either category...

I just checked the link. GNUstep in now listed in the dev rooms :-)

This sounds interesting. I don't recall to have read about it here
previously.
Why the discussion has ceased?

Cheers,
Quentin.

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: FOSDEM 2010 devroom list is available

2009-12-01T10:52:32Z

On 1 Dez., 18:42, Lars Sonchocky-Helldorf <lars.sonchocky-
helld...@...> wrote:

> Hi folks,
>
> I am still waiting for an official acceptance or (more likely it
> seems) rejection mail from FOSDEM. I already pinged the person in
> charge for the devrooms on that but got no reply as of now.
>
> Now Nikolaus has already let the unpleasant news out of the bag:
>
> Am 01.12.2009 um 14:56 schrieb h...@...:
>
> >http://www.fosdem.org/2010/list-devrooms-their-call-talks
>
> > but where is GNUstep?
>
> > Nikolaus
>
> So I guess there's no devroom at FOSDEM 2010 for us. Sorry folks,
> projects like Jabber/XMPP and NoSQL seem to be more important than
> us. Why there's Crossdesktop (a collaboration across, but not limited
> to, KDE, GNOME and XFCE) and still a single room for each KDE and
> GNOME I also don't know.

When looking through the list I get the impression that the organizers
have more or less sorted the requests by project size and novelty.
I.e. either novel or "big". Unfortunately, GNUstep wouldn't make a
good position in either category...

And, it appears that there are less Devrooms. Maybe they want to avoid
that visitors need too much time changing between presentations.

Both is a good approach to keep FOSDEM attractive for those who not
only want to meet "their" project. So I think they did the right
decisions.

>
> What can we do now?
>
> - we can have some sort of unofficial meeting, e.g. just meeting each
> other (and maybe have a dinner together) without having a devroom.

We should do this anyway!

We can also do some hacking in the Hacker's room (unfortunately this
is not intended for discussions). And occupying a table in the
Cafeteria is also possible - but IMHO not a pleasant atmosphere for
fruitful discussions.

So we should use it as a chance to discuss with other projects and
learn what they are doing better...

> - people who want to give a talk could still sign up for lightning
> talks:http://www.fosdem.org/2010/call_for_lightningtalks- everybody
> has to do that individually.
> - we could try to join other projects' devroom efforts, I guess for
> instance Nikolaus could try to come to an agreement with the Embedded/
> Mobile devroom folks, whereas Étoilé maybe would fit in the

My other important topic "OpenMoko" fits there as well.

> Crossdesktop room. GNUstep could make friends with the folks of the
> Mono Developer Room (just kidding ;-))

And Fred could go to X11 and ask them to include the NSGraphicsContext
primitives in the next X11 protocol :)

>
> I am somewhat sad and disappointed about this outcome, but whatever,
> the world goes on and we can try again next year. Maybe we see this
> as a chance to get our act together a little bit better (/me looks at
> our website for instance).

What I suggest is that we also should organize our own "DevRooms" and
hacking meetings in a more formal way than before.

I think it is not well known that there is also an offer from Mike
Dexter from www.linuxfund.org to sponsor GNUstep to reach more
stability and visibility. Unfortunately the discussion has ceased.
IMHO, this is a great opportunity to really invite (i.e. subsidize
some travel expenses and hotel cost) to a series of Hacking meetings.
And by having a series of such meetings, we could set up a "to do
list", assign tasks and report progress (to Linux Funds and the
public). It will be a little painful to go through this initially
since we all are individualistic volunteers, but IMHO it will help the
whole project especially if we don't have the FOSDEM devroom&stand any
more.

>
> So now that I have time (and finally bought a big external hard disk)

Well, 1TB disks aren't expensive these days and hold a lot of raw
video material :)

> I can finish editing the videos from last year and upload those on
> vimeo or the like later.

That would be nice!

Nikolaus
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: FOSDEM 2010 devroom list is available

2009-12-01T09:42:34Z

Hi folks,

I am still waiting for an official acceptance or (more likely it
seems) rejection mail from FOSDEM. I already pinged the person in
charge for the devrooms on that but got no reply as of now.

Now Nikolaus has already let the unpleasant news out of the bag:

Am 01.12.2009 um 14:56 schrieb hns@...:

> http://www.fosdem.org/2010/list-devrooms-their-call-talks
>
> but where is GNUstep?
>
> Nikolaus

So I guess there's no devroom at FOSDEM 2010 for us. Sorry folks,
projects like Jabber/XMPP and NoSQL seem to be more important than
us. Why there's Crossdesktop (a collaboration across, but not limited
to, KDE, GNOME and XFCE) and still a single room for each KDE and
GNOME I also don't know.

What can we do now?

- we can have some sort of unofficial meeting, e.g. just meeting each
other (and maybe have a dinner together) without having a devroom.
- people who want to give a talk could still sign up for lightning
talks: http://www.fosdem.org/2010/call_for_lightningtalks - everybody
has to do that individually.
- we could try to join other projects' devroom efforts, I guess for
instance Nikolaus could try to come to an agreement with the Embedded/
Mobile devroom folks, whereas Étoilé maybe would fit in the
Crossdesktop room. GNUstep could make friends with the folks of the
Mono Developer Room (just kidding ;-))

I am somewhat sad and disappointed about this outcome, but whatever,
the world goes on and we can try again next year. Maybe we see this
as a chance to get our act together a little bit better (/me looks at
our website for instance).

So now that I have time (and finally bought a big external hard disk)
I can finish editing the videos from last year and upload those on
vimeo or the like later.

see you,

Lars

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

FOSDEM 2010 devroom list is available

2009-12-01T05:56:09Z

http://www.fosdem.org/2010/list-devrooms-their-call-talks

but where is GNUstep?

Nikolaus
_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Arguments of +connectionWithRegisteredName:host:

2009-11-30T23:53:42Z

On 1 Dec 2009, at 02:20, Germán Arias wrote:

> Look this
>
> http://www.gnustep.it/nicola/Tutorials/DistributedObjects/node7.html
>
> In fact, this question born from this example. I discussed this with
> Nicola, and he suggested talk this here.

The example dates from before the time Apple changed the API to use host-local connections by default.
I don't think the documentation is wrong so much as a little unclear ...

If it is an asterisk ('*') then the nameserver checks all hosts on the local subnet (unless the nameserver is one that only manages local ports)

That phrase 'unless the nameserver is one that only manages local ports' could be interpreted more than one way.

So I added a line to explicitly state that the host name should be omitted if the nameserver does not support remote hosts.

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Arguments of +connectionWithRegisteredName:host:

2009-11-30T18:20:44Z

Look this

http://www.gnustep.it/nicola/Tutorials/DistributedObjects/node7.html

In fact, this question born from this example. I discussed this with
Nicola, and he suggested talk this here.

El lun, 30-11-2009 a las 22:56 -0300, Jamie Ramone escribió:

> This @"*" is a pure GNUstep thingy, and I havn't really used it. What
> exactly is it supose to do?
>
> On Mon, Nov 30, 2009 at 10:05 PM, Germán Arias <german@...> wrote:
> > When I try:
> >
> > [NSConnection connectionWithRegisteredName: @"Name" host: @"*"];
> >
> > I get:
> >
> > ./obj/Client: Uncaught exception NSInvalidArgumentException, reason:
> > Attempt to contact a named host using a message port name server. This
> > name server can only be used to contact processes owned by the same user
> > on the local host (host name must be an empty string). To contact
> > processes owned by other users or on other hosts you must use an
> > instance of the NSSocketPortNameServer class.
> >
> >
> > If this is true, the documentation is wrong. And a question: Why is
> > necessary the argument host? the method would be
> > +connectionWithRegisteredName:
> >
> >
> >
> > _______________________________________________
> > Discuss-gnustep mailing list
> > Discuss-gnustep@...
> > http://lists.gnu.org/mailman/listinfo/discuss-gnustep
> >
>
>
>

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Arguments of +connectionWithRegisteredName:host:

2009-11-30T17:56:14Z

This @"*" is a pure GNUstep thingy, and I havn't really used it. What
exactly is it supose to do?

On Mon, Nov 30, 2009 at 10:05 PM, Germán Arias <german@...> wrote:

> When I try:
>
> [NSConnection connectionWithRegisteredName: @"Name" host: @"*"];
>
> I get:
>
> ./obj/Client: Uncaught exception NSInvalidArgumentException, reason:
> Attempt to contact a named host using a message port name server. This
> name server can only be used to contact processes owned by the same user
> on the local host (host name must be an empty string). To contact
> processes owned by other users or on other hosts you must use an
> instance of the NSSocketPortNameServer class.
>
>
> If this is true, the documentation is wrong. And a question: Why is
> necessary the argument host? the method would be
> +connectionWithRegisteredName:
>
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@...
> http://lists.gnu.org/mailman/listinfo/discuss-gnustep
>

--
Besos, abrazos, confeti y aplausos.
Jamie Ramone
"El Vikingo"

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep

Re: Arguments of +connectionWithRegisteredName:host:

2009-11-30T17:30:04Z

If you don't want to specify the local host then the host: parameter
should be nil or an empty string (i.e. @""), from what I recall.
That's what the Apple docs say, and what I've always used.

On Mon, Nov 30, 2009 at 10:05 PM, Germán Arias <german@...> wrote:

Arguments of +connectionWithRegisteredName:host:

2009-11-30T17:05:23Z

When I try:

[NSConnection connectionWithRegisteredName: @"Name" host: @"*"];

I get:

./obj/Client: Uncaught exception NSInvalidArgumentException, reason:
Attempt to contact a named host using a message port name server. This
name server can only be used to contact processes owned by the same user
on the local host (host name must be an empty string). To contact
processes owned by other users or on other hosts you must use an
instance of the NSSocketPortNameServer class.

If this is true, the documentation is wrong. And a question: Why is
necessary the argument host? the method would be
+connectionWithRegisteredName:

_______________________________________________
Discuss-gnustep mailing list
Discuss-gnustep@...
http://lists.gnu.org/mailman/listinfo/discuss-gnustep