[OGo-GNUstep-Port] (WAS: Re: [GSWHackers] Future of GnusStep WebObject)

[NeXT]

I am not sure whether gnustep-port is correct list to CC but anyway, I 
have question. :-)

The main difference between SOPE and GSWeb is in Main.m(for 
Main.wo/Main.gswc),
I have -submit method and in that;

- (WOComponent *) submit
{
	NSLog(@"currentGuest.guestName:<%@>",
		[self valueForKeyPath:@"currentGuest.guestName"]);
	return nil;
}

In case of SOPE, the value was nil, and in GSWeb, correct value, the 
name. I cannot figure
out why -valueForKeyPath: not work in SOPE.(Possibly not set or 
acidentally released?)
Can you help me again?

Thanks in advance.

On 2004-03-03 06:35:54 +0900 Helge Hess <helge.hess@opengroupware.org> 
wrote:

> On 02.03.2004, at 20:41, NeXT wrote:
>> OK, bug reporting here :-)
>> 
>> KVC enhancement does not work. Main.m should have -(Guest 
>> *)currentGuest { 
>> return currentGuest; } method definition.
>> Without this, the application does not work. Setter method ie., - 
>> (void)setCurrentGuest: does not needed.
> 
> But you are on gnustep-base, not on libFoundation? I don't believe 
> that 
> unless gstep-base doesn't support ivar KVC too, it should definitely 
> work ;-)
> 
> If you start the app, does it log on the shell that it is using a 
> different 
> keypath association? (a Note: log)
> 
> regards,
>   Helge
> 
>> On 2004-03-03 01:53:26 +0900 Helge Hess 
>> <helge.hess@opengroupware.org> 
>> wrote:
>>> On Mar 2, 2004, at 4:27 PM, NeXT wrote:
>>>>> Hm. I might add this as an compatibility option to SOPE, no big 
>>>>> deal, 
>>>>> stay tuned ;-)
>>>> Good to here :-)
>>> OK, just implemented your requests ;-) (libNGObjWeb v4.2.314)
>>> a) removed dependency on EOSQLParser (does it work now with GDL 
>>> EOControl?)
>>> b) added ability to use system KVC for key/value associations, just 
>>> do
>>>        Defaults write NSGlobalDomain \
>>>          WOKeyPathAssociationClass WOKeyPathAssociationSystemKVC
>>>      this should give you ivar KVC (to revert, just delete the key)
>>> Let me know what if you encounter further issues ;-)
>