notiooo/pawtravel

A project in the course "Software Project" in 6th semester of computer science.

About me

I'm working as C++ Software Engineer at Nokia headquarters in Krakow, Poland.

Besides that:

• I love C++, but Python is my second language. It's where I started and it's what got me started reading my first programming books.
• You can follow my book reading progress here: https://books.grobert.eu/
• Computer graphics is my hobby.
• ...although I also try to play the piano in my spare time.

Projects that can be found on my website

Hall of fame

I think I'm proud of them in some way. At least for the time they were created

• MakeFarm
• Worms Similar Game
• Flappy Bird SFML Clone
• Grammar
• FlapANN

Recent Individual Projects

• MakeFarm
• Worms Similar Game
• Flappy Bird SFML Clone
• Grammar

Recent Group Projects

• FlapANN
• Nizer
• A* Assembly

Blog Posts :

• Arithmetic of decimal numbers with binary coded digits
• The way „The Onion Router" works
• What are "Heaps"? (for dummies)
• First post about a shark called "blahaj".

pawtravel's Issues

Web design and backend for navbar

Let this navbar search also be included in this task

Web design of the homepage

Please use the design from #9.

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Please work together with #59

Don't worry about voting system, it should be added by #57.

Hide secret key and add helper scripts

Project files should take into account the hiding of SECRET_KEY and the some scripts for other members to help them use the python environments.

Web design of the add travel guide panel/site

Please use the design from #24

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Web design of the add offer panel/site

Please use the design from #12

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Web design of the user profile

Please use the design from #13

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Design of detailed display of the offer

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue11 branch. Please base your work on the documentation provided.

Add possibility to modify travel guide

This task requires doing both backend and frontend!

Design of user profile

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue13 branch. Please base your work on the documentation provided. More details may be added later.

