I had a very, very (too much) quick look at your "jalv2, jallib intro". Dependent and independent pins, as the background too, could (should ?) be put in this document. On the other side, there are reference to some blog post. These are the tutorials & howtos. I think these should be put on a website, not in this doc.
What I mean is some information (how things are working, background, some theory) could be put in this doc, while other practical experiment should remain on a website, with photos, videos. There can be different tutorials for the same kind of topic. This is what I can think about improving this... About "if it complains about ADC_NCHANNEL, etc...", there are other answers in comments about this. Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org 2009/8/17 Joep Suijs <[email protected]> > The good news is that is answers my question implicitly - since I need > ADC_NCHANNEL, 18f452 probably had dependent pins. > > The bad news is that I visited this page before, but did not read it > because it has lots of text about background I don't care about (did not > know it was releveant). Sure, this is my mistake, but others might have a > similar short span of attention. > > How could this be improved? Well basicly, you can just start by saying > there are two groups and describe how to act with each of them. A list of > pic's of each group could be helpfull too, but a short test (if it complains > about adc_nchannel, then..) would realy help to quick-start. > More samples could also be helpfull. > > Should it be improved? As I said, the info is there so there is no real > need. So it is up to you to answer this... > > Joep > > PS About samles: today I noticed that samples are not genereated when a > 'jallib use' is done of a section that is not in the board file. At least > for jseven.jal, a missing jseven section does not prevent compiling, since > it defaults to a standard display layout. For jseven it is not worth to > change, but if it is the same for other tests, it could be usefull to change > this. > > 2009/8/17 Sebastien Lelong <[email protected]> > > Hi Joep, >> >> >> As an answer, I would recommend this excellent and amazing post on >> jalliblog (!) >> >> http://jallib.blogspot.com/2009/07/using-new-adc-libraries.html >> >> This is not that I don't want to answer, but please consider this as a >> test for my doc, read it and tell me if it answered your question. >> >> Cheers, >> Seb >> -- >> Sébastien Lelong >> http://www.sirloon.net >> http://sirbot.org >> >> >> 2009/8/17 Joep Suijs <[email protected]> >> >> >>> Hi Seb, >>> >>> A few years ago, I build a maze solving robot with jal0.4 on an >>> 18f452, using interrupts and lots of memor (512 bytes). Towards the >>> end of JalV2 beta testing, I started to port this app to JalV2 but >>> gave up after weeks of trying - too many bugs and too much work to >>> create all libraries. >>> >>> Last night I gave this an other try and got it up and running in 4 >>> hours, so JalV2 and Jallib do provide a quality development toolset! >>> >>> adc.jal was part of the port, but did only compile after I defined: >>> >>> const ADC_NCHANNEL = 8 >>> >>> and in addition to this, set_analog_pin() (used in your blog) does not >>> exist. >>> >>> Does this mean this chip is not supported (yet)? And could I have know >>> (as a user)? >>> >>> Joep >>> >>> >>> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
