[Burichan] [Futaba] [Nice] [Pony]  -  [WT]  [Home] [Manage]
Why are eleven paragraphs of bacon metaphor even necessary to explain one's sexuality.
[Return]
Posting mode: Reply
Name
Email
Subject   (reply to 29328)
Message
File []
Embed   Help
Password  (for post and file deletion)
  • Supported file types are: DAT, GIF, JPG, MP3, MP4, PNG, SWF, WEBM
  • Maximum file size allowed is 12500 KB.
  • Images greater than 250x250 pixels will be thumbnailed.
  • Currently 4717 unique user posts. View catalog

File 156553038704.png - (16.38KB , 247x247 , qr.png )
29328 No. 29328 ID: 3e9573

Features:
- Hide/Show suggestions
- Hide/Show author comments
- New view mode: Comic-style view (Paged per update or per update sequence)
- Navigate between updates with buttons and hotkeys
- Auto expand images
- Expand/collapse the Reply form and move it to the bottom
- Remember position in the quest
- Auto load and store settings for each thread individually

You can use the above feat- oh. Yes, hello quest readers. I'd like to present a new site extension user script that makes it easier to navigate quest content on this site. If you like reading quests, then using this extension will make doing so much faster and more convenient.

Note that the above set of features may expand over time as the extension is further developed.

Installation:
1. Get a browser extension for running site extension scripts. I recommend Tampermonkey over Greasemonkey due to the fact that it runs scripts twice as fast:
https://www.tampermonkey.net/
2. Get the site extension:
https://greasyfork.org/en/scripts/387953-quest-reader

The extension cannot be installed on most mobile browsers since they don't support browser extensions (ie. Tampermonkey). However, there are some exceptions.

Documentation in the posts below, tho I also made a 2min video that demonstrates all of the initial features here:
https://tgchan.org/kusaba/questdis/src/QuestReaderDemo.mp4

Man I hate writing documentation
Expand all images
>>
No. 29329 ID: 3e9573
File 156553043767.png - (206.51KB , 1500x750 , 1hidesuggestions.png )
29329

Showing and hiding suggestions.
A quest reader may sometimes wish to skip reading suggestions posted between the updates to reduce distraction and to increase the rate of their progress.
The extension adds a "Show suggestions" setting which allows hiding only suggestions while keeping the rest of the quest content shown. This feature is mostly useful when viewing the whole thread because suggestions aren't as distracting in the comic view modes.
>>
No. 29330 ID: 3e9573
File 156553048083.png - (260.33KB , 1500x750 , 2authorcomments.png )
29330

Showing and hiding author comments
The quest author's own posts, even when not part of an update, sometimes hold interesting information. The reader may wish to keep these posts visible despite hiding other suggestion posts.
The extension adds a "Show author comments" setting which allows toggling author comments separately from suggestions. This feature is mostly useful when the user turned off viewing suggestions. It's also useful in case the extension makes a mistake and accidentally identifies a text-only update post as an author comment instead.
>>
No. 29331 ID: 3e9573
File 156553052497.png - (215.98KB , 1500x750 , 3viewmode.png )
29331

New View mode: Paged comic-style view
A quest reader may be used to reading comics online and as such may prefer navigating comic-style content one page at a time. Since quests, especially image ones, are in many ways similar to comics, the reader may prefer navigating quest content in a similar fashion.
The extension adds a "View mode" setting which allows converting a thread into a set of pages by showing only a specific set of posts at a time. This can be enabled by selection one of the two setting's possible options:
- Paged per update
- Paged per sequence
The former will manage pages, where each page contains a single update post. This allows for a very consistent navigating experience.
The latter will manage pages, where each page contains a sequence of update posts. When a quest author makes multi-post updates, navigating this way allows for a more author-intended navigating experience.
In these two modes, navigating between updates is done purely through buttons and hotkeys.
>>
No. 29332 ID: 3e9573
File 156553054769.png - (107.25KB , 750x750 , 4navigation.png )
29332

