> > OK, so you want one of these controls yourself? Well, let's imagine you're > going to sit down and write one for your app. Are you honestly telling me > that you expect to end up with highly reusable code that could be placed in a > framework like Cocoa, and you'd be happy to ship to a large number of other > developers? Or (and far more likely) that you'll have implemented only the > bits of functionality your own app needs and left plenty of holes to fill?
Please i'm not trying to offend anyone here, i was just questioning... but since you ask. I try my best to design my classes with the re-usability in mind, also to the best of my knowledge of the language at the time of design, mostly because I do not like to have to rewrite things, it's a waste of time, efforts and money... occasionally I will rewrite a class to improve it with new acquired knowledge and techniques yes, for instance when i learned that i could iterate thru a collection using a for loop instead of while loop coupled with an iterator, i did change most of my classes to reflect that ease of use. same thing for when I learned of properties and KVM coding. Additionally I always write my code with "someone might need to use this" kind of approach, it takes me a little more time but it's worth it in the end. If I was to provide quality development tools to my users, I would make sure my employees have that mindset when hacking together a class, yes, because the time spent un-mixing the mess afterwards to release proper components is just to costly. 1: it takes them away from the creative bench to think of new features 2: it doubles the initial effort therefor doubling the cost, in human hours. Unfortunately for me right now i do not believe I have proper and all the handles on cocoa to create my own controls, but i'm getting there My first controls will probably have holes and missing features, and might respond to specific needs, but then again i'm one guy with less than a year of experience with cocoa. Tho I try my best to measure up, I'm not Apple. This thread of emails want not intended to bash Apple for not doing their work, I just needed to understand why the components are not already available in the toolbox when it seemed logical to me that they should of been there with the release of the operating system along with all the new features so application developers could take full advantage of it. Thank you all for your feedback and explanations! As usual this community Rocks! Cheers. Sandro Noel. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
