Why do I assume that Web Objects provides only a fixed and limited set of components to work with? Just my knowledge of most other web frameworks.
I read a book on JSF, and most of it was about referencing a fixed and limited set of components from within my enhanced-HTML file. The chapter on creating new components looked very complicated to me -- it appeared that one had to understand the internals of JFS to build a new component. I read a book on ASP.NET -- again, most of the book was about how to write tags to instantiate and configure a pre-built component into a web page; again, the chapter(s) on creating and using new components (even merely by subclassing or assembling groups of interacting standard componets) looked very difficult. Even if the component creation part was not difficult, one still had to configure it into the Visual Studio tool to access it -- unless one wants to hack into the huge ugly enhanced-HTML tag file Visual Studio generates (which was most users never look at). I read a book on JSP, and the chapters on creating custom tags made the process look like a big production. First of all, the methodology for programming a tag seemed peculiar, with all the special values I had to return (use the body, don't use the body, ...), and the fact that the Java code had to create and return properly-escaped strings of HTML text. Then I then had to insert an entry into an XML tag library descriptor file, and I had to add an XML descriptor into my web page to tell it to use that tag library. Let me just say that I was already a SCJP, yet the process of creating custom tags was far from intuitive to me. If I embed several JSF, JSP or ASP.NET tags in an HTML page and then discover that I need something similar on many other pages, there is no easy way to refactor my application to abstract that portion of my page into a new component. I'm not talking about mere "include" files; I'm talking about components with a choice of possible contructors taking various types of parameters. Given how horrendously complex this seemingly mundane task is in most web frameworks, it would be a pleasant surprise indeed to learn that Web Objects makes it easy. The reason the task is easy in Wicket is that one doesn't build web pages by nesting custom framework-oriented tags in a tage file. Simple attributes in plain HTML tells me where in the HTML file a component should be rendered, but everything else about that component's definition, configuration and use is done in Java code. So building and using custom web display components is no more difficult in principle than subclassing and using classes from the standard J2SE packages. Is everything in WebObjects also done in Java code, or do you build web pages by embedding special WebObject tags and subtags in your HTML file just as in most other frameworks? What is Web Object's process for abstracting part of a page into a new component with its own API? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anders Peterson Sent: Wednesday, August 30, 2006 2:21 AM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] WebObjects open source? Frank Silbermann wrote: > What facility does Web Objects provide that lets you avoid having to > re-set those properties fifty times? ... and however you choose to construct your "web display object" it is (naturally) also a component that can be used as a building block for other "web display objects". > (Isn't the inconvenience of adding slightly-customized variations of > components to the toolset the reason most Swing GUI programmers end up > building their GUI in code instead of using some IDE's graphical > GUI-painter?) Most people just don't want to change their way of doing things (and some graphical GUI-painters are not very good). You seem to think there is only a fixed and limited set of components to work with - why assume something like that? /Anders > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Anders > Peterson > Sent: Tuesday, August 29, 2006 12:51 PM > To: wicket-user@lists.sourceforge.net > Subject: Re: [Wicket-user] WebObjects open source? > > Not sure what to say... it makes me productive... > > It's not really fair to compare Wicket and WebObjects (WO). WO is a > whole package of frameworks and tools that function well together (but > can be used independently). Wicket needs team mates to replace WO > entirely. > > With Wicket any html and java editors will do just fine. This is > generally a good thing (I think) but it's also a restriction. With > WebObjects the tools are part of what makes the package great: > > Start up the WOBuilder tool, create a WODisplayGroup instance and > start > (visually) combining WOComponents and binding them to data. It's fast > and intuitive... > > /Anders > > http://developer.apple.com/documentation/WebObjects/Conceptual/WO53_WO > Bu > ilderGuide/ > > http://developer.apple.com/documentation/webobjects/Reference/API/com/ > we bobjects/appserver/WODisplayGroup.html > http://developer.apple.com/documentation/Webobjects/Reference/API/com/ > we > bobjects/appserver/WOComponent.html > > Eelco Hillenius wrote: >> :) It's one of my favorite parts of Wicket, so sure. >> >> What about the strong points of WebObjects, what are the things you >> really like about that? >> >> Eelco >> >> On 8/29/06, Anders Peterson <[EMAIL PROTECTED]> wrote: >>> Sure, if it has to be just like Wicket to compete; you win. ;-) ------------------------------------------------------------------------ - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
