kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

Since there has been no objections against this policy change, I
committed this patch.  Thanks.

On 9/7/2016 8:09 AM, Maciej Sumiński wrote:
> Wayne,
> 
> I attach a patch updating the UI policy. I would rather you commit the
> patch, to be sure you agree with the changes.
> 
> Regards,
> Orson
> 
> On 09/03/2016 02:17 AM, Wayne Stambaugh wrote:
>> We've been dancing around this issue for a while without any real
>> resolution.  I'm fine with using Mark's version of wxFB but a lot folks
>> are going to want to use whatever is packaged for their distro rather
>> than build wxFB from source which presents a serious issue.  I'm not
>> sure there is a good answer for this problem.  If no one else has any
>> objections, I'm willing to make Mark's wxFB fork the official version
>> for KiCad dialog submission for the time being.  In the long run, if
>> wxFB is not actively being developed, I would rather come up with an
>> alternative.
>>
>> FWIW, I think most of you know how I feel about dialog creation tools
>> vs. creating them programmatically.  Kicad's dialogs used to be created
>> this way but I got out voted at the time the decision was made to switch
>> to wxFB.  I'm feeling better about my choice all the time. ;)
>>
>> On 9/2/2016 7:11 PM, Chris Pavlina wrote:
>>> I would vote in favor of using Mark's fork officially for everyone, if
>>> it builds okay on all the platforms. wxfb is kinda nasty, if we're going
>>> to use it it's nice to have our own fork that solves at least a few of
>>> these issues.
>>>
>>> On Sat, Sep 03, 2016 at 08:45:12AM +1000, Cirilo Bernardo wrote:
>>>> I just use MRoszko's fork; it's cleaner than the original and much
>>>> easier to configure and build since the bizarre wxFB build system
>>>> had been eradicated and replaced by CMake.
>>>>
>>>> git clone https://github.com/marekr/wxFormBuilder.git wxfb
>>>> cd wxfb && git checkout wxFB3.5-1
>>>>
>>>> A half year or so ago I tried the later wxFB in development but it
>>>> broke so many things that I just reverted the files and went back to
>>>> wxFB3,5-1.
>>>>
>>>> - Cirilo
>>>>
>>>>
>>>> On Sat, Sep 3, 2016 at 7:28 AM, Chris Pavlina <pavlina.chris@xxxxxxxxx>
>>>> wrote:
>>>>
>>>>> Along these lines: this isn't the first time wxfb version issues have
>>>>> come up. Perhaps we should pick an "official" wxfb version for the
>>>>> project to use, and then actually provide builds of it for developer use
>>>>> (as it can be a bit annoying to track down a specific version)? Then we
>>>>> can upgrade together as new versions come out.
>>>>>
>>>>>
>>>>> On Sat, Sep 03, 2016 at 09:16:41AM +1200, Simon Wells wrote:
>>>>>> dialog_pad_properties_base.fbp h cpp was last modified in commit
>>>>>>
>>>>>> 63decd70e6ab1bf2fe95db3f426f6cdfc79be213
>>>>>> https://git.launchpad.net/kicad/commit/?id=
>>>>> 63decd70e6ab1bf2fe95db3f426f6cdfc79be213
>>>>>>
>>>>>> the problem is this version of wxformbuilder is newer than the one
>>>>>> available on sourceforge and it is very difficult to build on other
>>>>>> platforms ( i tried a while ago and gave up as it had issues)
>>>>>>
>>>>>> the version that was used to save these files has broken it on older
>>>>>> versions of wxformbuilder
>>>>>>
>>>>>> Is there a version of wxformbuilder that we should be using to avoid
>>>>>> it breaking on other versions?
>>>>>>
>>>>>> the last available from sf.net is 3.5rc1 iirc
>>>>>>
>>>>>> thanks
>>>>>>
>>>>>> Simon
>