I'd like to implement a user interface incorporating the new functions (currently in cvs), including
* generating a php class
* generating an html form
* generating the form catching script.
Eventually, classyphp (gah! The name!) will be able to take multiple CREATE TABLE statments, to create multiple classes. Makes me wonder - in what way will we utilize this tool (in order to create the user interface accordingly):
Do we want to generate _everything_, every single file, with the click of a button, or do we eventually want to choose what to generate (php classes, html forms).
I'm currently leaning towards choosing what to generate. Any thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In a similar app I had made for myself before, I had checkboxes to decide what output to get, in this case php class,html form etc.
The code for these was written to the screen in seperate textarea boxes so I could copy and paste them into my current work. I think this might be better than giving them a file to download and open.
This is useful for forms etc, but the class file might be a file to download.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree. I would imagine copy/paste is the way to go wholeheartedly. I constantly find myself generating a class file, adding a function, and for some reason need to re-generate the class again (due to a change in the database). Merging the original class with the extra function and the new class is a copy/paste job (unless you're using a fancy diff tool), so why not go copy/paste all the way from ClassyPHP?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd like to implement a user interface incorporating the new functions (currently in cvs), including
* generating a php class
* generating an html form
* generating the form catching script.
Eventually, classyphp (gah! The name!) will be able to take multiple CREATE TABLE statments, to create multiple classes. Makes me wonder - in what way will we utilize this tool (in order to create the user interface accordingly):
Do we want to generate _everything_, every single file, with the click of a button, or do we eventually want to choose what to generate (php classes, html forms).
I'm currently leaning towards choosing what to generate. Any thoughts?
In a similar app I had made for myself before, I had checkboxes to decide what output to get, in this case php class,html form etc.
The code for these was written to the screen in seperate textarea boxes so I could copy and paste them into my current work. I think this might be better than giving them a file to download and open.
This is useful for forms etc, but the class file might be a file to download.
I agree. I would imagine copy/paste is the way to go wholeheartedly. I constantly find myself generating a class file, adding a function, and for some reason need to re-generate the class again (due to a change in the database). Merging the original class with the extra function and the new class is a copy/paste job (unless you're using a fancy diff tool), so why not go copy/paste all the way from ClassyPHP?