[Scummvm-devel] Memory consumption in GUI branch

[Johannes Schickel]

On Sunday 26 October 2008 05:08:33 Neil Millstone wrote:
> I wonder if it's possible to compile a GUI-less version of ScummVM, and
> then do a custom GUI for the DS port?  Something simple is all that
> would be required for the launcher, but I suppose the in-game GUI would
> be an issue too.  Probably not feasable, but I thought I'd mention it
> anyway.

Hi,

No it wouldn't be easily possible to rip out the internal GUI and replace it 
via a custom one.

On Saturday 18 October 2008 16:31:14 Vicent Marti wrote:
> I've just prepared a patch with some simple preprocessor voodoo to
> switch between a minimal vector renderer and the standard vector
> renderer at compile time.

Actually your patch still seems to keep code for the AA renderer. I guess we 
should be able to completly remove that one?

Apart I don't think that macro define hackery will be needed. Just keep the 
template and be sure you only instantiate a single type of it.

I hope then the binary size for NDS should be small enough again.


On a related matter:

I actually find it quite bad manner, that people start to complain about 
problems in new code development after most of it is done and not while in 
this case the Summer of Code was still taking place. Everyone had 3(!) 
months in the project timeline to give feedback about the new GUI code. 
Also we didn't merge the code directly after SoC was over, we had still a 
month before merge, even though at this time most code was 'finnished' and 
because of lack of feedback considered fine.

I sometimes wonder what people think why we had developers blogs for SoC?
Why do we have a mailing list, where everyone is able to give feedback or 
ask questions? Why do we have a commit log mailing list? I understand that 
we might have taken the chance and ask the people more actively or use the 
mailing list ourselves to ask for feedback, and I regret that we didn't do 
it and promise to do better next time, BUT after all we had a public 
introduction of the task and the developer on the mailing list.

Thus I am really in the mood to blame you guys for not reporting feedback 
when we still had an easy chance to work out a solution. Now we have the 
code finnished and have to fix it up, which only gives additional work to 
those who write the code. In worst case after all it might mean that we 
need to reconsider the overall design after we implement everything. I 
don't think any of *YOU* would want to do additional work afterwards, just 
because people didn't tell their experience in time.

I'm sorry but this starts to get annoying and it doesn't really make fun 
anymore to work on a project where everyone complains last minute.

// Johannes

PS: I hope you get that this wasn't meant for offense, and if so I'm sorry, 
but rather as a (hopefully) worthy criticism.