Re: [Kicad-developers] [PATCH] kicad icons for OSX and other OSs

[Jerry Jacobs]

2011/9/15 jp.charras 

> Le 15/09/2011 11:07, fabrizio a écrit :
>
>> jean-pierre,
>> ok, now worries, I guess I just did not upload them. well in
>> attachment you can find the folder "icons" that I think should replace
>> the current content of the "bitmaps_png/icons" folder. Inside there
>> are all main .ico files for kicad as well as .icns files for user who
>> what to build it for OS X.
>>
>> It would be great if OSX people could use these icons instead of the
>> ones spread here and there.
>>
>> Also, I think the current version of Linux does not seem to use high
>> resolution icons
>>
>> Let me know if in somehow do not meet your needs.
>>
>> cheers
>> Fabrizio
>>
>>
> I saw new .ico files (in icons.zip) are in 256x256 pixels.
>
> I don't know if this very large size is useful for OS X, but Windows needs
> 32x32 pixels format.
>

In OS X we have a icon format ranging from 16x16 till 1024x1024 pixels, so
this is not really a problem.


> 256x256 format gives very large files (350KB instead of 8KB) and are always
> displayed as 16x16 or 32x32 pixels.
> The icon_3d.ico file is useless (the 3D frame cannot be called outside
> CvPcv or Pcbnew).
> Under Windows the .ico files are used only to create a resource file, and
> not inside sources.
> Under linux, .ico files are not used.
>

Under OS X the .icns files are used and copied inside the .app folders.


> Only icon_kicad.xpm or icon_kicad.png are used, and only to create a
> desktop shortcut to Kicad
>
> For desktop shortcuts, formats bigger than 48x48 (or perhaps 64x64) are not
> very usable.
> (You can display only few 256x256 icons on an usual monitor)
>
> So currently I am reluctant to change 32x32 or 48x48 icon files by 256x256
> icon very large file
>

I will recreate the .icns files from the svg sources by hand and you
Linux/Windows people don't have to worry about it. If there are things that
don't fit well I or other OS X people will comment on the suggestion(s) or
email(s).

Kind regards,
Jerry
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATH] kicad app icons spacing + better icons + kicad left tree spacing

[Jerry Jacobs]

On 09/12/2011 06:44 PM, jean-pierre charras wrote:

Le 12/09/2011 18:02, fabrizio a écrit :

Hello,
the following patch does the following:
- fix spacing between app icons in kicad right bar
- several .svg icons were update (better look and coherence)
- hotkey list window now has the right colour and better size (it
would be good to automatically resize this window with its content but
I do not know how to do it)
- fix kicad left menu spacing and icon size (now 26pt)

Not 100 % sure if this will create a problem for other OSs but I would
propose to consider deleting the following folders:
- artwork
- bitmaps_xpm

and maybe:
- resources

Regards
Fabrizio
PS all icons need to be rebuilt (sorry for this but when I start
modifying .svg files it is not easy, for me, to be smarter than CMake)



Some thoughts:

2 kicad icons ( icon_kicad.svg and icon_kicad2.svg ) are confusing.
One is enough.
Remove icon_kicad.svg and keep new icon_kicad2.svg is better
Do not forget to rename icon_kicad2.svg to icon_kicad.svg.
icon_kicad2.svg is better because it is more readable in 16x16 or 
32x32 pixels formats,

i.e. when this icon appears in menus or task bar.

artwork is now not needed, but I am thinking it is used by MacOSX folks.
So I ask for them to remove this folder and use new .svg icons.


The folder artwork was created by me and can be removed, but the icns 
(mac icon files) in the application folders should be left alone.



bitmaps_xpm contains "old" icons.

Before removing it, the Kicad doc must be updated, and it is a lot of 
work.
(otherwise it is not understandable if we use new icons in a stable 
release,

and the current doc, at least for new users)
An it will be updated only when new icons are stable.


Maybe there is a option to fully move all the kicad documentation to 
wikibooks (wikipedia books) because it is more distributed and you don't 
need a editor except for a webbrowser. And you can create a nice PDF out 
of it. And is far more consisted than all those ugly word-processor 
templates. Just my 2uF.



In Eeschema, the icon used for annotation tool is not self explanatory.
Can you create a better icon ( like the netlist icon for instance) ?
The icon used to add an image in Eeschema is not good (I am not clever 
to do icons).

Can you create a better icon ?

Thanks.


I appreciate all your time and effort guys!

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] About the new bitmaps

[Jerry Jacobs]

On 9/8/11 3:53 PM, fabrizio wrote:

Guys,
thanks for the feedback. Please keep coming with the suggestions, I am
available to change/modify all the icons that we want for better ones.


Have a look at some default tango icons, which will look good on all 
platforms:


http://tango.freedesktop.org/Tango_Icon_Library

The colorscheme/guidelines of tango are also good how to make nice icons:
http://tango.freedesktop.org/Generic_Icon_Theme_Guidelines

Keep up the good stuff!

It's awesome already :-)


cheers
Fabrizio


On Thu, Sep 8, 2011 at 3:45 PM, Fabio Varesano  wrote:

Personally, I would suggest using the standard floppy disk icon for the Save
and Save as features. I found the current ones quite confusing (pcbnew). The
small floppy (as in eeschema) also seems to work, but I foudn myself looking
for the floppy there too.

+1 on making the place junction icon green.

A part from these little improvements, awesome work!


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] new bitmaps

[Jerry Jacobs]

This is great, it really feels like it is more clear and usable then!

Good work,


On 9/3/11 6:25 AM, Dick Hollenbeck wrote:

Showing first builds.

Still pretty rough.

May have to push a separate branch and get some patches from folks for a couple
of days, before merging.


Dick


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] [OSX] Zoom and Verticalscroll events triggerd on mousescroll event

[Jerry Jacobs]

Dear All,

On OS X I face a problem when zooming/scrolling, because it is the same 
event that is triggered in kicad. Or the zooming or scrolling needs a 
modifier key before the operation can occur. Else it will queue zoom and 
scroll at the same time which is very annoying.


We should have a look at:
common/drawpanel.cpp:
  289 void EDA_DRAW_PANEL::OnScroll( wxScrollWinEvent& event )
  758 void EDA_DRAW_PANEL::OnMouseWheel( wxMouseEvent& event )

I'm not sure how I get a modifier key inside the mouse/scroll events.

Kind regards,
Jerry


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad new look - new icons and new buttons

[Jerry Jacobs]

On 8/25/11 8:18 PM, Fred Cooke wrote:

The mac native variant doesn't have them anyway. Nor do any other mac
apps. Apple, love or hate them, know UI design.

Looking at acrobat on linux, it uses them, but only for some items, such
as copy and paste but not cut or clear, and it gives the menus an
unbalanced look. If all were there it would likely look cluttered.


Only the toolbar icons remain to exist.


This wine/windows kicad on mac, thing that I've got has them, but they
overlap the text and look awful.


I already did some work on this, to remove all the menubar icons like 
gnome does.



My vote: adios menu icons!

Fred.

On Thu, Aug 25, 2011 at 7:54 PM, Dick Hollenbeck mailto:d...@softplc.com>> wrote:

On 08/24/2011 06:13 PM, Wayne Stambaugh wrote:
 > On 8/24/2011 5:04 PM, hauptmech wrote:
 >> 16x16 was just a vote, not a demand :). Screen space is the reason.
 >> I like jerry's suggestions.
 >>
 >> I agree with him that all functionality should be in the menus,
so that
 >> hiding the toolbars does not hurt functionality. Regarding icons
in the
 >> menus, I think it's fine to  remove them.
 > We now have 2 votes for removing the menu images.

Wayne,

I am reluctant to burn the bridge, even if we stop using it.

The reason I say this is because we can quite easily have multiply
sized images,
and there will be some image size that will not screw popup menu texts.

So as a path forward, what I suggest is to strive for encapsulation,
where we
can control policy in a few lines of code.

Get a menu utility function which makes this decision, and put a single

#if
#endif

in there, with a build option to control that.

Notice I do not have these sprinkled through the code, only a single
policy point.

Dick



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad new look - new icons and new buttons

[Jerry Jacobs]

It would be much better if all the toolbar options also in the menus, 
eventually with (configurable) hotkeys. Then there should be a option 
to disable the toolbar(s) :-). Also enabling the AUI to move the 
toolbars to a other screen with overflow would be good to overcome the 
problem if one screen is to small.


I was not able to get it fixed that the toolbars put the entries that 
overflow if it is rescaled under the overflow arrow.


Hope this is clear enough.

Jerry

On Wed Aug 24 22:25:34 2011, Wayne Stambaugh wrote:

On 8/24/2011 3:41 PM, Dick Hollenbeck wrote:

On 08/24/2011 02:07 PM, Wayne Stambaugh wrote:

On 8/24/2011 2:12 PM, fabrizio wrote:

Hi,
thanks, I am glad you like them.

may I ask why you want the buttons size to stay at 16pt? is it only a
matter of space? if so, how?

For toolbar images, 26 or 24 pixels is fine for all platforms.  On some
platforms (read Windows) the larger icons will make the menu spacing much wider
than the menu text (assuming your not using a 26 pixel font).  Menu images are
disabled by default on Linux with the latest Gnome 2 (not sure about Gnome 3)
so it wont effect Linux users.  If the user enables the Gnome menu images, the
same problem will exist on Linux.  I'm not an OSX user so I cannot comment on
how the larger menu images will look.  I could personally live without images
in the menu bar.  I would prefer to use the space taken by the image for more
descriptive menu text but I'm sure there are plenty of folks who would disagree
with me on that one.

Wayne



Guys,


I committed to write an automation script which generates all the bitmaps from
*.svg to *.cpp.  I believe it will be possible to parameterize the target image
size(s).

I am now only waiting for the *.svg s.

This *.svg ->  *.cpp automation is to live outside the normal Kicad build 
process.

However, it can be done twice, or three times, resulting in multiply sized PNG
containing *.cpp directories.

Each of these directories can be checked into the source tree.

Then, the master CMakeList.txt file for the Kicad project can dynamically pick
which one gets chosen, based on a parameterized *.cpp containing directory name.

I won't take it that far, only to the point of having parameterized build
automation, with a specific view to reward Fabrizio for his efforts, meaning I
intend to honor whatever bitmap size he wants, as payment for his efforts.

Others can cater to the hobbyist computers, later.  This infra-structure will at
that point be easy to extend, but I personally will not have time for that 2nd
stage effort.

Dick


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



Dick,

I appreciate your and Fabrizio's efforts on this and think the new images will
give the Kicad user interface a much needed face lift.  I was merely pointing
out the potential pitfalls of using the larger images in the menu bar.  I was
hoping someone would take my hint and suggest removing the images from the menu
bar altogether.  I would be willing to do this if we can get a consensus among
the Kicad users and developers.  As it currently stands, they are only
displayed on Windows by default.

Wayne

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad new look - new icons and new buttons

[Jerry Jacobs]

Most icons in Mac OS X are also bigger than 16px, which makes thing 
much more easier to recognise.


I prefer 24px size.

On Wed Aug 24 20:12:57 2011, fabrizio wrote:

Hi,
thanks, I am glad you like them.

may I ask why you want the buttons size to stay at 16pt? is it only a
matter of space? if so, how?

unfortunately an icon that looks great at 26x26 might not be
understandable at 16X16. Having the two options sometimes means to
have two different sets of icons. In our case would mean about 820
icons...

I guess what I am hoping here is to understand if we could be all
happy with larger and more beautiful icons. It is important to know
that more pixel does not always mean larger icons, obviously on the
same monitor it does. I however respect your desire, I know that some
people are crazy for tiny icons that sometimes you can even miss.

Dick, yep, I did know about the currently available .svg, thanks, and
I did already use all of them ;-). It would be great if we could put
our hands on (.svg) buttons from other similar applications... Anybody
knows any good .svg source?

One of the great things about open-source is that you can fish around
big time and people would thank you for that !.

Regards
Fabrizio


On Wed, Aug 24, 2011 at 7:00 PM, hauptmech  wrote:

Beautiful buttons.

I'd like to put in my vote for menu buttons staying at 16px or having a
setting for it in preferences.

On Mon, 2011-08-22 at 21:10 +0200, fabrizio wrote:

Dear All,
I have spent some time trying to put together a new set of icons and
buttons that might make KiCad look a little better.
Here you have an example of where I am so far:
http://www.vincentresearch.com/tmp/

