deciduously / attendance Goto Github PK

forms and utils

Turns out you can't select the text in an alert. Who knew.

e.g. Monday (3/5/18)

Maybe make a very simple GUI thing that just pops up as a confirmation

Instead of pasting style/script in by hand, make it happen automagically

Just static now - have it only show how many are here

It's holding up your mock roster

Should be able to largely re-use code - only difference is that these will NOT be buttons - just displaying the state

Have it check against the absences, and not add if the kid didn't come

Right now there's no way to see quickly which rooms we haven't called yet vs. which we have but had no absences to report

That's what ya gotta do next.

On reading in the csv, insert all the kids in that module. Only expose GET endpoints for name and stuff. The only PUT for a kid will be to toggle a KidRecord.

Take is as a POST request from cljs-ajax tied to the same buttons you've already got. have it do both until you port the frontend.

Might be overkill for this project, but it's a good learning exercise - and as this thing grows it will only help.

You've already structured it somewhat in line with what you'll need

Stored as map keys, which do not guarantee an order - not ideal from a usability perspective. Alphabetical sounds better.

Instead of a specially formatted single day CSV, take a raw Schedule By Week report

Use an individual url for each class to go for their own roster. Compojure can help with this? Load the roster from the server, and have a save feature to persist changes back

Or at least highlight infractions

Pilfer from deciduously-com, but in its own namespace now

You're doing something silly somewhere.

pos-hash is silly, you should remove that to close this but I think it's not the culprit here.

for both roster and add hours

For learning/showcase purposes, build your back either with a good template it with Rocket, and decouple the frontend. At first you can keep the Reagent version, but either port it to reframe or redo it in good old JavaScript/React Native

• Daily sheet to match handwritten record
• Daily email text in HTML format

Instead of logging to the console

You filthy animal

It got big

Currently, the app includes trailing empty fields in the headcount, making it look like all classes are the same size as the largest class. Just lop off empty fields when reading the CSV

Something like (transform [:roster #(= idx (:idx %))] #(update-in % [:here] not (get-in @App-State [:data])

Assuming I've split app-state into something like {:data {:roster {} :core {} :extended {}}}

User request

Some patterns ripe for pickin' out there.

Blocks aren't working - would rather they were responsive.

RESTfully, with bidi

copyright link, github link

We need Windows builds and Linux 32 bit builds

Either lean on localStorage or allow exporting and loading a dump of the RAtom to file

I need a server process that will expose a simple API for the individual class pages to talk to the database

:roster :core :extended - schedule maps just point to idx hash in :roster

Eventually xlsx.

Specter might be the right choice, but instead of bashing your heard against the wall on the deeply nested transformations, read the raw data into the data structure that you want.

Maybe read all the kids into a map with a unique I'd, and then populate a whole separate two tables with the schedules referring to the other map.

Process additional hours, respecting capacities, i addition to propagating absences to extended day

This might be the way to go at work.

Website

• Component - can reuse, probably, just no buttons
• Report - add to the end

do it

Instead of just hashing the name, assign some sort of other unique idx. This will require some thought as I'm currently relying on the deterministic nature of hash - it's called separately on strings and leverages the fact that it yields the same result to function properly.

Instead of hardcording the string in-memory

We know the current count from the names list - only need the max

Now that you have a server, why not add more functionality? This could be used for the order aggregator too!

I think you need \r\n, not just \n