Putting a splash screen up stopped all the complaints of It takes
_ages_ to load. The funny thing it is takes precisely the same amount
of time to load to a point of fully functional now, but the users all
said Wow you sped up the loading *heaps*. It's a little psychological
I guess.
That's
On Thu, 16 Jul 2009 10:48:29 +0200
Jürgen Hestermann juergen.hesterm...@gmx.de wrote:
Putting a splash screen up stopped all the complaints of It takes
_ages_ to load. The funny thing it is takes precisely the same
amount of time to load to a point of fully functional now, but the
users
Brad Campbell schrieb:
Also, on OSX, the act of displaying the screen and polling the
application event loop stops the app icon bouncing in the dock, so it
looks like its loading faster there also. (An unexpected side effect)
An existing and visible (foreground) window may increase the
Hans-Peter Diettrich wrote:
Brad Campbell schrieb:
Also, on OSX, the act of displaying the screen and polling the
application event loop stops the app icon bouncing in the dock, so it
looks like its loading faster there also. (An unexpected side effect)
An existing and visible (foreground)
On Tue, Jul 14, 2009 at 08:54:35PM +0200, Graeme Geldenhuys wrote:
Vincent Snijders wrote:
It is to show the splash screen as soon as possible, not to wait until
yet another executable is loaded.
Well then we are talking about milliseconds really. A splash screen is
normally show just
Marco van de Voort wrote:
On Tue, Jul 14, 2009 at 08:54:35PM +0200, Graeme Geldenhuys wrote:
Vincent Snijders wrote:
It is to show the splash screen as soon as possible, not to wait until
yet another executable is loaded.
Well then we are talking about milliseconds really. A splash screen is
2009/7/15 waldo kitty wkitt...@windstream.net:
ya know... i guess being so much old school as i am but i still fail to
really understand why a splash screen is really necessary for much of
anything... especially if it causes the app to consume a lot more memory
than truly necessary...
then
Hi,
I was looking at my system processes and noticed that 'startlazarus' is
consuming 26.7MB virtual memory 14.5MB physical memory. Now I'm not
100% sure what the difference is between virtual and physical memory,
but either way, it is a lot of memory considering that startlazarus
doesn't
Graeme Geldenhuys schreef:
but either way, it is a lot of memory considering that startlazarus
doesn't really do anything serious, other than launch the lazarus binary.
and show a splash screen.
On windows 32 bits, Mem Usage is 8 MB, VM Size is 5300 KB.
Vincent
--
On Tue, 14 Jul 2009, Graeme Geldenhuys wrote:
Hi,
I was looking at my system processes and noticed that 'startlazarus' is
consuming 26.7MB virtual memory 14.5MB physical memory. Now I'm not 100%
sure what the difference is between virtual and physical memory, but either
way, it is a lot
Michael Van Canneyt wrote:
Did you strip the debug info ?
OK, just did that and memory usage is still the same as before.
The file size dropped from 31.7MB (with debug info) down to 5.3MB
(without debug info).
Regards,
- Graeme -
--
fpGUI Toolkit - a cross-platform GUI toolkit using
2009/7/14 Graeme Geldenhuys grae...@opensoft.homeip.net:
Vincent Snijders wrote:
On windows 32 bits, Mem Usage is 8 MB, VM Size is 5300 KB.
This raises another question though. Why is it that under Linux is uses more
than double the memory than under Windows? And yet it is the exact same
Henry Vermaak wrote:
My startlazarus uses 10M physical memory, while lazarus uses 27M (RES
column in `top`).
What widgetset did you compile with? I used GTK2. I guess I can
experiment with other widgetsets for the startlazarus project, or is
startlazarus a pure console application? (I never
2009/7/14 Graeme Geldenhuys grae...@opensoft.homeip.net:
Henry Vermaak wrote:
My startlazarus uses 10M physical memory, while lazarus uses 27M (RES
column in `top`).
What widgetset did you compile with? I used GTK2. I guess I can experiment
with other widgetsets for the startlazarus
On Tue, 14 Jul 2009 11:55:41 +0200
Graeme Geldenhuys grae...@opensoft.homeip.net wrote:
Henry Vermaak wrote:
My startlazarus uses 10M physical memory, while lazarus uses 27M
(RES column in `top`).
What widgetset did you compile with? I used GTK2. I guess I can
experiment with other
Mattias Gaertner wrote:
executable without smart linking and without wpo
+ stack
+ loaded config files
+ mem fragmentation
A simple lcl app needs 2-4MB less.
Two questions...1) Can you defrag memory? I'm running Ubuntu 8.04.2 - if
that helps. Or do you just close all apps, logout and
Graeme Geldenhuys wrote:
Two questions...1) Can you defrag memory? I'm running Ubuntu 8.04.2 - if
that helps. Or do you just close all apps, logout and then log back in
and start all apps again. I tend to run my system for weeks on end
without logout or reboot.
Don't worry, I Googled
On Tue, Jul 14, 2009 at 11:18:23AM +0200, Michael Van Canneyt wrote:
On Tue, 14 Jul 2009, Graeme Geldenhuys wrote:
I was looking at my system processes and noticed that 'startlazarus' is
consuming 26.7MB virtual memory 14.5MB physical memory. Now I'm not 100%
sure what the difference is
On Tue, Jul 14, 2009 at 11:24:01AM +0200, Graeme Geldenhuys wrote:
Graeme Geldenhuys wrote:
I was looking at my system processes and noticed that 'startlazarus' is
consuming 26.7MB virtual memory 14.5MB physical memory. Now I'm not
And to make sure that I am reading the memory usage
Marco van de Voort wrote:
What do they say about these values? Most notably, are you 100% sure that
all memory regions that are shared are deducted?
I think Mattias hit the nail on the head regarding my system and memory
fragmentation. My system had a uptime of 14 days (which is not really
Graeme Geldenhuys wrote:
Graeme Geldenhuys wrote:
I was looking at my system processes and noticed that 'startlazarus'
is consuming 26.7MB virtual memory 14.5MB physical memory. Now I'm not
OK, so 'startlazarus' is a GUI application. But I also don't see why the
splash.pp unit has to
Marc Weustink wrote:
What's non GUI on a splash ?
Originally I thought startlazarus just passes parameters on to the lazarus binary and
handles the File Restart (and Restart after Build) feature of Lazarus.
But at closer inspection I saw it does splash screen handling and MessageDlg()
Graeme Geldenhuys schreef:
But at closer inspection I saw it does splash screen handling and
MessageDlg() calls as well, which needs to be GUI. But I'm still
confused. When I start Lazarus without the help of 'startlazarus' I also
see a splash screen, so why does 'startlazarus' also handle a
Vincent Snijders wrote:
It is to show the splash screen as soon as possible, not to wait until
yet another executable is loaded.
Well then we are talking about milliseconds really. A splash screen is normally show just after the Application.Initialize call. Surely a few milliseconds
Graeme Geldenhuys schreef:
Vincent Snijders wrote:
It is to show the splash screen as soon as possible, not to wait until
yet another executable is loaded.
Well then we are talking about milliseconds really. A splash screen is
normally show just after the Application.Initialize call.
On Tue, 14 Jul 2009 20:54:35 +0200
Graeme Geldenhuys grae...@opensoft.homeip.net wrote:
Vincent Snijders wrote:
It is to show the splash screen as soon as possible, not to wait
until yet another executable is loaded.
Well then we are talking about milliseconds really. A splash screen
Vincent Snijders wrote:
Can you test and verify the few (10) miliseconds claim on windows, with
it notorious slow process start up?
OK, I'll test tomorrow at work in my Windows VM session. I don't have Windows
at home to test now.
Regards,
- Graeme -
Vincent Snijders wrote:
If you want to trade speed for memory, it is better to rewrite
startlazarus to exit after it has started lazarus.
I did not look at the Lazarus IDE code yet, but I thought startlazarus must stay in memory for the
File Restart support and the Restart after Build
28 matches
Mail list logo
