RemObjects Wiki - Recent changes [en]

DA LINQ in Depth (.NET)

2012-05-17T06:32:36Z

← Older revision		Revision as of 06:32, 17 May 2012
(2 intermediate revisions not shown)
Line 1:		Line 1:
	{{ArticleTopic\|Data Abstract\|.NET}}		{{ArticleTopic\|Data Abstract\|.NET}}
	{{PageQuality\|good}}		{{PageQuality\|good}}
-	{{~~wipr\|42163~~}}	+	{{wipt}}
	{{stub}} <!-- do not remove while still wip -->		{{stub}} <!-- do not remove while still wip -->
	__NOEDITSECTION__		__NOEDITSECTION__
Line 37:		Line 37:
	<center>[[Image:Chosing_Linq_engine.png \| Chosing DALINQ Engine]]</center>		<center>[[Image:Chosing_Linq_engine.png \| Chosing DALINQ Engine]]</center>

-	It will create proper LinqDefinitions classes for given DA server and add {{~~linkc~~\|~~DALinqDataAdapter~~}} component to your DataModule class.	+	It will create proper LinqDefinitions classes for given DA server and add either {{class\|LinqRemoteDataAdapter}} or {{class\|LinqLocalDataAdapter}} (used in 2-tier applications) component to your DataModule class.

	For other side you can change any of your existing projects to use [[DA LINQ]] by making following steps:		For other side you can change any of your existing projects to use [[DA LINQ]] by making following steps:

Getting Started with Data Abstract for Xcode

2012-05-17T04:23:29Z

Frequent Next Tasks:

← Older revision		Revision as of 04:23, 17 May 2012
Line 26:		Line 26:
	** [[Displaying Data in NSTableViews]] (Mac)		** [[Displaying Data in NSTableViews]] (Mac)
	*** [[DAArrayDataSource In Depth]] (Mac)		*** [[DAArrayDataSource In Depth]] (Mac)
-	*** [[Displaying ~~Date~~ with Cocoa Bindings]] (Mac)	+	*** [[Displaying Data with Cocoa Bindings]] (Mac)
-	** [[Displaying ~~data~~ in NSOutlineView]] (Mac)	+	** [[Displaying Data in NSOutlineView]] (Mac)
	** [[Filtering Data with NSPredicate and NSPredicateEditor]] ([[WIP:Filtering Data with NSPredicate and NSPredicateEditor\|wip]])		** [[Filtering Data with NSPredicate and NSPredicateEditor]] ([[WIP:Filtering Data with NSPredicate and NSPredicateEditor\|wip]])
	** Data Handling		** Data Handling

DAArrayDataSource In Depth

2012-05-16T16:24:07Z

New page

{{ArticleTopic|Data Abstract|Xcode}}
{{PageQuality|good}}
__NOEDITSECTION__
__NOTOC__


One of the ways to show the data in the ''NSTableView'' component is to provide a delegate class for it as the ''dataSource'' property. More information about this approach you can find [[Displaying Data in NSTableViews|here]]

Its advantage is in its simplicity. You can manually control how the data gets into the table and from it. At the same time it is really efficient. But for the other hand you need to write quite a lot code for it and this we can consider as small but nevertheless disadvantage.

Another point is following: usually, the window or view controller, which owns the ''NSTableView'' component, plays the role of DataSource delegate. But what if we need to handle more than one table view component in the window? Of course each method of the the ''NSTableViewDataSource'' protocol takes the reference to the table view outlet. Thus we always know who called it. But we will need to combine, probably too different, implementations for these several table views into the single method making it more sophisticates and difficult to maintain.
In order so solve all questions above RemObjects offers special ''DAArrayDataSource'' class, which internally implements for you all necessary methods for working with table views. 

== Quick start==

It’s very simple to use the ''DAArrayDataSource''. All you need to do is to create an instance of the ''DAArrayDataSource'' and set its array property and set up a proper identifier for each column of the table view in order to map the table fields to the table view columns and finally tie up the ''DAArrayDataSource'' with your ''NSTableView''. Take a look at the sample below:

<source lang="objc">

// Create and configure the RemoteDataAdapter to use local Samples Server
NSURL *url = [NSURL URLWithString:@"http://localhost:8099/bin"];
DARemoteDataAdapter *adapter = [[DARemoteDataAdapter alloc] initWithTargetURL:url];
[[adapter dataService] setServiceName:@"DASampleService"];

// Get the data
DADataTable *workerTable = [[adapter getDataTable:@"Workers"] retain];

//Create the DAArraySource
DAArrayDataSource *arrayDS = [[DAArrayDataSource alloc] init];

// Load data here
[arrayDS setArray:[workerTable rows]];

// Tie it up with the NSTableView
[arrayDS setTableView:tableView];
</source>

