kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

On 02/01/2011 02:03 PM, Simon Rogers wrote:
> My initial response is that it would require all library providers to 
> run a bzr server which would be a bit more heavyweight than a dedicated 
> lib server. This may or may not be a problem.
>


Probably the easiest path to a high end part server is for us to write an
Apache module, and link in the DIR_LIB_SOURCE code, add caching similar to
what is being done in LIB, and "remote" it, via http.  Add HTTP_LIB_SOURCE
to EESCHEMA which agrees with the server on the wire protocol, i.e. how http
is used.  I suggest using compression.  Versioning is already in
DIR_LIB_SOURCE. 

If we were to link in the entire stack starting from LIB_TABLE and LIB, into
an Apache module, then the Apache module can be a client to some other server.



There is a lot more here than meets the eye, but hopefully not more than is
needed.



The interface (API actually) provides compatibility, choice, and freedom all
at once.  Nothing in the API prevents you from writing your lib server and
putting it on the moon.  Nobody cares, you just have to have a portion that
implements the LIB_SOURCE API and can be linked in with EESCHEMA which we
could call a client component.

You can use morse code between your client component and your server, or
smoke signals, or loopback sockets, or serial or USB.  Nobody cares.

The API facilitates any number of server technologies.  Again, nobody cares,
as long as the API is implemented.  You could use bit torrent.  The main and
key thing is that EESCHEMA gets its parts using the interface defined in
LIB_TABLE and LIB.  What is behind that API is LIB_SOURCE, and this is a
freedom of choice and freedom of implementation.


Dick



> On 01/02/2011 19:31, Fabio Varesano wrote:
>> I'm sorry if this question seems dumb, I'm still getting my feet wet
>> with Kicad and its source..
>>
>> but reading your document, isn't this already achievable by putting
>> your library under a versioning tool, like bzr, on a centralized server?
>>
>> FV
>>
>> On 02/01/2011 08:14 PM, Mike Goodfellow wrote:
>>> Dick, Wayne&  Jean-Pierre,
>>>
>>> A week ago Simon Rogers posted on the developers mailing list
>>> regarding some ideas with the Kicad library. A "we" was mentioned in
>>> the post, well, the "we" is made up of Simon and I - we both work
>>> together at the same company and have used Kicad for a while now.
>>>
>>> Anyway, onto the ideas. I have attached an overview document to this
>>> post, which outlines our ideas. I think what is important and needs to
>>> be stressed is that as it stands, we do not want to change anything
>>> fundamental in Kicad - instead, our work builds on functionality for
>>> the future. In fact, the idea of the sweet parser is perfect, and we
>>> require this to move our ideas forward. Furthermore, if there comes a
>>> time where it is ready to be merged into the main branch it can be
>>> done with relatively small modifications of the underlying application
>>> core, as I think you will be able to see.
>>>
>>> However, we would really like to open up the floor for comments on our
>>> proposals. We have been thinking about it for a while now. We have
>>> more detailed design documentation (in the form of pictures and
>>> flows), but these are not entirely ready for the public domain just
>>> yet (have been moving house this last week, and paid work has been
>>> getting in the way :-/ ).
>>>
>>> Please, if you have any questions or comments, let us know and we will
>>> endeavour to explain ourselves better! :)
>>>
>>> Kind regards,
>>>
>>> Mike Goodfellow
>>>
>>>
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help   : https://help.launchpad.net/ListHelp
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>