I'm changing the conf file into an XML document, and adding parsing objects to the next release.
--== 0.0.9 ==--
-- the DB_PASS is hidden when you set debug to TRUE so there's no over the shoulder password snatching.
-- removed bunk link from index.php since there's a parse error in the GenScript::createJSDB widget (both commented out).
-- updated GenObject::toString($use_html). Can return a text or html string.
-- started updating some of the comments for use with some of the PHP documentation systems. Still needs work.
-- webgen/Makefile has been modified to use macros. It still needs to clean out the copied license, readme and data dirs. If anyone can help, \
let me know. (The makefile basically is there to help make releases and patches)
-- GenScript should now pick up your custom variables and write them out when you re-generate a prototype from the database. Get/set modificat\
ions still aren't copied yet, sorry.
I haven't heard back from people too much, but let me know what is working and not working -- or desired features of a prototyping system.
I'd like to move to a beta environment by next week, including having an admin area. ~v.s.
Since listPeople shows how plural tags work, it's kinda important and it's been missing since prolly 0.0.6. Sorry; I need to start testing the releases better.
Please let me know if anything but the javascript database doesn't work (known issue).
Now autoincludes the deployed templates created by GenScript so you don't have to. ~v.s.
Since the usr directory is not auto-included yet, you need to add an include for person.php when generated from GenScript in order to run demo_webapp.php
There is an error in Genscript's export to javascript function that causes prototyping to fail. This will be fixed in CVS, but a release will not be available until monday.
There was a problem with the tarball that has been resolved.
GenPage was using DOCUMENT_ROOT instead of SERVER_DOCUMENT_ROOT; also fixed some things in data directory so templating works with the 'Hello World' page; webgen release now includes the data directory. ~ v.s.
In the apps directory, demo_webapp now has the application logic that previously resided in modules/webgen.php. I think it will be more clear in a seperate application file; this is currently only available over CVS, and will be released in 0.0.3. ~ v.s.
The basic premise of WebGen is that developing for the web is difficult on contractors. Not because of technical issues, but because of communication issues. Many small businesses don't understand what they need or want at the outset, and sometimes contractors don't have the time to fully analyze their systems. WebGen is designed to be the ginsu knife of web developers -- allowing us to quickly generate application code, debug it, and transform it quickly to meet changing requirements -- all while giving designers the hooks they need to have the freedom to do what they do best.... read more
Added apps directory; gave GenConn more flexibility; modifications to GenPage to work with an open templating system that isn't tied to the 'templates' directory.
Added an apps directory to contain generic implementations of various tools. The first one uses GenScript to generate your classes, and is available in CVS.
db/GenScript.php can now generate class files from a database that db/GenFactory.php can populate.
Still needed to be done is the reverse; and eventually, a check that can synchronize the two. At any rate, GenScript can now make a prototyping a cinch!
To simplify release of new code, a diff/patch Makefile has been set up in /patch
... is now available via CVS. It is not very robust, but it does work!
An initial framework is finally starting to take shape.
GenFactory now recognizes local variables that begin with "gen_" as variables that exist in the database, so a message passing architecture is coming together.
I've also added a debugger that is initialized in the GenObject root so all objects have access to it. It can be turned on and off very easily, and even overridden so you can turn on one or two debugs in the local file you're working on.... read more
Check'em out. They will be changing rather constantly over the next couple of weeks.
Todo: Break out the components and run phpdoc on'em.
Also, use the webpage to supply examples.