Group items tagged

Gaelyk is a lightweight Groovy toolkit for Google App Engine Java. Gaelyk lets you deploy small applications on Google App Engine Java. Gaelyk gives you the choice to use Groovy for developing your applications. Gaelyk builds upon Groovlets. and the Groovy template servlet Gaelyk allows you to cleanly seperate your views with Groovy templates and your actions in Groovlets. Gaelyk simplifies the usage of the Google App Engine SDK by providing more concise and more powerful shortcuts when using the datastore, memcache, the blobstore, the images service, the URL fetch service, when sending and receiving emails or Jabber messages, and much more. Gaelyk lets you define friendly REST-ful URLs thanks to its URL routing system Gaelyk provides a simple plugin system for improving code reuse and code sharing You can: download Gaelyk in the download area, learn how to create Gaelyk applications by reading the extensive tutorial, and participate in the community.

A few weeks back, I wrote a blog entry lamenting the attitude toward IDEs in the Scala community. A few people told me that the tooling situation was better than I'd implied, so I thought I'd spend a bit of time looking at using Scala (and Lift specifically) in Eclipse. I think the situation is still a ways away from the tooling situation for Java, but it is actually quite good, and I wanted to post a quick tutorial for those interested in developing Lift in Eclipse. Prerequisites This post assumes that you already have Scala 2.8 final and Eclipse 3.6 on your system. For Eclipse, I recommend upping the Xmx setting if you haven't already - I had issues when I had multiple Lift projects imported with Xmx set to 386. Also, this tutorial is going to use Maven, not SBT. SBT may be a better build tool for Scala projects, but I'm not sure how well it works with m2eclipse - I'm going to play with that more later. I also assume you know how to install plugins into Eclipse - I will create a more in-depth screencast for doing all of this if there is enough interest.

In this article I'll describe the setup I use to do develop Lift applications. While more heavy-weight than if an interpreted language is used, I find this setup provides fairly decent turnaround times. So, it took a little longer than expected to write this article which continues where the previous stopped. But all good things come to he who waits The software used in the previous article all had major updates in the meantime: Scala 2.8 (2.8.1 is just around the corner) Eclipse 3.6 Scale IDE for Eclipse (though a nightly build is currently needed for Eclipse 3.6) Gradle 0.9 RC1 Lift 2.1 RC2

Legacy systems embrace a large number of technologies, making the development of tools to cope with legacy systems evolution a tedious and time consuming task. As modernization projects face with both technologies combination and various modernization situations, model-driven approaches and tools offer the requisite abstraction level to build up mature and flexible modernization solutions. MoDisco provides an extensible framework to develop model-driven tools to support use-cases of existing software modernization :

"The Pencil Project's unique mission is to build a free and opensource tool for making diagrams and GUI prototyping that everyone can use. Top features: * Built-in stencils for diagraming and prototyping * Multi-page document with background page * Inter-page linkings! * On-screen text editing with rich-text supports * Exporting to HTML, PNG, Openoffice.org document, Word document and PDF. * Undo/redo supports * Installing user-defined stencils and templates * Standard drawing operations: aligning, z-ordering, scaling, rotating... * Cross-platforms * Adding external objects * Personal Collection * Clipart Browser * Object snapping * Sketchy Stencil * And much more..."

"Logback is intended as a successor to the popular log4j project, picking up where log4j leaves off. Logback's basic architecture is sufficiently generic so as to apply under different circumstances. At present time, logback is divided into three modules, logback-core, logback-classic and logback-access. The logback-core module lays the groundwork for the other two modules. The logback-classic module can be assimilated to a significantly improved version of log4j. Moreover, logback-classic natively implements the SLF4J API so that you can readily switch back and forth between logback and other logging frameworks such as log4j or java.util.logging (JUL). The logback-access module integrates with Servlet containers, such as Tomcat and Jetty, to provide HTTP-access log functionality. Note that you could easily build your own module on top of logback-core. "

"OpenI is an open source Business Intelligence application for on-demand or SaaS deployments. Based on J2EE, OpenI is an out-of-box solution to easily visualize data from OLAP and relational databases, where users intuitively build and publish interactive reports, analyses, and dashboards."

Emfatic is a text editor supporting navigation, editing, and conversion of Ecore models, using a compact and human-readable syntax similar to Java. The EPLed Emfatic now hosted at EMFT extends the Feb 2005 alphaworks release with support for EMF Generics, folding, "red squigglies", an EMF Type Hierarchy, hyperlinks, AutoEdits, and the possibility to define templates to speed up document creation, among other usability features. The best way to gain hands-on experience with Emfatic is to right-click on any .ecore file and choose Generate Emfatic source, a similar converter works in the opposite direction. Online help is also available. Emfatic itself builds upon Gymnast, a framework for jumpstarting text editors for custom Domain Specific Languages. Documentation on how to extend Emfatic, as well as on using Gymnast, can be found in this technical report.

Mod4j (Modeling for Java) is an open source DSL-based environment for developing administrative enterprise applications. It uses a collection of DSL's to model different parts of the architecture, combined with manually written code. Currently Mod4j consists of four DSLs: the Business Domain DSL, Service DSL, Data Contract DSL and Presentation DSL. The modeling environment is seamlessly integrated into the Eclipse IDE which gives the developers one environment where they can easily switch back- and forth between models and code. The different DSL?s used in Mod4j can be used independently, but if they are used in collaboration they will be fully validated with each other. Apart from integration in the Eclipse IDE, Mod4j also supports the use of Maven. That is, using the DSL models as the source, the complete code generation process can be run automatically on a build server without the need for Eclipse. The Mod4j DSLs and the corresponding code generators are based on a reference architecture. This allows developers to model various aspects of the application and generate code that strictly follows this reference architecture. The reference architecture is described in a separate document. For a good understanding of the generated code it is useful to read this document.

