Feature #4042
when adding/editing an event use tce forms instead of the homebrew table form
| Status: | New | Start date: | 2009-07-29 | |
|---|---|---|---|---|
| Priority: | Could have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 0 |
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.
History
Updated by Francois Suter almost 4 years ago
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.
Updated by Christian Kuhn 9 months ago
- 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.
Updated by Ingo Renner 9 months ago
- Status changed from Rejected to New
I'd like to keep this open. It's a valid issue and I think it's doable.