[Typo3-dev] TS inconsistencies...

["Kasper Skårhøj"]

Hey Dan.

A comment on your ideas with objects in PHP and TS; 

Generally; TS is a fast way to get a website up and running as JH said - if you know TS, that is... 

About your "100% backwards compatible" thing I'm a little sceptical, but surprise me. Maybe I don't really get what is so inconsistent that you have to do this. 

Then let me express just one fear; That what you are trying to do with good intensions, something which may be beautiful and which developers like yourself and many others can relate to much better than TS - that you are trying to IMPOSE this onto TypoScript while TypoScript may not be the right "agent" to carry the implementation! I think Rene shares my view here. So, when I read what you write about your ideas I simply ask the question: WHY do you want to use TypoScript anyways! Why not just create a NEW, parallel, 100% PHP based implementation, totally non-backwards compatible with TypoScript, based on concepts which those 50% of this list who more or less dislikes TypoScript anyways can much better understand! Waste TypoScript! Why bother! Throw it out if it doesn't fit what you want to do! I'm not sarcastic here, believe me. When I use TypoScript for my various implementations in TYPO3 I do it because a) the syntax is at hand and b) it works nicely for what I want most of the time. But I DON'T keep using TypoScript because I'm nostalgic about it! Really, if someone came up with an alternative frontend engine based on PHP objects then I would certainly welcome it warmheartedly! Such an implementation might have another audience, but wouldn't that just make TYPO3 fitting more people?




God bless

- kasper

*********** REPLY SEPARATOR  ***********

On 25-07-2003 at 13:50 dan frost wrote:

>>
>>
>>Sounds interesting. I suggest you post more details about it, because you
>have 
>>to do some advertising and persuade us before it will go into T3 :-)
>>
>>I think a new TS have to be backward compatible or old TS can be
>converted 
>>safe and easy.
>>  
>>
>I will certainly do some more persuading - but I need to work out how it 
>could be done - especially re: backwards compatibility.
>
>I aim for 100% backwards compatibility.
>
>>To make it more clear. Let's say you have an TS editor that provide (with 
>>popups or similar) information about possible properties and it's data
>type 
>>while editing. Would that be a (big) step forward?
>>  
>>
>>The point is that could be done because the needed information is
>available 
>>through the typo3.org documentation system and it's already used at some 
>>places in the BE.
>>  
>>
>Granted - the information already exists. What I think should happen is 
>that, using well written classes, these pop-ups would be dynamic. E.g. 
>each class would have a structure like:
>
>class someDataType {
>  $someDataType_description = "Blurb to be put into the pop-up";
>
>  function someFunction() {
>
>  }
>   etc...
>}
>
>The pop-up would then have (i) a description of the datatype; and (ii) a 
>list of methods - gained from asking the class what methods it has... 
>and possibly what the datatype's parents are...etc
>
>Look at php5 - this would be beautiful code with php5's new object 
>model. (See, e.g. http://www.phpbuilder.com/columns/argerich20030411.php3).
>
>dan
>
>
>_______________________________________________
>Typo3-dev mailing list
>Typo3-dev at lists.netfielders.de
>http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev



God bless

- kasper


- kasper
-------------------- o ---------------------
>>>    In God I trust - others pay cash!     <<<
Check www.typo3.com