Op zaterdag 28 oktober 2006 09:51, schreef NoWhereMan:
> ----- Original Message -----
> From: "Karel Demeyer" <[EMAIL PROTECTED]>
>
> > Really, splashes are bad, are so '90s and I won't like to see amsn use
> > it. You better make your app show the main window as quick as possible
> > (maybe this can be finetuned a little more), as a feedback to the user
> > the app didn't crash and it's already running, with the content maybe
> > showing an image and/or a picture so he/she nows it's normal he/she has
> > to wait a little. The window already should have the menubars though,
> > if possible. THen when everything's alright, show the actual content.
>
> that's not a bad idea at all; you may make the main window "a splash"...
> With this I just mean all the thing a splash would do "show an image,
> display some text) would be done in the main window.
In practice that approximates what Karel was saying already.
>
> I don't think showing the menus when the window is just shown would be
> needed, it would be even bad; users may try to choose "connect" while data
> is still loading.
Just have the menus shown, but have anything that is not available yet greyed
out.
>
> I think an image with some text ("loading this...", "loading that...")
> would be perfectly ok.
Is a user interested in knowing what an app does exactly when starting? I
don't think so. Only if it appears to be taking a long time, a user wants to
know if it is still going actually, or it got stuck somewhere. So the best is
to have a progress bar showing some animation (like usual on Mac a.o.) that
indicates how far we got, and if the process is still going on (if it got
stuck, the animation would stop).
>
> Anyway there is still a draw back: you'll have to parse the config to see
> where the window is actually positioned; a splash would be a quick and
> dirty solution, I second that, but it would be easier (I think) than
> redesigning the bootstrap process, and it would give feedback much eralier
> than what you suggest; btw, I agree with you that the solution you suggest
> would be much cleaner at the eyes, so, that's up to you, my two cents :)
If that config parsing appers to be a problem, we can always move the 'needed
early' config like those positions into a special config file which becomes
loaded first. We can show the window then, and proceed loading the rest of
the config, and do whatever we need to.
>
> bye
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel
