Re: Investigating Noesis
Posted: 03 Mar 2017, 13:02
Hey Team Noesis, congratulations on the v2.0 launch! I have been taking advantage of the new free-to-indie licensing and checking out your wares.
There was also a wicked awesome suggestion by your Twitter handle to possibly create a kickstarter to address the very popular request of a ubiquitous .NET client application model.
I decided to reply here as it is much more than 140 characters.
So to start with, Noesis offers pretty much everything that is required for this idea. There are four major platforms that would need (or expected) to be reached:
- Windows (duh)
- iOS (Mono)
- Droid (Mono)
- Web (on the way)
So next is the actual capabilities you find in WPF. Taking the morning to review your NoesisManaged assembly, it appears that all the pieces are in place here, with the exception of markup extensions which appear to be on the way (accomplishing something UWP hasn't been able to do in five years, but we'll step over that). Also, it appears that a lot of the expected controls are in the Noesis namespace, so that looks good. You also have NameScopes, so we're able to access controls in code behinds if necessary. Attached properties are also there, which is important as this adds a lot of the power/flexibility/extensibility that we enjoy with WPF.
The only thing that isn't offered is 3D, but that is easily addressed by pairing your product with Unity or any of the integrations that you (unofficially ) support. So to me this isn't a problem. There is also the System.Windows.Interactivity namespace, with behaviors and triggers. This would need to be built, but I do not think that would take much effort.
Plus the extra cherry on top is that you already feature Ammy integrations. You are also very engaging on your forums and (again, not drawing names, ha ha) seem to care a lot about Xaml. So there is a lot here that already exists and that you have going for you.
All the fundamentals are there. It would seem the only things missing are control contracts with the big name vendors (such as ComponentOne), and also styling. Because, as you mention in your tweet, your focus is on gaming, and not (I assume LOB) "applications." Well I hate to break it to you, but if you support theming and skins, you already support everything. It's just a matter of implementation at this point.
So I wanted to this out there and get your take on this and what you meant by a Kickstarter and what that would involve/look like. I would definitely be interested in perhaps assisting if necessary, but I am thinking most of the highly sought-after value is already there and wanted to get your take.
In any case, this is really promising, team. When I posted that idea to UserVoice in October 2015, I was expecting maybe 1,000 votes at the very most after a year or so of time. We're sitting here 19 months later at 6,200+ and it seems like promising answers are finally emerging. The comments of that idea are pretty active right now, with Noesis mentioned in nearly every one. Pretty excited about the future here.
Thanks again,
Michael (or Mike-EEE on Twitter and elsewhere)
There was also a wicked awesome suggestion by your Twitter handle to possibly create a kickstarter to address the very popular request of a ubiquitous .NET client application model.
I decided to reply here as it is much more than 140 characters.
So to start with, Noesis offers pretty much everything that is required for this idea. There are four major platforms that would need (or expected) to be reached:
- Windows (duh)
- iOS (Mono)
- Droid (Mono)
- Web (on the way)
So next is the actual capabilities you find in WPF. Taking the morning to review your NoesisManaged assembly, it appears that all the pieces are in place here, with the exception of markup extensions which appear to be on the way (accomplishing something UWP hasn't been able to do in five years, but we'll step over that). Also, it appears that a lot of the expected controls are in the Noesis namespace, so that looks good. You also have NameScopes, so we're able to access controls in code behinds if necessary. Attached properties are also there, which is important as this adds a lot of the power/flexibility/extensibility that we enjoy with WPF.
The only thing that isn't offered is 3D, but that is easily addressed by pairing your product with Unity or any of the integrations that you (unofficially ) support. So to me this isn't a problem. There is also the System.Windows.Interactivity namespace, with behaviors and triggers. This would need to be built, but I do not think that would take much effort.
Plus the extra cherry on top is that you already feature Ammy integrations. You are also very engaging on your forums and (again, not drawing names, ha ha) seem to care a lot about Xaml. So there is a lot here that already exists and that you have going for you.
All the fundamentals are there. It would seem the only things missing are control contracts with the big name vendors (such as ComponentOne), and also styling. Because, as you mention in your tweet, your focus is on gaming, and not (I assume LOB) "applications." Well I hate to break it to you, but if you support theming and skins, you already support everything. It's just a matter of implementation at this point.
So I wanted to this out there and get your take on this and what you meant by a Kickstarter and what that would involve/look like. I would definitely be interested in perhaps assisting if necessary, but I am thinking most of the highly sought-after value is already there and wanted to get your take.
In any case, this is really promising, team. When I posted that idea to UserVoice in October 2015, I was expecting maybe 1,000 votes at the very most after a year or so of time. We're sitting here 19 months later at 6,200+ and it seems like promising answers are finally emerging. The comments of that idea are pretty active right now, with Noesis mentioned in nearly every one. Pretty excited about the future here.
Thanks again,
Michael (or Mike-EEE on Twitter and elsewhere)