Would it be possible:
- to know if there is anybody interested in helping me out
- to know if there is anybody willing to help me to modify the current
code in order to accommodate the new icons/buttons.
- to have the .svg files (or some equivalent vectorial format) of the
current buttons set
-

I do not want to try to undo anything that somebody has done so far
and for this it would be great to have some feedback on the current
status and some opinions on where I am heading.

I'd like to propose to use PNG format for all icons and buttons and
64px for the KiCad buttons to start the 6 current programs. Also I'd
like to propose to drop the 16pt buttons used everywhere for a larger
24px buttons. That includes top bar buttons as well as lateral (left
and right bars). How does it sound?

Best regards
Fabrizio

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad new look - new icons and new buttons

[Jerry Jacobs]

On Tue Aug 23 08:14:26 2011, Dick Hollenbeck wrote:

On 08/23/2011 01:05 AM, Dick Hollenbeck wrote:

On 08/23/2011 01:02 AM, Dick Hollenbeck wrote:

http://docs.wxwidgets.org/stable/wx_wxbitmap.html

says PNG format is not supported on Windows version of wxWidgets, but I would
not walk away without consulting the sources.

More below.


PNG can be in the flow of information as an intermediate (man in the middle)
technology.  But I would like to treat it as almost a *.o file in a build
process.  Our real source file should be the *.svg file.  So I would like to see
us find a cross platform tool, and I think you have found that already, which
can be run from the command line to build the *.png files from the *.svg files.

I propose that we agree never to post edit the PNG files, and that they must
come from the *.SVG files.  I suggest we have a separate CMakeLists.txt file to
build the *.PNG files from the *.SVG files automatically, but perhaps not make
it a mandatory part of the build process, on the theory that some builders will
not want to have the tool which converts from *.SVG to *.PNG installed.

*.SVG ->  *.PNG


Therefore this means distributing both the *.PNG and the *.SVG files as part of
the source tree.  That is, unless you want to burden every builder with the need
to have this tool installed.


Then we have to decide on how to load the PNG files into the programs, and there
seem to be at least two ways to do this:


A) read the *.PNG files into memory from disk at program start time.

B) convert the *.PNG files into a BYTE array which is compiled into the
respective program.  But the byte array is definitely a PNG format, meaning we
get the advantage of the alpha channel support, which we do not currently have.


If B) is the chosen path.  This entails yet another step that we need to add to
the build path, meaning it needs to go into a CMakeLists.txt file and needs to
be able to happen from a commandline tool.

*.PNG ->  *.cpp

http://www.libpng.org/pub/png/book/chapter09.html

Although we are going with larger ICONs, I believe there may be no real memory
penalty since the PNG byte array is essentially be the PNG file in RAM, and it
is in a compressed format already.

So I think sticking with a BYTE array is the best path, because it will lead to
faster loading and we can continue to maintain the bitmap collection as a
library, and applications can continue to link against that.  I'm just proposing
that we put some of the build paths into a well documented CMakeLists.txt file,
one that does not necessarily run all the time as part of the normal compilation
process.

And if you are really paying attention, you recognize that the "byte array
containing" *.cpp files for the bitmaps would also need to be distributed as
part of the source tree also.


A reasonable tool to convert the *.PNG files into *.CPP is a cmake script 
itself.

In doing so, it can also write code to generate a global wxBitmap from the
filename of the PNG file.

The cmake script can be chain loaded from a CMakeLists.txt file which builds the
bitmap library.

So I rescind my proposition that the *.cpp files must be distributed as part of
the source tree.  They can be generated by a *.cmake script.


I totaly agree with building the png's by CMake out of the svg's. It 
saves alot of pain in the end.
Maybe a better approach is that the png's are shipped with kicad as 
resources and load at runtime.


Maybe we should have a look at the wxwidgets examples and 
http://zetcode.com/tutorials/wxwidgetstutorial/menustoolbars which uses 
the wxBitmap with PNG.


Kind regards,
Jerry 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad new look - new icons and new buttons

[Jerry Jacobs]

On Mon Aug 22 21:10:00 2011, fabrizio wrote:

Dear All,
I have spent some time trying to put together a new set of icons and
buttons that might make KiCad look a little better.
Here you have an example of where I am so far:
http://www.vincentresearch.com/tmp/

Would it be possible:
- to know if there is anybody interested in helping me out


I'm willing to help, i'm very experienced with inkscape.


- to know if there is anybody willing to help me to modify the current
code in order to accommodate the new icons/buttons.


The only code we need to change is to move it to PNG, because no 
vectorial format is supported (as far as I know).



- to have the .svg files (or some equivalent vectorial format) of the
current buttons set
-

I do not want to try to undo anything that somebody has done so far
and for this it would be great to have some feedback on the current
status and some opinions on where I am heading.

I'd like to propose to use PNG format for all icons and buttons and
64px for the KiCad buttons to start the 6 current programs. Also I'd
like to propose to drop the 16pt buttons used everywhere for a larger
24px buttons. That includes top bar buttons as well as lateral (left
and right bars). How does it sound?


I did put some svg rework in the artwork in the sourcetree of the main 
applications. Mainly I did it for use with Mac OS X because 32x32 was 
way to small for most purposes. See here: 
http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/files/head:/artwork


Kind regards,
Jerry


Best regards
Fabrizio

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] New utility: PcbCalculator

[Jerry Jacobs]

Maybe you should have a look at http://mcalc.sourceforge.net and 
http://wcalc.sourceforge.net also.


On 05/08/2011 22:02, jean-pierre charras wrote:

I added a new utility in Kicad: PcbCalculator
It can be used to calculate transmission lines impedances, or resistors
to set the value of the output of a regulator.

Please, feel free to add features to this utility (It is not a finished
work, but is it very usable).
This is easy because the code do not use the existing Kicad code, so no
need to know the internal Kicad code.

And I need your opinion about the interest of this kind of tool.




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Mac OS X Performance Questions

[Jerry Jacobs]

On 7/20/11 1:37 PM, Fred Cooke wrote:

Hi, I tried it, but the performance was still abysmal. I find it
unusable. Scrolling and zooming are one frame per second and it really
disrupts anything that you are trying to do.


The native performance on Mac OS X compared to Windows and Linux is a 
very big difference.



A friend of mine, who is a Mac lover, created this for testing, it's
made with "winebottler" and works acceptably. I just fired it up at the
same time as your custom one to compare performance with the same
machine load/available cpu time and it is really night and day.

Excuse the win UI. If the download disappears, let me know, I will
upload it to my server instead.

200 meg http://sorsacode.com/KiCad.app.zip


I tried it, and it is not bad at all if you want something that just 
works (That is why I still have Mac OS X noted as experimental on the 
kicad wiki). It draws tons faster then the native build (even with the 
X11 dependency).



Regards,

Fred.


Good luck, and maybe in some time the native build will have the same 
performance as on the other platforms.



On Wed, Jul 20, 2011 at 12:32 PM, Marco Serantoni
mailto:marco.serant...@gmail.com>> wrote:

Try this one http://www.mdx4.org/uploads/kicad/Kicad-20-MAY-2011.zip

This uses an hacked version of wx-widgets to enable the Native
wxOverlay, the result is a working Kicad with some small issues but
i think still usable.

This was possible after the fix of some problems with the UserScale
( http://trac.wxwidgets.org/ticket/13216 ) now in the svn tree.

Still missing a native wxOverlay implementation under Cocoa:
http://trac.wxwidgets.org/ticket/12894
(The default implemented flickers)

--
Marco



On Tue, Jul 19, 2011 at 8:57 PM, Fred Cooke mailto:fred.co...@gmail.com>> wrote:

OK, back from the shops!

kicad_osx_v3009_STABLE

It was some daily build, I think. I'm sure you know where from.

I suspected that it was a wx issue. Can you give me a link to pester
the wx devs? I will happily be their tester too :-)

I have a project of my own and a bunch of people, at least two
of whom
are reading this use or want to use Kicad to design PCBs for it.

One of my biggest fans is a Mac fan, which is how I ended up with a
Mac, he'll be happy if it works reasonably on them too.

Regards,

Fred.

On Tue, Jul 19, 2011 at 6:56 PM, Marco Serantoni
mailto:marco.serant...@gmail.com>>
wrote:
 >
 > On 15/lug/2011, at 15.39, Fred Cooke wrote:
 > Fred,
 > About which version you are referring to, picked from where ?
 > And which test you have done ?
 >
 > Cause is Know,
 > wx-widgets related vs XOR (un)support on OSX, workarounded
with wxOverlay that is not correctly implemented under wxCoccoa too.
 > ask to wx-developers.
 >
 > Regards,
 >  Marco
 >
 >> Hello All,
 >>
 >> A few weeks ago I tried KiCad on OS X and although eeschema
appeared
 >> to work OK, pcbnew was unusably slow (0.3fps scrolling or
zooming in
 >> 2d, 3d, which I just, tried is acceptable). I assume that you're
 >> already aware of this, and as such I have the following
questions:
 >>
 >> Is the cause known?
 >> If not, is it being looked for?
 >> If so, is it being worked on?
 >> If so, estimated date of completion?
 >>
 >> If my assumption about this being a known issue was wrong,
can I do
 >> something to provide feedback more formally?
 >>
 >> Thank you for your time!
 >>
 >> Regards,
 >>
 >> Fred.
 >>
 >> ___
 >> Mailing list: https://launchpad.net/~kicad-developers

 >> Post to : kicad-developers@lists.launchpad.net

 >> Unsubscribe : https://launchpad.net/~kicad-developers

 >> More help   : https://help.launchpad.net/ListHelp
 >
 >





___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Mac OS X Performance Questions

[Jerry Jacobs]

Hello Fred,

There are not so many people (yet) which run KiCad on Mac OS X, I build 
it regular and also with latest development version of wxWidgets. The 
underlaying graphics layer is not the most efficient/fastest in kicad.


The scrolling/zooming with the touchpad on the macbook zooms and scrolls 
at the same time and needs to be fixed.


More testing is needed on OS X but there is only a small group of users 
and developers on this platform.


Kind regards,
Jerry

On 7/15/11 3:39 PM, Fred Cooke wrote:

Hello All,

A few weeks ago I tried KiCad on OS X and although eeschema appeared
to work OK, pcbnew was unusably slow (0.3fps scrolling or zooming in
2d, 3d, which I just, tried is acceptable). I assume that you're
already aware of this, and as such I have the following questions:

Is the cause known?
If not, is it being looked for?
If so, is it being worked on?
If so, estimated date of completion?

If my assumption about this being a known issue was wrong, can I do
something to provide feedback more formally?

Thank you for your time!

Regards,

Fred.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] FindwxWidgets.cmake

[Jerry Jacobs]

On 4/5/11 3:44 PM, Wayne Stambaugh wrote:

We currently use a custom(?) version of FindwxWidgets.cmake that was cherry
picked from a more current version of CMake than we were using at the time.
The problem is our version of FindwxWidgets is suffering from bit rot.  The
version in CMake 2.8.4 ( and possibly earlier ) has some enhances that make it
more usable when you have multiple versions wxWidgets installed on your system.
  I would like to remove our local version of FindwxWidgets.cmake and use the
one that ships with CMake.  Does anyone have any objections or reasons not to
do this?


This sounds more elegant than our current solution, CMake 2.8 is not 
hard to install even if it doesn't exist on a system. Also from 
sourcecode (which I did a couple of times).


Jerry

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] bzr rev 2945 commit: a file change breaks Kicad

[Jerry Jacobs]

On 4/4/11 10:43 PM, Wayne Stambaugh wrote:

On 4/4/2011 3:51 PM, Jerry Jacobs wrote:

On 4/4/11 9:41 PM, jean-pierre charras wrote:


Jerry,
Your last change in rev 2945 in file:
common/hotkeys_basic.cpp
breaks Kicad.

The reason is when a key is added in a menu, with a \t before it, it
become a shortcut.
Therefore type is key is exactly equivalent to click on this menu, and
this key is no more sent to the kicad key handler..


I don't know for sure, but for me on OS X all the Placement hotkeys which I
tested (in EESchema) works as expected. With wxWidgets 2.9.2 svn. And don't
break the hotkey internals, correct me if I'm wrong.


Jerry,

It is important understand that hot keys are not the same as menu or tool bar
short cuts.  The menu and tool bar commands require an extra left mouse click
to create the object associated with the current tool.  Hot keys on the other
hand, create the object immediately at the current cursor position.  While your
change may work, it had to change the behavior of the hot key.  Your change
would have remapped the hot key to the equivalent place menu command.




