Template talk:Intel processor roadmap
|This is the talk page for discussing improvements to the Intel processor roadmap template.
|This template is of interest to the following WikiProjects:|
- 1 CPU microarchitectural core vs. microprocessor/SoC die/package codenames
- 2 Shift from SVG to Template:Graphical timeline or meta:EasyTimeline
- 3 2013-08 border cell
- 4 Vertical table format
- 5 Core / Merom / Penryn ref
- 6 Make template compatible with the VisualEditor ?
CPU microarchitectural core vs. microprocessor/SoC die/package codenames
I added several CPU codenames and removed several die codenames, however, I believe more should probably be done such as in the P6 space (adding Pentium M vs. Banias/Dothan and Enhanced Pentium M vs. Yonah). I understand things get a bit sketchy that far back but at least for now and immediate future I believe the CPU microarchitectural cores should not be conflated with the microprocessor/SoC dies/packages. 22.214.171.124 (talk) 13:39, 26 August 2013 (UTC)
Shift from SVG to Template:Graphical timeline or meta:EasyTimeline
It's too cumbersome to edit the SVG every time the diagram is changed (I wish it was editable like text). So I'm considering using the aforementioned alternate mechanisms. EasyTimeline is not easy at all though, and I don't think it supports non-linear scales. Graphical Timeline is a template monster of dimensions too. I like the EasyTimeline syntax, but the semantics (almost every attribute is mandatory) and it looks bad. --Ysangkok (talk) 00:43, 27 August 2013 (UTC)
- I was going to suggest moving to mw:Extension:EasyTimeline but I agree the transition would be nontrivial (though it might prove more maintainable after such). Too bad we do not have something like mw:Extension:Inline SVG extension available. 126.96.36.199 (talk) 14:56, 27 August 2013 (UTC)
2013-08 border cell
Vertical table format
@Dsimic: the existing horizontal table (as drawn from the original SVG) is starting to become unwieldy as Intel adds more architectures. I propose a vertical format table, but this will require some more careful editing to add new architectures in the future. See my proposed vertical format at the template sandbox, which includes a more fully fleshed-out documentation. Cheers, Mliu92 (talk) 15:09, 30 June 2016 (UTC)
- Hello! The vertical layout you've proposed does look better, and I don't find the additional editing complexity as a potential downside. The only thing preventing me from saying "yay!" is the amount of whitespace we'd have in the infobox that way, so I'd like to hear opinions from other editors, if you agree. Thank you for preparing the proposal in the first place! — Dsimic (talk | contribs) 18:15, 3 July 2016 (UTC)
What could be done to keep the horizontal table small is removing older generations (Netburst and P6). See User:Pizzahut2/sandbox. However some Netburst and P6 articles use the roadmap, so it's not ideal. I like the vertical format though, I'd say go for it. -- Pizzahut2 (talk) 00:41, 8 October 2016 (UTC)
Core / Merom / Penryn ref
About the ref  which lead to Core being replaced with Merom in Tick-Tock_model#Roadmap and in this template. Perhaps with this roadmap image (in the CNET article) Intel just meant that Merom was the first processor to use the new Intel Core architecture, and not that the whole platform (mobile, desktop, server) is called Merom. And same with Penryn - maybe it just happened to be the first 45nm CPU of the Intel Core architecture? So this would make the column with Merom and Penryn the "first implementation" (table heading for your mind).
What's my point? I'm trying to figure out if it's better to a) put all code names in this column (desktop, mobile, server), b) put only desktop code names in there (if there is a desktop implementation) or c) stick with the codename of whichever CPU came first. -- Pizzahut2 (talk) 17:21, 8 October 2016 (UTC)
Make template compatible with the VisualEditor ?
Editing the table manually is a bit cumbersome, so perhaps it would be better if the table can be edited with the VE? — Pizzahut2 (talk) 12:00, 29 August 2018 (UTC)
- If the table is contained as a template parameter, it can't be edited directly with the VE.
- Work-around: Copy the table only to a sandbox, edit it there, and copy it back when done.
- Possible solution: Use a sub page for the table (e.g. Template:Intel processor roadmap/table) and transclude it. As this is a template, I hope it's allowed to do it like this, I'm not sure though.
- Alternate solution: Use navframe divs instead of a navbox.
- Editing templates isn't officially supported.
- Work-around: When editing the table inside a sub page as suggested above, edit the URL, replace "action=edit" with "action=veedit". This only works if the new wikitext mode (beta feature) isn't enabled.
- Possible solution: Add an adjusted link for editing the table (perhaps inside noinclude tags). Example: Template:Navbar-table. Again, this only works if the new wikitext mode isn't enabled.
- Spacers confuse the VE and break the layout if it's changed using the VE.
- No work-around, adding all the spacers back after removing them isn't reasonable.
- Possible solution: Remove the spacers, this makes editing manually more difficult though.
- Closing "noinclude" tags inside the table are removed by the VE.
- Work-around: Add the tag back after editing.
- Possible solution: Replace noinclude sections inside the table with a HTML comment (only visible when editing).
— Pizzahut2 (talk) 12:00, 29 August 2018 (UTC)
I have updated the sandbox for use with the VisualEditor. Instead of a subpage I chose a new template for the table, since I fear that a subpage isn't allowed according to Wikipedia:Subpages. Basically, subpages are meant for special purposes like sandbox, template documentation etc.
- Template:Intel processor roadmap/sandbox (transcludes the table below)
- Template:Intel processor roadmap table (prepared for editing with the VE)
— Pizzahut2 (talk) 01:07, 30 August 2018 (UTC)
I found out that it's possible to make the table compatible with the VisualEditor without moving it to a separate page. If a navframe is used, the table isn't a template parameter and thus can be edited with the VisualEditor.
While I've managed to replicate a navbox using navframe divs, there are some minor differences. So for now I've reverted to split pages. Here's my attempt with navframe divs (single page):
— Pizzahut2 (talk) 14:28, 31 August 2018 (UTC)