drkakku / question-tracker-app Goto Github PK

This will deal with how the basic flow of the programme will function
such as the data x will come from the front end and then go to field y in z format.

draw up a basic diagram for the same so the development will become a bit more seamless.

for a starting point for the app

I don't know it yet but I would assume that pandas df might be most convenient for me for large batches of data processing but might not be efficient for queuing and storing data so using either json or pySQL might be the way to go.

sql might be the beast way to do this because it would be easy to covert the sql to pandas df
logic being sql need's structure for it to store data and each datapoint can be modified also this allows us to directly convert the data to df.

we need to decide how the whole dataStructure will work

what we need is

storing the basic information about the

• question name,
• question url,
• start date,
• start time,
• end date,
• end time,
• total time in min,
• total time in sec,
• solved(bool),
• description path,
• solution path,

The above information can be stored in a sql type data-structure

for the question solutions and optional descriptions we need another solution

• Solution Path Array(will get the paths to the various solutions appended to it)
• Description path

I have some ideas for now for both from end and back end.

• For Front-end I want to use react as I want to learn it, It is dynamic so the data will be easily updated and reflected on both the front end and backend unlike flask where we have to reload the page for each update(Ajax can fix it but lets try something new).
• I am leaning towards the idea of using python as the backend as I want to do some "sexy" data processing and I am most familiar with it.

if you have any other ideas please leave a comment for the same

(this is a experiment from my end to understand how a semi structured project will flow and what all things are involved in it so that I can understand the common pitfalls that we might encounter while finishing a project)
(Lets see how much time this "simple app" will take)

the goal for this change is the better management of the repos and more flexibility for the project.

This repo will house the backend of the project and will be restructured accordingly in the future changes.

please keep this in mind while performing future work on this repo.

thanks
regards