<div class="note">
'''Note:'''
The fact that the ''DAArrayDataSource'' encapsulates the ''NSTableViewDataSource'' methods inside will help you in case your controller has several table views. Just use separate instances of the ''DAArrayDataSource'' for each table view to avoid messiness in your code.
</div>

==Sorting data==

At the same time, the ''DAArrayDataSource'' provides a set of additional interesting features.  For example, without writing a line of code, you can sort data inside your table view by clicking on the column header. Moreover, you can sort by several fields at the same time. For example:

<source lang="objc">

// Sort by the Position field first
[arrayDS setSortField:@"WorkerPosition"];

// Then sort by First Name
[arrayDS setSecondarySortField:@"WorkerFirstName"];

// Both sorts are descending
[arrayDS setSortAscending:NO];

// And that's all, from here on, the data is sorted
</source>

<center>[[File:DAArrayDataSource.TwoFieldsSorting.png]]</center>

Also, the ''DAArrayDataSource'' will persist the current rows selection between different modes of sorting. Just before applying sorting, it will store the selection and will try to restore it after applying new sorting. Thus you will never lose the records on which you are working at the moment.

<div class="note">
'''Note:'''
Unfortunately, this won’t work if you try to reload all data and the entire “rows” array will be changed.
</div>

== Editing & display changes==

Another interesting feature is that the ''DAArrayDataSource'' controls the ability of the table view to do inline editing.  If its ''read-only'' property equals NO, you can edit data and all changed rows will be shown in a BOLD font until they are applied, so you can easily see what changes you’ve just made.

<center>[[File:DAArrayDataSource.ChangedRows.png]]</center>

==Advanced view customization==

The DAArrayDataSource has ability to widely adjust table view it owns. It allows you to specify the font type, its color and size, as well as the row height for the whole NSTableView. Using a delegate of the ''DAArrayDataSource'', which should implement the ''DAArrayDataSourceDelegate'', you can hook on various events. For example:

<source lang="objc">

- (void)tableView:(NSTableView *)tableView
needsTextColor:(NSColor **)text
backgroundColor:(NSColor **)back
forRow:(NSInteger)rowIndex {

// Getting the value
DADataTableRow *row = [[arrayDS array] objectAtIndex:rowIndex];
NSString *positionValue = [row valueForKey:@"WorkerPosition"];

// Conditional coloring
if ([@"Sales Manager" compare:positionValue] == NSOrderedSame)
*text = [NSColor redColor];
if ([@"Sales Representative" compare:positionValue] == NSOrderedSame)
*text = [NSColor greenColor];
if ([@"Inside Sales Coordinator" compare:positionValue] == NSOrderedSame)
*text = [NSColor blueColor];
}

-(void)tableViewSelectionDidChange:(NSTableView *)aTableView {

NSMutableString *selectedPerson = [NSMutableString stringWithString:@""];
for (DADataTableRow *row in [arrayDS selectedRows]) {

[selectedPerson appendFormat:@"%@ %@ (%@)\n",
[row valueForKey:@"WorkerFirstName"],
[row valueForKey:@"WorkerLastName"],
[row valueForKey:@"WorkerID"]];
}
[selectedPersonLabel setStringValue:selectedPerson];
}

</source>

<center>[[File:DAArrayDataSource.ViewCustomization.png]]</center>

