Recent changes to news

CodeCon Details

Mark Lentczner — Thu, 03 Feb 2005 19:29:10 -0000

CodeCon has released the schedule for the conference. Wheat will be demo'd Sunday:
http://www.codecon.org/2005/schedule0213.html

Jim, Kragen and I have been working furiously to get the system ready in time for the demo. Nothing like a deadline! There is a new Wheat API for the templating system, some reg-ex support, new work on Farm (the development environment), and improvements in file system layout.

After the conference, we'll have a the conference demo release tar-ball up on SourceForge, and hopefully some transcripts of how to run the demo available.

I'm excited!

Winter Update

Mark Lentczner — Thu, 03 Feb 2005 19:23:47 -0000

It has been way too long since an update about Wheat. For now, I just want to alert you all to two project events:

1) Wheat has been accepted as one of the projects to be demo'd at CodeCon 2005. This is a three day open source project conference held in San Francisco. The web site is:
http://www.codecon.org/2005/index.html
However, they don't seem to have much info up there yet...

2) The wonderful people at CommerceNet's zLab have taken an interest in Wheat and decided to "learn by doing". So, for a whole week in December, their Kragen Sitaker and I pair programmed on and in Wheat. We learned lots, coded lots, and identified what needs more work.

Summer Progress

Mark Lentczner — Tue, 17 Aug 2004 21:38:13 -0000

Summer has a bit slow, but progress has been made nonetheless. Several areas of infrastructure got worked on:

* The server threading architecture has been extensively rewritten as a pre-launched-thread server with a pool of worker threads. It is now thread-safe and signal-safe.

* Persistence was improved in that now only modified object mounts are persisted. XMLMedia supports checkpointed storage.

