#qi-hardware IRC log for Thursday, 2012-05-31

wpwrakcladamw: glad you're having fun :-) i think part of that may also be that fped allows you to think in more abstract terms. so each thing you do has a more powerful effect.02:01
wpwrakregarding the suppression of pins: the most direct way of suppressing pins would be to have a table, keyed by the pin's number, that says whether the pin should be shown or not02:02
wpwrakah wait, and we can rename them in the process, too02:03
wpwrakso:02:03
wpwraktable { ?n, name } { 1, 1 } { 2, 2 } { 3, 3 } { 4, 4 } { 5, 5 } { 6, 0 } { 7, 0 } { 8, 6 }02:05
wpwrakloop if = floor(1-name/100), 002:06
wpwraklemme check if this actually works :)02:06
cladamwyeah ... my problem is that I've not familiar with its conceipt of expression. :-)02:06
wpwrakyeah, works perfectly :)02:07
cladamwso if the table above it can do with just one pads frame not using two pads_t and pads_b, then i eventaully knows that table. :-)02:08
cladamwsince i still don't know the how syntax it is. :-O02:09
wpwrak(expressions) the way fped does things is a bit unusual. that's because everything has to work in a reasonably natural way in a "script" and in the GUI. so it's a mix of procedural and declarative concepts.02:09
cladamwhehe ... could you use pastebin for me the optimized codes ?02:09
wpwrakyou mean a modified eus.fpd ?02:10
cladamwyeah ... correct explainative mix of both procedural and declarative ones.02:11
cladamw(modified eus.fpd) yes. :-)02:11
cladamwbut maybe your Fped is updated latestly not like mine now so that i not sure if Fped can interprete it.02:12
wpwrakif you want to understand the finer details of fped, you should look at the script language, described in README. i think it's easier to understand the structure of things there02:12
wpwrakyes, you need the latest fped for this kind of thing to work :)02:13
cladamwphew ~ script again.02:13
cladamwmy priority one may not to learn it now, hehe  ... keep building those needed m1r4's modules.02:14
wpwraki think it's a good moment to learn what you want to learn02:15
wpwraksince you have a lot of opportunities to use it on real-life problems. that makes it much easier to learn.02:15
cladamwi have time goal now. :-)02:16
wpwrakah ?02:16
wpwrakhas wolfgang given you a deadline ?02:16
cladamwso maybe yesterday you mentioned another expression for older ver. of Fped. Can it ?02:16
cladamwDoes Fped have another expression for such for my current Fped ?02:17
wpwrak(looking at eus.fpd) pin_b and pin_t are nearly identical. is there any specific reason why you didn't use the same frame for both types of pins ?02:17
cladamwwpwrak, yeah ... i tried but failed in using 'if' ... hehe02:18
cladamwthen i seperate 'pin' into *_[b:t] frames. :-O02:18
wpwrak(old-style) you could just enumerate the pins: table { pos, name } { 1, 1 } { 2, 2 } { 3, 3 } { 4, 4 } { 5, 5 } { 8, 6 }02:19
wpwrakand remove the loop02:19
wpwrakwhat i called "pos" would be "i" in your case02:20
wpwrak(using if) hmm. you shouldn't need an "if" here02:20
cladamwAll roads lead to Rome. (even I knew it's not smart codes but tried ) ha ...02:21
wpwrakthe only possible problem i see with simplifying things is that it may be harder to get measurements. but let's see ...02:21
cladamw(olde-style) okay ... next module if the same case I'll try. :-)02:22
wpwrakby the way, to verify footprints, when you generate a postscript file and print it, fped will put one drawing at the real size. so if you have the component at hand, you can put it on the paper and verify that the footprint does indeed look right02:22
wpwrakthinking of it, the old-style approach is actually more efficient in this case :)02:23
cladamwwpwrak, okay ... that's i'd like to know from you. ( efficient) :-) thanks telling me. :-O02:24
wpwrakoh, and eus.fpd linke pins_t from frame outline. i think you want to link it from the root frame :)02:35
wpwrakhere's my version: http://downloads.qi-hardware.com/people/werner/tmp/eus2.fpd02:42
wpwrakshould also work with old versions of fped02:42
wpwrakthat part has a funny geometry. i think the dimensions are originally in mil.02:44
wpwrakif a part is in mil, it's better to use the original dimensions. fped will convert them for you anyway.02:44
wpwrakyou can also mix mil and mm. e.g., if a part is in mil, you can still use mm for measurement offsets02:45
cladamwa(eus2.fpd) wpwrak nice, thanks a lot. good to see smarter codes. :)04:04
jivs_seen xiangfu11:25
jivs_xiangfu, plz buzz me when you are online11:25
wpwrakgrmbl. i should know better than starting with the regression tests only after already having accumulated 4k lines to test :-(13:55
viricwpwrak: kernel or user code? :)14:13
wpwrakuser code (boom)14:15
wpwraki better clean out the bugs accumulated so far before setting it to work on m1r414:16
viricwhat did "(boom)" mean?14:16
wpwrakcomes from BOM (bill of materials). the the second O is a non-functional artistic addition :)14:18
viricif you made a kde frontend, you could name it kaboom14:19
viricok :)14:19
wpwrak;-))14:20
Aylado you know the anime Linus & Boom?14:20
Aylas/anime/cartoon14:20
virichm no14:21
wpwraknaw, i do my graphics only in SDL or Gtk. vade retro, C++ ;-)14:21
viricI only know Linus from Schultz14:21
wpwrakAyla: is that cartoon about Mr. Torvalds rewriting memory management while having a hangover ? :)14:22
Aylano, it's a lame cartoon about aliens14:22
qi-botThe build was successful: http://fidelio.qi-hardware.com/~xiangfu/build-nanonote/openwrt-xburst.full_system-20120530-0909 15:06
qi-bot[commit] Jiva Nath Bagale: bug fix for guile2 Makefile (master) http://qi-hw.com/p/openwrt-packages/5e8a25e15:46
LunaVoraxHello everyone19:46
qi-bot[commit] Werner Almesberger: b2/test/hierfld: field definitions in hierarchy (master) http://qi-hw.com/p/eda-tools/ef60e9219:54
qi-bot[commit] Werner Almesberger: b2/: new option -v to control verbosity level; move hierarchy dump from parser to boom.c (master) http://qi-hw.com/p/eda-tools/b0ed43619:54
qi-bot[commit] Werner Almesberger: b2/test/Common: drop that tacky "file-" prefix in pseudo-filenames (master) http://qi-hw.com/p/eda-tools/52e58cc19:54
qi-bot[commit] Werner Almesberger: b2/new function yywarn; make yyerror reuse yyerrorf (master) http://qi-hw.com/p/eda-tools/223944019:54
qi-bot[commit] Werner Almesberger: b2/: add test for redundant conditions in hierarchy (master) http://qi-hw.com/p/eda-tools/39382b119:54
qi-bot[commit] Werner Almesberger: b2/Makefile: run tests with bash, not with sh (master) http://qi-hw.com/p/eda-tools/494351919:54
qi-bot[commit] Werner Almesberger: b2/lang.y: don't pop fields from the stack before also handling the rule (master) http://qi-hw.com/p/eda-tools/a892b6319:54
qi-bot[commit] Werner Almesberger: b2/dump.c (dump_rel): use %g also for tolerances in percent (master) http://qi-hw.com/p/eda-tools/6159bdf19:54
qi-bot[commit] Werner Almesberger: b2/eval.c (eval_rel): fix stop pointer when parsing absolute tolerance values (master) http://qi-hw.com/p/eda-tools/8c26e5f19:54
qi-bot[commit] Werner Almesberger: b2/test/hierrul: field rules in hierarchy (master) http://qi-hw.com/p/eda-tools/e66267f19:54
qi-bot[commit] Werner Almesberger: Merge branch 'master' of projects.qi-hardware.com:eda-tools (master) http://qi-hw.com/p/eda-tools/4fb5f2619:54
kristianpaulwhitequark: how went your arm + fpga combo handshake?22:51
--- Fri Jun 1 201200:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!