Re: How to make app login window to look like OS X user login window ?

2009-04-23 Thread Glenn L. Austin

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 actually starting up, or should I  
click it
again, or is my computer dead, or what the heck is going on  
here...?


Splash screens serve a purpose other than advertising.  No program  
I know of
actually delays the load to show the splash screen.  Rather, they  
are a

prettier way of saying loading

I have an application that connects to a SQL server.  The app  
itself isn't a
slow loader, but the connection to the SQL server (often on another  
computer
or on hard drives that may be asleep) can take 5, 10, or more  
seconds to
establish.  The splash screen shows that progress and let's the  
user know

what things are being done.  Far better than a spinning beach ball.


Yes, but the vast majority of applications do not take that long to  
load. It may be a prettier way of saying Loading..., but unless  
it's got an actual progress bar on it it's just aggravating. I'll  
also throw in here that 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 get impatient and try to do something  
else.


I hate to bring this up, but I believe that defending your copyright  
means that it must be visible at launch of your app.  It doesn't have  
to be there long, just long enough to possibly see it.


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-23 Thread m


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 copyright notice.


Here's a pdf on the subject from the Copyright Office http://www.copyright.gov/circs/circ03.pdf 



_murat
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-23 Thread Gregory Weston

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 few apps for
which that's the case. Splash screens are no longer the norm and it's
fairly gratuitous to force a user to wait for a while as you
essentially advertise a product they already own to them.


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...?


Actually, I'd rather people read posts before they respond to them.

Splash screens serve a purpose other than advertising.  No program I  
know of
actually delays the load to show the splash screen.  Rather, they  
are a

prettier way of saying loading


Do you use GraphicConverter?

Splash screens *can* serve a purpose other than advertising. Which I  
acknowledged in the post you didn't finish reading before you felt  
moved to compose a response. That's why there were phrases like in  
general and relatively few the norm in there. Congrats on not  
having run into apps that use them gratuitously, but don't assume that  
means they don't exist.


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Benjamin Dobson


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.


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.___


Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Mario Kušnjer


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.___




Thanks everyone for answering !
Actually I was thinking on making a Splash Screen until app loading  
and when ready to do some kind of transition (like cube rotate that OS  
X uses) to the login window
It wouldn't display Splash Screen for long because login window is  
simple except for network connection checking because app should be  
able to use network resources


Mario
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Gregory Weston

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 is more a couple of philosophical digressions than anything to do  
with Cocoa, but I think there are a couple of things here that would  
benefit from a little extra scrutiny before you pursue them.


I would argue against making an effort to make one of your windows  
look just like a security-related OS UI. You'll confuse users who  
don't realize there's a difference and likely anger some of those who  
do and decide you're trying to be deceptive.


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 few apps for  
which that's the case. Splash screens are no longer the norm and it's  
fairly gratuitous to force a user to wait for a while as you  
essentially advertise a product they already own to them.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Michael Ash
On Wed, Apr 22, 2009 at 12:06 PM, Chris Williams ch...@clwill.com 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 my computer dead, or what the heck is going on here...?

This is why the icon bounces in the Dock. If it's bouncing, it's launching.

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.

Much better than a splash screen is to *make your app launch faster*.
Usually the startup tasks that take forever can be deferred until
after the basics of the app have been set up. For example, your SQL
connection doesn't need to be set up while the app is launching. Let
it launch, set up your menu bar and welcome window and whatever else
you have, *then* establish the connection. Your icon is no longer
bouncing, your app is started, and you're in a much better
environment for a long-running task.

Mike
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Benjamin Dobson


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 is my computer dead, or what the heck is going on here...?

Splash screens serve a purpose other than advertising.  No program I  
know of
actually delays the load to show the splash screen.  Rather, they  
are a

prettier way of saying loading

I have an application that connects to a SQL server.  The app itself  
isn't a
slow loader, but the connection to the SQL server (often on another  
computer
or on hard drives that may be asleep) can take 5, 10, or more  
seconds to
establish.  The splash screen shows that progress and let's the user  
know

