X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Mailer: exmh version 2.7.2 01/07/2005 (debian 1:2.7.2-18) with nmh-1.3 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: inbox To: geda-user AT delorie DOT com Subject: Re: [geda-user] refdes index locations In-reply-to: <4FFEB545.5010000@laserlinc.com> References: <4FFD6CF7 DOT 60707 AT laserlinc DOT com> <20120711201719 DOT A8816819FBAB AT turkos DOT aspodata DOT se> <4FFEB545 DOT 5010000 AT laserlinc DOT com> Comments: In-reply-to Joshua Lansford message dated "Thu, 12 Jul 2012 07:30:13 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-Id: <20120712155653.7D5EE819FBB2@turkos.aspodata.se> Date: Thu, 12 Jul 2012 17:56:52 +0200 (CEST) From: karl AT aspodata DOT se (Karl Hammar) X-Virus-Scanned: ClamAV using ClamSMTP Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Joshua: > > Very nice, but shouldn't you pick the center of the component instead > > of its lower left, or why not picking the lower left of the refdes, > > which is the thing one is loocking for when searching, that should be > > easy to find for the program ? > That is a good point. I'm impressed you figured that out. Did you get > the script running or did you read though script? if line.startswith( "C " ): lineSplit = line.split() x = int( lineSplit[1] ) y = int( lineSplit[2] ) symName = lineSplit[6] justSawComponent = True refdes = "" > If you get an itch for it, send me a patch which corrects it. If the > script is not parsing the component width, it shouldn't be that > hard to add it to the model. Remeber the "T" line (x,y)'s instead, if next one is refdes=xx, use it. > > Instead of forcing the user to tell the program the bonding box, why > > not scan through it (recursively), let the program do the job? > I thought about that and while finding the width and height of the page > is somewhat straightforward, scanning and obtaining the number of visual > rows and columns the sheet is divided into could be interesting. (What > is the "largest" single letter, and single number text field ..) > Especially as you would also be guessing as to which symbol even is the > title page. (who's the biggest, who has the term title in the > filename...) It would take less work and be more reliable, to go ahead > and create all the entries for all the different title pages. If > someone were to create their own brand new sheet the guess algorithms > for identifying and profiling the sheet might not work anyway. Ok, I'll pass on this one. > > What is the interface to finding symbols, is it in libgeda or in scheme? > The python script parses the ASCII schematic files themselves. (woot > human readable format) Yes, but the .sch-file doesn't tell you where your symbols are, it just tells you the basename. Regards, /Karl Hammar ----------------------------------------------------------------------- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57