C and Objective-C have many differences.
First of all, C is procedure-oriented language while object-C is object-oriented language.
They have different syntaxes.
Objective-C is more familiar to smalltalk than C/C++.
e.g. of calling method
c: foo(param1, para2, ...);
objective-c: [object foo:param];
There are many differences between two languages.
hey all. i have an UIWebView(tarayici in my situation) in view controller. it works fine when its scroll view delegate is not assigned to view controller. but i need to know when it is scrolled that is why i wrote this code.
self.tarayici.scrollView.delegate = self;
but when i write this down then webview acts so weird. for example after this code when i want to scroll then it scrolls only once if i make 3 or 4 attempts. so how can make it work more efficient with that code ?
i think i found the solution. The commented UIview animation block locked the main thread i think that is why Scroll View couldnt response to the new touches. but with this new animation block it works well.
All of your questions really depend on what you are trying to accomplish when programming in Objective-C. If you are just using it as a language the answer is yes you can program with it on windows and linux.
However if you are looking to develop with the Cocoa frameworks and/or for iOS platforms then you will need:
1 - Apple hardware (mini, macbook, iMac, Pro)
2 - XCode will be the IDE that you most likely will want to start with if you are new and learning.
3 - You can get XCode from the App Store on your OSX machine.
Do you understnad the principles of the product you want to create? Are you a skilled OSX programmer, etc.?
Member 10608761 wrote:
Can I overwrite the existing desktop manager and replace their code with mine?
If you need to ask this question then the chances are that your understanding of OSX is not yet at the right level. I would suggest finding some study materials that give details of the operating system internals so you can gain a good understanding of how it all fits together.
I have experience with Objective-C and iOS development, but slightly new to OSX. Windows OS has a really good api for its Windowing system, whereas Quartz has an API but it is significantly limited in comparison. I'm looking to replicate the functionality of the Windows API in OSX, (specifically window-level controls), but it looks like all Window/Visual commands are handled through Quartz Compositor.
If I can rewrite/extend/reverse engineer that module, I may be able to get the APIs I need.
Sorry, meant slightly new to OSX development. I have been using the operating system for several years, but have never published a full app on it like I have for iOS.
Basically my problem is this: Windows treats everything like a window, where some of those windows belong to the same application. OSX treats everything as an application, where some of those applications have multiple windows.
When using APIs like the SendKeys[^] in Windows, you post messages to a specific window, and thus can post messages to multiple windows of different applications at the same time.
In OSX, that's not possible. Everything is done on the application level. You post messages through Quartz Event Services[^] to applications only. This is not idea for posting messages to two windows of the same application at the same time (two Word documents for instance if you wanted to copy a document). You can switch the active window, post a message, and switch back, but that is extremely noticeable to the user.
Quartz compositor must have a way of posting messages to individual fields on windows (whether or not the API is exposed) so if I could a) overwrite the existing system to expose this functionality or b) reverse engineer the quartz framework to check for hidden APIs. Either way is hard, and looking for suggestions.
Last Visit: 31-Dec-99 18:00 Last Update: 1-Oct-22 7:25