Re: Pending Pull Requests, Pressing Issues?

I don't mind looking into the automated builds. Although there's a few things in there I'm unsure of - like what's bigv? As far as I can see, it tries to upload some files to there at the end of the builds, but this hasn't happened/worked in a long time.

If I were to do this, I'd probably set it to deploy to bintray, which I already use for hosting the mingw precompiled libraries.

The other thing is that the scripts to make the OS X package are... what I would call unmaintainable. It's a miracle to me that the OS X packages can even be made at all in its current state.

Jeremy
________________________________
From: Frank Trampe <[email protected]>
Sent: Wednesday, 7 September 2016 12:58 AM
To: FontForge developers' discussions
Subject: Re: [fontforge-devel] Pending Pull Requests, Pressing Issues?



On Tue, Sep 6, 2016 at 11:42 AM, Dave Crossland <[email protected]<mailto:[email protected]>> wrote:

On 6 September 2016 at 14:53, Frank Trampe <[email protected]<mailto:[email protected]>> wrote:
That seems unlikely at this point. The pull request isn't finished, and I think Pathum told me that the developer working on it is no longer available.

I can raise funds to enable Ben Martin to complete it, if it needs more work. But it isn't clear to me what additional work needs to be done.

I'm not sure either. My information is second-hand, and the pull request is very large, so it is difficult for me to ascertain by skimming it. The one thing that I notice is that a large chunk of the documentation has been deleted, which is bad.

However, I am really feeling frustrated that reordering menu items could be very complex :(

I think that it would be nice to have a dynamically configured menu system. Perhaps with an xml file with labels, shortcuts, icon image names, and base menu item names. But there are a lot of other more pressing issues.

There are also issues that we need to sort out regarding the actual changes, some of which this FontForge user finds puzzling/irritating. Even if we leave the old menu system as an option for those who want it (which we will almost certainly do since I want it), I think we need to get a bit more community feedback before pushing such a visible change on people.

I'd be happy to see FF releases with 2 versions, a 'stable' version with the classic menus and a 'testing' or 'unstable' version with the new menus, for say 12 months.

I'm not proposing a fork. I'm proposing having two sets of menu structures in the codebase and allowing for switching between them via a flag in the preference file. The important thing to me is that those of us who do not wish to switch can continue using the menu system with which we are happy and familiar.

Last time I looked, the new menus did a lot of things that broke the usual rules of menu structure (like moving the revert/reload entry out of the file menu), which I dislike. And anything different (whether better or worse for new users) creates a hassle for those who know how things work. I would strongly prefer to use the old menu system, and I imagine that others would like to do so also.

However, for me this reveals a more serious problem, which is that we don't have reliable automatic installer package creation for Windows and Mac OS X. jtanx has just posted that he has a windows installer going with AppVeyor, so I think for me the #1 changeset would be to the travis file, to get travis building Mac binaries for each PR.

I can raise funds for that to happen, if needed.

This would seem to be a useful thing.

I'm travelling for the next week. Could I look at this late next week?

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html

------------------------------------------------------------------------------

_______________________________________________
fontforge-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fontforge-devel
http://fontforge.10959.n7.nabble.com/Developer-f3.html