tag:blogger.com,1999:blog-37404288.post4199565322584497096..comments2023-11-02T14:40:18.756+01:00Comments on JP Moresmau's Programming Blog: EclipseFP 2.5.0 releasedJP Moresmauhttp://www.blogger.com/profile/09964251063221757176noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-37404288.post-28545181957427237202013-03-01T18:45:00.652+01:002013-03-01T18:45:00.652+01:00Thanks, after I set that preference to 0 the text ...Thanks, after I set that preference to 0 the text input keeps up. The syntax highlighting lags behind a bit, but that's an acceptable price to pay.Tom Crocketthttps://www.blogger.com/profile/08187984533973895431noreply@blogger.comtag:blogger.com,1999:blog-37404288.post-89823772069959768012013-03-01T16:42:47.539+01:002013-03-01T16:42:47.539+01:00Tom, I've just released 2.5.1. It fixes an iss...Tom, I've just released 2.5.1. It fixes an issue in the syntax highlighting preference page. At the bottom of that page is the setting for the page limit to do syntax highlighting in a different thread.<br />2.5.1 also searches for executables in $HOME/Library/Haskell/bin/<br />For the performance, I can see no slowdown. Sometimes an over-zealous antivirus can slow down invocations of buildwrapper?<br /><br />JP Moresmauhttps://www.blogger.com/profile/09964251063221757176noreply@blogger.comtag:blogger.com,1999:blog-37404288.post-82689840985230456242013-03-01T09:15:52.915+01:002013-03-01T09:15:52.915+01:00What's the preference to do syntax highlightin...What's the preference to do syntax highlighting in a background thread?<br /><br />It's surprising to me that you don't notice the performance problems on an older machine; my machine is a very new 2.6 GHz MacBook Pro. Here's a quick test: just mash a bunch of keys as fast as you can for a few seconds and then stop. When I do that for N seconds and then stop, the editor spends <i>at least</i> N seconds catching up. Compare this to the Java eclipse editor, which it is impossible to get ahead of.<br /><br />Anyway, thanks for looking into it!Tom Crocketthttps://www.blogger.com/profile/08187984533973895431noreply@blogger.comtag:blogger.com,1999:blog-37404288.post-21205982451856220302013-03-01T08:55:27.299+01:002013-03-01T08:55:27.299+01:00Hello Tom, sorry to hear about your issues. This n...Hello Tom, sorry to hear about your issues. This new version of EclipseFP should have faster performance in the editor. There is actually not that much being done in the UI Thread, but Eclipse does the syntax highlighting in that thread by default. There is a preference setting that allows you to specify a size for files over which the syntax highlighting is done in a thread, so you may see a lag in coloring, but at least you can type fast. But it's weird, as I said I have worked on that performance, and I use EclipseFP myself for all my Haskell development of course and don't notice a lag when typing (and my machine is not that powerful).<br />For the Mac executable location, I'll check the code, but there are lots of Mac users and nobody reported that issue before. I think we actually use Haskell to get the location where executables are installed...JP Moresmauhttps://www.blogger.com/profile/09964251063221757176noreply@blogger.comtag:blogger.com,1999:blog-37404288.post-3606924467823675782013-03-01T07:37:02.212+01:002013-03-01T07:37:02.212+01:00Thanks for the update! EclipseFP is showing a lot ...Thanks for the update! EclipseFP is showing a lot of promise.<br /><br />One annoying thing is that there is a perceptible lag when typing in the editor, enough for it to be distracting. It seems like too much computation is being done in the UI thread. This is actually a major reason why I haven't fully migrated my Haskell development to EclipseFP yet. A source editor is first and foremost a <i>text</i> editor, and any pure text editor that performed as poorly as this would be shunned!<br /><br />Another minor annoyance on Mac at least is that EclipseFP doesn't seem to know about the standard place to look for executables, which is $HOME/Library/Haskell/bin/. Because of this, it wants to cabal-install all the helper executables even when they're already installed, and even after it installs them it can't find them; you have to manually point it to each one in the preference page. The "try to find executable in common directories" doesn't look in what should be THE most common directory.<br /><br />Again, aside from those issues it's looking great!<br /><br />TomTom Crocketthttps://www.blogger.com/profile/08187984533973895431noreply@blogger.com