[TYPO3-dev] [Fwd: Re: text/img and img elements with css-class?]

[Ralf Hettinger]

Hi grac,

a solution has to be technically feasible and fit into the whole of the
CMS. I couldn't see unwillingness, instead I saw some interesting
approaches being disucssed here and within the content rendering group.

I for myself honestly don't understand your final statement but don't
want to start flaming here as well...
... but hey - maybe see you later when flexible and scalable layouts
will have been improved within TYPO3. It admittedly is sometimes kind of
a long way discussing possiblities in before instead of just going
straight - with (too much / not enough?) resoning.

Cheers
Ralf

Am 21.12.2008 11:56 schrieb grac:
> hi joey
> 
> JoH asenau wrote:
>> Just to show you that most of (if not all) the stuff you want is already
>> there:
>>
>> lib.parseFunc_RTE {
>>  externalBlocks := addToList(img)
>>  externalBlocks {
>>    img {
>>      callRecursive = 1
>>      callRecursive.tagStdWrap {
>>        HTMLparser = 1
>>        HTMLparser {
>>          allowTags = img
>>          tags {
>>            img = 1
>>            img {
>>              allowedAttribs = alt,class,src
>>            }
>>          }
>>        }
>>      }
>>    }
>>  }
>>
>> Taken from these parts of TSref:
>> http://typo3.org/documentation/document-library/references/doc_core_tsref/4.2.0/view/1/5/#id4198758
>>
>> http://typo3.org/documentation/document-library/references/doc_core_tsref/4.2.0/view/1/5/#id4208523
>>
>> http://typo3.org/documentation/document-library/references/doc_core_tsref/4.2.0/view/1/5/#id4208672
>>
>>
>> To get the desired classes in the popup-image-dialogbox use this one
>> as Page
>> TSconfig:
>> RTE.default.classesImage = cool,cooler,coolest
>> http://typo3.org/documentation/document-library/extension-manuals/rtehtmlarea_manual/1.7.4/view/4/4/
>>
>>
>> And to make the whole thing perfectly fitting the 1em=10px approach you
>> could try adding a userFunc to the fixAttribs Parameter to process the
>> values:
>>
>> lib.parseFunc_RTE {
>>  externalBlocks {
>>    img {
>>      callRecursive.tagStdWrap {
>>        HTMLparser {
>>          tags {
>>            img {
>>              allowedAttribs = alt,class,src,width,height
>>              fixAttrib.width.userFunc =
>> tx_yourextension->user_YourWidthFunction
>>              fixAttrib.height.userFunc =
>> tx_yourextension->user_YourHeightFunction
>>            }
>>          }
>>        }
>>      }
>>    }
>>  }
>>
>> although I'm not sure if the width/height attributes are allowed to
>> contain
>> em values.
>> So maybe it would be even better to use the userFunc for an additional
>> style
>> attribute implementing the desired em values calculated on the size
>> given by
>> the editors.
>> So i.e. instead of width="325" you would get style="width:32.5em;"
>>
>> IMHO this would be much better than just using classes or percentages,
>> because the editors would be able to work with units they are used to
>> while
>> defining the size of an image, though still having a relative pendant for
>> the FE output available and of course you would still be able to override
>> the size of the inline style, if the editor choose a class by using
>> !important inside the class definition.
>>
>> HTH
>>
>> Joey
>>
>>   
> didn't really work.
> but i found my own workaround, as described earlier.
> 
> so, therefore i consider this thread as closed, but not as solved.
> 
> the discussion so far showed me a general unwillingness of the dev-team
> to go deeply into the topic of ELASTIC LAYOUTS, including IMAGES (as
> genuine content elements, not as decoration elements).
> 
> all i heard were technical notes on the feasibility, but nothing
> concerning the current dispute RE WEB 2.0 usability.
> 
> in my view this is very sad.
> but it tells a lot about the lack of layout specialists in the typo3
> community.
> 
> no offence :-)
> 
> stephan