On Sun, Jan 18, 2009 at 08:32:58PM +, Peter Clifton wrote:
All the text editors I use (emacs / gvim / ...) can paste text from
the
CLIPBOARD, and Xterms can even paste text from the clipboard (I
presume
they push it into the pty as if the user had typed it?).
At least on my system xterm (a
On Sun, 2009-01-18 at 13:44 -0500, der Mouse wrote:
> >> I would actually recommend you use PRIMARY, not CLIPBOARD (though I
> >> also recognize that you may not have meant "clipboard" to be the
> >> technical term here).
> > No, Peter B and I discussed this, and we explicitly did _not_ want to
> >
On Jan 17, 2009, at 11:02 PM, John Griessen wrote:
>> You can't reliably run gattrib on a schematic you've got up in
>> gschem.
>> If you're not careful about saving and reloading pages as they're
>> modified elsewhere, you end up losing changes.
>
> I use gattrib with gschem running. I just s
>> I would actually recommend you use PRIMARY, not CLIPBOARD (though I
>> also recognize that you may not have meant "clipboard" to be the
>> technical term here).
> No, Peter B and I discussed this, and we explicitly did _not_ want to
> use PRIMARY.
Hm, then I suspect you'll find yourself unable
DJ Delorie wrote:
>> or will pcb support ASIC layouts in the future?
>
> I don't expect so, but I don't see how that relates to what gschem is.
>
I can see using pcb really soon on organic semiconductor materials similarly to
how I amusing it on conductive ink mask patterns.
>> Exit? Not neces
On Sat, 2009-01-17 at 16:58 -0500, der Mouse wrote:
> > Currently, if you 'copy' in gschem and 'paste' in another program,
> > nothing useful happens. We should ideally try and use the X
> > clipboard.
>
> I would actually recommend you use PRIMARY, not CLIPBOARD (though I
> also recognize that y
> Currently, if you 'copy' in gschem and 'paste' in another program,
> nothing useful happens. We should ideally try and use the X
> clipboard.
I would actually recommend you use PRIMARY, not CLIPBOARD (though I
also recognize that you may not have meant "clipboard" to be the
technical term here)
On Sat, 17 Jan 2009 18:54:17 +, Peter Clifton wrote:
>> Transfer of selection between schematics and layout seems an easier
>> task and would be very helpful. I used this a lot with protel95.
> Did you mean cross-probing by "transfer of selection"?
Yes, cross-probing of whole groups of symbo
On Saturday 17 January 2009 18:46:14 Kai-Martin Knaak wrote:
> On Sat, 17 Jan 2009 18:24:31 +, Peter Clifton wrote:
> > Realistically, I don't expect to see copy-paste between schematic and
> > board layout any time soon. It's getting to the edge of what fits the
> > physical copy+paste UI meta
On Sat, 2009-01-17 at 18:46 +, Kai-Martin Knaak wrote:
> On Sat, 17 Jan 2009 18:24:31 +, Peter Clifton wrote:
>
> > Realistically, I don't expect to see copy-paste between schematic and
> > board layout any time soon. It's getting to the edge of what fits the
> > physical copy+paste UI met
On Sat, 17 Jan 2009 18:24:31 +, Peter Clifton wrote:
> Realistically, I don't expect to see copy-paste between schematic and
> board layout any time soon. It's getting to the edge of what fits the
> physical copy+paste UI metaphor. Drag/drop would also be a stretch.
Transfer of selection betw
On Sat, 2009-01-17 at 12:39 -0500, DJ Delorie wrote:
> > Let's assume that, for now, we're just going to implement copying
> > and pasting of schematic data.
>
> It would be up to the receiving application (pcb in this case) to
> interpret the incoming data, anyway. gschem would only need to
> pu
> Let's assume that, for now, we're just going to implement copying
> and pasting of schematic data.
It would be up to the receiving application (pcb in this case) to
interpret the incoming data, anyway. gschem would only need to
publish its data format and the magic cookie it uses to say "it's
DJ Delorie wrote:
> It would be really cool if you could cut/copy in gschem, and paste in
> *pcb*, and have the right footprint show up.
So you mean that cut gets text that contains a reference and pcb could resolve
the data, (footprint), it refers to?
Sounds fab.
John G
--
Ecosensory Austin
[snip]
>Currently, if you 'copy' in gschem and 'paste' in another program,
>nothing useful happens. We should ideally try and use the X
>clipboard.
No objections to any of the options.
-Ales
__
On Friday 16 January 2009 23:22:11 DJ Delorie wrote:
> It would be really cool if you could cut/copy in gschem, and paste in
> *pcb*, and have the right footprint show up.
Let's assume that, for now, we're just going to implement copying and pasting
of schematic data.
> or will pcb support ASIC layouts in the future?
I don't expect so, but I don't see how that relates to what gschem is.
> Furthermore, we want gschem to be a front-end for simulation
> systems.
I'll lump "simulator" in with other "layout systems" then. If I had a
word that meant "all those
John,
So until this AI exists the cut and paste interface should allow an
application to state "Not Supported" but one application shouldn't limit
what other applications can do. Something about graceful degradation.
Steve Meier
On Fri, 2009-01-16 at 21:41 -0700, John Doty wrote:
> On Jan 16, 20
On Jan 16, 2009, at 9:34 PM, Steve Meier wrote:
> For a simulator, wouldn't you want to select a section of a schematic
> and say simulate this?
I'd love it, but that's beyond the state of the art for AI. In
practice, simulation requires a lot of thought in the design of the
"test fixture".
John,
For a simulator, wouldn't you want to select a section of a schematic
and say simulate this?
I think, thinking about scenarios leads to requirements. So to say be
able to select an area of a schematic and then transmute that schematic
section into the needs of the next application.
If the
On Jan 16, 2009, at 8:48 PM, DJ Delorie wrote:
>
>>> A program should do one thing well. Capturing circuit information
>>> (regardless of what that is) and providing that to a layout system
>>> (regardless of what *that* is) is that one thing here.
>>
>> As stated by you, that's two things.
>
>
My mental picture was that if I select a block from gschem and paste it
into pcb that the correct land patterns and the netlist between pins of
those land patterns should "walla" "appear" in pcb.
This is of course "futuristic"! But shouldn't the design of a cut and
paste operation be forward looki
> > A program should do one thing well. Capturing circuit information
> > (regardless of what that is) and providing that to a layout system
> > (regardless of what *that* is) is that one thing here.
>
> As stated by you, that's two things.
Sigh. I'll try to word it as one thing. "Be a design
On Jan 16, 2009, at 7:52 PM, DJ Delorie wrote:
>
>> "A program should do one thing well". Netlisting and layout are not
>> the charter of a schematic capture program.
>
> But 90% of the common users expect "obvious" things to work. Cutting
> and pasting between applications should "just work".
> "A program should do one thing well". Netlisting and layout are not
> the charter of a schematic capture program.
But 90% of the common users expect "obvious" things to work. Cutting
and pasting between applications should "just work". The gEDA+pcb
flow should "just work". Yes, there will be
On Jan 16, 2009, at 7:40 PM, Steve Meier wrote:
> footprint and netlist
gschem (correctly IMNSHO) doesn't even know what these are, as they
depend on which flow you're using.
"A program should do one thing well". Netlisting and layout are not
the charter of a schematic capture program.
footprint and netlist
On Fri, 2009-01-16 at 18:22 -0500, DJ Delorie wrote:
> It would be really cool if you could cut/copy in gschem, and paste in
> *pcb*, and have the right footprint show up.
>
>
> ___
> geda-user mailing list
> geda-user@moria.
It would be really cool if you could cut/copy in gschem, and paste in
*pcb*, and have the right footprint show up.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
On Jan 16, 2009, at 3:45 PM, Peter TB Brett wrote:
>
> Currently, if you 'copy' in gschem and 'paste' in another program,
> nothing useful happens. We should ideally try and use the X
> clipboard.
>
> I propose that we enable (in the following order):
>
> 1. Copy in gschem, paste in text editor.
Currently, if you 'copy' in gschem and 'paste' in another program,
nothing useful happens. We should ideally try and use the X
clipboard.
I propose that we enable (in the following order):
1. Copy in gschem, paste in text editor. Should it paste schematic file
source code equivalent to copied
30 matches
Mail list logo
