| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
It's looking pretty powerful and functional already.
|
|
https://vndb.org/t950.1388
|
|
|
|
|
|
The old 'Chinese' option should not be available for selection in new
entries, but I'll have to fix that later.
|
|
|
|
Fixes https://vndb.org/t8242.530
|
|
I originally created the language flags with a 50% alpha channel so they
wouldn't stand out too much (they're *really* bright at full opacity),
but I had forgotten to do that with recently added icons so it became
somewhat inconsistent. Doing this in CSS has the additional advantage
that I can now restore the brightness in certain cases (for "bold"
language icons, handy if mouse-hovering them may do something).
(Indicentally, this also makes icons.opt.png 100 bytes smaller. Not like
it matters much as I had originally planned to replace the language
flags with SVGs and make everything much less efficient, but I can't
make icons that render well at such a small size so I suppose we won't
be getting rid of PNG icons for a while)
|
|
Removing old PNG icons, one by one.
|
|
Still kind of experimental, let's see how people react.
Icons contributed by eacil. Some are colored versions based on the SVG
icons contributed by xy2, some are vectorized versions of old icons.
These retain much of the legibility of the old png icons by virtue of
not being monochrome. At least for the dark skins. I may experiment
later to see if the monochrome icons may be a solution for light skins,
now that I have the infrastructure in place anyway. Not sure I really
want to maintain two icon sets, though.
I used scour to optimize the SVGs for size, but they're still rather
less efficient than the combined PNG sprites. Maybe I'll use an SVG
merge trick later, but that tends to be less widely supported among
browsers.
Closes #30.
|
|
Yay!
There are no more request handlers in the VNDB::* namespace and no more
Javascript in data/js/. This cleans up a lot of old legacy code that
wasn't fun to maintain.
|
|
|
|
Had been planning to use a more powerful preprocessor for CSS for a
while, so that I can also reorganize and clean up the CSS a bit. The
cleanup will come later, this is the first step to reorganize the build
system a bit and remove skingen.pl.
I moved all generated static assets to static/g/ (for _g_enerated),
including icons.png and js files. This simplifies management of
static/f/ and static/s/, which are fully in git.
Skins are now defined as sass files in css/skins/ with their images in
static/s/ using plain directory structure.
|
|
|
|
For some reason it wouldn't always show up with a 1px padding.
|
|
- Homepage: Add a little margin below the box headers
- VN pages / User stats: Add extra row to recent votes if there's no
link to reviews.
- VN pages / Staff: Fix underlining of links on mouse-over.
|
|
|
|
Much cleaner. Downside is that with long usernames and small browsers
widths the main title might get cut off. Think it's better to work
around that by relayouting the boxes.
|
|
https://vndb.org/t2520.516
|
|
Instead of the old table. Fixes the problem of the boxes not correctly
using the full width of the page.
|
|
This change is likely to be a bit controversial, but I tried to keep the
links and boxes at roughly the same location: VNDB discussions where the
announcements used to be, VN discussions where the posts used to be and
latest reviews on the lower left.
The "Random VNs" box is gone, despite the negative feedback from last
time I removed it. It really is superfluous with the screenshots and
random VN button in the menu
And switch to CSS flexbox to layout the boxes, because for some reason
these changes triggered the not-full-width bug that also occurs on the
tags/traits indices.
|
|
Fixes https://vndb.org/t2520.513
|
|
|
|
Honestly, I'd much rather see that feature go, but people will complain.
|
|
Making sure that the filters wrap indented below the query type and
and/or selection button.
|
|
It's still more intuitive to have the [+] button placed where the new
filters will actually be added, I guess.
This lines should make it much clearer what the full and/or structure
looks like. The implementation is terrible and really should not work as
well as it does.
|
|
Pretty much as described in https://vndb.org/t14995.2
Still needs autocompletion and autofocus.
|
|
Hopefully it's more intuitive this way, though to be honest I'm not
exactly sure it is. The switch between compact mode and expanded nesting
mode can be a bit surprising.
In terms of code organization, I added the and/or selection to the same
nesting node that handles the type difference. This provides better
control over how the queries are displayed, but removes the ability to
move the "and/or" itself into a parent node. Can be reimplemented if
useful.
|
|
Based on https://vndb.org/t950.843
|
|
|
|
This required some changes to the query model and encoded form, since it
doing this with only <= and => operators is too limited.
I changed the compact encoding of strings to only encode the length in
the type field for specific (common) lengths and fallback to an
end-of-string character for everything else. This leaves room for more
custom types.
|
|
https://vndb.org/t950.821
Flag is based on https://commons.wikimedia.org/wiki/File:Farsi.svg with
a light green brackground.
|
|
First attempt to add filters that reference database entries. Will need
to be refined.
|
|
Still feels kind of awkward, but it'll have to do for now.
|
|
NOW we're really getting somewhere!
|
|
Styling is still a mess, but feature-wise it's starting to look like
something.
|
|
Turns out my initial idea with a seperate FQuery type wasn't going to
work out all that well, and it's easier to handle this by treating
nested And/Or queries as just another field. The nested field type is
going to be responsible for some extra tasks.
Also added a global 'Data' type to pass around in various functions.
This would be needed at some point anyway, but now that nested fields
can create/manage subfields, we'll need to be able pass around the
global object identifiers thing already.
And while I was fixing this model, I had a brilliant idea regarding the
UI. I was originally planning an explicit split between "quick selection
mode" and "advanced search mode", where you could only build nested
queries in the latter. But it's actually pretty trivial to make the
advanced search mode look like the quick selection mode in the simple
case. Buttons to change nesting type and to add more fields will result
in a mode natural flow between the two modes. I've not implemented the
UI for that yet, though.
...to be continued
|
|
|
|
Add title/description to the dropdown header, so people know what
they're searching for. Rename 'and/or' to 'all/any' (not sure if that's
an improvement, though) and try to fully display all options and
languages in the tiny little dropdown box.
Also, proper use of mathematical symbols. \o/
|
|
Broken in 960946ac90a8da32953a4a21128d993f2049f8d1
https://vndb.org/t2520.506
|
|
|
|
Doing this on the main branch to make it easier to get early testing and
feedback. Not like I have anything worth testing now, but it's not like
this code is getting in the way of anything else.
(Unless the changes broke something unrelated, in which case it's extra
good to get that early testing)
|
|
Now featuring full pagination & flexible columns.
|
|
Anonymous votes count for 0.01, regular votes for 1 and overrule votes
for 1000. It's a bit crude, but ought to do the job.
Reason for this change is that most reviews don't seem to get any votes
at all. With this anonymous voting we can do some sort of
scoring/ordering even with potentially less reliable votes.
|
|
Seems to be working so far. I'll find the actual bugs in production.
|
|
Duplicating that code was really too much, the listings are way too
similar.
|
|
Now supports full pagination, displaying & sorting on VN count and
displaying & filtering the searchable and applicable flags.
|
|
|