Navigate between updates with buttons and hotkeys
A quest reader may find it slow and inconvenient to use common means, such as a mouse scroll wheel, to navigate between updates and may wish to use a more purpose built set of tools to accomplish this.
The extension adds a set of buttons to the top and the bottom of the thread which allow the reader to move to the next, previous, first, or last update. This is useful due to the fact that it requires a single click to accomplish something that would normally take several mouse scrolls.
The extension also provides keyboard shortcuts to add to the ease of navigation.
- Left arrow: Move to the previous update
- Right arrow: Move to the next update
(I thought about binding Home and End keys to First and Last button actions as well, but that didn't seem useful enough)
>>
No. 29333 ID: 3e9573
File 156553062465.png - (151.77KB , 1500x750 , 6expandimages.png )
29333

Auto expand images
A quest reader may prefer to keep the images expanded at all times.
The extension adds a setting which allows automatic expansion of images upon visiting a quest thread. The expanded images are limited by the window's width and height. Only the visible images are expanded, so if using a paged view mode, less data is transferred.

(Actually, I tried dynamic image expansion in a normal thread view also, but that kinda messes navigating due to images changing sizes on the fly and causing visual element reflows. If there is demand for it, I may revisit this and try to make it work.)
>>
No. 29334 ID: 3e9573
File 156553064755.png - (189.60KB , 1500x750 , 5replyform.png )
29334

Expanding and collapsing the Reply form and setting its location
A quest reader who never uses the reply form may prefer to hide it to reduce distractions. They may also find it more convenient to have the reply form at the bottom, near the posts they're most likely replying to.
The extension adds a button above the Reply form which allows collapsing and expanding the form. It also adds a setting which controls whether the form is located at the bottom of the page, or the top.
>>
No. 29335 ID: 3e9573
File 156553068326.png - (80.71KB , 750x750 , 7rememberposition.png )
29335

Show the last viewed update when opening a quest thread
A quest reader does not always remember the last line they read in a quest and they may find it bothersome to bookmark the location every time they pause reading it. They may find it convenient for this process to occur automatically.
The extension adds a label showing the current position in the quest. The position is saved on-the-fly and automatically restored when opening the quest thread. While this frees the reader from having to remember where they were, it also makes it more convenient to check whether a new update has been posted in the thread, since the remembered position would stay the same, while the total amount of updates would increase. If the reader opens a thread and notices that the current position does not match the total amount of updates, they would immediately know that a new update has been posted.
>>
No. 29336 ID: 3e9573
File 156553070451.png - (76.04KB , 750x750 , 8remembersettings.png )
29336

Persisting the settings
A quest reader may wish to view different quests in different ways and may find it convenient to have their view settings saved.
The extension saves any setting changes automatically and also automatically restores them when opening previously visited quest threads. If the reader opens a never-before visited quest thread, the settings of the last visited quest are used. If no quest threads have ever been visited, then the default settings are used. As of writing, the extension uses browser's internal storage (localStorage) to store the settings.
>>
No. 29337 ID: 3e9573

Other notes:
The extension works for all quest threads in /quest/, /questdis/ and /graveyard/
The extension doesn't work when viewing "Last 50 posts" or "Last 100 posts". This is intentional.
I've tested the extension on the latest Firefox and Chrome and found no issues. If someone prefers a different browser, I could test that as well.
The extension seems to be compatible with tgchan-BLICK.
The extension can make mistakes, because there is no server-side data telling it which posts are updates, and which are suggestions. So it's more or less guessing what's what. It does a pretty good job tho.


Please post any comments, bug reports, feature requests, etc., below as they are greatly appreciated.
>>
No. 29338 ID: 3e9573

>>/questdis/130607
>>/questdis/130622
Thanks for the feedback! I'd like you to be as picky as you can heh.

>it doesn't always keep track of which update you're on
Yeah, it doesn't detect scrolling when dragging the scrollbar or when using mousewheel autoscroll mode. I'm trying to fix it so that any scrolling would be detected, but using IntersectionObserver sentinels is some next-level fuckery, so that could take a while heh.
>if you don't click off of the menu
- Fixed so that navigation doesn't work while a dropdown menu is selected
That was definitely a bug.
>the text in the second post still wraps
I intentionally kept this original layout behavior. But as you say, it's quite annoying due to the inconsistency that it causes.
- Changed so that reply elements never wrap to the right of the OP post
There is another similar default layout inconsistency where a post's text sometimes wraps underneath the image instead of wrapping to the right.
- Changed so that text always wraps to the right of the images of update posts.
I accomplished this by forcing update posts to always stretch 100% of screen width. I tried many other approaches, but nothing managed to work perfectly. I should probably add some settings to control these layout changes in case they would be undesirable to the user.
>unexpand the images
- Fixed.
I've had this implemented but removed it because it was problematic if the user manually expanded the images where the extension would immediately contract them again. Well, I suppose I'll just enable it again.
>"last 50 posts"
This is intentional. The extension needs to "see" the whole thread to be able to properly determine which posts are updates. Also, if it doesn't see the whole thread, then it cannot navigate to the start, the position cannot be stored / restored properly, and various other bugs would be had. I could, in theory, make the extension load the whole thread in the background when opening the "last 50/100 posts" view, but that would kinda defeat the purpose. I have added a note in the documentation tho.
>mixed quests
How does one differentiate between author comments and text-only updates? ;)
>sometimes in sequence view navigating to the next update brings you to the middle
I think I know what the problem might be and I think I fixed it, but not sure. Does it happen when there are .gif files contained in the sequence?
>a setting to automatically go to the latest update when viewing active quests
You mean, when opening any thread in the /quest/ board, that stored position should be ignored, and instead always start at the last update?
I'm not sure if that would be useful. I mean, when opening a thread, the first thing you're usually interested in is whether there have been new updates, right? If it always displayed the last update, then you'd have to rely on your memory, rather than the extension showing you if and how many new updates there have been posted. I've added an explanation about this in the documentation. But do explain why this would help you.
>an ability to go to the next thread
I'd love to add this, but I don't have a database of which threads belong to which quests. As of this moment, the site hosts 3940 quest threads, so it would be quite a job to organize them all.
>>
No. 29343 ID: e7c7d3

