Author

Powered By

  • OpenWGA Blogs 2.4.2 Build 132
    Running on:
    womodo CMS Server 7.6.4 Maintenance Release (Build 680)
    www.openwga.com

Searchresult for: KEYWORDS:"openwga 7.2"

Sort by:


Module Controllers in OpenWGA 7.2

Model-View-Controller is a standard design pattern in modern software development.

Dividing view components from controller scripts makes the code easier to maintain and enables developers to test controller functions with external test frameworks.

In OpenWGA the "view component" is the TML module that renders the page (or part of it). Until now this TML often also contains script code (the "controller") nessesarry to render the TML module. The new module controller concept in OpenWGA 7.2 let you move your controller code into a separate TMLScript module. This makes the TML itself cleaner and easier to understand and makes the script methods testable by test frameworks. It also may improve the performance of TML modules.

TMLScript objects V2

TMLScript objects are objects defined in TMLScript modules that carry certain parts of needed functionality for the design.

OpenWGA 7.2 introduced a new way to define and use TMLScript objects. We call this "TMLScript Objects V2" and it is now the prefered way to use script objects. However the "old way" to use TMLScript objects is still supported and is described here.

We already posted about the new TMLScript object strategy as a concept. Today we want to "wrap up" what we actually implemented in OpenWGA 7.2.

OpenWGA 7.2.1 released

We  just released a new version of OpenWGA Content Management server

We addressed about 30 issues in this new release - a summery can be found here.

In addition to some general bug fixes the following content modules has been improved:

  • Modal
  • Lightbox
  • Accordion
  • Tabs
  • Overlay / Popups

The module "google map" can now be rendered using a custom API key - either globally defined for the server or via option "google-maps-api-key" in a design.

Image derivates for columns have been improved to render images as small as possible depending on the columns width.

Content store dumps can now be created without archived contents. This reduces the size of the dump.

OpenWGA on GitHub

Since version 7.2.0.0 the source code of the OpenWGA community edition is available on GitHub:

https://github.com/Innovationgate/OpenWGA

There are two branches on GitHub:

  • "develop" is the branch we are developing in. This branch contains the newest changes - tested locally but not released yet.
  • "master" ist the branch containing released code. If you want to build your own OpenWGA from source code check out the master branch.

Because we changed the OpenWGA build process to use gradle it should be very easy to generate your own OpenWGA system. Just check out the master branch from GitHub and run "./gradlew clean build".

OpenWGA 7.2

For all of you who didn't notice: 

OpenWGA 7.2 has been released silently a few weeks ago.

The release can be downloaded as usual here.

We are working on 7.2.1 with some interesting new features and additional improvements. 7.2.1 is planned to be released shortly.

In addition to OpenWGA 7.2 we also released a new version 3.2.0 of OpenWGA Developer Studio (WDS) based on Eclipse 4.5 (Mars) supporting all new OpenWGA 7.2 Tags and TMLScript API calls.

About OpenWGA 7.2: Web Sockets and Application Events

The last days of February are passing and OpenWGA 7.2 Server is right now becoming feature complete. So yes, let's start this posting again with a delay announcement: The current prediction for a "When it's ready" date is the end of March. While we do not plan to do any larger work on the Server anymore there is still the Dev Studio, which needs to be adapted to everything coming in 7.2. Also: User documentation. Still a lot to do.

This might also be the right time to note, that the things presented in this 7.2 posting series are subject to change until the final release. While the general concepts are safe to be included in 7.2 some usage details that are described here might change slightly until release and actually have already changed since then everwhere we saw the potential for further clarification and optimization.

OK, so lets continue our walkthrough with yet two more completely new concepts in OpenWGA 7.2: Web Sockets and Application Events.

About OpenWGA 7.2: Controllers and other WebTML goodness

In the previous part of our little series about what is coming with OpenWGA 7.2 we already talked about the fact that this release is quite a huge package, bringing with it some pretty groundbreaking changes about the way you can organize your OpenWGA applications. You could almost call it "WGANext", if that wouldn't bring up other unhappy memories...

Well, and like you most likely figured out by yourself until now: It will take us more than the (tiny) rest of this year to get it finished. We currently expect a release somewhere in February (yes, the next year). Regarding product releases we're firm believers in the mantra "it's finished when it's finished", and think that everybody will be better served by a bit late but really polished first version than anything less mature before that.

Still, let's talk about features: We already glanced into the way TMLScript objects are to be defined and how managed globals will allow you to define domain objects for your app that magically know where their place is. What we are about to talk here builds upon the facts described in part 1, so you are recommended to finish that first. Done? Or don't care? Ok, so let's dive headfirst into WebTML controllers.

About OpenWGA 7.2

OpenWGA 7.1, our last feature release, went out of the door in February this year. Quite some time has passed since then and as we have been quiet with announcing anything new ever since you might think that our OpenWGA development has stalled, apart from the regular maintenance releases.

Well we're happy to inform you that actually the opposite is true. OpenWGA 7.2 is in the works and will be a release with quite large, and dare we say "groundbreaking" changes and enhancements. 

While it still is far from finished - we assume it will need the rest of the year to get it release-ready - there are already numerous things in store that we can tell you right now, and which we will do in a series of postings in the next weeks.

Let's start with a treatment about the general direction of this release and the things we implemented on the TMLScript basis of the framework to get there.


Entry 1 to 8 of 8