This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
start [2016/06/26 17:05] chrisgerken |
start [2016/08/18 15:23] chrisgerken |
||
---|---|---|---|
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, <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. | + | ===== 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]] | * [[org.gramar.base:index|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, | There are several Eclipse plugins providing support for Gramar in Eclipse. To install those plugins, | ||
Line 30: | Line 33: | ||
* Install all features on the site. | * Install all features on the site. | ||
* Repeat with update site <nowiki> URL http://gramar.org/eclipse/xaa </nowiki> | * Repeat with update site <nowiki> URL http://gramar.org/eclipse/xaa </nowiki> | ||
+ | * Repeat with update site <nowiki> URL http://gramar.org/gramars/xaa </nowiki> | ||
+ | |||
+ | 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 ==== | ||
+ | |||
+ | 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: | ||
- | == Coming soon == | + | <code> |
+ | <dependency> | ||
+ | <groupId>org.gramar</groupId> | ||
+ | <artifactId>gramar</artifactId> | ||
+ | <version>1.0.0</version> | ||
+ | </dependency> | ||
+ | </code> | ||
- | * Better HTML doc for the base tags and functions | + | For more information, see [[http://search.maven.org/#artifactdetails%7Corg.gramar%7Cgramar%7C1.0.0%7Cjar|org.gramar:gramar:1.0.0]] |
- | * Gramar as a versioned maven artifact | + |