＋设为首页 ＋添加到收藏夹
java applications, in particular those written with the swing toolkit, have a reputation for feeling clunky and out of place, as if they dont belong on your computer. often your users cant put their finger on what it is that doesnt feel quite right. it is often the look of the buttons, subtle menu bar differences, and a lack of a good launching mechanism. swing applications often look and feel different than native applications.
to illustrate each of these techniques, we will overhaul a faux instant messenger called the mad chatter. ive chosen to do use an im program as our ongoing example because it is complex enough to benefit from native integration while being simple enough to fit in a series of articles. the mad chatter will use the basic file and edit menus to save log files and edit text. being a chat application, it will also need a way of alerting the user, so we get to exercise dock bouncing and window flashing. 【程序编程相关:用 JFC/Swing 将可访问性构建到】
this is the first of a three part article series in which we will build a simple application from the ground up and make it look and feel native. this article will cover designing the menus and adding visual alerts. the second article will focus on building native executables and adding file type associations. the third part will complete the series with icons, dialog boxes, splashscreens, and a checklist of finishing touches. throughout the series, we will make use of several libraries and techniques that automate the process and make building high-quality swing applications as easy as possible. 【推荐阅读:字符转换与编码模式】
a menu bar that feels native global key combos alerts when a new message arrives installer free native packaging registering file type associations custom icons a splashscreen native file dialogssome of these tips have been covered in more detail elsewhere, so ill try not to rehash them. instead, ill cover them briefly and then go into how you can cleanly integrate them into your development process. 【扩展信息:Java 2 引用类使用指南】
over the course of these three articles, the mad chatter will get a complete makeover, including:
what is a native-feeling application?
now first lets talk about what it means to feel native. a simple explanation would be that the user cant tell the difference between your swing application and a native one. but that doesnt tell us the whole story. like good photography, feeling native isnt really about doing anything. its about not doing a whole bunch of things. not being slow, not having widgets that look different, not requiring special installation procedures. in general, its about not feeling any different than any other application. this includes key combos, menu placement, icons, packaging, and the correct terminology (quit vs. exit, preferences vs. options, etc.). it means all of the little details that have nothing to do with what the program actually does, but affects how the program feels. and this makes a huge difference to the users.
... 下一页