Chuck Esterbrook <ChuckEsterbrook@...> wrote:
>>I assume that 0.6 will:
>>* fix the console hanging and socket binding problems that
>>Jeff's been working on
>Those are either op sys or Python problems; not Webware. I'm not aware of
>any outstanding work in this area other than providing convenient options
>for discarding daemon output.
Those issues really surprise me, and it's tempting to think that it's related
to FreeBSD. From what I have heard in the past, I'd be too scared to run
anything threaded on some of the BSDs. ;-) Having said that, it would be good
to review the existing daemon startup/shutdown scripts.
>>* fix small misc bugs
I mentioned a problem with imp.find_module which defies explanation. I'll
definitely look into this more at the weekend, but it's something which only
needs fixing before the end of the beta series, if something does need fixing,
of course. (I'm fairly sure I didn't screw up with my PYTHONPATH or anything
>>*** making the switch to distutills (probably requires a
>>new package structure)
>Not high on my list. Compared to what other people are pining for (fixes,
>URL handling, etc) this is small.
>Also, from what I know of Python, distutils and that *.pth thing, we
>probably need to do little in terms of package structure. Webware
>components are Python packages to begin with, after all.
We just need someone who knows distutils to roll something up, I think.
However, there are some major benefits in making installation as easy, as
helpful and as comprehensive as possible. I had a look at SkunkWeb the other
day, and its installation is based on a configure script; personally, I
wouldn't recommend that over distutils - I have had some configure and autoconf
>I'm thinking of 2 distro's in the future:
>- Webware for Python: contains only what's in Webware CVS. What we do now.
>- Webware Deluxe: Contains the usual Webware plus hand-selected valuable
>packages like Cheetah, MySQLdb, etc. For the person who wants a complete
>web dev package out of the box (e.g., .tar) containing only stable,
>documented packages than can work together.
I think this is very important. Firstly, it provides something which should be
proven and obvious to "test against" should people have problems. Secondly,
anything which reduces the perceived number of components is likely to be more
appealing. Integrating systems can frequently be a nightmare.
>- The Install Guide could use more guidelines and advice about the
>distinctions between running WebKit for development vs. deployment. Again,
>the pay off is universal.
There were a few things in the documentation which need changing (apart from
version numbers) and I could surely provide some feedback there.
Tom Schwaller <tom.schwaller@...> wrote:
>That reminds that Webware still needs something like PHPNuke, PostNuke,
>Slashcode, Midgard,... to give people a point and click content
>mangement system they can deploy out of the box and contribute Modules for
>(Mail, Calender, Rating System, Syndication with other sites, Shop,
I think it's true to say that applications sell platforms to developers. At
least, I feel more enthusiastic about a platform if there's a nice
demonstration application which actually does something, as opposed to just a
README file and some classes.
It should even be possible for people to download Webware with one of these
applications and to be able to deploy it using the "best practices" concerned,
without spending days configuring them both, along with Apache or whichever Web
server is in use. Something that would really be cool would be an online
configurator which provides the necessary configuration files for you, but I'd
settle for helpful offline programs to do the same job, certainly. :-)
Of course, a lot of this is going to be contributed stuff, but it would be nice
to have "approved" contributed stuff.
Get your firstname@... email for FREE at http://Nameplanet.com/?su