This break Kicad, because many hotkeys does not the same thing as you
are click on menus.
Mainly because hot keys use current mouse cursor position (start a wire,
zoom, ...)
and obviously this is not possible when clicking on a menu.
This is true for menus in frame menu bar, not pop up menus, because they
are not active.
So in many cases keys added in menus in the menu bar are only comments,
not shortcuts.


This "bad" comments "break" the Mac UI policy and are a bit ugly compared to
the defaults.


I do agree with you assessment about the comments.  Not as much from a UI
policy standpoint as from a behavior standpoint.  Pressing the W key to begin
drawing a wire is not the same as selecting the wire tool and left clicking to
begin drawing a wire.  They are not the same thing so adding the comment is
confusing.




Please, unless you known (with wxWidgets) how to see the difference
between click on a menu
and click on the corresponding hotkey,
(I do not know how to do that, and if this is possible, because the same
event is sent,
perhaps try to use wxEvent::GetEventType() to do that, but this needs a
lot of changes),
go back to the previous version of common/hotkeys_basic.cpp.
Aesthetic reason to this change is not a good reason, if this change
breaks the previous behavior.
Currently, most of hotkeys are not working properly.


It is no problem to revert back to the previous version of this file.


If that is what you are going to do, please let me know as I have a commit
ready to submit.  I hold off until I hear otherwise.


I would love to uncommit the change on common/hotkeys_basic.cpp but 
still the devil hides behind Bazaar. @Wayne, maybe you could revert this 
file to the state of rev 2944 which doesn't break. Then the commits can 
carry on.


Still I'm trying to learn the bzr way of doing SCM, sorry guys!


Wayne


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] bzr rev 2945 commit: a file change breaks Kicad

[Jerry Jacobs]

On 4/4/11 9:41 PM, jean-pierre charras wrote:


Jerry,
Your last change in rev 2945 in file:
common/hotkeys_basic.cpp
breaks Kicad.

The reason is when a key is added in a menu, with a \t before it, it
become a shortcut.
Therefore type is key is exactly equivalent to click on this menu, and
this key is no more sent to the kicad key handler..


I don't know for sure, but for me on OS X all the Placement hotkeys 
which I tested (in EESchema) works as expected. With wxWidgets 2.9.2 
svn. And don't break the hotkey internals, correct me if I'm wrong.



This break Kicad, because many hotkeys does not the same thing as you
are click on menus.
Mainly because hot keys use current mouse cursor position (start a wire,
zoom, ...)
and obviously this is not possible when clicking on a menu.
This is true for menus in frame menu bar, not pop up menus, because they
are not active.
So in many cases keys added in menus in the menu bar are only comments,
not shortcuts.


This "bad" comments "break" the Mac UI policy and are a bit ugly 
compared to the defaults.



Please, unless you known (with wxWidgets) how to see the difference
between click on a menu
and click on the corresponding hotkey,
(I do not know how to do that, and if this is possible, because the same
event is sent,
perhaps try to use wxEvent::GetEventType() to do that, but this needs a
lot of changes),
go back to the previous version of common/hotkeys_basic.cpp.
Aesthetic reason to this change is not a good reason, if this change
breaks the previous behavior.
Currently, most of hotkeys are not working properly.


It is no problem to revert back to the previous version of this file.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Sweet parser

[Jerry Jacobs]

On 4/4/11 3:59 PM, Dick Hollenbeck wrote:

On 03/25/2011 08:02 PM, Wayne Stambaugh wrote:

On 3/25/2011 4:42 PM, Dick Hollenbeck wrote:

-

When it comes to coding, we should be careful not to allow the schematic
editor to go beyond the bounds of the public Sweet API.  This should be
possible to enforce by keeping the sweet stuff as a separate DLL.

I still think the best way forward will be to have a LIB_SOURCE that simply
reads old lib files and provides PARTs through the LIB_SOURCE API, which
inherently means generating a sweet string for each part, on the fly.  This
provides a good model for any other type of library conversion facility.

Great idea.  This is one of the things I've been thinking about as well.
  Converting the existing libraries can always be done with external
conversion tools written in other languages like Python but asking user
to convert libraries this way is not very practical.


There is a swig binding that I started.  This means python or some other
language could be used to output SWEET strings, or read them, by calling
into the C++ work.

The SWIG work is not current with all the latest C++ changes, when I get all
the parsing and formatting done, I'll go back and bring the SWIG interface
up to current.


This is awesome, it makes things easier for other scripting languages to 
support. And so there is no fight in just one developer with his 
language(s) of choice.



As soon as I am done with the sweet parser, I will be doing all the Format()
functions which is the reverse of the Parse() operation, and from this code,
given that we can Format() into a STRING_FORMATTER, means we can generate
Sweet strings from the C++ structures.  These building blocks can be put
into any "converting" type of LIB_SOURCE.


Here is the output from the PART::Format() function using the shell script
generated
input test data run through the test program 'test_sch_lib_table':


(part tigers/ears/rev10
   (reference U?
 (effects (at 12 13)(font (size 0.7 1))(visible yes)))
   (value 22)
   (footprint SM0805)
   (datasheet http://favorite.pdf)
   (model Airplane)
   (property mWatts 12
 (effects (at 1 34)(font (size 0.5 1) italic bold)(visible no)))
   (keywords batcave einstein varistor)
   (line (line_width 1.5)
 (pts (xy 12 13)(xy 12 20)))
   (rectangle (start 4 5)(end 6 8)(line_width 2.3)(fill transparent))
   (circle (center 1 0)(radius 5)(line_width 2.1))
   (arc (pos 22 33)(radius 12)(start 2 4)(end 13 33)(line_width 2.3)(fill
filled))
   (bezier (line_width 2)
 (pts (xy 0 1)(xy 2 4)))
   (text "This is some text"
 (at 23 23)(justify left bottom)(visible yes)(fill filled)(font arial
(size 0.8 1.2)))
   (pin output line (at 7 8)(length 2)(visible yes)
 (signal "#WE" (font (size 0.9 1.1) bold)(visible yes))
 (padname A23 (font (size 0.9 1.1) italic bold)(visible yes)))
   (pin input line (at 8 8 0)(length 2)(visible yes)
 (signal "#WAIT" (font (size 0.9 1.1) bold)(visible yes))
 (padname A24 (font (size 0.9 1.1) italic bold)(visible yes)))
)


If anything looks long winded (overly verbose), the next couple of weeks
would be a good time to make those 11th hour changes.

'line_width' as a keyword name, seems a bit long to me, but its a minor deal.


For me this looks very very good, far better than XML. This is just the 
UNIX KISS approach to save settings and work to a harddisk.



Overall, hopefully it still looks sweet.


Thank you for you effort!

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Line drawing problem under OS X

[Jerry Jacobs]

Dear all,

I figured out that kicad under OS X has problems with hairline drawing
not only with the sheet frame. Also with the hairline width text in
gerbview DCode circles and the sketch mode in pcbnew.
I tried digging in the sourcecode for the penwidth but did not yet
figured out where I need to change to make it work.

Kind regards,
Jerry Jacobs

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Zone corner chamfers/fillets and CPolyLine

[Jerry Jacobs]

On 2/19/11 11:15 AM, Marco Mattila wrote:

Related to this discussion, I just committed a new zone dialog layout.
As always, I welcome feedback.


The dialog looks very good on OSX, only the width of the layer list 
should be a bit more wide. And also it should dynamic scale when 
resizing the window. Same as for the nets list.


http://kicad.xor-gate.org/screenshots/zone-properties.png

Good work Marco,
Jerry

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] pcbnew --plot=gerber bug and workaround (was Re: first mail, introducing command line options for eeschema and pcbnew)

[Jerry Jacobs]

The "stange extensions" refer to the layer that is plotted to gerber.
Look at http://wiki.altium.com/display/ADOH/Gerber+Output+Options

The names are aliases for the corresponding layers:

gbl = Gerber bottom layer (solder)
gbs = Gerber bottom silkscreen (mask)
gto = Gerber top overlay
gbr = Gerber (generic)
gts = Gerber top silkscreen (mask)
gtp = Gerber top layer (solder)

Correct me if I'm wrong.

On 02/19/2011 03:36 PM, Werner Almesberger wrote:
> Wolfgang Spraul wrote:
>>-p, --plot=  	plots the board 
[hpgl|gerber|ps|ps_a4|dxf]
>>-l, --layers=	comma separated 
list of layer names (default: all enabled layers)

>
> I'm getting a bit of strangeness with the automatic layer selection and
> pcbnew --plot=gerber:
>
> When I plot my atben project [1] "manually" from pcbnew, the Gerber
> files are named
>
>atben-Back.gbl atben-Comments.gbr atben-Front.gtl
>atben-Mask_Back.gbsatben-Mask_Front.gts   atben-PCB_Edges.gbr
>atben-SilkS_Front.gto  atben-SoldP_Front.gtp
>
> I never investigated what the last letter in the extension meant, but
> the second one seem to consistently indicate front ("top") or back.
>
> Now, with  pcbnew --plot=gerber --fill-all-zones -l  I get these strange
> extensions:
>
>atben-Back.gbr atben-Comments.gbr atben-Front.gba
>atben-Mask_Back.gtsatben-Mask_Front.gbr   atben-PCB_Edges.gbr
>atben-SilkS_Front.gbs  atben-SoldP_Front.gbo
>
> If I specify the layers explicitly with -l, I get the "normal" result
> again: pcbnew --plot=gerber \
> -l `pcbnew --list-layers atben.brd | tr '\012' ,` \
> --fill-all-zones atben.brd
>
>atben-Back.gbl atben-Comments.gbr atben-Front.gtl
>atben-Mask_Back.gbsatben-Mask_Front.gts   atben-PCB_Edges.gbr
>atben-SilkS_Front.gto  atben-SoldP_Front.gtp
>
> If the default worked too, this already wonderful defense against
> unpleasant surprises would be even less surprising :)
>
> [1] 
http://projects.qi-hardware.com/index.php/p/ben-wpan/source/tree/master/atben

>
> Thanks,
> - Werner

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] More OSX developer help

[Jerry Jacobs]

Now with latest version from bzr the grid is broken again on OSX.
On EESchema it is visible if I zoom in very deep. When I fit the sheet 
on my screen then the grid is gone. With the 50mil setting (biggest grid).


wxWidgets from svn revision 66868

Application: PCBnew
Version: (2011-02-11 BZR 2808)-testing
Build: wxWidgets 2.9.2 (UTF-8,compiler with C++ ABI 1002,GCC 4.2.1,wx 
containers,compatible with 2.8)

Platform: Mac OS X (Darwin 10.6.0 i386), 32 bit, Little endian, wxMac

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Sourceforge Wiki Broken

[Jerry Jacobs]

On 02/14/2011 01:40 PM, Dick Hollenbeck wrote:
> On 02/14/2011 04:07 AM, Jerry Jacobs wrote:
>> Dear all,
>>
>> When I try to load the sourceforge wiki/site then it only shows a white 
>> empty page. I think it is broken since the new update of sourceforge 
>> services. Maybe we need to update mediawiki :-), this is more secure and 
>> has better features.
>>
>> Kind regards,
>> Jerry Jacobs
> 
> 
> 
> I think I can grant sourceforge ADMIN privileges to any volunteer that wants
> to be a wiki maintainer, or administrator.

I would like to be a administrator to make it more usable and keep it
up-to-date if you agree with it.

> Certainly I will have no time to maintain the wiki myself, so others will
> have to decide how that is to be done.

This is no problem as you already offer some time on other things :-)

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Sourceforge Wiki Broken

[Jerry Jacobs]

Dear all,

When I try to load the sourceforge wiki/site then it only shows a white 
empty page. I think it is broken since the new update of sourceforge 
services. Maybe we need to update mediawiki :-), this is more secure and 
has better features.


Kind regards,
Jerry Jacobs

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] More OSX developer help

[Jerry Jacobs]

On 02/11/2011 03:42 PM, Wayne Stambaugh wrote:
> Jerry,
> 
> Thanks for testing this out for me.
> 
>>
>> Now the grid draws as expected, there are still some issues left on OSX for 
>> the
>> drawing code:
>>
>>  - When moving a object you can't see where it is while moving
> 
> Which application? EESchema, PCBNew or all of them?

EESchema works just fine, with PCBNew it is broken.

>>  - The pen-width of the sheetframe is very thin (almost invisible)
> 
> This one is odd.  On Windows and Linux the sheet frame line width looks fine.

