Feature #4042
closed
when adding/editing an event use tce forms instead of the homebrew table form
Added by Ingo Renner over 15 years ago.
Updated over 9 years ago.
Description
When adding/editing an event use tce forms instead of the homebrew table form.
Don't know if that's possible at all, it would be very nice in the sense of consitency though. This is also something that bugged me with Gabriel all the time.
Low priority.
Well I tried and decided against it eventually. Actually what I tried to to is use the "TCA-light" introduced by Steffen Kamper in the User Setup module, but it turned out to be too constraining. TCEforms in its current state is really hard to use outside of its usual context. I'm all for using it, but I would then like to wait for Andreas Wolf's refactoring, which should make it easier to use TCEforms to build custom forms (I hope).
Also I added quite a few small JS calls which show and hide fields without reloading the whole page, and I think that's a definite usability improvement.
- Status changed from New to Rejected
I think we should close this issue for now:
There is still no better api for tceforms and it currently does not look like something will evolve in the near future. I think we should create a new issue if we ever find a realistic way to easier handle the additional fields. Maybe fluid together with a nice class structure could help here, but that would be a way bigger task that need to be thought through in the core, first.
- Status changed from Rejected to New
I'd like to keep this open. It's a valid issue and I think it's doable.
I'm looking at old Scheduler-related tasks and I wonder if it makes sense to leave this one open. Of course it is still valid, but the current policy is to close tasks with no feedback or activity for 6 months.
What such a project would need to do IMO is to replace the whole current architecture with a true TCA-powered Scheduler table, Flexforms for task options, no serialized objects in the DB anymore, etc. We should go the whole way or leave it as is. But I don't think anyone will tackle this.
I'd like to keep this open
- Category set to scheduler
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
Still an issue?
I think the Extbase way is ok.
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Mathias Schreiber)
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by