You can get the source code of the project I’ve used above here [http://rorox.remobjects.com/alexk/DAArrayDataSource_Sample.zip here] :

Displaying Data in NSTableViews

2012-05-15T19:51:01Z

← Older revision		Revision as of 19:51, 15 May 2012
(One intermediate revision not shown)
Line 13:		Line 13:

	Presenting tabular data is the one of the most common scenarios in the programming.		Presenting tabular data is the one of the most common scenarios in the programming.
-	Cocoa offers nice control - ''NSTableView'' ~~for this~~ and offers several approaches of work with it.	+	Cocoa offers nice control - ''NSTableView'' and offers several approaches of work with it.
-	~~One way is using ''Cocoa Binding'' technology and other is providing special delegate object as the ''dataSource'' property for ''NSTableView''.~~	+
-	~~In this article we will describe the second approach~~.	+

		+	One way is the providing special object as the ''dataSource'' property of the ''NSTableView''.
		+	This object plays the passive role of the delegate and provides set of methods actively used by the ''NSTableView''.
		+	In order to act as the data source it must conforms to ''NSTableViewDataSource'' informal protocol.
		+
		+
	== Displaying data ==		== Displaying data ==

-	'~~'NSTableView'' has dataSource property~~ which ~~can take a reference~~ to ~~an object that conforms~~ to ~~''NSTableViewDataSource'' informal protocol~~. In order to show the data our delegate need to implement several methods ~~which will be used by the ''NSTableView''.~~	+	Let's imagine the scenario where we have DADataTable instance called workersTable which data we need to expose in the NSTableView.
		+	The easiest way for us will be to turn our window controller to the datasSource delegate for the NSTableView control.
		+	In order to show the data our delegate need to implement several methods:

	One of them should return count of rows in our ''DADataTable''.		One of them should return count of rows in our ''DADataTable''.
Line 50:		Line 55:
	</source>		</source>

-	Note, that method above takes certain NSDataTableColumn of the NSTableView as the parameter. At the design time we can store there binded field name as the column identifier.	+	Note, that method above takes certain ''NSDataTableColumn'' of the ''NSTableView'' as the parameter. At the design-time we can store there binded field name as the column identifier. Later in run-time,inside this method, we can get it back and use as the key for obtaining value from given row.

	<center>[[File:Displaying data in the NSTableView.Column Identifier.png\|800px]]</center>		<center>[[File:Displaying data in the NSTableView.Column Identifier.png\|800px]]</center>
-
-	~~Later inside this method we can get it back and use as the key for obtaining value from given row.~~

	Now its time to setup the ''NSTableView''. Add it as the outlet. Also note that our controller respond to ''NSTableViewDataSource'' protocol		Now its time to setup the ''NSTableView''. Add it as the outlet. Also note that our controller respond to ''NSTableViewDataSource'' protocol
Line 61:		Line 64:

	@interface MainWindowController : NSWindowController <NSTableViewDataSource> {		@interface MainWindowController : NSWindowController <NSTableViewDataSource> {
-	...	+	...
	IBOutlet NSTableView *tableView;		IBOutlet NSTableView *tableView;
-	DADataTable *workersTable;	+	DADataTable *workersTable;
	}		}
		+	...
	@end		@end

	</source>		</source>

-	and set its dataSource property. The good place to do that is the AvakeFromNib method.	+	and set its ''dataSource'' property. The good place to do that is the ''AvakeFromNib'' method.

	<source lang="objc">		<source lang="objc">
Line 76:		Line 80:

	...		...
-	[tableView setDataSource:self];	+	[tableView setDataSource:self];
	}		}

Line 82:		Line 86:


-	Finally make the connection between the UI controls and outlets in the code	+	Finally, using InterfaceBuilder designer make the connection between the UI controls and outlets in the code

	<center>[[File:Displaying Data in the NSTableViews. Making connection.png\|800px]]</center>		<center>[[File:Displaying Data in the NSTableViews. Making connection.png\|800px]]</center>

	<div class="note">		<div class="note">
-	'''Note:''' This approach you can see in many of our samples. It is quite simple to do, and at the same time, ~~its~~ very efficient. Your data source can have thousands of rows but table view will still be quick and without lags.	+	'''Note:''' This approach you can see in many of our samples. It is quite simple to do, and at the same time, it is very efficient. Your data source can have thousands of rows but table view will still be quick and without lags.

-	For example, NSTableView on following screen ~~contains~~ about 45K! rows	+	For example, NSTableView on following screen working with about 45K! rows
-	~~<center>[[File:Displaying Data in the NSTableViews. Huge table.png\|800px]]</center>~~	+
	</div>		</div>
		+	<center>[[File:Displaying Data in the NSTableViews. Huge table.png\|800px]]</center>

	== Editing data ==		== Editing data ==


-	Our next ~~task~~ is to do ''NSTableView'' editable. ~~Its~~ quite simple, we just need to implement one more method of the ''NSTableViewDataSourceProtocol'' which can set new value for given row and given column for our ''dataSource'' object.	+	Our next goal is to make ''NSTableView'' editable. This is quite simple, we just need to implement one more method of the ''NSTableViewDataSourceProtocol'' which can set new value for given row and given column for our ''dataSource'' object.

	<source lang="objc">		<source lang="objc">

File:Displaying data in the NSTableView.Editing Data.png

2012-05-15T19:01:57Z

uploaded "[[File:Displaying data in the NSTableView.Editing Data.png]]"

Displaying Data in NSTableViews

2012-05-15T19:01:24Z

← Older revision		Revision as of 19:01, 15 May 2012
(One intermediate revision not shown)
Line 87:		Line 87:

	<div class="note">		<div class="note">
-	This approach you can see in many of our samples. It is quite simple to do, and at the same time, its very efficient. Your data source can have thousands of rows but table view will still be quick and without lags.	+	'''Note:''' This approach you can see in many of our samples. It is quite simple to do, and at the same time, its very efficient. Your data source can have thousands of rows but table view will still be quick and without lags.

	For example, NSTableView on following screen contains about 45K! rows		For example, NSTableView on following screen contains about 45K! rows
-		+	<center>[[File:Displaying Data in the NSTableViews. Huge table.png\|800px]]</center>
-	[[File:Displaying Data in the NSTableViews. Huge table.png\|800px]]	+
-		+
	</div>		</div>

