I've been to the codeplex site and I see members and a few bug reports, but I can't tell if there is new development going on or if it is just in cruise mode. Anyone have any further details?
Edit for comments
Many issues are proposed Proposed Issues
but the last time a code commit occurred was in November, 2010
Code Commit
AFAIK, commits don't occur unless there is some sort of hotfix, or a release. The codeplex repository isn't used for incremental updates such a nightlies or similar releases, more big bang.
Look forward to more information about the PRISM roadmap after BUILD in September.
http://compositewpf.codeplex.com/discussions/261609
Related
It is difficult to know what will be changed, new or fixed in RIDE.
How can we obtain that information?
The RIDE project now have a CHANGELOG that you can consult here.
You can see at the top of the document:
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to
Semantic Versioning.
You may also follow developments at https://forum.robotframework.org/, specifically on the RIDE topic.
As I write this question, 2 days after the beta of .NET 4.5 was released, the What's New in WPF 4.5 Version 4.5 Beta page on MSDN still lists "Integrating WPF with win32 Graphical User Interfaces" as an area in which WPF 4.5 offers improvements. That page talks about the two new properties on HwndHost that support this: IsRedirected and CompositionMode. Also, the top-level what's new in .NET 4.5 beta page mentions this integration as a new feature.
Again, as I write this, there are pages for those two items. You've got IsRedirected here and CompositionMode here. (Update 27th Jan 2014: original pages no longer available, so I've moved these links to point to the Internet Archive copies.)
However, if you go to the docs for HwndHost itself, neither of those properties is present. And they don't appear to be in Visual Studio either.
So it would appear that the rumours are true - it looks like the airspace improvements for interop have been dropped. But just in case anyone from Microsoft is reading this, it would be good if a) we could get positive confirmation and b) the pages mentioned above could be updated to stop getting our hopes up.
Update 27th Jan 2014: I've updated the links for IsRedirected and CompositionMode to point into the Internet Archive, because the original links are now dead. Also note that the What's New pages no longer mention this because those links are now for the final release. You can see the old pages that were current when I originally asked this question at this archived page and here.
There is a rather good blog post from Dwayne Need that describes the extraordinary effort they put in trying to make it work. Nothing subtle, they for example ending up intercepting over 200 GDI functions to get them to play along with the WPF rendering model. The outcome was to be expected:
You can imaging my heartbreak when, after an extensive review, we decided we could not actually ship this feature. Our concern was that we had to hack too deeply into the system, and in ways that were too difficult to explain - let alone maintain. Even though we required that developers explicitly turn on this feature for each HwndHost, we felt the kinds of problems they would encounter would be baffling to them and training our support engineers to handle the escalations would be very difficult. Even towards the end of our development, we were struggling with a long bug tail and performance concerns.
This is exactly the kind of deep system integration that needs to be done by the Win32 platform team, officially sanctioned and supported. With Win8, we are beginning to see some incremental improvements in this space, as noted before in the DirectComposition API. Unfortunately, it is still not possible to build the same kind of rich composited experience we had developed.
Whether the Windows group is going to commit to providing this kind of integration is right now an open question. They certainly put their money on a very different horse and spent a lot of effort on WinRT, a rendering model that's certainly inspired by WPF but doesn't do anything to make it better. If it is going to be tackled at all then count on years to get there.
Do check the rest of the blog post as well. It has excellent, albeit it high-level, advice on addressing existing airspace issues.
A suggestion to "Bring back the HwndHost.IsRedirected and CompositionMode" was posted at the Visual Studio UserVoice.
Microsoft declined it, saying:
at this time, we will not be able to add the feature to WPF and the .NET Framework.
It also looks like the MSDN pages you linked to have been taken down.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 7 years ago.
Improve this question
I just started a project with the newly release Sencha Designer Beta, and I was researching the free commercial license. Someone pointed out on a blog post comment that the 11. Support and Updates section of the license agreement is very restrictive and deceptive. After reading this section, I cannot fully understand it, as I have little experience in interpreting software license agreements.
Can anyone decode this for me in terms of what it really means about receiving updates to the Sencha Touch framework and what is means for someone who is creating an end-user mobile app?
11 . SUPPORT AND UPDATES
You are not entitled to any support for the Software under this
Agreement. All support must be purchased separately and will be
subject to the terms and conditions contained in the Sencha support
agreement. You are entitled to receive minor version updates to the
Software (i.e. versions identified as follows (X.Y, X.Y+1). You are
not entitled to receive major version updates (i.e. X.Y, X+1.Y) or bug
fix updates to the Software (X.Y.Z, X.Y.Z+1). Major version updates
and bug fix updates to the Software are available separately for
purchase.
I'm fully clear on the fact that you have to pay for support, but not about the availability of updates. When they release updated versions of the framework, how does this prevent someone from just updating their packages? What are the hidden pitfalls here? As long as we aren't directly requesting bug fixes and support, what in this text would prevent me from just downloading and updating my local framework to the latest release?
Here is a link to the blog post which contains the comment that caused me confusion on the matter: http://mobile.dzone.com/articles/sencha-touch-or-jquery-mobile
Please note that I do not endorse the view taken by this blog comment. I am only linking for the reason that it brought my questions to the surface.
As the person who wrote much of that text - originally for our Ext JS license - I can tell you that the intent was not to be deceptive, but some of the text doesn't make sense when it's applied to a free license like the Sencha Touch developer license (and legalese can be read with the wrong tone)
Here's what it means.
You've just downloaded version 1.0 of the software, good for you
You're entitled to get version 1.1, and 1.2, and 1.3 as well if and when we ship them
You're not entitled to get version 1.1.1, 1.1.2, 1.1.3 (if and when we ship them) - that's a benefit just for our technical support subscribers
You're not entitled to file technical support tickets either.
Does that make sense?
(Incidentally, I am a little upset by the implications of the comment in the post you linked and will reply to it now. Our support subscribers allow us to pay for developers to develop patches, which then we make available only to our support subscribers. All patches are rolled into the next minor release.)
I notice most of the discussions about Blackberry database options are old, and generally not too informative.
As of today, March 31st, 2010, what is the best, most universally supported, free database option available for Blackberry developers?
I heard SQLite is available for JDE v5, but last I checked, that was still in beta, and I didn't want to commit to developing on a system that is not supported by most of the phones in service.
Thing is, I don't see any dates on these claims. For all I know, the announcements I am reading are from 2008.
So, I am still on v 4.7. I need to use a relational DB for the app I am developing, but there aren't many resources for DB handling available - or at least resources that are useful to me. I find a lot of "tutorials" that assume you know everything there is to know about Blackberry development, or Java. But no complete classes or anything. Many of these examples don't even work. Eclipse gives warnings and errors from code copied and pasted from other people's examples.
I can answer any questions that may assist in this case. Hopefully, this thread will help many BB developers in the future.
Before v5 I don't think there is a native relational database that you can work with on the Blackberry, the closest thing is the Persistant Store API, however I think that there are 3rd party libraries that you can use, like SQL Anywhere.
Depending on the Java dialect supported on your Blackberry version, db4o could also work well for your usecase. It's an object database, quite similar to Perst.
Ok, in case anyone has had similar experiences with this, here is what I have done:
The JAR class path thing was resolved through no help at all from these sites.
What I did to get an outside JAR included in my package was to right click the package name in the navigation menu (Eclipse) - then select Build Path - then add libraries.
From this I was able to modify an existing library to include the JAR for the perst package.
Now I am able to import org.garret.perst.*
We'll see if there are any complications.
Forgive the number of posts, maybe it will help someone else down the way.
What are the pros/cons to using CTP technology for internal production softtware? By internal production I mean it's software we're not selling to anyone else but will be used by a large number of internal employees spread nationally.
I can see the obvious plusses (features and functionality that beats existing systems) and minuses (bugs, lack of support, changes in the interface, risk of discontinuation.) I'd like to hear from people with experience using preview tech in production software and the kinds of hurdles and things that we might not be considering.
The technology in question is the Silverlight Bing map control CTP.
Thanks,
It's a call that can be tough to make and really depends on your circumstances. A beta control from Microsoft, targeted at developers, that fills an immediate and important need, may be just the right fit if you are understanding the lack of support.
Especially given how quickly internal apps and even public sites go through revisions and quick improvement milestones.
The Silverlight Toolkit has been trying a new model for the last year; we've introduced special quality bands, to help customers make a call, and understand the investment and guarantees that the product team is making. I sort of hope we can get other teams to make a similar commitment.
The AutoCompleteBox control was essentially CTP a year ago, in the Preview quality band. Since then we invested and shipped it in the Silverlight 3 SDK as a mature, supported product.
Have a discussion with your management to define what risk you can take on while still enabling your internal users with quality value (scenarios that do work great, regardless of the released quality under the hood).
Consider source code!
One thing that you can also do is have a discussion around source and binaries. Although you won't always have an option to grab the source for many controls or frameworks, there are a lot of open source releases available today. Your control vendor may also be willing to offer a source license.
The cost for maintaining your own private branch of an open source control is high, but it is an avenue that can be explored if you need fixes earlier, want to add your own functionality, or feel that a developer day of work might just get an existing control customized for your scenario.
Updating with some more specific links:
Silverlight Toolkit
Here's more information on the Silverlight Toolkit's Quality Bands, for those that are interested. They are Experimental, Preview, Stable, and Mature; Preview is much like CTP, Preview - Beta, and Mature - Released and supported.
These are all just words, but they are "the word" of the team.
Microsoft Connect
WRT the Bing Maps control, I did see that there is a Microsoft Connect site out there. That's a great resource to have - although I am not in the program, typically Connect sites are there to help provide more frequent drops, a set of forums for discussing any issues, and a way to easily get in contact with the developers and testers on the product.
Other vendors
There are many other vendors out that that provide early releases, feel free to use the comments to add a non-Microsoft angle to this. I wanted to provide my opinion on these topics since I'm pretty familiar with a lot of the Silverlight-specific Microsoft frameworks that are out there.
Personally I don't think it's a good idea, as essentially your internal employees are your market, so this is essentially production software.
So things like licencing, compliance, support, SLA's may need to be thought through.
I know that would be frowned upon by my IT Director and Internal Audit people, to name two.
Are you reasonably sure it will work and not kill your employees' pets? Then it ought to be fine.
Seriously, just be sure it works for the target audience.
As always, IMHO.
Sometimes you just dont want to wait for a new feature, for instance we started using SQL Server 2008 in our new architecture just for the DateTimeOffset. We used this application internally, but this wasnt a major deployment. If its stable enough then why not. The Pros are you dont have to wait, you're testing new techniques, code and keeping up with technologies.
The cons are that some features will change, API arent finished or some things get renamed. These things present themselves pretty quickly and are normally easy to change. Also some things may not be documented, but there is always someone blogging about it.
With the tools available today like HockeyApp to manage betas for my apps I am less afraid to use preview APIs in beta versions of my apps. This way I can work out new functionality with real users who want to try out the bleeding edge.
When I have keep the new version limited to a small set of users this has been fine.
The times I have used preview technology in production I have been occasionally bitten by the bleeding edge. I have had to work around bugs or live with them while I waited for them to be fixed.