It’s time to start implementing support for recognizing gestures with neural networks. As I mentioned in the previous post, I had seen some potential problems. After two days of work, I can finally write that those problems are solved. In this post, I’ll describe how I solved the problem of different drawing area location. In the second paragraph, I’m going to describe implemented resizing strategy. At the end, in the third part, I’ll write some words about flattering gestures and values normalization.
This post is divided into two main parts. The technical part will be connected with adding custom headers passed to an authentication endpoint. In the second part, I’m going to describe plans for next few weeks.
The last few days have been very productive. I have written demo endpoint which is able to return information whether a user should be logged in or not. In this application, I used the tool I met on the last Polish Java User Group meetup – Bootique. I’m going to describe it in the first part of this article. In the second, I’ll show you changes I made in the proxy application. There are a lot of new features.
The third episode of Quick Action series. Using very simple example I’m going to show how you can retrieve data from Facebook Graph API using Facebook JS SDK. To make an application more user-friendly I decided to use Angular Framework.
Yesterday I realized that I write more about refactoring than implementation. To stay consistent today’s post is about…refactoring. Well, maybe not only about it, but mainly. In the previous week I finished following tasks:
- [F-4] Handling request result (response code, message)
- [F-8] Encapsulate logic from aksesi-gesture.js into a class
- [F-9] Secure initialization
- [P-1] Forwarding requests to an authentication endpoint
The 8th version of Java introduced a few really cool features. My favorites are streams and, connected with them, lambda expressions. In this article, I’ll show you some examples of refactoring existing code into the more modern version. All of the examples, except the 1st one, were inspired by the Aksesi Proxy source code.
Today’s post is a brief summary what has changed in recent days. Especially, at the weekend. As I explained in the previous post, I changed my workflow. Now I’m working in the task-oriented flow, with branching system on the GIT. Not only can you follow it with the Github repository but also with the Trello board.
Recently I spent some time thinking about the Aksesi project. I have made some decisions that I’m going to cover in the next post. The very first thing on my list was to remove all of the TODOs from the code and refactor awful parts. In this post, I’m going to show you what I’ve changed in last few days.
In the “At the red-green-refactor carousel – implementing conversion unit” post I described how I have developed basic functionalities for conversion unit. I also mentioned that there is no Spring Framework integration and why I decided to implement CU in that way. In the following post, I’m going to show you this mystic integration process.
It’s been a week since the last post. In the following one, I’m going to summarize you what I’ve changed it the Aksesi since then. I decided to refactor some parts of the frontend application. Moreover, I managed to simplify installation and configuration process. The major part of integration is done “in the background” and a user does not have to care about it.