Difference between revisions of "User talk:Hearmeout"

From SgWiki
Jump to navigation Jump to search
m
m
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== BNDEP MAN Buses ==
==Re:Opinions==
Hi,
 
First of all, I can't satisfy everyone moving forward, as there are a few disagreement. Let me explain the rational of the new bus model subpages changes.
 
The original format:
 
{|class="wikitable sortable" style='text-align:center;'
!style="{{CSS/BUS|xfc=|xbc=}}"|Operator
!style="{{CSS/BUS|xfc=|xbc=}}"|Registration no.
!style="{{CSS/BUS|xfc=|xbc=}}"|Livery
!style="{{CSS/BUS|xfc=|xbc=}}"|Deployment
!class="unsortable" style="{{CSS/BUS|xfc=|xbc=}}"|Former deployments
|-
|{{LTA}}
|SG0000M
|SBS Transit Livery
|SGDEP 999
|
|}
 
Editors have complained about the long rowspan used in the livery, and the cramping feel on mobile. This was taken note of and further enhanced to this:
 
{|class="wikitable sortable" style='text-align:center;'
!style="{{CSS/BUS|xfc=|xbc=}}"|Operator
!style="{{CSS/BUS|xfc=|xbc=}}"|Registration no.
!style="{{CSS/BUS|xfc=|xbc=}}"|Deployment
!class="unsortable" style="{{CSS/BUS|xfc=|xbc=}}"|Former deployments
|-
|{{LTA}}
|{{Livery/SBST|SG0000M}}
|SGDEP 999
|
|}
 
The livery was match into the Registration to mimic the bus model. As for the cramping feel and long scrolling, it had been done through scrolling effects and toggle button for former deployment.
 
To further enhanced, I trial merging the operator with Deployment through colour coding.
 
{|class="wikitable sortable" style='text-align:center;'
!style="{{CSS/BUS|xfc=|xbc=}}"|Registration no.
!style="{{CSS/BUS|xfc=|xbc=}}"|Deployment
!class="unsortable" style="{{CSS/BUS|xfc=|xbc=}}"|Former deployments
|-
|{{Livery/SBST|SG0000M}}
|style='{{CSS/LTA|xfc=|xbc=}}'|SGDEP 999
|
|}
 
User TTDEC highlighted and feedback the issue on colour blindness and I modified it to


Do you have any proof that SMB3043S perms 23, and that the 3 A95 batch 2s are all perm 168? For the record, when you put SG5761S as 168 perm on Sunday, that bus hasn’t even done 168 yet. Also, these buses have not done the services mentioned that frequently to be considered perms yet.
{|class="wikitable sortable" style='text-align:center;'
!style="{{CSS/BUS|xfc=|xbc=}}"|Registration no.
!style="{{CSS/BUS|xfc=|xbc=}}"|Deployment
!class="unsortable" style="{{CSS/BUS|xfc=|xbc=}}"|Former deployments
|-
|{{Livery/SBST|SG0000M}}
|{{Bus/SD|LTA|SGDEP|999}}
|
|}


AirFan19
With these iterations and not using the <code>rowspan</code> to reduce long row height span.


== Reply from my [[User talk:RobloxXF|talk page]] ==
---


Blud, these buses are still interchangeable. Take 184 and 302 bendy buses, I have seen those perm bendy buses doing 302 and not 184 on some days. Also 176 perm buses still doing 190. So do not undo those edits again unless you show evidence
Opinions are being gathered with implementation of subpages to reduce scrolling, with the trial on Scania K230UB (Euro IV) (Batch 2).


RobloxXF
Majority of the responsed gather disapproved of advertisement in bringing back, maintaining the status quo. However, a lot of online community disapproved of the shifting of advertisement columns away and want it back. This causes a lot of backlash which after reviewing opinions, return the advertisment column.


== Reply ==
{|class="wikitable sortable"
Hi,
!style="{{CSS/BUS|xfc=|xbc=|bgop=a0}}"|Registration no.
!style="{{CSS/BUS|xfc=|xbc=|bgop=a0}}"|Deployment
!class="unsortable" style="{{CSS/BUS|xfc=|xbc=|bgop=a0}}"|Details
|-
|{{Livery/SBST|SG0000M}}
|{{Bus/SD|LTA|SGDEP|999}}
|Ads<hr>Former Deployment
|}
 