>Usefulness of automatically going to the latest update.
I guess where I'm coming from, as a guy with lots of free time and little life, I check the sight quite frequently and have a pretty good idea if a quest updated or not. So most times I'm clicking on a thread not to see if there's an update but to reply. So I had suggested that feature to save myself some clicks. It definitely would not be useful to someone who checks in ever few days or once a week.
>>
No. 29344 ID: 3e9573

>>29343
Do you use Watched Threads site feature?
>>
No. 29345 ID: e7c7d3

>>29344
I do not. I keep forgetting that feature exists and notice the button to do so once in a blue moon.
>>
No. 29346 ID: 3e9573

>>29345
Well, the WT list provides the exact feature that you're looking for. Whenever anyone posts in a thread that you're watching, an alert is added next to a thread on the WT list. Clicking on the alert will take you to this new post.

The extension recognizes this and shows you the update containing the post that you're trying to see, which in this case would be the last update.
>>
No. 29347 ID: e7c7d3

>>29346
Good to know! I"m still very much learning this site, so a lot of my suggestions will be from the perspective of someone only aware of half the features.
Case in point, since I didn't see much activity on /meep here, I mostly ignored it. So in actually reading the first pinned post and finding out that it's actually another extension and not general site updates. Imagine that!
Basically, take anything I say with a grain of salt, but I will still try to note any bugs I find.
>>
No. 29348 ID: 312a22

This is a really nice extension, especially for reading through completed threads.

I do have a suggestion for full thread mode: only expand images after the most recently viewed update. That way it wouldn't waste time and bandwidth expanding all the images in the thread, when you only want to see the latest update.


>>29338
>I'd love to add this, but I don't have a database of which threads belong to which quests. As of this moment, the site hosts 3940 quest threads, so it would be quite a job to organize them all.

Well, that data has already been organized. You'd just have to scrape it from the Wiki. Still a lot of work just to add a next thread button though.
>>
No. 29350 ID: 3e9573