Marco Serantoni tried to fix this some long time ago which is not upstream.

>>  - The outline modes in pcbnew are broken
> 
> I'll take a look a these issues when I get a chance to see if I figure out 
> what
> is wrong.

Thank you.

>>
>> Thank you for fixing this, i have the feeling that the drawing code is a bit
>> faster than before. This is good because it will still take some time to move
>> to the GAL.
> 
> It should be faster due the the number of intermediate function calls that 
> have
> been eliminated.  Hopefully, the drawing code is cleaned up enough that when 
> we
> finally get around to implementing the GAL code it will be a much more
> manageable task.

Better make it clean and easy to understand than hacking new features in
and make a mess again.

When I find some time I try to integrate some more Mac features so it
will feel real native. I'm still struggling to find out how I can catch
CMD+W for closing every window. The CMD key is the apple key to almost
all shortcuts. On linux and windows this is the Ctrl key. I like to use
the keyboard shortcuts but still kicad lacks the window closing hotkey.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] More OSX developer help

[Jerry Jacobs]

On 2/9/11 9:02 PM, Wayne Stambaugh wrote:

While I have some of you OSX console drivers at my disposal ;), I just
committed a patch that fixes the optimized grid drawing code and need some help
verifying that this works on OSX.  When someone with OSX gets some spare time
please change line 581 in drawpanel.cpp from:


Took only a few minutes to test :-)



#if ( defined( __WXMAC__ ) || 0 )

to:

#if 0

and rebuild.  Test the apps that use the grid to make sure the grid is drawn
correctly.  If this works on OSX, then the only other thing left to do is some
performance testing to figure out with grid drawing method yields the best
performance.  This should take care of all the drawing using wxDC for
coordinate translation.


Now the grid draws as expected, there are still some issues left on OSX 
for the drawing code:


 - When moving a object you can't see where it is while moving
 - The pen-width of the sheetframe is very thin (almost invisible)
 - The outline modes in pcbnew are broken

Thank you for fixing this, i have the feeling that the drawing code is a bit
faster than before. This is good because it will still take some time to 
move

to the GAL.

Regards,
Jerry Jacobs
- http://xor-gate.org

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] OSX developer help.

[Jerry Jacobs]

On 2/9/11 1:52 PM, Nick Lott wrote:
> Hi all,
> KiCad nightly builds of the developer branch for os x are back.
> I've fixed my scripts for working with bazaar and the system is now
building and uploading daily.
>
> Currently not building Snow Leopard compatible universal binaries
(i386 and ppc only) but I hope to have this fixed in the next couple of
days.
>
> You can find them at http://www.brokentoaster.com/kicad
>
> Let me know if this is/isn't useful or if you have any problems.

Maybe you could remove very old builds from 2008-2010 to save space, and
it would be nice if you could upload the build/upload scripts so other
people can also create snapshots for OSX.

Still we need to refine some things and create a real installer so users
don't need to do everything by hand.

Some time ago Martijn suggested to split it in different installers to
make upgrading easy. The libraries, the apps and the documentation maybe?

Greets,
Jerry

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] OSX developer help.

[Jerry Jacobs]

On 02/09/2011 04:46 AM, Richard Tobias wrote:

Hi,

I only work with OSX and Linux and am willing to do some testing.  I
have a newbe to bzr issue.  I can not figure out how to get the absolute
latest version out of bzr.  I've been using svn for years, but can not
figure this out.


This is great that more and more people testing it on OSX, some day it 
will be as good as the windows and linux port.



I do an 'bzr udate'  and 'bzr upgrade', nothing seems to give me
anything new even though I see lots of changes happening here.


This manual was very usefull to me:
http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar


So, I'm just confused on how to find anything but the current stable
head of the repository.


If you first do a bzr checkout lp:kicad and then a bzr update then you 
should not have any problems.



I know this is a stupid question, but I'm stuck.


For me bzr is also not the best tool, but it works and you get used to 
it after some time. I don´t try to do very complicated things with it so 
it won't go boom.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] OSX developer help.

[Jerry Jacobs]

On 2/8/11 11:29 PM, Dick Hollenbeck wrote:
> On 02/08/2011 03:46 PM, Wayne Stambaugh wrote:
>> On 2/8/2011 4:27 PM, Dick Hollenbeck wrote:
>>> On 02/08/2011 01:15 PM, Wayne Stambaugh wrote:
 I just committed (r2800) a fix for a rendering bug in the optional
drawing
 modes in GerbView that I caused when I removed the old scaling
code.  I have it
 working on Linux and Windows.  I need one an OSX developer to
verify this works
 on OSX.  Load a couple of layers (preferably at least one negative
layer) and
 select the two optional rendering modes on the left vertical tool
bar to make
 sure there are no rendering errors.  Zoom in and out and scroll
around a few
 times just to be sure there is no unexpected behavior.  You may get an
 assertion on debug builds when zooming all the way out due to an
invalid
 wxBitmap.  It only happens on Linux so it may or may not be an
issue on OSX.
 There's no hurry, I just want to make sure I have caused any other
issues.
 Thanks in advance for the help.

It seems not to work very bad, only the pads and tracks in outline mode
goes to no display at all. There is no outline drawn then. Maybe Marco
Serantoni should test also if his time permits. I only build in
non-debug mode most of the time.

 Wayne
>>> How do we repay this guy?
>>>
>>> Open source is so un-fair.
>>>
>>> Wayne deserves both his own Mac, and his own Mac "terminal driver",
which is
>>> you sitting at the keyboard helping him.  :)

He can hold my mac for a few secs !

>> Thanks, but I'll pass on having my own Mac.  Two OSes are more than
my poor
>> brain can handle. :)

You guys just dream to have a Mac to do more usefull things :-)

> I knew you'd say that, that's why I said you deserve your own terminal
> driver also.
>
> That's like having both a car and a driver at your disposal.  Except
in this
> case the driver takes the car home with him.  So it just feels like
you have
> your own Mac.

You only love the fat pinguin right? ;-)

> Dick
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Saving plot dialog settings

[Jerry Jacobs]

For me the dialog is very very good, and works as expected. Still the 
issue remains that the dialog can't be closed with the window button and 
the cancel button. I hacked a class function DIALOG_PLOT_BASE::OnQuit 
with EndModal(0); and it worked. Maybe the virtual functions need be 
implemented?


I saw also the eeschema postscript dialog is derived from the 
wxFormBuilder base class and there are the virtual functions implemented 
and have not problem with this.


Sorry, but I'm not to got yet with C++ so don't blame my bad thinking.

Jerry


On 2/2/11 8:26 AM, jean-pierre charras wrote:

Le 02/02/2011 00:15, Marco Mattila a écrit :

Now there should be a little something for everyone in the latest
revision. It was possible to make the plot dialog a little smaller by
getting rid of the radio buttons and moving the output directory field
(although I'm not sure it's in the right place now...). I also agree
that the dialog is a bit too square. It's hard to make the height
smaller. And it doesn't make sense to make the window wider than
necessary. I can later take a look at how using wxCheckListBox affects
the layout. Wayne, you did mean that width>height, right?

Jerry asked about saving the outputdirectory in the board file. That's
the way it has been for a few revisions already.

marco



Plot dialog looks good!
Is the dialog is a bit too square ?
Remember it size depend on platform:
You cannot have *exactly* the right size, because the actual size of a
dialog depend on system settings and the system itself
(Language, font size, how widgets are drawn by the window manager...)



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Rev 2784 broken

[Jerry Jacobs]

On 2/2/11 9:48 PM, Dick Hollenbeck wrote:

On 02/02/2011 01:54 PM, Jerry Jacobs wrote:

On 2/2/11 8:50 PM, Dick Hollenbeck wrote:

make: *** [all] Error 2
I saw Dick changed some of this code and now the OS X build is broken
with wxWidgets 2.9.2 svn

Regards,
Jerry Jacobs


$ wx-config --list

  Default config is gtk2-unicode-release-2.8

Default config will be used for output

Alternate matches:
  base-unicode-debug-2.8
  base-unicode-release-2.8


==

Jerry,

Every so often this is going to pop up as long as you continue to use the 8
bit wxString.  I don't mind it if you don't.  It is a result of wxString()
honoring a constructor in one mode that it does not in another build mode.

Jean-Pierre says we should only support UNICODE mode.  I do not agree with
him on that subject, mostly because the default build mode of wxWidgets
2.9.x on Linux is "UTF8 encoded 8 bit mode", and this is a new schmancy mode
other than ANSI mode, and other than UNICODE mode.


We definitely need as many wxString build modes as we they can think of.
Someone once said that hindsight is 20/20, but here I doubt that.  Another 6
or 8 wxString modes would be even better   :)


If you can occasionally ring this bell, and not get frustrated, we will
always be able to work through it.  I note that this is the 2nd time this
month you've had to ring the bell.

Again, I don't mind if you don't.

Dick

white:~ jerry$ wx-config --list

  Default config is osx_cocoa-unicode-static-2.9

Don't scream to soon that it is a compiler problem... maybe it is a real
wxWidgets problem (again), and we have to poke the people at wx maybe?

I only build in Unicode mode.


Well we still have no clear understanding, I do need your compiler version
please.


white:~ jerry$ gcc -v
Using built-in specs.
Target: i686-apple-darwin10
Configured with: /var/tmp/gcc/gcc-5664~105/src/configure 
--disable-checking --enable-werror --prefix=/usr --mandir=/share/man 
--enable-languages=c,objc,c++,obj-c++ 
--program-transform-name=/^[cg][^.-]*$/s/$/-4.2/ --with-slibdir=/usr/lib 
--build=i686-apple-darwin10 --program-prefix=i686-apple-darwin10- 
--host=x86_64-apple-darwin10 --target=i686-apple-darwin10 
--with-gxx-include-dir=/include/c++/4.2.1

Thread model: posix
gcc version 4.2.1 (Apple Inc. build 5664)

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Rev 2784 broken

[Jerry Jacobs]

On 2/2/11 8:50 PM, Dick Hollenbeck wrote:

make: *** [all] Error 2
I saw Dick changed some of this code and now the OS X build is broken
with wxWidgets 2.9.2 svn

Regards,
Jerry Jacobs



$ wx-config --list

 Default config is gtk2-unicode-release-2.8

   Default config will be used for output

   Alternate matches:
 base-unicode-debug-2.8
 base-unicode-release-2.8


==

Jerry,

Every so often this is going to pop up as long as you continue to use the 8
bit wxString.  I don't mind it if you don't.  It is a result of wxString()
honoring a constructor in one mode that it does not in another build mode.

Jean-Pierre says we should only support UNICODE mode.  I do not agree with
him on that subject, mostly because the default build mode of wxWidgets
2.9.x on Linux is "UTF8 encoded 8 bit mode", and this is a new schmancy mode
other than ANSI mode, and other than UNICODE mode.


We definitely need as many wxString build modes as we they can think of.
Someone once said that hindsight is 20/20, but here I doubt that.  Another 6
or 8 wxString modes would be even better   :)


If you can occasionally ring this bell, and not get frustrated, we will
always be able to work through it.  I note that this is the 2nd time this
month you've had to ring the bell.

Again, I don't mind if you don't.

Dick


white:~ jerry$ wx-config --list

Default config is osx_cocoa-unicode-static-2.9

Don't scream to soon that it is a compiler problem... maybe it is a real 
wxWidgets problem (again), and we have to poke the people at wx maybe?


I only build in Unicode mode.

Thanks,
Jerry

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Rev 2784 broken

[Jerry Jacobs]

My build fails with:

In file included from 
/Users/jerry/Projects/kicad/testing/include/wxBasePcbFrame.h:14,
 from 
/Users/jerry/Projects/kicad/testing/include/pcbstruct.h:43,
 from 
/Users/jerry/Projects/kicad/testing/3d-viewer/3d_viewer.h:24,
 from 
/Users/jerry/Projects/kicad/testing/3d-viewer/3d_aux.cpp:22:
/Users/jerry/Projects/kicad/testing/include/richio.h: In member function 
‘std::string OUTPUTFORMATTER::Quoted(const wxString&)’:
/Users/jerry/Projects/kicad/testing/include/richio.h:508: error: call of 
overloaded ‘Quoted(const char*)’ is ambiguous
/Users/jerry/Projects/kicad/testing/include/richio.h:503: note: 
candidates are: virtual std::string OUTPUTFORMATTER::Quoted(const 
std::string&)
/Users/jerry/Projects/kicad/testing/include/richio.h:505: note: 
std::string OUTPUTFORMATTER::Quoted(const wxString&)

