Thanks for the kudos. But I was a little surprised that after all the work you recently put in, you would then immediately outline a roadmap that sounds like "how to evaporate Webware" at which point its hard to imagine using 1.0 for anything. I *wasn't* surprised when several unsubscribes followed your message. If sub 3.0 focuses on removing non-WebKit items and 3.0 gets rid of the app server, then what is left at the end of the road?
** Random feedback on your comments: Regarding plug-ins, AFAIK setuptools, distutils, etc. don't cover automatic discovery by an application server, augmenting app server admin pages, versioning, etc. which is where I was planning on going with Webware plug-ins. No one ever seemed to understand that and I never found the time to develop them further with more capabilities, code and docs. Oh, well. Regarding unicode, isn't that baked into Python strings in 3.0? Does anything have to "be done"? On .NET which is where I've been doing a lot of work in lately, Unicode is simply implicit and free. I agree with the 1.1 idea of removing support for old versions of Python. Regarding naming conventions, we discussed the following enhancement on this list a long time ago, but no one got around to implementing it. Here's a recap: Support you prefer to say obj.foo_bar() over WebKit's obj.fooBar()? We can provide that by enhancing WebKit.Object's __getattr__ to look up "fooBar" for any "foo_bar", enhance the __dict__ of the class where "fooBar" was located to now have an entry for "foo_bar" and return the value. This is only slow on the first fetch and just as fast as usual afterwards. Another idea was to make things like self.request() into properties so you can say self.request. You can avoid breaking existing code by simply adding a WebKit.Object.__call__ that returns self. Pretty neat, imo. ** General comments: Personally, I enjoy using WebKit and MiddleKit and I also make use of various tools in MiscUtils and WebUtils. The productivity there is still good so I've had zero incentive to move existing apps to other frameworks. I'm working on such a project this very week. I thank you for your efforts and stewardship! And for making a 1.0 branch for maintenance. I'm also interested in hearing what people on the list have to say, especially those that maintain existing apps. Also, very important, would be to ask the webware-discuss members what they would like to see in the future, whether they are maintaining apps, etc. ** Why I Faded Out Had I put more consistent effort into Webware through the years, including updating it with the times, then it might have become the premiere app server for the Python community. However, I became disillusioned with Python over the long run due to various problems including lack of performance, the GIL, lack of property syntax, etc. Consequently, I created the Cobra programming language which already has numerous advantages over Python. See http://cobra-language.com/docs/python/ Cobra is more fundamental to me and, compared to Webware, can be applied to a wide variety of projects (web, games, simulation, finances, AI, etc.). Therefore, I see it as a consistent, life long project for myself. In addition to moving towards Cobra 1.0, I'm also looking to make it multibackend starting with JVM support and following that with a cross VM library (VM = Virtual Machine as in .NET or JVM). It will then become interesting to ask if there should be a cross VM app server... a Webware for Cobra. -Chuck -- http://cobra-language.com/ ------------------------------------------------------------------------- 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=/ _______________________________________________ Webware-devel mailing list Webware-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-devel