>>29348
>only expand images after the most recently viewed update
Done. Actually, I made it even better. It will now only expand the current and the next image, and will expand images on-the-fly as you scroll up or down.

The only problem is that I had to disable smooth scrolling when navigating up using buttons/hotkeys. That's because if the scrolling up was smooth, it would bug out due to images changing sizes while scrolling, causing it to scroll to a wrong location.

Among other things, I also added a new feature. The tab title, which up until now always showed the board name (eg. "Quests"), will now show the quest title instead.

>Well, that data has already been organized. You'd just have to scrape it from the Wiki.
Adding a button is simple. The problem is the data. Some quests have a lot of threads, with various timelines and settings, which may be entirely unconnected. For instance, https://tgchan.org/wiki/AsteroidQuest you can't easily determine which threads is next simply going by the thread list. And you even have NSFW threads mixed with SFW ones. Well, I'll see what I can do.
>>
No. 29351 ID: 3e9573
File 156616690852.png - (81.70KB , 750x750 , 9wikilink.png )
29351

Link to quest's wiki
A quest reader may sometimes find that a thread does not provide easy access to its own wiki article. They may find it convenient to always have such a link available without having to do any searching.

The extension adds a link to a quest's wiki article to the top and the bottom right of the page. It accomplishes this by searching the wiki for the thread ID and enables the links if the correct article is found.

(I had to do a whole lot of scraping, checking what redirects where and whatnot, and correct a whole bunch of stuff in the wiki, but I'm now happy to report that pretty much all of the current ~3950 quest threads can be found. There's still some corrections to be done, but this is mostly due to problems in the wiki.)
>>
No. 29352 ID: 3e9573
File 156616696789.png - (65.48KB , 974x600 , 10questdislink.png )
29352

Link to quest's discussion thread
A quest reader may find it convenient to have quick and easy access to a quest's discussion thread.

Similar to the previous feature, the extension adds a link to the quest's latest discussion thread, if it can be found in the wiki.
>>
No. 29353 ID: 3e9573
File 156616705122.png - (302.17KB , 1500x750 , 11selectthread.png )
29353

Navigate between quest's threads
A quest reader may wish to navigate between the threads that belong to the quest that they're viewing.

The extension adds a dropdown menu, where each (properly titled) option represents one of the quest's threads. Changing the selected thread will cause the browser to navigate to the newly selected thread.

It's like magic.
>>
No. 29354 ID: 3e9573
File 156616712681.png - (154.05KB , 750x750 , 12titles.png )
29354

Show quest's title and author in tab title
When a quest reader has a lot of quests open in browser tabs, it becomes important for them to be able to differentiate between them. Up until now, the tabs were titled by the board names. If a tab contains a quest thread, it would be convenient to show the quest's title and author instead.

The extension changes the title of the tab in the browser to the quest's title. Similarly, it changes the title element at the top of the thread. The priority is given to the Subject element of the OP post, however the extension will still search the wiki to find the author's name.
>>
No. 29355 ID: e7c7d3

Hey, thanks for the update! Glad for the ability to move between threads.

Some bugs: Still experiencing the bug that brings you to the middle image when navigating to the next update sequence. Can't replicate it when I encounter it, but I have noticed that the last two times it has happened to me that a lot of the posts were saged. There was a gif involved in the second instance, and I can't remember for the first.

The second problem I've encountered is that when going to the latest update in a quest through a link on the discord, it doesn't register as me seeing that latest update. Thus, when I refresh the page (which I do to see if people have already made suggestions) it brings me to the previous update as if that was the last one I saw and not the update I was linked to.

Thanks for all the work that you're putting into this though!
>>
No. 29356 ID: 3e9573

>>29355
You're welcome!

Ok, I managed to fix both bugs. You can update and they will be gone.

Man, it took me a while to figure out this scroll bug. You're using Firefox, right? This bug only affects Firefox (66.0+) because it has internal bugs in the way it implemented scroll anchoring. But yeah, I managed to solve it.