make[2]: *** [3d-viewer/CMakeFiles/3d-viewer.dir/3d_aux.cpp.o] Error 1
make[1]: *** [3d-viewer/CMakeFiles/3d-viewer.dir/all] Error 2
make: *** [all] Error 2

I saw Dick changed some of this code and now the OS X build is broken 
with wxWidgets 2.9.2 svn


Regards,
Jerry Jacobs

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Saving plot dialog settings

[Jerry Jacobs]

On 2/1/11 7:43 PM, jean-pierre charras wrote:

Le 01/02/2011 19:20, Jerry Jacobs a écrit :

Hello Marco,

I like it but it has still some issues with wxWidgets on Mac with
version 2.9.2 from svn (rev 66766).




I committed a fix, with a minor enhancement. This issue could be a
wxFormBuilder issue,
or could be due to some changes between wxWidgets versions.
Perhaps the commit fixes this problem. Can you test it?


The radio buttons are fix for now, only the labels still overlap of the 
3th gerber option entry.


I also agree with the point from Wayne and this would enhance the dialog 
even more and make it more future proof.



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [PATCH] Saving plot dialog settings

[Jerry Jacobs]

Hello Marco,

I like it but it has still some issues with wxWidgets on Mac with 
version 2.9.2 from svn (rev 66766).


I put a screenshot on my server over here:
http://kicad.xor-gate.org/screenshots/new-plot-screen-issues.png

The issues are the format frame, and the gerber options entries labels 
overlap.


Also I can't close the window with the exit button on the window border, 
and the same goes for the close button. So I have to kill pcbnew to 
"quit the application".


A suggestion would also be to display the cwd in the Output directory 
line if the user opens the dialog, and maybe this output directory can 
be saved/loaded from the pcbfile/project.


On 2/1/11 7:10 AM, jean-pierre charras wrote:

Le 31/01/2011 21:55, Marco Mattila a écrit :

Jean-Pierre,

I have yet another suggestion for the layout of the plot dialog (see
attachment). The width would be the same as in your recent patch, but
the height would be smaller. What do you think?

marco



I like it!




___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Revision 2604 has broken cvpcb and some random warnings

[Jerry Jacobs]

On 11/12/2010 08:03 PM, Marco Serantoni wrote:
> Seen,
> 
> Mercì Jean-pierre

Thank you for this very fast response and fixes!

> On 12/nov/2010, at 19.53, jean-pierre charras wrote:
> 
>> Le 12/11/2010 19:06, Marco Serantoni a écrit :
>>>
>>>
>>> On 12/nov/2010, at 11.02, Jerry Jacobs wrote:
>>>
>>> Jerry i'm working on it.
>>
>> I committed some changes (mainly an annoying  bug when reading old eeschema 
>> files)
>> This issues should be fixed now.
>>
>> -- 
>> Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Revision 2604 has broken cvpcb and some random warnings

[Jerry Jacobs]

[ 70%] Building CXX object cvpcb/CMakeFiles/cvpcb.dir/cvpcb.cpp.o
/Users/jerry/Projects/kicad/testing/cvpcb/cvpcb.cpp: In member
function ‘virtual bool WinEDA_App::OnInit()’:
/Users/jerry/Projects/kicad/testing/cvpcb/cvpcb.cpp:87: error:
‘ID_KICAD_ABOUT’ was not declared in this scope
/Users/jerry/Projects/kicad/testing/cvpcb/cvpcb.cpp:88: error:
‘ID_OPTIONS_SETUP’ was not declared in this scope
make[2]: *** [cvpcb/CMakeFiles/cvpcb.dir/cvpcb.cpp.o] Error 1
make[1]: *** [cvpcb/CMakeFiles/cvpcb.dir/all] Error 2

Including id.h seems to fix this.

Also some not nice warning include:

[ 87%] Building CXX object pcbnew/CMakeFiles/pcbnew.dir/block.cpp.o
/Users/jerry/Projects/kicad/testing/pcbnew/block.cpp: In function
‘void drawPickedItems(WinEDA_DrawPanel*, wxDC*, wxPoint)’:
/Users/jerry/Projects/kicad/testing/pcbnew/block.cpp:653: warning:
enumeration value ‘NOT_USED’ not handled in switch
/Users/jerry/Projects/kicad/testing/pcbnew/block.cpp:653: warning:
enumeration value ‘EOT’ not handled in switch
/Users/jerry/Projects/kicad/testing/pcbnew/block.cpp:653: warning:
enumeration value ‘TYPE_NOT_INIT’ not handled in switch
/Users/jerry/Projects/kicad/testing/pcbnew/block.cpp:653: warning:
enumeration value ‘TYPE_PCB’ not handled in switch
/Users/jerry/Projects/kicad/testing/pcbnew/block.cpp:653: warning:
enumeration value ‘TYPE_SCREEN’ not handled in switch

And this:

/Users/jerry/Projects/kicad/testing/pcbnew/export_vrml.cpp:760:
warning: ‘void export_vrml_zones(BOARD*)’ defined but not used

And this:

In file included from /Users/jerry/Projects/kicad/testing/common/xnode.cpp:26:
/Users/jerry/Projects/kicad/testing/include/xnode.h: In member
function ‘wxString XNODE::GetAttribute(const wxString&, const
wxString&) const’:
/Users/jerry/Projects/kicad/testing/include/xnode.h:76: warning:
‘GetPropVal’ is deprecated (declared at
/opt/wxwidgets/65968/include/wx-2.9/wx/xml/xml.h:229)
/Users/jerry/Projects/kicad/testing/include/xnode.h: In member
function ‘bool XNODE::GetAttribute(const wxString&, wxString*) const’:
/Users/jerry/Projects/kicad/testing/include/xnode.h:80: warning:
‘GetPropVal’ is deprecated (declared at
/opt/wxwidgets/65968/include/wx-2.9/wx/xml/xml.h:226)
/Users/jerry/Projects/kicad/testing/include/xnode.h: In member
function ‘wxXmlAttribute* XNODE::GetAttributes() const’:
/Users/jerry/Projects/kicad/testing/include/xnode.h:88: warning:
‘GetProperties’ is deprecated (declared at
/opt/wxwidgets/65968/include/wx-2.9/wx/xml/xml.h:223)

And last:

In file included from
/Users/jerry/Projects/kicad/testing/eeschema/netform.cpp:53:
/Users/jerry/Projects/kicad/testing/include/xnode.h: In member
function ‘wxString XNODE::GetAttribute(const wxString&, const
wxString&) const’:
/Users/jerry/Projects/kicad/testing/include/xnode.h:76: warning:
‘GetPropVal’ is deprecated (declared at
/opt/wxwidgets/65968/include/wx-2.9/wx/xml/xml.h:229)
/Users/jerry/Projects/kicad/testing/include/xnode.h: In member
function ‘bool XNODE::GetAttribute(const wxString&, wxString*) const’:
/Users/jerry/Projects/kicad/testing/include/xnode.h:80: warning:
‘GetPropVal’ is deprecated (declared at
/opt/wxwidgets/65968/include/wx-2.9/wx/xml/xml.h:226)
/Users/jerry/Projects/kicad/testing/include/xnode.h: In member
function ‘wxXmlAttribute* XNODE::GetAttributes() const’:
/Users/jerry/Projects/kicad/testing/include/xnode.h:88: warning:
‘GetProperties’ is deprecated (declared at
/opt/wxwidgets/65968/include/wx-2.9/wx/xml/xml.h:223)

I compile on OS X with wxWidgets 2.9.2 (svn revision 65968)

Kind Regards,
Jerry Jacobs

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Interesting idea to make money with open-source

[Jerry Jacobs]

Dear all,

I bumped on a very nice article which can also be used in the KiCad
project. Or any other open-source project.

http://fsmsh.com/3439

Kind regards,
Jerry Jacobs

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] launchpad branding images

[Jerry Jacobs]

On 10/12/2010 02:31 PM, Dick Hollenbeck wrote:
> On 10/12/2010 08:07 AM, Fabio Varesano wrote:
>> There you go.
>>
>> FV
>>   
> 
> You da man!
> 
> Go see your work at launchpad.net
> 

Hope we see it soon then :-)

> 
>> On 10/12/2010 02:12 PM, Dick Hollenbeck wrote:
>>   
>>> On 10/12/2010 06:41 AM, Fabio Varesano wrote:
>>> 
>>>> I would be happy to do that! Should I use artwork/kicad.svg as
>>>> starting point?

I did redraw all of the application icons except bitmap traced and
pimped up the kicad logo because it was in a bad shape. Maybe you could
enhance it and let it look like the other ones that live in
/artwork

Kind regards,
Jerry Jacobs
- http://kicad.xor-gate.org

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] eeschema object selection and block commands

[Jerry Jacobs]

On 09/14/2010 08:42 PM, Wayne Stambaugh wrote:
> On 9/14/2010 7:28 AM, Lorenzo wrote:
>> Dear developers,
>> I'm an electronic developer and I found in the Kicad project an
>> extremely interesting EDA suite. Even it is obvious that (in this
>> moment) it cannot compete in productivity with most important EDA
>> systems (e.g. Altium, OrCAD, PADS...), it is growing fast and it has the
>> power to be used in production environments proportionally to its
>> growth. It is probably the only industrial EDA application that is
>> multi-platform, open source, and released in a stable version.
>>
>> It's about two years I'm trying to give my small contribute to this
>> project; we had a discussion about additional features some time ago,
>> and I was probably too enthusiast to identify and imagine a proper
>> implementation work flow for my ideas. The first time I saw the code I
>> was discouraged not only by the lack of comments and the French language
>> used to write the application, but also by the dirty folder structure,
>> file names, and function positions. This is pretty changed now, and the
>> code looks generally better.
>> 
>> *** SNIPPED OUT SOME STUFF ***
>>
>> Hope to “hear” from you what you think about that.

Hi Lorenzo,

I would also thank you for you time and effort you put in KiCad to
improve it. Especially because you also use it at work and normal at
work there is not much time to fix things. The code is improved very
much compared from two years ago. When I joined KiCad as a translator.
Since then there are many good new features and enhancements added.

Maybe nice to know that I give a 50 minutes talk at a Tdose in The
Netherlands again. Almost the same as previous year which you can still
look on a recorded movie.

http://kicad.sourceforge.net/wiki/index.php/Press

Jerry Jacobs

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] OSX Installer debate

[Jerry Jacobs]

On 13-09-10 20:18, Dick Hollenbeck wrote:

> Is there a way to run OSx on a virtual machine on Ubuntu?
> If not, then I'm afraid I cannot be part of "the Mac group", until
> somebody buys me a Mac.

I saw a guy at school past week running OS X in a virtual machine. After
surfing google about installing OS X 10.6 in virtualbox I found some
very nice pages, still you need a Snow Leopard install DVD and test it
for yourself. It should not be that hard to get it working as more
people want to run it on normal hardware under a virtual machine.

> Dick

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] OSX Installer debate

[Jerry Jacobs]

On 09/13/2010 05:01 PM, Martijn Kuipers wrote:
> 
> On Sep 13, 2010, at 15:20 PM, Dick Hollenbeck wrote:
> 
>> On 09/13/2010 08:53 AM, Martijn Kuipers wrote:
>>> How do we want the OSX packages to look like (installer) ?
>>> At the moment we have a DMG-generated from scripts and one generated with 
>>> CPack (I patched my CMakeList.txt with the patch from Jerry floating around 
>>> on the list).
>>>
>>> Neither are satisfactory, in my opinion.
>>>
>>> Let me explain:
>>> If we add docs and libraries to the DMG file, then it is no longer 
>>> Drag&Drop. 
>>> Normally you drag the application (on our case the Kicad folder with all 
>>> applications) to the Applications link, which are both shown by the 
>>> installer in the finder. However, if we also include libraries in the DMG, 
>>> then these need to be installed in /Library/Application Support/kicad or in 
>>> $HOME/Library/Application Support/kicad (according to Marco). We don't want 
>>> the user to drag them into the applications.
>>>
>>> I see 2 posible solutions:
>>> 1. Use packagemanager, which allows more complex installs. Disadvantage is 
>>> that you have no clue what is installed where and since there is no 
>>> uninstall I think it's rather messy.
>>> 2. Split the libraries and applications in separate DMGs. I personally like 
>>> this option, since it allows you to easily update either Kicad or the 
>>> Libraries. Not sure what to do with docs. Can we put them in a sub-folder 
>>> in the Kicad folder under applications? Same with scripts ?
>>>
>>> I would love to hear your opinions on this. 
>>>
>>> /Martijn
>>>
>>
>> There are two classes of users:
>>
>> 1) those that install from a pre-built package.
>> 2) those that install by building the source themselves.
>>
>> In the linux world there is a package manager person for each distro,
>> and he is responsible for users in class 1) on his distro.
>> So I actually think you should be talking to those people for that
>> category of user.
> 
> Sure. For Kicad who is the OSX package manager? I hope (s)he is reading this 
> list. As for Linux, I think Kicad ought to provide a static-version (should 
> fit most distros). Of course, if someone wants to add deb, rpm, etc., then 
> that is fine with me, it is just more work because of the version 
> dependancies between the different components. Wrapping a static-package 
> inside deb or rpm is not a good solution (my personal opinion).

There is no official OSX package manager (yet). Marco Serantoni did a
good job to add some work to the kicad code-base for compiling and
packing it. Then after some time I decided to also buy a macbook for
personal reason and wrote some documentation about compiling and tried
to improve it together with Marco.

Also there are still some odd things when using Kicad on OSX for example
the viewport is damn slow of PCBnew. But it is usable and functional.

>> For category 2) users, I see no reason why cmake and/or one of its
>> sibling programs cannot be used.  This makes it easier for those of use
>> that do not use OSx to stay in the conversation.
> I don't object to cmake at all. I think the DMG is not as nice as it could 
> be, but I have not spend much time looking at all the options CPack gives you.
> 
> If there is an area where Win/Linux/OSX can be different, it is in the 
> installers. And my questions were solely related to the OSX installer, where 
> I don't think the split I mentioned is so different from what we have now.  I 
> don't think there are libraries included in the kicad source, they are in 
> kicad-lib-committers/kicad/library. 

The DragNDrop is preferred for applications. And a installer or a lose
package with symbols/footprints/3d modules and documentation is shipped
seperated.

The odd on OSX is that if you did ran a installer and it dumps all the
files and folders somewhere that there is no uninstaller like under
linux package managers or windows installers. But the installer can be
made smart so it will remove old folder of a previous install.

> My suggestion would be to create 2 installers;
> - Kicad application
> - Libraries (with Libraries I mean eeschema components, footprints, 
> packages3d and modules). The name is confusing, but I did not mean things 
> like wxWidgets, Boost, etc.

For me this idea is good enough, we should not forget the Mac
UI/Packaging guidelines else it will be different from other macified
software!

> I am a "User 1" type, if I can find a recent enough version, otherwise I am 
> "User 2". But even as "User 2" I prefer to create packages and then install 
> those. 

As Kicad is getting more users and some people who write patches/join
the mailing list it is better that there will be a official Mac OS X
group within Kicad. This because things are very different on a Apple
machine than on a PC (*Win, *NIX) with user interface.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists

Re: [Kicad-developers] Menu item images on OSX

[Jerry Jacobs]

On 25-08-10 21:55, Wayne Stambaugh wrote:
> On 8/25/2010 11:21 AM, Jerry Jacobs wrote:
>> On 08/24/2010 08:50 PM, Wayne Stambaugh wrote:
>>> During my resent journey though the Kicad source I notice quite a few 
>>> instances
>>> of the following in the menu creation code:
>>>
>>> #if !defined( __WXMAC__ )
>>> item->SetBitmap( save_project_xpm );
>>> #endif /* !defined( __WXMAC__ ) */
>>>
>>
>> Yes this is far from optimal and the better solution is to have a option
>> to hide the icons in the menubars with a setting for all apps.
> 
> I was primarily thinking about the readability of the code rather than user
> preference.  Not that the user preference isn't important.  I think compiling
> for the intended platform makes sense in this case.  I also don't have the 
> time
> to commit to as user selectable solution at this time.  Creating a simple 
> macro
> that expands to nothing on OSX builds is something I can knock out in an hour
> or two.
> 
>>
>>> Is there a specific reason why images should be excluded or included from 
>>> Mac
>>> menu items?  The problem is there doesn't seem to be any consistency in it's
>>> use.On some of the applications it's used on almost all of the menu items
>>> (Kicad) and some applications virtually none at all (EESchema).  In any 
>>> event
>>> this screams creating a macro that expands to nothing on Mac builds to rid 
>>> of
>>> all of the #if/#endif statements.  Any insight from the OSX folks would be
>>> appreciated.

http://developer.apple.com/mac/library/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGMenus/XHIGMenus.html

Here you can see the Apple UI guidelines for menus.

>> I'm only a OS X user for just about a year now and find that kicad eda
>> the only application is that has imho to many icons in the menubar on OS
>> X. All the other applications that run on my apple machine don't have
>> any menubar icons or maybe a few. Some people prefer to have icons and
>> some people don't like me. And then the best of both world would be
>> disabling it by default and if people prefer they can set a checkbox in
>> the preferences.
> 
> If menu images are not used in OSX menu entries, than it makes sense to at
> least be consistent in all of the Kicad applications and not use them on OSX
> builds.  I'll take a look at the OSX UI Guidelines to see if it mentions 
> images
> in menu entries specifically and use that as my guide.

Also thunderbird doesn't have any menu icons I just figured out.

Jerry Jacobs


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad: New About Dialog

[Jerry Jacobs]

On 09/01/2010 07:02 PM, jean-pierre charras wrote:
> Rafael Sokolowski (our german translator) sent me a patch for a new
> Kicad About dialog.
> I committed it in rev  2470.
> The look is very good.
> Old code is not removed (see basicframe.cpp to select old or new dialog).

If all the other people agree, you have my vote to remove the old code.

> See below his first mail.
> 
> Rafael Sokolowski a écrit :
>>>>
>>>> Hello Jean-Pierre,
>>>>
>>>> I have seen on the todo list that there is the wish to have an
>>>> unique looking about box under different platforms. I have created
>>>> one that looks quite the same by use of wxGtk or wxMSW but I have no
>>>> occasion to test it under OS X. The API of my version is very
>>>> similar as it is currently used in KiCad by initializing this
>>>> wxAboutDialogInfo object.

The "old" one crashed and now with this implemention it seems to work on
OS X. Also I attached a patch which enables the about dialog again in
the Application menu -> About. Which is standard for all Mac applications.

Screenshot: http://kicad.xor-gate.org/screenshots

(I hope the patch is in correct encoding as Dick asked some time ago, I
use thunderbird with default settings. It went wrong with the

>>> Thanks, Your About dialog is very good. So I am interested to
>>> integrate it in Kicad.

This is indeed a very nice dialog and is more clear than the ones I have
seen before in other projects.

Kind regards,
Jerry Jacobs
- http://xor-gate.org
=== modified file 'cvpcb/cvpcb.cpp'
--- cvpcb/cvpcb.cpp 2010-02-21 20:23:16 +
+++ cvpcb/cvpcb.cpp 2010-09-01 19:43:53 +
@@ -84,8 +84,8 @@
  /* WXMAC application specific */
 #ifdef __WXMAC__
 // wxApp::SetExitOnFrameDelete(false);
-// wxApp::s_macAboutMenuItemId = ID_KICAD_ABOUT;
-   wxApp::s_macPreferencesMenuItemId = ID_OPTIONS_SETUP;
+wxApp::s_macAboutMenuItemId = ID_KICAD_ABOUT;
+wxApp::s_macPreferencesMenuItemId = ID_OPTIONS_SETUP;
 #endif /* __WXMAC__ */
 
 

=== modified file 'eeschema/eeschema.cpp'
--- eeschema/eeschema.cpp   2010-08-28 18:02:24 +
+++ eeschema/eeschema.cpp   2010-09-01 19:39:45 +
@@ -120,8 +120,8 @@
 /* WXMAC application specific */
 #ifdef __WXMAC__
 // wxApp::SetExitOnFrameDelete(false);
-// wxApp::s_macAboutMenuItemId = ID_KICAD_ABOUT;
-   wxApp::s_macPreferencesMenuItemId = ID_OPTIONS_SETUP;
+wxApp::s_macAboutMenuItemId = ID_KICAD_ABOUT;
+wxApp::s_macPreferencesMenuItemId = ID_OPTIONS_SETUP;
 #endif /* __WXMAC__ */
 
 wxFileName filename;

=== modified file 'kicad/kicad.cpp'
--- kicad/kicad.cpp 2010-05-29 18:34:18 +
+++ kicad/kicad.cpp 2010-09-01 19:51:12 +
@@ -82,8 +82,8 @@
 /* TODO fix SetExitOnFrameDelete */
 #ifdef __WXMAC__
 // wxApp::SetExitOnFrameDelete(false);
-// wxApp::s_macAboutMenuItemId = ID_KICAD_ABOUT;
-   wxApp::s_macPreferencesMenuItemId = ID_OPTIONS_SETUP;
+wxApp::s_macAboutMenuItemId = ID_KICAD_ABOUT;
+wxApp::s_macPreferencesMenuItemId = ID_OPTIONS_SETUP;
 #endif /* __WXMAC__ */
 
 WinEDA_MainFrame* frame;

=== modified file 'pcbnew/pcbnew.cpp'
--- pcbnew/pcbnew.cpp   2010-08-28 18:02:24 +
+++ pcbnew/pcbnew.cpp   2010-09-01 19:39:14 +
@@ -94,9 +94,8 @@
 {
 /* WXMAC application specific */
 #ifdef __WXMAC__
-
 // wxApp::SetExitOnFrameDelete(false);
-// wxApp::s_macAboutMenuItemId = ID_KICAD_ABOUT;
+wxApp::s_macAboutMenuItemId = ID_KICAD_ABOUT;
 wxApp::s_macPreferencesMenuItemId = ID_OPTIONS_SETUP;
 #endif /* __WXMAC__ */
 

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Can't set CMAKE_CXX variables for CMakeCache.txt on OS X

[Jerry Jacobs]

Dear all,

I'm very tired to always set variables like the one to get boost
compiling on OS X. Then always need to set the CMAKE_CXX_FLAGS by hand
in the CMakeCache.txt to -D__ASSERTMACROS__ . But some day I want to let
kicad build on OS X out-of-source without changing anything. I added the
rules in CMakeLists.txt but it doesn't place them in the CMakeCache.txt:

set(CMAKE_CXX_FLAGS "-D__ASSERTMACROS__")
set(CMAKE_BUILD_TYPE "Debug")

I tried with CMake 2.6.4 and 2.8.2 and searched some mailing lists and
tried different configuration and still failed.

http://comments.gmane.org/gmane.comp.programming.tools.cmake.user/30647

This guys has the same problems.

Maybe somebody can help.

Regards,
Jerry

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Group selection not working with fluxbox, windowmaker (patch included)

[Jerry Jacobs]

On Fri, Aug 13, 2010 at 3:52 PM, Heiko Rosemann  wrote:
> Hello everyone,
>
> I have come across the same problem as Jacques mentioned in
> http://tech.dir.groups.yahoo.com/group/kicad-users/message/7780 - group
> selection does not work, dragging the mouse with left button pressed
> shows no reaction. This was on gentoo linux, fluxbox 1.0.0,
> wxGTK-2.8.10.1-r5 and I also tried it with windowmaker. Strangely,
> dragging the middle mouse button for zooming works...

This very neat feature was indeed missing until now you submitted the
patch/idea.

> After reading his "solution" in
> http://tech.dir.groups.yahoo.com/group/kicad-users/message/7781 I also
> tried xfce and with xfce this works.

For me with awesome tiling window manager it works very good, only as Dick said
the patch needs to be cleaned up.

> But that's no solution for me, I don't want to switch window managers
> just for pcb layout.

Yes, it should also work cross-platform and doesn't need to depend on
a window manager.

I hope someone can put this feature upstream and finds some time to
cleanup the patch.

-- 
Kind Regards,
Met vriendelijke groet,
Jerry Jacobs
- http://www.xor-gate.org

--
"If we knew what it was we were doing, it would not be called
research, would it?",
Not everything that counts can be counted, and not everything that can
be counted counts. - Albert Einstein

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Compiling fails on XML class on Apple OS X with wxWidgets 2.9-svn

[Jerry Jacobs]

Dear all,

I tried compiling the latest revision of wxWidget and KiCad on my 
Macbook with Apple OS X and it failed on the XML library that Dick is 
using now. I recompiled again and the option to enable the XML library 
is the --enable-expat but still it fails. The weird thing is that there 
are some function symbols in the static monolithic library in the 
wxXmlDocument class. So that means it is enabled. Below there is my 
wxWidgets configuration of configure and the error I get during linking. 
Maybe some people have suggestions or ideas. The point is I want to test 
the latest stuff and need to compile it myself then.


Kind regards,
Jerry Jacobs
- http://www.xor-gate.org

./configure --enable-unicode=yes --enable-shared=no --enable-monolithic 
--with-opengl   --enable-universal_binary --enable-aui --enable-debug 
--with-osx_cocoa   --with-macosx-sdk=/Developer/SDKs/MacOSX10.5.sdk/ 
--prefix=/opt/wxwidgets/rev-65251 --enable-expat


Linking CXX executable eeschema.app/Contents/MacOS/eeschema
Undefined symbols:
  "_XML_SetCharacterDataHandler", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_SetCommentHandler", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_SetCdataSectionHandler", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_SetUserData", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_ParserFree", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_ParserCreate", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_SetElementHandler", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_SetUnknownEncodingHandler", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_GetErrorCode", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_SetDefaultHandler", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_Parse", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  "_XML_GetCurrentLineNumber", referenced from:
  _StartCdataHnd in libwx_osx_cocoau-2.9.a(monolib_xml.o)
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

  _CommentHnd in libwx_osx_cocoau-2.9.a(monolib_xml.o)
  _TextHnd in libwx_osx_cocoau-2.9.a(monolib_xml.o)
  _StartElementHnd in libwx_osx_cocoau-2.9.a(monolib_xml.o)
  "_XML_ErrorString", referenced from:
  wxXmlDocument::Load(wxInputStream&, wxString const&, int)in 
libwx_osx_cocoau-2.9.a(monolib_xml.o)

ld: symbol(s) not found
collect2: ld returned 1 exit status
make[2]: *** [eeschema/eeschema.app/Contents/MacOS/eeschema] Error 1
make[1]: *** [eeschema/CMakeFiles/eeschema.dir/all] Error 2
make: *** [all] Error 2

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] CPack integration for crossplatform creation of binary and source archives -- patch

[Jerry Jacobs]

On Sat, Jul 31, 2010 at 4:19 PM, Dick Hollenbeck  wrote:
> Jerry,
>
> Some questions below:
>
>> Dear all,
>>
>> As I was trying to find a neat way to create mac packages on the fly I
>> bumped to CPack. This application is shipped with CMake and can be used
>> inside the existing CMakeLists.txt configuration. For mac I enabled for
>> now only DragNDrop packages which are like zip archives instead of
>> full-fledged PackageMaker installers. The most neat thing is it creates
>> the archives by itself without using any external script or utility.
>> Then the packaging/mac-osx/dmg-generator directory can be removed from
>> the source-tree if this patch is applied.
>>
>> If you look deeper at CPack or CMake CPack module it also integrates
>> generation of NSIS installer for windows and self-extracting shell
>> script for *NIX. This takes us a whole bunch of work from our hands if
>> other people want to do snapshots/nightly builds or actual releasing the
>> software.
>>
>> A console output on my mac when creating source archives (make sure you
>> do a out of source build or else all the CMake cache stuff will also be
>> in the source archive!)
>>
>> white:darwin jerry$ sudo make package_source
>> Run CPack packaging tool for source...
>> CPack: Create package using TGZ
>> CPack: Install projects
>> CPack: - Install directory: /Users/jerry/Work/kicad/repository
>> CPack: Compress package
>> CPack: Finalize package
>> CPack: Package
>> /Users/jerry/Work/kicad/build/darwin/kicad-2010.07.23-Source.tar.gz
>> generated.
>>
>> When creating binary package(s) which can be selected with the
>> CPACK_GENERATOR variable they can be build with the *make package* command.
>>
>> For more information see cmake --help-module CPack
>>
>> I attached the main CMakeLists.txt patch. Only maybe other people have
>> a suggestion to extract the date from BZR or system when building
>> instead of changing the 3 variables BUILD_ YEAR, MONTH, DAY.
>>
>
> I think we can assume:
>
> 1) Those who would use cmake to build Kicad also have BZR installed.
>
> 2) Those who would use BZR also have python installed.
>
> Therefore we can assume python at a version necessary to run BZR is
> installed within the CMakeLists.txt script, but may not be in the PATH.
>
> Could someone (you?) write a simple python "eval" type statement to get
> these strings?  Then we can use a CMake macro to chain load python for
> such values.

