Need Update

[chawafjamil]

Hello,

I’m running on the beta version of Mac OS Sierra. And Fraise is not working anymore. Could you please update it. Thank you ; )

Kindest regards,

Jamil Chawaf.

[Toastrackenigma]

I also have this problem - "You can’t use this version of the application “Fraise.app” with this version of macOS." :(

Please fix...

[chawafjamil]

Hi,

You can use TextMate meanwhile. It's a good text editor similar to Fraise.
;)

Regards,

Jamil.

On 14 Aug 2016 00:37, "Orlando Parisblue" notifications@github.com wrote:

I also have this problem - "You can’t use this version of the application
“Fraise.app” with this version of macOS." :(

Please fix...

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#49 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALz4VwEbIQrk9CsNysm811sqfOvT1Uw5ks5qflUxgaJpZM4JJt7Q
.

[rkarolak]

With El Capitan I'm not able to use File > Open. Selecting a file to edit closes the open dialog box and nothing happens.

[randallbruder]

Just a heads up, the Sierra compatability issue is shown when you run /Fraise.app/Contents/MacOS/Fraise in Terminal:

objc[5411]: Objective-C garbage collection is no longer supported.

[abentele]

Fixed it in my fork: https://github.com/abentele/Fraise
Also created a pull request.
Main features (load/save files etc.) are working with macOS Sierra, but not every feature is already well tested. Feedback is welcome!

[rkarolak]

Thanks for working on that abentele. I'm trying your release and it seems to be working well after compiling in Xcode. However, I get the prompt asking about enabling auto-updates every time I open Fraise. No matter which I select it still will ask me next time I start up Fraise. Otherwise it looks like the other settings stick.

[abentele]

Thanks for testing my fix.

Yes, that's a remaining issue, the auto-update feature doesn't work. Not only the question when starting up Fraise, but also the auto-update itself throws an error.

My main goal yesterday was to make Fraise running with macOS Sierra (for my own needs). So I didn't have the time to investigate in the auto-updates problem. It maybe has to do with either the update of the sparkle library (fixed a crash on startup of Fraise) or the broken configuration of the auto-update feature: maybe the configured update site doesn't exist any more (jfmoy, could you please comment on this).

Btw: the auto-update feature doesn't make much sense as long as there is no developer who maintains the software continuously.

[rkarolak]

True. It probably best to just remove the prompt and then disable the update features all together for now. The auto-update and the menu item for the original Fraise (jfmoy's) hasn't worked for a long time.

[gpongelli]

HI @abentele, thank you for updating Fraise to Sierra.
On my fork I've completely removed Sparkle and fixed some warnings.

[abentele]

@rkarolak, @gpongelli: thanks for your suggestions and help on this topic!

So for now I've completely removed the auto-update feature, including the dependency to sparkle. @gpongelli: thanks for your commit, I forgot to remove the items you removed, so I will merge it to my fork for code cleanup.
Maybe someone has the time to revert this commit and to rework the auto-update feature in future.

Today I'm happy to announce a new release working with macOS Sierra: Use the binary download from https://github.com/abentele/Fraise/releases/tag/3.7.4, or build it from source using XCode. I think of it as a beta release, because I didn't have the time to test it. Check it out and give us feedback.

[abentele]

@gpongelli: I didn't look at all your commits when I wrote my last comment.
Unfortunately we worked on the same issue at the same time, with almost the same result regarding the auto-update feature (your commit e52dac2 conflicts with my commit bbc3b59 which does the same).

To solve this conflict, I cherry-picked all your commits excluding e52dac2. So your valuable work is saved, and I suggest you to delete your fork and maybe start with a new clean fork of my branch, to solve the conflict on your side.

Btw.: I think that we should continue work on the many remaining warnings and deprecated code. Goal should be that there are zero warnings.

[amrx06]

great job, thank you very much!
I tried cotEditor but it's a little bit different and I prefer Fraise (indentation, icons, default parameters…).

The left panel (Document List) doesn't work for quite a long time (OS X 10.9 maybe?). If you've any clue that's good, otherwise I can live without and thank you again for your great job :)

[abentele]

@amrx06: thanks for your comment. The document list panel works; maybe the with of the panel is 0 pixels which in fact means it's invisible. You may drag the left side of your window (where the document list should be) to make it visible. Does that work?
If it really doesn't work, please open a new issue here: https://github.com/abentele/Fraise/issues

[amrx06]

correct, the panel had a size of 0. Wonderful :)

[reppolice]

@abentele apologies for the ping, but I have not been able to remove the SDK 10.6 dependence in this project, and even a reference to a relative directory under fraise-master, that was weird! I only saw it in one place in the project settings, but it looks like it is in many, any chance you could mention how many such references there were, and/or if there was a way to wipe them all in one go?

[abentele]

@reppolice the SDK 10.6 dependencies were not the big problem; you can see my changes in commits from third of October 2016. I also had to replace (and finally remove) the incompatible Spark library. Most work was replacing the garbage collection code with ARC, mainly done with commit 588641b (thanks to tearsofphoenix).
I never saw references to relative directories you mentioned. Could you please be more precise, i.e. how are they named?

Please use the issues list within my fork https://github.com/abentele/Fraise/issues or direct mails to me (abentele.github@icloud.com) for such questions. As you may see in the project history, @jfmoy didn't maintain the project over the last years.