According to sgbusntrain, I had modified it with his suggestion, and Wekelwrady/Aphabetlore1 thoughts on the heading Lush Green colour with a lighter shade, so that the sortable button is visible and a bit of differiated with the lush green livery.
 
{|class="wikitable sortable"
!style="{{CSS/BUS|xfc=|xbc=|bgop=a0}}"|Registration no.
!style="{{CSS/BUS|xfc=|xbc=|bgop=a0}}"|Deployment
!class="unsortable" style="{{CSS/BUS|xfc=|xbc=|bgop=a0}}"|Ads
!class="unsortable" style="{{CSS/BUS|xfc=|xbc=|bgop=a0}}"|Former Deployments
|-
|{{Livery/SBST|SG0000M}}
|{{Bus/SD|LTA|SGDEP|999}}
|{{N/A}}
|
|}
 
My current priority is to bring Advertisement column back and the usage of subpages to prevent lags on mobile as highlighted by Kay.
 
====Opinion is crucial====
As you can see, I didnt implement it my way fully, but rather tackle issue pieces by pieces. Many editors are editing model advestisment or deployment and not updating former deployment or service pages, which is why I started changing to bring former deployment side by side, and sgbusntrain linked it up to the respective service page.
 
'''Your Opinion is crucial and important, and I didnt ignore it.''' I had taken note of your recommendation of merging batches with many go in favour, but the specification table will be messy.
 
Just for this reason alone and the bandwidth I had, I only proceed with the implementation of Advertisement column back, before merging of batches.
 
Regarding the GB card, UPD Decal, Lifespan Expiry etc column are in the pipeline. As for former deployment being collapsible, I afraid editors will forget it exists if collapsed by default, and therefore I didn't implement it moving forward.
 
Regarding the colour coding - like what I explained earlier, colour blindness and hence I could not proceed with it.
 
==== Bus Stop Template ====
Regarding your bus stop template of standardisation, this will affect not only on bus service pages, but also MRT/LRT station pages.
 
I had take note of it for easier attractions/landmark standarisation, and alphabetlore1 suggestion of hyperlink.
 
In conclusion, your opinion is important, and with the bandwidth I had, the countless demands from many editors, and the issue of old format (prior to changes), I am in a very tight situation and would not be able to accomodate every editors request, but I will try to solve the problem created from the old format -  data inaccuracy across pages due to editors not editing many page.
 
==== Fun fact ====
If you have noticed, the new bus service pages fleet table carry the same information, without listing the  number of buses per modal. The number of buses (double/single decker) is based on duty size and no longer require editors to count and tally. The inclusion of the modal without any rego, make it easier to infer that this modal appears as a perm to serve this service, just in case editors forget to update the service page - making the service page still accurate per say.


Thank you for your effort. The reason I scrapped the plans first is because the page will get long and I trying to figure a way to integrate both Former Deployment to the current page, and remove the advertisement columns for buses. This helps to reduce the amount of page when user had to edit in the change of deployment (from 3 pages to 2).
Complaints were made regarding harder to count or difficulty in counting the number of bus per modal, which I had implement a clearer centered align format  with each rows at most 5 columns. So just count row×column and one can glance the amount of buses per modal.


It is also to streamline and make information more clearer and readable like what you had pointed out. But so far I haven't had any luck on the ideas to solve this issue.
As always, I would like to seek your opinion on your statement that how is the new format harder, and I will consodilate and try my effort to come out with solution, and if you have any solution, feel free to highlighted it up. I hope you understand the difficulty in my position, where editors only edit a page leading the inaccuracy in the old format, and the rational of such changes.


To add on with a further streamline process, I had created a trial page Bus Service 900 which actually holds more information and details, omit the fleet listing by putting in general bus model to further streamline the need to edit 3 pages into 1 when there is a change of deployment. A change in oeprator will result in the whole page edit which is something that we are already doing.
Regards,
Supernutorcrazy


Next this also helps to integrate historical information into the page, which allow the page to be even more wikipedia.


Please feel free to experiment with the ideas and concept you have. It may not be perfect, but let try to clean up to make the page more meaningful to the general public. Bus Enthusiast will hate me for this, just like Arthurjie, but is a necessary move to make.
My first piority is to bring back Advertisement Column back to the modal as every social media platforms wants it, but not most editors as seen in my talk page. This make the changes from:


