start
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
start [2016/06/25 14:42] chrisgerken created |
start [2017/01/16 21:38] (current) chrisgerken [Eclipse Support] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Okay, we admit it. There is a code generation component to Gramar. With Gramar you can capture repeatable software architectures and generate (historically speaking) upwards of 95% of a deployable application's implementation (code, config files, HTML and wiki pages, unit test cases, etc.). But that's just the shiny object in the room. The real value in using Gramar is that it gives you a way to formally and explicitly describe to others how you want your software built. | + | ===== Grammatical Architectures ===== |
| + | |||
| + | So what if there's a code generation component to Gramar? With a [[Gramar_Defined|gramar]] you can capture repeatable software architectures and generate (historically speaking) upwards of 95% of a deployable application's implementation (code, config files, <nowiki>HTML</nowiki> and wiki pages, unit test cases, etc.). But that's just the shiny object in the room. The real value in using Gramar is that it gives you a way to formally and explicitly describe to others how you want your software built. | ||
| Gramar is a tool that helps software architects describe their architectures in the most consumable form possible: tools that generate the code they care about while leaving developers the freedom to develop the business logic that the developers care about. | Gramar is a tool that helps software architects describe their architectures in the most consumable form possible: tools that generate the code they care about while leaving developers the freedom to develop the business logic that the developers care about. | ||
| Line 11: | Line 13: | ||
| Read about the [[Gramar_Development_Process]]. | Read about the [[Gramar_Development_Process]]. | ||
| - | === Background === | + | ==== Background ==== |
| Gramar is a next-generation greenfield implementation of Eclipse Model-to-Text JET and, before that, the Design Pattern Toolkit from IBM. A gramar can be applied not just in Eclipse, but in IntelliJ, as a stand-alone java application, within a web application or in any other environment with a Java runtime. | Gramar is a next-generation greenfield implementation of Eclipse Model-to-Text JET and, before that, the Design Pattern Toolkit from IBM. A gramar can be applied not just in Eclipse, but in IntelliJ, as a stand-alone java application, within a web application or in any other environment with a Java runtime. | ||
| - | == Getting started == | + | ==== Getting started ==== |
| * [[http://github.com/chrisgerken/gramar|Source code]] | * [[http://github.com/chrisgerken/gramar|Source code]] | ||
| - | * [[https://github.com/chrisGerken/gramar/wiki|Development Wiki]] | + | * [[org.gramar.base:index|Base Gramar tags and XPath functions]] |
| - | * [[https://github.com/chrisGerken/gramar/wiki/Extension-org.gramar.base|Base Gramar tags and XPath functions]] | + | |
| * [[http://gramar.org/javadoc/v1.0.0/index.html|Latest Gramar Javaoc]] | * [[http://gramar.org/javadoc/v1.0.0/index.html|Latest Gramar Javaoc]] | ||
| + | * [[gramars|Open source gramars]] | ||
| + | * [[techniques|Techniques]] | ||
| - | === Eclipse Support === | + | ==== Eclipse Support ==== |
| - | There are several Eclipse plugins providing support for Gramar in Eclipse. To install those plugins, | + | As of the latest release of Eclipse support for Gramar, there is only one plugin to load for full Eclipse support. We've also learned the hard way that as Eclipse 3.8 doesn't really play well with Java 1.8, it's probably best to work with Eclipse Neon and Java 1.8. |
| + | |||
| + | To install Gramar into Eclipse Neon... | ||
| * In Eclipse, goto `Help -> Install new software...` | * In Eclipse, goto `Help -> Install new software...` | ||
| - | * **Add...** a new update site with the URL '''http://gramar.org/eclipse/gramar''' | + | * **Add...** a new update site with the <nowiki> URL http://gramar.org/eclipse/gramar </nowiki> |
| - | * Install all features on the site. | + | * Install all features on the site (ought to be just one for now). |
| - | * Repeat with update site URL '''http://gramar.org/eclipse/xaa''' | + | * Restart Eclipse. |
| + | |||
| + | Note that there is a known problem getting started in general with Eclipse on Ubuntu. Details can be found [[http://askubuntu.com/questions/761604/eclipse-not-working-in-16-04|here]]. | ||
| + | ==== Walkthroughs ==== | ||
| + | |||
| + | There is an end-to-end [[org.gramar.storm.gramar:walkthrough|walkthrough]] for a gramar that generates almost 98% of the complete implementation of an Apache Storm topology. | ||
| + | |||
| + | More walkthroughs for other gramars are coming soon. | ||
| + | |||
| + | ==== Gramar in Maven Central Repository ==== | ||
| - | == Coming soon == | + | Version 1.0.0 of gramar is now in the maven central repo. In order to access gramar function from within your Java code or gramar, use: |
| - | * Better HTML doc for the base tags and functions | + | <code> |
| - | * Gramar as a versioned maven artifact | + | <dependency> |
| + | <groupId>org.gramar</groupId> | ||
| + | <artifactId>gramar</artifactId> | ||
| + | <version>1.0.0</version> | ||
| + | </dependency> | ||
| + | </code> | ||
| + | For more information, see [[http://search.maven.org/#artifactdetails%7Corg.gramar%7Cgramar%7C1.0.0%7Cjar|org.gramar:gramar:1.0.0]] | ||
start.1466865760.txt.gz · Last modified: 2016/06/25 14:42 by chrisgerken
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