Line 120:		Line 118:

	That’s all. Now we can edit data inside the ''NSTableView'' control and they will be written directly to our data table.		That’s all. Now we can edit data inside the ''NSTableView'' control and they will be written directly to our data table.
		+
		+	<center>[[File:Displaying data in the NSTableView.Editing Data.png]]</center>

File:Displaying Data in the NSTableViews. Huge table.png

2012-05-15T18:53:13Z

uploaded "[[File:Displaying Data in the NSTableViews. Huge table.png]]"

Displaying Data in NSTableViews

2012-05-15T18:52:53Z

← Older revision		Revision as of 18:52, 15 May 2012
Line 86:		Line 86:
	<center>[[File:Displaying Data in the NSTableViews. Making connection.png\|800px]]</center>		<center>[[File:Displaying Data in the NSTableViews. Making connection.png\|800px]]</center>

-	<div id="note">	+	<div class="note">
	This approach you can see in many of our samples. It is quite simple to do, and at the same time, its very efficient. Your data source can have thousands of rows but table view will still be quick and without lags.		This approach you can see in many of our samples. It is quite simple to do, and at the same time, its very efficient. Your data source can have thousands of rows but table view will still be quick and without lags.
		+
		+	For example, NSTableView on following screen contains about 45K! rows
		+
		+	[[File:Displaying Data in the NSTableViews. Huge table.png\|800px]]

	</div>		</div>
Line 94:		Line 98:


-	Our next task is to do NSTableView editable. Its quite simple, we just need to implement one more method of the NSTableViewDataSourceProtocol which can set new value for given row and given column for our dataSource object.	+	Our next task is to do ''NSTableView'' editable. Its quite simple, we just need to implement one more method of the ''NSTableViewDataSourceProtocol'' which can set new value for given row and given column for our ''dataSource'' object.

	<source lang="objc">		<source lang="objc">
Line 115:		Line 119:
	</source>		</source>

-	That’s all. Now we can edit data inside the NSTableView control and they will be written directly to our data table.	+	That’s all. Now we can edit data inside the ''NSTableView'' control and they will be written directly to our data table.

File:Displaying Data in the NSTableViews. Making connection.png

2012-05-15T18:24:28Z

uploaded "[[File:Displaying Data in the NSTableViews. Making connection.png]]"

Displaying Data in NSTableViews

2012-05-15T18:22:15Z

← Older revision		Revision as of 18:22, 15 May 2012
Line 11:		Line 11:
	Summary = This topic goes in detail into using NSTableViews to display tabular data on the Mac OS X		Summary = This topic goes in detail into using NSTableViews to display tabular data on the Mac OS X
	-->		-->
-	~~=Displaying Data in NSTableViews=~~

	Presenting tabular data is the one of the most common scenarios in the programming.		Presenting tabular data is the one of the most common scenarios in the programming.
Line 53:		Line 52:
	Note, that method above takes certain NSDataTableColumn of the NSTableView as the parameter. At the design time we can store there binded field name as the column identifier.		Note, that method above takes certain NSDataTableColumn of the NSTableView as the parameter. At the design time we can store there binded field name as the column identifier.

-	[[File:Displaying data in the NSTableView.Column Identifier.png]]	+	<center>[[File:Displaying data in the NSTableView.Column Identifier.png\|800px]]</center>

	Later inside this method we can get it back and use as the key for obtaining value from given row.		Later inside this method we can get it back and use as the key for obtaining value from given row.
Line 85:		Line 84:
	Finally make the connection between the UI controls and outlets in the code		Finally make the connection between the UI controls and outlets in the code

-	[[File:Displaying Data in NSTableViews. Making connection.png]]	+	<center>[[File:Displaying Data in the NSTableViews. Making connection.png\|800px]]</center>

	<div id="note">		<div id="note">

File:Displaying data in the NSTableView.Column Identifier.png

2012-05-15T18:19:14Z

uploaded "[[File:Displaying data in the NSTableView.Column Identifier.png]]"

Displaying Data in NSTableViews

2012-05-15T18:17:55Z

Created page with '{{ArticleTopic|Data Abstract|Xcode}} {{PageQuality|good}} __NOEDITSECTION__ __NOTOC__ <!--MetaData Products = DA Editions = Xcode Platforms = Categories = Displaying Data Concep...'

New page

{{ArticleTopic|Data Abstract|Xcode}}
{{PageQuality|good}}
__NOEDITSECTION__
__NOTOC__

=Displaying Data in NSTableViews=

Presenting tabular data is the one of the most common scenarios in the programming.
Cocoa offers nice control - ''NSTableView'' for this and offers several approaches of work with it.
One way is using ''Cocoa Binding'' technology and other is providing special delegate object as the ''dataSource'' property for ''NSTableView''.
In this article we will describe the second approach.

== Displaying data ==

''NSTableView'' has dataSource property which can take a reference to an object that conforms to ''NSTableViewDataSource'' informal protocol. In order to show the data our delegate need to implement several methods which will be used by the ''NSTableView''.

