You are browsing as a guest. Sign up (or log in) to start making projects!

OpenAtlas

  • 3 Devlogs
  • 5 Total hours

OpenAtlas is a knowledge atlas that automatically organizes everything you save from the web into projects . A browser extension lets you instantly capture links, while the system classifies, tags, and links them so you can rediscover information without digging through tabs or bookmarks.

Open comments for this post

2h 25m 20s logged

OVERVIEW:
Began work on front end! Nothing is functional atm, and it doesn’t look great, but the framework is there. All of the projects and middle stuff are placeholders. It does look workable though. And also I actually figured out newlines?!?!?!?!?! Thanks random guy on slack

NEXT STEPS:

  • Improve looks
  • Other pages
  • Improve extension design

    CHALLENGES:
    ‎- Variables in css, they should be helpful for later editing of design, and was very interesting to learn.
    ‎ ‎
    For this devlog I decided to also highlight some challenges that have been persistent throughout the projects, those are below.
  • Error messages. In an effort to improve the opensource-ness of my project, I have been working to include fallbacks and useful error messages. It is not only helpful for my own debugging, but for everyone else trying to use or replicate my project!
  • Proper naming conventions for variables and functions are also part of this effort for me, in the past I just make everything camel case, but recently have been trying to do better with this.

OVERVIEW:
Began work on front end! Nothing is functional atm, and it doesn’t look great, but the framework is there. All of the projects and middle stuff are placeholders. It does look workable though. And also I actually figured out newlines?!?!?!?!?! Thanks random guy on slack

NEXT STEPS:

  • Improve looks
  • Other pages
  • Improve extension design

    CHALLENGES:
    ‎- Variables in css, they should be helpful for later editing of design, and was very interesting to learn.
    ‎ ‎
    For this devlog I decided to also highlight some challenges that have been persistent throughout the projects, those are below.
  • Error messages. In an effort to improve the opensource-ness of my project, I have been working to include fallbacks and useful error messages. It is not only helpful for my own debugging, but for everyone else trying to use or replicate my project!
  • Proper naming conventions for variables and functions are also part of this effort for me, in the past I just make everything camel case, but recently have been trying to do better with this.

Replying to @Jack_

0
2
Open comments for this post

59m 30s logged

OVERVIEW:
Linked server to a database! I am using sqlite to store all data, which was really fun to learn. Whenever the server receives a packet, it pushes it to the database, which updates in real time. Also set up framework to have get requests from the database, so data can be read. Also turns out I lied about being able to use devlogs correctly, my method for newlines in these devlogs just stopped working, its great.
NEXT STEPS:

  • Begin webui, I decided to use react after some research because it appears to be much more useful of a skill than just vanilla html, css, and js, which is what I used for webos.
  • Improve extension design
    CHALLENGES:
  • I learned a lot about databases which was really interesting, however I found it difficult to figure out how bits worked in the database as well as learning how sql requests work
  • It was also difficult to be able to see the database, it isnt a necessity for the project but is really nice so you can actually see the state of the project data

OVERVIEW:
Linked server to a database! I am using sqlite to store all data, which was really fun to learn. Whenever the server receives a packet, it pushes it to the database, which updates in real time. Also set up framework to have get requests from the database, so data can be read. Also turns out I lied about being able to use devlogs correctly, my method for newlines in these devlogs just stopped working, its great.
NEXT STEPS:

  • Begin webui, I decided to use react after some research because it appears to be much more useful of a skill than just vanilla html, css, and js, which is what I used for webos.
  • Improve extension design
    CHALLENGES:
  • I learned a lot about databases which was really interesting, however I found it difficult to figure out how bits worked in the database as well as learning how sql requests work
  • It was also difficult to be able to see the database, it isnt a necessity for the project but is really nice so you can actually see the state of the project data

Replying to @Jack_

0
1
Open comments for this post

1h 12m 46s logged

OVERVIEW:

This time was spent creating the basis for what OpenAtlas will become. I created a basic extension, imported it into firefox, and made it communicate with my server. I learned a lot about how extensions work. It should also be backwards compatible with Chrome. I can’t wait to learn about databases. Also, I finally figured out how to properly format devlogs, HackClub please make this easier, just make newlines be newlines, I am begging you!

NEXT STEPS:

  • Create and figure out how to use databases
  • Start WebUI
  • Improve extension design

CHALLENGES:

  • Learning how to use a manifest in my extension and how important they are
  • Learning how javascript can interact with a browser through various commands
  • Learning how servers work and can be interacted with

OVERVIEW:

This time was spent creating the basis for what OpenAtlas will become. I created a basic extension, imported it into firefox, and made it communicate with my server. I learned a lot about how extensions work. It should also be backwards compatible with Chrome. I can’t wait to learn about databases. Also, I finally figured out how to properly format devlogs, HackClub please make this easier, just make newlines be newlines, I am begging you!

NEXT STEPS:

  • Create and figure out how to use databases
  • Start WebUI
  • Improve extension design

CHALLENGES:

  • Learning how to use a manifest in my extension and how important they are
  • Learning how javascript can interact with a browser through various commands
  • Learning how servers work and can be interacted with

Replying to @Jack_

0
1

Followers

Loading…