Re: gEDA-user: [RFC 3/6] Embedding system revamp

["Mark Rages" <markrages@xxxxxxxxx>]

On Sat, Jan 17, 2009 at 9:56 AM, Ales Hvezda <ahvezda@xxxxxxxxxxxxxx> wrote:
>
> [snip]
>>gEDA currently allows symbols or pictures to be embedded in a
>>schematic. However, the current embedding system requires the full
>>data to be embedded for each instance of an embedded item.
>>
>>This has a number of shortcomings:
>>
>>1. It bloats filesize by requiring multiple redundant copies of the same
>>   data.
>>
>>2. It makes updating embedded symbols a hassle, especially if you
>>   accidentally miss one copy of a particular symbol.
>>
>>3. It is limited in terms of the filetypes that can be
>>   embedded. Although I can't currently think of any reason to embed
>>   file types other than images, symbols or (possibly) schematics, one
>>   might crop up in the future.
>>
>>I propose that a schematic or symbol file explicitly embed each embedded
>>file once only, to then be referred to each time a component or picture
>>object instantiates that file.
>
> 1. Disk space is cheap and it is currently really obvious how things are
>   being stored.
>
> 2. Updating symbols is not that hard (select everything and update).  Plus
>   gschlas can probably be modified to provide functionality update all
>   components in the specified schematics.  However, what happens if a
>   user does want N different versions of the same symbol embedded?
>
> 3. If you think of something other than symbols and images, please post.
>
>        I'm neutral on this one at the moment.  I think I will need to
> hear more pros/cons to justify the non-trivial amount of change (code
> wise and from a user's point of view) you are proposing.  Also, keep
> in mind that the default of gschem is not to embed symbols/pictures,
> so how many users will really take advantage of this?
>
> [snip]
>>[*] Note that we may also consider making gEDA files officially use CRLF
>>    line-endings, for better compatibility with 'quoted-printable'
>>    encoding & Windows users.
>>
>
>        Really _not_ sold on this one.  I think you will get significant
> push back if you expect POSIX users to have ^M in their files by default.
> gaf (anything really) should handle both including mixed gracefully.
>
>                                                                -Ales


I think embedded works well as-is.

gEDA should accept both styles of line endings, and emit the ones
native to its platform.

Regards,
Mark
markrages@gmail
-- 
Mark Rages, Engineer
Midwest Telecine LLC
markrages@xxxxxxxxxxxxxxxxxxx


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user