Group items tagged

"These are the major new features added since Slick 1.0.1: A code generator that reverse-engineers the database schema and generates all code required for working with Slick. New driver architecture to allow support for non-SQL, non-JDBC databases. Table definitions in the Lifted Embedding use a new syntax which is slightly more verbose but also more robust and logical, avoiding several pitfalls from earlier versions. Table definitions (and their * projections) are not restricted to flat tuples of columns anymore. They can use any type that would be valid as the return type of a Query. The old projection concatenation methods ~ and ~: are still supported but not imported by default. In addition to Scala tuples, Slick supports its own HList abstraction for records of arbitrary size. You can also add support for your own record types with only a few lines of code. All record types can be used everywhere (including table definitions and mapped projections) and they can be mixed and nested arbitrarily. Soft inserts are now the default, i.e. AutoInc columns are automatically skipped when inserting with +=, ++=, insert and insertAll. This means that you no longer need separate projections (without the primary key) for inserts. There are separate methods forceInsert and forceInsertAll in JdbcProfile for the old behavior. A new model for pre-compiled queries replaces the old QueryTemplate abstraction. Any query (both, actual collection-valued Query objects and scalar queries) or function from Column types to such a query can now be lifted into a Compiled wrapper. Lifted functions can be applied (without having to recompile the query), and you can use both monadic composition of Compiled values or just get the underlying query and use that for further composition. Pre-compiled queries can now be used for update and delete operations in addition to querying. threadLocalSession has been renamed to dynamicSession and the corresponding methods have distinct names (e.g. w

"This project aims at providing a Scala to JavaScript compiler, so that one can write the client-side of a Web application in Scala, and have it compiled into JavaScript code."

"This library dynamically compiles scala source files and loads them as classes. Changed scala files will be recompiled and the changed class with be loaded. Multiple source paths are supported as well as compilation class path and class loading class paths (so that the scripts can load extra libraries). Classpath detection can be automatic (effectively using the classpath of the caller) or manual."

"Protostuff is the stuff that leverages google's protobuf. A serialization library with built-in support for forward-backward compatibility (schema evolution) and validation. available formats: protostuff (native) graph (protostuff with support for cyclic references. See SerializingObjectGraphs) protobuf json smile (binary json useable from the protostuff-json module) xml yaml (ser only) kvp (binary uwsgi header) support for messages that are generated by the protostuff-compiler (java_bean) cyclic references via graph format see CompilerOptions for more customized compilation of .proto files support for existing pojos (See runtime schemas) cyclic references via graph format polymorphic (a nested message can be an interface/abstract class or even java.lang.Object) support for existing protoc-generated java messages see the io instructions for json, xml, yaml) no support for cyclic references (limitation of the builder pattern) Interoperability across various mobile platforms android kindle j2me (protostuff-me module) Transcoding support converts one encoding to another. See PipeUsage. Source and Sink protostuff, protobuf, json, json-numeric, smile, smile-numeric, xml Sink only yaml "

"This is a maven plugin that adds a new packaging type ('scala-jar') to maven with a better default lifecycle. This lifecycle binds net.alchim31.maven:scala-maven-plugin:compile to the 'compile' phase by default while also retaining an invocation of maven-compiler-plugin. Additionally, com.vast:scala-surefire-maven-plugin:test is bound to the 'test' phase. This allows native and seamless use of ScalaTest in your build."

"Babel is a JavaScript compiler. Use next generation JavaScript, today."

Imperdible!

Dick Wall explores the state and future of Java, his reasons for switching to programming in Scala, the SubCut Dependency Injection library for Scala, Scala Compiler Plugins and much more.

The VMKit project is a framework for building virtual machines. It uses LLVM for compiling and optimizing high-level languages to machine code, and MMTk to manage memory. J3 is an implementation of a JVM with VMKit.

"Let the Scala compiler work for you. We provide type classes, instances, conversions, supplements to the standard library, and much more."

"Library for expressing quantities and units of measurement in Scala in a type safe manner, where the compiler checks that assignments and calculations with the units are correct."

Functional dependencies are a near-standard extension to Haskell (present in GHC and elsewhere) which allow constraints on the type parameters of type classes to be expressed and then enforced by the compiler.

"HPaste unlocks the rich functionality of HBase for a Scala audience. In so doing, it attempts to achieve the following goals: Provide a strong, clear syntax for querying and filtration Perform as fast as possible while maintaining idiomatic Scala client code -- the abstractions should not show up in a profiler! Re-articulate HBase's data structures rather than force it into an ORM-style atmosphere. A rich set of base classes for writing MapReduce jobs in hadoop against HBase tables. Provide a maximum amount of code re-use between general Hbase client usage, and operation from within a MapReduce job. Use Scala's type system to its advantage--the compiler should verify the integrity of the schema. Be a verbose DSL--minimize boilerplate code, but be human readable!"

MonoHelper offers XBuild integration into Visual Studio, so you can use Mono within Visual Studio (Build & Run). When using XBuild or XRebuild command, MonoHelper detects current installed Mono Runtime or use preconfigured installation path, call XBuild with current configuration settings and outputs the results into the Output Console. It also generates pdb symbol files, so you can debug XBuild compiled programs with Visual Studio (running with .NET Runtime - see Stackoverflow about how this is done). If you want to run your program with installed Mono runtime, this is also possible.

"Apache Phoenix is a SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Apache Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows. "

"Apache Phoenix is a SQL skin over HBase delivered as a client-embedded JDBC driver targeting low latency queries over HBase data. Apache Phoenix takes your SQL query, compiles it into a series of HBase scans, and orchestrates the running of those scans to produce regular JDBC result sets. The table metadata is stored in an HBase table and versioned, such that snapshot queries over prior versions will automatically use the correct schema. Direct use of the HBase API, along with coprocessors and custom filters, results in performance on the order of milliseconds for small queries, or seconds for tens of millions of rows."

"Tool permitting static assets to be attached to compiled go binaries, permitting single-file project deployment"

"Today, we announced the release of Scala.js v0.6.0, the Scala to JavaScript compiler, and dropped the experimental flag associated to it. Yes, you read it right: Scala.js is no longer experimental! After exactly 2 years of development, we finally feel comfortable calling it production-ready."