Hey, it's time to wake up, Boonex!

Is there any Dolphin updates on horizon besides alpha-release of non-function D8?

Is there are any damn mobile apps updates on horizon? Half of the code functionality is deprecated already, iOS 8 has been released some time ago, who is responsible to fix all damn deprecations and bugs? Since February 2015 it all could stop working if dear Boonex will not get time to update things that people are paying for.

"Starting February 1, 2015, new iOS apps uploaded to the App Store must include 64-bit support and be built with the iOS 8 SDK, included in Xcode 6 or later. "

https://developer.apple.com/news/?id=10202014a

Will you have time to change it all in less than 20 days?

I have really hard time to change native things in the app... It's just total rotten crap inside, without any comments which makes it damn hard to change anything. If you are selling source code, you should ALWAYS make comments and name things in appropriate way, rather than "sCaption", "sValue1", "sValue2", etc, etc, etc. Things should be named more clear rather than "myArray" like in damn "Hello World" simple one-view-based examples for noobs!

What does that crap means and how to understand what is it for without changing it and see where it will spark?!

 if (nil != sValue2) isValue2 = YES; else isValue2 = NO;

This looks like from my first TurboPascal programming in late 90th.

Why other people have to pull their hairs to understand what does all "values" and "captions" are for? Why to not make damn debug on/off switch for all NSLog across the app as leaving debug logging slows down the app on final release?! Why to not make a separate functions for things rather than single one and using across the entire app? When you make avatar image larger on ProfileInfo screen, it makes it larger everywhere across the app.

Why do we have to deal with this crap?...

Wake up, Boonex, it's time for updates and moving forward instead of being a dead horse!

So it is Boonex's responsibility for Apple's shit?  Why not go to Apple and complain to them?

 Oh, you are right... My favorite vinyl disk isn't compatible with modern BlueRay players as well... It's just sad..

"...new iOS apps uploaded to the App Store..." [emphasis added]

So this only affects BoonEx when they release an update to the app. I don't see how this affects the current version they have in the App Store. I welcome Apple forcing people to get with the times, though.

 Yes, it affects all new apps that will be released after this time. Including Dolphin apps. That's what I mean.

Sorry, Nathan, I've clicked "report" by mistake instead of "quote", your post became hidden, hope it will get fixed.

Nah, forum reports don't do anything. And you're right, I forgot about the rebranded apps. So yes, BoonEx needs to comment on this. I've PMed AlexT and linked him to this thread.

I believe that enabling 64-bit support is easy as change the setting in the app, as per Apple instructions:

"To enable 64-bit in your project, we recommend using the default Xcode build setting of “Standard architectures” to build a single binary with both 32-bit and 64-bit code."

sCaption and sValue variable names are given with purpose:

sValue - stores some value, imagine loop: foreach ($aSomeName as $sKey => $sValue) - $sValue changes in the loop, upon each iteration it can be first name, surname, headline, etc...

sCaption - if it's just a caption then it is referring to the current context, for example, caption of button if it is in button class.

Noooo, Boonex don't wanna wake up as they are having a beautiful dream about DU (Trident)

We will update mobile apps along with Dolphin 7.2 release, or even earlier.

Good Idea..

 So $aSomeName doesn't require a proper name as well? 

You have a bunch of the same color wires without any labels on them. How would you know which one is which? You only can pull it and see what happens or walk thru all its length to see where it's connected to. 

 >> for example, caption of button if it is in button class

We are dealing with the real concrete code, not with "examples". In real code it should be obvious. Why to not name it, let's say, sRefreshBtnCaption for refresh button instead of sCaption, so other programmers can re-use it without running thru the code and capturing its instances? If you need to make a loop with $value variable, sure it's ok, but it must have a description at least what this loop is for and what's inside. But you didn't wrote comments even for the functions! Using the same variables names in multiple files with various meanings is just bad practice of programming and you know that.

The rule of commenting is so obvious from the beginning so we shouldn't even touch such subject.

Maybe you'll be ready to sell your product sooner, but you and your customers will have headaches after. It's a perfect time killer.