Regards
{|class="wikitable"

Latest revision as of 21:29, 10 February 2025

Re:Opinions[edit]

Hi,

First of all, I can't satisfy everyone moving forward, as there are a few disagreement. Let me explain the rational of the new bus model subpages changes.

The original format:

Operator Registration no. Livery Deployment Former deployments
Land Transport Authority SG0000M SBS Transit Livery SGDEP 999

Editors have complained about the long rowspan used in the livery, and the cramping feel on mobile. This was taken note of and further enhanced to this:

Operator Registration no. Deployment Former deployments
Land Transport Authority
SG0000M
SGDEP 999

The livery was match into the Registration to mimic the bus model. As for the cramping feel and long scrolling, it had been done through scrolling effects and toggle button for former deployment.

To further enhanced, I trial merging the operator with Deployment through colour coding.

Registration no. Deployment Former deployments
SG0000M
SGDEP 999

User TTDEC highlighted and feedback the issue on colour blindness and I modified it to

Registration no. Deployment Former deployments
SG0000M
Land Transport Authority
SGDEP999

With these iterations and not using the rowspan to reduce long row height span.

---

Opinions are being gathered with implementation of subpages to reduce scrolling, with the trial on Scania K230UB (Euro IV) (Batch 2).

Majority of the responsed gather disapproved of advertisement in bringing back, maintaining the status quo. However, a lot of online community disapproved of the shifting of advertisement columns away and want it back. This causes a lot of backlash which after reviewing opinions, return the advertisment column.

Registration no. Deployment Details
SG0000M
Land Transport Authority
SGDEP999
Ads
Former Deployment

According to sgbusntrain, I had modified it with his suggestion, and Wekelwrady/Aphabetlore1 thoughts on the heading Lush Green colour with a lighter shade, so that the sortable button is visible and a bit of differiated with the lush green livery.

Registration no. Deployment Ads Former Deployments
SG0000M
Land Transport Authority
SGDEP999
N/A

My current priority is to bring Advertisement column back and the usage of subpages to prevent lags on mobile as highlighted by Kay.

Opinion is crucial[edit]

As you can see, I didnt implement it my way fully, but rather tackle issue pieces by pieces. Many editors are editing model advestisment or deployment and not updating former deployment or service pages, which is why I started changing to bring former deployment side by side, and sgbusntrain linked it up to the respective service page.

Your Opinion is crucial and important, and I didnt ignore it. I had taken note of your recommendation of merging batches with many go in favour, but the specification table will be messy.

Just for this reason alone and the bandwidth I had, I only proceed with the implementation of Advertisement column back, before merging of batches.

Regarding the GB card, UPD Decal, Lifespan Expiry etc column are in the pipeline. As for former deployment being collapsible, I afraid editors will forget it exists if collapsed by default, and therefore I didn't implement it moving forward.

Regarding the colour coding - like what I explained earlier, colour blindness and hence I could not proceed with it.

Bus Stop Template[edit]

Regarding your bus stop template of standardisation, this will affect not only on bus service pages, but also MRT/LRT station pages.

I had take note of it for easier attractions/landmark standarisation, and alphabetlore1 suggestion of hyperlink.

In conclusion, your opinion is important, and with the bandwidth I had, the countless demands from many editors, and the issue of old format (prior to changes), I am in a very tight situation and would not be able to accomodate every editors request, but I will try to solve the problem created from the old format - data inaccuracy across pages due to editors not editing many page.

Fun fact[edit]

If you have noticed, the new bus service pages fleet table carry the same information, without listing the number of buses per modal. The number of buses (double/single decker) is based on duty size and no longer require editors to count and tally. The inclusion of the modal without any rego, make it easier to infer that this modal appears as a perm to serve this service, just in case editors forget to update the service page - making the service page still accurate per say.

Complaints were made regarding harder to count or difficulty in counting the number of bus per modal, which I had implement a clearer centered align format with each rows at most 5 columns. So just count row×column and one can glance the amount of buses per modal.

As always, I would like to seek your opinion on your statement that how is the new format harder, and I will consodilate and try my effort to come out with solution, and if you have any solution, feel free to highlighted it up. I hope you understand the difficulty in my position, where editors only edit a page leading the inaccuracy in the old format, and the rational of such changes.

Regards, Supernutorcrazy


My first piority is to bring back Advertisement Column back to the modal as every social media platforms wants it, but not most editors as seen in my talk page. This make the changes from: