Well, I have updated some widget requests on the Wiki. My plan is to spend a little time this weekend and simply implement one of those widgets then go back and document it :) It can't hurt and it will most probably expose any issues which are difficult for the external developer to grasp (Just having a quick look tells me that the paint() function, and it's options could do with a bit of a document...)
Roja Koen Deforche wrote: > Hey Anthony, > > 2008/11/5 Anthony Roger Buck <[EMAIL PROTECTED]>: > >> Interestingly i just spent a few hours looking around and have come across >> "http://www.qooxdoo.org"; for a direct replacement for Ext it seems ideal >> (ignoring your reply...) High quality, rich and fast with a huge selection >> of widgets & LGPL (duel with Eclipse Public!). >> > > You are right, I hadn't follows their progress, but indeed, their demo > material looks nice. > > >> Yet again I love every idea regarding minimizing both communication >> (onDemand) and JS exposure but providing the vast array of widgets which >> these guys can will surely take time? Also providing widgets which are >> "default attractive" must also be taken into account (no offense intended >> but look at the difference between the calendars on wt & ext)... I know that >> it's simply a matter of using CSS to improve this but in the world we live >> in where rapid development is important it is rather nice to have an >> attractive "look" straight out of the box. >> > > Hehe. We are very well aware of the fact that we are not yet providing > the polished looks that most others have... > > I always think I can spend my time better programming (as I am not > very much of a designer/CSS person), but I do not think it should be a > too big effort... Which will become more of a priority as other things > start to settle down (in the functional department). > > And we are also aware that it will take quite some time. But I do not > think the web is going to go away soon either. :-) > > If anything happens, it will be HTML 5 which hopefully will bring many > basic widgets for free, reducing the added value of client-side > JavaScript libraries, and increasing the value of a RPC-free > server-side framework! > > And, I also hope that with extra man power things will start to speed > up (next year). > > >> Maybe a good tutorial about how to develop widgets would help? >> > > I certainly would welcome help, but there really isn't much magic to > the built-in widgets ? > > There is certainly some experience that I have developed that I could > share, and here and there we cut some corners, using internal API or > expanding the basic infrastructure, but other than that, it is pretty > much simply using Wt's public API. > > But I think it is perhaps a good idea -- I'll discuss with Wim and > some other people from the mailinglist? > > Regards, > koen > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
