[Typo3-dev] feEdit API (structural ideas)

[Christian Jul Jensen]

On Sun, 6 Jul 2003 16:11:48 +0200, "Dennis Petersen"
<fessor at software.dk> wrote:

> > I think it will be fairly easy to write an extension that offers a
> > plugin which renders the edit-form, from any choosen table, using
> > feEdit API. That will as far as I understand DH, come pretty close
> > to some of the functionality he suggests.
> Hi Christian!
> Does that mean that the extension will only render a form from a
> selected table?
> I am trying to make a billiards tournament plugin and this involves a
> more complex DB structure with relations between several tables, so my
> needs would be to actually to provide table names and fields that I
> wish to render as paramters to the API (layout is in a template).
> So this is really not available in feEdit? No wonder I did not figure
> it out;)

The extension uses the TCA-configuration to determine the rendering of
tables, and thus reflects the BE way of rendering tables. The extension
provides a class that is instantiated with a tablename, you could
probably make an instance pr. table. It is also possible to give a
callback function, to define your own special rendering.


> So if you would not mind taking the time to describe how the feEdit is
> usually integrated into an extension I would not mind having a look at
> it. Do you have an extension which actually imports the feEdit and
> uses it... not as containing the source code within the extension from
> a copy paste? Sincerely,

Of course, julle_events, julle_external_links and julle_companydirectory
all uses the extension. Feel free to ask specific questions. Also make
sure to look in the source of feedit, the configuragtion options is
described in the var section of the class. If you find that the class
could be extended in ways that would generally fit needs like the ones
you have, please let me know, I'll consider including that in future
releases.

*note* Please use t3lib_div::make_instace("julle_feedit"), instead of
new julle_feedit. I don't do that in the extensions mentioned above, but
that's the right way to do it. I just really wasn't aware of the
difference, when I coded the stuff.

-- 
Christian Jul Jensen
Freelance webprogrammer
TYPO3 typehead Denmark