Return-Path: X-Original-To: apmail-zest-commits-archive@minotaur.apache.org Delivered-To: apmail-zest-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9C017186B5 for ; Fri, 24 Jul 2015 21:18:03 +0000 (UTC) Received: (qmail 32533 invoked by uid 500); 24 Jul 2015 21:18:03 -0000 Delivered-To: apmail-zest-commits-archive@zest.apache.org Received: (qmail 32485 invoked by uid 500); 24 Jul 2015 21:18:03 -0000 Mailing-List: contact commits-help@zest.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zest.apache.org Delivered-To: mailing list commits@zest.apache.org Received: (qmail 32350 invoked by uid 99); 24 Jul 2015 21:18:02 -0000 Received: from eris.apache.org (HELO hades.apache.org) (140.211.11.105) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jul 2015 21:18:02 +0000 Received: from hades.apache.org (localhost [127.0.0.1]) by hades.apache.org (ASF Mail Server at hades.apache.org) with ESMTP id 7D75BAC1AA2 for ; Fri, 24 Jul 2015 21:18:02 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r1692588 [8/8] - in /zest/site/content: ./ java/develop/ Date: Fri, 24 Jul 2015 21:18:00 -0000 To: commits@zest.apache.org From: paulmerlin@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150724211802.7D75BAC1AA2@hades.apache.org> Modified: zest/site/content/java/develop/sample-swing.html URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/sample-swing.html?rev=1692588&r1=1692587&r2=1692588&view=diff ============================================================================== --- zest/site/content/java/develop/sample-swing.html (original) +++ zest/site/content/java/develop/sample-swing.html Fri Jul 24 21:17:59 2015 @@ -66,7 +66,7 @@ })(); -

Swing Bindings Sample

Sample of how to write custom binders.

Browse Source

This introduction will deepen your understanding of Zest™, as we touches on a couple of the common features of Zest™. It is expected that you have gone through and understood the "Zest™ in 10 minutes" introduction.

If you want to reproduce what’s explained in this tutorial, remember to depend on the Core Runtime artifact that depends -on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:

Table 3. Artifact

Group IDArtifact IDVersion

org.qi4j.core

org.qi4j.core.runtime

2.1-SNAPSHOT


Moreover, you’ll need an EntityStore for persistence and an Indexing engine for querying. Choose among the available +on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:

Table 3. Artifact

Group IDArtifact IDVersion

org.qi4j.core

org.qi4j.core.runtime

0


Moreover, you’ll need an EntityStore for persistence and an Indexing engine for querying. Choose among the available implementations listed in the Extensions section.

See the Depend on Zest™ in your build tutorial for details.

We will go back to the OrderEntity example;

@Concerns( { PurchaseLimitConcern.class, InventoryConcern.class } )
 public interface OrderEntity
     extends Order, Confirmable,

Modified: zest/site/content/java/develop/tools-envisage.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/tools-envisage.html?rev=1692588&r1=1692587&r2=1692588&view=diff
==============================================================================
--- zest/site/content/java/develop/tools-envisage.html (original)
+++ zest/site/content/java/develop/tools-envisage.html Fri Jul 24 21:17:59 2015
@@ -79,7 +79,7 @@ Visualizations can be printed to PDFs.

As you can see, Envisage operates on the ApplicationModel, this means that you can easily embedd it in your own Applications too.

Two gradle tasks runSample and runSchool are defined in this module as a -shortcut to run the examples. See Build System.

Screenshots

tools-envisage-structure.png

tools-envisage-type.png

tools-envisage-stacked.png

tools-envisage-stacked-collapsed.png

Embedd in your Application

Table 78. Artifact

Group IDArtifact IDVersion

org.qi4j.tool

org.qi4j.tool.envisage

2.1-SNAPSHOT


Screenshots

tools-envisage-structure.png

tools-envisage-type.png

tools-envisage-stacked.png

tools-envisage-stacked-collapsed.png

Embedd in your Application

Table 78. Artifact

Group IDArtifact IDVersion

org.qi4j.tool

org.qi4j.tool.envisage

0


Each tutorial step in this series starts with the result from the previous tutorial, so you can always look at the next tutorial step for guidance on what to do.

At the bottom of each tutorial step, the is Solutions section, which list the files you should have come to if you have followed the instructions.