I also did a lot of wiki editing so that all the quests can be found, plus inserted all the missing discussion threads in there.
>>
No. 29357 ID: 864e49

Maybe a way to adjust the size and/or res the images expand to?
>>
No. 29358 ID: 312a22

When opening a quest thread with a saved position, the page doesn't always scroll to the correct position. I think it's a issue with the page scrolling before the images are done loading.It doesn't seem happen on recently opened threads, probably because the images are still cached.
>>
No. 29359 ID: 18f1c5

>>29357
This is pretty much the next feature I was going to add. That is, the ability for the user to manually set the size limits to which the images expand.
Also, the ability to stretch the images to this size if they're smaller than that limit.

>>29358
Try updating now (version 11) and tell me if the problem is still there.
>>
No. 29360 ID: 312a22

>>29359
Nope. I'm using Firefox, if I clear the cache then try opening a thread, it will only scroll part of the way down on longer threads.



Also, the navigation buttons are greyed out when viewing the first image of a thread in this version.
>>
No. 29363 ID: 18f1c5

>>29360
Ah, thanks for catching that. Both bugs should now hopefully be fixed.
>>
No. 29366 ID: 18f1c5
File 156697933624.png - (290.29KB , 1500x750 , 13replyformstyle.png )
29366

Changing the Reply form style
A reader may find the default design of the Reply form annoying for various reasons. The inconsistent length of the fields, fields not functioning as expected, fields not functioning at all, confusing placement of the elements, to name a few, may be some of the design features that a reader would wish improved upon for a better experience.

The extension changes the way the Reply form looks. It changes the following things:
- It removes the first column which contained text field names. Instead, it uses placeholder text to describe what each field is
- It adds a "Reply form" header with two icons in the top right. The left icon minimizes the form (Basically, the "Hide form" button from the initial features). The right icon... more on that in the following post.
- It signifies that the empty Name field will result in a default name of "Suggestion"
- It renames the Email field into Options, so someone doesn't accidentally input their actual email address there
- It moves the Reply button to the bottom right, where a user would usually expect to find it
- It removes the "(reply to ######)" text. We already know that we're replying to the thread if we have the thread open
- It hides the info in the bottom bullets and instead shows it when hovering cursor over a new * element to the left of Spoiler checkbox.
- It hides the Embed field. That field doesn't even work.
- It adds a ? element, which shows "Password for post and file deletion" tooltip when hovering cursor over it, while removing the original text next to the password field

Hmm. Maybe I should simply have put "Suggestion" as a placeholder text for the Name field. Or "Suggestion (default name)" would be better. Anyway, the changes to the Reply form are hard-coded for now. If someone doesn't like the new look of the Reply form, please say so, and I'll either make it a setting or fix the problems you have with it.

I also plan on adding a few additional changes. For instance, I want to hide the Options field and add a "sage" button, and a "dice" button instead.
>>
No. 29367 ID: 18f1c5
File 156697938310.png - (192.14KB , 1500x750 , 14replyformpopout.png )
29367

Floating Reply form
When a user is writing a reply, they may find it more convenient to have the Reply form hover on the screen, next to the post(s) they're replying to, instead of it having a fixed position on either top or the bottom of the page, especially when the distance between the post(s) and the reply form is large.

The extension adds an icon in the top right corner of the header of the Reply form. Clicking on this button pops out the Reply form and makes it float on the screen. When the Reply form is in the floating mode, the header serves as a drag handle, so it's possible to move the form around.
Lastly, the Reply form will become transparent or opaque, depending on whether the mouse cursor is over of it, and whether one of the input fields has focus.

I'm not sure if the transparency is helpful or just annoying. May need some feedback on this.
>>
No. 29368 ID: 18f1c5
File 156697949637.png - (172.26KB , 1500x750 , 15imagesizelimits.png )
29368

Custom image size limits
A quest reader may prefer to set their own size limits to images when they're expanded.

The extension now has a new Image settings section. This section contains two new settings, the "Max image width", and "Max image height", which control the maximum percentage of the browser window the expanded images are limited to.