One of them should return count of rows in our ''DADataTable''.

<source lang="objc">
- (NSInteger)numberOfRowsInTableView:(NSTableView *)tableView {

if (workersTable == nil)
return 0;

return [[workersTable rows] count];
}
</source>

And other should returns object for given row and column from the data source. NSTableView will use this dataSource delegate for getting data it need to show to the user.

<source lang="objc">

- (id) tableView:(NSTableView *)tableView
objectValueForTableColumn:(NSTableColumn *)column
row:(NSInteger)rowIndex {

if ((workersTable == nil) || ([[column identifier] length] == 0))
return nil;

DADataTableRow *row = [[workersTable rows] objectAtIndex:rowIndex];
return [row valueForKey:[column identifier]];
}

</source>

Note, that method above takes certain NSDataTableColumn of the NSTableView as the parameter. At the design time we can store there binded field name as the column identifier.

[[File:Displaying data in the NSTableView.Column Identifier.png]]

Later inside this method we can get it back and use as the key for obtaining value from given row.

Now its time to setup the ''NSTableView''. Add it as the outlet. Also note that our controller respond to ''NSTableViewDataSource'' protocol

<source lang="objc">

@interface MainWindowController : NSWindowController <NSTableViewDataSource> {
...
IBOutlet NSTableView *tableView;
DADataTable *workersTable;
}
@end

</source>

and set its dataSource property. The good place to do that is the AvakeFromNib method.

<source lang="objc">

- (void) awakeFromNib {

...
[tableView setDataSource:self];
}

</source>

Finally make the connection between the UI controls and outlets in the code

[[File:Displaying Data in NSTableViews. Making connection.png]]

<div id="note">
This approach you can see in many of our samples. It is quite simple to do, and at the same time, its very efficient. Your data source can have thousands of rows but table view will still be quick and without lags.

</div>

== Editing data ==

Our next task is to do NSTableView editable. Its quite simple, we just need to implement one more method of the NSTableViewDataSourceProtocol which can set new value for given row and given column for our dataSource object.

<source lang="objc">

- (void) tableView:(NSTableView *)tableView
setObjectValue:(id)value
forTableColumn:(NSTableColumn *)column
row:(NSInteger)rowIndex {

NSString *identifier = [column identifier];
if ([identifier length] == 0)
return;

DADataTableRow *row = [[workersTable rows] objectAtIndex:rowIndex];
[row setValue:value
forKey:identifier];

}

</source>

That’s all. Now we can edit data inside the NSTableView control and they will be written directly to our data table.

Business Rules Scripting Overview

2012-05-15T05:38:01Z

← Older revision		Revision as of 05:38, 15 May 2012
(One intermediate revision not shown)
Line 9:		Line 9:
	Concepts = Business Rules Scripting		Concepts = Business Rules Scripting
	Interfaces =		Interfaces =
-	Classes = EcmaScriptProvider, ~~TDAEcmaScriptProvider~~	+	Classes = EcmaScriptProvider, TDASpiderMonkeyScriptProvider
	Summary = A brief overview of the Business Rules Scripting feature		Summary = A brief overview of the Business Rules Scripting feature
	-->		-->
Line 32:		Line 32:

	{{Delphi}}		{{Delphi}}
-	If you use Delphi, you simply need to place the {{class\|~~TDAEcmaScriptProvider~~}} on the Data Abstract service and assign the {{bold\|ScriptProvider}} property on the service to the new component (for server scripting), or place the same class next to the data table(s) ({{class\|TDAMemDataTable}} class) and assign the {{bold\|ScriptingProvider}} property on that component to the ~~[[EcmaScriptProvider Class]]~~ (for client scripting).	+	If you use Delphi, you simply need to place the {{class\|TDASpiderMonkeyScriptProvider}} on the Data Abstract service and assign the {{bold\|ScriptProvider}} property on the service to the new component (for server scripting), or place the same class next to the data table(s) ({{class\|TDAMemDataTable}} class) and assign the {{bold\|ScriptingProvider}} property on that component to the {{class\|TDASpiderMonkeyScriptProvider}} (for client scripting).

	{{Xcode}}		{{Xcode}}
Line 38:		Line 38:

	== Script Editor ==		== Script Editor ==
-	[[Schema Modeler]] includes support for creating and editing business rules scripts, both in [[Schema Modeler for Windows]] and [[Server Explorer (Xcode (Mac))]]. On Windows, the script editor can be brought up by clicking the "Business Rules" button in the Data Table toolbar, which brings up a dedicated editor window:	+	[[Schema Modeler]] includes support for creating and editing business rules scripts, both in [[Schema Modeler 7 for Windows]] and [[Server Explorer (Xcode (Mac))]]. On Windows, the script editor can be brought up by clicking the "Business Rules" button in the Data Table toolbar, which brings up a dedicated editor window:

	[[File:Business Rules Editor.png\|Business Rules Editor]]		[[File:Business Rules Editor.png\|Business Rules Editor]]
