At 12/16/12 05:56 PM, 23450 wrote:
I took a look at it when it was posted a week or two ago. Seems to be lacking some much needed focus. Most Libs that are popular do 1 or a couple things very very well. With this, developers can get say 2 or 3 libs that would best fit their particular project. GTLib has so many different components that i would not want to bloat my project by including so much code that I would not use.
fair point, but AS3 doesn't include things that you don't use. You could say Flixel is a bloated framework because it has a lot of functionality, but if you don't use every single one of its classes then it's quite fast. It's pretty much the same thing, here. There's a lot of stuff you can do with it, but there's very little cross-referencing in the library so it's not "bloated" persay.
but you are right, there needs to be a direction in the library. I just have no idea where to go with it, to be honest. There's a lot of stuff in there that i'd like to see stay, but a file management system, a client/server/mysql socket, a microphone and webcam listener, and a dungeon generator does not a direction make.
Of course, it most certainly does not do "everything", so your left with potential developers having no idea what the library does.
of course it doesn't do everything :P
I just like to think that it does a lot.
Hopefully that helps. Way to actually try and make a library though. I'm to lazy. : P
yeah, critique is always appreciated ^.^
what do you guys think of this idea:
give the library a single direction (i'm leaning towards file and networking-related items such as uploading and downloading, file management, version management, and client/server/mysql) and putting all the other classes in separate repos.