This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
This article is within the scope of WikiProject C/C++, a collaborative effort to improve the coverage of C and C++ topics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.C/C++Wikipedia:WikiProject C/C++Template:WikiProject C/C++C/C++ articles
This article is within the scope of WikiProject Computer graphics, a collaborative effort to improve the coverage of computer graphics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer graphicsWikipedia:WikiProject Computer graphicsTemplate:WikiProject Computer graphicscomputer graphics articles
On 01 Nov 2004, this article was cited in a SecurityFocus articleonphishing. Securiger 06:50, 8 Nov 2004 (UTC)
stretching the definition of 'article' here .. =]
Who knows for sure Macromedia Dreamweaver MX uses the Presto engine? I haven't seen any official comment regarding this. Also, testing the latest Macromedia Dreamweaver 8 on my heavy CSS-only layout reveals Dreamweaver8 to not being able to properly render the page (as Opera 7 and 8 do). Also, if you test Adobe CS 2 you will clearly see many Opera-tic render bugs while editing CSS-layout, and the right-click context menu is the Opera one :).
The only reason to believe Dreamweaver uses the Presto engine is ... the zoom feature and that it renders CSS much better than IE (yet not as good as Presto, nor Gecko).
Isn't it possible that Dreamweaver uses its own render engine? -- 193.230.211.170
On my Mac, Dreamweaver MX installed a (iirc OS 9 version of) Opera. See [1], which says the companies were working together on integrating Opera into Macromedia products, for more verification. -- k 04:01, 27 September 2005 (UTC)
That's for Macromedia Dreamweaver on Mac. How about Windows? I'm almost sure Presto is not used on the Windows version of Dreamweaver. Robodesign19:28, 30 September 2005 (UTC)[reply]
I think you're correct. I'll change the article to reflect this -- k 21:31, 19 November 2005 (UTC)
I'd like to see Opera Mini added to the History and development section to show how the Presto engine is used in production. I would do try and add this myself, but I don't really know enough about this subject and I don't have the time right now. Thanks. --Hm2k (talk) 17:17, 21 September 2009 (UTC)[reply]
The phrase "remained in use until Opera 12.14" strongly suggests that 12.14 was the last version of Opera using Presto. Yet 12.15 appears to use Presto as well. Although I can't find a source which verifies it, the User-Agent includes "Presto/2.12.388" (and does not include WebKit) and neither the changelog nor the release announcement makes mention of any changes to the layout engine. I'm also not sure the cited source supports the claim that 12.14 is the last version with Presto. Thoughts? -- Kevinoid (talk) 14:34, 4 April 2013 (UTC)[reply]
Part of an edit requested by an editor with a conflict of interest has been implemented.
Ex-Presto developer here. Yes, all 12.xx versions of Opera definitely use Presto. Currently, only Opera version 14 for Android (out in beta) and desktop (no public release yet) use Chromium, and we're skipping the lucky number 13. The statement is partly true, in that we started phasing out Presto after 12.14, but the implication that 12.14 is the last to use Presto is misleading. (A really horrible security bug, for instance, could prompt another minor release years from now.)
Documenting this precisely with verifiable sources is slightly hard, but you're right that the current, incorrect statement isn't sufficiently documented by the blog post either. So IMO it can be corrected without making things worse from a citation POV. I don't think you'll ever find any official statement like "12.15 is the last Presto", so it's better to say something like "the 12.1x series is the last to use Presto" or refer to version 14 like I did above.
I feel quite disemboldened by WP:PSCOI, and the writing lobes of my brain aren't with me today, so please edit the article for me to express this. —Leif Arne Storset11:10, 5 April 2013 (UTC) (COI: Employee of Opera Software)[reply]
I see the sourcing challenge. The source in this case does not actually support that Presto was "phased out" but neither was a source offered that confirmed it was still in use, so the article now only says that Opera began using Webkit and V8. without specifying what happened to Presto. CorporateM (Talk) 23:26, 30 June 2013 (UTC)[reply]
Hi Mr. Storset, nice to see you write here in person. I guess you still are one of the good old Opera guys who propelled forward the original project, and not what it has become of it now. There was a great article having one of your bosses(?) speak up about the demise of Opera (http://www.theregister.co.uk/2015/11/03/vivaldi_browser/ ). Unfortunately, I must say the current mentioning of Presto being used until version 15 is plainly wrong. First V15 betas were the FIRST versions ever to be released WITHOUT Presto, so I hope this'll be still corrected sensibly later. -andy 2.242.144.117 (talk) 18:26, 22 January 2016 (UTC)[reply]
「Opera versions based on the Core fork of Presto, Opera 7.0 through 9.27, used the Linear B engine」
「The Futhark engine is used in some versions on the Core 2 fork of Presto, namely Opera 9.5 to Opera 10.10.」
I have just modified one external link on Presto (layout engine). Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to trueorfailed to let others know (documentation at {{Sourcecheck}}).
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).
If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.