| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Haven't found any bugs this way, yet. I doubt there'll be any problems,
but it's a nice new feature that could help quite a bit. :-D
|
|
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.
|
|
The check is quite basic and you can easily get around it. It's just
intended to warn about common mistakes.
|
|
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.
|
|
And rewrote the expand/collapse JS/CSS code so that the difference
between expanded and collapsed view is merely the class of the
containing table. This way the JS code doesn't have to pass through the
table rows and is thus noticeably faster for larger tables (i.e. /p65).
|
|
Primary reason for this change is because Algorithm::Diff::Fast isn't
all that fast for character-level diffs. :-/
|
|
It's an awesome feature now. :-)
|
|
A nice expanded view. It also happens to be faster than the old view in
terms of SQL queries. (In most cases at least)
Can be improved a little more by:
- Adding an 'expand/collapse' feature to list only the VNs
- Adding a column indicating the role of the producer (dev/pub)
|
|
|
|
And changed the order a bit, as suggested by ImmLff.
|
|
This is implemented by adding ihid (item hidden) and ilock (item
locked) columns to the changes table,
The (vn|release|producer).(hidden|locked) columns now work as a
cache, refering to the changes.(ihid|ilock) columns with
changes.id = (vn|release|producer).latest.
The cached columns are updated automatically each time a new revision is
inserted.
This is a pretty large change, bugs are quite likely.
|
|
|
|
|
|
The warnbg and warnborder colors from the skins are used for
highlighting.
|
|
This column was used to differentiate between automated edits and user
edits, but that later changed to checking for changes.requester = 1.
The column has since never really been used, and due to a bug introduced
in VNDB 2.0, it has never been updated, either. Meaning it's not even
accurate for any database changes made after december 2008...
|
|
A form validation error is somewhat more user friendly than a 500.
|
|
And also changed the way the item_table.latest column was updated: it is
now only updated after the revision insert has completed, making it
easier to write trigger functions in SQL.
|
|
|
|
|
|
TODO:
- document the relations
- emit a relgraph notify when needed
|
|
Again, mostly copied from the VN relation editor...
|
|
|
|
And again copied something from the VN relation code... meh.
|
|
The current list of relations isn't final yet, may be changed later on.
Quite a bit of this code has been copied from the VN relations... need
to find a way to use prober code reuse here.
TODO:
- Nice relation editor interface
- Display relations in revision browser
- Display relations on producer pages
- Generate relation graphs
- Sync update_2.8.sql into dump.sql
|
|
|
|
|
|
|
|
|
|
|
|
The subform id is now passed to htmlForm() as first formpart item. This
way the id won't change even if the title does, which will be the case
with the interface translation.
|
|
Hmmm, I think I'll need to update some of the utility functions to take
more functionality from the Handler pages in regard to getting text
strings. Using mt() on everything that is essentially already passed to
other functions with a unique string for identification is a bit double.
So far I've updated htmlRevision to do this. (The name argument is
still present but currently ignored, to preserve backwards compatility,
the rest of the code will be updated soon.) Other utility functions like
htmlForm should probably do something like that as well.
|
|
This finishes Util::CommonHTML, with the exception of htmlVoteStats
|
|
and age()
|
|
And replaced the ugly release type cssicon class hack. The class is now
'tr'.$type_numer, instead of the first three characters of their English
representation in lowercase. No idea why I haven't done it this way in
the first place...
|
|
User ranks are easy... but the language names are used everywhere!
|
|
Everything has now finally been converted to use the PgSQL LISTEN/NOTIFY
feature. This commit removes the last Tie::ShareLite dependency.
|
|
This should make a nice connection between the few kinds of database
entries we have.
|
|
|
|
dbProducerGet()
Added an 'extended' flag to the 'what' argument, which should be used
if more columns are desired.
|
|
|
|
Three-box-layout didn't work very well together with the screenshots
on the homepage and the CSS icon hack needed a to get rid of
a strange top margin.
With this, the following browsers should render all pages correctly:
FF2, FF3 and the latest Opera, Safari and Chrome
|
|
These changes are all pretty much related, so couldn't really do
that in multiple commits.
|
|
DB/{Votes,VNList,WishList}.pm into ULists.pm
|
|
|
|
Including anything related to editing, item histories, etc.
No need to have those pages in google, is there?
|
|
Code reuse = good.
Release edit form is now finished, functionality-wise.
|
|
|
|
It'll take a while before the VN edit form is finished... it's
one of the most complex things of VNDB.
|
|
They pretty much all work the same anyway
|
|
|