I have zero experience with Python programming, and I have time to learn
it. Maybe somebody else with experience can have a look at it. And why are those
things not handled with CMake itself in form of Variables?

> Here was somebody doing something similar with perl:
>
> http://osdir.com/ml/programming.tools.cmake.user/2006-06/msg00323.html
>
> I would see no harm in enabling other CPack "targets" for CMake, as long
> as they did not unconditionally fire when running CMake.  The Doxygen
> target is one such optional cmake target.

Those package and package_source targets don't break the normal behavior.
So adding those for every major platform like *Win, *NIX, Mac should not be a
big deal.

It was just that it is much easier for me to build a DMG/Zip on OSX with CPack
than some hacked scripts and utilities. And this would also count for windows
and linux. Then we have more possibilities and everything is configured from
one file, and all the rest is handled by CPack.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] CPack integration for crossplatform creation of binary and source archives -- patch

[Jerry Jacobs]

Dear all,

As I was trying to find a neat way to create mac packages on the fly I 
bumped to CPack. This application is shipped with CMake and can be used 
inside the existing CMakeLists.txt configuration. For mac I enabled for 
now only DragNDrop packages which are like zip archives instead of 
full-fledged PackageMaker installers. The most neat thing is it creates 
the archives by itself without using any external script or utility. 
Then the packaging/mac-osx/dmg-generator directory can be removed from 
the source-tree if this patch is applied.


If you look deeper at CPack or CMake CPack module it also integrates 
generation of NSIS installer for windows and self-extracting shell 
script for *NIX. This takes us a whole bunch of work from our hands if 
other people want to do snapshots/nightly builds or actual releasing the 
software.


A console output on my mac when creating source archives (make sure you 
do a out of source build or else all the CMake cache stuff will also be 
in the source archive!)


white:darwin jerry$ sudo make package_source
Run CPack packaging tool for source...
CPack: Create package using TGZ
CPack: Install projects
CPack: - Install directory: /Users/jerry/Work/kicad/repository
CPack: Compress package
CPack: Finalize package
CPack: Package 
/Users/jerry/Work/kicad/build/darwin/kicad-2010.07.23-Source.tar.gz 
generated.


When creating binary package(s) which can be selected with the 
CPACK_GENERATOR variable they can be build with the *make package* command.


For more information see cmake --help-module CPack

I attached the main CMakeLists.txt patch. Only maybe other people have
a suggestion to extract the date from BZR or system when building 
instead of changing the 3 variables BUILD_ YEAR, MONTH, DAY.


Kind regards,
Jerry Jacobs

=== modified file 'CMakeLists.txt'
--- CMakeLists.txt  2010-06-13 04:10:16 +
+++ CMakeLists.txt  2010-07-23 16:45:09 +
@@ -1,5 +1,11 @@
 project(kicad)
 
+# Set build date for automated builds and packages
+# This needs to be done in a automatic way some day
+set(BUILD_YEAR  2010)
+set(BUILD_MONTH 07)
+set(BUILD_DAY   23)
+
 # test the minimum Cmake version requirement (could be different under unix or 
Windows
 if(WIN32)
 cmake_minimum_required(VERSION 2.6.4 FATAL_ERROR)
@@ -263,4 +269,32 @@
 PATTERN ".svn" EXCLUDE)
 endif(UNIX)
 
+###
+# Package binarie and source builds with CPack
+#  for help about this variables see cmake --help-module CPack
+###
+
+# Set package resource files
+set(CPACK_RESOURCE_FILE_LICENSE ${CMAKE_SOURCE_DIR}/COPYRIGHT.txt)
+set(CPACK_RESOURCE_FILE_README  ${CMAKE_SOURCE_DIR}/README.txt)
+set(CPACK_RESOURCE_FILE_WELCOME ${CMAKE_SOURCE_DIR}/README.txt)
+
+# Exclude files when building the Source package
+set(CPACK_SOURCE_IGNORE_FILES "/.bzr/;/.swp/")
+
+# Set package version
+set(CPACK_PACKAGE_VERSION_MAJOR ${BUILD_YEAR})
+set(CPACK_PACKAGE_VERSION_MINOR ${BUILD_MONTH})
+set(CPACK_PACKAGE_VERSION_PATCH ${BUILD_DAY})
+
+# Set APPLE configuration for CPack usage
+if(APPLE)
+  set(CPACK_DMG_FORMAT UDBZ)
+  set(CPACK_GENERATOR DragNDrop)
+endif(APPLE)
+
+# Load the CPack module for CMake
+include(CPack)
+
+# Load the CTest module for CMake
 include(CTest)


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] pcbnew module editor toolbar items now in menubar -- patch

[Jerry Jacobs]

On 21-07-10 15:21, Wayne Stambaugh wrote:

On 7/21/2010 3:52 AM, Jerry Jacobs wrote:

Because almost all toolbar items are not in the menubar of the module
editor I wrote a small patch.
Maybe someone can take care of the few TODO's inside the patch which I
was not able to get.


Jerry,

Most of your TODO's suggest creating new IDs for the module editor instead of
reusing the IDs from PCBNew.  Is there any technical reason to do this?  As
long as the ID is descriptive enough than I see no reason to create another ID
specifically for the module editor.  We already reuse wxID_CUT, wxID_COPY,
wxID_PASTE, etc.  I did some ID rationalization a while back that significantly
reduced the number of redundant IDs and unnecessary recompiling.  I would
rather avoid adding new IDs unless there is a good reason to do so.


Yeah I didn't know why there are mixed IDs but now I understand, and 
this a good choice. So the TODO's can be forgotten.




The File ->  Close  needs a ID handler and need's to be fixed.
And maybe some entries should not be selectable in some cases like
undo,redo and the placement of components if there is no module
loaded or new module created.

Maybe all the *modedit* files can better be moved to a subdirectory if
the code will be growing.
And also moving the dialog_*  files. Because we get
already a nice amount of files and directories are handy to sort things up.


This is good idea for the eeschema subdirectory as well as it is getting rather
unwieldy.



See the attached patch, it applies to rev 2418 without problems.


Your patch has some code formatting issues.  There are some indenting alignment
problems.

+item = new wxMenuItem( openSubmenu,
+ID_MODEDIT_IMPORT_PART,
+_( "from File" ),
+_( "Import a footprint module from a existing file" ) );

should be

+item = new wxMenuItem( openSubmenu,
+   ID_MODEDIT_IMPORT_PART,
+   _( "from File" ),
+   _( "Import a footprint module from a existing
file" ) );

There is also some trailing white space as well.  If your editor supports
showing white space, you may want to turn it on.  Uncrustify will also remove
any trailing white space.


I use vim and have not all settings yet to manage the coding style for 
the kicad project as my coding style is a bit different. But I will have 
a look at uncrustify then, it installs on my Apple Mac so that is nice.



Thanks,
Wayne


Hope somebody will find some time to clean the patch and review it for 
pushing it upstream. I have write rights to the repository but don't 
commit major (UI) changes.


Kind regards,
Jerry Jacobs


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] pcbnew module editor toolbar items now in menubar -- patch

[Jerry Jacobs]

On 21-07-10 14:38, Dick Hollenbeck wrote:

On 07/21/2010 02:52 AM, Jerry Jacobs wrote:

>> 

See the attached patch, it applies to rev 2418 without problems.



For future patch attachments, can you keep your email client from base64 
encoding
these attachments?  Thanks.  This way we can see the patch without saving it to 
disk
first.

No need to resend this one, just tweak your settings please, if you can.


The email content includes: ===



Kind Regards,
Met vriendelijke groet,
Jerry Jacobs
- http://www.xor-gate.org

--00151750e3b8a1e816048be1142d
Content-Type: application/octet-stream;
name="pcbnew_module_editor_extended_menubar.patch"
Content-Disposition: attachment;
filename="pcbnew_module_editor_extended_menubar.patch"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_gbvvjf330

PT09IG1vZGlmaWVkIGZpbGUgJ3BjYm5ldy9tZW51YmFyX21vZGVkaXQuY3BwJwotLS0gcGNibmV3
L21lbnViYXJfbW9kZWRpdC5jcHAJMjAxMC0wNC0yMCAxMToyMzo1OSArMDAwMAorKysgcGNibmV3
:
:
--00151750e3b8a1e816048be1142d
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


This seems a problem with the webclient from gmail. I hope thunderbird 
does it well or maybe you guys have a hint to make it work the way you 
want to receive it in the mailing list.


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Close "Edit Item Dialog" by ESC in Library Editor -- patch

[Jerry Jacobs]

On Thu, Jul 22, 2010 at 9:34 AM, Yury Khalyavin  wrote:
> Good day.
>
> This patch allow to close Edit Item dialog in wxGTK by pressing ESC
> button.

This is a very usefull feature, as most application I work with support it.

>
> Regards,
> --
>    Yury Khalyavin

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] feedback on launchpad