* Together, these changes make using the server for live data feasible.
(See http://www.wheatfarm.org/wiki/StoryCardsForR1PartThree\)

Unit tests for the blog are being moved into Wheat script. A first shot at a unit test framework in Wheat has been developed.

Next in store is work on a larger, blog-like application specifically for taking notes during conferences. Stay tuned...

Blog in Wheat

Mark Lentczner — Thu, 27 May 2004 22:56:44 -0000

The simple blog application for Wheat is now written and running entirely in the native Wheat language. In just a month we have come from being able to execute a simple expression to running a whole application (albeit a simple one). The Wheat code for the blog application can be viewed on-line.

See blog.ws:
http://cvs.sourceforge.net/viewcvs.py/wheat/r1/app/blog.ws?view=markup

If you check out the latest source from the CVS repository, build and run it, you can then point your browser at the running Wheat server and see the blog application running. It is known to build and run under various unix flavors, Mac OS X, and Windows with cygwin.

See CVS repository on SourceForge:
http://sourceforge.net/projects/wheat/

I'm catching my breath after this last push, and thinking about what to do next. There are several enticing things, but we can't do it all at once. Please feel free to join the discussion.

See the Wiki StoriesForR1:
http://www.wheatfarm.org/wiki/StoriesForR1

3 + 4 = 7!

Mark Lentczner — Mon, 19 Apr 2004 21:52:26 -0000

Wheat executed its first compiled method yesterday! The method was:
doit(): { return 3 + 4; }
The result was 7. While this doesn't seem like much, it actually tests a surprising amount of the language machinery: Wheat now has a working lexer, parser, compiler, method builder (assembler) and virtual machine.

Two months ago, we were working on the Blog application. By the beginning of March we had a skeletal Blog with an RSS feed running. However, this was coded entirely in the C++ syntax for Wheat. We decided that not having the Wheat native text syntax running was an impediment to people understanding and trying out the project. The language and compiler were put ahead of completing the Blog.

Now that we have the native Wheat test syntax running, we can return to writing the Blog application. However, this time we can write it in Wheat's native syntax. This will make it much more clear how Wheat makes writing such applications very easy.

I will also be doing some work to get a rudimentary Wheat hosted development environment running. This will enable you to run the Wheat server, browse to a page on the server, type code and have it compiled and run. Tinkering with live code is a lot more fun that just reading about it.

As always your interest, suggestions, comments and contributions are always welcome!

- Mark & the Wheat team.

Relevant Wiki pages:

Wheat's Native Text Syntax
http://www.wheatfarm.org/wiki/TextSyntax

The Compiler Implementation
http://www.wheatfarm.org/wiki/CompilerImplementation

Wheat Implementation Direction
http://www.wheatfarm.org/wiki/ImplementationMap

Rounded the first curve....

Mark Lentczner — Fri, 20 Feb 2004 07:21:45 -0000

...And we can see our first application: A Blog. We now have enough machinery to render and serve real web pages with content drawn from Wheat objects. We hope to have a full running Blog application within a month.

Some amusing code stats: Over 20,000 lines of code in 97 files (not counting the included libraries expat or ptypes). About 25% of that is unit tests. There are 72 public classes in header files and another 53 in implementation files.

The code currently builds and runs on Mac OS X, Linux and FreeBSD. See the SourceForge site for anonymous access to the CVS repository.

Lastly, see the Wiki for current discussions and to monitor the progress toward the Blog application.

Hopefully, by the next e-mail I send, we'll be Blogging in Wheat!

- Mark

Wheat source is now available...

Mark Lentczner — Fri, 09 Jan 2004 23:01:16 -0000

SourceForge seems to have cured the problems with the anonymous CVS access. The anonymous CVS server now has up-to-date copies of the Wheat source. A good build that passes all its unit tests is at the tag markl-gravity-20040102a. If you're feeling adventurous, try the head revision. On Linux or MacOSX you should be able to do this in a shell:

mkdir someplace-for-wheat-development
cd someplace-for-wheat-development
cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/wheat login
# just hit return when asked for a password
cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/wheat \ co -r markl-gravity-20040102a r1
cd r1
make
make # there is a bug, you'll have to make twice the very first time!
./bin/wheat-r1 -t root/config.xml
# runs 69 unit tests, all should pass
./bin/wheat-r1 root/config-web-text.xml
# runs the Wheat server
# Point your browser at http://localhost:8100/

Please see the README.txt file in the project directory. Mac users can also use XCode to build - see the README.txt file for details.

Remember: This is still VERY early work on Wheat, and it it doesn't do much visibly. But, lots of the infrastructure is running, and verified by the unit tests.

For more information about CVS for the project, see:
http://sourceforge.net/cvs/?group_id=94386

- Mark

Mark Lentczner
markl@wheatfarm.org
http://www.wheatfarm.org/

A month's worth of development

Mark Lentczner — Mon, 05 Jan 2004 16:44:06 -0000

It has been a while since the last Wheat update. Quite a bit has happened:

Jim Kingdon and I have been working on the rendering module: This lets objects control their mapping to the web server URL space and control their own rendering via XML templates. The code is close, and is capable of rendering some very simple blog entries!

Other things that got coded in the last month:
- XML Media is now working (Wheat objects stored in XML documents)
- Debugging support (displaying object information in gdb)
- Build under Linux
- Many virtual machine refinements (semantics and implementation of inheritance, stacks, message lookup and sending, primitive installation and execution)
- An initial object library (very rudimentary)

We are working toward getting a Blog and a Wiki running in Wheat. I hope to have something running by end of February.

The project has moved to using SourceForge's CVS servers as the main source repository. Alas, SourceForge's anonymous CVS servers don't seem to be keeping up-to-date with the developer CVS servers. As soon as they fix this, I'll post details on how you can download and build Wheat for yourself.

- Mark

XML Work & Input Needed

Mark Lentczner — Mon, 24 Nov 2003 23:14:23 -0000

This week saw lots of work on the XML media implementation. The entire storage system, which is normally the host file system, has been abstracted so that the XML document tree can alternately be stored in memory. This makes unit testing of the XML media very easy: Just mount it on memory storage instead of file storage and then do string compares to make sure it is writing correctly.

The XML writer is coming along. It currently can write a Wheat object as a single XML document. Next is supporting objects that persist as collections of XML documents (needed for persisting large object trees). I expect to complete this by the end of this week. When done, Wheat will be persisting all its data.

I need some input on two design decisions. Both conundrems can be found on the Wiki:

XML Media Document Options -
http://www.wheatfarm.org/wiki/XMLMediaDocumentOptions

Project Terminology -
http://www.wheatfarm.org/wiki/ProjectTerminology

Please look them over and add your comments and opinions to the Wiki.

Have a good Thanksgiving...

- Mark

Site updates: Notes from Hacker's Talk

Mark Lentczner — Mon, 17 Nov 2003 20:19:36 -0000

The web site ( http://www.wheatfarm.org/ ) has been overhauled. The site now features a full set of contact URLs so you should be able to find everything. I've also put the latest news item on the page.

A major addition are my notes for my talk at Hackers. Now there are some words to go with those images...

Lastly, I realize that the XHTML 1.0 and CSS 1 compliant layout doesn't work perfectly in all browsers (which seem notoriously non-compliant... especially IE...). I think it should all be readable in most browsers. If not, please drop me a line.

- Mark