I find it hard to believe that this point even has to be made, but there is a difference between designing something and implementing a design. There is also a difference between UI look and UI behavior. By replicating the 280 Slides look (by copying its existing design and images), the best you could do is prove that GWT makes it easy to implement a design, but I do not believe that even this was done in the demo you made.
1. I'm not sure what exactly is impressive about this demo, you have a couple buttons which pop up a window that has dummy content in it, and then expect people to think that it proves that making something that looks and behaves like 280 Slides is easy. For starters, this is the least impressive portion of 280 Slides. I don't for example see a slide navigator which shows a tiny version of the working area, and I also don't see a working area that has vector properties that works in all browsers. These are the components which would be hardest to build without Cappuccino in my opinion. I'm not sure even the toolbar works like the one in 280 Slides. For example, when you make the window too small does it auto place the items that aren't visible into a menu on the right based on their priority of importance? If your point was simply that you can make buttons with custom images in GWT, then I guess you've succeeded.
2. Beyond this, designing itself is also quite difficult, which I hope is not something we have to argue about, since to say otherwise would be to invalidate the designing profession as a whole. One thing we are trying to do with Cappuccino is provide a good set of base artwork and a HIG that will make this easier for people who can't afford a real designer. Large portions of this work will of course be usable outside of Cappuccino since we are making them open source, but others will be much easier as they will be built into Cappuccino.
1. I'm not sure what exactly is impressive about this demo, you have a couple buttons which pop up a window that has dummy content in it, and then expect people to think that it proves that making something that looks and behaves like 280 Slides is easy. For starters, this is the least impressive portion of 280 Slides. I don't for example see a slide navigator which shows a tiny version of the working area, and I also don't see a working area that has vector properties that works in all browsers. These are the components which would be hardest to build without Cappuccino in my opinion. I'm not sure even the toolbar works like the one in 280 Slides. For example, when you make the window too small does it auto place the items that aren't visible into a menu on the right based on their priority of importance? If your point was simply that you can make buttons with custom images in GWT, then I guess you've succeeded.
2. Beyond this, designing itself is also quite difficult, which I hope is not something we have to argue about, since to say otherwise would be to invalidate the designing profession as a whole. One thing we are trying to do with Cappuccino is provide a good set of base artwork and a HIG that will make this easier for people who can't afford a real designer. Large portions of this work will of course be usable outside of Cappuccino since we are making them open source, but others will be much easier as they will be built into Cappuccino.