Note that 100% isn't the actual width of the screen, but about 50 pixels less. This is so that the offset to the right of the image matches the offset to the left of it.
>>
No. 29369 ID: 18f1c5
File 156697961438.png - (118.39KB , 1500x750 , 16stretchimages.png )
29369

Stretching small images
A quest reader with a large screen may prefer to have small images stretched beyond their intrinsic resolution so that they're easier to see.

The extension adds a new setting called "Force fit images" to the Image settings. Enabling this setting will cause the images to stretch beyond their resolution to try to fit an image container. The size of the image container is defined by the "Image container width" and "Image container height" settings.

This is kinda problematic because I can stretch an image to a certain width, or I can stretch it to a certain height, but I can't easily stretch it to both a width and a height while keeping image's aspect ratio. A simple solution that I found is that I can fit an image to a certain container, but then this container will usually have empty space in one of the dimensions. I could make it work so that there would be no empty space, but it wouldn't be very simple~ so I'll wait and see if there's any demand for that first.
>>
No. 29371 ID: e7c7d3

I've noticed the tweaks to the reply box. I quite like them. I haven't tried having it hover, but I'll try to give it a try in the future and see how it feels.

Bit of a bug, similar to what I was experiencing before. >>29355
This time, however, it moves me to the previous update instead of the latest one when I post a reply. Same thing happened when I updated my own quest. It moved me to the previous update and not the one I just posted.

I will confirm I am using firefox, just in case that's relevant again.
>>
No. 29373 ID: 18f1c5

>>29371
>when going to the latest update in a quest through a link on the discord
- Fixed so that when opening a thread with a hash, the stored update position is discarded and replaced with the one that contains the post that is linked.

>when I updated my own quest it moved me to the previous update
Hmm, I haven't thought of that. That is, if you, as the Quest Author, make a post, then that would usually create a new update. So after a refresh, the current position would stay the same while the total amount of updates would increase, causing the current position to no longer be the last.

The way I see it, if you're a normal suggester, and you make a post, then it's a correct behavior that the current position doesn't increase. After all, it's important for a suggester to notice that a new update was posted while they were writing their post.
On the other hand, if you're the Quest Author, then you would obviously want to be automatically moved to the last update, as you would already know that your own post would create a new update.

- Fixed
When clicking on the Reply button, the extension will now check the Name field in the Reply form and compare it with all the names/IDs that the author used. If they match, it should know that you're the author, and it will automatically move you to the last update after a refresh. Now, I wasn't able to test this functionality entirely, since I'm not an author any quests, so please update and tell me if it works correctly.
>>
No. 29375 ID: 18f1c5
File 156719980395.png - (144.60KB , 1500x750 , 17postreferences.png )
29375

Show post references (AKA backlinks)
When a quest reader is also a suggester, it may be hard to find which exact posts are replying to the reader's own posts.

The extension adds a set of links underneath each post. Each of the links points to a post that contains a reference (link) to the said post, allowing for a quick and easy way to see if a post got any replies or was referenced for any other reason. This is a standard imageboard feature which seems to be missing on this imageboard.

The extension also adds a setting that controls whether these links should be shown or not. Or only for non-update posts.
Considering suggesters usually reference update posts for no reason, or rather, that referencing the last update post is already implicit, it doesn't make much sense to show these links in update posts. That's why the default value for this setting is "For non-update posts".

The question that I have is, what would be a good title for these link sets? "Links:", "Linked in:", "Linked from:", "Backlinks:", "References:", "Referenced in:" "Replies:"(current), etc. I can't quite decide heh.
>>
No. 29376 ID: e7c7d3

>>29373
Seems to work, at least for a single image update. I'll keep an eye out if anything wonky happens with multi-images and saging.

>>29375
I prefer Replies. While not always accurate, it's succinct and a bit more intuitive to it's nature than something like 'backlinks'
>>
No. 29377 ID: dd6ea6

Did someone just try to necro rapequest?
>>
No. 29378 ID: b3c4cf
File 156733925207.png - (192.58KB , 1500x750 , 18speed.png )
29378

