On 21 Jun 2008, at 18:04, Karel Demeyer wrote: > Hi all, > > I don't know if I have any credibility with the new ppl on the block > but I'll try to raise an interface issue. My issue being I don't > think we need a splash screen as we're creating a IM program, wich > should be lightweight and not in your way in a "workflow". (I saw > code for it in the commits) > > Splash screens are used for several reasons: to give a user feedback > that the program was started like "OK, you've double clicked the > icon, don't have to do it again") and to give an idea on how long it > will take for the prorgam to load till it's usable. > If aMSN 2's startup time would be so long that we need such a > measure, I thin kthe "fix" won't be to add a splash screen which > would make the program use even more resources, but to fix the > program so it starts up faster. > The best way to give a user feedback, imo, is to open the main > window as quickly as possible with the right dimensions, even if not > everything has been configured yet. If needed you can add a > progressbar in THAT window to show progress (but I hope this won't > be needed, see my previous point). Then the different features can > be un-greyed once they're usable. Once it's possible to do the > login, the user should be able to do this. If the program needs to > load more pixmaps for example, before showing the CL, it should load > these while "logging in..." and only show the CL after everything > needed is initialised. > I think this is more to have a feature complete GUI Core. If one particular DE wants GUI loaders more, then aMSN2's core will have the functionality. I'd assume the person developing the particular interface (Cocoa for example), will have the choice whether to implement the splash screen or not..
> On another note this advise: don't use things just because it's > possible (same goes on for "UI special effects"). Rather try to use > these possibilities to create a more consistent user experience or > to make the program more accessible. Therefor another question for > those UI-coders: please think of accesibility (keyboard usage, color- > themes suited for colorblind of bad-sighted ppl etc). Some DE's have accessibility features included transparently for developers, and if we adhere to the DE guidelines whilst coding our front ends, the accessibility should sort itself out.. > I hope I don't "shoot" ppl this way (the same goes on for the > subject). > > Please give your ideas, > > Karel. > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php_______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
