adamkhrona

6 ms·

1.
by adamkhrona 14y ago
This is good: it's totally insecure to pass auth credentials in plain-text URLs.
2.
by adamkhrona 14y ago
Same here, as a developer of a cross-platform library, this is the only configuration that works for us. By restricting virtualization of OSX, Apple has effectively forced most developers to use this configuration.
3.
by adamkhrona 14y ago
San Francisco (SOMA), CA - Biz Dev Commando - Contract to Hire (awesomium.com) Live in SF? Got some business sense? Wanna join a startup that's blowing up? Sweet! We need a business development 'commando' to take charge of our day-to-day sa
4.
by adamkhrona 15y ago
Just to add to this, the "special characters" are "%E2%80%AE" which is the escaped form of the UTF-8 "Right-To-Left Override" control character (which effectively reverses the display of text). If you try copying the URL to plain-text, you'
5.
How To Capture Web-Pages with Awesomium and C(labs.awesomium.com)
1 points by adamkhrona 15y ago|0 comments
6.
by adamkhrona 15y ago
Hey guys, thanks for the interest in our library! We're actually getting ready to launch a massive update (1.6.2) to Awesomium in a couple days (new tutorials, new SDK, new .NET wrapper, new samples, etc.) Stay tuned. :-)
7.
by adamkhrona 15y ago
Hey, main developer of Awesomium here-- allow me to answer your question: Awesomium 1.6 was designed from the ground up with the following goals in mind: * Must render to a 32-bit BGRA pixel-buffer (most common image format) * Must be absol
8.
by adamkhrona 15y ago
Indeed-- there's a lot of demand for this kind of component in .NET (especially considering the limitations of the built in WebBrowser class). Our .NET wrapper is open-source and up on GitHub: https://github.com/khrona/AwesomiumSharp Btw,
9.
by adamkhrona 15y ago
I'm the main Awesomium developer-- the 1.6 branch is based off a stable revision from April 2010. We've recently updated to the latest Chromium trunk and will be launching an experimental, public build of our 1.7 branch soon. (Would have ha
10.
by adamkhrona 15y ago
Not exactly-- awesomium can be used for both headless rendering and embedded GUI rendering. It outputs to a BGRA 32-bit pixel-buffer; it's the embedder's job to display it in their respective UI framework.
11.
by adamkhrona 15y ago
Can't beat the Apple Cinema Display 27 inch (or if you're a PC guy, the Dell UltraSharp 27 inch). Got two of them, love them, would never go back.
12.
by adamkhrona 15y ago
Thank you for the suggestions, I'll work on making the site more clear to a technical audience. Our first draft of the site was actually very heavy on the tech details but we ended up trying to dumb it down a bit to appeal to a wider audien
13.
by adamkhrona 15y ago
We did indeed use Chromium as a base but have implemented a great deal of extra modifications on top to make this the ideal solution for offscreen embedding. Significant portions of the renderer, plugin containers, and Javascript system had
14.
Awesomium: the First, Full-Featured, Windowless Web-Browser Framework(awesomium.com)
12 points by adamkhrona 15y ago|7 comments
15.
by adamkhrona 16y ago
We're working on a Linux port for use server-side but that's not to say our current framework is not headless. We developed this branch to be completely independent of any windowing systems (and have even coaxed Flash and Silverlight to ren
16.
by adamkhrona 16y ago
We created a genuinely windowless branch of Chromium two years ago named Awesomium; it's free for non-commercial use and is used in several major games and commercial projects: http://www.awesomium.com
17.
by adamkhrona 16y ago
Chrome was designed to be as simple and easy-to-use as possible; part of this initiative involved being immediately compatible with most corporate set-ups (eg, IE users on a company intranet) so a decision was made to use Windows' proxy con