> Douglas Butler wrote:
> >
> > > So what features would you want from a schematic
> > > capture program? That is not going to be easy if you
> > > need it to capture stuff from different sources, that
> > > may have different sized symbols, text, etc etc.
> > > -Roman
> >
> > Sounds good!  I would want R's C's L's transformers diodes transistors
> > (bipolar & fet) simple gates grounds (at least two types) and supplies.
> > Most importantly I would want little boxes I could put text into, for
> > all the odd components that will come up.
> >
> > Sherpa Doug
>
>
> I just whipped up a sample:
> http://centauri.ezy.net.au/~fastvid/text.gif
>
> You can get quite a complex circuit in a tight
> space and it looks clean.
> With the right software to draw them it would be
> really easy to send circuits back and forth with
> quick changes. :o)
> -Roman

>
> > I just whipped up a sample:
> > http://centauri.ezy.net.au/~fastvid/text.gif
> >
> > You can get quite a complex circuit in a tight
> > space and it looks clean.
> > With the right software to draw them it would be
> > really easy to send circuits back and forth with
> > quick changes. :o)
> > -Roman
>
> But not everybody has that kind of display...
> ...you can't complain about html postings and then post in ansi...I think
> ascii is more universal. The user just has to view it in a fixed width font
> such as Courier. This version should work on any terminal:
>
>                           |
> +12V----------------------|--------*---------
>                  +--------*        |
>                  C        C        L1
> In----R1-------B-Q1   +-B-Q2       |
>                  E    |   E        |
>                  |    +---|---*-R4-*---------Out
>                  R2       R3  +-C1-+
>                  |        |
> Gnd--------------*--------*------------------

> > > I just whipped up a sample:
> > > http://centauri.ezy.net.au/~fastvid/text.gif
> > >
> > > You can get quite a complex circuit in a tight
> > > space and it looks clean.
> > > With the right software to draw them it would be
> > > really easy to send circuits back and forth with
> > > quick changes. :o)
> > > -Roman
> >
> > But not everybody has that kind of display...
> > ...you can't complain about html postings and then post in ansi...I think
> > ascii is more universal. The user just has to view it in a fixed width font
> > such as Courier. This version should work on any terminal:
> >
> >                           |
> > +12V----------------------|--------*---------
> >                  +--------*        |
> >                  C        C        L1
> > In----R1-------B-Q1   +-B-Q2       |
> >                  E    |   E        |
> >                  |    +---|---*-R4-*---------Out
> >                  R2       R3  +-C1-+
> >                  |        |
> > Gnd--------------*--------*------------------
>
> Sure! No real problem to have a "mode" button to
> save the text in either mode. It doesn't really have
> to be ansi as such, most text character sets and windows
> fonts have those characters and since colour is not needed
> they should display on just about anything these days,
> pardon me linux people if i'm wrong. But the use of the
> proper line characters allows a compact neat diagram.
>
> Which buttons do you press on the PC keyboard to generate
> the extended characters? I've forgotten how to do it.
> Can anyone send some of the line chars to the list and
> see if they display?
> -Roman

> > > > I just whipped up a sample:
> > > > http://centauri.ezy.net.au/~fastvid/text.gif
> > > >
> > > > You can get quite a complex circuit in a tight
> > > > space and it looks clean.
> > > > With the right software to draw them it would be
> > > > really easy to send circuits back and forth with
> > > > quick changes. :o)
> > > > -Roman
> > >
> > > But not everybody has that kind of display...
> > > ...you can't complain about html postings and then post in
> > ansi...I think
> > > ascii is more universal.
> > >                           |
> > > +12V----------------------|--------*---------
> > >                  +--------*        |
> > >                  C        C        L1
> > > In----R1-------B-Q1   +-B-Q2       |
> > >                  E    |   E        |
> > >                  |    +---|---*-R4-*---------Out
> > >                  R2       R3  +-C1-+
> > >                  |        |
> > > Gnd--------------*--------*------------------

>
> I just did a test e-mail to myself in Outlook Express...  Sending an e-mail
> with extended characters prompts the user: 'Send Unicode or send As-Is'?
> As-Is results in just a bunch of question marks where the characters are
> supposed to be.  Unicode works ok.  But, I assume that not all e-mail
> viewers support Unicode...
>
> ----- Original Message -----
> From: "Roman Black" <EraseMEfastvidspam_OUTTakeThisOuTEZY.NET.AU>

> Here's trying some symbols:
> alt 127 
> 128 Ç
> 145 æ
> 146 Æ
> 168 ¿

>
> This might explain it better:
> www.jhall.demon.co.uk/currency/charset.html
>
> Look at the ISO 8859/1 standard:
>
>  !"#$%&'()*+,-./0123456789:;<=>?
> @ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_
> `abcdefghijklmnopqrstuvwxyz{|}~
>  ¡¢£¤¥¦§¨©ª«¬­®¯°±²³´µ¶·¸¹º»¼½¾¿
> ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞß
> àáâãäåæÇèéêëìíîïðñòóôõö÷øùúûüÝþÿ
>
> > Yeah, in windows, change your font to 'Terminal' or 'Lucida Console'.   If
> > you look through the page those pics are from, you'll see a side-by-side
> > comparison between standard ASCII and Windows' character set.
> >
> > But, as Paul H. pointed out, e-mail is limited to 7-bits. :(
>
> But I just emailed this:
> alt 127 
> 128 Ç
> 145 æ
> 146 Æ
> 168 ¿
>
> To myself and the pic list and both came through the
> email system fine. I'm prepared to sacrifice a few
> characters like these to have nice corners and joins.
> -Roman

>I'm still interested in writing some EE draw software
>even with crude corners, I think the amount of times
>I would use it, like in PIC .asm source I could put
>the circuit, in posts to the piclist, in making quick
>web page circuits, etc etc.
>
>                 C
>   -------R----B
>   |             E
>   |             |
>   |             |
>   ---------------
>
>Those nice joins and corners would make a lot of
>difference though. So what ascii characters are
>guaranteed to always work in emails? Are there a
>few of those we could sacrifice for nice circuits?
>Just for - and | that join up would be nice, and
>a good join + and crossover (not join).
>Any thoughts?
>
>

>
> ----- Original Message -----
> >I'm still interested in writing some EE draw software
> >even with crude corners, I think the amount of times
> >I would use it, like in PIC .asm source I could put
> >the circuit, in posts to the piclist, in making quick
> >web page circuits, etc etc.
> >
> >                 C
> >   -------R----B
> >   |             E
> >   |             |
> >   |             |
> >   ---------------
> >
> >Those nice joins and corners would make a lot of
> >difference though. So what ascii characters are
> >guaranteed to always work in emails? Are there a
> >few of those we could sacrifice for nice circuits?
> >Just for - and | that join up would be nice, and
> >a good join + and crossover (not join).
> >Any thoughts?
> >
> >
>
> I would suggest not requiring people to have special fonts installed. I
> think for example, using * for a join and + for a crossover works OK. Also
> using + for corners shouldn't introduce any confusion. Those neat line
> characters only work in DOS anyway. A friend of mine once made a font for
> the Macintosh that simply drew components instead of letters, so for
> instance if 'a' was a horizontal resistor, 'b' a vertical resistor, 'c' a
> horizontal cap, etc.
> /\/\/\/*=Martin

> But I just emailed this:
> alt 127 
> 128 Ç
> 145 æ
> 146 Æ
> 168 ¿
>
> To myself and the pic list and both came through the
> email system fine. I'm prepared to sacrifice a few
> characters like these to have nice corners and joins.
> -Roman