On Thu, 14 Mar 2013, Kyle Auble wrote:
[...]
> I did want to ask for input on a few things:
[...]
Sorry, I don't have anything useful to contribute on these.
However since this is about the Wiki theming I'll mention a problem I
ran into last week-end: tables. There are two problems with them:
*
Am 14.03.2013 um 20:07 schrieb Graham Knap :
> I would like to try to help with improving the performance of
> StarCraft II on Wine. I'm working with a friend. Over the past couple
> of weeks, we have tried to read whatever documentation we could find.
> We have tried a couple of different approach
Hello,
On Fri, Mar 15, 2013 at 12:52 AM, Aric Stewart wrote:
> I am just getting back from a vacation so I will review this and your other
> patch early next week when I am fully back.
>
> Thanks for doing work here!
Thanks for replying, wasn't sure you saw my posts. And of course
thanks for yo
On 3/7/13 4:57 AM, Phil Krylov wrote:
> Hello Aric,
>
> On Tue, Feb 5, 2013 at 11:25 PM, Alexandre Julliard
> wrote:
>> Module: wine
>> Branch: master
>> Commit: ef4b7c5948e43d4ceeed98ba4ddbf6c59d36
>> URL:
>> http://source.winehq.org/git/wine.git/?a=commit;h=ef4b7c5948e43d4ceeed98ba4ddb
Hi everybody,
Although my hiatus was longer than expected, I've been making progress
with updating the wiki code over the past few days (spring break is a
very good thing).
My workflow is a bit non-linear so I want to sort my changes into
patches first, but fingers-crossed, I'll be pushing them t
Hi everyone
I would like to try to help with improving the performance of
StarCraft II on Wine. I'm working with a friend. Over the past couple
of weeks, we have tried to read whatever documentation we could find.
We have tried a couple of different approaches to profiling, without
much success.
2013/3/14 Nozomi Kodama :
> No news about these patches?
>
>
> Nozomi?
>
>
Hmm, I was under the impression that these patches were already picked
up in git, but I see I was mistaken.
Anyway they look okay to me, except for a bit in the tests from the
first patch that I noticed just now by reading
Tijl Coosemans writes:
> Loading a library at a specific address not only depends on the
> compile-time linker, but also on the run-time loader, so it's
> probably best to implement -image-base only on PLATFORM_* where
> the loader supports it. Since a target platform would then have
> to choose
