kicad-developers team mailing list archive

[Martijn Kuipers <martijn.kuipers@xxxxxxxxx>]

Edwin,

On Mar 27, 2012, at 12:43 PM, Edwin van den Oetelaar wrote:

> Sorry for top-posting but..
> 
> I expressed a vision, which could be a direction. (like the moon 50
> years ago in 1962)

Sure, and I gave you my opinion. 

> The future will tell if it is something of value.

Off the record, I have been wrong before :-)

> I am just one person with limited time.
> Let me start on something small, you mention import/output/gcode..
> Just point me to something concrete and I will cooperate and try to be helpful.

The best I can direct you is the link Brian gave you 
<quote>
For speed, here's a direct link to the bug tracker for KiCad hosted on
Launchpad: https://bugs.launchpad.net/kicad
</quote>

When I checked it said: 558 open bugs, so there is plenty to do.

I wasn't trying to make you feel unwelcome, if I did I apologize. All help is welcome.

/Martijn

> 
> Have a good day,
> Edwin
> 
> On Tue, Mar 27, 2012 at 1:30 PM, Martijn Kuipers
> <martijn.kuipers@xxxxxxxxx> wrote:
>> 
>> On Mar 27, 2012, at 12:22 PM, Edwin van den Oetelaar wrote:
>> 
>>> First: Thanks for the warm welcome everyone.
>>> 
>>> For now I just want to get to know the project by fixing some bugs
>>> that nobody got time for. (or some feature you think most important)
>>> 
>>> As a vision I see more of the project rewritten in a
>>> python/WxPython/Cython (not SWIG, sorry folks)
>> 
>> Note: I don't know anything about Cython but a quick google.
>> 
>> I think not many devs on the list share your vision. There is some scripting work being done,
>> but that  is scripting inside KiCad and not KiCad inside scripting.
>> 
>> I also think a major rewrite of KiCad to Python/C#/QT4/Whatever, is not something that will benefit the project (my opinion).
>> 
>> There are still many things that could be done in Python/wxPython/Cython, but I foresee those as small addon programs to
>> KiCad and not the other way around. Things like importer/exporter/gcode creator/etc.
>> 
>> 
>> /Martijn
>> 
>>> This will make the whole system very flexible (while running) without
>>> need of re-compiles. Many things (including GUI and import/export) can
>>> benefit from a high-level approach with code-development in advanced
>>> editors/interactive shells (like Pycharm, DreamPie) The introspection
>>> (also of code written in Cython) will bring new levels of productivity
>>> and performance (and development speed) never seen before. (not in
>>> Eagle, not in any of the commercial software I worked with and (got)
>>> payed for)
>>> The reason that this will work with KiCAD and not with the other
>>> projects is that KiCAD is open and the rest of the world is not,
>>> everyone is 'protecting their investment' by keeping things closed and
>>> charging insane amounts of money for minor updates (which are released
>>> as new major versions, so get your wallet ready).
>>> In about 2 years KiCAD will have taken over in number of features,
>>> means of workflow-management and integration with other software.
>>> Some things that will make an impact : integration/import of
>>> mechanical drawings/footprints from others. Editing/routing with
>>> 'inference engine' in a sketch-up way. (showing alternatives in
>>> real-time, smart align and snapping)
>>> 
>>> What do you dream about?
>>> 
>>> Have a good day,
>>> Edwin
>>> 
>>> 
>>> 
>>> On Tue, Mar 27, 2012 at 12:21 PM, Fabrizio Tappero
>>> <fabrizio.tappero@xxxxxxxxx> wrote:
>>>> Welcome Edwin,
>>>> 
>>>> great to hear that you want to help. You will have plenty of chances
>>>> to do so. What is that interests you?
>>>> 
>>>> cheers
>>>> fabrizio
>>>> 
>>>> 
>>>> On Tue, Mar 27, 2012 at 12:12 PM, Martijn Kuipers
>>>> <martijn.kuipers@xxxxxxxxx> wrote:
>>>>> Hello Edwin,
>>>>> 
>>>>> You had the first step right. Joining this mailing-list is the right place to start helping KiCad.
>>>>> We have a few very core contributors (I am not one of them), who are improving KiCad in a rapid pace.
>>>>> 
>>>>> As a matter of fact, the improvements through the last year of KiCad have been amazing thanks to them.
>>>>> 
>>>>> Just for the interest, what would be your platform of choice you use KiCad on? Windows/Linux/Mac/Other?
>>>>> 
>>>>> Eeschema has undergone a major change in the format of its libraries, based on s-expressions, which I think is one of
>>>>> the best changes that happened, even though it does not directly improve the user-experience. So if you are thinking of
>>>>> things related to schema-import from other programs (Eagle v6 for example), you best look at the new format.
>>>>> 
>>>>> Other than that, I would suggest to work on some of the things you want to see improved: That gives you the best motivation.
>>>>> 
>>>>> Like other open source, you will need a sponsor for committing things. Let me advise you on some things to take care of:
>>>>> - read and follow coding-style;
>>>>> - explain what you want to achieve and how to achieve it. The list is pretty responsive
>>>>> - Make piece-wise patches, don't expect a large patch to be applied, as it is difficult to check.
>>>>> 
>>>>> KiCad is a very large code, so the core-devs are very keen on keeping the code maintainable.
>>>>> 
>>>>> Met vriendelijke groeten/Warm regards,
>>>>> Martijn
>>>>> 
>>>>> 
>>>>> 
>>>>> On Mar 27, 2012, at 10:56 AM, Edwin van den Oetelaar wrote:
>>>>> 
>>>>>> Hello everyone,
>>>>>> My name is Edwin, I have some motivation and skill to help with your project.
>>>>>> Although I am not very old yet, I do have some deep knowledge of
>>>>>> PCB's, data-formats, workflow and related software.
>>>>>> (I have been working in this field for more than 15 years)
>>>>>> 
>>>>>> I can program in almost anything, and have some visions on how to make
>>>>>> this project even better.
>>>>>> 
>>>>>> Just throw me a bone (a few bugs to get my teeth into) so I can chew
>>>>>> on it, and help you.
>>>>>> I am a bit confused about how this is coordinated, I see so many
>>>>>> websites (sourceforge/lauchpad/yahoo, some French stuff)
>>>>>> Just point me in the right direction.
>>>>>> 
>>>>>> Keep it going, and have a happy day,
>>>>>> 
>>>>>> Edwin