Anjo, >> You people should be ashamed of yourself. We certainly welcome enhancements, fixes, or even only ideas, but you must be aware that all the work currently rests on a very small amount of people and they *will* simply stop when the amount of signal to noise progresses to the worse.
Then I'd like to see one of *you* coming forward and working 6 weeks full time to prevent people from needing to edit plists in TextEdit. << Well, a couple of hours ago I added my thoughts to Robert's blog. I'm sorry if you think I'm not appreciative of the work that has gone into WOnder,WOLips,etc. Only a couple of days ago when trying to solve a problem that is really only of an intermediate level of difficulty in WO, and the solution to which was not documented in any of the books on WO that I have nor in any of the Apple documentation, but a search through the history of the omni list pointed me towards a WOnder solution. It was beautifully simple using WOnder. So, please do not think that we do not appreciate what a fantastic resource WOnder is. But if I had had to learn WO in the last couple of years using Eclipse and not XCode I think I would have given up. If someone is a very experienced WO developer, and a very experienced Java developer, then I can imagine that Eclipse might offer them a better experience. If it turns out that XCode's support for WO development is going to worsen, then one could expect that people will make more of an effort to get over the differences in using Eclipse for WO development. Certainly if we want to see more people using WO in the future, the toolset needs to provide an easy ramp up, and the documentation needs to be illustrated with regard to the toolset. Quite frankly, if I have to resort to manually editing plist files in order to keep on using WO, I will - at least then my only dependency will be on knowing the structure of the files and on the relationships between them. That is not to say that those of us who do not use Eclipse are not deeply grateful for the work that you guys have done. I certainly am. Maybe in the future it will save me from having to resort to Vi for my WO development :-) Even though I'm not using WOLips, I will go and subscribe to the list so that at least I'm keeping up to date with the issues. We have yet to see what the future holds in light of the developments at WWDC this week. Maybe XCode is going to become an even better place to be than it has been for the last year or so. Is there a list of outstanding issues with regard to WO development on Eclipse? Maybe if the people who are not ready to jump to Eclipse could focus on helping solve those issue then they would be paving the way to their own adoption of Eclipse as their IDE (e.g. the reverse engineering of the dependency between WOBuilder and XCode being open - I just grabbed that one from a quick perusal of the archive). Bernard Devlin _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