If you want to reproduce what’s explained in this tutorial, remember to depend on the Core Runtime artifact that depends -on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:

Table 5. Artifact

Group IDArtifact IDVersion

org.qi4j.core

org.qi4j.core.runtime

2.1-SNAPSHOT


See the Depend on Zest™ in your build tutorial for details.

Step 1 - Interface Refactoring

Initial Hello World

This whole tutorial describes how to step-by-step modify a typical HelloWorld "application" into a full-fledged Zest™ +on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:

Table 5. Artifact

Group IDArtifact IDVersion

org.qi4j.core

org.qi4j.core.runtime

0


See the Depend on Zest™ in your build tutorial for details.

Step 1 - Interface Refactoring

Initial Hello World

This whole tutorial describes how to step-by-step modify a typical HelloWorld "application" into a full-fledged Zest™ Composite Oriented application. Here is the initial code of HelloWorld.

 /**
  * Initial HelloWorld implementation. Everything is mixed up

Modified: zest/site/content/java/develop/tut-services.html
URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/tut-services.html?rev=1692588&r1=1692587&r2=1692588&view=diff
==============================================================================
--- zest/site/content/java/develop/tut-services.html (original)
+++ zest/site/content/java/develop/tut-services.html Fri Jul 24 21:17:59 2015
@@ -80,7 +80,7 @@ activation and Configuration Entities ma
 

Each tutorial step in this series starts with the result from the previous tutorial, so you can always look at the next tutorial step for guidance on what to do.

At the bottom of each tutorial step, the is Solutions section, which list the files you should have come to if you have followed the instructions.

If you want to reproduce what’s explained in this tutorial, remember to depend on the Core Runtime artifact that depends -on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:

Table 6. Artifact

Group IDArtifact IDVersion

org.qi4j.core

org.qi4j.core.runtime

2.1-SNAPSHOT


See the Depend on Zest™ in your build tutorial for details.

< h4 class="title">Step 1 - Creating a ServiceComposite

In this tutorial we start with basic Java classes, to simulate a very simple Library where you can borrow +on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:

Table 6. Artifact

Group IDArtifact IDVersion

org.qi4j.core

org.qi4j.core.runtime

0


See the Depend on Zest™ in your build tutorial for details.

Step 1 - Creating a ServiceComposite

In this tutorial we start with basic Java classes, to simulate a very simple Library where you can borrow and return books.

Zest™ relies heavily on the use of interfaces. This makes it possible for an object to externally implement a number of interfaces which internally is backed by a number of Mixins, some of which you may have written yourself, and some of which may have been Modified: zest/site/content/java/develop/two-minutes-intro.html URL: http://svn.apache.org/viewvc/zest/site/content/java/develop/two-minutes-intro.html?rev=1692588&r1=1692587&r2=1692588&view=diff ============================================================================== --- zest/site/content/java/develop/two-minutes-intro.html (original) +++ zest/site/content/java/develop/two-minutes-intro.html Fri Jul 24 21:17:59 2015 @@ -70,7 +70,7 @@ Zest™ SDK sources. You should start your favorite editor and find the code related to this tutorial, run it and play with it.

To show that Zest™ is not necessarily complex, not hard to get going with and easy to deploy, we are first showing the classic HelloWorld, as small as it can get and still be Composite Oriented Programming and not only standard OOP.

If you want to reproduce what’s explained in this tutorial, remember to depend on the Core Runtime artifact that depends -on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:

Table 1. Artifact

Group IDArtifact IDVersion

org.qi4j.core

org.qi4j.core.runtime

2.1-SNAPSHOT


See the Depend on Zest™ in your build tutorial for details.

Ready, Set, Go!

Let’s say we want to do the common HelloWorld example, but with a more domain-oriented setting. +on Core API, Core SPI, Core Bootstrap and Core Functional & I/O APIs:

Table 1. Artifact

Group IDArtifact IDVersion

org.qi4j.core

org.qi4j.core.runtime

0


See the Depend on Zest™ in your build tutorial for details.

Ready, Set, Go!

Let’s say we want to do the common HelloWorld example, but with a more domain-ori ented setting. We have a Speaker interface that does the talking. But we also need an implementation for Speaker, which we declare here via the @Mixins( SpeakerMixin.class ).

@Mixins( SpeakerMixin.class )
 public interface Speaker