Difference between revisions of "User talk:Apex-LW'21"
m |
m (Summary: Some Resolved, Some request to resolved) |
||
| Line 22: | Line 22: | ||
---- | ---- | ||
== | ==Summary of Issues== | ||
===Link to Deployment Specification=== | |||
Johnlynh77 had suggested to link to specification and a new link was added to link it. | |||
'''Solution Example:''' | |||
Example: | |||
{| class="toccolours" border="1" cellpadding="3" style="border-collapse:collapse" | {| class="toccolours" border="1" cellpadding="3" style="border-collapse:collapse" | ||
|-bgcolor=#009548 | |-bgcolor=#009548 | ||
| Line 48: | Line 34: | ||
|- | |- | ||
|rowspan="2"|MAN NL323F | |rowspan="2"|MAN NL323F | ||
|[[MAN NL323F (Batch 1)#Specifications|(Batch 1)]] | |[[MAN NL323F (Batch 1)#Specifications|(Batch 1)]] | ||
|[[MAN NL323F (Batch 1)#Tower Transit|SMB3001M – SMB3034T]] | |[[MAN NL323F (Batch 1)#Tower Transit|SMB3001M – SMB3034T]] | ||
| Line 80: | Line 41: | ||
|[[MAN NL323F (Batch 2)#Tower Transit|SMB3035R – SMB3051T, SMB3053M – SMB3074C & SMB3084Z]] | |[[MAN NL323F (Batch 2)#Tower Transit|SMB3035R – SMB3051T, SMB3053M – SMB3074C & SMB3084Z]] | ||
|} | |} | ||
===Highlighting Production Batch Ordered by comapnies=== | |||
Johnlhnh77 had suggested to display the original company ordered by (for buses prior to BCM). | |||
SBS3602U and Supernutorcrazy had realised the important of listing as the Production Batch for Mercedes-Benz O530 Citaro may cause confusion and conflict between users as both SMRT and SBS Transit purchase the same buses and some of it from SBS Transit had been used in SMRT fleet. As such, it would be best for a new column to be place which stated the original purchaser. | |||
'''Solution Example:''' | |||
{| class="toccolours" border="1" cellpadding="3" style="border-collapse:collapse" | {| class="toccolours" border="1" cellpadding="3" style="border-collapse:collapse" | ||
|-bgcolor=#E3031E | |-bgcolor=#E3031E | ||
!<font style="color:white;">Bus model</font> | !<font style="color:white;">Bus model</font> | ||
!colspan="2"|<font style="color:white;">Registration no.</font> | !colspan="2"|<font style="color:white;">Registration no.</font> | ||
!<font style="color:white;">Originally purchased by</font> | |||
!<font style="color:white;">WAB</font> | !<font style="color:white;">WAB</font> | ||
|- | |- | ||
| Line 126: | Line 58: | ||
|Demonstrator | |Demonstrator | ||
|SMB136C | |SMB136C | ||
!rowspan="3"|{{SMRT Buses}} | |||
!rowspan="7"|{{WAB}} | !rowspan="7"|{{WAB}} | ||
|- | |- | ||
| Line 134: | Line 67: | ||
|[[Mercedes-Benz O530 Citaro#Batch 2 (SMB149R – SMB188C)|SMB149R – SMB188C]] | |[[Mercedes-Benz O530 Citaro#Batch 2 (SMB149R – SMB188C)|SMB149R – SMB188C]] | ||
|- | |- | ||
| | |Mercedes-Benz O530 Citaro | ||
|[[Mercedes-Benz O530 Citaro (Batch 3)|Batch 3]] | |[[Mercedes-Benz O530 Citaro (Batch 3)|Batch 3]] | ||
|[[Mercedes-Benz O530 Citaro (Batch 3)#SG1691L – SG1699R|SG1691L – SG1699R]] | |[[Mercedes-Benz O530 Citaro (Batch 3)#SG1691L – SG1699R|SG1691L – SG1699R]] | ||
!{{SBS Transit}} | |||
|} | |} | ||
- | ===[Half-Resolved] Redundancy of Tower Transit Bus Deployment By Service=== | ||
Supernutorcrazy has suggested that the pages for Tower Transit Bus Deployment by Services was redundant as lack of quality information. | |||
SBS3602U suggested that we will wait for a period of time to see if the deployment will be stabilised if not the whole pages and subpages to be deleted. | |||
Request for a dateline before the pages and subpages to be deleted. | |||
===[Unsolved] Messy Headers and Format especially with a single model with multiple long headers=== | |||
Supernutorcrazy had suggested to merged it to a single table with a new columns that represent the operator which operates it and include a sortable table to reduce the need of long headers as the operators who operates the buses may not get it in running order. | |||
However, SBS3602U highlight that if we will to get rid of it and follows [[Volvo B9TL (Wright Eclipse Gemini 2) (Batch 4) By Registration]], it will cause editor to scroll down pretty far and may causes mobile devices to crash while editing. The long section names etc was still messy. | |||
In light of this, it is possible to semi-get rid of it, but limit the number of rows per table to about 200 and also retain certain element like not in running order. (Eg: SBS1Z – SBS23K; SBS3449X – SBS3482Z & SBS3487K – SBS3523P; SG5000E - SG5120S & SG5176G – SG5185E; SG5300P – SG5395R & SG5397K – SG5399E; SG5546Y – SG5555X) | |||
-- | --Johnlhnh77, SBS3602U, Supernutorcrazy | ||
Revision as of 10:34, 9 August 2016
Welcome to my talk page!
Please post on my user talk page (not my user page) if you want me to delete any outdated / unrelated articles or any unused images existed in sgWiki. Also, please provide the links to the uploaded images (if any) when requesting to delete the articles.
I will review the pages first before I will delete, but however, should any of the pages that requires cleanup or is sufficiently related, it will not be deleted, unless there is a reason to believe that the article is the above-mentioned. Pages (including its talk page of a current page) which are blanked out, unanswered or remained for a certain prolonged period will be deleted in the event of any routine house-keeping or cleanup in sgWiki.
If your account is mistakenly banned due to posting of false or unrelated information, etc, please ask the administrator who had originally banned you by writing on the user's talk page to appeal, unless if you are mistakenly banned by me. If an information is mistakenly marked as false statement, you had to clarify with the administrator and provide justification that the information is true and accurate. However, the decision will be made by the administrator and the decision of the appeal is final, after the investigation is complete.
Do note that the successful appeal of the ban (only for those accounts banned by me) can only be done once. Once the ban appeal is successful, you are to comply with the sgWiki Guidelines. Appeals for repeated bans will not be considered.
The appeal procedures will also apply to the warning points imposed to the account.
If any articles or uploaded photos are deleted by mistake, please use my talk page to appeal. Please note that any deleted articles/photos will be subjected to further review and decision. This appeal only applies to articles/photos that were previously deleted by me. If you wish to appeal on any articles/photos that were previously existed in sgWiki that were deleted by any other administrators, please write on the respective talk pages.
Any accounts that are in severe violation of the rules as stated on the sgWiki Guidebook will not be unbanned. Please ensure that all edits and articles are complied with the sgWiki Guidelines.
If your account is being affected by any Autoblock function caused by the user being blocked for spam advertising, etc, please use my talk page so that I can remove the Autoblock.
For any Captcha issues, please refer to the administrator 'Jason' by writing on his talk page.
For bus-related pages, if you find any mistakes in any pages (only those edited by me), please use my talk page to point out the mistakes and clarify with me. I will make the necessary corrections as soon as possible.
Summary of Issues
Link to Deployment Specification
Johnlynh77 had suggested to link to specification and a new link was added to link it.
Solution Example:
| Bus model | Registration no. | WAB | |
|---|---|---|---|
| MAN NL323F | (Batch 1) | SMB3001M – SMB3034T | 
|
| (Batch 2) | SMB3035R – SMB3051T, SMB3053M – SMB3074C & SMB3084Z | ||
Highlighting Production Batch Ordered by comapnies
Johnlhnh77 had suggested to display the original company ordered by (for buses prior to BCM).
SBS3602U and Supernutorcrazy had realised the important of listing as the Production Batch for Mercedes-Benz O530 Citaro may cause confusion and conflict between users as both SMRT and SBS Transit purchase the same buses and some of it from SBS Transit had been used in SMRT fleet. As such, it would be best for a new column to be place which stated the original purchaser.
Solution Example:
| Bus model | Registration no. | Originally purchased by | WAB | |
|---|---|---|---|---|
| Mercedes-Benz O530 Citaro | Demonstrator | SMB136C | 
|
|
| Batch 1 | SMB139U – SMB148T | |||
| Batch 2 | SMB149R – SMB188C | |||
| Mercedes-Benz O530 Citaro | Batch 3 | SG1691L – SG1699R | 
| |
[Half-Resolved] Redundancy of Tower Transit Bus Deployment By Service
Supernutorcrazy has suggested that the pages for Tower Transit Bus Deployment by Services was redundant as lack of quality information.
SBS3602U suggested that we will wait for a period of time to see if the deployment will be stabilised if not the whole pages and subpages to be deleted.
Request for a dateline before the pages and subpages to be deleted.
[Unsolved] Messy Headers and Format especially with a single model with multiple long headers
Supernutorcrazy had suggested to merged it to a single table with a new columns that represent the operator which operates it and include a sortable table to reduce the need of long headers as the operators who operates the buses may not get it in running order.
However, SBS3602U highlight that if we will to get rid of it and follows Volvo B9TL (Wright Eclipse Gemini 2) (Batch 4) By Registration, it will cause editor to scroll down pretty far and may causes mobile devices to crash while editing. The long section names etc was still messy.
In light of this, it is possible to semi-get rid of it, but limit the number of rows per table to about 200 and also retain certain element like not in running order. (Eg: SBS1Z – SBS23K; SBS3449X – SBS3482Z & SBS3487K – SBS3523P; SG5000E - SG5120S & SG5176G – SG5185E; SG5300P – SG5395R & SG5397K – SG5399E; SG5546Y – SG5555X)
--Johnlhnh77, SBS3602U, Supernutorcrazy