I’m having a strange issue with trunk and IE8 where the browser’s
history stack inexplicably “disappears”. That is, the history drop
down list empties (including previously visited non-GWT sites, like
MSN) and the back/forward buttons don’t work. My guess is that this is
a bug in IE8 that GWT is
for a
Firefox 3.5 regression they are shipping today).
Cheers,
joel.
On Tue, Jun 30, 2009 at 12:01 AM, Amir Kashani amirkash...@gmail.comwrote:
I’m having a strange issue with trunk and IE8 where the browser’s
history stack inexplicably “disappears”. That is, the history drop
down list empties
, but not the linker changes. We're going to be
releasing out of this branch very soon (as soon as we merge the fix for a
Firefox 3.5 regression they are shipping today).
Cheers,
joel.
On Tue, Jun 30, 2009 at 12:01 AM, Amir Kashani amirkash...@gmail.comwrote:
I’m having a strange issue
are resolved.
Thanks,
joel.
On Wed, Jul 1, 2009 at 10:57 PM, Amir Kashani amirkash...@gmail.comwrote:
I've verified that making the following changes to the 1.6 release
branch causes the bug:
- Replace IFrameTemplate.js with tr...@r5523
- Modify line 430 to not append .cache.html (seems
script to get this fixed
(at least for now). Thank god we didn't put this in the 1.6 release branch.
On Tue, Jul 7, 2009 at 2:29 PM, Joel Webber j...@google.com wrote:
On Tue, Jul 7, 2009 at 1:40 PM, Amir Kashani amirkash...@gmail.comwrote:
Opened issue 3808 and attached a patch
If possible, could someone who is familiar with the ClientBundle /
ImageResource architecture take a look at this issue and let me know if my
diagnosis of the problem seems accurate. If so, does my suggested solution
seem like the appropriate approach?
If so, I'd happily spend the time to create
Hello, yourself. This looks absolutely awesome! Thank you!
- Amir
On Tue, Aug 4, 2009 at 10:44 AM, rj...@google.com wrote:
Reviewers: jgw,
Description:
Introduces UiBinder
http://code.google.com/p/google-web-toolkit-incubator/wiki/UiBinder
The actual source code has been through
.
On Tue, Aug 4, 2009 at 3:42 PM, Amir Kashani amirkash...@gmail.comwrote:
What are the limitations for a Widget developer without a custom parser?
I've only begun to look at the code, but it seems like it'll still be
possible to use a custom widget albeit with cumbersome markup.
- Amir
Joel,
I love how this is turning out so far, great work. While this system handles
a vast majority of layout situations, correct me if I'm wrong, but I think
it breaks down with non-100% height layouts that require a footer. An
example: a header area, followed by a horizontally split content area
prev buttons.
Can this layout handle this?
Excellent work as always. I'm keenly following this. Can't get it
quick enough :)
On Aug 10, 9:26 am, Amir Kashani amirkash...@gmail.com wrote:
Joel,
I love how this is turning out so far, great work. While this system
handles
a vast majority
, 2009 at 1:36 PM, Amir Kashani
amirkash...@gmail.com
wrote:
As Ray mentioned, one has a pretty simple workaround and two is
pretty
uncommon. I'm a little more concerned about the third case. A
few
examples
of issue with internally used widgets I've created
For my last work project, we used Kiyaa!, a GWT library that offers its own
declarative UI system (and data-binding). In addition, we used PureMVC as a
very lightweight MVC-framework. If you're familiar with PureMVC, you'll know
that it's much closer to MVP, as described by Ray Ryan, than it is a
, Amir Kashani amirkash...@gmail.com wrote:
For my last work project, we used Kiyaa!, a GWT library that offers its
own
declarative UI system (and data-binding). In addition, we used PureMVC as
a
very lightweight MVC-framework. If you're familiar with PureMVC, you'll
know
that it's much
While we're on the topic, it doesn't seem that the BundleAttributeParser
catches these special attributes. Specifically,
gwt:Button res:addStyleNames=css.myCssClass /
doesn't seem to work.
- Amir
On Wed, Aug 26, 2009 at 8:56 AM, Ray Ryan rj...@google.com wrote:
And you can set the debug id
implementing the expression language
stuff mentioned in the wiki entry (
http://code.google.com/p/google-web-toolkit-incubator/wiki/UiBinder). So
that line will become something like:
gwt:Button addStyleNames=res.css.myCssClass /
rjrjr
On Wed, Aug 26, 2009 at 3:18 PM, Amir Kashani amirkash
Oh, carry on then. Good show!
- Amir
On Wed, Aug 26, 2009 at 3:13 PM, Ray Ryan rj...@google.com wrote:
On Wed, Aug 26, 2009 at 5:23 PM, Amir Kashani amirkash...@gmail.comwrote:
Hmm, I don't have it handy but it's the name xmlns I use for all other
resource injection, and those work fine
26, 2009 at 3:18 PM, Amir Kashani amirkash...@gmail.comwrote:
While we're on the topic, it doesn't seem that the BundleAttributeParser
catches these special attributes. Specifically,
gwt:Button res:addStyleNames=css.myCssClass /
doesn't seem to work.
- Amir
On Wed, Aug 26, 2009 at 8:56
with addStyleNames, which gets special handling.
Do you mind filing an issue?
The new syntax hasn't been committed yet, it's in review. Although now that
I think about it, it just might accidentally fix this problem. Which is
nice.
On Fri, Aug 28, 2009 at 9:34 AM, Amir Kashani amirkash
Fairly recently, we converted our app to make extensive use of CssResource
and StyleInjector. When we did this, we noticed a *huge* performance
bottleneck while generating the stylesheets, causing development mode to
take about a minute to start. Using a (Java) profiler, I noticed about 90%
of the
, Amir Kashani amirkash...@gmail.com wrote:
Fairly recently, we converted our app to make extensive use of CssResource
and StyleInjector. When we did this, we noticed a *huge* performance
bottleneck while generating the stylesheets, causing development mode to
take about a minute to start. Using
And refactoring? =)
I'm loving UiBinder as it is, but it'll be that much better with IDE
support.
- Amir
On Tue, Sep 15, 2009 at 8:09 AM, Jason Parekh jasonpar...@gmail.com wrote:
Hey Brett,
You can definitely expect to see some great UiBinder support in an upcoming
version of the Google
.)
On Wed, Sep 16, 2009 at 8:01 PM, Amir Kashani amirkash...@gmail.comwrote:
Ray,
Not sure if UiBinder and ui:style are far enough along that I should be
putting bugs in the issue tracker or just posting here. If you'd rather me
create bugs, let me know.
There seems to be issues with handling CSS
On Thu, Sep 17, 2009 at 9:21 AM, Ray Ryan rj...@google.com wrote:
On Wed, Sep 16, 2009 at 8:52 PM, Amir Kashani amirkash...@gmail.comwrote:
See issues 4052 and 4053.
You mean class names defined inline, right? Not supporting these
identifiers for @external class names could be an issue
http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM
Interesting setup ;-)
http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM- Amir
On Mon, Oct 5, 2009 at 11:46 PM, David david.no...@gmail.com wrote:
Hi,
Great news, just one question that some other people might want to
I think using it would be the first step of fixing Issue 4052. Of course,
the harder half is keeping track of the Java-safe method names and making
the appropriate substitution when you run into a brace expression. I suppose
that requires maintaining some state (namely, a map of class name
If any work is going to be done in consideration to 4052, it's probably
worth keeping
http://code.google.com/p/google-web-toolkit/issues/detail?id=4053 in mind,
as they're likely related.
- Amir
On Wed, Oct 7, 2009 at 11:49 AM, rj...@google.com wrote:
LGTM
I'm not sure if it's worth the
HTMLPanel's ability to mimic other tags is limited in that it can't become a
TR or TD. Following the implementation, it's clear why: placing these
elements without their requried parent tags into a DIV is invalid so the
browser never creates the DOM element that HTMLPanel requires. UiBinder is
of the table/grid widgets to dynamically allocate rows?
Besides FlexTable you might also look at the incubator's PagingScrollTable.
On Oct 9, 2009 6:23 PM, Amir Kashani amirkash...@gmail.com wrote:
HTMLPanel's ability to mimic other tags is limited in that it can't become
a TR or TD. Following
Looks like this covers issue 4052, no?
- Amir
On Mon, Nov 16, 2009 at 1:15 PM, rj...@google.com wrote:
Reviewers: jasonparekh1,
Message:
Jason, can you take this?
Description:
Fixes bad code gen when css class names in a ui:style block have dashes
in them, by adoptiung a convention that
I haven't looked at the patch, but it sure sounds like it!
On Mon, Nov 16, 2009 at 2:52 PM, Ray Ryan rj...@google.com wrote:
Yup, thanks. And 4053?
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
While I think deprecating these widgets is definitely the right move, I
don't think the normal policy of removing them after one release will work
(is this still the actual policy?). Breaking an application's dependence on
these widgets and switching to the new equivalents is a particular daunting
I know 2.1 doesn't include any effort at linking the new frameworks
together, but it seems that there were some ideas thrown around before
feature freeze. Specifically, I've stumbled upon various classes that were
once commited as part of the Expenses app
Ted,
Are you familiar with the XForms specification? I think the original goal
was to get browser vendors to implement it to replace HTML forms, which
doesn't seem to be happening, but it's a very solid in dealing with a lot of
the use cases of form creation pretty gracefully. EMC even has a GWT
We've adopted the new MVP framework pretty heavily in a couple of new
projects and at this point, I don't think we've ever not used
AbstractActivity. So, as long as the existing methods in Activity don't
become inaccessible to non-GWT code (i.e. not package protected or final), I
don't see a
I don't know what features are planned or contemplated beyond what Neil
mentioned, but could the use of sub-interfaces help? For example, Neil's
feature (+1 BTW) might use a PlaceAwareActivity which extends Activity?
AbstractActivity can potentially implement them all new sub-interfaces.
The
35 matches
Mail list logo
