User talk:BwE: Difference between revisions
mNo edit summary |
m (→cpe (E3)) |
||
| Line 14: | Line 14: | ||
The end goal is to have sections templated, so it can either be linked (like I have done now), or embedded (like the NAND/NOR tables are on the (way too long) Hardware Flashing page. | The end goal is to have sections templated, so it can either be linked (like I have done now), or embedded (like the NAND/NOR tables are on the (way too long) Hardware Flashing page. | ||
This makes it easier to share knowledge/experience and minimalise redunancy. Also, with shorter pages, pageloads are improved. Plus with splitting, the pages can use navigationblocks (like most hardware pages now). That is also why I am splitting off alot of other pages (e.g. Hypervisor Reversing, Flash Page, Hardware pages etc). | This makes it easier to share knowledge/experience and minimalise redunancy. Also, with shorter pages, pageloads are improved. Plus with splitting, the pages can use navigationblocks (like most hardware pages now). That is also why I am splitting off alot of other pages (e.g. Hypervisor Reversing, Flash Page, Hardware pages etc). | ||
The debricking was a confusing (I'll get to that) lengthy text, that assumed one single reason/example and would confuse users even more (there is no limit to user stupidity), because you can replicate the exact errors by at least 5 other hardware or flash faults. For this reason I choose to refer to the main Errorstate page, which then could be used for more indepth problem solving, while keeping an eye on the fact that PS3 has over 1500 components that can flaw anytime. | The debricking was a confusing (I'll get to that) lengthy text, that assumed one single reason/example and would confuse users even more (there is no limit to user stupidity), because you can replicate the exact errors by at least 5 other hardware or flash faults. For this reason I choose to refer to the main Errorstate page, which then could be used for more indepth problem solving, while keeping an eye on the fact that PS3 has over 1500 components that can flaw anytime.<br /> | ||
Also, some errors are not flasher specific, which imo would be better off shared common with other flasherspecific pages.<br /> | |||
The page edit(s) is/are kept in history, so nothing is lost forever, perhaps it can be handy in future in a reformed way, now our noses point the same way [[User:Euss|Euss]] | The page edit(s) is/are kept in history, so nothing is lost forever, perhaps it can be handy in future in a reformed way, now our noses point the same way [[User:Euss|Euss]] | ||
Latest revision as of 14:20, 26 November 2012
cpe (E3)[edit source]
removed counterproductive edit http://ps3devwiki.com/index.php?title=E3&diff=prev&oldid=16467 - reasons :
- multiple reduncancy to be moved to templating (unified checked and verified methods with safeguard steps) ;
- wrong/faulty information ;
- information already handled on other pages ;
- navigate ability and structure
- reduction of page length
- But what of the debricking?
- I felt it was very important and accurate (as I have experienced each issue myself).
- Regarding the other changes; I get keeping it short and redirecting the remainder of the 'guide' to other pages but some users like and can easily follow the guides I had written out. BwE
The end goal is to have sections templated, so it can either be linked (like I have done now), or embedded (like the NAND/NOR tables are on the (way too long) Hardware Flashing page.
This makes it easier to share knowledge/experience and minimalise redunancy. Also, with shorter pages, pageloads are improved. Plus with splitting, the pages can use navigationblocks (like most hardware pages now). That is also why I am splitting off alot of other pages (e.g. Hypervisor Reversing, Flash Page, Hardware pages etc).
The debricking was a confusing (I'll get to that) lengthy text, that assumed one single reason/example and would confuse users even more (there is no limit to user stupidity), because you can replicate the exact errors by at least 5 other hardware or flash faults. For this reason I choose to refer to the main Errorstate page, which then could be used for more indepth problem solving, while keeping an eye on the fact that PS3 has over 1500 components that can flaw anytime.
Also, some errors are not flasher specific, which imo would be better off shared common with other flasherspecific pages.
The page edit(s) is/are kept in history, so nothing is lost forever, perhaps it can be handy in future in a reformed way, now our noses point the same way Euss