[Jerry Jacobs]

On Wed, Jul 21, 2010 at 11:31 PM, Dick Hollenbeck  wrote:
> Are people happy with launchpad?
>
> 10 = extremely happy
> :
> :
> 1 = extremely dissatisfied

I think you mean in the context of the KiCad project hosted and
maintained on launchpad system?

For me i'm more happy and see more progress and better management than
on the services sourceforge
can give us. Only i'm not to happy with bzr for revision control and
as a personal matter of taste I prefer Git.

I give it a 8 = very happy.

Keep it up guys,
We are moving forward.

(sorry Dick I need to reply to all instead of only to the one who put
it on the mailinglist :-) )

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] pcbnew module editor toolbar items now in menubar -- patch

[Jerry Jacobs]

Because almost all toolbar items are not in the menubar of the module
editor I wrote a small patch.
Maybe someone can take care of the few TODO's inside the patch which I
was not able to get.

The File -> Close  needs a ID handler and need's to be fixed.
And maybe some entries should not be selectable in some cases like
undo,redo and the placement of components if there is no module
loaded or new module created.

Maybe all the *modedit* files can better be moved to a subdirectory if
the code will be growing.
And also moving the dialog_*  files. Because we get
already a nice amount of files and directories are handy to sort things up.

See the attached patch, it applies to rev 2418 without problems.

-- 
Kind Regards,
Met vriendelijke groet,
Jerry Jacobs
- http://www.xor-gate.org


pcbnew_module_editor_extended_menubar.patch
Description: Binary data
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Daily builds?

[Jerry Jacobs]

On Wed, Jun 30, 2010 at 11:46 AM, Stephen Eaton  wrote:
> G’day Guys,
>
> Are there daily builds available anywhere?  Especially for those who don’t
> have the development system setup on windows?

Yes there are but I forgot to add them also. They are crosscompiled
from a linux machine.
Dont forget to download also the DLL files.

http://kicad.sourceforge.net/wiki/index.php/Download -> http://kicad.1301.cz

Good Luck


> Regards,
>
> Stephen…

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Component library object change proposal.

[Jerry Jacobs]

On Fri, Jun 25, 2010 at 3:56 AM, Wayne Stambaugh  wrote:
>
> On 6/24/2010 6:53 PM, Brian Sidebotham wrote:
>> On 24 June 2010 21:36, Wayne Stambaugh  wrote:
>>> On 6/24/2010 3:44 PM, Dick Hollenbeck wrote:
>>>> On 06/24/2010 02:19 PM, Wayne Stambaugh wrote:
>>>>> In preparation for the forth coming changes to the component library
>>>>> file format, I would like to make some changes in the design of the
>>>>> component library object format and the component library editor behavior.
>>>>>
>>>>> The current component library design creates aliases as a stand alone
>>>>> objects that reference the actual component object.  The component
>>>>> object also keeps a copy of the alias information (strings) in a
>>>>> wxStringArray.
>>>>
>>>>
>>>>>  It seems to me that an alias has no meaning without the
>>>>> associated component and keeping a copy of the alias data in the
>>>>> component object is redundant.  I propose that the component object
>>>>> maintain the list of it's alias objects and only components are added to
>>>>> the library object.
>>>>
>>>> The above 2 sentences seem to contradict each other.  Can we assume that
>>>> last one is what you intended?
>>>
>>> Oops!  You are correct it is the last one.
>>
>> If I understand correctly, what you want to do is move all aliases of
>> a component into the component object? I think this would make a good
>> improvement for some future uses of aliases.
>>
>> At the moment, aliases are not very powerful because of some limitations.
>>
>> I don't know whether you caught any of the heavy symbol library
>> discussion a few weeks ago, but a heavy symbol library can be
>> implemented much easier is aliases are made a bit more powerful.
>>
>> At the moment for example, I could create an alias which has a
>> different footprint, but not an alias that has a different value. It
>> would be another step towards good support for a heavy symbol library
>> to be able to change the value of aliases. As well as this, aliases
>> really need to support the template field names. At the moment you
>> cannot have these fields in an alias. This would allow aliases to be
>> used as a heavy symbol library, where only one graphic would need to
>> be created.
>>
>> Further on from that, aliases would be easily selectable via a pop-up
>> list box or similar. One of the biggest time wasting parts of a heavy
>> symbol library (if taken to it's extreme) is that simply changing a
>> value of a passive component has to be done by replacing the
>> component. If a hotkey can be used on a component when editing a
>> schematic in eeschema to bring up a listbox of all of the aliases of
>> the component, one can quickly be selected to change the value of the
>> part.
>>
>> This sort of thing works well when you need to change things like SMT
>> electrolytics, as you would simply select by voltage and capacitance
>> and the correct case size footprint would come from the alias. There's
>> no risk of forgetting to change the footprint because you've altered
>> the value.
>>
>> I just wanted to give a possible good future use for aliases in case
>> any of this is useful whilst you are working in this area.
>
> Brian,
>
> This is all really good information.  Hang on to it until I submit the
> blueprint for the proposal for the new library file format.  The new
> file format proposal I'm working on already covers a lot of what you
> have listed above.  I want to try keep all the discussion about the new
> file format in one place for my own sanity and to make sure nothing gets
> lost.

Maybe another thing is to split it complete from the kicad core. So
create a real library written in ISO C++ so people who want to write
plugins and language bindings will be more happy than the hacked code
to read and write files in the current codebase. Because if you find
some software which can do something with the kicad file formats they
all write their own parsers/handlers and that is a bit of a pain to
keep the other people updated for the new upcomming file format(s).
Also if you dont use any existing library be used in your library like
wxwidgets it is portable to everywhere and also for people who want
something different than wxwidgets like Qt/Gtkmm etcetera. Than you
will see much more tools and utilities than now.

Maybe you should have a look how dxflib and podofo pdf library. Then
are very powerfull libraries and very consistent with names and
classes. In my opionion this is a pre for a new file format
reader/writer.

Kind regards,
Jerry Jacobs

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Icon rework and OS X updates

[Jerry Jacobs]

Artwork finished and pushed to testing revision 2367
http://kicad.xor-gate.org/screenshots

Have fun,
Jerry

On Tue, May 11, 2010 at 11:38 PM, Alain Portal  wrote:
> Le mardi 11 mai 2010 22:49:10, vous avez écrit :
>> Try to open the /artwork/*.svg the *.icns files are for OS X.
>>
>> Its over here:
>> http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/files/h
>> ead:/artwork/
>
> I saw its!
> Unforntunatly, there is only the kicad picture, not eeschema, not pcbnew ;-)
>
>> It would not nice if I don't include a vector icon, this is the reason
>> why I reworked it.
>
> I agree with you, this is why I ask you if you agree to rpovide the others.
>
> Regards
> Alain
> --
> Les pages de manuel Linux en français
> http://manpagesfr.free.fr

On Tue, May 11, 2010 at 10:38 PM, Alain Portal  wrote:
> Hi,
>
> Le dimanche 9 mai 2010 18:22:32, Jerry Jacobs a écrit :
>> Dear all,
>>
>> As you probably aware I succeeded my first merge and commit with bzr.
>> I must say its easy to use and powerful and has more advantages over
>> subversion. I committed some icons I reworked with Inkscape in vector
>> format, and are now default on OS X platform. Still I have to do
>> PCBNew and GerbView icons. If you don't like it I will only use it for
>> the OS X platform, this because we need maximal size of 512x512 pixel
>> icons to appear nice. Of course you suggestions are welcome. I also
>> committed that kicad doesn't display icons in the menu. This is
>> default behavior of Mac applications. If somebody has a better
>> suggestion to turn the menubar icons of in wxwidgets I don't need the
>> define checks in our code.
>>
>> See for yourself:
>> http://kicad.xor-gate.org/screenshots
>
> This is a nice job you did, and I would be happy to get it.
> You sayed you worked with Inkscape?
> Unfortunately, I tried to open some *.icns files with my Linux Inkspace 
> version
> (0.47) and it failed :-(
>
> So, could you please send me a png version of eeschema, pcbnew and kicad
> (biggest size and resolution of your work) artwork?
> I would like to improve (or add) icons and mime types for Linux.
>
> Regards,
> Alain
>
> --
> Les pages de manuel Linux en français
> http://manpagesfr.free.fr
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
>



-- 
Kind Regards,
Met vriendelijke groet,
Jerry Jacobs
- http://www.xor-gate.org

--
"One of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of
their C programs" - Robert Firth
Not everything that counts can be counted, and not everything that can
be counted counts. - Albert Einstein

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Icon rework and OS X updates

[Jerry Jacobs]

Dear all,

As you probably aware I succeeded my first merge and commit with bzr.
I must say its easy to use and powerful and has more advantages over
subversion. I committed some icons I reworked with Inkscape in vector
format, and are now default on OS X platform. Still I have to do
PCBNew and GerbView icons. If you don't like it I will only use it for
the OS X platform, this because we need maximal size of 512x512 pixel
icons to appear nice. Of course you suggestions are welcome. I also
committed that kicad doesn't display icons in the menu. This is
default behavior of Mac applications. If somebody has a better
suggestion to turn the menubar icons of in wxwidgets I don't need the
define checks in our code.

See for yourself:
http://kicad.xor-gate.org/screenshots

Kind regards,
Jerry Jacobs

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Kicad libraries for pcbnew

[Jerry Jacobs]

Hello Ųyvind,

Is it possible to branch the kicad-newlib and add your libraries to it?
This is better for the team if we want to merge the libraries with the
official releases.

Kind regards,
Jerry

On Tue, Apr 20, 2010 at 11:32 AM, Ųyvind Aabling wrote:

> I have added some more components and some improvements to my
> pcbnew libraries at 
> http://www.uni-c.dtu.dk/~univind/kicad/<http://www.uni-c.dtu.dk/%7Eunivind/kicad/>
>
> I've added:
>
> * Aluminum Electrolytic Capacitors (SMD), both polarized and unpolarized.
> In the lack of a better name, I've named them
> AEC-[PU], but I'm open to suggestions :-)
>
> * I've renamed all the Capacitors (except the AEC), so
> they're all called C-, making it much easier
> to identify Capacitors among all the other components,
>
> * Socketed DIPs: Full socket and double-row Tulip,
>
> * Ceramic Disc and Tantalum Drop Capacitors,
>
> * Fuses: 5x20 incl. clips and 5x20/6x32 combo clips,
>
> * Improved silkscreen on the horiz mount TO-PPs - now, it includes
> the vert mount silkscreen, making the mounting orientation clearer.
>
> * Horiz mounted versions of the TO-92 and TO-237,
>
> * The MT-200 power transistor house (e.g. 2SC2922 and 2SA1216),
>
> * More realistic house on the heatsinked BQFP80-M05-HS,
>
> * Improved placement algorithm for the sample boards,
> and automatic creation of multiple sample boards if the
> components of a library doesn't fit on a single board.
> The grid placement within a row still needs a little more work
> (to give more uniform spacing), but it's almost there.
>
> Now at 847 parts and 5880 lines of code (incl.
> dimension tables), so still about 7 lines/part.
>
> Øyvind.
> ___
> Mailing list: 
> https://launchpad.net/~kicad-developers<https://launchpad.net/%7Ekicad-developers>
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : 
> https://launchpad.net/~kicad-developers<https://launchpad.net/%7Ekicad-developers>
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Kind Regards,
Met vriendelijke groet,
Jerry Jacobs
- http://www.xor-gate.org

--
"One of the main causes of the fall of the Roman Empire was that, lacking
zero, they had no way to indicate successful termination of their C
programs" - Robert Firth
Not everything that counts can be counted, and not everything that can be
counted counts. - Albert Einstein
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp