Skip to content
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

Make it possible to render forms in v9.5 #4

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

kaystrobach
Copy link
Contributor

No description provided.

composer.json Show resolved Hide resolved
ext_emconf.php Outdated Show resolved Hide resolved
@kaystrobach
Copy link
Contributor Author

done.

At the end there is one big question left - will we invest time to keep the wizard running?

https://github.com/kaystrobach/form_legacy/blob/patch-1/Classes/View/Wizard/Element/FormWizardElement.php

Would mean, that we put extjs into the extension, that we change the VH to fit in the new schema of v9, that we either adjust the JS to load extjs either via requireJS or the pagerenderer.

any ideas for that dilema?

@kaystrobach
Copy link
Contributor Author

from my POV it's not worth the time.

But there is also an community POV:

but there are tons of these forms in the wild, if there would be a sponsor it should be atleast possible to make it an option to enable the wizard again.

@bmack
Copy link
Member

bmack commented Nov 14, 2019

Hey @kaystrobach,

in general I'm happy to work on this extension (which could be "making it possible in newer versions of TYPO3" or "add better migration tools to the new Form Framework), if:
a) it is properly funded
b) the need and use cases are available (personally, I do not know who was / is using this thing who reached out other than yourself), as it's always hard to do something in the wild

As this extension, just like most of TYPO3 contributions (incl. my time) are funded by individuals or their employers (and their clients), I won't actively put in energy in doing so.

Other than that, I don't think I don't think it makes a lot of sense to put in my (or anyone else's) spare time in continuing developeing an extension which has been superseded by a better alternative.

@kaystrobach
Copy link
Contributor Author

I think this whole project is not so well known :-/

Maybe we should form an initiative out of it ... just thinking.

@olforestman
Copy link
Contributor

I am with Kay. The extension is not well known. We've spent a lot of time on the form wizard in the former days. It is a very complex construct and will be quite difficult to have it running with the old ExtJs version (I think newer ones wouldn't work). IMHO it would be better to create a migration path to the new form framework.

@kaystrobach
Copy link
Contributor Author

@bmack having a final decission to remove the form wizard here would allow me to finalize this PR

Options:

a) just render a textarea
b) render the wizard and migrate all the stuff.

@bmack
Copy link
Member

bmack commented May 26, 2020

Basically: Let's make the extension to be working in v8+v9 at the same time. This means that in v9 we render the textarea whereas in v8 the custom Wizard is loaded.

@kaystrobach
Copy link
Contributor Author

Agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants