kicad-developers team mailing list archive

[louijp <louijp@xxxxxxxxx>]

I agree with Adam, this has been on and off for at least a year. But nobody came up with a plan to fix it. Now it seems that we have more OS X developers, so I hope someone will take the ball and run with it.
Jean-PaulAC9GH


Sent from my Verizon Wireless 4G LTE smartphone

-------- Original message --------
From: Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx> 
Date: 2015/06/21  2:38 PM  (GMT-05:00) 
To: Nick Østergaard <oe.nick@xxxxxxxxx> 
Cc: kicad-developers@xxxxxxxxxxxxxxxxxxx, Jean-Paul Louis <louijp@xxxxxxxxx> 
Subject: Re: [Kicad-developers] idea for post-release file manipulations 

That is a legitimate bug.  Not sure if it is on the tracker yet, but it has been discussed on the list.
There are plenty of OS X UI issues that should be evaluated before the stable release.  I suspect moat of then are wxwidgets issues.  *sigh*
Adam Wolf
Adam Wolf
On Jun 21, 2015 1:07 PM, "Nick Østergaard" <oe.nick@xxxxxxxxx> wrote:
Where is the bug listed in the bug tracker Jean-Paul?



2015-06-21 19:46 GMT+02:00 Jean-Paul Louis <louijp@xxxxxxxxx>:

> Are we going to the stable release with all the drop-down items broken on pcbnew OSX?

>

> I cannot use the mouse or the track-pad to select any of the items on the four drop-down menus for Track size, Via size, Grid size and Zoom selection.

>

> I reported this several times, but nobody seems to acknowledge it. Is it an issue with my setting? or it is a real issue?

>

> Thanks for letting me know.

>

> A very frustrated Jean-Paul

> AC9GH

>

>> On Jun 21, 2015, at 1:22 PM, Adam Wolf <adamwolf@xxxxxxxxxxxxxxxxxxxx> wrote:

>>

>> Simon,

>>

>> A group of us have talked about making a git plugin that will be compatible w the github plugin, but will use git on the user's system and won't do network io on its own.

>>

>> We have basically always pushed it off until after the stable release, but as soon as things quiet down i think we should see who is interested and make a roadmap and get buy-in from the lead team.

>>

>> Adam Wolf

>>

>> On Jun 21, 2015 11:46 AM, "Wayne Stambaugh" <stambaughw@xxxxxxxxx> wrote:

>> See include/richio.h

>>

>> Our I/O objects already support wxInputStream and wxOutputStream.

>> Although there is no reason you couldn't add objects that use

>> std::istream and std::ostream or the boost::iostreams.  I believe the

>> wxIoStreams already support support archives so all you would have to do

>> is create the stream and pass it too the proper LINE_READER or

>> OUTPUT_FORMATTER object.  You would automagically have archive stream

>> support for board file and footprint libraries.

>>

>> On 6/21/2015 8:55 AM, Simon Richter wrote:

>> > Hi,

>> >

>> > Am 21.06.2015 um 03:06 schrieb Cirilo Bernardo:

>> >

>> >> a. Abstracting a stream class which can magically support

>> >> file retrieval by http, local files, and perhaps github (I know

>> >> next to nothing about how github works) and local file

>> >> writing.

>> >

>> > std::istream?

>> >

>> >> b. The stream class can automatically inflate *.gz files

>> >> (basically files compressed by zlib and with .gz at the end).

>> >

>> > boost::iostreams::gzip?

>> >

>> >> Supporting *.gz can typically shrink footprint files to 30-40%

>> >> of the uncompressed size and VRML files can often

>> >> compress to <15% of the original size and large STEP

>> >> and IGES files can compress to 10% of the original.

>> >

>> > Is that actually a problem for users, though?

>> >

>> > I'd probably even want to see the opposite -- network operations removed

>> > from the rest of the program. Right now, if I have github footprints in

>> > my list, entering cvpcb or pcbnew always takes a while because the

>> > libraries are updated everytime.

>> >

>> > I'd rather have an explicit mechanism to update the libraries, giving me

>> > local files that are instantly and always available, with no new failure

>> > modes to handle for the application.

>> >

>> >    Simon

>> >

>> >

>> >

>> > _______________________________________________

>> > Mailing list: https://launchpad.net/~kicad-developers

>> > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx

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

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

>> >

>>

>>

>> _______________________________________________

>> Mailing list: https://launchpad.net/~kicad-developers

>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx

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

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

>> _______________________________________________

>> Mailing list: https://launchpad.net/~kicad-developers

>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx

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

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

>

>

> _______________________________________________

> Mailing list: https://launchpad.net/~kicad-developers

> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx

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

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