Before you read, please look at this video, showing the core features of ECP. The EMF Client Platform is a framework to build EMF-based client applications. The goal is to provide a one-click application based on a given EMF model. Besides the EMF model no additional components have to be developed or generated. Therefore ECP provides a standard solution including the most common features needed for EMF-based client applications. This application can then be customized step by step. This can be done by extending ECP or replacing single components completly.

Provide mechanisms for integrating Java security providers into Eclipse: Applications that need to implement security related functionality require cryptographic services upon which to build. Java provides the Java Cryptography Architecture (JCA) as a mechanism for installing implementations of several interfaces used for cryptography, including MessageDigest, Signature, KeyStore, Certstore, and more. In a typical Java application, these implementations reside in the extensions directory of the JRE. In a dynamic Eclipse application, the appropriate packaging mechanism is in Eclipse plug-ins. The goal is to allow JCA to be used in an Eclipse environment while maintaining the programming model of the JCA subsystem. A related goal is to expose the configuration of the JCA system via an Eclipse-based user interface, allowing authorized users to inspect and modify the Security object.

"m2eclipse provides comprehensive Maven integration for Eclipse. You can use m2eclipse to manage both simple and multi-module Maven projects, execute Maven builds via the Eclipse interface, and interact with Maven repositories. m2eclipse makes development easier by integrating data from a project's Object Model with Eclipse IDE features. With m2eclipse, you can use Maven within Eclipse in a natural and intuitive interface. Installing m2eclipse is straightforward, simply point your Eclipse IDE installation to the Eclipse Update Sites. For instructions, prerequisites, and a demonstration video, go to Installing m2eclipse. Once you've installed m2eclipse, you can watch our m2eclipse videos to learn how to install m2eclipse and create your first Maven project with m2eclipse. For a more complete introduction to m2eclipse, Developing with Eclipse and Maven. Developing with Eclipse and Maven is a free, online book, which provides comprehensive documentation for the m2eclipse Maven integration for Eclipse."

Supplemental Custom Widgets for SWT (and more) Nebula is a place where different Eclipse-Projects and Independent developers collaborate on building Custom SWT widgets and reuseable UI-Components useable in UI-Applications built using SWT and JFace. All Nebula components are available on the navigation tree on the left or from the table below. Each image links to a page that will further describe the component and its function

When you write Eclipse plug-ins sooner or later you will start thinking about testing your work. The very first steps will lead you to the Internet. But to my (and maybe your ;) ) surprise this information is not very easy to find. I know two ways to accomplish this task and I want to describe the first one - testing Eclipse plug-ins using build-in JUnit support.

ECF is a framework for building distributed servers, applications, and tools. It provides a modular implementation of the OSGi 4.2 Remote Services standard, along with support for REST-based and SOAP-based remote services, and asynchronous messaging for remote services. See the ECF Wiki for examples, tutorials, other documentation, as well as plans and efforts currently underway for future releases.

Apache CouchDB is a document-oriented database that can be queried and indexed in a MapReduce fashion using JavaScript. CouchDB also offers incremental replication with bi-directional conflict detection and resolution. CouchDB provides a RESTful JSON API than can be accessed from any environment that allows HTTP requests. There are myriad third-party client libraries that make this even easier from your programming language of choice. CouchDB's built in Web administration console speaks directly to the database using HTTP requests issued from your browser. CouchDB is written in Erlang, a robust functional programming language ideal for building concurrent distributed systems. Erlang allows for a flexible design that is easily scalable and readily extensible. See the introduction and the technical overview for more information.

" Registered 2008-09-26 by Michael Terry Déjà Dup is a simple backup tool. It hides the complexity of backing up the Right Way (encrypted, off-site, and regular) and uses duplicity as the backend. Features: * Support for local, remote, or cloud backup locations, such as Amazon S3 or Rackspace Cloud Files * Securely encrypts and compresses your data * Incrementally backs up, letting you restore from any particular backup * Schedules regular backups * Integrates well into your GNOME desktop For Ubuntu users, there are three ways to get Déjà Dup: * Supported releases: http://apt.ubuntu.com/p/deja-dup * Stable release backports: https://launchpad.net/~deja-dup-team/+archive/ppa * Daily builds: https://launchpad.net/~deja-dup-team/+archive/testing If you are interested in contributing, there are many ways to help: * http://live.gnome.org/DejaDup/GettingInvolved"

" The Web Modelling Language is a visual notation for specifying the content, composition, and navigation features of hypertext applications, building on ER and UML."

"The Open Services for Lifecycle Collaboration (OSLC) is an open (creative commons) REST based service specification aimed at improving/simplifying Application Lifecycle Management (ALM) system integration. A number of aspects of ALM integration are covered by OSLC ranging from Requirements Management to Automation(Build/Deploy). The OSLC Change Management (CM) spec outlines a standard for creating, modifying, and querying for change requests (tasks) from OSLC based service providers. A goal of the Mylyn project is to implement a client for OSLC-CM (see [1]). Additionally, support for both OSLC Automation and OSLC SCM are part of the Mylyn restructuring proposal: http://www.eclipse.org/project-slides/mylyn-restructuring-review.html Once these plans have solidified, we can begin to fill out the roadmaps for each specification. "

" Xtext has been released as a part of the Eclipse Galileo release train on June 24th, 2009. Xtext is a framework for building DLSs (domain specific languages). In fact, it can be seen as a DSL for defining DSLs. In this article, we will develop a small DSL for defining entities."