g*****g
发帖数: 34805 | 1 The problem with GWT is, it's a totaly different approach.
It's pretty hard to integrate it to your original design.
Gradual adoption is not possible. |
|
x****y
发帖数: 252 | 2 I have used DWR, which is similar to GWT, supports AJAX, and should be
easier to be intergrated to original design. |
|
t*******e
发帖数: 684 | 3
有没有可能把Designer设计的网页转换成GWT,ZK开发的网站，而保持look&feel没有任
何变化的。 |
|
S*********t
发帖数: 78 | 4 it seems better than GWT. |
|
t*******e
发帖数: 684 | 5 For developers, it boils down to the choice of an HTML centric development
approach or an Ajax centric approach. Conventional web frameworks (Struts,
JSF, Wicket, Webwork...) are all designed for HTML centric development
efforts. While GWT, Echo, ZK are Ajax centric.
In the sense that a web project begins with HTML design, conventional web
frameworks are probably better choices. |
|
k***r
发帖数: 4260 | 6 I think gwt is more for RIA, the whole app with widgets.
JQuery is a real js library. Also try ExtJS or YUI |
|
b******y
发帖数: 9224 | 7 I am also trying out GWT... |
|
u*****n
发帖数: 3277 | 8 thanks. guys.
have you used google GWT? is it a good option for this purpose too?
problems. |
|
D*****a
发帖数: 41 | 9 Try GWT and you can enjoy more if you are a pure Java programmer!! |
|
b******y
发帖数: 9224 | 10 Yep, I like GWT, widely supported and open source. |
|
k***r
发帖数: 4260 | 11 Seriously, what "more" do you get if you compare GWT with
the component frameworks? |
|
g*****g
发帖数: 34805 | 12 GWT is a pure client framework, it's fine at doing what it's doing.
But it may fall short when doing
1. When you need custom component
2. When integrate with traditional web design
Every framework has advantage and drawback, but there's no one fits all
approach. After evaluate many frameworks, I agree with this option.
Stripes is best action-based framework, Wicket is best component framework. |
|
w*r
发帖数: 2421 | 13 it is true J2EE grows too complicated and framework looks nice but the
choices between frameworks cost a lot of learning curve. I guess the
solution is to keep up learning and keep up working . How about setup a
project like write something like bbs from basic jsp and then switch to jsf,
and then spring, and then change backend to hibernation and then switch to
use gwt ... and ...
it should get you up to speed... |
|
t*******e
发帖数: 684 | 14 有web designer设计网页的话，就不需要学。没有的话可以学点，也可以用ajax
frameworks, 比如Zk, echo, GWT. |
|
d*g
发帖数: 66 | 15 谢谢goodbug
I may need to report why I choose SPring MVC, so would you please give me
some good strong reasons....
and if Spring MVC to handle the request, anything good to fit into Gui side,
like build a table or tree structure... do you recommend just pure jsp +
html or anything else lke GWT?
Thanks a lot |
|
g*****g
发帖数: 34805 | 16 It's a traditional front controller MVC framework, people
with JSP/Struts background may see it familiar. It's flexibile
and popular so if you get a problem, you probably can find an
answer by google. For table and tree components, if plain jsp
can do it for you, it'd be most simple. For a little bit of ajax
components, I'd recommend Dojo, GWT is more difficult to integrate.
If you want to go full fledge ajax, spring mvc won't be the right
choice. Personally I'd recommend wicket for that kind of |
|
h**k
发帖数: 662 | 17 感觉用java 产生界面应该不是很强大把，怎么跟直接用javascript比那？跟其他
framework容易结合吗。 |
|
g*****g
发帖数: 34805 | 18 控件有限，跟其他framework不容易结合。 |
|
s******n
发帖数: 876 | 19 好象google最关心的是cross-browser comparability.
用户群太大，nitch browser market对她们来说也不是个
可以忽略的小数目.
另外的可能性是他们闲人太多，没事找事。 |
|
k***r
发帖数: 4260 | 20 Just to be exact - they will own your "front-end" in
this particular case :-)
There is a Python project that works in a similar way
but is open source. |
|
c*****t
发帖数: 1879 | 21 What's the point of using Python? Really odd.
Using Java because you can take advantage of static compiling,
refactoring etc. |
|
k***r
发帖数: 4260 | 22 Python has a great deal of advantages over Javascript. |
|
c*****t
发帖数: 1879 | 23 Like?
JS is not a toy language by itself. |
|
m******t
发帖数: 2416 | 24 I really don't think js is inherently (that is by language design)
more "mess-prone" than python or any other dynamically
typed languages. I have seen both very well readable js code
and messy python code.
The bad reputation of js probably came from the fact taht
for a very long time it's the only choice to do anything even
remotely fancy on the client-side, so every html author
used it. And unfortunately most of them never received
enough programming training to produce proper
code. |
|
g*****g
发帖数: 34805 | 25 And the cross browsing issue never helped.
In short, browser should take a more intelligent, more
strict language than html and js. An extensible xml format
with rich components will be nice. HTML5 is in that direction,
but we have to stick to what we have now. |
|
k***r
发帖数: 4260 | 26 A great part of the problem is the tolerance of the browsers
to poorly written buggy js. This makes it impossible, or at
least very difficult to tell what's right or wrong in html/js.
What makes it worse is that different browsers have different
ways of rendering html/js with bugs/errors. This is a great
part of the whole browser compatibility problem.
And the strategy is to avoid fiddling with JS. Instead, code
in a different language (be it Java or Python or Perl, etc.)
and generate well-teste |
|
b******y
发帖数: 1684 | 27 最近项目里面front end跟不上，只好去跟着弄了一下js, jquery什么的，
很没劲啊。 |
|
F****n
发帖数: 3271 | 28 Believe it or not, front end is always the hard part. |
|
g*****g
发帖数: 34805 | 29 Depends on what kind of website, the more users you have,
the more complicate backend will be. |
|
I*******o
发帖数: 53 | 30 sigh...
what are the leading/major front technology now? js? |
|
|
|
w******g
发帖数: 2047 | 33 Very impressive, it is now called smart gwt, very impressive |
|
|
k***r
发帖数: 4260 | 35 老话题，呵呵
有些历史但是现在不时髦的的就先不说了，现在还火爆的里面，比较传统的
还算简单的有stripes。新一点的有component based wicket,
Echo 2/Echo 3, Vaadin。专门做RIA的ZK, Click，还有client
的framework GWT, Flex, 乱花渐欲迷人眼。
goodbug推崇wicket，版上还有几位推荐过ZK。偶目前对Vaadin比较感
兴趣。Echo 2/3的widgets十分强大，不过貌似比较笨重。ZK的widget
看上去不太好看，呵呵。
大家谈谈你用过的framework吧！ |
|
h**k
发帖数: 662 | 36 谢谢，技术上说，我也更喜欢extgwt，另外，虽然smartgwt有免费的version，但也只
限于client,server functions还要交钱。 |
|
m******o
发帖数: 774 | 37 Have not done anything but reading GWT stuff. I have to say that I
completely agree with you on this. I will begin to play with it and
seriously recommend it to every java developer (who happens to be here and
reads this :o)
. |
|
k****u
发帖数: 133 | 38 To be more precise, declarative languages like XML/HTML is the best choice
for UI layout, as how people used to design/layout HTML pages. But there
still needs to be some bindings from XML elements to Java UI components so
that we can add UI logic, event handling, remoting, etc to the UI components
. That's exactly how Flex programming model works (MXML for layout and
ActionScript3 for programming components) and GWT obviously is going under
the same route. |
|
m******t
发帖数: 2416 | 39 I have a side project that uses flex. The declarative stuff was nice in the
beginning, but soon it became restrictive because I was trying to add some
highly dynamic logic.
I'm working on a project using gwt now, and for that reason I'm not really
very thrilled by the new xml UI in 2.0.
components |
|
m******o
发帖数: 774 | 40 本来在试Spring，这中间不知怎么跑到GWT去了，接着又看到vaadin。感觉vaadin非常
的有潜力啊，各位大牛意下如何？ |
|
k****u
发帖数: 133 | 41 Ironically, the desktop-like web apps don't scare people away at all, in the
contrary, people are seeking hard for the high interactiveness of the
desktop GUI on today's RIAs. And that's exactly where major RIA frameworks like GWT/
Flex are heading towards.
feel
Who |
|
g*****g
发帖数: 34805 | 42 But you can take far less time to build Gmail with Vaadin,
that's the point. Gmail predates GWT. |
|
m******t
发帖数: 2416 | 43
how
GWT encourages css based styling, and from I read, so does vaadin.
So it may be easier than you imagine to have page designers working
in parallel with developers. |
|
b*****t
发帖数: 1276 | 44 Yeah, if you have committed to use GWT, then there is no reason that you
should not use Vaadin.
same |
|
k****u
发帖数: 133 | 45 找工作的一条真理：一定不能心虚。java的各种framework这几年如雨后春笋般涌现，
没有人能全部精通，掌握好自己用过的几个，然后展现出你的学习能力和自信，这才是
最重要的。关于具体的，middle tier依然是spring的天下，persistence的话应该还是
hibernate，presentation tier有多个选择：jsf, gwt, flex。按照上面的去找，应该
不会差。 |
|
k****u
发帖数: 133 | 46 GWT or Flex, both are client side and give you editability, and much clean
to program than JS.
us. |
|
g**********y
发帖数: 14569 | 47 That's good alternative. But very strange, even Google itself rarely use GWT. |
|
|
g**********y
发帖数: 14569 | 49 en, 那我得学学GWT去，client端的app还是很有前景的。 |
|
m******t
发帖数: 2416 | 50 The out of box experience was impressive. I like the easy and
straightforward paradigm, which makes it possible to spend
most of the time actually implementing features, instead of
learning the tool. And the ability to implement logic in
full java capabilities (vs. GWT's watered-down subset) is
incredibly satisfying.
The big concern though is that the price we pay for all the
good things above is to do everything on the server. The UI
isn't going to be very snappy due to network latency. No
matt |
|
