Beiträge

Ina El-Kadhi, OXID Head of Development

OXID Admin NG – Alpha Release

An alpha version/developer preview of the new OXID Admin NG (Admin Next Generation) based on the Symfony 2 framework has been released today. From now on we will test the alpha in cooperation with selected partners and continue the developing process considering their precious feedback – thanks to all, who participate.

The following text passages (by Admin NG Product Owner Pierluigi Meloni, taken from the documentation) give you some insights into this project.

Main focus
The main focus of this admin project is set on what everything is really about, the pure e-Commerce domain. The intention is to model a clean and pure representation of this domain, where business logic and application logic are completely separated, so that the domain representation has no application related dependencies. It should also be easily possible to have access to this business logic without depending on a certain framework. To master this challenge we chose a domain-driven approach.

For the first release version of the Admin NG by domain we mean everything that deals with products and product management. We invested lots of time in evaluating and designing models that represent the domain around products activity. Furthermore this project is not built upon the OXID eShop code base. A new application has been created by using the Symfony 2 framework. The application uses a layered architecture as shown in the following graphic.

GrafikThe Admin NG is an application that is to be run in parallel to the OXID eShop.

A big challenge hereby is that this new application uses the same database as the current eShop to facilitate the adminstration of the eShop via the new Admin NG. So the Admin NG has to read the current database and produce more or less the same output the admin currently integrated into the OXID eShop does.

REST Interface
One objective is to make the business logic layer easily accessible. To realize this REST interfaces will be implemented. Having well defined REST interfaces creates many opportunities for interacting systems like creating custom GUIs for shop front and back ends, mobile apps, ERP or PIM systems, stand-alone checkouts and so on.

So far the alpha version realizes one REST interface for categories as a proof of concept.

Further domains
After finishing the product management we will turn our focus on the representation of another part of the e-Commerce domain. Further parts are order management, checkout processes and so on.

Current admin functionality
This project does not intend to replace the current admin of the OXID eShop completely. The main focus is set on pure e-Commerce business logic rather than on managing a CMS or a web shop application. Yet this is not impossible, as the new application will be modularized or bundled. It will be possible to write bundles for the new admin back end to access the eShop database, so every feature of the current admin could easily be reimplemented and improved. An example for such a bundle (although it is not properly bundled yet, but will be in near future) is the categories management. It is already realized in the new application and can be used.

AuthorIna El-Kahdi, OXID Head of Development
Ina El-Kadhi has learnt all the facets of software development first hand, with her 15 years diverse experience in the business field as developer, chief software architect, (agile) team leader, requirements engineer, product manager up to contributing member of senior management. A qualified Scrum Product Owner and Master, Head of Development at OXID repsonsible for all core platform products.

Translate OXID eShop Into the Language of Your Choosing

For some time now we have been working with OXID eShop translation center, that helps to interpret language keys used in OXID eShop and stored in language files. The software behind this is oTranCe, and it especially supports translators that have no clue about coding: there will be no longer any hassle with breaking pages because of a comma set wrong or character encoding.

Please feel free to download the language packages from the translation center with the credentials guest | guest. All translations made there will be published under the open source license GPLv3 and can be used freely by any OXID eShop edition.

Probably, if you need a special language, you have to support this in your daily business and for this have somebody to know the language. It would be communially beneficial if you please give something back: let your team members register and interpret some language keys by themselves. Here is a video tutorial about it:

 

If you want to know more about language file handling and get some language installation tips in OXID eShop please visit this page:
http://wiki.oxidforge.org/Tutorials/Language_handling

Here you will also find the well earned backlinks to the translators helping with this project. Just in case you need somebody to support foreign requests in your daily business or building up your product range in a foreign language 😉

Additionally, we started publishing the ready-to-use language packs on OXID eXchange and will extend these downloads step by step as soon as translations reach 100% for front end files or the entire package: front end, admin plus setup. We also provide the needed map.php, transliteration lists and language flags in the right shape and size for the theme Azure.

Chip in if you feel like you fancy a go!

Recap of Admin2.0 Hackaton

In our last blog post, we announced a special community event: a kick-off meeting for starting coding on a new admin panel. In all roundabout 10 interested developers from the community, from our partner network and also from shop owners came together in rooms in our branch office in Halle (Saale), Germany.

@Tobias writes in his German blog post:

“From the get go on Thursday evening, we were talking about, in a cozy atmosphere, the first common issues. The entire Friday was needed for working on the concept of the project so that the first lines of code could be written on Saturday.

In general, the new admin panel shall be so encapsulated that it can be used in parallel to other possible admin panels. As a basis for this, a REST API will be used so that even other applications have the possibility to pull or push data from and to the shop in a standardized format (JSON, XML, CSV etc).

After we planned this concept together, we split up into two groups, one for the admin front end (Rafael [HEINER DIRECT], Dennis [Koffer-direkt.de] Simone [marmalade], Rüdiger [GN2-Netzwerk]), and one for the REST API backend (Joscha [marmalade], Dave [GN2-Netzwerk], Daniel [Mayflower], Stefan [Mayflower], Tobias [shoptimax]). Not to forget the “hands by remote” (Kristian [D3], Ray [Haller Stahlwaren] -> Thanks for the care package!)
The result already looks good, and the present state can be seen at github.”

OXID Hackaton March 9th/10th: OXID Hackaton March 9th/10th

Of course, the development process continued after the event. In the meantime, the basis of the REST server is finished and all data from the oxarticle object can be called up. The authentication routine is nearly finished, and only token support is missing, but it will be done soon.

We applied for open source support at Atlassian and thankfully got a Jira + Confluence account. Also, there will be a server for the quality assurance with a Jenkins installation to check the status of the coding style and PHPunit tests.

In our last conference call on Monday evening this week, we agreed on how to share the upcoming tasks. Most likely, there will be another face-to-face meeting on the eve of OXID Commons 2012.

Stay tuned. If you want to get in touch with the team, please register to the mailing list or register yourself to the Jira account. Of course, any help would be appreciated 😉

OXID invites: A Community Project to Start in Halle on March 9th and 10th

In the last year, at our annual unconference accompanying OXID Commons, we already reported on the idea of developing a community driven admin 2.0 panel. This idea was followed by investigations into the client site and first rough drawings. Now, with the first developer meet-up this year in Hamburg, this topic came into swing again. We agreed on a kick-off meeting and coding event on March 9th and 10th which will take place in rooms in our branch office in Halle (Saale), Germany.

If you are interested, even from a distance, we’d be glad if you would join us! Or supporting this project, want to contribute in any other way. For example, we already have got some care packages for the coders 🙂 Please feel free to register yourself on the event’s wiki page on OXIDforge.

See you there!