Line 192:		Line 192:

	2. Declare the function above as custom function:		2. Declare the function above as custom function:
-	~~DAEcmaScriptProvider1~~.Engine.Variables.SetVariable('Base64GUID', Base64GUID);	+	DASpiderMonkeyScriptProvider1.Engine.Variables.SetVariable('Base64GUID', Base64GUID);

	3. Use the custom function Base64GUID() in Business Rules editor. For example, on the client side, the custom function can be used in the onNewRow event like this:		3. Use the custom function Base64GUID() in Business Rules editor. For example, on the client side, the custom function can be used in the onNewRow event like this:
Line 203:		Line 203:
	CustomValue := 10;		CustomValue := 10;

-	~~DAEcmaScriptProvider1~~.Engine.Variables.SetVariable('CustomVariable',CustomValue);	+	DASpiderMonkeyScriptProvider1.Engine.Variables.SetVariable('CustomVariable',CustomValue);

	{{bold\|Note:}} Arguments are passed in inverted order. So calling MyFunc(val1, val2, val3) you get args[0]=val3, args[1]=val2 and args[2]=val1		{{bold\|Note:}} Arguments are passed in inverted order. So calling MyFunc(val1, val2, val3) you get args[0]=val3, args[1]=val2 and args[2]=val1
Line 213:		Line 213:
	* [[Data Abstract Scripting Events]]		* [[Data Abstract Scripting Events]]
	* {{class\|EcmaScriptProvider}}		* {{class\|EcmaScriptProvider}}
-	* {{class\|~~TDAEcmaScriptProvider~~}}	+	* {{class\|TDASpiderMonkeyScriptProvider}}

Adding a Second Data Service to your Data Abstract Server (.NET)

2012-05-14T13:38:15Z

← Older revision		Revision as of 13:38, 14 May 2012
(2 intermediate revisions not shown)
Line 1:		Line 1:
	{{HowToTopic\|Data Abstract}}		{{HowToTopic\|Data Abstract}}
	{{PageQuality\|good}}		{{PageQuality\|good}}
-	{{~~wip~~}}	+	{{wipt}}
		+	__NOEDITSECTION__
	__NOTOC__		__NOTOC__
	<!--MetaData		<!--MetaData
Line 76:		Line 77:
	Now the service knows how to read and write data but it still doesn't know what data it should serve.		Now the service knows how to read and write data but it still doesn't know what data it should serve.

-	You need to set the {{bold\|ServiceSchemaName}} property. It should contain the name of one of the server's .daSchema [[Schema]] files.	+	You need to set the {{bold\|ServiceSchemaName}} property. It should contain the name of one of the server's .daSchema [[Schemas\|Schema]] files.

	<center>		<center>
	[[File:Adding a Second Data Service - 04 - Service Schema Name.png]]		[[File:Adding a Second Data Service - 04 - Service Schema Name.png]]
	</center>		</center>
-

	==== Service Connection ====		==== Service Connection ====

File:Adding a Second Data Service - 04 - Service Schema Name.png

2012-05-14T13:37:08Z

uploaded "[[File:Adding a Second Data Service - 04 - Service Schema Name.png]]"

File:Adding a Second Data Service - 04 - Data Streamer.png

2012-05-14T13:34:08Z

uploaded a new version of "[[File:Adding a Second Data Service - 04 - Data Streamer.png]]"

File:Adding a Second Data Service - 04 - Data Streamer.png

2012-05-14T13:31:43Z

uploaded "[[File:Adding a Second Data Service - 04 - Data Streamer.png]]"

Adding a Second Data Service to your Data Abstract Server (.NET)

2012-05-14T13:21:21Z

Data Streamer:

← Older revision		Revision as of 13:21, 14 May 2012
(One intermediate revision not shown)
Line 46:		Line 46:

	<center>		<center>
-	[[File:Adding a Second Data Service - 01 - ~~Defining~~ Service.png\|600px]]	+	[[File:Adding a Second Data Service - 02 - New Service.png\|600px]]
	</center>		</center>

	Now close the Service Builder. Service interface and invoker files will be regenerated automatically to reflect RODL changes and new _Impl file will be added to the server project		Now close the Service Builder. Service interface and invoker files will be regenerated automatically to reflect RODL changes and new _Impl file will be added to the server project
-

	=== Step 2. Service settings ===		=== Step 2. Service settings ===
Line 63:		Line 62:
	Drag Data Streamer component from the Visual Studio toolbox to the service design pane		Drag Data Streamer component from the Visual Studio toolbox to the service design pane

-	<~~pic here~~ >	+	<center>
		+	[[File:Adding a Second Data Service - 03 - Data Streamer.png]]
		+	</center>

	Point the service property {{bold\|ServiceDataStreamer}} to the recently added Data Streamer instance		Point the service property {{bold\|ServiceDataStreamer}} to the recently added Data Streamer instance

	<center>		<center>
