JZ, here again. I finally installed the new version locally and here are my thoughts:
(1) the many config files are a pain to work with, though it is nice that you only have to touch two of them. The files themselves could use some more inline documentation for beginner (and advanced) users. Since I'm not a coder I might take this on and leave the development for others.
(2) I'd like to see the return of the auto-drop down builder from the previous version. This time however, I'd really like it to be smarter and work like someone would want it to in a real web app. the insert screen should populate the drop down(s) from field(s) in lookup tables. The editing drop down should show the inserted value as the selected one, but also show the lookup values so that original value could be updated. You'd have to specify the lookup table in the builder config screen.
(3) I'd like to see the initial navigation screen made to be an include that is available on all the generated pages. I'd also like to see it look more like a nav bar (horizontal with buttons) or maybe even use form elements (drop downs that perform functions onChange).
More to follow. Thanks again for the project!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks a lot for the suggestions JZ.
1. THe main motivation for separating the constants files is for most projects, there are different teams/peoples working on them and thus need lock privileges on these files. So from my experience, I tried to separate the different entities in the kinds of things they focus on. Definitely, there need to be more inline documentation :)
2. I dont know yet how to make this feature into a easy user intuitive interface. Please give me your suggestions on how it could be and lets brainstorm baout it.
3. In the new version I am releasing, I have this feature. I have acheived it with css tableless layouts.. so there's one layer on the screen which is the navigation bar... I have fixed all bugs submited to the 3.0Alpha and hopefully will release the beta version in a few days..
Thanks again for the suggestions and thoughts
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
JZ, here again. I finally installed the new version locally and here are my thoughts:
(1) the many config files are a pain to work with, though it is nice that you only have to touch two of them. The files themselves could use some more inline documentation for beginner (and advanced) users. Since I'm not a coder I might take this on and leave the development for others.
(2) I'd like to see the return of the auto-drop down builder from the previous version. This time however, I'd really like it to be smarter and work like someone would want it to in a real web app. the insert screen should populate the drop down(s) from field(s) in lookup tables. The editing drop down should show the inserted value as the selected one, but also show the lookup values so that original value could be updated. You'd have to specify the lookup table in the builder config screen.
(3) I'd like to see the initial navigation screen made to be an include that is available on all the generated pages. I'd also like to see it look more like a nav bar (horizontal with buttons) or maybe even use form elements (drop downs that perform functions onChange).
More to follow. Thanks again for the project!
Thanks a lot for the suggestions JZ.
1. THe main motivation for separating the constants files is for most projects, there are different teams/peoples working on them and thus need lock privileges on these files. So from my experience, I tried to separate the different entities in the kinds of things they focus on. Definitely, there need to be more inline documentation :)
2. I dont know yet how to make this feature into a easy user intuitive interface. Please give me your suggestions on how it could be and lets brainstorm baout it.
3. In the new version I am releasing, I have this feature. I have acheived it with css tableless layouts.. so there's one layer on the screen which is the navigation bar... I have fixed all bugs submited to the 3.0Alpha and hopefully will release the beta version in a few days..
Thanks again for the suggestions and thoughts