Difference between revisions of "User talk:Alphabetlorefan1"

From SgWiki
Jump to navigation Jump to search
(41 intermediate revisions by 11 users not shown)
Line 6: Line 6:
#Do not type any nonsense messages
#Do not type any nonsense messages
#If I did not reply to your message, that means I am busy
#If I did not reply to your message, that means I am busy
#Don't troll me


Thanks
Thanks


==Opinion==
== Re: Evaluation on 117/M ==
Hi,


I would like to seek your opinion on the following proposed changes:
Hi Alphabetlorefan1,


1. Launch of sgWiki Bus Spotting Page
Would like to approach you for an evaluation on the possibility of creating 117/M under one single page, as you have expressed interest in completing 117/M.
A new page will be created daily and automatically deleted a month later. For example, "Bus Spotting/1 February 2025" would be removed on 1 March 2025. This page is intended to allow editors to document bus registration numbers without the typical edit limitations, enabling infinite edits.


The primary objective is to encourage collaboration among editors and to improve the accuracy of bus deployment data in relation to their permanent services. Many users have noted that the deployment page contains inaccurate and outdated information. By using these pages, we aim to track bus operations more effectively and allocate the correct permanent services, without requiring editors to board the buses to verify duty schedules.
As 117A is running during 117M operating hours but counted as a short-trip service under 117, there may be an instance of confusion, given that 117 starts later on paper. Furthermore, 117 and 117M's only difference is in Seletar, in which both routes may not see any long-term amendments other than Seletar. Hence, the table below attempts to address the difference with alternate operating hours by the parent route and route variant under one combined page.  


2. Use of Subpages for Bus Model Deployment
I am currently also waiting for admin's response before I proceed to create other services that fall under the same example with 117/M. Do share your opinions and thoughts on the idea. Thanks.
I have received considerable feedback, mostly criticism, regarding the separation and consolidation of bus advertisements across models. Most complaints focus on advertisement changes rather than deployment accuracy, which contributes to the aforementioned inaccuracies. As such, I propose reorganising the Bus Model deployment using subpages as follows:


Example: Volvo B9TL (WEG Batch 2) will be divided into four subpages:
{| class='wikitable' style='text-align:center;'
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 1 (Low Entry, SBS7700T – SBS7729L)
!Departure Period<br>(Weekdays)
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 2 (Low Floor, SBS3000G – SBS3099Y)
!Service Available
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 3 – (Low Floor, SBS3100B – SBS3199S)
!Passing through
# Volvo B9TL (Wright Eclipse Gemini 2) (Batch 2)/Page 4 – (Low Floor, SBS3200X – SBS3238M & SBS3269Z)
|-
|<font size=3>05:30 – 08:00</font>
|<font size=5>'''117M'''</font>
|style='text-align:left;'|
* West Camp Road
* '''Seletar Aerospace Crescent'''
* '''Seletar Aerospace Link'''
* Seletar Aerospace Drive
|-
|<font size=3>08:15 16:50</font>
|<font size=5>'''117'''</font>
|style='text-align:left;'|
* West Camp Road
* Seletar Aerospace Drive
|-
|<font size=3>17:00 19:00</font>
|<font size=5>'''117M'''</font>
|style='text-align:left;'|
* West Camp Road
* '''Seletar Aerospace Crescent '''
* '''Seletar Aerospace Link'''
* Seletar Aerospace Drive
|-
|<font size=3>19:15 23:30</font>
|<font size=5>'''117'''</font>
|style='text-align:left;'|
* West Camp Road
* Seletar Aerospace Drive
|}


A navigation bar will be added at the top and bottom of each page, linking the respective subpages. Each page will feature a single table listing up to 100 buses, organised in the following format:
<div class="mw-collapsible">
<p class='exc'>[Show/Hide Full Route Details]</p>
{| class="wikitable"
!rowspan=2 style='{{CSS/BUS|xfc=|xbc=}}'|Bus Stops
!rowspan=2 style='{{CSS/BUS|xfc=|xbc=}}'|Point of Interest
!colspan=2 style='{{CSS/BUS|xfc=|xbc=}}'|Weekdays
!colspan=2 style='{{CSS/BUS|xfc=|xbc=}}'|Saturdays
!colspan=2 style='{{CSS/BUS|xfc=|xbc=}}'|Suns / PHs
|-
!style='{{CSS/LTA|xfc=|xbc=}}'|First bus!!style='{{CSS/LTA|xfc=|xbc=}}'|Last bus
!style='{{CSS/LTA|xfc=|xbc=}}'|First bus!!style='{{CSS/LTA|xfc=|xbc=}}'|Last bus
!style='{{CSS/LTA|xfc=|xbc=}}'|First bus!!style='{{CSS/LTA|xfc=|xbc=}}'|Last bus
|-
|{{BS68181|swt=<br><font size=3>'''<center>({{Bus/117|a=M}} only)</center>'''</font>}}
{{Bus/FBLB|05:50/08:23<br>(117M)|17:24/19:23<br>(117M)|sa=|su=|fr=}}
|colspan=4 {{N/A}}
|}


Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment
===Update===
Good afternoon Alphabetlorefan1,


