Page 6 of 6
Re: UnityPackage 1.3 BETA7
Posted: 27 Feb 2017, 05:44
by ai_enabled
Still doesn't work properly for us (well we have 148 XAML files in our game!), but I've already sent a project to NoesisGUI team so the fix is matter of time. Now it's for GDC! I wish all the best to you, guys!
By the way, am I the only one who thinks that this version should be 3.0, not 1.3? There are so many new features and refactoring and v1.2 was released 2 years ago! That's good for marketing too.
Re: UnityPackage 1.3 BETA7
Posted: 27 Feb 2017, 09:03
by Ziriax
Yes, 3.0 it should be, good idea!
Re: UnityPackage 1.3 BETA7
Posted: 27 Feb 2017, 11:26
by jsantos
Yes, this is something we have debated here many times. Not 3.0 ... but, shouldn't it be a 2.0? We have two days to decide... : )
Re: UnityPackage 1.3 RC3
Posted: 27 Feb 2017, 12:04
by jsantos
RC3 released! New platforms included: android and uwp
Re: UnityPackage 1.3 RC3
Posted: 27 Feb 2017, 16:43
by nokola
Nice! Trying the Android now. Also, best of luck at GDC, very exciting!
Version: Personally I don't care whether it's 1.3 or 2.0. I think 2.0 may make more people look at it that are not familiar with the technology compared to 1.3. btw, is WebGL planned for this version?
Re: UnityPackage 1.3 RC3
Posted: 27 Feb 2017, 16:45
by nokola
Just to mention again: absolutely phenomenal job adding all these new platforms, thanks for making it.
Re: UnityPackage 1.3 RC3
Posted: 27 Feb 2017, 17:10
by KeldorKatarn
Considering there are a lot of breaking changes, like the noesisGUIPanel being a NoesisView now and the way code behind is added and how XAMLs are assets now I'd really suggest you go for 2.0. 1.3 suggests only updates and feature additions. 2.0 signals more that this includes major API and workflow as well as asset pipeline changes.
Re: UnityPackage 1.3 BETA7
Posted: 28 Feb 2017, 11:49
by ai_enabled
Yes, this is something we have debated here many times. Not 3.0 ... but, shouldn't it be a 2.0? We have two days to decide... : )
Well, 3.0 is better for marketing
. But you're right, it's 2.0 indeed. 1.1/1.2 was a good evolution, but 1.3 is a big leap ahead. I know from my experience when you work on something big you don't feel the progress that huge (as from your point of view it's very incremental, little by little, during years), but actually it is.
Considering there are a lot of breaking changes, like the noesisGUIPanel being a NoesisView now and the way code behind is added and how XAMLs are assets now I'd really suggest you go for 2.0. 1.3 suggests only updates and feature additions. 2.0 signals more that this includes major API and workflow as well as asset pipeline changes.
Exactly! In some cases It's a lot of work to upgrade to the new version.