← Back to team overview

kicad-developers team mailing list archive

Re: Eeschema refactor.

 

On 12/8/2015 10:59 PM, Henner Zeller wrote:
> Hi Wayne,
> Do you have a todo-list somewhere on the things you intend to work on
> ? I think everyone on this list has a rough idea of TODOs they want to
> work on (I know I do, but I only have limited time), but if we put
> them somewhere easy to manage (maybe even the bugtracker, but I think
> it sucks big time), then this might be good.

No, but I need to make one when I find some time.  There is the road map
in the dev docs but it's a bit out of date.  I'm going to try to get the
stable release 5 road map done over the Christmas break as part of my
FOSDEM presentation prep.  This road map will have the major changes
slated for the current development cycle.  I may throw together a tiered
todo list based on difficulty and add it to the dev docs.  I've had some
stuff in my own todo list for years so maybe someone else will find the
time to do them.

> 
> On 8 December 2015 at 15:58, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>> Yesterday I committed the first of a series of patches that are part of
>> the Eeschema refactor work.  As of right now I have 41 patches queued up
>> with more to come.
> 
> Wow, that sounds prolific!

It is but it has to be done.  I am not comfortable stacking more feature
code on top of the Eeschema low level code we have right now.

> 
>>  I will apply them slowly over the next few months
>> just in case I managed to break anything.  The first few patches should
>> be pretty benign but as time goes by, they will have the potential to
>> become more disruptive.  If you find anything that is broken, please let
>> me know right away so I can get it fixed.  You should be able to see a
>> pattern pretty quickly with the first few patches.  I will slowly roll
>> the functionality of SCH_SHEET_PATH, SCH_SHEET_LIST, and SCH_SCREENS
>> into the SCH_SHEET object where the entire schematic hierarchy will
>> live.  Once that is complete, I will create a top level SCHEMATIC object
>> that will act as the top level container similar in scope to the BOARD
>> object in Pcbnew.
> 
> Nice!
> 
>>  Hopefully this transition will be fairly smooth so I
>> can start on the schematic I/O manager and the new file formats sometime
>> later this year.
>>
>> _______________________________________________
>> 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


References