what things are being done.  Far better than a spinning beach ball.


Yes, but the vast majority of applications do not take that long to  
load. It may be a prettier way of saying Loading..., but unless it's  
got an actual progress bar on it it's just aggravating. I'll also  
throw in here that 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 get impatient and try to do something else.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Chris Williams
Below:

 From: Michael Ash michael@gmail.com
 
 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 course it doesn't demand being on top.

 
 Much better than a splash screen is to *make your app launch faster*.
 Usually the startup tasks that take forever can be deferred until
 after the basics of the app have been set up. For example, your SQL
 connection doesn't need to be set up while the app is launching

Phhfffttt... The app is a database app.  Without the connection, there is no
app.

 Let
 it launch, set up your menu bar and welcome window and whatever else
 you have, *then* establish the connection. Your icon is no longer
 bouncing, your app is started, and you're in a much better
 environment for a long-running task.

It used to do that.  Then the first time you touched anything it hung to 10
seconds, and people thought the app was broken.

You can load my app quickly by disabling the remember where I was last
checkbox.  Then it doesn't have to search the database several times, and
load the disk directory tree, on startup.  But no one does that.

You seem to live in a world where every app is lightweight.  This app has
over a million records in the SQL database, and indexes well over a million
files in an almost 2TB file set.  Things take time.  Letting your users know
what's going on -- above and beyond a bouncing icon or a spinning beach ball
-- is just common sense.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Chris Williams
Completely agreed.  That's just arrogant and insulting.

 From: Benjamin Dobson importedfromsp...@googlemail.com

 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 get impatient and try to do something else.

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Michael Ash
On Wed, Apr 22, 2009 at 1:07 PM, Chris Williams ch...@clwill.com wrote:
 Below:

 From: Michael Ash michael@gmail.com

 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 course it doesn't demand being on top.

Very good! Most don't, but some are really bad that way.

 Much better than a splash screen is to *make your app launch faster*.
 Usually the startup tasks that take forever can be deferred until
 after the basics of the app have been set up. For example, your SQL
 connection doesn't need to be set up while the app is launching

 Phhfffttt... The app is a database app.  Without the connection, there is no
 app.

 Let
 it launch, set up your menu bar and welcome window and whatever else
 you have, *then* establish the connection. Your icon is no longer
 bouncing, your app is started, and you're in a much better
 environment for a long-running task.

 It used to do that.  Then the first time you touched anything it hung to 10
 seconds, and people thought the app was broken.

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
whatever features don't rely on the connection. That might just be the
about box, but maybe that's what they're after. If you do it modally
then at least your dock icon stopped bouncing and you can easily
switch to the app to check on its progress and such.

 You can load my app quickly by disabling the remember where I was last
 checkbox.  Then it doesn't have to search the database several times, and
 load the disk directory tree, on startup.  But no one does that.

 You seem to live in a world where every app is lightweight.  This app has
 over a million records in the SQL database, and indexes well over a million
 files in an almost 2TB file set.  Things take time.  Letting your users know
 what's going on -- above and beyond a bouncing icon or a spinning beach ball
 -- is just common sense.

Sure, I'm just saying that there are generally better ways to let them
know than a splash screen.

Mike
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Greg Guerin

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
whatever features don't rely on the connection. That might just be the
about box, but maybe that's what they're after. If you do it modally
then at least your dock icon stopped bouncing and you can easily
switch to the app to check on its progress and such.



I suggest showing the long-running action using the app's normal way  
of showing long-running actions, whatever that might be.


An example of this is Safari, if it has a home page that takes some  
time to load.  There's no splash or loading screen; Safari just  
presents its normal window with its normal connecting and loading  
indicator, exactly the same as if you'd clicked a link to a page that  
takes a long time to load.


If the only possible long-running action for the app occurs at  
launch, then an I'm working splash screen or other window might  
make sense.  But if the app has a normal way of showing the user that  
an action is taking a long time to complete, I recommend using that  
over a specialized launch-only window.


  -- GG
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Shawn Erickson
On Wed, Apr 22, 2009 at 9:06 AM, Chris Williams ch...@clwill.com 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 blocked by the length
task. A splash screen is generally a bad way to do that on Mac OS X,
as is causing the beach ball to show.

