[Adium-devl] Parental Controls

[Ofri Wolfus]

Properties are publicly known, but that fact usually means nothing in  
terms of writing code for using them. If you code base on the public  
info only, your coding blindly and there's no point in it usually.
That being said, IIRC one of the Colloquy devs is working at Apple so  
he might have more privileges than other developers.
On a side note, I also remember something about WebKit using ObjC 2  
in their public repository, but then again WebKit is also kinda special.

Stuff like this would be much easier if we used a DVCS ;-)

- Ofri

- - - - - - - - - - - - - - - - - - -
http://www.dpompa.com
- - - - - - - - - - - - - - - - - - -


On 08/06/2007, at 15:49, Chris Forsythe wrote:

> Is the properties information up on developer.apple.com publicly  
> viewable? If so, then it's ok, and if not, then he's violating an  
> NDA possibly.
>
> Chris
>
> On Jun 8, 2007, at 4:08 AM, Ofri Wolfus wrote:
>
>> Doesn't Colloquy have 10.5 support with properties and such?
>> I don't think anyone will have any problems with 10.5 code in a  
>> branch of an open source project as long as you don't actually  
>> document what the new calls do (i.e. expose the NDA'ed docs).  
>> Eventually, the purpose of the seeds is to allow developers to  
>> make their apps compatible with 10.5, and that's exactly what  
>> we'll be doing.
>> But this is only my interpretation.. I know about nothing on these  
>> stuff ;)
>>
>> - Ofri
>>
>> - - - - - - - - - - - - - - - - - - -
>> http://www.dpompa.com
>> - - - - - - - - - - - - - - - - - - -
>>
>>
>> On 08/06/2007, at 08:54, Peter Hosey wrote:
>>
>>> On Jun 07, 2007, at 21:35:45, Joe Ranieri wrote:
>>>> I'd be willing to take a stab at parental controls on 10.5.
>>>
>>> Well, unfortunately, I think we'd have to wait until 10.5 is  
>>> actually out, since an open-source project adopting Leopard APIs  
>>> now would spoil Apple's secrets.
>>>
>>> Perhaps implement it as a plug-in? Then you would work on it in  
>>> your own Adium check-out (perhaps using SVK to version it  
>>> locally), then submit the patch when 10.5 comes out, without  
>>> having to worry *too* much about Adium's code changing out from  
>>> under you. (It's a risk anyway, but less so than working on Adium  
>>> itself.) It would also help make it optional, since those of us  
>>> who don't need parental controls could pass on installing the  
>>> plug-in.
>>>
>>> Another option that you have is to take private notes without  
>>> actually coding anything. Accrete information as it comes in, and  
>>> eventually you'll have the feature more-or-less already written  
>>> in English, leaving only the job of porting it to Cocoa and Adium  
>>> after the 10.5 release.
>>>
>>> Will you be at WWDC, or are you referring to the future, when  
>>> 10.5 is available for public consumption?
>>>
>>> ___________________________________
>>> \ Peter Hosey / boredzo at adiumx.com
>>> PGP public key ID: C6550423 (since 2007-01-01)
>>>
>>>
>>> _______________________________________________
>>> Adium-devl mailing list
>>> Adium-devl at adiumx.com
>>> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>>
>> _______________________________________________
>> Adium-devl mailing list
>> Adium-devl at adiumx.com
>> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20070608/57e9273b/attachment-0001.html>