Haskell Libraries Wishlist
O.Chitil at kent.ac.uk
Wed Oct 13 10:41:34 EDT 2004
>>I'd just like to mention that last academic year I had a project student
>>building such a system. Although the result is nice (it provides even some of
>>the sophisticated features Simon mentions), I'm not happy enough with it to
>>use it. This is partially because of the limited Haskell knowledge the
>>student had, but mostly because the whole thing is based on WASH. From this
>>project I learned that WASH is a large and complex library; it automatically
>>pages); it has a number of problems, especially with preserving state; and it
>>is changing quickly. The last point is good in that a number of problems
>>disappeared within the year, but on the other hand the continously changing
>>API also requires you to change your WASH application all the time.
>Is the source for your app available? Is there a demo online?
There was an online demo, but with the end of the project this summer
the university deleted it.
If you are seriously interested I could send you source and the project
report. I just don't want to make it fully public, because there might
be copyright issues with the University of York.
>I agree that WASH is large and complex, but I have used it for a few things.
>yet tried to patch it.
>I've been using Andrew Cooke's Halipeto for my personal website, it's a nice
Halipeto only appeared in the middle of the project, and hence wasn't
by default. In WASH it mostly serves for checking input fields. For this
application there is not much need for checking input fields and the way
in which WASH indicates errors in input is in my opinion not very clear
More information about the Libraries