X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=wjp6pP5gDbWebeotCG+Q2+D+MtNV84P7P1wwFJj+jzk=; b=Gnn2tzptDWgswPodKbgG1VdmrFJofzt2pSd1GaI4oVOw9yoW1dMn29d33U2t9MKjYR sU8QT6vpfw33J15yDLZLTZlU67M1vjb7KtIMpoT6TqlSBYwlCig3L0c8n4zqYYArsffe EJ8Ga/x8d45N0WmnZzgJ0Do2+dtgOj8mnzLjutOvkTzpmsb4bpjzsAJ1KSpDZIJxaPU7 CeSH6HWl6y3d7APJuItUrFwYL3NoskK806pN1AMZMezjCPyBKKkZz6AZwhDA3SqS1Jne Pt7f+UUiPJ2wwgifXyj1hcJ3HkWK/x22owE9dmTPtPfinOpm7AFKo9YzYPWm+ASzl6J8 Z8iA== MIME-Version: 1.0 In-Reply-To: <4FFD92CB.1040108@ecosensory.com> References: <20120709210244 DOT 60387819FB92 AT turkos DOT aspodata DOT se> <87liisbbr8 DOT fsf AT gag DOT com> <20120710134503 DOT A63E2819FBA0 AT turkos DOT aspodata DOT se> <87pq83a5rj DOT fsf AT gag DOT com> <4FFD92CB DOT 1040108 AT ecosensory DOT com> Date: Wed, 11 Jul 2012 10:45:24 -0700 Message-ID: Subject: Re: [geda-user] One big vs. a few smaller sym's for MCU's From: Ouabache Designworks To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=14dae934125170fbff04c49169ef 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 --14dae934125170fbff04c49169ef Content-Type: text/plain; charset=ISO-8859-1 On 07/10/2012 12:24 PM, Bdale Garbee wrote: > >> Once you're past 100 pins or so on the device, breaking them up by >> function so that you can have for example a page in the schematic that's >> about the power supply, one that's about external memory interfaces, one >> that's about network interfacing, etc etc etc, that can seem quite >> useful... and make it worth the slightly larger effort of creating and >> maintaining a set of symbols. >> >> That's my take on it, at least. >> > > Having a page dominated by one huge asic where most of it is whitespace is rather useless. I would almost consider doing an inverted symbol where the pins point into the graphic and you can use the interior whitespace for the rest of the logic. Another thought would be to place a package that shows for example four op-amps but have the ability to "fragment" that symbol and relocate any of the op-amps independent of the remainders. That way you could have one huge symbol with all the functions separated but could still break it up and move the functions around. John Eaton Ouabache Designworks --14dae934125170fbff04c49169ef Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On 07/10= /2012 12:24 PM, Bdale Garbee wrote:
Once you're past 100 pins or so on the device, breaking them up by
function so that you can have for example a page in the schematic that'= s
about the power supply, one that's about external memory interfaces, on= e
that's about network interfacing, etc etc etc, that can seem quite
useful... and make it worth the slightly larger effort of creating and
maintaining a set of symbols.

That's my take on it, at least.


Having a page dominated by one huge as= ic where most of it is whitespace is rather
useless. I would almost cons= ider doing an inverted symbol where the pins point into
the graphic and = you can use the interior whitespace for the rest of the logic.


Another thought would be to place a package that shows for example = four op-amps but have
the ability to "fragment" that symbol an= d relocate any of the op-amps independent of the
remainders. That way yo= u could have one huge symbol with all the functions separated=A0 but
could still break it up and move the functions around.


John Eato= n

Ouabache Designworks
--14dae934125170fbff04c49169ef--