Tuesday, 7 March 2017
Second Release Blog
Well my implementation looked easy at first moment, but it proven to be a little bit more challenging than I thought.
I proposed on Issue #607 to prompt the logged out user if their files changes had been changed or if the file was already saved.
I discuss the first ideas with professor David and he guided me through out the logic behind Brackets saving files locally to the users browser. He showed me the file main.js had the logic hat whenever file was considered dirty it will wait five seconds before save it or immediately if the user jump between files.
Later after a few other ideas exchange inside the issue page professor David trying to make the problem more understandable he told me to look for how other developer had approached events that happened between brackets/bramble and Thimble.
That made the code much easier to navigate and understand, I was able to implement a few lines of code, but I could not test it since I was unable to create the path reference between the files which hold the logic.
Finlay after much struggle I had to look for professor's help again since I could not figure out how to create a variable with the path to the file and finally test my changes.
It was very challenging and I learned a lot about JavaScript and even more how to rely on the community and other people that are willing to help me understand complicated code.
Right now the initial idea is partially implemented, but I will create another issue this time on Thimble repository and use the second part as my release #0.3.
Monday, 27 February 2017
Lab Blog
The fix that I proposed to complete is not exactly a bug. It is acutely an accommodation and facilitation to the user of thimble.
After I fix a but on the saving pattern when the user was logged in. Professor David Humphrey asked me to go further and now display something now whenever the user is not logged in and make changes to the code and those get saved locally by brackets to the browser.
I also invited Luke Pacholski to give some hints and his opinion as a designer to how it should be done.
The biggest challenge is to handle the references between Brackets and Thimble, but Professor Davide showed me how to find in the README.txt other methods that are using a similar reference that I might have to use.
After I fix a but on the saving pattern when the user was logged in. Professor David Humphrey asked me to go further and now display something now whenever the user is not logged in and make changes to the code and those get saved locally by brackets to the browser.
I also invited Luke Pacholski to give some hints and his opinion as a designer to how it should be done.
The biggest challenge is to handle the references between Brackets and Thimble, but Professor Davide showed me how to find in the README.txt other methods that are using a similar reference that I might have to use.
Subscribe to:
Posts (Atom)