Hi Matt, I tried to include usage of glcd_common.jal in my sample. Indeed, far from easy to integrate :)
I understand there are incompatibilities with GLCD fonts file. glcd_common includes glcd_font, which by default uses glcd_5x7_font and glcd_font_8x12. Why ? And why named differently ? glcd_nokia_3310 requires definition of var_nmb, which "holds number of bytes used for a char". What would be the equivalent in your glcd libs ? Also, can you explain how is glcd_font_8x12 working ? In nokia_3310, should print_char be renamed to lcd_write_char(), as in glcd_ks0108 ? Why glcd_ks0108 defines its own 5x7 font table, and doesn't use glcd_5x7_font lib ? Some random questions, quite hard to dive into this... Cheers, Seb 2011/2/6 mattschinkel <[email protected]> > Hey Seb, we can defiantly continue with this discussion. I'm happy to > hear you have interest. > > I do suggest you try and give feedback on glcd_font.jal as well as > glcd_common.jal > > Nobody has to use these libraries, but it is good to give an option > for users to use a library that is up to date. For example, someone > could write a procedure of their own for drawing a line but it would > be better to use the procedure Jallib group agrees is the best. > > Also check out 18f4620_glcd_touch_stm032qvt-003.jal for an example. I > still have my circuit for that connected. > > Matt. > > On Feb 6, 5:45 am, Sebastien Lelong <[email protected]> > wrote: > > Hi Matt, > > > > I've a working setup using Nokia 3310 GLCD on my Jaluino. Do you want to > > reactivate this thread on work in this ? Now I can help and even write > code > > :) > > > > My current sample code is very simple but works great. I plugged the LCD, > > following instructions herehttp:// > www.amontec.com/lcd_nokia_3310.shtml(linkfrom Source: tag), > > and that's it ! Impressed... > > > > include jaluino_medium > > include delay > > > > alias nok_sclk is pin_b6 -- assign nokia clock > > alias nok_sda is pin_b4 -- assign nokia serial data in > > alias nok_cs is pin_c1 -- assign nokia chip enable > > alias nok_res is pin_c0 -- assign nokia reset > > alias nok_dc is pin_c2 -- assign nokia data/commant > > > > pin_b6_direction = output > > pin_b4_direction = output > > pin_c2_direction = output > > pin_c1_direction = output > > pin_c0_direction = output > > > > include glcd_6x8_font > > include glcd_nokia3310 > > lcd_init() > > > > var byte x > > forever loop > > for 255 using x loop > > delay_100ms(3) > > print_char(x) > > end loop > > end loop > > > > I can see some weird API and wrong comments though. > > > > Let me know ! > > > > Cheers, > > Seb > > > > 2010/12/30 mattschinkel <[email protected]> > > > > > > > > > Hey Paul, are you still working on this? > > > > > Matt. > > > > > On Dec 18, 7:03 am, pdhaene <[email protected]> wrote: > > > > Thank you again. It looks like I get satisfied after all > > > > > > Some great things you do in code shows me I have much > > > > to learn of what can be done in Jal. > > > > > > I better take some time of for serious reading :o) and > > > > come back later > > > > > > Paul > > > > > > On 18 Dec., 06:45, mattschinkel <[email protected]> wrote: > > > > > > > Hey Paul, I made some files as an example of one way to put cache > in a > > > > > separate library. If glcd_cache is included, everything will be > > > > > written to the cache. When you run glcd_cache_to_glcd() the cache > > > > > would get transferred onto the glcd (after you put code in that > > > > > procedure). > > > > > > >http://jallib.googlecode.com/svn/trunk/project/glcd_cache/ > > > > > > > The sample file is 18f460_glcd_nokia_33100.jal > > > > > > > This is great as it makes glcd_cache optional, and others may use > it > > > > > for their glcds with small modification to their glcd device lib. > > > > > > > I assume lcd_write_pixel() is the only procedure that you will > access > > > > > to before the glcd device library is included. > > > > > > > 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. > > > > -- > > Sébastien Lelonghttp://www.sirloon.nethttp://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]. > 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]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
