<div dir="ltr">Dan, I already have another tree here: <div><br></div><div><a href="https://bitbucket.org/adt6247/chirp-wxwidgets">https://bitbucket.org/adt6247/chirp-wxwidgets</a><br></div><div><br></div><div>No commits to it yet. I'm trying to get my build environment working. The upgrade to Sierra seemed to break pip for me, so I need to figure out what's going on there before I can do Python projects. </div><div><br></div><div>My strategy was going to be what you suggested. I'll do a separate implementation of the `chirp.ui` package, and try to keep it as code compatible with the GTK. I'm probably going to start by renaming the ui package to `ui-gtk`, and have a parallel `ui-wx`. Once we decide to merge, we can rename it back to `ui`. </div><div><br></div><div>I also noticed that setup.py doesn't use setuptools. I was thinking about refactoring that as well. But that can come after the UI. It would be nice to have this have a more standard layout, but there's no reason to do this all at once. I'm of the opinion that refactoring a project should be done in such a way that the commit history can really illustrate the migration. But that's probably me being a bit persnickity. </div><div><br></div><div>I am able to follow the code fairly easily. Not a whole lot of comments, but it's well organized, and there's very little fluff. </div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>--</div>Aaron Traas | <a href="https://traas.org/" target="_blank">https://traas.org/</a> | <a href="http://twitter.com/AaronTraas" target="_blank">@aarontraas</a><div><br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Dec 29, 2016 at 10:56 AM, Dan Smith via chirp_devel <span dir="ltr"><<a href="mailto:chirp_devel@intrepid.danplanet.com" target="_blank">chirp_devel@intrepid.danplanet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> The Chirp UI has been mature for many years and very little work goes<br>
> into it now. That means you probably would not disrupt anybody with a<br>
> UI overhaul. Moreover, I don't believe any of the active Chirp<br>
> developers have much experience or interest in UI development, so if<br>
> you want to "own" this that would be a great complement to the team.<br>
<br>
</span>Yeah, I hate having to work on the UI. I like the idea of using wx for<br>
it, if it gets us a more native look on all the platforms. Double good<br>
if we can make our OSX payload more integrated.<br>
<br>
There is a lot of workflow in the UI that will either have to be<br>
replicated or generalized, which makes me think this is likely a pretty<br>
large project. I think the way I'd want to see it go is:<br>
<br>
1. Put up another tree somewhere that you can push to for a while<br>
2. Add the new UI in parallel to the old one and add some simple switch<br>
early in chirpw to select between them<br>
3. Once a reasonable amount of functionality is there, we can see about<br>
merging it into the main tree, and make it optional somehow for<br>
regular users to try it.<br>
4. Continue iterating until we can make the new one default, and then<br>
eventually remove the old one.<br>
<br>
For #3, I will have to do some stuff to the windows build system I<br>
imagine. We also need to figure out what the OSX path looks like if<br>
we're going to bootstrap downloading and installing things during app run.<br>
<br>
The setup.py process is super non-standard on all the platforms because<br>
of all the gorp I have to pull in to make the build work on windows. It<br>
would be great if this ends up with that being far simpler and more<br>
conventional.<br>
<span class="HOEnZb"><font color="#888888"><br>
--Dan<br>
</font></span><div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
chirp_devel mailing list<br>
<a href="mailto:chirp_devel@intrepid.danplanet.com">chirp_devel@intrepid.<wbr>danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_devel" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/<wbr>mailman/listinfo/chirp_devel</a><br>
Developer docs: <a href="http://chirp.danplanet.com/projects/chirp/wiki/Developers" rel="noreferrer" target="_blank">http://chirp.danplanet.com/<wbr>projects/chirp/wiki/Developers</a><br>
</div></div></blockquote></div><br></div>