Posts

Final release - 1.0

It has been few days since I planned to write this post. It is very difficult to put all thoughts together. This is a final blog post for OSD700 and I wanted to make different than others. I have rewrite this post already for the third time and seriously I am just giving up. I read through others post to find some ideas and inspiration.

How did I get to OSD600. My friend told me that this is a "nice to have" course. Why did she say that I don't know she never take this course herself. When I saw that requirements for this  is WEB422 and JAC444 I decide to give it a chance. Indeed that was only course that I was looking forward. Why? Well unfortunately I was not lucky enough to have good experience with web development. Since WEB222 I realize how much I don't like web development. I think it's related to the professor that teach me this course or may be I just was the one who prefer C/C++ (I know its sounds weird, but I always enjoy this weird old language). Anot…

Release 1.0 - Lazy Loading

Image
In this release I have covered one issue that add feature of Lazy Loading images of the blog post. It took me a little bit of time to add this feature and some help from my professor.

What is lazy loading?
When user open a website that consist of many big images and videos it will take some time to load all of them. This could be an issue because some users does not have time to wait until all media will be loaded and simply will just close the application. Luckily there is feature that allowed to load images while user scrolling through the web page.

How do I know if my application uses lazy loading feature?

That is not to hard to check. Here are steps:

- Load web page
- Open developer tools
- Select network
- Navigate to IMG

Under the list of already load pictures (if any or all) there will be usages showing how much resources were used. If during scrolling the page the lower number of used resources is increasing once the image appear in the view its mean application using lazy lo…

Release 0.9

Image
Last few weeks were pretty busy with studies. All school has moved online and students and professors had to adjust to a new way of study-teach workflow. For this release I was working on few front-end issues and I would like to share what experience did I gain while I was solving problems.
My First Issue was about making word Telescope in the top-left to go to home page.  
At first when I look in this issue I did not know in what kind of problems I can run into. Seems it's only add link to the title
 This is the only line of code I have to do for this issue. By doing this I have learn something new.  If I add <Link to='/'>{title} I assumed that {title} should still keep the style that was assign in the <Typography>  because I haven't specify any new className in the <Link> but the outcome was different than I expected From: To:
Uhhh...this is not look right due to our website design. So basically was giving "Telescope" default colour and u…

"Windows virus" or problems with Docker Toolbox

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, but myself never feel that pre…

Yesterday I had a hope... Or release 0.8

Image
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 break the long wor…

Release 0.7

Image
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 <pre> loo…

Release 0.6

Image
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. This package run tests on the backgro…