Poe

INTRODUCTION
For now Poe is basically nothing more than a thought in the wind, so this will be more like information on what may come in the future. Poe is going to be an entire toolkit for developing stuff. What kind of stuff? Well... for now we are goint to be using it to develop stuff in Perl. In the future, however, I want it to be able to not only develop stuff in lots of other popular languages, but also to intermix these languages on the level of individual functions. But that is quite a ways off...

CURRENT POE STATUS
Currently Poe in its entirety consists of the Poe Browser, which I am currently hashing out. It is still very much in the design phase. I am still collecting my thoughts for what kind of features it will have.

POE PROJECTS
- Poe Browser
  * Already started
  * Enable a programmer to have an understanding of the heiarchy of the project at all times
  * Use multiple languages so the programmer can take their pick
  * Use multiple development and deployment platforms, and encourage portability

- Poe GUI wrappers
  * For each language create a common wrapper around many GUI kits
  * For example, create a single perl or C interface for Gtk, Tk, Motif, V, Win32, MacOS, etc.

- GUI Designer
  * Use an optionaly more integrated approach. Don't just provide a designer, provide an IDE.
  * Be able use a variety of languages and toolkits, using the Poe Browser and Poe GUI wrapper
  * Steal ideas from other GUI makers, like Glade or VB

- Poe Perl Parser
  * Parse perl, in perl
  * From raw perl produce a parse tree
  * Provide methods to traverse the resulting tree
  * Maybe not in the Poe heiarchy... Parse::Perl perhaps?