Please take a look at the Automated Testing overview for SmartGWT:
http://www.smartclient.com/smartgwtee-latest/javadoc/com/smartgwt/client/docs/AutomatedTesting.html
If you aren't using one of the tools here, pay special attention to the
Other Tools section, which explains that SmartGWT
Hi Kumar,
SmartGWT has an extensive subsystem for interacting directly with WSDL web
services from the browser. Some samples here:
http://www.smartclient.com/smartgwtee/showcase/#data_integration_server_wsdl_weather
This is all part of the free LGPL product, assuming you don't need a
(d) does not apply to SmartGWT. No GWT update has ever broken SmartGWT or
broken backcompat.
(e) does not apply to SmartGWT. Nightlies are available for all editions -
see smartclient.com/builds
(c) presumably means customizing a widget by messing with it's DOM or
overriding internal
(d) no release of GWT has ever broken SmartGWT. We don't rely on much from
GWT other than Java-JavaScript translation, so there is little room for
something to break.
(c) This may refer to breakage from customizations like modifying a
component's DOM or overriding internals. In SmartGWT we
Isomorphic Support routinely receives kudos from customers and the
community, with 20-30 forum posts a day coming right from the dev and
support teams. When we aren't helping individuals, we're creating new
samples and writing new docs for everyone.
This person (sbt) is not a customer, posted
Sorry that's quite absurd: SmartGWT is often introduced to solve
performance problems, and it solves them.
SmartGWT is intentionally designed to have a one-time-ever download of
a feature rich runtime in exchange for reducing subsequent server
requests. For example, Adaptive Filtering greatly
That JMeter testing sounds invalid. You're simulating the repeated
download of static resources that in reality happens once ever per
user.
SmartGWT is designed for applications that are used more than once per
user, and/or that users spend at least a few minutes with. In that
scenario,
understandable that experience with some previous
framework would make someone think so, but it's very easy in SmartGWT,
and we think an explicit destroy() is the right approach in terms of
giving us the opportunity to work around browser garbage collection
bugs.
On Sep 7, 7:22 pm, ckendrick charles.kendr
Just a note on SmartGWT -
Built-in GWT widgets rely on the browser to garbage collect a detached
DOM tree. In older browsers like IE6/7 we found a number of cases
where this didn't work completely, so we opted for manual destroy().
It's possible that as of IE8/9 all such leaks are gone
You should post this in the SmartGWT forums at forums.smartclient.com.
On Jun 14, 8:09 am, samounas elmokhtari.as...@gmail.com wrote:
Can u help me please?
On 14 juin, 14:55, samounas elmokhtari.as...@gmail.com wrote:
Hi,
I have a problem with the file mapping of JPA anddatasource.xmlof
Be sure to compare the cost of the product to the value of your time
spent re-creating the same functionality, maintaining it, and missing
out on all features we keep adding to the SQL subsystem. As well as
not finishing your project as soon, slipping deadlines etc. As well
as delivering a
What layout issue on what browser with what code? This is not a known
issue, so to get it addressed, post a test case to the SmartGWT
forums:
http://forums.smartclient.com/forumdisplay.php?f=14
On May 11, 12:25 pm, Alan Chaney a...@mechnicality.com wrote:
Hi
I've started to build an
too much to deliver for the ultralight use case.
It's just different designs for different use cases.
I hope the core GWT widgets continue to focus on the ultralight use
case, because there's just nothing comparable, especially for mobile.
On Mar 12, 12:44 pm, ckendrick charles.kendr...@gmail.com
And here are the authors to disagree :)
1) Yes, we make intentional departures from the GWT way, such as..
2) SmartGWT has better cross-browser consistency than GWT itself.
Why? Because GWT relies on native browser behavior and CSS for
layout, and this is where all the quirks come from. We do
In addition to new client-side features already detailed here:
http://www.jroller.com/sjivan/entry/smart_gwt_2_1_released
New server features:
* New built-in server-side validators
isUnique makes it trivial to enforce common cases like having
a unique user name.
Apologies for the second posting. Some links were mangled, they are
corrected below.
In addition to new client-side features already detailed here:
http://www.jroller.com/sjivan/entry/smart_gwt_2_1_released
New server features:
* New built-in server-side validators
isUnique
Carl,
On skins, you don't sound as though you've looked at the Showcase
since 2.0, when we made a series of improvements which now has most
users commenting that our skins are sharper than GXTs.
On grids, this is the first time I've ever seen someone claim the GXT
grids are better, I really
advantages related to grids, however this and my
previous post are probably the best answer to the original question:
what are the technical advantages.
On Feb 15, 12:02 pm, ckendrick charles.kendr...@gmail.com wrote:
Carl,
On skins, you don't sound as though you've looked at the Showcase
since 2.0
Just to sum up, the only people in this thread reporting negative
hands-on experiences with SmartGWT have all gone against our explicit
advice in the documentation, FAQ, and in some cases, personal
attention in the forums.
The only person with hands-on experience claiming there are bugs
turned
@Jeff, ahhughes: as far as the built-in GWT widgets, they are well-
designed and fine for simple things, but if your requirement is to
have a grid that supports full-row inline editing, grouping,
filtering, frozen columns, paging through large datasets, resizable/
reorderable headers with
Re: widgets inside grid rows: not only is it out of the box in
SmartGWT, there are multiple out of the box modes for it, including
nested editable grids.
http://www.smartclient.com/smartgwt/showcase/#featured_nested_grid
Library.
ckendrick and I have different understandings about override ... :-P
We already discussed this some time ago ...
SmartGWT you can't override it's functionality, just it's behavior.
SmartGWT is more feature rich than GXT, but I don't like their
licensing terms, I prefer GXT one
With SmartGWT you can also extend widgets and override methods in pure
Java.
Just a tour through the SmartGWT and SmartGWT Pro/EE showcases should
be enough to identify a number of feature advantages which may matter
for your application.
http://www.smartclient.com/smartgwt/showcase/
On Jan 12, 3:43 pm, Open eSignForms yoz...@gmail.com wrote:
If you need the widgets now, SmartGWT seems like a fine solution, and the
LGPL is a nice license if you don't otherwise need their
server-side/enterprise features. Pure GWT just doesn't have those grids and
such yet, but it sounds
Incorrect, SmartGWT allows both. Purchasing a license does not imply
that you *must* use the closed-source server-side portion. If you use
just the capabilities of SmartGWT LGPL, you can offer the LGPL
licensing terms to customers that prefer it, and you can purchase a
license from Isomorphic to
On Jan 12, 12:39 pm, Kenny G ken.grei...@gmail.com wrote:
I found it well worth the time to use, even though I did
not use the Datasource features to populate grids.
Whoah! Kenny you should really try the DataSource feature next time,
you have so far used less than half of what even the free
On Dec 26 2009, 3:51 am, gaill...@audemat.com gaill...@audemat.com
wrote:
You can't stat about 'uninformed choice', quick doesn't mean dirty
Even creating new widgets could be made easily with GWT, with SmartGWT
we must have good javascript skill to achieve the same task
This statement is
If the choice was made quickly it was probably an uninformed
choice. We don't have anyone complaining that there is less
customization so perhaps you could clarify that.
With SmartGWT Pro and EE, you can literally open up a visual tool and
create a fully functional CRUD interface to Hibernate by
- not every override point
from SmartClient is yet available in SmartGWT, but we are getting
closer to that all the time.
On Aug 16, 8:45 pm, Tercio Filho terciofi...@gmail.com wrote:
On Aug 16, 7:39 pm, ckendrick charles.kendr...@gmail.com wrote:
@tercio You're still missing the key point
a purchase of SmartGWT Pro,
where the amount of SmartGWT-specific server code involved is
literally zero for many cases, and very small for the others.
On Aug 16, 12:27 pm, Tercio Filho terciofi...@gmail.com wrote:
@ckendrick
The way SmartGWT works, every component caches it's data,
independently
is the way to go, but
remember that your minimum app is going to be 1mb in size because of
the SmartGWT core files.
On Aug 14, 10:34 pm, ckendrick charles.kendr...@gmail.com wrote:
Hi Malte,
As far as once-ever load time, if you're building an enterprise
application
Hi Malte,
As far as once-ever load time, if you're building an enterprise
application with several screens and lots of productivity features,
you're going to be using substantially all of SmartClient - if it was
written in Java, the impact of the GWT compiler's static analysis
would be
://www.smartclient.com/smartgwt/download.jsp
isn't working.
On Aug 4, 9:16 pm, ckendrick charles.kendr...@gmail.com wrote:
We do give you the ability get in and override any part of the
generated SQL as a Velocity template. Simple example:
http://www.smartclient.com/smartgwtee/showcase
With SmartGWT you can represent a data structure as a DataSource. A
DataSource can be tied to any kind of data provider - not just
different JPA implementers but also WSDL web services, REST services,
non-JPA persistence systems like Ibatis, etc. The persistence engine
is pluggable, so you can
DataSource in
SmartGWT EE.
On Aug 4, 4:16 pm, John Ivens john.wagner.iv...@gmail.com wrote:
There are no examples that I know of actually showing a connection, for
example with a sample mysql database or really anything else. Please
correct me if I'm wrong.
On Tue, Aug 4, 2009 at 3:42 PM, ckendrick
, where I kludged Hibernate to be able to store XML in the
database?
On Tue, Aug 4, 2009 at 4:38 PM, ckendrick charles.kendr...@gmail.comwrote:
Hi John,
For live connections to SQL, Hibernate and other data providers see
the SmartGWT Pro/EE showcase:
http://www.smartclient.com
If you use the free version, you use RestDataSource as the starting
point for integration. RestDataSource simply specifies XML or JSON
messages to send and receive with your server; it is totally agnostic
as to how your server is implemented (it could, for instance, be PHP).
SmartGWT is an popular, open source, extremely rich widget library and
databinding framework for GWT, available under the LGPL. SmartGWT
Enterprise Edition (SmartGWT EE for short) is a commercially licensed
version of SmartGWT that includes Java Server side functionality,
additional tools, and a
If SmartGWT seems slow, just disable Firebug or similar development
utilities, and be sure you haven't done anything like completely
disabling browser caching. For normal end users who don't have these
tools or settings, it's quick.
On Dec 19, 7:13 am, Juan Backson juanback...@gmail.com wrote:
Lest anyone get the wrong idea from francesco, when using SmartGWT you
can debug your GWT *application* code normally within hosted mode.
If you had a need to debug the core SmartClient libraries (normal
users will not have a need to do this), you'd use debugging tools like
Firebug and
40 matches
Mail list logo