Speed
A quest reader may find the loading times of quest threads inconvenient, especially when the threads get large.

The extension now decreases the time it takes to load a quest thread, especially when using a paged view mode.
That's right, loading quest threads is now faster with the extension than without.

Loading time decrease:
Whole thread: 15%
Paged view: 66%
Measurements done in Chrome when viewing a quest thread with 2000 posts.

The extension accomplishes this by starting up earlier in the page loading process and hiding the whole page until it's done processing the posts. This eliminates the need to render elements which the extension was going to hide anyway. Unfortunately, the loading of thumbnails still happens in the background. There's no way to prevent that from my side.
>>
No. 29379 ID: b3c4cf

>>29377
The choice of quest threads used in examples is arbitrary. I'm open for recommendations tho.
>>
No. 29381 ID: e7c7d3

>>29367
Been giving this a try. Been handy in checking the spelling of characters names and when thinking of responses to particular posts in an update. Not very useful though when viewing a quest by post or even by sequence if the update and suggestions are low enough, But I guess that's why it's optional :P

The only minor thing is that it only goes transparent if you've clicked off of it, I find. So if you've moved it over something you have to move your mouse off the reply box and click. Might not be a bad thing? But i figure I should bring it up anyways.

>>29373
Also, updated my quest with multiple images and one saged. Problem seems to be fixed on my end.
>>
No. 29382 ID: b3c4cf

>>29381
>if the update and suggestions are low enough
Yeah, it's mostly useful in the whole thread view, or when the update has a lot of suggestions.

The real benefit of it is in the handling of the Insert ID links.
As you know, in the header of any post, there's No. 123456 text. The No. part is a perma link, while the 123456 part is an "Insert ID link". Clicking on the Insert ID link inserts the >>123456 text into the message box. I always found clicking on these links to be super annoying because clicking on it scrolls you all the way to the top of the page, where I then have to scroll all the way back to the post to see what I was going to write.
With a floating Reply form, no disrupting scrolling ever happens, which is nice.

In fact, I just added a new feature. For the "Reply form" setting there's now a new option: Auto-float. Choosing this setting will cause the Reply form to be hidden by default. However, clicking on any of the Insert ID links, or the "Reply" link at the bottom, will call up an already-floating Reply form. This saves you from having to first scroll to the top/bottom and click on the form's popout button.
Hmm. I feel that this setting should be the default.

>it only goes transparent if you've clicked off of it
I'm glad you noticed this. Yeah, the form is opaque if any of the textboxes in there have focus.
This is intentional because when someone wants to write some text, they will usually move the cursor away so that it isn't in the way of writing. It would be quite bothersome if they had to keep the cursor inside the reply form the whole time.
So yeah, once you've clicked on the reply form, you have to click off of it to make it transparent. Perhaps it would be better if it was simply opaque all the time?

>Problem seems to be fixed
Good. Of course, as I develop the extension further, new bugs will pop up, either for the new or the old features, so be on the lookout :P
>>
No. 29389 ID: b3c4cf
File 156825265190.png - (106.91KB , 750x750 , 19analytics.png )
29389

Analytics features

The extension now has 4 additional Analytics settings:
- Color suggester IDs
- Show user post counts
- Show per-user nav
- Show multi-posts

These features are primarily meant for quest authors. They used to be in my other extensions (>>28635), but I carried them over so that the other extensions can be removed.

Color suggester IDs
By turning on this setting, the background color of suggester IDs is changed.

When suggesters are anonymous, the only way to distinguish them is by reading their IDs (or by using the Pony theme). If the suggester IDs are colored, a single glance becomes enough to recognize who's who, which, in theory, is faster than reading text. Of course, this can also be distracting, which is why it's a setting. Hmm. Maybe a better solution would be to generate some icons for every user instead. Just not pony icons.

Show user post counts
By turning on this setting, a number appears to the right of every user ID. This number represents the user's post count in the thread. If the user is new, that is, if they only made posts in a single update, the number will turn red, eg.(1).

This feature makes it easier to distinguish between new and old suggesters. Also, it can be used to quickly spot any votestuffing.

