Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TeeJay (2309)

TeeJay
  (email not shown publicly)
http://www.aarontrevena.co.uk/

Working in Truro
Graduate with BSc (Hons) in Computer Systems and Networks
pm : london.pm, bath.pm, devoncornwall.pm
lug : Devon & Cornwall LUG
CPAN : TEEJAY [cpan.org]
irc : TeeJay
skype : hashbangperl
livejournal : hashbangperl [livejournal.com]
flickr :hashbangperl [flickr.com]

Journal of TeeJay (2309)

Monday June 23, 2003
05:25 PM

back on autodia

[ #13021 ]
I am back onto autodia development again. Hopefully I can get an hour or two in tonight.

The next release of 1.7 should add some cool new stuff

  • An experimental Python handler for those who prefer white-space handicapped scripting
  • Patches to C++, PHP and Perl handlers to make them work a bit better
  • Read in ArgoUML (hopefully)
  • Read in Torque database schema xml
  • Merge in some tedia2sql features

I am now unsure if I should start merging code and SQL output into autodia.

I think it would be better to keep autodia to a specific purpose - creating documentation and diagrams of code or database schema's and not to add code / sql / database creation into it.

This means starting a new CASE type project that generated perl code (and related stuff like SQL Phrase books, perldoc, tests, sql, databases, rc files, etc) from Diagrams in Dia and ArgoUML.

What on earth to call it ?

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.