Then you must go to http://code.msdn.microsoft.com/windowsapps/Universal-Windows-app-cb3248c3 and see how JavaScript is a new foundation for Windows apps. If you don’t understand that JavaScript has been adopted as industry standard, you are limiting yourself in a very cr@py way.
[quote=99319:@Eduardo Gutierrez de Oliveira]I don’t think it’d be a bad idea to learn JavaScript, since the language is useful for many other things but that would be simple preparation for the time when you have to decide whether you want to migrate your automations.
[/quote]
Actually without Javascript there are many aspects of HTMLViewer and Xojo Web which could not be addressed easily. This week for example I used it to detect arrow keys in Internet Explorer that Xojo KeyPressed event does not see. And not too long ago to set scaling on Windows HTMLViewer. And this without having formally learned JavaScript. The language is fairly accessible, I think.
Thanks everyone, I’ll start studying JavaScript ASAP to improve my options.
There is very little to worry about, Adobe are terrible at following Apple’s guidelines for 10 years ago. It was only recently they they updated to Cocoa, with huge chunks of their framework still in Carbon (this is probably a big reason why Apple still can’t kill Carbon).
Heck Adobe still use Resource Forks, which urm Apple advised developers to ‘move on’ from, back in 2000 with Mac OS X 10.0 DP 1!
Almost as bad as FileMaker, who were still using PEF executables up until 2 years ago.[quote=99021:@Oliver Scott-Brown]So glad I don’t use Apple bullshit.[/quote]
This is just flame bait dude, there’s a reason why Apple’s platform is more secure than Windows… It has very little to do with only owning 12% of the computer market.
And FileMaker is technically Apple’s 
Yes, and carbon is another point I do not understand why not continue to provide minimal support but cut like by the way happen soon, I think this point Microsoft is more consistent since because not change technologies like Apple so radically.
Windows 8.1 “Metro” or “Windows Store” apps are a major technological change. For the moment being the desktop installed base is very large, but as all new machines massively use Metro, and as the Windows Store heavily promotes Metro apps, Windows developers will have to adapt in a far worse way.
I’m not sure what you mean.
Apple introduced Carbon to OS X in 2001, and even offered a Carbon library for early versions of Mac OS 8 (8.1, I think), for compatibility. They finally deprecated Carbon in 2012, after 11 or 12 years.
Carbon apps will actually still work fine in Yosemite when it’s released in the fall.
Let me explain, I have a friend who has a Photoshop 6 running on Windows 8, on my mac I can not even run Photoshop CS, I know this has nothing to do with Carbon pro but I just used to say that I think this point Windows more stable, although I only use Mac!
But that’s just my point of view might be wrong.
Well, that has more to do with Adobe making bad Mac software, than Apple. Old versions of Microsoft Office for Mac are still Carbon apps and still run “fine”; apparently this is still the case in Yosemite.
[quote=99693:@Paulo Vargas]Let me explain, I have a friend who has a Photoshop 6 running on Windows 8, on my mac I can not even run Photoshop CS, I know this has nothing to do with Carbon pro but I just used to say that I think this point Windows more stable, although I only use Mac!
But that’s just my point of view might be wrong.[/quote]
To be kind of cynical, I rather develop for Mac where software has to be upgraded regularly because of platform change. This generates a market for repeat business. I have had customers who bought apps back in 2002 for System 9. Then they had to upgrade for System X on PPC. Then on Carbon. Soon they will have to switch to Cocoa. I could not tell you I had a single customer go through all these motions, but I know quite a few who had to upgrade through some of these technological changes, and they where happy to find out their favorite application was available for their brand new Mac. And Apple renews hardware often enough to create a virtuous business cycle.
The Windows side, on the other hand, is often a one-shot sale : once an app works, it never gets upgraded. For a developer, the customer is lost 
[quote]
Michel Bujardet
10 hours ago Beta Testers, Xojo Pro
Edited 10 hours ago by Michel Bujardet
Oliver Scott-Brown So glad I don't use Apple bullshit.
Then you must go to http://code.msdn.microsoft.com/windowsapps/Universal-Windows-app-cb3248c3 and see how JavaScript is a new foundation for Windows apps. If you don’t understand that JavaScript has been adopted as industry standard, you are limiting yourself in a very cr@py way.[/quote]
Microsoft wasn’t necessarily happy with the idea but node.js kind of made it necessary; although Microsoft is accepting more openness they would have preferred something other than Javascript.
The world is jumping on the Javascript bandwagon so I hope that everybody things about the various implementations.
I also hope everybody realizes that the Javascript language uses 64 bit floating point. Tests have shown that it is good to about 53 bits and after that floating point errors start creeping in - you’re on your own.
Judging from Visual Studio, they have not made up their mind entirely and keep all options open. But the JavaScript implementation of Windows Store apps appears a lot simpler to program than C and VB.
[quote=99709:@Walter McCrate]The world is jumping on the Javascript bandwagon so I hope that everybody things about the various implementations.
I also hope everybody realizes that the Javascript language uses 64 bit floating point. Tests have shown that it is good to about 53 bits and after that floating point errors start creeping in - you’re on your own.[/quote]
Remember how Java was going to revolutionize programming ? Did not happen. Bandwagons are usually too good to be true.
That said, and to stay on topic, I find JavaScript well suited for automation. After all, there are real similarities between filling values in web pages, and feeding apps with typed characters. Not to mention click(). And I will never understand why Apple deprecated click() from AppleScript.
At a quick glance, though, while the core of JavaScript remains the same, fragmentation through dialects is bound to happen. There are major differences between JavaScript applied to web pages, to UI automation, and to Windows Store app development.
And I find the 53 bits limit interesting ; will it be the reason why MS did not issue its Office Suite in Metro flavor ? 
This is an interesting thought!
I don’t see this. Microsoft actually implemented JavaScript (or, rather, their JScript version of it) before anyone.
[quote=99693:@Paulo Vargas]Let me explain, I have a friend who has a Photoshop 6 running on Windows 8, on my mac I can not even run Photoshop CS, I know this has nothing to do with Carbon pro but I just used to say that I think this point Windows more stable, although I only use Mac!
But that’s just my point of view might be wrong.[/quote]
Not at all - your point of view is very valid and is shared by many. The only time I used to update Photoshop is when it no longer works, my copy of CS3 doesn’t work very well on Mavericks, so now I’m forced into their rental service. I’m okay with it, as I managed to get it for only $9.99 a month, which means that I roughly pay what I used to. While my Windows using friends are still using older version of Photoshop. What irks me the most, is that I only use Photoshop for content creation and there are less and less new tools for this. (Yes I’ve tried Pixelmator, several times and have written essays each time, politely outlining what tools and features someone like me would need to move from PS).
Back to the point, Apple’s aggressive refactoring and replacing is Apple’s strength and weakness.
It’s good because it means that out of date APIs that are insecure or unstable are updated to more modern, secure and more stable APIs. It’s what makes Apple’s OSes among the most reliable and secure in the world. It’s good for software developers, because it means that customers will be forced to update in the future. Apple continually add more powerful and awesome features to their toolbox, which we can take advantage of (RAW format support, Advanced Graphics manipulation to name a few that we use).
It’s frustrating for developers, constantly trying to keep up with Apple. Over the last few years, we’ve spent an extraordinary amount of time, simply trying to keep up with the App Store rule changes.
Microsoft’s attitude of compatibility is their greatest strength and their greatest weakness.
It’s good for developers, because you can continue to use APIs from way back int he 1990s, it’s good for consumers because they can continue to use software from the 1990s (On a new Mac, you can’t even run 8 year old software).
However it’s bad for consumers also, because MS still support almost all their legacy APIs as well as several more modern replacements, it leaves the OS insecure, unoptimized and bloated. It’s hard for MS to truly introduce a toolbox as vast and as optimized as Apple’s, quite simply because they have so much to support.
If MS adopted Apple’s attitude, Windows would become secure, more optimized and overall a better experience… However they’d lose their compatibility and that is their strength.
Yes Sam Rowlands I share your vision of the whole, this is exactly what I think too.
My biggest challenge is that before I outsourced much programming and the 3 years I have been developing myself what it takes me a long time by not having as much experience in this matter of AppleScripts that I use quite up some JavaScripts to run on mac and these changes constant discouraged me a bit.