I’m running into issues mixing the Bit component set and MM’s built-in components. The trouble I’m having is that I need a datagrid, which is not included in the bit component set, so I have to use MM’s version. Now the Macromedia datagrid includes MM’s scrollbar and text input components, so the original Bit components get overrided by MM’s. The scrollbar completely ceases to render, and the TextInput now show Macromedia’s inset outset pattern instead of the smooth looking bit component TextInput. Now I know that the button component is named PushButton exactly for the purpose of avoiding issues of using both component types in the same movie, so why didn’t they do this with scrollbars and TextInputs? Wouldn’t using a fully qualified name (”com.bjc.controls.TextInput” for example) solve this issue? I realize that I could switch over to MM’s components for this job, but it’s almost finished by now and the components are skinned, meaning it would be very difficult to make the transition. Here’s hoping this issue is resolved or better yet that we have a working com.bjc.controls.DataGrid.

Also, I’d really like to see a DateField component in the next version. It would be relatively easy to create from the Calendar component and would leverage my current use of DateField in almost all of the RIAs I’ve created so far. What about you? What would you like to see in the next version of the bit component set? I’ll be sure to forward your comments to Keith and BeamJive .