Within the user profile here is a split between displaying your own profile (when you're logged in) and the profile of other users.

Web application design

Please use the materials from pull #7 to keep the designs consistent. Please work on the designated branches for each task. This is the dev/issue(issue number) scheme. Please base your work on the documentation provided.

Please place completed tasks on the repo in the PawTravel/docs/design/prototypes folder and then in a folder with the name of structure:
#(issue number) - (name of the issue).

For example:
PawTravel/docs/design/prototypes/#14 - Design of the message panel

Use the materials from pull #7 as follows:

Tasks to do:

• #9
• #10
• #11
• #12
• #13
• #14
• #15
• #16
• #22
• #23
• #24

Add slug url for offer

Web design of the message system

Please use the design from #14

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Alert system

Please think carefully about how alerts work. At what point should they be checked? Maybe a timer every minute? Or maybe a check after every vote? It cannot be too tiring for the system. Please think over the model of how alerts are to be stored in the database, displayed or when they are sent. Also, please avoid duplication of alerts in case someone has alert for 100 votes and the offer has votes 99 -> 100 -> 99 -> 100.

Please cooperate with #45 and look at designs #15.

Design of panel with user alerts

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue15 branch. Please base your work on the documentation provided. More details may be added later.

A panel where the user can set the notifications displayed to him on new offers corresponding to his settings.

Design of the add travel guide panel/site

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue24 branch. Please base your work on the documentation provided. More details may be added later.

Design of the message panel

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue14 branch. Please base your work on the documentation provided. More details may be added later.

Message panel is a panel that allows to send messages to each other/conduct correspondence between users via internal mailbox.

Web design of the comments for the comment system

Web design of the main page of the Travel Guides

Please use the design from #22

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Don't worry about voting system, it should be added by #57.

Backed of the voting system

Have someone prepare a ready-to-use block/code and then inject it into offers and travel guides. Giving upvote/downvote cannot refresh the page!!!1!

And think about the model etc.

Add it for example to the: #59, #47, #39, #48, #41, #64, #65

Add basic frontend framework files connected with backend

Web design of the detailed display of the travel guide

Please use the design from #23

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Don't worry about voting system, it should be added by #57.

Prepare reference materials for design

Based on #1, create a common graphic style that will be used to create all pages in a consistent style. From #1 we need to select elements that we think are nice and relevant and then prepare a set of UI for lunacy.

This has actually already been done in #7 but an issue has not yet been created for it. To complete the formalities I'm opening this issue with the information that all three of us managed to come to an agreement and create such a set.

Web design of user settings

Please use the design from #16

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Design of the main page of the Travel Guides

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue22 branch. Please base your work on the documentation provided. More details may be added later.

Web design of travel guides main page

Please use the design from #22

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Please work together with #64

Don't worry about voting system, it should be added by #57

Basic project settings and Custom User Model

The most necessary basic design settings should appear here, along with the Custom User Model that we will all need.

Design of detailed display of the travel guide

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue23 branch. Please base your work on the documentation provided. More details may be added later.

Design of the homepage

Please use the materials the materials from pull #7 to keep the designs consistent. Please also use the suggested designs from #1. Work on this design should be done on the dev/issue9 branch. Please base your work on the documentation provided.

Design of user settings

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue16 branch. Please base your work on the documentation provided. More details may be added later.

Backend of the travel guides main page

Please look at #22. The work done should be similar to that in #59. Work together plx

Don't worry about voting system, it should be added by #57.

Develop project requirements and documentation

Assigned individuals are responsible for developing and creating the documentation available at this address: here.

Initial homepage proposals

I am asking everyone to create a design in the "Lunacy" app for the home page of the app. This will allow all of us to see your style expectations, requirements and design vision. In the meantime, please take the time to refine your vision of what the project is about, which we will discuss in more detail.

Please pull-request changes while adhering to the seven rules of a great Git commit message.

Please also include this issue ID in the commit name. Also, please include in your change the exported images of the website design as well as lunacy project files. The Lunacy project and images should be included in a folder with your github nickname. The folder path should be as follows:
docs/design/prototypes/First homepage proposals/

Comment system

Users want to be able to go to their profiles and write to each other. Do not use extensions that add comments based on users from another service such as facebook or disqus!

Please, clicking reactions or likes must not refresh the page!

Backend of the homepage

Please work together with #39. Don't worry about voting system, it should be added by #57.

Design of login and registration panel

Please use the materials the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue10 branch. Please base your work on the documentation provided.

Backend for message system

It doesn't have to be dynamic (in real-time), but if someone has ambitions, go ahead. Generally, two users should be able to write to each other and read each other's messages. Their chat history should also be available for viewing.

Please work closely and talk to #44, and look at design #14.

Basic web design basis of the website

Need to create basic templates that will be used on almost each page. What we are talking about here is a basic.html that will contain basic meta-data plus possible places for additions such as {# block content %} that may by use by using {% extends 'base.html' %} before.

The change should also link the libraries and frameworks we use, such as "uikit" or "vue".

Fix the slug in travel guides

Backend for user settings

Please work together with #46 and #50

Web design of detailed display of the offer

Please use the design from #11.

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Don't worry about voting system, it should be added by #57.

Form for adding a travel guide

Please do the backend (forms, etc) for design #24 and please work together with #49 and #62.

Btw add there TinyMCE too, contact with #53.

Backend and models for the travel guide detail page

Please follow the design #23 here and please work with #48 and #61

Summary of all prototypes

The instructor asked that all designs/prototypes be put into one PDF along with a brief description and the diagrams currently created.
Please complete the document here.

Add possibility to modify offer

Backend for user profile

Please work closely with #43 and look at designs #13

Backend and models for the offer detail page

Please follow the design #11 here and please work with #41.

Design of the add offer panel/site.

Please use the materials from pull #7 to keep the designs consistent. Work on this design should be done on the dev/issue12 branch. Please base your work on the documentation provided. More details may be added later.

Form for adding an offer

Please do the entire backend (models, forms, etc) for design #12 and please work together with #42.

Btw add there TinyMCE too, contact with #61

Web design of the panel with user alerts

Please use the design from #15

If a backend has not yet been created for this, please leave the "placeholders" free, which the backend will fill in. If a backend has been created, please cooperate with the creator of the backend of this website, or have him adapt the content displayed to the current frontend.

Users system (including login/registration)

Please ensure that the login and registration page works properly here.. A system that allows to sign in with external services such as Google, Facebook or Linkedin should work properly. Apart from that, registration and login inside our service without external services should work properly.

Please think carefully about how this should be combined with our Custom User Model and how it will appear in the code and on the page!