-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qc4 FormBase namespacing #18
Comments
I do not know what the @spekary thinks. But I use this like this: use QCubed\Project\Control\FormBase as QForm; Then: class Home extends QForm It can be very freely used, for example: use QCubed\Project\Control\FormBase as Form; and class Home extends Form PS. In that case, if I understood your question correctly... |
No it is just to be more convenient and without aliasing. |
Okay, I got it. Let's see what @spekary says... |
All user form classes should derive from |
Every other control have ControlName and ControlNameBase naming. |
@spekary can you check this code?
class Home extends FormBase {
previous v.3 was:
class Home extends QForm {
i think should be:
class Home extends Form {
or,
class Home extends Qcubed\Project\Control\Form {
All *Base classes are default qcubed , I think will be more convenient
to have different naming in project instead of default ones.
so we can write this at start:
use QCubed\Project\Control\Form ;
The text was updated successfully, but these errors were encountered: