Open Source

In this release I have worked on few front-end issues. But before I jump into describing what did I do and what new things I learned I would like to share my "experience" with Docker. Once Telescope launch Elastic search things start to become more and more interesting.  When I update my master branch I try as usual to run Telescope locally. I did my usual set of commands to run App and to add feeds on the page.  `npm run develop` in VSCode `npm start` (this I'll explain later) After that all problems begin. I realize I'm not the only one who has same problem.  So what was the problem? Me and my classmates call it "Windows virus".  What are the symptoms ? 1. Your machine has Windows 10 Home Edition version. 2. There are no Linux or Unix install as secondary Operating System on the machine 3. You have no other option but just Docker Toolbox installed. I heard many times that people complain about the Toolbox and how inconvenience it is, ...

It has been few days since I'm trying to put all the thoughts together. I think I'm finally ready. I'm writing this post in the time when the whole world going through the major tryouts. Despite that nobody cancel Open Source, moreover somebody find this time of self isolation as a time to contribute more to the Open Source Community. Last week I was working on few Telescope issues. I even find a time to submit one bug and review two pull request. A first issue I was working on was about link that overflow in mobile view. Actually as I discovered later that issue was as well on the desktop view. Interesting fact that not all links were overflowing so it was not easy to spot where the problem came from. In order to solve this problem I find interesting article about similar issues. First I will talk about possible solution and than about the one    picked. CSS has few solutions: ` overflow-wrap: break-word;` `word-wrap: break-word;` Both of those lines will brea...

Every week bring me close to the release 1.0. Do I feel excited? I don't know answer for this question because it's not just Release 1.0 but also the end of the course, the end of the semester and hopefully the end of school. All I know for sure 1.0 is not carry just one meaning for me. What did I do for Release 0.7. This time I had a chance to work on styling and get to know CSS a bit more than I knew before. My first issue was to fix look of our posts Issue #700 . The idea behind this issue is to make all posts have same fonts, sizes, line spacing, image size, etc. This issue was base on comparing our website to other websites that also focused on presenting articles. Medium , Longreads , The New Yorker ,  The New York Times  were analyse as an example to follow. While this sources provide good idea of what fonts for the title and post itself should be used, sizes spacing there were still other tags that need adjustment for Telescope . For example: <code> and ...

Going back to Telescope. Between release 0.5 and 0.6 I was working on the Telescope project. I was assign to few issues during the 2 weeks period.  My first issue was to add test to make sure our application starts. This issue reference to the page where possibly I can look for solution. Ideally issue -363 should solve: a) make sure that our app is working b) allowed to hit correct root. After reading examples and documentation I have learned that there is 'start-serve-and-test' npm package that starts server, waits for URL, then runs test command; when tests end, shuts down server.  How to use this package: Install this package  npm i  start-server-and-test Add command to the script. In my case Telescope already has command to start server and command for the tests. This way I just had to combine both commands into one that I named "CI" and add localhost.  Indeed this package did not solve the intention  of the issue I was working on....

In this post I will continue to describe what I have done so far to complete my issue . This issue try to conquer problem of integrating React Experimental channel into the Gutenberg project. Steps that I have to do: 1. First I read through all the documentation about Experimental channel and what the ways to implemented. Experimental channel can only be implement on the projects that use React as external library. The reason is because if the project uses React for GUI and there is any bugs or features that can fail it can botched the front end. Gutenberg uses React as external library so that is why they try to see how Experimental will work on Gutenberg and on the other side to test new features. 2. Currently Gutenberg uses React 16.9.0. So after reading through the all documentation I updated version of the React on Gutenberg. Because Gutenberg uses React as an external library there are some changes to be done in the PHP. So here is my files with changes: Af...

This is the first part of release 0.5 and in this post I will talk about steps that I will take in order to solve issue #18216  in Gutenberg Project .  What is issue about: Find a way to integrate React Prerelease channels into WordPress/Gutenberg . React Prerelease channels allows Projects that are not using React as a user-facing application test features that are might will be available in the next releases. By integrating React Prerelease channels into Project community will help in improving React while testing out new features. What needs to be done in Gutenberg : 1. Install Next or Experimental channels  (as I'm waiting for respond which channel I have to integrate Next or Experimental I will talk for now only about Next channel ) inside of the project  In package.json  change version of react and react-dom to  "next" so package.json will look this way: 2. Set up CircleCI or Travis CI in order to run occasionally tests. ...

This is the end. The end of not just release 0.4 but also the end of semester. Many things were planned but as usual not everything is done. I completed 2 issues( external , internal ) and 2 PR ( external , internal ) as were required and still had some extra time and I wanted to keep working on other issues. Indeed, when I reach this last week before exam I realize how time consuming extra work could be. Anyway, I did my best to accomplish at least something. 1. While I was working on my external issue  I have learn and review few things from C++. My goal in this issue was to increase performance of the compiler. In this snipped of code calling _STD invoke(_STD declval<_Types>()...) is very expensive in the meaning of performance. That is because template function invoke() is implemented by calling static function call(). So my task was to use _Invoke::Call(), and this will increase performance. 2. In my internal issue , I faced some problems. I was not able to run w...