Sun Stroke in Santa Clara @ JDJ

转载 2008年05月01日 06:09:00
<script type="text/javascript"><!-- google_ad_client = "pub-2947489232296736"; /* 728x15, 创建于 08-4-23MSDN */ google_ad_slot = "3624277373"; google_ad_width = 728; google_ad_height = 15; //--> </script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script>
<script type="text/javascript"><!-- google_ad_client = "pub-2947489232296736"; /* 160x600, 创建于 08-4-23MSDN */ google_ad_slot = "4367022601"; google_ad_width = 160; google_ad_height = 600; //--> </script><script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script>

  Sun has asked for feedback in a "J2SE Client developer survey," Sun.com/webapps/survey/display?survey_id=1064" target="new" />

  http://java.Sun.com/webapps/survey/

  display?survey_id=1064.

  Scott Violet himself went onto javalobby.org asking for input and my initial thoughts were, "Fantastic - finally Sun is taking Java seriously on the client." I got myself a fresh latte coffee and sat down to complete the survey.

  Unfortunately, the survey questions were a tad different than what I was hoping for. After a lot of questions about what desktops I used and what I was planning to use, I felt like I was filling in a Computer Weekly subscription form. Finally, up came the burning issues that Sun wants to get our input on: two questions about JFileChooser.

  Here's my answer folks: I don't care diddly squat about the file chooser, nor do my users. I build applications that are concerned with viewing, displaying, and editing database entries. The software has to integrate with multiple back-end technologies, make use of different messaging protocols, and interface with call-center telephony and voice response systems. My users' programs have to calculate claim amounts based on catastrophe reinsurance spirals, and they do this by interfacing to spreadsheets and news services. This is the bread and butter of application development for anyone who is involved in serious business software.

  This is what I want to see done to J2SE client development.

  Ditch emulated widgets. It's yesterday's problem, and users want their applications to look and behave like other desktop programs. Most companies standardize on a desktop, and instead of Sun spending time writing lots of fancy Java code that pretends to be a native widget, just use the native widget. infragistics JSuite and Quest JClass already provide good native extended AWT controls, and I'm tired of hearing that it can't be done because of different cross-platform focus processing. If SWT and others get it to work, so can you. Antialiased fonts and mitred line corners in Java 2D can be used by people who need them, but for most business apps that are concerned with data display and entry, just give us the extra native controls we need. And, on Windows give us better ActiveX integration. One user told me, "It's not even a case of Swing programs playing second fiddle to Visual Basic on Windows; the best it can do is stand in the back row of percussion and occasionally burp."

  Rethink what layout managers are all about. If they're designed to allow multilingual GUIs, they're the wrong solution. I've worked for international companies that deploy apps in different branches across the world, and more often than not they standardize on a single language. If the program does need translating, then J2SE needs something similar to the .nib files of interfaceBuilder, where the entire GUI is serialized as a separate file that's hand customized for each locale. The XMLEncoder sort of provides the beginnings of this, but this needs to go further and be formalized into a standard GUI architecture that allows true separation of business from display logic.

  Segueing into my final point, rethink how listeners work. J2SE client development tends to encourage almost reckless use of inner classes for event handling logic, and inner classes are expensive to load and require flashy VM trickery to work. Someone needs to go back to square one and look at how other languages such as Python and Smalltalk deal with this, and maybe introduce some way of soft typing event callbacks.

  I looked for the bit at the end of the survey that lets me type in comments that I want the Swing team to read; however, there was only a tiny text box available. Next time make the box bigger, plea

<script type="text/javascript"><!-- google_ad_client = "pub-2947489232296736"; /* 728x15, 创建于 08-4-23MSDN */ google_ad_slot = "3624277373"; google_ad_width = 728; google_ad_height = 15; //--> </script> <script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script>
<script type="text/javascript"><!-- google_ad_client = "pub-2947489232296736"; /* 160x600, 创建于 08-4-23MSDN */ google_ad_slot = "4367022601"; google_ad_width = 160; google_ad_height = 600; //--> </script><script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js"> </script>

opensso 单点登录

  • 2010年11月04日 09:21
  • 873KB
  • 下载

OpenMP API 用户指南(Sun Studio).pdf

  • 2007年07月21日 15:43
  • 610KB
  • 下载

servlet-3_0-final-spec.pdf

  • 2010年01月06日 08:30
  • 1.37MB
  • 下载

数据挖掘之clara算法原理及实例(代码中有bug)

本文讲解了大数据聚类算法中的一种clara.并通过matalb实例代码实现验证算法
  • u013018721
  • u013018721
  • 2014-07-21 20:31:00
  • 2032

文本挖掘之聚类算法之CLARA聚类算法

CLARA (Clustering LARge Applications,大型应用中的聚类方法)(Kaufmann and Rousseeuw in 1990):不考虑整个数据集, 而是选择数...
  • u011955252
  • u011955252
  • 2016-03-04 19:37:56
  • 934

Clara算法的总结

总结 一、步骤: CLARA从数据集中抽取多个样本集,对每个样本集使用PAM,并以最好的聚类作为输出。 具体步骤: 1)  for i = 1 to v (选样的次数),重复执行下列步骤( (...
  • u013834836
  • u013834836
  • 2014-11-17 19:37:46
  • 1467

Codeforces Round #389 (Div. 2)B. Santa Claus and Keyboard Check(模拟)

题目: B. Santa Claus and Keyboard Check time limit per test 2 seconds memory limit per...
  • riba2534
  • riba2534
  • 2016-12-26 11:41:48
  • 336

CodeForces 748E. Santa Claus and Tangerines

Santa Claus has n tangerines, and the i-th of them consists of exactly ai slices. Santa Claus ca...
  • wxh010910
  • wxh010910
  • 2016-12-30 21:51:07
  • 431

【Codeforces 748 C Santa Claus and Robot】+ 思维

C. Santa Claus and Robot time limit per test 2 seconds memory limit per test 256 megabytes inpu...
  • WYK1823376647
  • WYK1823376647
  • 2016-12-26 19:26:09
  • 484

Codeforces Round #389 C. Santa Claus and Robot

C. Santa Claus and Robot time limit per test 2 seconds memory limit per test 256 megabytes ...
  • Ginray
  • Ginray
  • 2016-12-27 22:22:28
  • 511
收藏助手
不良信息举报
您举报文章:Sun Stroke in Santa Clara @ JDJ
举报原因:
原因补充:

(最多只允许输入30个字)