-	[[File:Adding a Second Data Service - 03 - Data Streamer.png]]	+	[[File:Adding a Second Data Service - 04 - Data Streamer.png]]
	</center>		</center>
-

	==== Service Schema ====		==== Service Schema ====

File:Adding a Second Data Service - 02 - New Service.png

2012-05-14T13:19:30Z

uploaded "[[File:Adding a Second Data Service - 02 - New Service.png]]"

Adding a Second Data Service to your Data Abstract Server (.NET)

2012-05-14T13:17:18Z

Service Properties:

← Older revision		Revision as of 13:17, 14 May 2012
Line 100:		Line 100:

	<center>		<center>
-	[[File:Adding a Second Data Service - 04 - Service Properties.png~~\|600px~~]]	+	[[File:Adding a Second Data Service - 04 - Service Properties.png]]
	</center>		</center>


	That's it. New Data access service is defined and is fully functional.		That's it. New Data access service is defined and is fully functional.
-

	=== Step 3. Testing new service ===		=== Step 3. Testing new service ===

File:Adding a Second Data Service - 04 - Service Properties.png

2012-05-14T13:16:58Z

uploaded a new version of "[[File:Adding a Second Data Service - 04 - Service Properties.png]]"

File:Adding a Second Data Service - 04 - Service Properties.png

2012-05-14T13:15:56Z

uploaded "[[File:Adding a Second Data Service - 04 - Service Properties.png]]"

Installing RemObjects SDK for Delphi

2012-05-14T13:11:14Z

deleted "[[Installing RemObjects SDK for Delphi]]" content was: '#REDIRECT WIP:Installing RemObjects SDK for Delphi' (and the only contributor was 'Vyacheslavd')

File:Adding a Second Data Service - 05 - Wizard Dialog.png

2012-05-14T13:08:09Z

uploaded "[[File:Adding a Second Data Service - 05 - Wizard Dialog.png]]"

Adding a Second Data Service to your Data Abstract Server (.NET)

2012-05-14T13:07:21Z

Step 3. Testing new service:

← Older revision		Revision as of 13:07, 14 May 2012
Line 115:		Line 115:
	Open the New Project dialog and select one of the templates shipped with Data Abstract.		Open the New Project dialog and select one of the templates shipped with Data Abstract.

-	New Project Wizard dialog will appear. Select the 'Client for an existing custom Data ~~abstract~~ Server' project type	+	New Project Wizard dialog will appear. Select the {{bold\|Client for an existing custom Data Abstract Server}} project type

	<center>		<center>
Line 138:		Line 138:

	These two Wizard steps prove that service is defined and is accessible by client applications.		These two Wizard steps prove that service is defined and is accessible by client applications.
-
-

	== Summary ==		== Summary ==

Relativity Server User Access Levels

2012-05-14T13:06:31Z

← Older revision		Revision as of 13:06, 14 May 2012
Line 1:		Line 1:
	{{ProductTopic\|Data Abstract\|Relativity Server}}		{{ProductTopic\|Data Abstract\|Relativity Server}}

		+	__NOEDITSECTION__
	__TOC__		__TOC__

LoginEx

2012-05-14T13:05:56Z

← Older revision		Revision as of 13:05, 14 May 2012
Line 12:		Line 12:
	Summary =		Summary =
	-->		-->
-		+	__NOEDITSECTION__
	__TOC__		__TOC__

Adding a Second Data Service to your Data Abstract Server (.NET)

2012-05-14T13:05:30Z

← Older revision		Revision as of 13:05, 14 May 2012
Line 2:		Line 2:
	{{PageQuality\|good}}		{{PageQuality\|good}}
	{{wip}}		{{wip}}
-	~~__NOEDITSECTION__~~
	__NOTOC__		__NOTOC__
	<!--MetaData		<!--MetaData

File:Adding a Second Data Service - 06 - Wizard Service Name.png

2012-05-14T13:04:54Z

uploaded "[[File:Adding a Second Data Service - 06 - Wizard Service Name.png]]"

Adding a Second Data Service to your Data Abstract Server (.NET)

2012-05-14T12:57:22Z

← Older revision		Revision as of 12:57, 14 May 2012
(2 intermediate revisions not shown)
Line 19:		Line 19:
	Most common are:		Most common are:
	* Some data should be accessible without login (f.e. in read-only mode)		* Some data should be accessible without login (f.e. in read-only mode)
-	* Data subset has to be public accessible via [[OData]] or [[REST]]	+	* Data subset has to be public accessible via [[OData Publishing (.NET)\|OData]] or [[REST Overview\|REST]]
	* Some data should be accessible only via Local Data Adapter		* Some data should be accessible only via Local Data Adapter
