Re: Preparation for 1.0 release

On Oct 31, 2003, at 6:08 PM, Graham Booker wrote:
> What does everyone think of the Network Controller and it associated 
> Prefpane?  It is mostly done, and I am sure that I can complete it 
> before the FCS release (likely by the beta stage).  At the moment it 
> is only missing the detection of the network change, but I know how to 
> do this with the code that Eric sent me.  The UI portion is frozen 
> though.  And of course testing, but I have already tested most of it.

I was having some problems with the pref pane... I added the files to 
the project but I had to compile the NetworkController class twice 
(once for the pref and once for the app). We may want to make the pref 
pane access this through the maincontroller instead of directly to 
avoid that.

Also, the pref pane doesn't seem to properly save any prefs. I tried 
fixing the two checkboxes we are moving from General, but it seems that 
the actions for these buttons get called before the mainViewDidLoad is 
called, so that resets those prefs to off before they get populated. 
Maybe something is messed up in the nib file?

> Also, can anyone put this in the project for me?  I seemed to have 
> lost my project builder in switching to Xcode.  Either that, or tell 
> me how to get it back.  It may be better if someone else does it as I 
> do not know how to actually add the pref pane properly to the list.  
> Whenever I display prefs, the network pref is in a second row and only 
> the top 20% of it is visible.  Everything needed is committed with the 
> exception of a network pref pane icon.  I can concoct one if needed.

As Alan mentioned, we need to split things up more to fit them. This 
was all discussed during the Fireside back in July. I think I may add 
the pref pane but not put it in the list just yet in CVS so we can work 
out what else is wrong first. I have added the files to the project 
already, but not a new target yet.

-Jason

> After it is in, I can commit my AIM changes that use this.  I have 
> held off on my AIM updates since it would be a pain to separate it 
> from the networkcontroller update.
>
> Yeah, the Conversation branch is too young to make it into 1.0.  
> Especially since it will have a sizable localization hit.  Maybe for 
> 1.1, 1.5, 2.0, whatever.