| Age | Commit message (Collapse) | Author |
|---|
|
Add a mention about HTML metadata generator value.
|
|
|
|
Sync with latest maint branch bugfixes.
- Fix/Update LibreJS @source URL to cgit tree
- Change package.json bugs contact to bugs@pantsu.cat email, remove URL
- package.json: Use lowercase pomf for package name
- Gruntfile: Sort grunt-swig options alphabetically
Conflicts:
Gruntfile.js
|
|
Code cleanup, that's all.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
One of NPM's rules [1] is: "New packages must not have uppercase letters
in the name." This also follows the convention where Git repository
names are lowercase.
This change is mostly irrelevant to us, but it's a bug nonetheless.
There's no concern over backwards compatibility regarding SemVer as far
as I'm aware.
This bug was introduced in 7d28ef53a8166cbdcb558a84d5a53cfd73472438.
[1]: https://docs.npmjs.com/files/package.json
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Actually on second thought, SemVer doesn't allow us to remove
functionality without incrementing the major version number... which we
don't want to do for this.
Set the bugs email address to bugs@pantsu.cat. Hoping here bugs@ to be
an alias to ewhal@ for the time being until a real mailing list will be
reachable at that address. This fixes the issue for the time being
without removing functionality.
It is okay that we made a mistake. We don't need to increment the major
version here now, because no release was tagged and released in this
branch.
Nevermind that Pomf isn't even published on NPM packages, so this
"feature" is never seen in its current form in the npm(1) program. We'll
still respect SemVer, for what little worth it may be to other tools.
This reverts commit 310d8d9fdd33826b9a6d5c1f9b1f8aa1c373c461.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Why is this a thing? We never used pantsu/pomf issue tracking. It was
disabled a long time ago in gogs, and now it doesn't even exist.
For consideration, we could provide an email address here. There's no
mailing list for bugs (yet) and it's unlikely to see one soon.
Compliments commit bf4fbf5f8718c4668a57d7dc09880deb904fef1b. Inspired by
~alucard/pomf at Cuntflaps, though never reported to us.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
git.pantsu.cat has switched from gogs to cgit. gogs used a slightly
different URLs to point to tree, so the old URLs from gogs are no longer
valid.
For consideration, to ease maintenance we'll just keep pointing the URL
to the master branch and not a specific commit or maint branch.
?h=master is not really required here, it's the default branch. I am
aware that the current maint and master branches diverge heavily from
each other in terms of JavaScript, but this will be an issue that will
disappear eventually. Thus, this is the simplest fix.
A HTTP redirect will be setup for the old URL to the new one
(eventually) to fix broken links.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Sync with v2.0.1 maint branch.
Doing this sync any later would make me insane and lost.
|
|
Add `<meta name="generator" value="Pomf x.y.z">` to page layout, where
x.y.z is the current Pomf version number defined in package.json with
the help of Grunt.
This change is done to satisfy WHATWG's HTML standard, section 4.2.5.1
Standard metadata names.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Instead of hardcoding the version number and duplicating version strings
in markup, have Grunt grab the version value from package.json. Adds
Gruntfile value pkgVersion.
For consideration, this will cause some issues in efforts to remove
Grunt from Pomf 3.x branch. Right now it's still considerably the best
or simplest thing we can do.
Suggested-by: Eliot Whalan <ewhal@pantsu.cat>
Suggested-by: Austin Gillmann <alucard@cuntflaps.me>
|
|
WHATWG's HTML standard vaguely implies in section "4.2.5.1 Standard
metadata names" that documents that lack a metadata generator value were
written by a user in a text editor. This is not the case for Pomf.
The next Pomf release is expected to be version 2.1.0, which was picked
here for the value.
While we are here, update copyright year to 2016 for this template.
|
|
I have a belief that Swig banners are a Grunt only thing, and they don't
really integrate very well into Swig anyway. It's kind of a hack, and a
bad one because we don't need it anymore.
By deprecating Swig banners, we should have easier time replacing
Grunt/npm with Make in a future release.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Add CHANGELOG.md with human readable change logs for 1.0.0..HEAD. The
change log adheres to "Keep a CHANGELOG" [1] convention, not GNU
standards.
Release notes for 1.0.0 and 1.0.0+8757e9a are stubs.
[1]: http://keepachangelog.com/
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Pomf 2.1.0 has not been released yet, but we're keeping track of changes
anyway as per "Keep a CHANGELOG" [1] guidance. Thus, the date is marked
"Unreleased".
More changes will be tracked as development will continue and progress
forward.
[1]: http://keepachangelog.com/
|
|
|
|
|
|
Includes changelogs for 1.0.0+8757e9a..v2.0.0. The format used is "Keep
a CHANGELOG" [1] as a result of conversation with Eliot.
For future improvement, changelogs for newer releases (e.g. v2.0.1 and
unreleased v2.1.0) should be written.
[1]: http://keepachangelog.com/
Acked-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
This marks the Pomf 2.0.1 release.
Sorry again that the changelogs didn't make it to this release - we're
working on it. Hopefully.
|
|
Sync with maint branch to merge two patches to master.
|
|
- Add missing newline to Response.class.php
- Fix undeclared vars in html_success() and text_success()
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
Reviewed-by: clsr <clsr@clsr.net>
|
|
As explained by clsr:
> <clsr> With default PHP settings, that'd print a warning, then treat
> $result as if it was an empty string before appending.
This bug was introduced in commit
a92961f24072bc4c3881bf0e2f609562f3703471 and
1411bce1dc13bf6fea66b5899ba29d50d5c53bb0.
Reported-by: clsr <clsr@clsr.net>
Suggested-by: clsr <clsr@clsr.net>
|
|
Right before text_error(), there was a missing newline. This bug was
introduced in commit a92961f24072bc4c3881bf0e2f609562f3703471.
|
|
Sanity merge. Instead of merging feature branches to both maint and
master, we should merge them to maint and then merge maint to master as
per gitworkflows(7).
This makes sure the branches are in sync and there will be no issues
later on. It also simplifies git-log(1) with --graph.
Fixes disperancy with `git log master..maint`, which should not list any
commits. My fault.
|
|
Remove page specific style rules. These are unused relics from before
2.0.0 release.
This merge compliments 7743e0ec4e1c71e7cc0e0df6203e02d221c82721, which
was merged too early.
|
|
Remove page specific style rules. These are unused relics from before
2.0.0 release.
This merge compliments 7743e0ec4e1c71e7cc0e0df6203e02d221c82721, which
was merged too early.
|
|
The tools page has only had alive and maintained tools on it since Pomf
2.0.0. Ded and old tools have been removed in commit
627937d0fa632a677f278af467886915c0a36f35.
It is anticipated that these style rules will be never used again. If we
did, we can add them back later: "you aren't gonna need it" (YAGNI). If
it's dead, you should probably remove the tool from the tools page
instead of beating a dead horse.
[wub@partyvan.eu: Modified Git commit message, as discussed]
Signed-off-by: Juuso Lapinlampi <wub@partyvan.eu>
|
|
Remove inclusion of a dead template in JavaScript-free uploader.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Remove inclusion of a dead template in JavaScript-free uploader.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
The JavaScript-free uploader doesn't care about browser features too
much, specifically about window.FormData. That API is for JavaScript.
Because there also isn't any JavaScript to execute, this template never
gets called. It's dead HTML, so remove it.
|
|
Fix some 404 and outdated links in the tools page.
- Update ShareX URL and settings
- Update Gyazowin source code link
- Rename Gyazo Client to Gyazowin for simplicity
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Fix some 404 and outdated links in the tools page.
- Update ShareX URL and settings
- Update Gyazowin source code link
- Rename Gyazo Client to Gyazowin for simplicity
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Acked-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
Acked-by: Eliot Whalan <ewhal@pantsu.cat>
|
|
This outline-offset value has been commented out for how long, and it
seems to have no purpose. Remove it.
Signed-off-by: Juuso Lapinlampi <wub@partyvan.eu>
|
|
Replaces js/pomf.js and its dependencies with Luminarys' new js/app.js,
written in vanilla JavaScript with no dependencies required. This should
improve browser backwards compatibility.
Includes patches from wub@ to add Luminarys to package.json contributors
and adding the proper copyright header to js/app.js.
Luminarys' original code had removed an unused CSS property from
css/pomf.css. I reverted this change to merge it later as a seperate
fix, to be able to merge it properly to the maint branch.
|
|
Adds Luminarys <postmaster@gensok.io> to package.json contributors list.
Luminarys initially committed js/app.js, the new client-side code for
Pomf to replace the old js/pomf.js. This was a significant contribution.
|
|
Adds "Copyright (c) 2016 Luminarys <postmaster@gensok.io>" to js/app.js
with the Expat license embedded.
|
|
Pomf's old JavaScript is a frozen dependency hell with an old version of
Zepto. The amount of code included has reached the point of
unmaintainability, where nobody really understands very well how the
code works.
This code gets rid of all the previous client-side JavaScript and
replaces it with new, vanilla JavaScript. No dependencies required. This
new JavaScript should be quite a bit faster too.
Browser backwards compatibility has not been tested yet, however it is
expected that IE10 and later will work, improving our current backwards
compatibility.
Reviewed-by: Eliot Whalan <ewhal@pantsu.cat>
[wub@partyvan.eu: Added Git commit message and fixed Git branching.
Reverted /* outline-offset: -2px;*/ removal.]
Signed-off-by: Juuso Lapinlampi <wub@partyvan.eu>
|
|
"Gyazo Client (Puush like client)" is a horrible word monster. In the
Pomf community, it is better known as Gyazowin which refers to the
actual project and repository name.
Call it Gyazowin from now on in the tools page.
|
|
Pantsu.cat's fork of Gyazowin (aka "Gyazo Client (Puush like client)")
had moved its development to git.pantsu.cat somewhere around September
23, 2015. This link to GitHub is now dead (404 Not Found).
Replace it with the repository hosted on git.pantsu.cat, at least until
ewhal@ decides to get rid of that unmaintained repository.
Reported-by: Jaex
|
|
ShareX has moved its source code repository to GitHub. Google Code is
also shutting down, so update and point the URL to the GitHub
repository.
While we are here, update and sanitize the ShareX settings we need to
use. Also update the copyright year in header.
Reported-by: Jaex
Suggested-by: Jaex
|
|
We are ready to release Pomf 2.0.0. Patches will follow semantic
versioning, so th next 2.0 branch release will be 2.0.1. The next
feature release will be the 2.1 branch with release 2.1.0.
OK ewhal@
|
|
New code has been added to Response.class.php this year in commit
b94ac9a. Update LICENSE and Response.class.php copyright header with
year 2016.
We can't do this for every file in the project repository unless they
are actually changed, due to the way our copyright legislation works. We
also can't remove the mention of 2015, because most of the code was
initially published in 2015 and so remains copyrighted since that year.
|
|
Clean up a lot of the cruft in Response class.
Gyazo is deprecated and falls back to 'text' for similar functionality,
reducing code duplication. It will be removed in a future release.
CSV gets a text/csv Content-Type. CSV linebreaks are also now CRLF, and
values are wrapped in quotes.
The default error is now a JSON response instead of a generic 400 Bad
Request in plaintext.
output=json is now explicit and no longer undefined behavior.
|
|
The gyazo response would return an empty response, because the construct
didn't actually fallthrough to text properly. Force gyazo's response
type to be 'text' to fix the issue.
Accordingly, the 'gyazo' cases for send() and error() now become dead
code. Remove them.
OK ewhal@
|
|
Add myself to package.json contributors. I have a significant amount of
code and effort dedicated to this project, so I can be contacted for
questions.
OK ewhal@
|
|
Lint our spaghetti JavaScript code to be at least slightly more
readable. Configuration used is ESLint 1.7.x and airbnb/legacy.
It's been so long I cannot remember every change that was done, but long
story short: all the ESLint errors are now gone, at least at the date of
last commit.
moep contributed some ideas for patches: some were implemented, some
were discarded as the time and patience for merging this ran out. Thus,
there are still ESLint warnings about anonymous functions.
I don't feel like spending much more time on this. The future Pomf 2.1
development branch will replace the JavaScript code in its entirety,
courtesy of luminarys@.
Suggested-by: moep
Tested-by: Eliot Whalan <ewhal@pantsu.cat>
OK ewhal@, maybe a vague OK from luminarys@ a long time ago
|
|
|
|
Reword the "no Git issue tracking" policy in contributing section.
Previously the contributing section in README.md would say we don't use
git.pantsu.cat's issue tracker to track issues. That Git service
repository's issues have been disabled today, so we might as well say we
don't use any Git service issue tracking. Unofficial mirrors like the
one on notabug.org may still have issue tracking, which I believe we
have no control over.
This commit also clarifies that we do it for ethical and technical
objections. (In short, it's because the Git service is centralized and a
walled garden.) For more information, see
wubthecaptain/deathwatch-pomf@fc86cbf for information why.
|
