[interfacekit] Re: Check in

Forgot to mention the implementation-only interface widgets:

BControl, BButton, BCheckBox, BRadioButton, BBox, BStringView.

Erik Jakowatz wrote:

>  > What isn't so great was that I found MessageFilter.h already done.  I
>  > thought I had that class reserved, but I guess I messed up somehow.
> 
> No, that's my bad.  I thought it had been assigned to you, looked and 
> saw it wasn't and dove in.  I should have checked in with you to be 
> sure; sorry I stepped on your toes. =(  I haven't written the use cases 
> yet (Bad programmer!  No bisquit!), so please do check those in so your 
> effort isn't wasted.  Feel free to do a code review on it as well.
> 
> I was just able to surf out to the site, so you might try again.  There 
> are a whole bunch of Interface Kit widgets which have implementations 
> and none of the other stuff.  Here's what is up for grabs:
> 
> App Kit: BRoster, BClipboard, BPropertyInfo
> Interface Kit:
>      BPoint and BRect have implementations, nothing else
>      BPicture, BScreen, BShape, BShapeIterator
>      BColorControl, BSlider, BTab, BTabView
>      BStatusBar
>      BTextView, a couple of items on BTextControl
>      BDragger, BShelf
>      BChannelControl, BChannelSlider, BMultiChannelControl,
>          BOptionControl, BOptionPopUp
> 
> If there are classes in this list which have been assigned, please let 
> me know so I can correct my mistakes. =P  I've gotten some productive 
> coding out of my system, so I think I'll spend a little time working the 
> tools so that there's easy-to-find lists of what is assigned to who and 
> what isn't assigned to anybody.
> 
> e
> 
> Jeremy Rand wrote:
> 
> 
>>Wow, I just did a cvs update and there is a whole bunch more code in 
>>the app_kit directory.  That's great.
>>
>>What isn't so great was that I found MessageFilter.h already done.  I 
>>was working on it.  I had the use cases written and the header file and 
>>was about to start the tests and implementation.  The good news was I 
>>wasn't that far into the work at all so it isn't that much lost.
>>
>>I thought I had that class reserved, but I guess I messed up somehow.  
>>So, I need a new class to work on.  What is left?  I would check the 
>>site to see the progress but it seems to be down right now.
>>
>>If you have something which needs attention send it to me.  I have some 
>>time this week.
>>
>>
>>
>>>BTW, how's it going for everybody?  Any issues or problems?  Now that 
>>>
>>>
>>I 
>>
>>
>>>no longer have a job to drag me out of the house, I've actually had 
>>>
>>>
>>time 
>>
>>
>>>to sit down and code!  The result is that BAlert will be in the 
>>>repository *very* soon.  The initialization code, in particular, is a 
>>>bit messy, but it seems to work just as the original.  Many thanks to 
>>>the TextEntryAlert code in Brian Tietz's SantasGiftBag library -- it 
>>>helped enormously to have that as a reference!
>>>
>>>e
>>>
>>>
>>--
>>Jeremy Rand
>>jrand@xxxxxxxx
>>
>>
>>
>>
> 
> 
> 
> 
>

Other related posts: