[TYPO3] extension development.

[mario]

Hi Bernd, all

thanks for your reply.
I have tried Kickstarter a number of times, and mostly it works
wonderfully. Thanks for your advise.

Still, I am still puzzled on how much php code Kickstarter is supposed
to write by itself. 

Consider the function getFieldContent. Most often I have got just the
following definition (which by itself is not enough to get a working
extension):

-------------------------------------
function   getFieldContent($fN)	{
		switch($fN) {
			case 'uid':
return $this->pi_list_linkSingle($this->internal['currentRow'][$fN],
$this->internal['currentRow']['uid'],1);	// ...
			break;
			default:
	return $this->internal['currentRow'][$fN];
			break;}}
------------------------------------

Once I got the extra case (My_field_name being a RTE textarea) too,
which however it do not understand how to reproduce 
				
---------------------------------------
		case "My_field_name":
return
$this->pi_RTEcssText($this->internal['currentRow']['My_field_name']);
			break;
---------------------------------------

So the question is: how do I exactly control which code Kickstarter is
going to produce by default?

Thanks for any further help.
mario

ps is anybody working to improve kickstarter even more?



On Thu, 2007-03-08 at 23:30 +0100, Bernd Wilke wrote:
> On Thu, 08 Mar 2007 01:24:29 +0000, mario wrote
> with subject "Re: [TYPO3] extension development.":
> 
> > Hi Bernd,
> > 
> > On Thu, 2007-03-01 at 10:19 +0100, Bernd Wilke wrote:
> > > On Wed, 28 Feb 2007 11:25:22 +0100, Asbjørn Morell wrote
> > > with subject "Re: [TYPO3] extension development.":
> > > 
> > 
> > > 
> > > partly supported (if you choose the correct options in kickstarter):
> > 
> > which one exactly? 
> 
> I used it a long time ago - and didn't found it at once.
> 
> but digging around (I just started the kickstarter to build up a new
> extension and peeked into 'view result') I got it:
> 
> when creating a frontend-plugin you can choose between different options.
> just use the first:
> (there the last three input-options)
> --------------------------------------------------------------------------
> >(x) Add to 'Insert Plugin' list in Content Elements'
> 
>     Most frontend plugins should be added to the Plugin list of Content
> Element type 'Insert Plugin'. This is what happens with most other plugins
> you know of.
>     [... pic shown ...]
> 
>     [ ] Add icon to 'New Content Element' wizard:
>     [... pic shown ...]
> 
>     Write a description for the entry (if any):
>     [___________________________] [English]
> 
>     If you have configured custom tables you can select one of the tables
> to list by default as an example:
> >   [_table_(tx_myext_table)_(n_fields)__][V]
> >
> >   [X] Listing: Sections instead of table-rows
> >   [X] Singleview: Sections instead of table-rows
> 
> --------------------------------------------------------------------------
> first you have to create your own table to be used, then this table will be
> available to select in the dropdown.
> 
>  
> > > * listing of records
> > > * displaying single records
> > 
> > do you mean as it seem to work for Kasper`s cd collection example?
> 
> I don't know. possible. Maybe someone else can verify?
> You get a framework to display a list of records and jump to a
> single-record-display. It seems all is done. Just if you didn't like the
> layout, or shown fields you have to change the generated php.
> 
> At the time I used this I had to enhance all functions, because I used
> three cascaded tables instead of one single, which made all a little bit
> more difficult (I had to build up the queries by myself instead of using
> the generated single-table-queries)
> 
> > Very happy if you clarify these points
> > my best 
> > mario
> 
> BW
> Bernd
> 
-- 
mario <chiari.hm at flashnet.it>