- Entwicklung - example.com

Fwd: Get Your New PHP Extensions Guide
by Denny Brandes 08 Apr '20

08 Apr '20

Nice topic. PDF is attached :-) -------- Weitergeleitete Nachricht -------- Betreff: Get Your New PHP Extensions Guide Datum: Tue, 7 Apr 2020 09:46:00 -0500 (CDT) Von: Zend by Perforce <info(a)perforce.com> Antwort an: info(a)perforce.com An: d.brandes(a)traso.de <http://go.roguewave.com/FUbLD001Q0A0O0Gw000Gfwl> Learn How to Write PHP Extensions Your Step-by-Step Guide . . . DOWNLOAD GUIDE <http://go.roguewave.com/XfD0ORL0w000GGlbw00UA20> Writing PHP extensions is a critical development skill for quickly adding innovative features to your PHP applications. Download the new PHP Extensions Technical Guide to get comprehensive, step-by-step instructions for writing extensions. Key topics include: • Build environments. • Extension skeletons. • Building, installing, testing, and rebuilding extensions. • Adding new functionality. • PHP structures and arrays. • Memory management. • PHP classes and objects. • Object-oriented programming in extensions. To help with learning, you can also access a repository of the code files generated when following the steps in the tutorial. Increase your development skills and learn how you can improve your PHP applications with extensions. Take advantage of this free guide today! DOWNLOAD GUIDE <http://go.roguewave.com/XfD0ORL0w000GGlbw00UA20> <http://go.roguewave.com/FUbLD001Q0A0O0Gw000Gfwl> To unsubscribe please click here. <http://go.roguewave.com/b0000fLDGA30GOUS000wblw> Zend by Perforce 400 First Avenue North #200 | Minneapolis, MN 55401 Zend by Perforce © Perforce Software, Inc. All rights reserved. Facebook <http://go.roguewave.com/VbLT000fGU0G000ADlwO4w0> Twitter <http://go.roguewave.com/z0wb0fD000lLw5GUAOU0G00> LinkedIn <http://go.roguewave.com/b0000fLDGA60GOUV000wblw>

1 0

Interesting article: The Container is a lie!
by Stefan Wieden 27 Mar '20

27 Mar '20

https://platform.sh/blog/2020/the-container-is-a-lie/ -- Viele liebe Grüße Stefan Wieden - Development ___________________________________________________________________________ TraSo GmbH Nonnenstraße 42 D-04229 Leipzig Tel.: +49 341 355 740 20 Internet: http://traso.de E-Mail: s.wieden(a)traso.de ___________________________________________________________________________ Geschäftsführer: Haiko Gerdes Handelsregister: Amtsgericht Leipzig, HRB 21850

2 1

weiteres Vorgehen mit xRes Testsystemen test 01+02 DEV+TSO
by Stefan Rank-Kunitz 25 Mar '20

25 Mar '20

Guten Morgen liebstes Supportteam, Durch einen Hotfix der letzten Woche ist es dazu gekommen, dass die aktuelle xRes Version 20.04-19 nicht mehr kompatibel ist zur PHP Version 5.4. Das Probem ist ein Einzeiler und könnte durch einen weiteren Hotfix leicht korrigiert werden. Tatsächlich sind die beiden letzten xRes Systeme, die überhaupt auf PHP 5.4 laufen, genau Test01+02 (jeweils DEV und TSO), das genannte Problem hat also keinerlei Relevanz für den xRes Livebetrieb. Sören hat in den vergangenen Wochen begonnen, mit verschiedenen SupporterInnen neue xRes Testsysteme auf Test04+05+06 aufzusetzen (XJNE, XNRO, ...). In Abstimmung mit René und Sören schlage ich nun vor, dass wir das oben genannte technische Problem zum Anlass für den Umzu nehmen: * test01+02 bleiben mittelfristig stehen, damit alle Mitarbeiter weiterhin Configs holen und Dinge tun können. Leider müssen die Systeme auf der xRes Version 20.04-13 stehen bleiben, weil diese die letzte komplett funktionierende Version für diese Testsysteme ist. In 1-2 Monaten ... nach Freigabe durch die SupportmitarbeiterInnen, reißen wir die Systeme ab. * Sören hat angeboten, den eingeschlagenen Weg zum Aufbau neuer Testsysteme fortzusetzen und damit Ersatz für test01+02 zu schaffen. Diese Testsysteme können (wie bisher umgesetzt) personen-gebunden sein, aus meiner Perspektive ist das aber keine feste Regel und Eure Rückmeldung zur Struktur der Testsysteme ist absolut gefragt! Mir ist vollkommen klar, dass dieser Umzug auch bei Euch zusätzlichen Aufwand bedeutet. Diesen Aufwand können wir aber leider nicht nicht-machen ... irgendwann ist er dran und vielleicht gibt und die aktuelle Krise die zeitlichen Ressourcen, diesen Umzug zu machen. Ich freue mich auf Eure Rückmeldung und hoffe, dass wir damit PHP 5.4 und (bei Umstellung der LMX LiveSysteme übernächste Woche) auch PHP 5.6 abschalten können. Das wäre wirklich wunderbar. LG Stefan -- Mit freundlichen Grüßen Stefan Rank-Kunitz - Technical Director - ________________________________________________________ TraSo GmbH Nonnenstraße 42 D-04229 Leipzig Tel.: +49 341 355 740 - 43 E-Mail: s.rank-kunitz(a)traso.de ________________________________________________________ Handelsregister: Amtsgericht Leipzig, HRB 21850

1 0

xRes Core uses the INTL extension
by Rodrigo Cinto 04 Mar '20

04 Mar '20

This extension has always been available (and enabled) in Bamboo, Test and Live systems based on my verification. The same goes for the Docker container. Just be sure, however, in case you are running any PHP in your host machine for scripts or tests. Regards, Rodrigo

1 0

Fwd: Zend Framework user? See how to migrate to Laminas in this free webinar.
by Denny Brandes 21 Feb '20

21 Feb '20

FYI -------- Weitergeleitete Nachricht -------- Betreff: Zend Framework user? See how to migrate to Laminas in this free webinar. Datum: Thu, 20 Feb 2020 12:56:27 -0600 (CST) Von: Zend by Perforce <info(a)perforce.com> Antwort an: info(a)perforce.com An: d.brandes(a)traso.de Free Webinar <http://go.roguewave.com/Y0flQ0MwO00wb000DLA0OGT> LIVE WEBINAR Migrating from Zend Framework to Laminas Matthew Weier O'Phinney Will Show You How It’s Done . . . THURSDAY, FEBRUARY 27, 2020 9:00 A.M. PT | 12:00 P.M. ET Learn More + Sign Up! <http://go.roguewave.com/UwNO0lG0DL0AfQ00Tw000Pb> Have questions about the Zend Framework transition to Laminas — including how to migrate? Get answers in this free one-hour webinar! Matthew Weier O'Phinney, a leading PHP contributor, Zend Framework developer, and now Development Lead for the Laminas Project, will: • Explain the Zend Framework transition to Laminas. • Demonstrate the key steps you’ll take to migrate to Laminas. • Answer your questions. We hope you join us! Learn More + Sign Up! <http://go.roguewave.com/UwNO0lG0DL0AfQ00Tw000Pb> <http://go.roguewave.com/Y0flQ0MwO00wb000DLA0OGT> To unsubscribe please click here. <http://go.roguewave.com/gQ0blwD0w00TLG0fA000OQO> Zend by Perforce 400 First Avenue North #200 | Minneapolis, MN 55401 Zend by Perforce © Perforce Software, Inc. All rights reserved. Facebook <http://go.roguewave.com/VbLP000fQT0G000ADlwORw0> Twitter <http://go.roguewave.com/SL0G0f0bD0l0wAO0T00QwQS> LinkedIn <http://go.roguewave.com/gT0blwD0w00TLG0fA000RQO>

1 0

What if xRes had a fully automated test environment?
by Rodrigo Cinto 30 Jan '20

30 Jan '20

In a world where we had xRes fully automated, how would the workflow of a new feature look like? Here I create a imaginary scenario, and describe what would be needed for it to happen. Hypothetical scenario: Early Booking Everything starts with the requirements *Story* As a Hotel Provider, I'd like to inform special conditions for reservations considered "Early Booking". Such information should be kept by xres and furthermore exported to midOffices systems. *Details *An Early Booking can happen when a room reservation is made in a long term advance. The criteria to define the booking an Early Booking stays at the Hotel Provider side, so it decides when to apply and inform it. *Acceptance Criteria* 1. Initial Providers that should support EB information: MTS, HBD 2. Tags informed for EB: Deposit Price, Currency, Initial Deposit Date, Final Deposit Date 3. xRes must retain the EB information in the Booking 4. EB information should be displayed in the Booking Details page in xAdmin 5. EB Tags must be present in the XML Request of the exports for Midoco and xMid *Assumptions* 1. The EB information will be provided by the Hotel Provider in its XML response from Actions BA or B. 2. The EB Tags to be exported for MidOffices will follow the example provided and attached in this task. After all the requirements clarified, the story can be broken down into smaller tasks. The development should make sure that not only the new functionality has been achieved, but also that there is enough evidence for it to be validated in both automated and human ways. In parallel, the Test Cases can be written, asserting that all the requirements will be satisfied and without any side effects. Test Cases *#TC1* *Scenario* One Hotel Room with a single bed and all services included is booked for one man 6 months in advance. *Steps* 1. With any booking interface, perform an Action BA. 2. Perform an Action B. 3. Export the new booking to MidOffices. *Expected Results* 1. A new Booking should be created. 2. In the booking details page, information about Early Booking should be visible in the Hotel block. 3. The Request XML of the export for xMid should contain the EB info in the correct standards. 4. The Request XML of the export for Midoco should contain the EB info in the correct standards. More complex scenarios could be created, or even scenarios considering failures from third parties could also be considered. For example, a family of two adults, one child and one infant book two rooms, but the provider responds with invalid format dates in one of the EB tags. The Test Case should follow the same concept, and the Expected Results should be established. But for this example, I we will keep only the Happy Path. Functional Test Automation The Functional tests should be running in a controlled and isolated environment, with a dedicated xRes instance and Database. That way, it is possible to break it without consequences. Here's how it'd look like: Explaining the diagram above, as said before, everything starts with the Requirements (Test Cases). As many Test Cases as possible are transcribed into Automated Functional Tests, on a Test Automation Platform. The Test Automation Platform can be any tool or technology that supports High level automations. It could be Postman, Behat, Selenium, Codeception, etc. The list goes on. Regardless of the solution, the Automated Tests Platform should be capable of: * Have access to the Config files for Tests Setup; * Have access to the DB for Setup, Cleanup, and Assertions; * Have access to Log files for Assertions; * Have access to Shell Command Line input and output for Tests executions and Assertions; * Be able to perform HTTP requests; Given that the solution which I have more experience with is Behat, and I know for a fact that it supports such low level actions behind the system, we'll use it in this example. In Behat Gherkin language, a test would be something like this: Feature:In order to see the Early Booking information As a xAdmin user, I want to book a room and export it. Scenario:Book an Early Booking Hotel Room and export it. Given my name is "Rodrigo Cinto", 31 years old, email "r.cinto(a)traso.de" And I live in "Leipzig", address "Nonnenstrasse42", Zipcode "04229" And I book a Hotel BERLIN with services DZZA And from "201120" to "221120" When I make an Action BA And I make an Action B And the Hotel Provider responds an Early Booking with Deposit Price '100.00', Currency 'EUR', Initial Payment Date '2020-02-05', Final Payment Date '2020-11-05' And I execute the MidOffices export queue Then I would like to see "Early Booking" and "2020-02-05 - 100.00 EUR" in the "Last booking details page" And I would like to see "Early Booking: 2020-02-05 - 100.00 EUR" in the "Midoco export logs" And I would like to see "Early Booking: 2020-02-05 - 100.00 EUR" in the "xMid export logs" It seems a little sorcery, but Behat allows you to create a PHP function for each one of those statements with help of Regular Expressions. To possibilitate full environment control, the responses from the External Services Providers like Hotel, Flights and Transfers must be provided by a Fake API Server, or Provider Simulator. This Fake API Server is a very important component, which can be configured to answer to any request, with any response, following the Tests Requirements. To make sure the Tests don't compromise other environments, a separated instance of xRes and Databases should be provisioned as well, with copy cats of Hotels, Flights, Users, and so on. The new tests are then stashed among all the other previously created tests, each one of them with their own setup, execution, assertions, and tear down. Now it is time to integrate the Automated Functional Tests with the rest of the workflow. Good thing about automation is that we can run it whenever we want. Therefore, we should be able to decide whether we'd like to run the tests or not during a new Release launch. Is it a heavy push? We should wait for the tests to be executed. Is it a hotfix that needs to be pushed as quick as possible? Leave the Functional Tests for later. It would even be possible to schedule periodic executions, in order to make sure the system is tidy and there are no hidden surprises in old delivered features. Still speaking of Releases, after it is done, only then we can finally check manually the Test Cases we couldn't or didn't want to automate, but in a perfect world they should be minimal verifications. How far are we from it to become reality? Not much. 1. The xRes developers are significantly mature regarding the concept of mocking API responses, and we have more then one solution for that, from the lowest interaction level to the highest. The only thing we'd have to do would to provision an actual machine for the tool. 2. We'd need to install a brand new instance of xRes. But we have the needed expertise and it would be a perfect opportunity to learn more about how xRes essence works. 3. For the Test Cases, we'd have to change our mindset regarding reading and writing requirements, and documenting our Tests. Big challenge at this one. 4. The testing platform would require a learning curve, but we are smart people, and we are used to learn something new every day. 5. We already have customizable deploying tools like Bamboo, so adding a new optional routine to it wouldn't be too hard.

1 0

xRes external update
by Soeren Pestner 27 Jan '20

27 Jan '20

