Sebastien Lelong wrote: >> >> I do recall the Rob asked that we start testing with that version some >> weeks ago. > > > Right, buildbot uses 2.4m beta for its regular builds. Some of us > exclusively uses 2.4m-beta. >
I would use it as well but don't know how to get it. > >> IIRC you were trying to get in into the latest bee version >> around the beginning of November. I had the impression that we should >> test it at assist Kyle. but I may be mistaken. >> > > Bee packages looks like final packages, and don't include beta compiler > (that's what I think it should). Helping Kyle can be done without bee > package :) OK, I guess I am out of line here. Just going by what I read on this list. Guess I must have been wrong again. > >> If you can't or don't want to include it it's OK with me. I don'r know >> how or when Kyle will release it if no one helps test it though. >> > > Again, helping Kyle can be done without bee. Or do I miss something ? > I guess it's me that is confused by past posts. > >> Don't mind me, I'm just a fly on the wall wanna be contributor to this >> project. >> >> I have another request while I'm able. Would it be possible to put in a >> section of the Web page for users to ask questions of the Experts? I >> think it would be a good source for the FAQ section. The current FAQ >> page seems to be entice people to switch to JALv2, but is little help to >> someone who has switched and wants to advance. JMHO >> >> > Nice idea ! How do imagine this can be done ? Question on mailling list, > with different answers, that could be synthetized on website as a kind-of > FAQ ? That would be one way that would work. It would require a JalLib group post to here and the JalList to get it going. Another would be a section added to the web page for questions from users to ask questions. As I don't know anything about drupal though, I don't know if that is possible or not. Regarding the tutorial. I have been meaning to ask if the picture that starts the "Getting Started" section could/should be made readable. If it can, it might be informative if the pic could be identified. As it is now it is just confusing, to me at least. It adds nothing to the content of that section. Sorry to have bothered you again. I'll get back to reading the list and trying to progress to the next stage. Regards Wayne > > > > Cheers, > Seb > > > > >>>>> 2009/12/6 Sebastien Lelong <[email protected]> >>>>> >>>>>> Hi guys, >>>>>> >>>>>> >>>>>> Once upon a time samples were split by device. I was quite happy with >>>> this >>>>>> structure, because I could access all samples available for a given >>>> target. >>>>>> Then samples were all put into a single directory. And even if there >>>> were a >>>>>> lot of files, this flat structure was something easy to use (search >> for >>>> a >>>>>> sample not available for your PIC, using a feature, just to get some >>>> example >>>>>> code, ...). I now like this structure. >>>>>> >>>>>> So, I agree with Rob, current structure does the trick, and splitting >> it >>>>>> isn't that easy. Since one sample can use multiple libraries, it can >> be >>>> that >>>>>> simply flat. Splitting by family is like splitting by device, you may >>>> get >>>>>> lots of file in PIC16, and not much in PIC10. >>>>>> >>>>>> Splitting samples should bring a functionality other than "there are >>>> less >>>>>> files into a single directory". Jallib API doc (jalapi), for each >>>> library, >>>>>> provides samples using it. This is an interesting entry point. Since >>>> going >>>>>> from samples to libraries isn't that flat, maybe we can go further and >>>> start >>>>>> to build a database, queried from our website ("I want some samples >>>> using >>>>>> SPI library, whatever the PIC, or using 16F886, or using a PIC in >> PIC16 >>>>>> family, or using a PIC closed to mine, that is in the same datasheet, >> or >>>> the >>>>>> same datasheet as PIC X, Y, Z, ......) >>>>>> >>>>>> >>>>>> Cheers, >>>>>> Seb >>>>>> >>>>>> >>>>>> >>>>>> 2009/12/6 Sunish Issac <[email protected]> >>>>>> >>>>>> Yes Rob. I was thinking of splitting the sample folder, not the >>>> lib/include >>>>>>> files. >>>>>>> I had not thought about sample files using multiple libraries. >>>>>>> >>>>>>> If no other split is possible, may be we can atleast split by >>>> PIC10,12,16 >>>>>>> and 18 families. >>>>>>> >>>>>>> Sunish >>>>>>> >>>>>>> >>>>>>> On Sun, Dec 6, 2009 at 2:18 PM, Rob Hamerling < >> [email protected] >>>>> wrote: >>>>>>>> Hi >>>>>>>> >>>>>>>> Sunish Issac wrote: >>>>>>>>> With the release of so many samples, looks like its time to split >> the >>>>>>>>> samples folder. Spliting by sample type would be more sensible than >>>> by >>>>>>>>> PIC name. IIRC there was discussion about this before. >>>>>>>> Yes, the collection has happily grown, and finding the right sample >>>>>>>> maybe some work. But is that so bad? It's nothing compared to the >>>> effort >>>>>>>> to build and provide this collection, and for free. You must not >> look >>>> a >>>>>>>> gift horse in the mouth! >>>>>>>> >>>>>>>> Specify your criterium for splitting of the sample directory. Number >>>> of >>>>>>>> files, other? It may already help to split off the blink samples, >>>> these >>>>>>>> use no libraries at all. >>>>>>>> Splitting by type (I suppose you mean used library) is not so >> straight >>>>>>>> forward since many samples use more than one library. So be more >>>>>>>> specific with your suggestion. >>>>>>>> >>>>>>>> About splitting the include library: Device files might be put in a >>>>>>>> separate directory, which would require one extra directory in the >>>>>>>> include pathspec. But in my view there is even less reason to split, >>>>>>>> because users have hardly any reason to look in a library. >>>>>>>> >>>>>>>> Regards, Rob. >>>>>>>> >>>>>>>> -- >>>>>>>> Rob Hamerling, Vianen, NL (http://www.robh.nl/) >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> 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]<jallib%[email protected]> >> <jallib%[email protected]<jallib%[email protected]> >>>> <jallib%[email protected]<jallib%[email protected]> >> <jallib%[email protected]<jallib%[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]<jallib%[email protected]> >> <jallib%[email protected]<jallib%[email protected]> >>>> <jallib%[email protected]<jallib%[email protected]> >> <jallib%[email protected]<jallib%[email protected]> >>>>>>> . >>>>>>> For more options, visit this group at >>>>>>> http://groups.google.com/group/jallib?hl=en. >>>>>>> >>>>>> -- >>>>>> Sébastien Lelong >>>>>> http://www.sirloon.net >>>>>> http://sirbot.org >>>>>> >>>>> >>>> -- >>>> >>>> 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]<jallib%[email protected]> >> <jallib%[email protected]<jallib%[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]<jallib%[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.