Show per-user navigation
By turning on this setting, two buttons appear to the right of every user ID. If enabled, the left button (up arrows) will navigate to the user's previous post, while the right button (down arrows) will navigate to the user's next post.

This feature makes it easy to move between a user's (or your own) posts. This can be useful for a variety of reasons.

Show multi-posts
By turning on this setting, a red-colored text post X/Y will appear next to posts of suggesters that made more than one suggestion for the update. The number X represents the post index and Y the total number of posts. So if a suggester posts two suggestions in an update, the first one will get "post 1/2" and the second one "post 2/2".

This feature makes it convenient for quest authors to spot which suggesters made multiple posts for the update. By using the per-poster navigation, they can then move between such posts so they can easily decide which one of the suggester's multiple suggestions they should take into account.
>>
No. 29390 ID: e7c7d3

>>29389
Been loving the colour IDs. Been putting that setting on in a lot of the quests I follow. Just always nice to know who's who. I've also been using the user post count for my own quest. It's a nice addition.

Haven't used the other two features, but I could see them helping to parse through things.

I should also mention I haven't encountered new bugs, but I also haven't been playing around with the settings as much.
>>
No. 29392 ID: 312a22

When scrolling in thread view, images in multi image updates don't expand until they're half way up the screen.
>>
No. 29393 ID: a13082
File 156899894211.png - (139.93KB , 1500x750 , 20time.png )
29393

Change timezone and format
The server currently uses Pacific Time (PST/PDT) timezone for all post timestamps. A quest reader who is not in the server's timezone may prefer to have these times converted to their own timezone, or use a relative time format, making it easier for them to figure out when exactly a post was made.

The extension adds a new setting called Timestamp format. This setting controls the way in which post timestamps are displayed.
The setting options include:
- Server time: Leave post timestamps as they are.
- Local time: Convert post timestamps to browser's local timezone.
- Relative to now: Show how much time has passed since the post was made to right now.
- Auto: Show relative time if the post was made less than a day ago, otherwise show local time.
- Hidden: Hide post timestamps. If you're simply reading a quest, do you even need to know when exactly posts were made?

The extension now also allows the user to click on post timestamps to quickly switch between relative and absolute time.

I also thought about adding a "Relative to update" option, which would show how much time has passed between a suggestion and the update it was made for, but I dunno if anyone would find that useful.
>>
No. 29394 ID: a13082

>>29392
Is it better now?
>>
No. 29395 ID: 2b3343

>>29394
Yes, images are expanding properly now. Thanks for the update.
>>
No. 29396 ID: a13082

Some fixes and optimizations:
- The extension will now remember the wiki page for the quest. It will also use the browser's session storage to remember wiki data. This way the wiki won't get hammered no matter how much you're refreshing the quest hehe.
- The site has a bug in the Watched Threads list where the "X New Posts" link takes you to the wrong post; it takes you to the last read post instead of the first unread post. If a quest is updated, this bug causes you to visit the post before the last update (effectively showing the wrong update in a paged view mode) instead of the last update itself. I implemented a workaround for this bug: If the page is loaded where the #hashed post ID is the last suggestion for an update, it will show the next update instead.
- Added tooltips for all the settings
- When the "Force fit images" is enabled, the container will no longer have vertical empty space. Horizontal empty space still remains a problem, however.
- Other small fixes

Stuff I'm working on next:
- Have the extension function in all the threads, not just quest threads, plus the board thread list. Albeit with quest-related settings disabled.
- Add a button to replay animated gif's

Stuff I'm thinking about:
- Stretch thumbnails to full image sizes in the Whole Thread view mode if expand images is enabled. That way the layout wouldn't jump around anymore as the images expand on the fly. Instead, a blurry image (stretched thumbnail) would simply be replaced by a non-blurry one.
>>
No. 29398 ID: e7c7d3

>Button to replay gif's

That'll be nice. I know there's been a couple times reading a thread and the author's added a "blink and you'll miss it" shock or clue in a gif, but the gif's been long played by the time I get to it.


Delete post []
Password  
Report post
Reason