|
Group: Forum Members
Posts: 533,
Visits: 2K
|
Hi,
I was hearing about SF 2.0 for quite a long time, which mentioned will be including a lot of fanstatic features such as LINQ support, ORM mapper and etc. I would like to know, what is your roadmap for this? Will it be 2008, 2009 or... all this features will be released incrementally?
Thank you
|
|
Group: StrataFrame Users
Posts: 52,
Visits: 559
|
Hi Trent,
Thanks for update.
My friendly and sincere suggestion to MicroFour to increase support to this form users for daily issues.
We can wait this great product while knowing SF team is near us.
We will feel our self in safe in that case.
And this will give you enough time to develop SF 2.0.
Best regards
|
|
Group: StrataFrame Developers
Posts: 6.6K,
Visits: 6.9K
|
Hector: The daily time we can now contribute to SF is also being more active in the forums. All good advice.
|
|
Group: StrataFrame Users
Posts: 277,
Visits: 1.1K
|
Trent, I have to admit I feared the worst so I appreciate the update. I look forward to hearing how severe the upgrade path is for an existing SF 1 application, i.e. is it a re-write around a significantly different SF2.
|
|
Group: StrataFrame Developers
Posts: 6.6K,
Visits: 6.9K
|
Aaron: I can address at least part of that. I am not sure how much time you have spent in WPF, but there is a very steep learning curve to be proficient. The concept is completely different and you have to learn how to work with multiple languages, basically. You have all of the new classes and concepts, but you also have to learn XAML. Conceptually WPF is 100% different and it has been my experience that you cuss it until to catch it.  There are some things that if feels like you are going backwards on, but others that are incredible regarding WPF. The fact that it sits on top of a true graphics engine (Direct X) and can run in a less robust environments as well is pretty awesome in regards to performance. However, the further you dig into WPF the more you see the need and importance of a framework. That being said, StrataFrame V2 has changed philosophies moving to a true object entity model. This means that your old BOs will be re-created as entities, which trust me, you will be happy about once you do it. We will try and provide some tools to convert things over to a certain degree, but the objects you use now will be replaced as you move forward. This doesn't have to all be done at once. The good news is that you are still in .NET, so you can migrate things over a piece at a time, but in the end, you will have a new code base for your UI and business entities. The data layer is pretty transparent, so there isn't much to do there. Hope that at least gives you a bit of information so you can plan moving forward.
|
|
Group: StrataFrame Users
Posts: 2.4K,
Visits: 23K
|
Hi Trent, Glad to you see back!!!! As you may guess, there are many more questions  I like the idea of WPF, even though I have not even try it yet, but when using Windows Form, will the BO still be based on Entity Framework? P.S. I am working on converting a complex VFP application into SF VB.Net and even though I am very used to the DDT, there are some automation needs that would help setting the NULL Type, etc. current version could be very tricky and get things messed up if not careful, I can't wait to see the new one, even if that what is being released first.
Edhy Rijo
|
|
Group: StrataFrame Developers
Posts: 6.6K,
Visits: 6.9K
|
> I like the idea of WPF, even though I have not even try it yet, but when using Windows Form, will the BO still be based on Entity Framework?
Just to clarify, it is not the "Entity Framework" from Microsoft, but it is an entity object model. Yes, you will still use the entity model in the Windows Forms side of things. Obviously you can still use the standard BO there as well. In fact, I have used an SF V1 BO to populate an object model to use in WPF. So there are a lot of ways to go about this, but in the end you want to convert all of your BOs into entities. They are going to be faster and do a lot more for you. But for now, since the SF V2 isn't released, yes, create BOs and move forward as you normally would.> The future of WPF
I saw that Oliver posted regarding the future of WPF so I thought I would comment here. First, Microsoft is all in with WPF. There hasn't been any GDI+ development since before Windows 7 hit the street. WPF is pretty amazing when you dig into the guts of it, but moreover, this is the platform that Microsoft is betting on. HTML5 is cool and there will be more attention given to it by Microsoft, but it cannot and will not replace the desktop platform. Silverlight, on the other hand, is basically an extension of WPF to the web. And honestly, if you are writing an application that needs to be made available online, then yes, go for it. It is robust and you can write powerful applications using WPF for the web environment. However, you wouldn't want to use Silverlight for a standard website. In this case HTML5 will most definitely become the leader, and has. But in short, WPF as a development platform is only going to grow and so at some point it is really important to jump off of the Windows Forms platform and onto WPF.
At some point I am going to be releasing my blog. This will cover some topics about my transition to WPF. Honestly, it really made me mad at first. I wanted to get in the ring for at least a 5 minute round with whoever was trying to force WPF into the marketplace. But once I wrapped my head around the engine and its potential, I started to come around. Like any platform, there are things that I don't like and things that I do. But in the end, I think that WPF is here to stay and is the direction developers need to move in order to stay current with the marketplace and the OS platforms coming out in the future.
|