This approach seeks to balance different perspectives, and to be more mobile friendly, as I am uncertain why some users are strongly opposed to these changes.
The admin has given his reply that it is possible to create 117/M under one single page. The 117/M page creation will be yours as usual. If you wish to discuss this further, do let me know.


Alternative Table Layouts:
Thank you.
# Registration No/Livery | Operator/Current Deployment | Former Deployment (Maintain status quo)
# Batch | Registration No/Livery | Operator/Current Deployment | Former Deployment (Merging of Batches, numerical order, maintain status quo)
# Batch | Registration No/Livery | Operator/Current Deployment | Advertisement | Former Deployment (Merging of Batches, numerical order)


Please let me know your thoughts on these proposals. Thank you for your time and feedback.
== Lets sum this up ==


Regards, Supernutorcrazy
Good to see you having a batch of images you uploaded. But due to some reasons, you have to be aware of something because one of them told me everything in my talk page.


==Concern regarding SBS6709B on routes 129 and 293==
With this, we recommend you to read this: https://sso.agc.gov.sg/Act/CA2021 and https://support.google.com/legal/answer/3463239?hl=en


I edited the page because someone informed me that he was in a Discord server where a user once claimed that SBS6709B was always seen on route 129 instead of route 293, and that they take route 129 everyday.
Before you can proceed off, ah my brain feels relaxed


Please check again on your edits. Thanks. GyecheonSageori (aka Gye) ([[User Talk:GyecheonSageori|talk,]]) 14:15, 31 December 2024 (+08)
== Re: Bus Service Page creation ==
 
Good evening Alphabetlorefan1,
 
Noted your remarks, I can understand where you are coming from. I will proceed with 179/A when I feel the time is right.
 
In addition, I also plan to take on some of the remaining services that you have announced that you will take over, I now have lesser free time, I feel that it is time to speed up the processes and focus more on page maintenance thereafter. Will that be fine with you as well?
 
Thanks

Revision as of 18:49, 30 March 2025

About Me

Hey, its Alphabetlorefan1. If you have any questions or any necessary stuff, you can leave it here until I respond. But wait, before you leave a message here, read this first:

  1. No spamming
  2. Be respectful to me
  3. Do not type any nonsense messages
  4. If I did not reply to your message, that means I am busy
  5. Don't troll me

Thanks

Re: Evaluation on 117/M

Hi Alphabetlorefan1,

Would like to approach you for an evaluation on the possibility of creating 117/M under one single page, as you have expressed interest in completing 117/M.

As 117A is running during 117M operating hours but counted as a short-trip service under 117, there may be an instance of confusion, given that 117 starts later on paper. Furthermore, 117 and 117M's only difference is in Seletar, in which both routes may not see any long-term amendments other than Seletar. Hence, the table below attempts to address the difference with alternate operating hours by the parent route and route variant under one combined page.

I am currently also waiting for admin's response before I proceed to create other services that fall under the same example with 117/M. Do share your opinions and thoughts on the idea. Thanks.

Departure Period
(Weekdays)
Service Available Passing through
05:30 – 08:00 117M
  • West Camp Road
  • Seletar Aerospace Crescent
  • Seletar Aerospace Link
  • Seletar Aerospace Drive
08:15 – 16:50 117
  • West Camp Road
  • Seletar Aerospace Drive
17:00 – 19:00 117M
  • West Camp Road
  • Seletar Aerospace Crescent
  • Seletar Aerospace Link
  • Seletar Aerospace Drive
19:15 – 23:30 117
  • West Camp Road
  • Seletar Aerospace Drive
Collapse

[Show/Hide Full Route Details]

Bus Stops Point of Interest Weekdays Saturdays Suns / PHs
First bus Last bus First bus Last bus First bus Last bus
icon
68181
Bef JTC Aerospace
Seletar A'space Lk

(117M only)
05:50/08:23
(117M)
17:24/19:23
(117M)
N/A

Update

Good afternoon Alphabetlorefan1,

The admin has given his reply that it is possible to create 117/M under one single page. The 117/M page creation will be yours as usual. If you wish to discuss this further, do let me know.

Thank you.

Lets sum this up

Good to see you having a batch of images you uploaded. But due to some reasons, you have to be aware of something because one of them told me everything in my talk page.

With this, we recommend you to read this: https://sso.agc.gov.sg/Act/CA2021 and https://support.google.com/legal/answer/3463239?hl=en

Before you can proceed off, ah my brain feels relaxed

Re: Bus Service Page creation

Good evening Alphabetlorefan1,

Noted your remarks, I can understand where you are coming from. I will proceed with 179/A when I feel the time is right.

In addition, I also plan to take on some of the remaining services that you have announced that you will take over, I now have lesser free time, I feel that it is time to speed up the processes and focus more on page maintenance thereafter. Will that be fine with you as well?

Thanks