Hi Janis: This is my report about MFlow: MFlow is an innovative, Web framework of the kind of other functional, stateful frameworks like WASH(†) , Seaside Ocsigen or Racket. But MFlow does not use continuation passing, but a backtracking monad that carries out the synchronization of browser request and server process execution state. This monad is on top of another "Workflow" monad that add effects of logging and recovery of process/session state. Both are managed by an application server that dispatch each request to the appropriate server process. In case of timeout, the process is restarted using the state recovering mechanism. The logs generated are very small, so MFlow solves the problems of fat serializaitions associated with stateful frameworks. Like the continuation-based frameworks. MFlow invert back the inversion of control, so, cotrary to MVC frameworks, programming multipage web application is simple and natural. At the same time MFlow is RESTful compliant. Not only the URL use the REST style, but also any GET page in the stateful flow can be pointed to with a REST URL. That is unique for an stateful WF. Additionally, besides, applicative formlets it also implement monadic formlets by means of a page monad, that permits to dynamically change the page content and input fields depending on the user input. That is called "page flows". Independent widgets can have its own flow within a page. HTML layout and text content can be added and modified later at runtime using a wysiwyg tool, so there may be a complete separation of layout and logic if wished. Other features are widget autorefreshing in the page via implicit Ajax, level-2 widgets (widgets that contain widgets), integration with Persistent, integration of AWS. JQuery integration, WAI integration. blaze-html integration. push and complete execution traces for errors (thanks to the backtracking monad). MFlow has facilities for single page developments, that would need a lot of client side javascript has been packaged as composable haskell elements that uses ajax internally to create dynamic interfaces that are type safe. It may be considered the continuation of the great WASH framework. More information: There is a site, made using MFlow which includes demos at: http://mflowdemo.herokuapp.com 2013/10/6 Janis Voigtlaender <jv@informatik.uni-bonn.de>

[Transition in editorship of HCAR in progress!]

Dear all,

We would like to collect contributions for the 25th edition of the

==============================**==============================**==== Haskell Communities & Activities Report

http://www.haskell.org/**haskellwiki/Haskell_**Communities_and_Activities_ **Report<http://www.haskell.org/haskellwiki/Haskell_Communities_and_Activities_Report>

Submission deadline: 1 Nov 2013

(please send your contributions to hcar at haskell.org, in plain text or LaTeX format) ==============================**==============================**====

This is the short story:

* If you are working on any project that is in some way related to Haskell, please write a short entry and submit it. Even if the project is very small or unfinished or you think it is not important enough --- please reconsider and submit an entry anyway!

* If you are interested in an existing project related to Haskell that has not previously been mentioned in the HCAR, please tell us, so that we can contact the project leaders and ask them to submit an entry.

* Feel free to pass on this call for contributions to others that might be interested.

More detailed information:

The Haskell Communities & Activities Report is a bi-annual overview of the state of Haskell as well as Haskell-related projects over the last, and possibly the upcoming six months. If you have only recently been exposed to Haskell, it might be a good idea to browse the previous edition --- you will find interesting projects described as well as several starting points and links that may provide answers to many questions.

Contributions will be collected until the submission deadline. They will then be compiled into a coherent report that is published online as soon as it is ready. As always, this is a great opportunity to update your webpages, make new releases, announce or even start new projects, or to talk about developments you want every Haskeller to know about!

Looking forward to your contributions,

Mihai Maruseac and Janis Voigtlaender (for this edition)

FAQ:

Q: What format should I write in?

A: The required format is a LaTeX source file, adhering to the template that is available at:

http://haskell.org/**communities/11-2013/template.**tex<http://haskell.org/communities/11-2013/template.tex>

There is also a LaTeX style file at

http://haskell.org/**communities/11-2013/hcar.sty<http://haskell.org/communities/11-2013/hcar.sty>

that you can use to preview your entry. If you do not know LaTeX, then use plain text. If you modify an old entry that you have written for an earlier edition of the report, you should soon receive your old entry as a template (provided we have your valid email address). Please modify that template, rather than using your own version of the old entry as a template.

Q: Can I include Haskell code?

A: Yes. Please use lhs2tex syntax (http://www.andres-loeh.de/**lhs2tex/<http://www.andres-loeh.de/lhs2tex/> ). The report is compiled in mode polycode.fmt.

Q: Can I include images?

A: Yes, you are even encouraged to do so. Please use .jpg format, then.

Q: Should I send files in .zip archives or similar?

A: No, plain file attachements are the way.

Q: How much should I write?

A: Authors are asked to limit entries to about one column of text. A general introduction is helpful. Apart from that, you should focus on recent or upcoming developments. Pointers to online content can be given for more comprehensive or "historic" overviews of a project. Images do not count towards the length limit, so you may want to use this opportunity to pep up entries. There is no minimum length of an entry! The report aims for being as complete as possible, so please consider writing an entry, even if it is only a few lines long.

Q: Which topics are relevant?

A: All topics which are related to Haskell in some way are relevant. We usually had reports from users of Haskell (private, academic, or commercial), from authors or contributors to projects related to Haskell, from people working on the Haskell language, libraries, on language extensions or variants. We also like reports about distributions of Haskell software, Haskell infrastructure, books and tutorials on Haskell. Reports on past and upcoming events related to Haskell are also relevant. Finally, there might be new topics we do not even think about. As a rule of thumb: if in doubt, then it probably is relevant and has a place in the HCAR. You can also simply ask us.

Q: Is unfinished work relevant? Are ideas for projects relevant?

A: Yes! You can use the HCAR to talk about projects you are currently working on. You can use it to look for other developers that might help you.

Q: If I do not update my entry, but want to keep it in the report, what should I do?

A: Tell us that there are no changes. The old entry will typically be reused in this case, but it might be dropped if it is older than a year, to give more room and more attention to projects that change a lot. Do not resend complete entries if you have not changed them.

Q: Will I get confirmation if I send an entry? How do I know whether my email has even reached its destination, and not ended up in a spam folder?

A: Prior to publication of the final report, we will send a draft to all contributors, for possible corrections. So if you do not hear from us within two weeks after the deadline, it is safer to send another mail and check whether your first one was received.

______________________________**_________________ Haskell mailing list Haskell@haskell.org http://www.haskell.org/**mailman/listinfo/haskell<http://www.haskell.org/mailman/listinfo/haskell>

-- Alberto.