|
I will not buy any library without source code for two reasons. The first is debugging. The second is if the company closed its doors I will still be able to use the library in the future.
John
|
|
|
|
|
It should contain a CListCtrl.
It surely can't be called a Library if it misses a CListCtrl
codito ergo sum
|
|
|
|
|
Funny that good performance (CPU utilization and memory footprint above all) is not listed. It is true that some applications may not care about performance, but a library?
And of course, everything else on the list, please
|
|
|
|
|
just buy a bigger CPU...
no one worries about performance anymore...
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
El Corazon wrote: just buy a bigger CPU...
...to all users?
Besides, you forgot the RAM - I should buy them that as well
|
|
|
|
|
Nemanja Trifunovic wrote: Besides, you forgot the RAM - I should buy them that as well
absotively! posilutely!
don't forget mine.... I'll take 8gig please....
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
El Corazon wrote: don't forget mine.... I'll take 8gig please....
You still don't have enough? Why not get a couple gig for each thread?
Gary
|
|
|
|
|
ghle wrote: You still don't have enough? Why not get a couple gig for each thread?
enuff enugh enough is not in my vocabulary.... how about a gig for every post!
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
Nowaday people dont worry about coding good and clean,,,only make its function and lets goo!!!
|
|
|
|
|
El Corazon wrote: how about a gig for every post!
Well, only if you think a gig for each post is larger than a couple gig for each of your threads.
Gary
|
|
|
|
|
While documentation is important, there is noithing like a library full of examples to make things clear in a short time period.
|
|
|
|
|
Could not agree more with this.
|
|
|
|
|
That is why source code is important - it usually contains a lot of examples implicitly
Natza Mitzi
|
|
|
|
|
- Robust
- Good design
- Good documentation
|
|
|
|
|
leppie wrote: Good documentation
This might assume paramount importance since for any type of product/project, it enhances maintenance without much pressures and turmoils.
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
I feel RobustNess and good documentation is key for evry good project or software.. i have seen many robust project are poor on design.. but still very famouse with people, ( i don't wanna give name to them!)
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You/codeProject$$>
|
|
|
|
|
leppie wrote: - Robust
- Good design
- Good documentation
Yeah, three things that all software library vendors fail the most at. Go figure.
Marc
|
|
|
|
|
hai you too owner of well know opensource library!
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You/codeProject$$>
|
|
|
|
|
Definitely robust and good design.
I believe that good design requires (only) adequate documentation. While poor design requires (very) good documentation.
Also, nice to have good price, support, and flexibility!
|
|
|
|
|
Member 3991178 wrote: I believe that good design requires (only) adequate documentation. While poor design requires (very) good documentation.
Agreed! I've been trying to think of a good way to say that since the poll came out.
With my favorite libraries, i've spent very little time reading the docs. My least favorite libs, i spend an awful lot of time pouring over the source. ...and then, there are the ones without source, where i spend the evening hours tracing through disassembly and cursing the idiots that wrote it.
|
|
|
|