← Back to team overview

kicad-developers team mailing list archive

  1. kicad-developers team
  2. Mailing list archive
  3. Message #02356

Re: Latest SVN commits.

  Thread Previous • Date Previous • • Thread Next 
Wayne Stambaugh a écrit :
> Dick Hollenbeck wrote:
> 
>> No objections to your suggestions.
>> 
>
> The only change that I suggested that I though might cause some issues
> was the UI changes. The rest of it was getting the code base cleaned up
> and simplified which makes life easier for developers. I really would
> like to see Kicad use some of the higher level wxWidgets classes such as
> the document and view classes. There is some nice undo/redo support
> already built in to wxWidgets but the current Kicad design makes using
> it nearly impossible. I think this is one of the features Kicad really
> needs as far as the end user is concerned.
>
> 
>> It can be frustrating when changes a person makes are reversed out, so I 
>> think seeking agreement is wise. It might eliminate some frustration. 
>> 
>
> I remember seeing the button text colors finding their way back into the
> annotation dialog and thinking why did I waste my time. You have some
> experience in this area as well if I am not mistaken.
>
> 
>> However, folks forget, and make mistakes. But I think with an agreement 
>> in place you can catch somebody breaking it earlier than later. :)
>> 
>
> That was my goal was to inform everyone the changes I see as a way for
> Kicad to continue to move forward. I figure if I don't get too many
> objections in the next few days, I'll start moving ahead with them.
>
> 
>> Thanks for all your work!
>> 
>
> You are certainly welcome.
>
> Wayne
> 
I had some problems with my mail. Its works now!
Dick wrote exactly what i am thinking.

Kicad code must be cleaned and enhanced.
There is a lot of legacy code due to kicad history:
written in C for dos, eeschema and pcbnew started as 2 different pieces 
of software (eeschema started from a schematic found on internet, after 
starting pcbnew from scratch)
Rewritten to run under Windows and Linux.
Rewritten to use wxWindows 1.6 (formerly wxWidgets) and C++ and modified 
to use wxWidgets 2 ...
And has a lot of workaround to handle a *lot* of bugs in early versions 
of wxWidgets.
Fortunately, now wxWidgets is mature and powerful, and now complementary 
tools exist to help us (wxFormBuilder for dialogs building),
So Kicad can now uses all wxWidgets features.

Because there is now also a lot of files in eeschema and pcbnew 
directories, i am thinking also to a slight change inside these directories:
In each directory, create a sub directory like "dialogs", and move all 
dialog files in this new sub directory.
(Could be also made for "class_xxx" files).
Common pcbnew files could be also moved from pcbnew to a specific directory.

Also,thanks for all your work!

-- 
Jean-Pierre CHARRAS

Maître de conférences
Directeur d'études 2ieme année.
Génie Electrique et Informatique Industrielle 2
Institut Universitaire de Technologie 1 de Grenoble
BP 67, 38402 St Martin d'Heres Cedex

Recherche :
GIPSA-LAB - INPG
Rue de la Houille Blanche
38400 Saint Martin d'Heres

--------------020508020408070004060807 Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Wayne Stambaugh a &eacute;crit&nbsp;:
<blockquote cite="mid:49DA63CC.6010700@..." type="cite">
<pre wrap="">Dick Hollenbeck wrote:
</pre>
<blockquote type="cite">
<pre wrap="">No objections to your suggestions.
</pre>
</blockquote>
<pre wrap=""><!---->
The only change that I suggested that I though might cause some issues
was the UI changes. The rest of it was getting the code base cleaned up
and simplified which makes life easier for developers. I really would
like to see Kicad use some of the higher level wxWidgets classes such as
the document and view classes. There is some nice undo/redo support
already built in to wxWidgets but the current Kicad design makes using
it nearly impossible. I think this is one of the features Kicad really
needs as far as the end user is concerned.

</pre>
<blockquote type="cite">
<pre wrap="">It can be frustrating when changes a person makes are reversed out, so I 
think seeking agreement is wise. It might eliminate some frustration. 
</pre>
</blockquote>
<pre wrap=""><!---->
I remember seeing the button text colors finding their way back into the
annotation dialog and thinking why did I waste my time. You have some
experience in this area as well if I am not mistaken.

</pre>
<blockquote type="cite">
<pre wrap="">However, folks forget, and make mistakes. But I think with an agreement 
in place you can catch somebody breaking it earlier than later. :)
</pre>
</blockquote>
<pre wrap=""><!---->
That was my goal was to inform everyone the changes I see as a way for
Kicad to continue to move forward. I figure if I don't get too many
objections in the next few days, I'll start moving ahead with them.

</pre>
<blockquote type="cite">
<pre wrap="">Thanks for all your work!
</pre>
</blockquote>
<pre wrap=""><!---->
You are certainly welcome.

Wayne
</pre>
</blockquote>
I had some problems with my mail. Its works now!<br>
Dick wrote exactly what i am thinking.<br>
<br>
Kicad code must be cleaned and enhanced.<br>
There is a lot of legacy code due to kicad history:<br>
written in C for dos, eeschema and pcbnew started as 2 different pieces
of software (eeschema started from a schematic found on internet, after
starting pcbnew from scratch)<br>
Rewritten to run under Windows and Linux.<br>
Rewritten to use wxWindows 1.6 (formerly wxWidgets) and C++ and
modified to use wxWidgets 2 ...<br>
And has a lot of workaround to handle a *lot* of bugs in early versions
of wxWidgets.<br>
Fortunately, now wxWidgets is mature and powerful, and now
complementary tools exist to help us (wxFormBuilder for dialogs
building),<br>
So Kicad can now uses all wxWidgets features.<br>
<br>
Because there is now also a lot of files in eeschema and pcbnew
directories, i am thinking also to a slight change inside these
directories:<br>
In each directory, create a sub directory like "dialogs", and move all
dialog files in this new sub directory.<br>
(Could be also made for "class_xxx" files).<br>
Common pcbnew files could be also moved from pcbnew to a specific
directory.<br>
<br>
Also,thanks for all your work!<br>
<pre class="moz-signature" cols="72">-- 
Jean-Pierre CHARRAS

Ma&icirc;tre de conf&eacute;rences
Directeur d'&eacute;tudes 2ieme ann&eacute;e.
G&eacute;nie Electrique et Informatique Industrielle 2
Institut Universitaire de Technologie 1 de Grenoble
BP 67, 38402 St Martin d'Heres Cedex

Recherche :
GIPSA-LAB - INPG
Rue de la Houille Blanche
38400 Saint Martin d'Heres
</pre>
</body>
</html>
 --------------020508020408070004060807--

Follow ups

References

  Thread Previous • Date Previous • • Thread Next