Currently I am using libglade for building gui. However, I would like to use gtkbuilder.
I couldn't find gtkbuilder interface in lablgtk2 (OCaml interface to gtk+).
Is it not available in lablgtk2?
According to the comments in this bug report, it seems like gtkbuilder support will come along with the switch to Gtk3:
https://forge.ocamlcore.org/tracker/index.php?func=detail&aid=1058&group_id=220&atid=1032
The issue of migration to Gtk3 in lablgtk was discussed in July 2011:
https://lists.forge.ocamlcore.org/pipermail/lablgtk-list/2011-July/001910.html
In the former bug report comment (from April 2012), there is the insinuation that this switch might happen soon.
Sorry if the answer isn't too useful, but it is nice that the developers share these hints about what's coming up in the future.
Related
I found this link Add powershell support for Build Events indicating that as of VS2019 v16.2 you can now use powershell directly in VS build events. Mads closed this with the following comment:
This feature has now been released in the latest product update
released version 16.2. Please install and let us know your feedback.
Please continue to provide feedback and help us be even better.
I'd like to use this but I can't find it in VS and I can't find docs on it (there is a lot of noise on this topic). Mads comment above was dated Jul 18, 2019 so it's been there a while.
Have I missed or misunderstood something about that thread? Does anyone know how this feature might be enabled/used?
I'm specifically interested in this feature not in generic info on running powershell as a build event via cmd.
Update: I've added the following ticket Add (or document) powershell support for Build Events to the MS Developer Community site to request support or documentation of this feature.
MS has dropped support for the code definition window with Roslyn.
I already have R# installed and don't want to install CodeRush as well to get this functionality back.
Has anyone seen a (free) plugin that does this and preferably only this? Peek does not fit with my workflow (as also stated in the mentioned post)
It seems to me that the introduction of Swift has some fantastic potential for Ruby and improving Ruby performance. As a team, we're loving the ability to universally use Ruby at the moment. For example, we have effectively replaced JavaScript with Opal for our Ruby and Rails apps and are using RubyMotion for iOS (and now soon Android) development.
My question: Are there any ways that we can bring Ruby into the status of first class citizen in Xcode so that we'll be able to take advantage of the Xcode 6 Playgrounds, get a ruby repl in Xcode's console, and perhaps take advantage of the other new offerings?
I am HOPING that we are not still screwed a la this old request.
FYI, I have also posed this question to Apple via bugreport.apple.com in hopes to get some additional insight for extending Xcode from the other side of the fence.
I also can't anticipate the internal decisions of Apple BUT there are some facts we can be sure of:
Apple is marketing Swift as THE future way to build iOS apps, there was no mention of adding additional Ruby support (or any other language) for XCode anywhere I've seen in WWDC 2014 announcements or elsewhere in the official Apple release notes, if I'm wrong, please link.
Laurent Sansonetti (as you probably know) was pretty much the MacRuby guy, he was the main developer on the project. Apple wasn't interested in really developing MacRuby further commercially and asked him to work on other Apple projects more (not to speak for him, this may be wrong but he mentioned this at Bubbleconf which I attended in 2012) http://blog.phusion.nl/2012/06/27/laurent-sansonetti-of-rubymotion-fame-to-speak-at-bubbleconf-2012/). He implied this was one of his reasons when he departed from Apple to found his company HipByte.
Apple has made no improvements to MacRuby support or to support Ruby for iOS, or XCode tooling for Ruby since 2012 when Laurent left. Correct me if I'm wrong.
If you're after a REPL or live-coding environment for RubyMotion, RubyMotion has a ticket for it in their bug tracker: http://hipbyte.myjetbrains.com/youtrack/issue/RM-74. Please upvote it, even just hot reloading Teacup stylesheets would be a massive time-saver for us too.
I have seen that yesterday Web API RTM has been released by Microsoft.
However I can't seem to find any log about what has changed from RC to RTM and any tips on what has changed.
We have a service that's ready for production next week, and I am not sure whether to roll with RC or upgrade to RTM this late in the project. What value does it add?
Thanks
Ubal
The official release notes can be found here at www.asp.net.
As #Aliostad kindly mentioned, I wrote an overview post highlighting what's changing and including some code samples and other references.
Henrik also wrote a nice overview post - and that one's also focused on the preview for the out-of-band functionalities available as NuGet packages (OData, tracing, Help page, and a formatting library for Win8).
If you ask whether you should upgrade - obviously yes. There aren't many breaking changes so it should be rather painless, and you get a mature, production-deployable product. It's well worth it imho.
How do I let Microsoft know about a problem I've found in one of their core library routines? Do they have a central repository to report these things?
I am not a member of Microsoft Development Network (MSDN).
Or should I even bother?
There is no official way to report bugs to Microsoft for an end-user. If you are participating in a beta program for an upcoming release, the beta program includes a bug-reporting channel. Otherwise, if the bug causes problems that you want to get resolved, you can call Microsoft support, and they will help you solving the problem (be it by providing a patch, or a work-around); if the problem turns out to be caused by a bug indeed, they will refund the costs of the support call.
Microsoft does have a central repository (perhaps separate ones per product), but this repository is not accessible for the general public.
If it's a documentation bug (or if the documentation should call it out), you can get good results with the Feedback links in MSDN library. You can report bugs in Microsoft developer tools (among other things) by signing up at connect.microsoft.com.
If you're sure you've found a bug in a core library routine, you can raise a PSS (support case. It'll cost you money, but if it turns out you're right (and they issue you a hotfix), I think that they refund the money.
I've never been so confident that I've found a bug that I'm willing to make that gamble.
I don't know why ChrisN took back his answer. I saw it earlier today when he had it up, He said:
You can report bugs on the Microsoft Connect website (I've done this in the
past). You don't have to have an MSDN
subscription.
I had not heard of the Microsoft Connect website, but when I used the search box there to search for "Registry Unicode", the first entry listed was a bug very similar to the one I encountered. And clicking through on that entry led me to look at the conversation that appears to be Microsoft people addressing the issue, passing it on to appropriate people and escalating it as necessary.
I have no experience with the Microsoft Connect website, but if it turns out to be as promising as it appears, this may be the answer to my question.