[TYPO3-dev] Use ereg(), not stristr():

ben van 't ende [netcreators] ben at netcreators.com
Sat May 17 21:58:04 CEST 2008


Steffen Kamper wrote:
> Hi,
> 
> i would like to split that issue into 2 steps.

great usability enhancement. it NEVER made any sense to me, this ereg thingie. i 
just tried both for all these years without really understanding it.

gRTz

ben

> While i'm rearranging the options in OB i would like to change only label in 
> first step.
> (i think entering reg. expressions are the very advanced method, and those 
> know that it work with that option)
> 
> see screenshot at [1]
> 
> In a second step i would use Masi's proposal and enhance the search.
> 
> Did anyone noticed the bugs remarked in source and in toDo.txt? :)
> 
> vg Steffen
> 
> [1] http://www.steffenkamper.info/fileadmin/screens/ob.png
> 
> 
> 
> "Martin Kutschker" <martin.kutschker-n0spam at no5pam-blackbox.net> schrieb im 
> Newsbeitrag 
> news:mailman.1.1211032443.31712.typo3-dev at lists.netfielders.de...
>> Susanne Moog schrieb:
>>> hi,
>>>
>>> Steffen Kamper schrieb:
>>>> this is an option in Objectbrowser search.
>>>>
>>>> I think you confirm that no user will know what that means.
>>>> So can you make a proposal how this option could be labeled?
>>> always wondered what exactly the difference is. If I understood PHP 
>>> manual correctly there are two main differences:
>>>
>>> - ereg is case sensitive, stristr not
>> Yes.
>>
>>> - and with ereg it is possible to enter regular expressions
>> This is the main difference! But if we used internally preg_match we cold 
>> make it case insensitive too.
>>
>> Another option would be to allow for the more know "shell wildcards" ? and 
>> *. Internally they would be turned into a regualar expression.
>>
>>> Then I would propose something like "case sensitive" as label - of course 
>>> we would neglect the possibility to use regular expressions then but who 
>>> needs them in the object browser? <- Is there someone out there willing 
>>> to explain the usefulness of them there?
>> Instead of a check box we could have a drop down "search type": "string", 
>> "wildcard", "regular expression" (all case insensitive).
>>
>> Masi 
> 
> 


-- 
netcreators :: creation and innovation
www.netcreators.com -  www.TYPO3.nl

Interesse in werken bij Netcreators?
http://www.netcreators.com/bedrijf/vacatures/




More information about the TYPO3-dev mailing list