Digimead Artifacts

You are welcome ;)))
Maven Central: 
libraryDependencies += "###ORG###" % "###ARTIFACT###" % "###VERSION###"
<dependency>
  <groupId>###ORG###</groupId>
  <artifactId>###ARTIFACT###</artifactId>
  <version>###VERSION###</version>
</dependency>
<dependency org="###ORG###" name="###ARTIFACT###" rev="###VERSION###" />
@Grapes(
    @Grab(group='###ORG###', module='###ARTIFACT###', version='###VERSION###')
)
'###ORG###:###ARTIFACT###:###VERSION###'
'###ORG###:###ARTIFACT###:jar:###VERSION###'

You may add Maven repository: 
resolvers += "digimead-maven" at "http://storage.googleapis.com/maven.repository.digimorg/"
Or you may add Ivy repository: 
resolvers += Resolver.url("digimead-ivy", url("http://storage.googleapis.com/ivy.repository.digimead.org/"))(Resolver.defaultIvyPatterns)
And then 
addSbtPlugin("###ORG###" % "###ARTIFACT###" % "###VERSION###")
Or you may create a 
project/project/Build.scala
file that looks like the following: 
import sbt._
object PluginDef extends Build {
  override def projects = Seq(root)
  lazy val root = Project("plugins", file(".")) dependsOn(plugin)
  lazy val plugin = uri("git://github.com/###ORG###/###ARTIFACT###.git#TagOrCommit")
}
You may find more information about Build.scala in SBT documentation

Mr. Alexey Aksenov aka ЁЖ

Primary email
Secondary email
Skype
ICQ
Russian phone
United Kindom phone
WorldWide SIP

Repositories:
Digimead Ivy located at http://storage.googleapis.com/ivy.repository.digimead.org/
Digimead Maven located at http://storage.googleapis.com/maven.repository.digimead.org/
TA Buddy: Desktop - Combined Pages
Contents in Depth ⇦ Previous Page

Contents

TA Buddy: Desktop 

TA Buddy: Desktop application.

Latest stable version - UNKNOWN

Latest development version - UNKNOWN

Initialization diagram 

Application components 

Core 

Core UI 

Element editor 

Logic 

Model definition 

Model editor 

Translation 

Core 

Console 

Console provides command line interface for the application.

There is a singleton, Akka actor, that intermediate between a user and the application.

There is a solid interface with echo method from the application side.

And there are pack of synchronized interfaces like local console, telnet, GUI console and so on from the user side. User input is processed by dynamic set of parser combinators. Result of each correct command is operation invocation.

All interfaces are binded and updated at the same time after successful command execution since it is a single user application by design.

So an everyone could see the same console state at different implementations.

User Input --> Console --> Command --> Future --> Operation --> Result --> Converter --> Output

List of the console commands. 

Command

Description

Notes

help

Show detailed information about command

Default context: Core. By default list commands that are available from the current context. You may pass all argument to get list of all registered commands.

test

Test command for development purpose.

Default context: none.

info

Show application information.

Default context: Core.

exit

Exit from application.

Default context: Core.

Operation 

test

help

info

exit

Service with application entry point 

Service with translation API 

Definitions 

Command 
Context 
NLS 
Operation 
OperationApprover 

Report 

Support 

Current state

I Like It

Versions

Correctness

Orphus system
Select spelling error with your mouse and press Ctrl+Enter
This information is provided in the hope that it will be useful and help people with their first steps, even if it is written in broken English... Would you have preferred well written Russian? :-) Please, correct it, if you find something inappropriate.
Fork me on GitHub