Morph MORPH
SIGN IN SIGN UP
cefsharp / CefSharp UNCLAIMED

.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

0 0 118 C#
Normal View History Raw
Updated copyright year and made sure it used same format everywhere (#1966)
2017-03-05 23:44:37 +01:00
// Copyright © 2010-2017 The CefSharp Authors. All rights reserved.
Add copyright to CefSharp.Example
2015-08-03 10:41:29 +10:00
//
// Use of this source code is governed by a BSD-style license that can be found in the LICENSE file.
using System;
Serialize Dictionary type to V8 object (#2303) * Serialize Dictionary type to V8 object Handle Dictionary type, otherwise it will be treated as class/structs and cause exception. * Make the testcase covert IDictionary interface & ensure consistent bracket style.
2018-03-22 09:00:52 +08:00
using System.Collections;
JSB Add support for dynamic keyword (using ExpandoObject) As ExpandoObject implements IDictionary we can use it interchangeable with only minor breaking changes. Those expecting Dictionary<string, object> should change to IDictionary<string, object> or ExpandoObject for their param types This will also impact anyone who has implemented their own custom IBinder I'd suggest changing the type checking from explicitly checking Dictionary<string, object> to use Type.IsAssignableFrom or another method of comparison DefaultBinder binder has been updated to accommodate ExpandoObject (now being returned by ObjectsSerialization.cpp) Add new async binding for testing new assignment method Rewrite some of the async bound object tests to use await and let - modernize them
2017-12-21 13:00:36 +10:00
using System.Collections.Generic;
Add DebuggerHidden attribute so VS doesn't break when `Break on User-Unhandled Exceptions` is checked
2015-08-03 11:37:49 +10:00
using System.Diagnostics;
JSB Add support for dynamic keyword (using ExpandoObject) As ExpandoObject implements IDictionary we can use it interchangeable with only minor breaking changes. Those expecting Dictionary<string, object> should change to IDictionary<string, object> or ExpandoObject for their param types This will also impact anyone who has implemented their own custom IBinder I'd suggest changing the type checking from explicitly checking Dictionary<string, object> to use Type.IsAssignableFrom or another method of comparison DefaultBinder binder has been updated to accommodate ExpandoObject (now being returned by ObjectsSerialization.cpp) Add new async binding for testing new assignment method Rewrite some of the async bound object tests to use await and let - modernize them
2017-12-21 13:00:36 +10:00
using System.Text;
added examples for async bindings
2015-07-29 13:39:07 +02:00
using System.Threading;
namespace CefSharp.Example
{
public class AsyncBoundObject
{
Add DebuggerHidden attribute so VS doesn't break when `Break on User-Unhandled Exceptions` is checked
2015-08-03 11:37:49 +10:00
//We expect an exception here, so tell VS to ignore
[DebuggerHidden]
added examples for async bindings
2015-07-29 13:39:07 +02:00
public void Error()
{
throw new Exception("This is an exception coming from C#");
}
Add DebuggerHidden attribute so VS doesn't break when `Break on User-Unhandled Exceptions` is checked
2015-08-03 11:37:49 +10:00
//We expect an exception here, so tell VS to ignore
[DebuggerHidden]
added examples for async bindings
2015-07-29 13:39:07 +02:00
public int Div(int divident, int divisor)
{
return divident / divisor;
}
public string Hello(string name)
{
return "Hello " + name;
}
JSB Add support for dynamic keyword (using ExpandoObject) As ExpandoObject implements IDictionary we can use it interchangeable with only minor breaking changes. Those expecting Dictionary<string, object> should change to IDictionary<string, object> or ExpandoObject for their param types This will also impact anyone who has implemented their own custom IBinder I'd suggest changing the type checking from explicitly checking Dictionary<string, object> to use Type.IsAssignableFrom or another method of comparison DefaultBinder binder has been updated to accommodate ExpandoObject (now being returned by ObjectsSerialization.cpp) Add new async binding for testing new assignment method Rewrite some of the async bound object tests to use await and let - modernize them
2017-12-21 13:00:36 +10:00
public string DoSomething()
added examples for async bindings
2015-07-29 13:39:07 +02:00
{
Thread.Sleep(1000);
JSB Add support for dynamic keyword (using ExpandoObject) As ExpandoObject implements IDictionary we can use it interchangeable with only minor breaking changes. Those expecting Dictionary<string, object> should change to IDictionary<string, object> or ExpandoObject for their param types This will also impact anyone who has implemented their own custom IBinder I'd suggest changing the type checking from explicitly checking Dictionary<string, object> to use Type.IsAssignableFrom or another method of comparison DefaultBinder binder has been updated to accommodate ExpandoObject (now being returned by ObjectsSerialization.cpp) Add new async binding for testing new assignment method Rewrite some of the async bound object tests to use await and let - modernize them
2017-12-21 13:00:36 +10:00
return "Waited for 1000ms before returning";
added examples for async bindings
2015-07-29 13:39:07 +02:00
}
Allow calling managed methods from objects bound with RegisterAsyncJsObject that return arrays of structs (#1981) * Fixed problem when calling CefV8Value::CreateArray. Needs prior call to V8 context enter * Call callback dispose in case of failure * Support serialization of struct arrays to JS side * Fixed formatting
2017-03-13 11:37:55 +00:00
JSB - Add support for async methods to return classes Structs and classes can now be returned from an async method Properties and fields are supported now. The returned class/struct is readonly effectively, no updates will be sent to the bound object. Just to clarify this is only for objects bound using RegisterAsyncJsObject
2018-01-08 15:12:52 +10:00
public JsSerializableStruct ReturnObject(string name)
Fix return value serialization for async JS bindings (#2167)
2017-10-23 14:24:04 +05:00
{
JSB - Add support for async methods to return classes Structs and classes can now be returned from an async method Properties and fields are supported now. The returned class/struct is readonly effectively, no updates will be sent to the bound object. Just to clarify this is only for objects bound using RegisterAsyncJsObject
2018-01-08 15:12:52 +10:00
return new JsSerializableStruct
Fix return value serialization for async JS bindings (#2167)
2017-10-23 14:24:04 +05:00
{
Value = name
};
}
Fix Async JSB unable to return class Added note about memory leak Added Test case to validate fix
2018-03-05 12:20:02 +10:00
public JsSerializableClass ReturnClass(string name)
{
return new JsSerializableClass
{
Value = name
};
}
JSB - Add support for async methods to return classes Structs and classes can now be returned from an async method Properties and fields are supported now. The returned class/struct is readonly effectively, no updates will be sent to the bound object. Just to clarify this is only for objects bound using RegisterAsyncJsObject
2018-01-08 15:12:52 +10:00
public JsSerializableStruct[] ReturnStructArray(string name)
Allow calling managed methods from objects bound with RegisterAsyncJsObject that return arrays of structs (#1981) * Fixed problem when calling CefV8Value::CreateArray. Needs prior call to V8 context enter * Call callback dispose in case of failure * Support serialization of struct arrays to JS side * Fixed formatting
2017-03-13 11:37:55 +00:00
{
return new[]
{
JSB - Add support for async methods to return classes Structs and classes can now be returned from an async method Properties and fields are supported now. The returned class/struct is readonly effectively, no updates will be sent to the bound object. Just to clarify this is only for objects bound using RegisterAsyncJsObject
2018-01-08 15:12:52 +10:00
new JsSerializableStruct { Value = name + "Item1" },
new JsSerializableStruct { Value = name + "Item2" }
};
}
public JsSerializableClass[] ReturnClassesArray(string name)
{
return new[]
{
new JsSerializableClass { Value = name + "Item1" },
new JsSerializableClass { Value = name + "Item2" }
Allow calling managed methods from objects bound with RegisterAsyncJsObject that return arrays of structs (#1981) * Fixed problem when calling CefV8Value::CreateArray. Needs prior call to V8 context enter * Call callback dispose in case of failure * Support serialization of struct arrays to JS side * Fixed formatting
2017-03-13 11:37:55 +00:00
};
}
JSB Add support for dynamic keyword (using ExpandoObject) As ExpandoObject implements IDictionary we can use it interchangeable with only minor breaking changes. Those expecting Dictionary<string, object> should change to IDictionary<string, object> or ExpandoObject for their param types This will also impact anyone who has implemented their own custom IBinder I'd suggest changing the type checking from explicitly checking Dictionary<string, object> to use Type.IsAssignableFrom or another method of comparison DefaultBinder binder has been updated to accommodate ExpandoObject (now being returned by ObjectsSerialization.cpp) Add new async binding for testing new assignment method Rewrite some of the async bound object tests to use await and let - modernize them
2017-12-21 13:00:36 +10:00
Dont discard null Values from arrays (#2218) * Don't discard arrays that contain null values * Revert unintended change in this branch * Added qunit test * Code review and added new tests
2018-01-18 01:46:58 +00:00
public string[] EchoArray(string[] arg)
{
return arg;
}
public int[] EchoValueTypeArray(int[] arg)
{
return arg;
}
public int[][] EchoMultidimensionalArray(int[][] arg)
{
return arg;
}
JSB Add support for dynamic keyword (using ExpandoObject) As ExpandoObject implements IDictionary we can use it interchangeable with only minor breaking changes. Those expecting Dictionary<string, object> should change to IDictionary<string, object> or ExpandoObject for their param types This will also impact anyone who has implemented their own custom IBinder I'd suggest changing the type checking from explicitly checking Dictionary<string, object> to use Type.IsAssignableFrom or another method of comparison DefaultBinder binder has been updated to accommodate ExpandoObject (now being returned by ObjectsSerialization.cpp) Add new async binding for testing new assignment method Rewrite some of the async bound object tests to use await and let - modernize them
2017-12-21 13:00:36 +10:00
public string DynamiObjectList(IList<dynamic> objects)
{
var builder = new StringBuilder();
foreach(var browser in objects)
{
builder.Append("Browser(Name:" + browser.Name + ";Engine:" + browser.Engine.Name + ");");
}
return builder.ToString();
}
Serialize Dictionary type to V8 object (#2303) * Serialize Dictionary type to V8 object Handle Dictionary type, otherwise it will be treated as class/structs and cause exception. * Make the testcase covert IDictionary interface & ensure consistent bracket style.
2018-03-22 09:00:52 +08:00
public Dictionary<string, int> MethodReturnsDictionary1()
{
return new Dictionary<string, int>()
{
{"five", 5},
{"ten", 10}
};
}
public Dictionary<string, object> MethodReturnsDictionary2()
{
return new Dictionary<string, object>()
{
{"onepointfive", 1.5},
{"five", 5},
{"ten", "ten"},
{"twotwo", new Int32[]{2, 2} }
};
}
public Dictionary<string, IDictionary> MethodReturnsDictionary3()
{
return new Dictionary<string, IDictionary>()
{
{"data", MethodReturnsDictionary2()}
};
}
added examples for async bindings
2015-07-29 13:39:07 +02:00
}
}
Reference in New Issue Copy Permalink