Keep in mind hat while there’s (a lot) of overlap, not every DA user works in Elements. Many Cocoa users use ObjC and Apple Swift, and they are very happy having an API thats designed for Cocoa, rather than a common ground, the same is true for developers using, say, Android Studio wire DA/Java — they are happy DA has an APIn designed to fit in well with Java.
I read your message and see your sample is java related. I dont have any problem with java, that part of the app is already working perfect.
My problem is with cocoa, elements and RO and DA. I check the cocoa RO folders and thers not samples. Zero.
Please, let me know how to calla service method using proxy on elements and cocoa (IOS).
I need simple sample on ELEMENT and IOS for:
Loading Briefcase in async mode (passing dynamicwhere options to the datasets fill method).
DynamicWhere (i guess will be cover if theres a sample for the previous code).
Inserting a record on a DA briefcased remote dataset.
Fill a picker with data from a DA briefcased remote dataset.
Response to the event of selecting a picker item.
Calling a method for a RO server using proxy (as explained at start)
I hope you can point me out to that samples for IOS.
That’s odd. Probably installer didn’t found the Elements for Cocoa installation and decided not to drop samples. They had to be deployed to the folder c:\Users\Public\Documents\RemObjects Samples\Data Abstract for Cocoa
Please drop a mail to support@ and I’ll send you the samples.
You’ll just fetch the data table as you normally would, then add int to the briefcase and save it.
The Sample should cover that (check the commented-out code), but i recommend using DA SQL instead.
no difference than non-briefcased.
really depend son what a “picker” is. at this point, you’re talking basic UIKit GUI, unrelated to DA. You’ll want to read upon Apple’s docs, eg for UIPickerView, ditto for the previous item — binding the data table to show in a picker.
the code generated for you when you do “Connect to Remoting SDK Server” should show that, in particular the ServerAccess file that gets generated. it exposes singleton properties for all of the pixies you may need. If you want to do it manually:
var service := new RORemoteService withTargetURL(serverURL) serviceName("MyService");
service.channel.delegate := self;
var myService := MyService_AsyncProxy withService(service);
myService.beginSomeMethodCall(params...) startWithBlock( (aRequest) -> begin
var result := myService.endSomeMethodCall(aRequest);
// work with result
for an async call. The ServerAccess wraps the first half of that so you can just go
Well. if a call raises an exception, it by definition cannot have a result — because you‘d never get to it. So what is it, does the call return nil, or does it throw an exception? in the latter case, what is the exception message?