Chris Williams wrote:
I would also argue that in general splash screens are an anachronism.
They're a holdover from slow hard drives attached to slow CPUs and
the
idea that an app taking several seconds to finish preparing itself
for
user interaction was normal. Today there are relatively f
On Apr 23, 2009, at 8:10 AM, Glenn L. Austin wrote:
I hate to bring this up, but I believe that defending your copyright
means that it must be visible at launch of your app.
This is incorrect. There are many examples of works that are protected
by copyright but that do not display a copyri
On Apr 22, 2009, at 9:20 AM, Benjamin Dobson wrote:
On 22 Apr 2009, at 17:06:10, Chris Williams wrote:
So you'd rather the user sits there wondering if this huge, highly
complex
application (like any Office or Adobe app) that takes 10-15 seconds
to load,
even longer on a slow laptop, is ac
On Apr 22, 2009, at 7:30 PM, Mario Kušnjer wrote:
Well I was thinking this way: First window that shows when you start
the app is login window because user can't use an app if he doesn't
log in.
My point is that this isn't the logic your application should be
following. Instead, your app
On Wed, Apr 22, 2009 at 10:21 PM, Kyle Sluder wrote:
> On Wed, Apr 22, 2009 at 10:08 PM, Chris Hanson wrote:
>> And instead of checking network connectivity, your application should just
>> try to use the network and fail gracefully when it's not available. After
>> all, it could go away between
On 2009.04.23, at 04:08, Chris Hanson wrote:
You shouldn't always show a log-in panel in your application either;
Mac OS X has the Keychain for secure storage of user credentials,
you should only ask the user to log in to your service if there's no
stored credential or they've done somethi
On Wed, Apr 22, 2009 at 10:08 PM, Chris Hanson wrote:
> And instead of checking network connectivity, your application should just
> try to use the network and fail gracefully when it's not available. After
> all, it could go away between when you check and actually start using it, or
> while you'
You shouldn't always show a log-in panel in your application either;
Mac OS X has the Keychain for secure storage of user credentials, you
should only ask the user to log in to your service if there's no
stored credential or they've done something like reset their password.
And instead of c
On 22 Apr 2009, at 17:06, Chris Williams wrote:
So you'd rather the user sits there wondering if this huge, highly
complex
application (like any Office or Adobe app) that takes 10-15 seconds
to load,
even longer on a slow laptop, is actually starting up, or should I
click it
again, or is m
Le 22 avr. 09 à 20:31, Shawn Erickson a écrit :
On Wed, Apr 22, 2009 at 9:06 AM, Chris Williams
wrote:
blah blah... Far better than a spinning beach ball.
If written well an application can launch quickly and then get into UI
that informs the user that a lengthy process is taking place w
On Wed, Apr 22, 2009 at 9:06 AM, Chris Williams wrote:
> blah blah... Far better than a spinning beach ball.
If written well an application can launch quickly and then get into UI
that informs the user that a lengthy process is taking place while
ideally letting them do other tasks that aren't b
Michael Ash wrote:
I'm not saying that you load it lazily on demand. I'm saying that you
get the app up and running in a minimal fashion, and *then* establish
the connection. Do it immediately, but after you've officially
"launched". If you do it modelessly, then the user can still access
whatev
On Wed, Apr 22, 2009 at 1:07 PM, Chris Williams wrote:
> Below:
>
>> From: Michael Ash
>>
>> I don't really mind splash screens, although I find them to be
>> pointless. However, if your splash screen does not go into the
>> background when I click on another app while waiting for your app to
>>
Completely agreed. That's just arrogant and insulting.
> From: Benjamin Dobson
>
> I have seen splash screens that have a higher
> window level than normal. This is just wrong. If you're app takes long
> enough to load to warrant a splash screen, it takes long enough to
> load for the user to ge
Below:
> From: Michael Ash
>
> I don't really mind splash screens, although I find them to be
> pointless. However, if your splash screen does not go into the
> background when I click on another app while waiting for your app to
> load, then your app goes into the trash instantaneously.
Of cou
On 22 Apr 2009, at 17:06:10, Chris Williams wrote:
So you'd rather the user sits there wondering if this huge, highly
complex
application (like any Office or Adobe app) that takes 10-15 seconds
to load,
even longer on a slow laptop, is actually starting up, or should I
click it
again, or
On Wed, Apr 22, 2009 at 12:06 PM, Chris Williams wrote:
> So you'd rather the user sits there wondering if this huge, highly complex
> application (like any Office or Adobe app) that takes 10-15 seconds to load,
> even longer on a slow laptop, is actually starting up, or should I click it
> again,
So you'd rather the user sits there wondering if this huge, highly complex
application (like any Office or Adobe app) that takes 10-15 seconds to load,
even longer on a slow laptop, is actually starting up, or should I click it
again, or is my computer dead, or "what the heck is going on here"...?
Mario Ku?njer wrote:
Greetings everyone !
So the question is how to make a window that doesn't have a title bar
and borders ?
Actually I would like it to be just like user login window of OS X.
This could also go for a so called "Splash Screen" on app launch.
Thanks to all in advance.
This
On 2009.04.22, at 08:55, Benjamin Dobson wrote:
Although I'd appreciate it if you could in any way avoid the latter.
I have always found them extremely annoying on OS X. If you're app
takes a long time to load, something small and simple like what
iWork does seems
better.___
On 22 Apr 2009, at 06:32:55, Mario Kušnjer wrote:
Greetings everyone !
So the question is how to make a window that doesn't have a title
bar and borders ?
Actually I would like it to be just like user login window of OS X.
This could also go for a so called "Splash Screen" on app launch.
On 21 apr 2009, at 22.32, Mario Kušnjer wrote:
So the question is how to make a window that doesn't have a title
bar and borders ?
Actually I would like it to be just like user login window of OS X.
This could also go for a so called "Splash Screen" on app launch.
Hello Mario,
I think y
Greetings everyone !
So the question is how to make a window that doesn't have a title bar
and borders ?
Actually I would like it to be just like user login window of OS X.
This could also go for a so called "Splash Screen" on app launch.
Thanks to all in advance.
Mario
23 matches
Mail list logo