Review... (can't find the blob of text that I recall explicitly
talking about splash screens)

http://developer.apple.com/documentation/userexperience/Conceptual/AppleHIGuidelines/XHIGHIDesign/XHIGHIDesign.html#//apple_ref/doc/uid/TP3353-TPXREF106

http://developer.apple.com/documentation/userexperience/Conceptual/AppleHIGuidelines/XHIGHIDesign/XHIGHIDesign.html#//apple_ref/doc/uid/TP3353-TPXREF110

-Shawn
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Jean-Daniel Dupas


Le 22 avr. 09 à 20:31, Shawn Erickson a écrit :

On Wed, Apr 22, 2009 at 9:06 AM, Chris Williams ch...@clwill.com  
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 blocked by the length
task. A splash screen is generally a bad way to do that on Mac OS X,
as is causing the beach ball to show.


And the worst is that  if the long task blocks the event loop, there  
is no way to cancel it…



___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


[OT] Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Alastair Houghton

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 my computer dead, or what the heck is going on here...?


If you think Office or any of Adobe's apps really have a good excuse  
for that behaviour, I'm afraid you're sorely mistaken.  The problem  
they're trying to solve is well-known, and has been solved for *years*  
in some other bits of software.  Since we're talking huge apps, a  
reasonable comparison might be Emacs, which, if it tried to load  
everything individually like Adobe's apps appear to, would probably  
take even longer to load.  Yet it appears almost instantaneously.   
(Yes, I know, I know, that's because of a horrible unexec() hack, at  
least on most platforms, though IIRC the OS X implementation is a  
little cleaner than average.)


Another large example is OS X itself; it does an Emacs-like trick with  
device drivers, loading them all in one lump from a cache file  
whenever possible.


I suppose both Adobe and Microsoft would retort that they have a lot  
of historic baggage and that re-implementing the start-up code isn't  
high priority for them.  Maybe even that there genuinely are things  
they need to do that really do take time and can't be avoided (though  
I'm doubtful).  I'm only picking on their apps because you mentioned  
them, and they're easy targets :-)


Splash screens serve a purpose other than advertising.  No program I  
know of

actually delays the load to show the splash screen.


The point is that most of what they do at load time can usually either  
be avoided entirely, optimized somehow or deferred until it's really  
necessary.


I have an application that connects to a SQL server.  The app itself  
isn't a
slow loader, but the connection to the SQL server (often on another  
computer
or on hard drives that may be asleep) can take 5, 10, or more  
seconds to
establish.  The splash screen shows that progress and let's the user  
know

what things are being done.  Far better than a spinning beach ball.


But much better to display the app's main UI and then use the app's  
usual progress indication mechanism.  And then, ideally, to make any  
parts of the UI that *can* start working work as soon as possible.


Of course, we're generalising here, and there is a fine line between  
having a splash screen and having a window that opens that says that  
you're just connecting to your server or fetching essential data.


Incidentally, since you're talking about a database app, it's worth  
contemplating whether there is anything that you don't really need to  
fetch straight away; you *might* find that you don't even need to load  
any data up front, but just need to do some queries to establish the  
structure of the data that you're going to have to load.  I'm sure  
you've thought of all of this already wish such a large volume of  
data, but even if that's true then it might be a useful pointer for  
someone else reading this e-mail.


Anyway, this is getting kind of off-topic, but hopefully it's a useful  
post anyway.


Kind regards,

Alastair.

--
http://alastairs-place.net



___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Chris Hanson
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 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're using it - at that point,  
what does checking get you?


  -- Chris

On Apr 22, 2009, at 12:57 AM, Mario Kušnjer mario.kusn...@sb.t- 
com.hr wrote:




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.___




