[ 
https://issues.apache.org/jira/browse/TINKERPOP-1552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683197#comment-15683197
 ] 

Florian Hockmann edited comment on TINKERPOP-1552 at 11/21/16 10:57 AM:
------------------------------------------------------------------------

I began working on a C# GLV and created a repository for that: 
[https://github.com/FlorianHockmann/Gremlin.CSharp]

If you want, I can give you commit rights to it so we can use that repository 
to work together on the GLV.

It is currently in a very early stage, especially tests and documentation are 
completely missing.

I also added an IRemoteConnection interface to Gremlin.Net that is basically 
the same as the python RemoteConnection interface. Gremlin.Net also includes 
(currently dummy) implementations for Bytecode and Traversal that should be the 
same for all .NET based GLVs and should therefore not be part of 
Gremlin.CSharp. You can see the current state in the [glvSupport 
branch|https://github.com/FlorianHockmann/Gremlin.Net/tree/glvSupport ], but 
IRemoteConnection is not implemented by a concrete class at the moment.

The complete implementation is currently not type-safe as it is much easier to 
implement that way, especially for the auto-generated steps. But at least for 
the driver / RemoteConnection part, it might be a good idea to change that and 
stay closer to the Java implementation. So the current IRemoteConnection 
interface is just a first draft.

Just wanted to give you a quick status update and provide a repository for 
collaboration.


was (Author: florian hockmann):
I began working on a C# GLV and created a repository for that: 
[https://github.com/FlorianHockmann/Gremlin.CSharp]

If you want, I can give you commit rights to it so we can use that repository 
to work together on the GLV.

It is currently in a very early stage, especially tests and documentation are 
completely missing.

I also added an IRemoteConnection interface to Gremlin.Net that is basically 
the same as the python RemoteConnection interface. Gremlin.Net also includes 
(currently dummy) implementations for Bytecode and Traversal that should be the 
same for all .NET based GLVs and should therefore not be part of 
Gremlin.CSharp. You can see the current state in the 
[https://github.com/FlorianHockmann/Gremlin.Net/tree/glvSupport glvSupport 
branch], but IRemoteConnection is not implemented by a concrete class at the 
moment.

The complete implementation is currently not type-safe as it is much easier to 
implement that way, especially for the auto-generated steps. But at least for 
the driver / RemoteConnection part, it might be a good idea to change that and 
stay closer to the Java implementation. So the current IRemoteConnection 
interface is just a first draft.

Just wanted to give you a quick status update and provide a repository for 
collaboration.

> C# Gremlin Language Variant
> ---------------------------
>
>                 Key: TINKERPOP-1552
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1552
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: language-variant
>    Affects Versions: 3.2.3
>            Reporter: Jorge Bay
>
> It would be nice to have a C# GLV that runs under .NET Framework 4.5+ and 
> .NET Core.
> The maven build could use the Exec Maven Plugin to exec .NET Core's [dotnet 
> test|https://www.microsoft.com/net/core#macos] command.
> Some requirements, from the mailing list (edited):
> {quote}
> 1. The GLV should keep in line with class/method names of the java API
> where possible to ensure consistency of feel across languages.
> 2. There needs to be adequate tests (we're still discussing the approach to
> testing GLVs and i think that needs to be tackled sooner than later as more
> GLVs start to come in). Those tests should produce xunit style output
> unless there is some good reason not to.
> 3. There needs to be adequate documentation (e.g. Reference docs)
> 4. The build/deploy process needs to be bound to maven which might be one of 
> the trickier bits to deal with.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to