[
https://issues.apache.org/jira/browse/TINKERPOP-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15632322#comment-15632322
]
stephen mallette commented on TINKERPOP-1543:
---------------------------------------------
It's best to think of an archetype as a "template that works" - so a working
sample that someone could modify and turn into their own working code. It
sounds like this could fit that purpose. I've often thought an archetype of
Graph providers would be useful too, but the problem is that for the effort
involved there weren't enough Graph providers to really benefit.
Anyway, if you want to go the archetype route, which I think makes sense, I
would get most of your project fleshed out as a standalone project first (i.e.
get it working and near "done"), then translate it into a archetype and
test/debug the archetype. Archetype development can get a little tedious for
more complex projects because you aren't coding the code, you are writing a
template to be used later to build a project. So your first step should be
"working project" and then the second step is how best to template it.
I think archetypes are a very neat way to demonstrate a concept. It's like
working documentation that ends up being useful to a developer as an artifact.
> Create a distinct language archetype.
> -------------------------------------
>
> Key: TINKERPOP-1543
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1543
> Project: TinkerPop
> Issue Type: Improvement
> Components: documentation, language-variant
> Affects Versions: 3.2.3
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
>
> I want to do a "demo language" to show people how to create a language that
> compiles to Gremlin bytecode.
> I believe this should be done via the {{gremlin-archetype}} framework?? (cc/
> [~spmallette].
> The language would be the 2D "pipe" language discussed on gremlin-users@.
> List of potential names for the language:
> * GremlinDimensions
> * gThang
> * 2g
> * StraightG
> This archetype would include:
> 1. A language parser.
> 2. Connectivity to the process test suite.
> 3. Documentation.
> If [~spmallette] or [~dkuppitz] could set me up a branch with the "archetype"
> stubbed, that would be super helpful and I can then nerd out from there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
