This is an automated email from the ASF dual-hosted git repository.
spmallette pushed a commit to branch TINKERPOP-2002
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
The following commit(s) were added to refs/heads/TINKERPOP-2002 by this push:
new 1a210ff TINKERPOP-2002 Resized and removed rexster images in
"connection" sections
1a210ff is described below
commit 1a210ffc7c4f7e2e21e43c8992e1a50e909f896d
Author: Stephen Mallette <sp...@genoprime.com>
AuthorDate: Tue Nov 13 13:29:14 2018 -0500
TINKERPOP-2002 Resized and removed rexster images in "connection" sections
---
docs/src/reference/gremlin-applications.asciidoc | 2 +-
docs/src/reference/gremlin-variants.asciidoc | 30 +++++++++++-------------
2 files changed, 15 insertions(+), 17 deletions(-)
diff --git a/docs/src/reference/gremlin-applications.asciidoc
b/docs/src/reference/gremlin-applications.asciidoc
index 83424c7..499416b 100644
--- a/docs/src/reference/gremlin-applications.asciidoc
+++ b/docs/src/reference/gremlin-applications.asciidoc
@@ -520,7 +520,7 @@ executing. It is up to the script to properly commit or
rollback transactions i
[[connecting-via-drivers]]
=== Connecting via Drivers
-image:rexster-connect.png[width=400,float=right] TinkerPop offers client-side
drivers for the Gremlin Server websocket
+image:rexster-connect.png[width=180,float=right] TinkerPop offers client-side
drivers for the Gremlin Server websocket
sub-protocol in a variety of languages:
* <<gremlin-dotnet,C#>>
diff --git a/docs/src/reference/gremlin-variants.asciidoc
b/docs/src/reference/gremlin-variants.asciidoc
index a19222a..0c5c107 100644
--- a/docs/src/reference/gremlin-variants.asciidoc
+++ b/docs/src/reference/gremlin-variants.asciidoc
@@ -100,10 +100,9 @@ connection methods described in the
<<connecting-gremlin,Connecting Gremlin>> Se
=== Connecting
-image:rexster-connect.png[width=400,float=left] The pattern for connecting is
described in
-<<connecting-gremlin,Connecting Gremlin>> and it basically distills down to
creating a `GraphTraversalSource`.
-For <<connecting-embedded,embedded>> mode, this involves first creating a
`Graph` and then spawning the
-`GraphTraversalSource`:
+The pattern for connecting is described in <<connecting-gremlin,Connecting
Gremlin>> and it basically distills down
+to creating a `GraphTraversalSource`. For <<connecting-embedded,embedded>>
mode, this involves first creating a
+`Graph` and then spawning the `GraphTraversalSource`:
[source,java]
----
@@ -616,10 +615,9 @@ pip install gremlinpython
=== Connecting
-image:rexster-connect.png[width=400,float=left] The pattern for connecting is
described in
-<<connecting-gremlin,Connecting Gremlin>> and it basically distills down to
creating a `GraphTraversalSource`. A
-`GraphTraversalSource` is created from the anonymous `traversal()` method
where the "g" provided to the
-`DriverRemoteConnection` corresponds to the name of a `GraphTraversalSource`
on the remote end.
+The pattern for connecting is described in <<connecting-gremlin,Connecting
Gremlin>> and it basically distills down to
+creating a `GraphTraversalSource`. A `GraphTraversalSource` is created from
the anonymous `traversal()` method where
+the "g" provided to the `DriverRemoteConnection` corresponds to the name of a
`GraphTraversalSource` on the remote end.
[source,python]
g =
traversal().withRemote(DriverRemoteConnection('ws://localhost:8182/gremlin','g'))
@@ -965,10 +963,10 @@ nuget install Gremlin.Net
=== Connecting
-image:rexster-connect.png[width=400,float=left] The pattern for connecting is
described in
-<<connecting-gremlin,Connecting Gremlin>> and it basically distills down to
creating a `GraphTraversalSource`. A
-`GraphTraversalSource` is created from the
`AnonymousTraversalSource.traversal()` method where the "g" provided to
-the `DriverRemoteConnection` corresponds to the name of a
`GraphTraversalSource` on the remote end.
+The pattern for connecting is described in <<connecting-gremlin,Connecting
Gremlin>> and it basically distills down to
+creating a `GraphTraversalSource`. A `GraphTraversalSource` is created from
the `AnonymousTraversalSource.traversal()`
+method where the "g" provided to the `DriverRemoteConnection` corresponds to
the name of a `GraphTraversalSource` on
+the remote end.
[source,csharp]
----
@@ -1223,10 +1221,10 @@ npm install gremlin
=== Connecting
-image:rexster-connect.png[width=400,float=left] The pattern for connecting is
described in
-<<connecting-gremlin,Connecting Gremlin>> and it basically distills down to
creating a `GraphTraversalSource`.
-A `GraphTraversalSource` is created from the
`AnonymousTraversalSource.traversal()` method where the "g" provided to
-the `DriverRemoteConnection` corresponds to the name of a
`GraphTraversalSource` on the remote end.
+The pattern for connecting is described in <<connecting-gremlin,Connecting
Gremlin>> and it basically distills down to
+creating a `GraphTraversalSource`. A `GraphTraversalSource` is created from
the `AnonymousTraversalSource.traversal()`
+method where the "g" provided to the `DriverRemoteConnection` corresponds to
the name of a `GraphTraversalSource` on
+the remote end.
[source,javascript]
----
