Re: API design rant!
My rant about GXT: http://groups.google.com/group/google-web-toolkit/msg/693cacbce437d08a The summary: GXT was a waste of $600 and one month of my time. Please don't emulate GXT. Jeff On Thu, Sep 30, 2010 at 5:14 AM, Slava Lovkiy slava.lov...@gmail.com wrote: I am 100% agree about GXT Api as being not extensible, causing to produce parallel suite of widgets. On Sep 30, 3:39 am, Jeff Larsen larse...@gmail.com wrote: GWT may not have the most perfect API design, but saying GXT is a design to implement is laughable at best. GXT has just barely enough good things to make it worth using. BARELY. I keep their crappy library segregated behind interfaces and wrap all their even types waiting for the day I can rip that giant pile of crap out of my project. Tell me without going to the docs or drilling into their source what events a GXT button can handle. You can't by just looking at their API. You want to extend some of their controls, you're screwed because they, for not reason I'm able to discern, have tons of private variables with no getter/setter. If you want slow crappy code where you're constantly forced to go to the documentation then use GXT. If you want to extend one of their classes you could easily be copy/ pasting a ton of their code/heirarchy in order to get some minimal functionality included. On Sep 29, 9:06 am, markM mark.a.mccon...@pfizer.com wrote: I think we often times forget too that folks are producing these products for us for free. One can always pay for GWT EXT if they like. On Sep 28, 12:38 pm, Brett Thomas brettptho...@gmail.com wrote: Not to mention none of those three things have to do with API Design... On Tue, Sep 28, 2010 at 12:01 PM, Thomas Broyer t.bro...@gmail.com wrote: On Sep 28, 4:29 pm, Greg Dougherty dougherty.greg...@mayo.edu wrote: Well, look at the JavaDoc for extended by com.google.gwt.dom.client.Style.Unit (AKA Style.Unit). I don't think it's possible to write worse Documentation than that, other than perhaps writing something that is actively and consistently wrong. Which doc are you talking about? the CSS length units part? (what more should it say? if you don't know what a CSS length unit is, you'd better stop doing web dev; or start learning CSS) the values and valueOf part? (they're not in the code, they come with the enum type, just like extends java.lang.EnumStyle.Unit) I assume people actually test code before it gets added to the project. I assume those text cases are a pretty through workout of all the code's claimed features. It's an Open Source project, so I assume there's no commercial reason to keep those test cases hidden. You mean these test cases? http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/... Given that, why are there no *LayoutPanels in Showcase? Fixed:http://code.google.com/p/google-web-toolkit/source/detail?r=8766 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2Bunsubs cr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.-Hidequoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
I am 100% agree about GXT Api as being not extensible, causing to produce parallel suite of widgets. On Sep 30, 3:39 am, Jeff Larsen larse...@gmail.com wrote: GWT may not have the most perfect API design, but saying GXT is a design to implement is laughable at best. GXT has just barely enough good things to make it worth using. BARELY. I keep their crappy library segregated behind interfaces and wrap all their even types waiting for the day I can rip that giant pile of crap out of my project. Tell me without going to the docs or drilling into their source what events a GXT button can handle. You can't by just looking at their API. You want to extend some of their controls, you're screwed because they, for not reason I'm able to discern, have tons of private variables with no getter/setter. If you want slow crappy code where you're constantly forced to go to the documentation then use GXT. If you want to extend one of their classes you could easily be copy/ pasting a ton of their code/heirarchy in order to get some minimal functionality included. On Sep 29, 9:06 am, markM mark.a.mccon...@pfizer.com wrote: I think we often times forget too that folks are producing these products for us for free. One can always pay for GWT EXT if they like. On Sep 28, 12:38 pm, Brett Thomas brettptho...@gmail.com wrote: Not to mention none of those three things have to do with API Design... On Tue, Sep 28, 2010 at 12:01 PM, Thomas Broyer t.bro...@gmail.com wrote: On Sep 28, 4:29 pm, Greg Dougherty dougherty.greg...@mayo.edu wrote: Well, look at the JavaDoc for extended by com.google.gwt.dom.client.Style.Unit (AKA Style.Unit). I don't think it's possible to write worse Documentation than that, other than perhaps writing something that is actively and consistently wrong. Which doc are you talking about? the CSS length units part? (what more should it say? if you don't know what a CSS length unit is, you'd better stop doing web dev; or start learning CSS) the values and valueOf part? (they're not in the code, they come with the enum type, just like extends java.lang.EnumStyle.Unit) I assume people actually test code before it gets added to the project. I assume those text cases are a pretty through workout of all the code's claimed features. It's an Open Source project, so I assume there's no commercial reason to keep those test cases hidden. You mean these test cases? http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/... Given that, why are there no *LayoutPanels in Showcase? Fixed:http://code.google.com/p/google-web-toolkit/source/detail?r=8766 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2Bunsubs cr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.-Hidequoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
I think we often times forget too that folks are producing these products for us for free. One can always pay for GWT EXT if they like. On Sep 28, 12:38 pm, Brett Thomas brettptho...@gmail.com wrote: Not to mention none of those three things have to do with API Design... On Tue, Sep 28, 2010 at 12:01 PM, Thomas Broyer t.bro...@gmail.com wrote: On Sep 28, 4:29 pm, Greg Dougherty dougherty.greg...@mayo.edu wrote: Well, look at the JavaDoc for extended by com.google.gwt.dom.client.Style.Unit (AKA Style.Unit). I don't think it's possible to write worse Documentation than that, other than perhaps writing something that is actively and consistently wrong. Which doc are you talking about? the CSS length units part? (what more should it say? if you don't know what a CSS length unit is, you'd better stop doing web dev; or start learning CSS) the values and valueOf part? (they're not in the code, they come with the enum type, just like extends java.lang.EnumStyle.Unit) I assume people actually test code before it gets added to the project. I assume those text cases are a pretty through workout of all the code's claimed features. It's an Open Source project, so I assume there's no commercial reason to keep those test cases hidden. You mean these test cases? http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/... Given that, why are there no *LayoutPanels in Showcase? Fixed:http://code.google.com/p/google-web-toolkit/source/detail?r=8766 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.- Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
GWT may not have the most perfect API design, but saying GXT is a design to implement is laughable at best. GXT has just barely enough good things to make it worth using. BARELY. I keep their crappy library segregated behind interfaces and wrap all their even types waiting for the day I can rip that giant pile of crap out of my project. Tell me without going to the docs or drilling into their source what events a GXT button can handle. You can't by just looking at their API. You want to extend some of their controls, you're screwed because they, for not reason I'm able to discern, have tons of private variables with no getter/setter. If you want slow crappy code where you're constantly forced to go to the documentation then use GXT. If you want to extend one of their classes you could easily be copy/ pasting a ton of their code/heirarchy in order to get some minimal functionality included. On Sep 29, 9:06 am, markM mark.a.mccon...@pfizer.com wrote: I think we often times forget too that folks are producing these products for us for free. One can always pay for GWT EXT if they like. On Sep 28, 12:38 pm, Brett Thomas brettptho...@gmail.com wrote: Not to mention none of those three things have to do with API Design... On Tue, Sep 28, 2010 at 12:01 PM, Thomas Broyer t.bro...@gmail.com wrote: On Sep 28, 4:29 pm, Greg Dougherty dougherty.greg...@mayo.edu wrote: Well, look at the JavaDoc for extended by com.google.gwt.dom.client.Style.Unit (AKA Style.Unit). I don't think it's possible to write worse Documentation than that, other than perhaps writing something that is actively and consistently wrong. Which doc are you talking about? the CSS length units part? (what more should it say? if you don't know what a CSS length unit is, you'd better stop doing web dev; or start learning CSS) the values and valueOf part? (they're not in the code, they come with the enum type, just like extends java.lang.EnumStyle.Unit) I assume people actually test code before it gets added to the project. I assume those text cases are a pretty through workout of all the code's claimed features. It's an Open Source project, so I assume there's no commercial reason to keep those test cases hidden. You mean these test cases? http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/... Given that, why are there no *LayoutPanels in Showcase? Fixed:http://code.google.com/p/google-web-toolkit/source/detail?r=8766 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2Bunsubs cr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.-Hide quoted text - - Show quoted text - -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
Well, look at the JavaDoc for extended by com.google.gwt.dom.client.Style.Unit (AKA Style.Unit). I don't think it's possible to write worse Documentation than that, other than perhaps writing something that is actively and consistently wrong. My general experience with reading the GWT JavaDoc is to ask why did this person even bother? Presumable, anyone working on an Open Source project is doing it because they want to create code that will be USED. Which leaves me scratching my head wondering why they then produce such crappy examples that you have to come to the discussion group in order to figure out how to actually use the code. I assume people actually test code before it gets added to the project. I assume those text cases are a pretty through workout of all the code's claimed features. It's an Open Source project, so I assume there's no commercial reason to keep those test cases hidden. Given that, why are there no *LayoutPanels in Showcase? Why does not the GWT code tree have complete test implementations of every single panel, testing out all their features (and, incidentally, letting the rest of us see the programmer's idea of the best way to use those features)? Greg On Sep 27, 9:38 am, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: do you have some interesting showcase? :) On Mon, Sep 27, 2010 at 4:33 PM, dmen dmenou...@gmail.com wrote: Have been working with datepicker.. This must be the nth time I think gosh your component model and API are poorly designed! The compiler is great sure, but *please* take a look at projects like Ext GWT of how things should be done the-right-way before you introduce APIs the- clumsy-way that will be around forever. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
On Sep 28, 4:29 pm, Greg Dougherty dougherty.greg...@mayo.edu wrote: Well, look at the JavaDoc for extended by com.google.gwt.dom.client.Style.Unit (AKA Style.Unit). I don't think it's possible to write worse Documentation than that, other than perhaps writing something that is actively and consistently wrong. Which doc are you talking about? the CSS length units part? (what more should it say? if you don't know what a CSS length unit is, you'd better stop doing web dev; or start learning CSS) the values and valueOf part? (they're not in the code, they come with the enum type, just like extends java.lang.EnumStyle.Unit) I assume people actually test code before it gets added to the project. I assume those text cases are a pretty through workout of all the code's claimed features. It's an Open Source project, so I assume there's no commercial reason to keep those test cases hidden. You mean these test cases? http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/test/com/google/gwt/ Given that, why are there no *LayoutPanels in Showcase? Fixed: http://code.google.com/p/google-web-toolkit/source/detail?r=8766 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
Not to mention none of those three things have to do with API Design... On Tue, Sep 28, 2010 at 12:01 PM, Thomas Broyer t.bro...@gmail.com wrote: On Sep 28, 4:29 pm, Greg Dougherty dougherty.greg...@mayo.edu wrote: Well, look at the JavaDoc for extended by com.google.gwt.dom.client.Style.Unit (AKA Style.Unit). I don't think it's possible to write worse Documentation than that, other than perhaps writing something that is actively and consistently wrong. Which doc are you talking about? the CSS length units part? (what more should it say? if you don't know what a CSS length unit is, you'd better stop doing web dev; or start learning CSS) the values and valueOf part? (they're not in the code, they come with the enum type, just like extends java.lang.EnumStyle.Unit) I assume people actually test code before it gets added to the project. I assume those text cases are a pretty through workout of all the code's claimed features. It's an Open Source project, so I assume there's no commercial reason to keep those test cases hidden. You mean these test cases? http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/test/com/google/gwt/ Given that, why are there no *LayoutPanels in Showcase? Fixed: http://code.google.com/p/google-web-toolkit/source/detail?r=8766 -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
API design rant!
Have been working with datepicker.. This must be the nth time I think gosh your component model and API are poorly designed! The compiler is great sure, but *please* take a look at projects like Ext GWT of how things should be done the-right-way before you introduce APIs the- clumsy-way that will be around forever. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
do you have some interesting showcase? :) On Mon, Sep 27, 2010 at 4:33 PM, dmen dmenou...@gmail.com wrote: Have been working with datepicker.. This must be the nth time I think gosh your component model and API are poorly designed! The compiler is great sure, but *please* take a look at projects like Ext GWT of how things should be done the-right-way before you introduce APIs the- clumsy-way that will be around forever. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
Don't have the time to back my claims now; hence I said rant. I intend to write a lengthy blog post about this though. Just for the datepicker I 'll say that GWT has a separate package counting 10 artifacts compared to just 2 GXT artifacts that are superior in so many ways. On Sep 27, 5:38 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: do you have some interesting showcase? :) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
ok, i was only curious On Mon, Sep 27, 2010 at 5:01 PM, dmen dmenou...@gmail.com wrote: Don't have the time to back my claims now; hence I said rant. I intend to write a lengthy blog post about this though. Just for the datepicker I 'll say that GWT has a separate package counting 10 artifacts compared to just 2 GXT artifacts that are superior in so many ways. On Sep 27, 5:38 pm, Jaroslav Záruba jaroslav.zar...@gmail.com wrote: do you have some interesting showcase? :) -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
Don't get me wrong however. I am thankful for the whole GWT contribution (free and open source). Just felt ranting a little. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: API design rant!
I'm in no relationship to GWT-team. And I'm quite sure no one would take your rant like you don't appreciate the benefits GWT brings. On Mon, Sep 27, 2010 at 5:09 PM, dmen dmenou...@gmail.com wrote: Don't get me wrong however. I am thankful for the whole GWT contribution (free and open source). Just felt ranting a little. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
