icssc / antalmanac Goto Github PK

pygal graphs not working on either, isee blank
i thinkn just hafta settle for noninteractive graph on those

• Add "About" button to navbar
• Create a popup module (similar to the notifications one but bigger) for information about the project.

Information to include

• How we're maintained by ICSSC Projects
• Link to Discord (discord.gg/GzF76D7UhY)
• Link to GitHub

Create functionality to use PR for NOR waitlist closure!

is the current layout. We should come up with a more compliant and aesthetic design for this.

Design needs to integrate an image carousel since multiple images are available in buildingCatalogue.js now.

I want to add a little box/area where we can put in information about changes, news information, etc. We need to implement a backend endpoint that serves this data to the frontend. We can rapidly and easily change the information displayed by editing the mongoDB with the information we'd like to serve. This would be good for instances where we announce new features or changes or even notices if our services are unavailable (like AANTS) etc.

• Create datatabase location and data model
• Create API endpoint
• Implement frontend

When changing color of events to light colors, font color should change accordingly for better visibility. Also add border in case of white.

Seems like the f18.json file doesn't exist in the dir: src/components/AlmanacGraph.

OpenMaps has way better detail on the UCI campus but doesn't allow using its tile servers in production. Currently, we use mapbox but that has less detail on the campus buildings.

To reproduce: Add a course, like MATH 2A (44000 from Spring 2020) then open the tooltip for it. Then, search for AFAM 40C (20210 from Spring 2020) and add it. The tootip will suddenly shift to the AFAM events.

currently enrollment history data are kept in a .txt file
very not safe and very inefficient
need to implement sql system asap!

Bug Reproduction:
-go to mobile
-open drop down for advanced search

Fields overlap each other and the search button
https://media.discordapp.net/attachments/558501572456480780/582630921749004289/image0.png?width=373&height=663

There are many instances where we used inline styles for debug/prototyping (and out of carelessness) that we can move to use the standard. This will allow us to easily inject global styles (better dark mode support) and also manage styles at a glance easily.

var leads to hoisting and and should be avoided in modern ES6 code base.

It takes two seconds to get the search result back for searching for all CS classes. I noticed that the response time is directly proportional to the number of entries returns back.

Unintuitive design
Need to be reflected everywhere

The result page for searching all class in CS is super long and it takes a long time to scroll through.
It would be nice to only show an overview of each course on the result page. And we can click on each class the expand to get a detailed description.

This was moved to the backlog because it required more work in that we should prevent registration if someone hasn't loaded in their username.

This is an really amazing project in technical aspects. You guys solve many technical challenges that the AntPlanner was not able to solve. But from a user's persepctive, this app does not offer enough reasons why I should switch from the AntPlanner, which is what I am really familiar with, to the AntAlmanac.

One issue most of AntPlanner's predecessors have is that they look and function exactly the same as the old AntPlanner. There's a weekly calendar on the left half of the page, there's a place where you can search for classes on the right half. You can save or load a schedule using a unique ID. And you can add a class to the schedule by clicking on the class tile.

It's okay to borrow ideas from other apps. But AntPlanner is a crappy app, and that's why you guys are trying to build something that's better. AntPlanner is just an app that a random dude hacked together over a weekend. He didn't design this thing at all. He just grabbed a calendar from a library, put WebSoc into a iframe, then stuff them together in a single webpage. He didn't even bother to add a "Add" button, instead you just click on the class tile to add a class.

I like the material UI that you guys built. It looks really pleasant. And I like the features you guys added here and there. But there no appealing reasons why I would prefer AntAlmanc than AntPlanner. Both of them are the same, it just that one of them has a more modern GUI. I hope you guys can look into some other popular calendar apps outside of UCI, and build something better that the users can just ditch AntPlanner right away.

• Implement a carousel for multiple images
• If multiple courses are at the same location, show number of overlapping courses and list all courses at the location
• Use addedCourses instead of eventsInCalendar to create markers

When searching for a class, the user must provide at least one of the following:
GE OR Department OR Course Code/Range OR Instructor.

If all of those are missing, the search button should be disabled.

Add action to reset forms

#62 related

Instead of adapting the desktop site to be mobile compatible with responsive design, I think we should design a fully mobile experience and deploy on m.antalmanac.com or something like that.

Right now the bundle (which you can get by running npm run build inside the client directory) stands at ~6.8 MB. This is significantly smaller when g-zipped, but is still way too large and could be trimmed down. We should look into webpack minification customization, make sure tree shaking is working, and also figure out if we want to bundle images and other static files.

• Change vanilla HTML components to Material UI components
• Give each cell max-width so that every table aligns nicely
• Change text and section type colors so that they look good with dark mode
• See if we can optimize mounting of various modals etc (also avoid having every single table listen to the Flux store which warns as a memory leak)

Some have important information that users might inadvertently miss out on.

It's slow to scroll when hover the mouse over the course code on the search result pane. It's normal if I place the mouse somewhere else.

AppStore contains the notification toast/snackbar variables.

https://material-ui.com/components/snackbars/

Issue

Potential Causes?

After some digging, I have some guesses

• Something to do with position: relative in .MuiButtonBase-root because disabling it in the inspector "fixes" it but causes problems with the buttons themselves.
• Something to do with the z-index being manually set?
• This article mentions something about absolute vs relative, and which gets the priority during render

This occurs both on the calendar and in the added classes list:

I'm still able to click the transparent circle to adjust the color of the class.

For accidentally swiping back in the app, which cleared the schedules the user is drafting.
There should be a confirmation to exiting or hitting the back button.

When accessing older schedules on both mobile and desktop (specifically when the window is minimized for desktop), error occurs with getDay variable, declaring it as undefined. Newer schedules work perfectly fine.

• Disable "Add Event" button in modal until boxes have been checked to select both the day(s) and the selected schedule(s)
• Add a tool tip message over disabled "Add Event" button indicating that the days and schedule boxes need to be checked.
• Cancel button should clear the event name

Endpoint format: https://zotistics.com/?teacher=PATTIS+R.&selectQuarter=Fall&selectYear=2020-21&selectDep=All+Departments&classNum=&code=&submit=Submit

Implement "Sign In with Google"

We'll need to mention what information we're storing (course codes, schedule names, etc.) and what information we are tracking (Google Analytics).

Google Analytics might provide specific language for us to include in our privacy policy.

• Add project description
• Add screenshot of project
• Add history of project
• Add technologies used

Right now, if you search for classes, then go to the maps or added classes tab, going back to the search tab will show you the form. We need to keep the search results pane mounted somehow, with little cost to performance.

Currently, the code base is hard coded with some external URLs that can change over time. It would be better to extract all of them into a single configuration file. One reason for that is: we might need different configuration for local testing than the actual production build.

These are some places to look out first: https://github.com/the-rango/AntAlmanac/search?q=amazonaws