Subject [IBO] Re: TIB_Date and DatePick enhancements
Author mmenaz
Don't take my words like I were insisting that things have to go my way. I think that only discussing pros/cons with many people things can go better. Ok, I can subclass, full stop. But this is a solution that I would use for special needs. Put the vertical line. If the person who complained about it only subclassed the component, no other would have benefit from the improvement.
What I want to discuss here is about general IBO improvements.
You have outlined some points I was not thinking about, like documentation already printed, for instance.
But when a component provider like Woll2Woll realize a new version of a component, I don't think that he defaults it's behaviour to the old one: people pay for the new, improved look and performances.
If 100 people use the calendar, and 80 think that it's hard to read, is it better put default to the most user friendly look, or to the "old style"? Maybe the remaining 20 people should set the property the way they like, not the 80 (they can subclass ;)).
What I mean is: what is the deciding factor between compatibility and innovation?
I think that "core" components should be, by default, compatible, while visual one should be, by default, innovative. What's your feeling about that? I like improving components, and I think that with the help of you and IBO users we can make it better and better :)
Marco Menardi

--- In IBObjects@y..., "Jason Wharton" <jwharton@i...> wrote:
> No drawbacks unless you have user documentation, marketing materials, etc.
> with screen shots of your application and you want things to remain
> consistent. Also, some people being color-blind and people making use of
> color schemes in there apps, it is preferable to use gray scale in highly
> generic situations like the datepick in order to avoid conflicts. clRed is
> not a good color in this situation.
> Some things you added will remain without a property, like the line
> separating the days from the numbers. That was a definite improvement. But,
> making the days 3 characters in length is NOT a simple change so I added a
> property to control its length. 2 is a nice option as well.
> Make your own subclass and use it in your applications to carry your
> preferred default conditions if the ones I use are not fully to your liking.
> Regards,
> Jason Wharton
> CPS - Mesa AZ