-	* Data shold be served using different [[Data Streamers]] (f.e. efficient [[Bin2]] data streamer should be used for requests made by Data Abstract-based client applications while less efficient [[JSON]] data streamer could provide data for third-party based Java Script client app)	+	* Data shold be served using different Data Streamers (f.e. efficient [[Bin2DataStreamer\|Bin2]] data streamer should be used for requests made by Data Abstract-based client applications while less efficient [[JSON]] data streamer could provide data for third-party based Java Script client app)
	* Different subsets of data should be accessible by different users (f.e. ordinal data and user management data)		* Different subsets of data should be accessible by different users (f.e. ordinal data and user management data)
	* etc...		* etc...
Line 40:		Line 40:
	Service Builder will start.		Service Builder will start.

-	<~~< pic here~~ >>	+	<center>
		+	[[File:Adding a Second Data Service - 01 - Service Builder.png\|600px]]
		+	</center>

-	Now select library and press the Service button. New Service definition will be added to the RODL.	+	Now select library and press the Service button. New Service definition will be added to the RODL. Set its ancestor to {{bold\|DataAbstractService}}.

-	<~~pic here~~>	+	<center>
-		+	[[File:Adding a Second Data Service - 01 - Defining Service.png\|600px]]
-	~~Set its ancestor to DataAbstractService~~	+	</center>
-		+
-	<~~pic here~~>	+

	Now close the Service Builder. Service interface and invoker files will be regenerated automatically to reflect RODL changes and new _Impl file will be added to the server project		Now close the Service Builder. Service interface and invoker files will be regenerated automatically to reflect RODL changes and new _Impl file will be added to the server project
Line 56:		Line 56:

	At this moment Data service is defined, but it is still not usable and any attempt to access it will fail with an exception. Several service properties should be set to make it usable.		At this moment Data service is defined, but it is still not usable and any attempt to access it will fail with an exception. Several service properties should be set to make it usable.
		+

	==== Data Streamer ====		==== Data Streamer ====
Line 67:		Line 68:
	Point the service property {{bold\|ServiceDataStreamer}} to the recently added Data Streamer instance		Point the service property {{bold\|ServiceDataStreamer}} to the recently added Data Streamer instance

-	<~~< pic here~~ >>	+	<center>
		+	[[File:Adding a Second Data Service - 03 - Data Streamer.png]]
		+	</center>


Line 76:		Line 79:
	You need to set the {{bold\|ServiceSchemaName}} property. It should contain the name of one of the server's .daSchema [[Schema]] files.		You need to set the {{bold\|ServiceSchemaName}} property. It should contain the name of one of the server's .daSchema [[Schema]] files.

-	<~~< pic here~~ >>	+	<center>
		+	[[File:Adding a Second Data Service - 04 - Service Schema Name.png]]
		+	</center>


Line 95:		Line 100:
	In most cases the only service property that needs attention is {{bold\|RequireSession}}. Set it to {{bold\|true}} if access to the service should be restricted to logged-in users only.		In most cases the only service property that needs attention is {{bold\|RequireSession}}. Set it to {{bold\|true}} if access to the service should be restricted to logged-in users only.

-	<~~<pic here~~>>	+	<center>
		+	[[File:Adding a Second Data Service - 04 - Service Properties.png\|600px]]
		+	</center>


Line 111:		Line 118:
	New Project Wizard dialog will appear. Select the 'Client for an existing custom Data abstract Server' project type		New Project Wizard dialog will appear. Select the 'Client for an existing custom Data abstract Server' project type

-	<~~pic~~>	+	<center>
		+	[[File:Adding a Second Data Service - 05 - Wizard Dialog.png\|600px]]
		+	</center>

	Set the server application url and press the {{bold\|Next}} button.		Set the server application url and press the {{bold\|Next}} button.
Line 117:		Line 126:
	At this step you should see the recently added Data access service name as one of the possible values in the {{bold\|DataAssess Service name}} combobox.		At this step you should see the recently added Data access service name as one of the possible values in the {{bold\|DataAssess Service name}} combobox.

-	<~~pic here~~ >	+	<center>
		+	[[File:Adding a Second Data Service - 06 - Wizard Service Name.png\|600px]]
		+	</center>

	Select this service, provide user name and password if needed and press the {{bold\|Next}} button.		Select this service, provide user name and password if needed and press the {{bold\|Next}} button.
Line 123:		Line 134:
	On the next step service schema should appear. The New Project Wizard will load using the recently added Data access service.		On the next step service schema should appear. The New Project Wizard will load using the recently added Data access service.

-	<~~< pic~~ >>	+	<center>
		+	[[File:Adding a Second Data Service - 07 - Wizard Service Schema.png\|600px]]
		+	</center>

	These two Wizard steps prove that service is defined and is accessible by client applications.		These two Wizard steps prove that service is defined and is accessible by client applications.