[Wirelessdriver-devel] Re: WEP and closed network support now operational

[David R. <n1...@ma...>]

I found out that since all of my text are in nib files they are 
automatically localizable. I found the documentation for Preference 
Panes and I'll see how long it will take to implement one. At the moment 
it looks like all I have to do is change a few pieces around and keep 
all my code that I have but I'll see.

-- Dave

On Tuesday, October 23, 2001, at 10:22  AM, David Ross wrote:

>
> On Tuesday, October 23, 2001, at 01:47  AM, Rob McKeever wrote:
>
>>
>> On Monday, October 22, 2001, at 10:27  PM, yu...@ma... wrote:
>>
>>> Great stuff guys!!!! I too am now closed network/WEP enabled at home. 
>>> Wheeee!
>>>
>>> Some thoughts and questions...
>>>
>>> Does the userclient.app from Robs code actually do anything, or has 
>>> it's function been incorporated into Dave's WirelessConfig.app? Robs 
>>> UserClientTemplate.app compiles fine but won't launch for me. If the 
>>> former is correct we should probably clean the template from Robs 
>>> tree and integrate the required files into Daves part of the tree. I 
>>> may be way off here, if so please explain.
>>
>> Dave's pretty much duplicated what I had done in TemplateApp.c.  I'm 
>> going to be replacing the template app with a framework in the next 
>> couple of days and then the template will be pretty much completely 
>> useless and can be removed.
>
> I just committed a modified project file that no longer includes 
> TemplateApp.c so there should be no more confusion in this case. Thanks 
> Rob tho for the example in TemplateApp.c or I'd not have gotten done so 
> quickly.
>
>>>
>>> I'll prepare a FAQ adjustment to explain how to get the correct WEP 
>>> code to input into the config tool and e-mail it to you for browsing 
>>> before we release the new version to the public at large.
>>
>> We should also expand the troubleshooting section some.  I'll post my 
>> basic steps to the developer_private list tomorrow morning.
>
> I'd like to see if I can find Apple's hashing mechanism so that the WEP 
> password would be what you would type normally. With an option to just 
> specify the 40 bits in hex. This will take a bit as I don't think it is 
> published.
>
>>> On that note, how soon till you are ready to release the first 
>>> WEP/closed version? I know there are a few more bugs in the driver 
>>> and GUI you want quashed before release, but I would recommend the 
>>> philosophy release early, release often..public releases to version 
>>> tracker should be tested by at least 2 of us and should have updated 
>>> readme's in the installer. Only Rob should make public releases 
>>> besides cvs. If anyone want to update the links on the home page to 
>>> reflect a release, or add to the faq, feel free but just let the 
>>> others know.
>>
>> I'm voting for a target of late in the week to try for a release.  
>> This gives us a chance to fix a few more issues, round out some rough 
>> spots, etc.
>>
>> Do either of you think we should add any additional docs to this next 
>> release?  ...or are we good to go with what has been there until now, 
>> plus the possible addition of a brief troubleshooting FAQ to keep us 
>> all sane under the e-mail onslaught?
>
> I think with the new GUI app that the trouble shooting will be less as 
> it will handle more of the configurations they wish to try. Though 
> there are more things in heaven and earth that can go wrong that I'll 
> ever know.
>
>>>
>>> Is it possible to make the WirelessConfig.app a preference pane ala 
>>> the new 3rd party panes from tinkertool/asm etc that are installed in 
>>> /Library/Preferences. Or would we even want this? I'd like it, if it 
>>> were possible.
>>
>> Yes... but one thing at a time.  I'd also like to see either a 
>> Dockling or a menu bar item down the road as well.
>
> Supposedly the Preference pane API is published - but I haven't found 
> it yet. I'm guessing that it will take around 20 min to convert the app 
> from Application to Preference Pane mode once I get the API. The 
> menuitem api isn't published so I think we are going to have to ask the 
> author(s) of ASM to lend us their stubs.
>
>>>
>>> What do we see as the future roles for the GUI? It currently is 
>>> simple and functional (the way things should be). I found that I 
>>> could used the Apple admin utility (or Sevy's Java Configurator) for 
>>> BS configuration once I had enabled WEP via Dave's GUI, so we don't 
>>> need to supply the whole set of admin tools. WAP discovery would be 
>>> very useful to add to Daves gui. Beyond that....AirSnort ;-) It would 
>>> be good if the help menu directed people to the FAQ and provided the 
>>> current FAQ.
>>
>> I'm going to see what I can do about public autodiscovery tomorrow and 
>> Wed.  It would be great to have it for the next release.
>
> As soon as auto discovery is ready I'll integrate that into the gui.
>
>>>
>>> We will want an icon for the WirelessConfig.app I'd be happy to give 
>>> it a whack unless you already have a plan. Do we want to stick with 
>>> this name? Other possibilities include WirelessConfigurator.app 
>>> WirelessAdmin.app WirelessAdminUtility.app WirelessUtility.app 
>>> WEP_Utility.app etc. etc. It would be good to choose a name now and 
>>> stick with it.
>>
>> I'll let you guys fight that one out.  I've never been good at that 
>> end of things.
>
> I just named it the first thing that popped into my head that didn't 
> sound to trite. If you really wish it to change that is fine with me 
> and I'll go around and fix all the naming in the nibs and project 
> files. I will be adding localizable text today so that it can be 
> translated if anyone wants to (I only know English so I wouldn't be the 
> best person to localize).
>
>>
>>>
>>> Cheers and keep up the great work!
>>>
>>> Y
>>>
>>
>> Likewise!  It's been an immense help having someone to handle the 
>> stuff I'm not very good with.
>>
>> -Rob
>>
>
> This project is fun and give me stuff to do while I wait for the HR 
> dept of my new job to process me.
>
> -- Dave
>