/tech/ - Technology

s/package to try/package decided to try/

Interesting idea. Do you already have a public repo?

>>27282
Might set this up soon, even if it's proprietary there's no reason for it not to be source available. Just am fairly new to source control and so haven't even initialized yet.

>>27280
Most of what got done today was the functionality of all the buttons in the footer, but also the pagination, and front-end for the completed and delete buttons (not sure why didn't make these refreshes like everything else). The footer has sorting (by start and end time), the timezone button in the bottom right, and a view selector in the bottom left. The other major change was in reprogramming the way timezones were handled so as to prevent many errors that were occurring. In addition to these changes did a lot of tweaks to the CSS, making the navigation look a little less like that of an imageboard, and to make everything look nice.

Unlike my previous application am not going to pains presently to make this application work without JavaScript. It's riddled with hidden forms, and JavaScript, even the textarea, and accessing the page without a GET parameter, is JavaScript only, making it unusable on text browsers. It should be theoretically possible to add back most of the functionality for noscript users at some point in the future, if and only if the user knows the GET parameters. It may not be worth it.

So far today managed to make all the buttons AJAX which means the remaining two buttons (for removal, and completion of events) are also now usable. Other than this was experimenting with making a responsive and mobile friendly 365 view. Found a template on the internet and making it responsive resulted in a poorly formatted traditional Georgian calendar which isn't pictured. The reviews of the 365 view overall have been poor however, so am considering giving it up. Anyone have any thoughts on it? The idea is that there would be little color coated (by severity) circles in of the relevant calendar entries.

So far today fleshed out the rest of the interface for the kanban view. This meant adding a maximize button to the editor (last night), an optional text input form for groups, and a drop down for importance of the event together with the backend work necessary for this. An edit button was also implemented. Lastly a compressed view was added which will be the basis for a search functionality, though pagination is presently broken for this view. Further the groups do not yet have their backend implemented. My present goal is to have the kanban view relatively complete within the next two days making it seven days total for its implementation. After this the plan is to move to the three-sixty-five display assuming don't get more negative feedback on it >>27300 (though even this would be much appreciated).

>>27300
Finished getting the edit button to work sans-groups, and got the pagination of the search view to work. Otherwise have been fiddling with the CSS styles of the 365 and Georgian pages. Here's a picture of the poorly formatted Georgian calendar. It doesn't look good, especially compared to the "mahjong"-style, but the "majong"-style has a display ratio which is too skewed, in total it would only take up half the screen once scaled, or a little more. The margins could be shrunk a little at the expense some of a consistent style (this probably isn't the biggest deal). Am just a little disappointed so far today. Not sure if anyone has a suggestion as far as the UX goes.

Bumping even though haven't slid to the next page yet, hopefully no one minds.

>>27319
Made a few altered mock ups for the Georgian page (those for trimester, and quarter), and changed the color scheme back for the mahjong page. Didn't achieve much today other than this, failing to pick a second course for grad school, and watching television.

>The idea is to keep it very event focused, where the only way to discover threads is through a system of calendars, or private messages.
For people with OCD, why don't you add the option to subscribe to groups and compile a "mailbox", Usenet style.

>>27324
This is an excellent idea, cheers!

Got the (Georgian, and quadrimester) mock ups translated to templates and the views installed in the main program today, this means the localization is working as you can see from the images. The Georgian is a responsive view for the quadrimester which is the default. This felt like a decent compromise between the relatively unpopular 365 view which had much more information but took up too much horizontal space and the Georgian calendar which on most computers feels myopic. Overall it felt a bit better than yesterday.

Ah, was just able to get the day names to center and the month names to properly align, it's now looking far better!

Mostly been doing system administration things today see >>27383 but got a very small amount of programming done too. This was implementing the basics of the event system for the calendar views. It should be fairly easy to flesh this system out sense there is a lot of source that can be reused from the kanban view. Hopefully in a few days the system administration is all done and am feeling energized enough to resume some good work on this program.

Was back into things for a moment yesterday, though not fully. Main thing was some refactoring. Ended up making a Calendar class and merged the two views for the two pages. This should make implementing the error handling a little easier, and has already made supporting the various parameters near automatic.

Mostly just finished up the refactoring from yesterday today, but felt like a good deal of progress was made. The Calendar class greatly simplified everything from the views to the queries, and everything in between; fixing tons of bugs along the way; and expanding configurability. Though it had to be renamed Agenda, for now, frustratingly. Also got a little bogged down for a moment in a nine case case analysis for the construction of the object. The attached picture is a view of the quarter for mobile with a single event scheduled for yesterday. Hopefully tomorrow can begin to start adding more features to the views: namely search, and filter by importance, and the start_end, and continuous sort styles. Might end up doing some system administration instead though as still haven't gotten my new computer working.

I like the idea. Are you properly handling anti-XSS sanitization? Also: if you keep all CSS and JS in separate files you can set a very strict Content Security Policy https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP which is a very strong defense against XSS. Upstream we've been looking into making vichan compatible with it, but it will take a lot of work

>>27452
>Are you properly handling anti-XSS sanitization?
Will certainly need to look into this, it seems like it might be very helpful. There is a very trivial XSS as the WYSIWG editor outputs HTML into an input form, and this is used without escaping by the application this was not the case in the imageboard which had standard vichan formatting and did HTML escaping.

>>27452
>Content Security Policy
This reminds me of the OpenBSD pledge some, and seems like a good idea. There is apparently middleware support for my AGSI https://github.com/tmotagam/Secweb too.

Yesterday added a "start end" sort option to the search view. Got a few more small things done on this project today. Namely added a search bar, filter based on importance, fixed a bug that was causing all the match statements matching an enum.Enum in the program to default to the first entry, and some other minor bug fixes. This was most of the open tasks that needed to implemented in the calendar system. The other three major systems are the group system for inviting and accepting invitations to groups (needs to be written from scratch), the forum component which needs to be rewritten for reddit style threading (found this not too long ago: https://gist.github.com/bokwoon95/4fd34a78e72b2935e78ec0f40e7e49e1), and lastly the assessment component, which will not yet be documented here in detail.

Seems like this project might be put on pause while looking for bigger fish. In the mean time put up a source-available-style repository here: https://codeberg.org/jung/fasti Only update that have made since the previous message was to make the agenda class immutable with a builder subclass handling all the construction state. (this can be seen here: https://codeberg.org/jung/fasti/src/branch/main/fasti/agenda.py#L43). Might make a new thread soon with a new project or otherwise with a project ideas thread; have a few (typically) very large projects in mind in fact together they make up the bulk of a userland, but not sure which to pick, or if another idea might suite me better. Bumping since slid, even though it's likely the final post of the thread.

Am considering attempting to revive this project.
Have made a few commits to make it run on my machine.
Am currently reworking the month view, but it's a real mess (picrel).
Haven't got too much to say about it at the moment.

>>27553
Also this was stupid. There aren't really bigger fish for me.

Got some of the Unicode icons swapped out with SVG so that the rendering is consistent.
Changed some features of the style in general to be more consistent.
Made some modification to the CSS, and JS to get them to work well in Palemoon.
Swapped out the biweekly headed view for the standard weekly headed view.
Updated the README with install instructions so remember how to do it next time.
Am unsure how a significant dedication of time to this project would go.

>>29663
Got the rest of the icons converted to SVG.
Implemented a continuous mode for the events.
Switched the post form to use datetime-local.

Going forward think the post form needs to be split into two parts:
- One part for the type, dates, and groups to be submitted.
- A second part for the actual entry of the OP or web form.
Further there needs to be confirmation windows to confirm event removal and edits.
Two "gestures" need to be added to the yearly view:
- Click to select date ranges.
- Click on event to open them.
There is a ton that needs to be done to have various kinds of threads supported.

>>29668
Probably going to bail on the gestures, and got a popup to confirm event deletion, and setup the two step post form. The next major step would be to copy and paste the forum software from: https://codeberg.org/jung/arsvia This is the second major part of the application which has roughly the mantra "everything is an event, everything is a conversation."

>>29669
Am considering chucking the georgian view into the waste-bin of history and expanding the kanban view with a button (the option URL parameters is already available) to select date units to display, week, month, quarter, year. Properly aligning months for the latter three (unlike in picrel).

>>29679
Got week alignment to work when there's more than a week to display and to adjust as appropriate based on locale.
Realize there is a very large number of parameter combinations most of which have hundreds of states.
Further many of them interact or overlap in nontrivial ways that hasn't been sorted yet.
Mainly in that there are days, months, but also start, and end dates; it's unclear what specifying combinations should do.
Think if it's refined it may even result in a simplification or improved understanding of the queries.

>>29682
>Realize there is a very large number of parameter combinations most of which have hundreds of states.
Through the power of mathematics was able to find seven cases one of which was a pass which weren't wiped out by (tacit) assertions.
This process also clarified the way modes, sorts, days, months, start, and end all interact, to the great prosperity of all (even fixed a bug).

>>29693
Have a nascent (if not complete) reverse_search mode now.
Am unpleased with how the two search modes interact with month, start, and end.
Am thinking of a rather ugly extension to the arrows at the top such that it is similar to:

< 5/1/25 5/30/25 >

And having an additional numeric area for specifying the number of time units together with a drop down for the time units to the right.

>>29699
This is what that looks like, am satisfied.
Think the main functionality of this view is complete.
Need to reflect a little on the design of the groups page.
Or decide on whether to start on the threads next.
Groups are more central and should be easier, but threads are more thought and worked out.

>>29700
Decided to start on the groups pages next sense it felt more essential.

>>29704
Am seemingly too cooked to work on this today.
Can't even decide how to arrange the POST endpoints.

>>29715
Haven't made any really progress on the project today or yesterday, but did some administration.
Updated the project page and moved over all my commits and everything to a new username.
My old one is still visible here and on some parts of codeberg, but you have to start somewhere.
Think it's just better to have different usernames for different platforms; for things you don't want to associate.
Might also avoid posting the link to the source here in the future as a basis of further separating these persona.
Will probably continue with updates and images however, and no doubt it will be discoverable on this basis.

Here are some progress pics on the groups page.
The back-end is a little more complete than the front-end.
But this is a live page, and not a mock-up.

Would like to add removal buttons, and have three check-boxes to the right.
These check-boxes are to toggle visibility of email, subgroups, and events.
Also would like an unaccepted groups area for rejected and unprocessed groups.

This was about the full extent of the concept one had in mind for this aesthetic of the groups.
Only thing really missing is that would swap the buttons for SVGs but this would make it worse.
The tree looks decent when the leaves are hidden, but it's ugly when they're rendered.
Not really sure what to do, think am lacking in inspiration, meaning some else's work.

Cleaned up the CSS a little more. Need a solution to dynamically make the groups take up less of the screen.
Something to do with flexboxes no doubt.

>>29831
>Something to do with flexboxes no doubt.
Had the idea that when clicking the expand also expanding horizontally to fill the width of the body; so implemented this.
Also setup the flexbox stuff, so if the screen is small it takes full, otherwise it attempts to divide into thirds and flex-grow: 1;
Next up are the SVG icons, Websocket scripts, (backend) group specific calendar, (backend) combined groups calendar, and (optional) trash can.

>>29867
Got the SVGs dialed in and then decided it was better off with simple text buttons.
It seems to look best in landscape on mobile atm, though in general mobile is not entirely well supported.
Namely there are issues with the menu button overlapping the content and making it inaccessible.
Not sure about the best way to go about fixing that is.

Also wrote some checks to see if the user is a member of a group before displaying it to them.
And also to add them automatically to a group if they're creating it.
And another set of checks to make sure only the creator of a group can edit it.
And to make sure there aren't duplicate members or subgroups.

wish could have thought of something more interesting to make than a calendar forum.
Might have much more motivation to complete it if this was the case…

>>29873
Had several ideas for something like https://memex.garden (before knew of it), a microEmacs, an RCS chat.
Probably a skill issue that what was implemented was only a calendar and forum in python.