Thanks everyone for answering !
Actually I was thinking on making a Splash Screen until app loading  
and when ready to do some kind of transition (like cube rotate that  
OS X uses) to the login window
It wouldn't display Splash Screen for long because login window is  
simple except for network connection checking because app should be  
able to use network resources


Mario
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/cmh%40me.com

This email sent to c...@me.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Kyle Sluder
On Wed, Apr 22, 2009 at 10:08 PM, Chris Hanson c...@me.com 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're using it - at that point, what does checking get you?

Avoidance of a timeout, perhaps?  Checking reachability might spare
your user a 5 to 10 second trying to contact server spinning
progress indicator.  That 5 to 10 seconds could instead be spent
smacking oneself for forgetting to turn on AirPort.

--Kyle Sluder
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Mario Kušnjer


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 something like reset their password.


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're using it - at that point,  
what does checking get you?


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.
And about Splash Screen: The user name and password provided in login  
window is checked against a remote database over network, so that is  
why network check is done on app launch and while
that is performed I show Splash Screen. If network resources are  
unavailable no login window is showed but instead a window that  
perform certain tasks regarding the problem (if no connection - open  
network pref, if no database - select or create database, etc).

I hope I made it a little bit clear about what I'm trying to accomplish.

Thanks to everyone

Mario
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Michael Ash
On Wed, Apr 22, 2009 at 10:21 PM, Kyle Sluder kyle.slu...@gmail.com wrote:
 On Wed, Apr 22, 2009 at 10:08 PM, Chris Hanson c...@me.com 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're using it - at that point, what does checking get you?

 Avoidance of a timeout, perhaps?  Checking reachability might spare
 your user a 5 to 10 second trying to contact server spinning
 progress indicator.  That 5 to 10 seconds could instead be spent
 smacking oneself for forgetting to turn on AirPort.

Any half-competent network code will error immediately in that
situation, not time out. Any situation where network code will time
out is also a time when reachability will either also time out or will
return a false positive.

Mike
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-22 Thread Chris Hanson

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 application should just attempt to log in.   
If the user can't be logged in using their stored credentials —  
because there are no stored credentials, because their log-in  
information was rejected, etc. — then show your application's log-in  
panel.  And be sure that your log-in panel has a checkbox that allows  
the user to save their credentials in the Keychain.


And about Splash Screen: The user name and password provided in  
login window is checked against a remote database over network, so  
that is why network check is done on app launch and while
that is performed I show Splash Screen. If network resources are  
unavailable no login window is showed but instead a window that  
perform certain tasks regarding the problem (if no connection - open  
network pref, if no database - select or create database, etc).


Again, the network may become unavailable between when the network  
check takes place and when the user actually attempts to log in.  This  
happens all the time to users on wireless connections, so it's not  
something you can just dismiss.  Your application needs to be prepared  
for the network state to change over its lifetime, at any point in the  
application's execution.  Application launch isn't a special time that  
should be singled out.


Furthermore, there are a ton of ways any particular Mac may be able to  
reach your server over the network: A wireless network, a wired  
network, a 3G network card, a FireWire network, a VPN…  And there's no  
primary or default connection, any  all network connections may  
be available from any given Mac at any given time, with the built-in  
routing infrastructure deciding which one a particular connection gets  
routed through.  There's no simple Are network resources available?  
check that you can make, other than Can I connect to my server, right  
now?


And even then, you're still not out of the woods:  Some networks may  
have proxies in place that will intercept your attempt to connect to  
your server until the user visits a log-in page in their web browser.   
(Coffee shops often do this in the United States.)  Your software will  
need to cope with that situation too.


To sum up: Your application will need to deal sensibly with shifting  
network conditions while it's running.  Application launch time is not  
special or different in this respect.


  -- Chris

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


How to make app login window to look like OS X user login window ?

2009-04-21 Thread Mario Kušnjer

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
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com


Re: How to make app login window to look like OS X user login window ?

2009-04-21 Thread Joar Wingfors


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 you might find what you're looking for in this sample:

	http://developer.apple.com/samplecode/RoundTransparentWindow/index.html 



j o a r


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com