Re: gEDA-user: gschem crash on object drag
Abhijit Kshirsagar abhijit...@gmail.com writes: I'm using gschem 1.6.1.20100214 on an Ubuntu 10.10 machine. I'm making a simple schematic - just a couple of devices and just one page. I find that it crashes with a Segmentation fault reported on my terminal. Please upgrade to gEDA 1.6.2, which contains fixes for several bugs in 1.6.1, and see if that resolves your problem. If upgrading does not seem to fix the bug, please provide detailed steps to reproduce the crash. There is at least one known crash bug in 1.6.2: https://bugs.launchpad.net/geda/+bug/704829 The bug is fixed in the latest unstable 1.7.x releases, but we do not provide Ubuntu packages for these. Regards, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gschem gnetlist problem
Colin D Bennett co...@gibibit.com writes: On Wed, 13 Jul 2011 02:20:22 +0200 Kai-Martin Knaak k...@familieknaak.de wrote: I remember to have been scratching my head on this, when I did my first BOMs. My students tend to fall into this trap, too -- Even when they were told they'd need an attrib file. The keyword backtrace suggests a severe crash had happened. I guess, it is a scheme one-liner to text for existance of the file and issue a newbie friendly message. Or even better, produce a sensible default file on the fly. Peter B? John D.? Can you whip up such a line? How about allowing the user to specify the name of the 'attribs' file on the gnetlist command line? Sometimes I would like to produce BOM listings with different sets of fields (e.g., parts list for assembly vs. BOM for other purposes). Yes, both are pretty straightforward to add (I think), but I don't have time right now. File feature requests? :-) Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: command autocomplete (gtk)
Andrew Poelstra as...@sfu.ca writes: In pcb right now (and with my autocomplete patch) if you run a command (say, About), then hit :Esc to open and close the command line, it will re-run the command. Is this expected behavior? Can I remove it? That sounds very much like a bug to me. I think you should remove it, personally. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gEDA file format - couple of questions on attributes.
Kai-Martin Knaak k...@lilalaser.de writes: Rather than restrict the input to a smallish subset, the code should deal gracefully with as much of UTF8 as possible. Um, the code deals just fine with attribute names containing arbitrary UTF-8. It's just not *recommended* to use attribute names that don't match the regexp I supplied. What is the rationale to this restriction? It's not a restriction, it's a recommendation. The main reasons are that: 1) We need to support gnetlist backends when gEDA is compiled against Guile 1.8.x, which doesn't understand UTF-8. BTW, if you want to use non-ASCII characters in your attributes, I highly recommend to use Guile 2.x. 2) In the future, we may wish to do clever things with attribute names, perhaps giving characters like '#', '/' or ':' on the left hand side of the '=' in an attribute special meaning to gnetlist. If you stick to the regexp I provided, you will be future-proof. To repeat: you can use any Unicode codepoints you like in attribute names at the moment. However, at the moment it's safest to stick to '^[a-z][a-z0-9_-\.]*$'. Regards, Peter P.S. To clarify, attributes *must* match '^(.*[^ ])=([^ ].*)$' (multiline) at the moment. -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Unicode and Guile [was: couple of questions on attributes.]
[ This is a really dull e-mail. You can probably safely skip it. ] John Doty j...@noqsi.com writes: On Jun 28, 2011, at 4:17 AM, Peter Brett wrote: 1) We need to support gnetlist backends when gEDA is compiled against Guile 1.8.x, which doesn't understand UTF-8. BTW, if you want to use non-ASCII characters in your attributes, I highly recommend to use Guile 2.x. Actually, UTF-8 attributes (names and values) work fine with Guile 1.8-based gEDA. The clever design of UTF-8 makes code intended for ASCII just work so long as it doesn't need to pick wide characters out of a string. Let me spell it out: Guile 1.8.x does not understand UTF-8, which means the vast majority of standard Scheme string functions don't work according to the RnRS specifications [1]. Guile 2.x does understand UTF-8, which means that all standard Scheme string functions work according to the RnRS specifications. If you are moderately careful, you can use Guile 1.8.x without running into string encoding problems [2]. If you use Guile 2.x, you won't run into string encoding problems. Therefore, I *recommend* that if you wish to use non-ASCII Unicode in your schematics or symbols, you should upgrade to using Guile 2.x. Mainly because then things *will* actually just work. I hope that's clear enough for everybody. Peter [1] N.b. I do not necessarily mean that they don't work. I *do* mean that you can quite efficiently generate invalid UTF-8 that makes apps barf and people who triage bug reports cry. Luckily, most gnetlist backends don't use anything other than string=?, format and string-append, which have no issues. [2] Believe me, string encoding problems are incredibly tedious. -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gEDA file format - couple of questions on attributes.
[Re-sending to list, since there's been additional interest.] Gareth Edwards gar...@edwardsfamily.org.uk writes: Hi there, I'm still intermittently working on a parser in Python for the gEDA/gaf file format and I have a couple of questions that I hope the list can answer. 1) are there any restrictions on the characters in attribute names and values (other than no = in the name) ? At the moment, gEDA allows names to include any UTF-8 character other than '=' or \0, but (for some reason) they must not end with a space. However, I strongly recommend that you only use attribute names that match: ^[a-z][a-z0-9_-\.]*$ Since you're writing a parser, consider emitting a warning if you encounter an attribute name which doesn't. 2) Can attributes be multiline text or are they always single line text (but perhaps several)? Yes, they can be multiline (any UTF-8 character other than \0). Also, they (randomly) may not start with a space. Since the gEDA file format requires UTF-8, please make sure your parser raises the alarm if it encounters encoding errors. Cheers, Peter P.S. I'm hoping to tighten up the rules on attributes soon-ish. -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Scheme API branch merged
commit 23181c3de91dc22ab40d6a7080e3b094bd4ca0ac Merge: c4ca820 242562c Author: Peter TB Brett pe...@peter-b.co.uk Date: Mon Jun 27 15:24:08 2011 +0100 Merge branch 'peter-b/guile-scheme-api'. Thanks to the following people who provided useful input that helped with the development of these changes: * Peter Clifton * Ludovic Courtès * John Doty * Gareth Edwards * John Griessen * Neil Jerram * Josh Jordan * Dan McMahill * Maciej Pijanka * Ivan Stankovic * Matthew Wampler-Doty * Andy Wingo -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gschem saving symbols
Josh Jordan outerspacema...@yahoo.com writes: Thanks for the help. I am having trouble running your scheme branch. When I open gschem it says: gschem: error while loading shared libraries: libgeda.so.40: cannot open shared object file: No such file or directory Because there is really libgeda.so.39 being installed. I just double-checked, and my branch installs libgeda.so.40 correctly. Please ensure that your LD_LIBRARY_PATH is set up properly to include whatever prefix you're installing my branch to. Your scheme way looks much simpler than my way in C that has too much text processing. That's why the branch exists. There's a bug in the script, by the way: it also needs to un-translate the resulting symbol to the page origin. I'll fix it at some point. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: help request: gnetlist not reading scm files
Ethan Swint eswint.r...@verizon.net writes: On 06/14/2011 05:27 PM, Stefan Salewski wrote: Guess: try bom2 as advertised from gnetlist -g help If that does not help, then we have to wait for a reply from smart people. I have no idea about the meaning of the error messages... Doh! caPitaliZation matters. The correct backend is bom2, not BOM2. Thanks! Just to note: unstable branch gnetlist gives more informative messages here: $ gnetlist -gFOOBAR gschem/examples/drawing_primitives.sch ERROR: Could not find backend `FOOBAR' in load path. Run `gnetlist --list-backends' for a full list of available backends. Cheers, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Fixing the attribute censorship bug
John Doty j...@noqsi.com writes: On Jun 1, 2011, at 7:58 PM, Peter Brett wrote: John Doty j...@noqsi.com writes: On May 31, 2011, at 11:02 PM, Peter Brett wrote: This script deliberately poisons the netlist. Exactly. This is consistent with other gnetlist behavior. If no attribute is found, the resulting value is unknown. So, I think Yes, and that behaviour is broken too. If no attribute is found, no value should be returned. I think that would be a severe burden on projects using heavy symbols. One often needs attributes that apply to only a subset of components, or are to be chosen downstream. unknown is a fine indicator. Being totally unable to distinguish between there is no such attribute and the attribute has its value set to 'unknown' *even if you need to* is obvious missing functionality in gnetlist. Backends can substitute magic strings (e.g. unknown) if they want to; the core should behave sanely. [snip] Let's not overload the config files with even more attack vectors for malicious designs. Some sort of plugin system? I have no idea what you mean. As you point out, per-project config files can contain executable code. And this is a *security* bug and is *broken* by design, and that facility is going away as soon as practically possible. [snip] In particular, we have -l and -m because the order in which things are defined matters. Which is stupid, and shouldn't be necessary. I thought you were asking for the possibility to load this kind of plugin from a config file. This would require additional support, to allow a config file to specify a list of expressions to be evaluated later. It would be almost trivial to add such support to gnetlist-post.scm, if that was desired. I am asking for the ability to load plugins in the same way as backends. gnetlist -p plugin -g backend Or to specify *plugin names* to load in the config file (gnetlist-plugin plugin 1) (gnetlist-plugin plugin 2) Plugins should be loaded after gnetlist's basic initialisation is complete. It shouldn't be too challenging an exercise to define a set of hooks etc. that allow plugins to modify most aspects of gnetlist's behaviour. This approach has several benefits: 1. The config file doesn't run the plugin directly, so security checks can be carried out before loading the plugin (at a minimum, forcing the plugin to be loaded from a defined plugin search path). 2. It enables command-line options like: gnetlist --list-plugins 3. It permits the removal and/or serious rethinking of the -l, -m and -c arguments (-c in particular is hilarously broken). This is more complicated to implement than your proposed hack, but has the advantages of security, usability, discoverability, and elegance. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Fixing the attribute censorship bug
John Doty j...@noqsi.com writes: On May 31, 2011, at 11:02 PM, Peter Brett wrote: This script deliberately poisons the netlist. Exactly. This is consistent with other gnetlist behavior. If no attribute is found, the resulting value is unknown. So, I think Yes, and that behaviour is broken too. If no attribute is found, no value should be returned. The only reason we can't do that at the moment is that the file format doesn't support removing an attribute. attribute_conflict makes sense when there's a conflict. In my ideal world (haha) gnetlist would generate errors on attribute conflicts. :-) What kind of error do you want? Halt netlisting and cause gnetlist to exit with a non-zero exit status. So that the problem doesn't get lost in all of the chatter. gnetlist -m censor_fix.scm (other gnetlist args) For the benefit of those who share your preference for this behaviour: does loading this scm file from a configuration file work? :-) No, because it works by redefining (unique-attribute). That's defined in gnetlist.scm, which is loaded after the configuration files. It wouldn't be hard to set up a mechanism where a configuration file could create a list of deferred actions, Let's not overload the config files with even more attack vectors for malicious designs. Some sort of plugin system? Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Fixing the attribute censorship bug
The attached script not only emits a message, but substitutes attribute_conflict for the attribute in question. Since that's not normally a legitimate value, it should help the user to detect the problem. From my perspective, I don't understand why this is better. 1.7.0 warns about undefined behaviour, and defaults to backwards-compatibility (which makes some sense IMHO). This script deliberately poisons the netlist. In my ideal world (haha) gnetlist would generate errors on attribute conflicts. :-) gnetlist -m censor_fix.scm (other gnetlist args) For the benefit of those who share your preference for this behaviour: does loading this scm file from a configuration file work? :-) Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: cvs.gedasymbols.org and gschem
k...@aspodata.se (Karl Hammar) writes: The code that executes the ...-search command is in libgeda/src/g_rc.c (relative the top of the git repo.), in the function: SCM g_rc_component_library_search(SCM path); I have changed that function to a wrapper around int C_g_rc_component_library_search(gchar *string, gchar *name, GRegex *regex); which can be more easily called recursively within c. That function contains the main body of the former function. Its added parameters are name and regex. regex is simply a precompiled regular expression matching file names ending in .sym (since we don't want to have entries that doesn't contain any symbol files). Name's function is described below under the code snippet. Nack, for a number of reasons. 1) GRegex was introduced in GLib 2.14, and during the 1.7.x cycle we are targetting GLib 2.12 or later. 2) This is an absolutely *textbook* example of the sort of thing that's more cleanly done using Scheme (Guile has all of the necessary functionality in the standard library). 3) I strongly recommend *not* using component-library-search because it gives you no control over the precedence ordering of libraries when searching for a symbol name match -- you're entirely at the mercy of the order in which the filesystem decides to give the directories to you. Even when that happens to be in alphabetical order, it's rarely what you actually want. Having it implemented in C as a core part of libgeda functionality seems to me to send the incorrect message that using it is a good idea. I've been thinking of nuking g_rc_component_library_search() and reimplementing it as a Scheme extension, and I would gladly accept a patch that does this. Regards, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Random thoughts on the future interface of PCB
However, if the goal is to attract users, there is a more powerful means: An installer of native windows versions that works with no caveats. I am *always* willing to accept patches to improve gEDA compilation and performance on Windows. However, I would need (modest) sponsorship to do the work *myself*, not only because I do not have a modern copy of Windows, but also because it would take a significant amount of relatively unproductive time to get up-to-date on the idiosyncrasies of Windows development (I think I last compiled a Windows program in about 2004). Cheers, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Random thoughts on the future interface of PCB
1. Would any of the existing maintainers be able to devote more time to gEDA if they had financial support to do so ? In my case: yes. :-/ Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: current working file name in gschemrc
(Apologies for top-posting) Postscript is passed to the standard input of the print command, which is run using popen(). It uses the default shell 'sh' to run the command. I think that the sort of behaviour you're looking for might be best achieved by writing some sort of wrapper program that accepts Postscript on stdin and a destination filename as its argument. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre - Original message - Now, I got stuck with the next step: Copy the pdf produced by cups-pdf in $HOME/PDF to the working directory of the current project. Seems like adding bash commands to the print command works. E.g. lp -d PDF -t mosfet-node; echo foobar or even lp -d PDF -t mosfet-node; ls -l $HOME Output is on stdout. The dot expands correctly to the current working directory. But if I try to access the produced pdf file with lp -d PDF -t mosfet-node; mv $HOME/PDF/mosfet-node.pdf . the second command seems to act on the state before the print command. If there was no PDF file before, I get: mv: cannot stat `/home/kmk/mosfet-node.pdf': No such file or directory If there was such a file, then this file gets copied rather then the newly produced one. It acts, as if the shell that executes the command string does not wait for the lp command to terminate before it proceeds with the mv. Is there anything I can do about this? What kind of shell is the command string executed by? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: current working file name in gschemrc
It does work! How does it work? By replacing an internal gschem script? Essentially, yes. What is the prupose of ~A in this line? It's a Scheme format specifier. I think in this case I will invite you to RTF Guile Manual, since it explains the operation of the 'format' function quite well. :-) http://www.gnu.org/software/guile/manual/html_node/Writing.html#index-simple_002dformat-2052 Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: [PATCH] Fix so symbol directories cannot be loaded twice
(Apologies for top-posting, but I'm doing this from my phone) Does adding something like the following to your $HOME/.gEDA/gschemrc work? (define %component-library component-library) (define %reset-component-library reset-component-library) (define loaded-dir-libs '()) (define (component-library dir . rst) (if (member loaded-dir-libs dir) #f (begin (apply %component-library dir rst) (set! loaded-dir-libs (cons dir loaded-dir-libs) (define (reset-component-library) (set! loaded-dir-libs' ()) (%reset-component-library)) I haven't actually run it, but it might solve your problem. ;-) Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre - Original message - Dear Peter, Commands of the form (component-library dir) I had placed in a gafrc were getting called multiple times, so a lot of copies of the same directories started appearing in my symbols dialogue box. The attached patch fixes that bug by preventing the same symbol directory to be loaded twice. ~Matt Attachment check.patch ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: ANNOUNCE: New gEDA Scheme extension API
I had a problem of not following the directions. Back on track now. The error was caused by running make on git branch *master instead of the checkout we were told to do. Nevermind... Glad to hear it's now working. To those of you who're playing with the API -- I pushed out some important bugfixes yesterday that you'll probably want to make sure you have. If you checked out the code using the instructions I gave in my original e-mail, you can update by running: git pull And I've got some useful additional features on the way over the next couple of days, too. :-) Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: font problem in 1.6.0
- Original message - Nope, that wasn't it, I found another one. Christian Schilmoeller ran into this exact problem in late December; the resolution was to install all the dependencies via macports. What language locale do you have set? We had a bug where using , as the decimal separator instead of . caused huge fonts IIRC. Can't remember if that was pre-1.6.0 though. In any case, you should really be using 1.6.1! :P Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Dashed Line Disappearing Detail and 1.6.1
/usr/bin/ld: cannot find -lltdl collect2: ld returned 1 exit status Install libtool-ltdl-devel. Cheers, Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Beginner Confusion
- Original message - http://www.gpleda.org/sources.html claims that the development version is 1.5.4 and that the stable version is 1.6.0 Shouldn't the development version be a 1.7.x type of number based on a stable 1.6? There hasn't yet been a release in the 1.7.x series since the 1.6.x stable branch was forked. If you want to try the latest changes, check out the 'master' branch from the git repo. Cheers, Peter ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: gschem 1.5.2.20090328
- Original message - I've hit this problem a couple of times now. Any plain text on the schematic is messing up the backend processing. The most recent problem occurred when I made a very minor change, rotated a connector on the schematic. Gnetlist -g PCB reports read garbage and points to the sch file that I just modified. Please upgrade to 1.6.0 and try again. It's possible that whatever issue you're encountering has been fixed in the last 9 months. Peter ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: xgsch2pcb does not play nice with hierarchical design
- Original message - My current project contains a moderate hierarchy. It is basically a main schematic sheet with two sub-sheets. By default, only the main schematic appears in xgsch2pcb. To edit the sub-sheets, I have to fall back to the Down Schematic action in gschem. This kind of defeats the purpose of a project manager. Not really. Speaking as the designer of xgsch2pcb, it was intended to be a *minimal* X frontend to gsch2pcb, noy a project manager. Although in order to achieve this aim it's had to become able to do some of the things that a project manager is expected to do, it's *still* not a project manager. To answer your original question, gsch2pcb needs a list of top-level schematic files as an input, so xgsch2pcb provides a way to specify a list of top-level schematics. As an added bonus, it provides a way to launch gschem to edit them. TL;DR NOTABUG, WONTFIX. (I reserve the right for Peter C. to disagree with me.) Peter ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Generate PS with gschem-lightbg, display editor in gschem-darkbg
- Original message - is there a possibility to have generated PS files in the lightbg scheme and yet still edit the gschem files with the darkdb scheme? I fiddled with the options in gschemrc -- all I achieved was to change the background color of the generated PS file to white while all foreground colors were still the same as in the lightbg-scheme (i.e., pretty unreadable). [Snip] I'm convined there's an easy way of doing it, could somebody please help me? You need to set the print colour map separately from the display colour map. See system-gafrc for details. If you're still stuck, let me know. Peter ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: PANGO FONTS MERGED: Call for testing
Ineiev ine...@gmail.com writes: On 8/17/09, Peter Clifton pc...@cam.ac.uk wrote: I just merged the pango font stuff to git HEAD. Thank you! it even shows Cyrillics. I think now I'll be able to suggest gEDA in my workplaces (the normocontrol requires Russian texts on the schematics). Unfortunately, full Unicode *printing* isn't supported yet (though save/load/display are), so I'm afraid you might need to hold off for a bit. What about different typefaces? can I somehow select a font? Not yet, sorry. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: PANGO FONTS MERGED: Call for testing
Duncan Drennan duncan.dren...@gmail.com writes: On cygwin: ./configure --prefix=/home//geda [snip] configure: error: GLib 2.12.0 or later is required. The latest official glib2 release on cygwin is 2.10.3 :( Yes, this problem was also noted by Bert Timmerman. GLib 2.12 is a dependency of GTK+ 2.10, which we currently require. I have difficulty believing that the Cygwin GTK+ package hasn't been updated more recently than May 2006 (actually, that's frankly ridiculous). I recommend that you whinge at the Cygwin package maintainers for the GTK+/GLib packages. Alternatively, you could try building your own GTK+ packages, if you're feeling keen. Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: PANGO FONTS MERGED: Call for testing
Bill Gatliff b...@billgatliff.com writes: Peter Clifton wrote: I tried (and failed) to find a vector format OpenOffice could paste. Basically it will only accept its own format for vector drawing (even WMF/EMF paste an image when accepted via the clipboard). The converters I found to emit the required format were variously broken - mainly with text handling. I haven't tried to paste into OpenOffice, but I have had good luck merely exporting from gschem to a ps file, and then using gimp et. al to take it from there. I routinely convert to eps and then import into LaTeX, for example. One big advantage of ODF export would be the ability to embed schematics losslessly into ODF presentations. Peter ;-) -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Gschem/Custom Symbol/Path
Kai-Martin Knaak k...@familieknaak.de writes:
On Mon, 27 Jul 2009 07:37:12 +0100, Peter TB Brett wrote:
There is a directory where you can put custom gafrc files which will
automatically be loaded by system-gafrc (and won't be overwritten on the
next update).
${prefix}/share/gEDA/gafrc.d/
What would ${prefix} be on a debian system?
This should tell you. ;-)
which gschem | sed -e 's:/bin.*::'
Peter
--
Peter Brett pe...@peter-b.co.uk
Remote Sensing Research Group
Surrey Space Centre
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: merge multi symbol components
Kai-Martin Knaak k...@familieknaak.de writes: On Thu, 23 Jul 2009 20:00:01 -0400, John Doty wrote: But the idea that computers can actually automate your workflow has been lost in the personal computer era. The strength of gEDA is that you *can* automate it: You have praised this many times before. Ironically, one of the weaknesses of gEDA is a lack of scriptability. Even pcb with all its actions is only half way there. All I can say is, Watch this space. ;) Peter -- Peter Brett pe...@peter-b.co.uk Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: a note from a novice user
On Wednesday 26 July 2006 13:42, Igor2 wrote: Another interesting approach would be to provide a live cd. There are many live linux distros out there, so it would be possible to add gEDA to one of them. This way the 'lazy' user could try out the system without needing to understand parts of it, reading manuals, installing or anything like that. If he likes it, probably he will invest some more time in the installation process. It would be like a trial period so the user could decide to invest time or not after experiencing a working version. Here at Cambridge University Engineering Department all our undergraduate CAD teaching is done off a custom-rolled Knoppix, which includes geda (among other things). Works well for real usage, not just trying it out. :) Peter -- Quake II build tools maintainer http://tinyurl.com/fkldd v2sw6YShw7$ln5pr6ck3ma8u6/8Lw3+2m0l7Ci6e4+8t4Eb8Aen5+6g6Pa2Xs5MSr5p4 hackerkey.com pgpun9SRu3f1j.pgp Description: PGP signature ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
