Hi Matt, I gave you an alternative with arguments to you failed to respond, so I guess 'I hope you conciser my suggestion' means 'do it my way'. This has happened before with new libraries and does happen again: I spend more time on making libraries jallib compliant (with comment, samples and so) and lengthy discussions than on the library development itself. This is just not effective any more. I'm done with this and similar discussions. I will revoke the recent additions and will think twice before adding a new library again.
Joep 2012/4/30 mattschinkel <[email protected]>: >> There is no 24lc* lib or sample with 'eeprom' in the name. > > I am only concerned about the file name, not the procedure names. See > here: > http://jallib.googlecode.com/svn/trunk/include/external/storage/eeprom/ > >> for a library supporting his particular chip and not 'an eeprom', >> regardless of the type, size, interface etc? > > First the user will look for the word eeprom, then they will look for > a particular chip. In grouping things, you usually look for the most > common word first. > > For example, If you go to the microchip website, you will first click > on memory, then eeprom, then lastly, the device name. > >> Your libs have ee_ in the name, which is probably only informative once you >> know it means eeprom. > Yes, you will know what ee_ is after you read the file name. If you > feel it needs to be changed, we can do so. > >> The function of a particular chip is easy to find with google if required, >> and it is also described in the lib itself. > True, but this is about advertizing and an easy way for someone to > find an eeprom in the jallib pack. > > As a jallib user shopping for an eeprom, I first look in the jallib > pack to see what jallib supports before I go out and purchase. I would > not like to open every file in the package to read what it is until I > find an eeprom. I think this is the most important point. How many > files do we have? > >> Note that the naming mismatch between the sample and lib is true for >> quite a few samples and we might consider to change this: a sample is >> mandatory for each lib and unless there is a good reason, the name of >> the sample should be the same as the lib. > > I do believe future samples can be named better, and according to the > lib. Maybe this should go in JSG. Libs must be named correctly > however. > > Anyways, I hope you conciser my suggestion. > > Matt. > > -- > You received this message because you are subscribed to the Google Groups > "jallib" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
