| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
I found myself forgetting to add a file to $JS_FILES in the Makefile
several times now, and with Perl and Elm modules being detected and
loaded automatically, it feels weird not to do the same for .js files.
This embedded order trick is ugly, but it's pretty simple and gets the
job done.
|
|
|
|
|
|
Dynamically updating the visibility state of the "this item is public"
icon kind of sucks. But meh, you really want that state to update
correctly.
|
|
The order in which .js files are concatenated is (and always has been)
important, so rather than relying on name order I've changed that to an
explicit $JS_FILES list in the Makefile. Less convenient, but at least
we have more freedom regarding .js file naming and organization now.
Rather than encoding the Elm flags as JSON in 'data-' attributes, I've
added a system for global page variables (pagevars) where the Elm flags
are now stored separately from their HTML tags. This has the advantage
of more efficient encoding (no more "s), faster parsing (just a
single JSON.parse()), and easier/more efficient modification of the Elm
arguments from JS. The pagevars provide a unified way of passing other
variables to JS as well, which I've used to deduplicate the list of
labels on the new ulist page. That shaves off a good 40 KiB on the page
size for a typical listing.
Whether all of this actually improves the page loading time, I don't
really know. Most of the slowness in Firefox seems to come from simply
instantiating many <input time="date"> objects.
|
|
|
|
Very much experimental. I'm not sure this is even the right model.
|
|
This version requires that all .elm files given to 'elm make' export a
'main' function, so we can't pass internal libraries anymore. I didn't
feel like maintaining a separate list of entrypoints, lazy workaround:
grep for elm files with a definition of 'main'.
|
|
option
Elm has a bug where the 'selected' attribute is not properly propagated,
that's fixed by patching the generated JS.
Also moved Ffi.js one level up, as it's important that that file is
loaded before any Elm modules are initialized.
|
|
And add a small 'formField' function to shrink the Elm form generation
code a bit.
|
|
|
|
Most of this is copied from v3. I did improve on a few aspects:
- db_edit() and db_entry() use VNDB::Schema rather than dynamically
querying the DB. This has the minor advantage of a faster startup.
- The Elm code generator now writes to multiple files, this avoids
the namespace pollution seen in v3's Lib.Gen and makes the dependency
graph a bit more lean (i.e. faster incremental builds).
- The Elm code generator doesn't update the timestamp of files that
haven't been modified. This also speeds up incremental builds, the elm
compiler can now skip rebuilding unmodified files.
- The Elm API response generator code now uses plain functions rather
than code references and all possible responses are now defined in
Elm.pm. Turns out most API responses were used from more than a single
place, so it makes sense to have them centrally defined.
The doc page preview function is also much nicer; I'd like to apply this
to all BBCode textareas as well.
(Elm.pm itself is ugly as hell though. And we will prolly need some HTML
form generation functions in Elm to make that part less verbose)
|
|
This gets rid of global.pl, config.pl and config3.pl and uses the
cleaner config3.pl format for the config file. The config is easily
accessible from anywhere by importing the new VNDB::Config module; The
global $VNDB::S,O,M,ROOT variables have been removed.
Sorry for all the churn...
|
|
|
|
I think this is the last one. 'make' in a development environment is now
beautifully fast and 'make prod' generates nicely small assets.
(arguably we could have an even faster dev setup by not generating an
icons.png in the first place, but then we'd need more code to
differentiate between dev & prod, which is also a pain)
This change does remove the "slow" option that would use the compressed
image size in the optimization algorithm, but I hadn't used that option
for a while anyway, it takes an hour and only saves about 100 bytes.
|
|
Similar to previous commit.
|
|
This rather significantly speeds up development builds. Also simplifies
skingen.pl and its config a bit.
The new compressed files are written to /s/*/style.min.css{,.gz}, it is
up to the web server to serve those instead of /s/*/style.css.
|
|
This way individual Perl modules can add stuff to the generated Elm
code, without having to edit a central file.
That's only used for forms for now, though.
|
|
I was getting tired of having to keep two branches up-to-date with the
latest developments, so decided to throw v3 into the same branch - just
different files (...which will get mostly rewritten again soon). The two
versions aren't very different in terms of dependencies, build system
and support code, so they can now properly share files. Added a section
to the README to avoid confusion.
This merge also makes it easier to quickly switch between the different
versions, which is handy for development. It's even possible to run both
at the same time, but my scripts use the same port so that needs a
workaround.
And it's amazing how often I break the Docker scripts.
|
|
|
|
|
|
Fixes a 'make' on a clean checkout
|
|
...unless I missed something.
|
|
This has been mostly automated.
|
|
This changes quite a bit to the way the editing functions work. Because
these functions are very repetitive and it's easy to keep things out of
sync, I created a script to generate them automatically. I had to rename
a few function and table names for consistency to make this work.
Since database entries don't have a 'latest' column anymore, and since
the order in which tables are updated doesn't have to be fixed, I
dropped many of the SQL triggers and replaced them with a
edit_committed() function which is called from edit_*_commit() and
checks for stuff to be done.
Don't forget to run 'make' before importing the update script.
|
|
First part of a Javascript cleanup.
|
|
It became a bit of a hassle to keep updating that file manually in Gimp.
This script performs surprisingly well for our set of icons.
|
|
If you don't have any style.css files yet, make won't know what files to
create. It does with this shell pattern.
|
|
I forgot that the static domain is only intended for files that are
never modified. Or at least, not without a URL change. The tags.json.gz
doesn't fit into that.
|
|
This isn't documented yet.
|
|
|
|
And added an update_2.23.sql file which now also includes the previously
added indices. Currently, this update file can be run as often as you
want, it doesn't make any noticable changes when you run it on a
database that has already been updated. (i.e. I can update the main site
without a new release)
|
|
Required in order to search for hidden entries (obviously :P)
|
|
+ Fixed makefile
I haven't been able to properly test this yet as a bug[1] in PostgreSQL
9.0.4 is preventing me from editing release entries.
[1] http://archives.postgresql.org/pgsql-bugs/2011-08/msg00119.php
|
|
|
|
|
|
|
|
Not very useful at the moment, but will be used to improve several other
things.
|
|
There may still be some bugs present and I've only converted the points
where TUWF is incompatible with YAWF. The new TUWF features are not in
use yet, I'll do that later on.
Note that, in order to run the new code, TUWF must be installed on your
system. The configuration for the TransAdmin plugin has also changed.
Other than that there shouldn't be any issues.
|
|
This is the first step in adding support for overruling tag votes by
moderators.
Also removed some unused options from dbTagStats(); the
tag-vote-stats-by-user pages have been removed in the previous VNDB
update, which was the only page using these additional options.
|
|
This can be seen as a partial revert of
0a4f97f0186d6941a4cab2e3bd05201f1fed1441.
I used to think using NULL for special values is more "correct" in
database terms. But in the end I guess I should be aiming for whatever
solution is easier. Both are "correct" in a sense anyway.
|
|
|
|
|
|
This greatly reduces the size of the Javascript file. The compressed
size has been reduced with about 9kB, and is now a total of 14kB for
en.js. A nice property of this is that more translations can be added
without increasing the JS size.
While I was at it, I made jsgen.pl also replace mt() function calls in
cases where an exact TL string was requested without any additional
arguments and/or formatting codes. This helped reduce the compressed
size by about 1kB.
My aim is to keep *all* the JS code of VNDB smaller than the jQuery core
library, as a general "fuck you" towards users of large and bloated JS
libraries. We must keep the VNDB page loading times lower than that of
other sites, after all!
|
|
Apparently the trick didn't work, and for some reason I only noticed
that now.
|
|
This is somewhat eaiser to read and maintain
|
|
This effectively removes compatibility with all PostgreSQL versions
below 9.0.
The use of the WHEN clause has two major advantages:
1. Performance: Trigger functions aren't executed when they don't need to.
2. Easier and more general trigger functions; as some of the logic has
been placed in the trigger definitions now.
|
|
TODO: add links to these feeds from the site
|
