re: Your comment the cost is big.
FWIW: One item that I recall was very complex was the message loop
implementation, which handles both native Windows events and coordinates
inter-thread Task processing.. It was quite difficult to create a task
processing system that integrated with the Windows
Feel free to make an eComstation port though, 2.0 is about to be
released, plus its not that different from any other OS ;)
- Itai
On Jun 23, 12:48 pm, Elliot Glaysher (Chromium) e...@chromium.org
wrote:
On Tue, Jun 23, 2009 at 8:58 AM, Dan Kegeldaniel.r.ke...@gmail.com wrote:
p.s. And OS/2
Is eComstation the OS/2 that dare not speak its name? :-)
On Fri, Jun 26, 2009 at 6:50 AM, Itaiida...@chromium.org wrote:
Feel free to make an eComstation port though, 2.0 is about to be
released, plus its not that different from any other OS ;)
- Itai
On Jun 23, 12:48 pm, Elliot
I presume that Chromium decided to support Windows 2000 when the
project started in 2006. The reasons may be:
(1) The profit is big. There were 6% Windows 2000 users in 2006.
(2) The cost is small. There should not be too many differences
between Windows 2000 (5.0) and Windows XP (5.1).
On Tue, Jun 23, 2009 at 7:13 AM, pizhu.she...@gmail.com wrote:
With a dozen of minim modifications, I have patched chrome 2.0.172.28
to run on Windows 2000.
Great, please submit patches for review.
- Dan
--~--~-~--~~~---~--~~
Chromium Developers mailing list:
On Tue, Jun 23, 2009 at 8:36 AM, pizhu.she...@gmail.com wrote:
please submit patches for review.
Until now, I have only
(1) patched HeapSetInformation(), GetUserGeoID(), GetGeoInfoW() and
TTGetNewFontName() to do nothing and to return failure.
(2) patched RtlGenRandom()/SystemFunction036()
On Tue, Jun 23, 2009 at 8:58 AM, Dan Kegel daniel.r.ke...@gmail.com wrote:
It's not been sold for three or four years, its market
share is going nowhere but down (see
http://en.wikipedia.org/wiki/Usage_share_of_operating_systems )
and the last gasp of extended support expires on 13 July 2010
Yes, the real reason is that there is an ongoing cost of keep that
version working including extra QA cycles for each release. In terms
of supporting a windows version with very few users we should focus
our efforts on Win7.
But you are welcome to keep an external fork. If there is any
