search

foundationkit / FoundationKit

Everything that really should be in Foundation, but isn't. Future-proof with ARC
Other
80 stars 9 forks source link

Everything that really should be in CoreFoundation, but isn't. #6

Closed MSch closed 13 years ago

MSch commented 13 years ago
  1. That should be Foundation not CoreFoundation, right?
  2. If it's Foundation then why's stuff like EGOImageLoading in there?

What's the scope of the project?

eaigner commented 13 years ago

Don't know. I would suggest adding only categories on actual foundation classes.

myell0w commented 13 years ago

Because sth like easy lazy image loading SHOULD be in foundation. It's such a general task that it really should be supported by UIImageView out of the box.

eaigner commented 13 years ago

And again... UIImageView is not foundation. Maybe you should move it to a separate UIKitKit project ;)

MSch commented 13 years ago

I have no problem with a AppKitSquared respective UIKitSquared project.

myell0w commented 13 years ago

Don't hang yourself on the name, UIImageView is sth used in every project and we want to make life easier for stuff used in every project. I don't want to include 20 Different foundationXY libraries in my app just to be able to be productive in cocoa

MSch commented 13 years ago

Well I don't use UIKit in my project, and you don't use AppKit, so AppKitSquared and UIKitSquared seem to be in order?

myell0w commented 13 years ago

There will be two different targets for iOS and Mac, but initial focus is on iOS. Maybe You're the right one to maintain the Mac-Target

MSch commented 13 years ago

Why two targets and not two repos? There's no code sharing between Mac and iOS anyways?

eaigner commented 13 years ago

Well with actual foundation classes - there is.

MSch commented 13 years ago

Yeah but those belong in FoundationKit anyways. I meant the UIKit and AppKit additions

MSch commented 13 years ago

See http://titanpad.com/foundationkit