Update of the plans for 2018, including a new release of Tokyo (10.2.3):
Update of the plans for 2018, including a new release of Tokyo (10.2.3):
https://community.embarcadero.com/blogs/entry/exciting-rad-studio-developments-in-2018
https://community.embarcadero.com/blogs/entry/exciting-rad-studio-developments-in-2018
https://community.embarcadero.com/blogs/entry/exciting-rad-studio-developments-in-2018
https://community.embarcadero.com/blogs/entry/exciting-rad-studio-developments-in-2018
I think this is a positive approach. More releases which allow fixes and improvements to be delivered rather than waiting for the next major release.
ReplyDeleteGood move on the proactive communication too. Rather than waiting until it is released, we are getting some information up front!
I hope this approach continues and we start getting more information on the specific improvements and fixes before it is released.
Moving in the right direction for me.
Marco Cantù Can I suggest that you contact the people that raised issues with the recent hotfix and Release 2 and allow them the opportunity to beta test this release. That would send a positive message that you are actively looking to ensure this is tested on as many setups as possible. No doubt you will get some very helpful feedback :)
"We have many exciting new features and product enhancements planned for Delphi..", yeeees, we are all very excited about the next surprises
ReplyDeletePerhaps one those exciting features will be a working hotfix for the broken 10.2.2 hot fix...
ReplyDeleteMarco Cantù Well, instead of "many exciting new features and enhancements" it would be enough, if we can use Tokyo again for Android apps. All of our apps working with Berlin are not even starting with Tokyo 10.2.2 ... and now in 4 months our subscription ends .... wow, was a very "good" invest last year into something we were not able to use ...
ReplyDeleteDon't know what to say, we hope the best ...
Martin Sedgewick thanks for the suggestion, we are definitely going to have a significant number of external people test 10.2.3 before shipping it.
ReplyDeleteJennifer Powell all of the hotfix content will be rolled in the new update, but the hotfix is coming out soon before that
Yusuf Zorlu you write "all of our apps working with Berlin are not even starting with Tokyo 10.2.2": is this the animation issue or something else? Has this been reported? Did you get in touch with support?
MacOS 64bit compiler is very important, we cannot provide new apps for the AppStore!
ReplyDeleteMarco Cantù i have found some tickets in past and had voted for them, so it seems that this issue is known ... i.e.
ReplyDeletehttps://quality.embarcadero.com/browse/RSP-19552?filter=-3
https://quality.embarcadero.com/browse/RSP-19738?filter=-3
https://quality.embarcadero.com/browse/RSP-19694?filter=-3
and so on ...
Any news on this? https://quality.embarcadero.com/browse/RSP-17195
ReplyDeleteYusuf Zorlu I see. It is a severe issue, but it is a Android 4.x issue. Don't take me wrong, I know it is critical as you don't control your users devices, but "all of our Android apps are not starting" is slightly broader than they are not starting on one version. Anyway, the issue is being looked after by R&D.
ReplyDeleteIn general, we recommend escalating critical issues via support. As part of the subscription, you have 3 support tickets, and bug reports don't even count against those, I think. This does help prioritizing, along with votes.
Marco Cantù this is critical because we work with Motorola / Symbol / Zebra scanners with Android os and those devices can't updated ... all devices have 4.x installed, so the sentence "all of our android apps" is correct in our case!
ReplyDeleteYusuf Zorlu Got it!
ReplyDeleteMarco Cantù we also faced this issue with Industrial Android 4.x devices (Honeywell, Zebra, Motorola). Tokyo was never used because of this. Software was developed under Berlin.
ReplyDeleteMarco Cantù It is not Android issue. It is in FMX code. FMX is destroying OpenGL shared context, and then it calls code that finalizes the shaders. Finalizing shaders calls Valid function that in turn creates shared context again, but it is different one and deleting shader fails - and FMX raises exception (which at that point is absolutely useless) but the point is that logic of FMX code is completely broken.
ReplyDeleteIt seems pretty lame that Marco, who I understand to be quite high up in the food chain, feels compelled to ask people to use up precious support queries to get show stopper bugs fixed.
ReplyDeleteI can still remember the promise of a new focus on quality. Seems that promise was empty.
the owner of Delphi just blogged about how more and more people are using Delphi for android support...and yet that is broken still? (in Tokyo)
ReplyDeleteWhat blog did you read that on?
ReplyDeleteStéphane Wierzbicki Marco Cantù One of my clients (whose clients use Zebra devices) is still stuck at Berlin(for Android) because of the issue being referred to by Dalija Prasnikar. My Lenovo Tab 3 (Android 5.1.1) suffers the same fate
ReplyDeleteIt was linked from the EMB Facebook posts 're the owner of EMB post I referred to above.If I find it I will post link
ReplyDeletehttps://community.embarcadero.com/article/16606-modernize-your-apps?utm_source=Facebook_Organic&utm_medium=social
ReplyDeleteDalija Prasnikar Yes, thanks, I know it is a FMX issue and it end up with slightly different type of crash depending on the version of Android. 4.x is the one affected worse. We have a fix in the works.
ReplyDeleteDavid Heffernan I don't get your point. Pointing to critical issues does not use up your support calls, afaict. The support team is the official contact to escalate bugs, not PM team (although we are more than willing to help). I doubt that's an Embarcadero or Idera approach, seems fairly universal. Considering that anyone on a recent version has support included in his subscription, I don't see how we are not focusing on quality by asking to escalate critical bugs via support.
"Owner of EMBT" is a strange way to refer to the general manager, BTW. He does not own the company, he helps running it...
Marco Cantù will this FMX issues fixed in Tokyo release? I'm asking this because I'm reluctant to renew my subscription (in my special case, Tokyo is taking dust...)
ReplyDeleteStéphane Wierzbicki this is the plan.
ReplyDeleteMarco Cantù I was looking at the part of your post where you talking about 3 support cases. I'm surprised you don't know whether escalating bug reports count against the 3 support cases. Perhaps you should find out definitively.
ReplyDeleteIt would be appropriate to not always make new releases, but sometimes to correct the 5000 errors that are already in the product. So to speak, a "Delphi Power Bugfixing Pack 2018" (for free, of course, we've already paid thousands of dollars!)
ReplyDeleteEmb has launched two updates knowing full well that Android is broken on Tokyo. Two many bells and whistles and insufficient nuts and bolts coming out. Very difficult to beat the drum for Delphi with Tokyo not living up to what it is advertised to do? So are we going to receive compensation on the next round of subscription payment due? Emb's move to do away with upgrades was strategic to prevent us from moving away from subscription when a large issue such as this is brewing. The next subscription payment will be a grudge payment with two many empty promises coming out of the stable. Some may elect to stop subscription however the barrier to coming back at full price is rather high!!!!! Direct communication from Emb is lacking on these issues while Idera sends plenty of direct email advertising. Perhaps a more appropriate survey that allows individual responses to highlight what is actually happening on the ground would be welcomed. Deliver the full package and the developers will continue to beat the drum and the development language will gain an improved market perception and we as developers will continue to remain loyal and happy.
ReplyDeleteHaving read the blog post, I am glad that 10.3 addresses the state of the debuggers, since the current state is rocky/unstable. I do wish it also had mentioned Nullable types, which are in the roadmap - which has a disclaimer on what will/will not make it. Will we get Nullable types in 10.3? If not, my excitement level drops off pretty fast.
ReplyDeleteLars Fosdal Plans for Delphi language improvements in 10.3 have not changed. There will be a few nice features...
ReplyDeleteMarco Cantù "There will be a few nice features..." I've never understood this need for secrecy. Why can't you tell us exactly what's going to be in it?
ReplyDeleteJoseph Mitzen Actually, that is pretty much routine for software everywhere. You really don't know until cutoff.
ReplyDelete