For xRes version 20.02 I've merged some external packages updates and composer changes into develop. 1. composer use traso gitlab only ---------------------------------------- In composer.json we decided to configure "packagist.org": false Means we only use traso gitlab for fetching packages. 2. composer should use gitlab api --------------------------------- Denny and Denny have investigated the gitlab communication over the gitlab api and found a work around to using it. If you can see "Downloading" instead of "Cloning", when you run composer install/update, everything's fine. otherwise: cp /etc/ipa/ca.crt /etc/pki/ca-trust/source/anchors/ update-ca-trust extract 3. php56 -------- With the new bamboo system we can build php versions greater the 5.4. We start with php56, so there are some package updates. Please run: php composer.phar install-testing -- -- Sören Pestner - Entwickler - TraSo GmbH Nonnenstraße 42 D-04229 Leipzig telefon: +49 341 355 740 - 49 email: s.pestner(a)traso.de Geschäftsführer: Haiko Gerdes Handelsregister: Amtsgericht Leipzig (HRB 21850)

1 0

Fwd: Webinar: What’s New in PHP 7.4
by Denny Brandes 24 Jan '20

24 Jan '20

Someone interested? -------- Weitergeleitete Nachricht -------- Betreff: Webinar: What’s New in PHP 7.4 Datum: Fri, 24 Jan 2020 09:13:41 -0600 (CST) Von: Zend by Perforce <info(a)perforce.com> Antwort an: info(a)perforce.com An: d.brandes(a)traso.de Live Webinar, January 30, 2020 <http://go.roguewave.com/rl030G0c0LnDbwATO00w0f0> LIVE WEBINAR PHP 7.4 Is Here! Learn What’s New . . . JANUARY 30 | 9:00 a.m. PT | 12:00 p.m. ET Sign Me Up <http://go.roguewave.com/rl040G0c0LoDbwATO00w0f0> PHP 7.4 provides capabilities for significantly boosting performance and improving code. In this one-hour webinar, Maurice Kherlakian, Director of Product Management for Zend, explains the release’s new features, including: • Preloading • Typed properties in classes • FFI • Arrow functions • Spread operators in arrays At the end of his presentation, Kherlakian will answer your questions. We hope you join us! Sign Me Up <http://go.roguewave.com/rl040G0c0LoDbwATO00w0f0> <http://go.roguewave.com/rl030G0c0LnDbwATO00w0f0> To unsubscribe please click here. <http://go.roguewave.com/lcLwp000DTbO0G0fl0w050A> Zend by Perforce 400 First Avenue North #200 | Minneapolis, MN 55401 Zend by Perforce © 2019 Perforce Software, Inc. Facebook <http://go.roguewave.com/Mw0G0w0bAclTf00qD0OL060> Twitter <http://go.roguewave.com/JL0DAw07TG0wrcb0fO000l0> LinkedIn <http://go.roguewave.com/DA8l00s0GLb00c0TDw0O0fw>

1 0

Visual Perception of Code
by Ozan Akman 03 Dec '19

03 Dec '19

There is a nice video that explain things to make your development life easier, Especially for the people who use small fonts and dark background while coding. https://www.youtube.com/watch?v=rDMI1dpNfdw Happy coding, Cheers! -- Mit freundlichen Grüßen Ozan Akman - Entwicklung ________________________________________________________ TraSo GmbH Nonnenstraße 42 D-04229 Leipzig Tel: +49 341 355 740 20 E-Mail: o.akman(a)traso.de Internet: https://www.traso.de ________________________________________________________ Geschäftsführer: Haiko Gerdes Handelsregister: Amtsgericht Leipzig, HRB 21850 _______________________________________________ team mailing list team(a)lists.traso.de https://lists.traso.de/listinfo/team

1 0

36C6
by Felix Seidel 14 Nov '19

14 Nov '19

Neues Jahr, neuer Kongress! Auch dieses Jahr gleiches Spiel, tragt euch im Doodle ein, wenn ihr hin wollt, wer sich einträgt muss aber auch gehen. Es gibt dieses mal nur einen Versuch Tickets zu bekommen, weil die beideren anderen Termine bereits durch sind. Achtet bitte darauf, dass der Zeitraum wieder zwischen Weihnachten und Silvester liegt und dass auch noch Leute für eine Bereitschaft Verfügbar sind. Genauer Zeitraum: 27.-30.Dezember 2019 Link zum Doodle: https://doodle.com/poll/w58zsrr53pcg65ty Bitte bis Sontag Abend Eintragen, der letzte Termin für die Tickets ist nächsten Donnerstag und ich muss Zeit zum planen haben. Danke & Viele Grüße, Felix -- Mit freundlichen Grüßen Felix Seidel - Lead Developer xMid - ________________________________________________________ TraSo GmbH Nonnenstraße 42 D-04229 Leipzig Tel: +49 341 355 740 47 E-Mail: f.seidel(a)traso.de Internet: https://www.traso.de ________________________________________________________ Geschäftsführer: Haiko Gerdes Handelsregister: Amtsgericht Leipzig, HRB 21850

1 0