Thanks Martin,

Martin Heidegger a écrit :
> I just read the code of FlashFinder,  some things that come up in my mind:
>
> * Packaging: This project should (to success) be used by lots of people so
>                       a popular package like: 
> org.osflash.usability.text might be
>                       reasonable.
Yes
>
> * Localisation: All the localisation should work seamlessy therefore I 
> suggest something like
>
>                        class ....EnglishLocale {
>                           var find:String = "Find";
>                           var matchCase:String = "Match case";
>                           var highlightAll:String = "Highlight all";
>                        }
To have a file by language ? (sorry I don't know "seamlessy")
Something like :

    function Locale()
    {
        _default = "en";
       
        _locale = {}
        _locale["en"] = org.osflash.usability.text.flashfinder.lang.en;
        _locale["fr"] = org.osflash.usability.text.flashfinder.lang.fr;
    }
   
    public function getLocale(s:String):Object{
        return _locale[s] ? _locale[s] : _locale[_default];
    }

trace(getLocale().find);

?

I think too to xml to add new language without recompilate.
(use the the both method, and xml optional)

>
> * It is important that people can optimize search settings ( on custom 
> way ) therefore i would provide a "Finder" interface like:
>
> the benchmarking should be done outside of this process - to work for 
> every implementation.
> Of course those implementations should be added to the process somewhere
Yes good idea
>
> * The current way to initialize the application is too complex imho. I 
> think its important for
> "miniFlashers" to have ONE function that just includes everything 
> (where he doesn't need to
> bother about anything) like:
>
>     FlashFinder.use();
With FlashFinder.initialize(target:MovieClip, name:String, depth:Number, 
x:.....) only target is necessary and it make all textFields searchable
(ok to use _root if no target).

FlashFinder.include() was only to create the map in cache before 
selection....

I think change it and do :
mode "all" (default) >> all Textfields are searchable
mode "include" >> only included TextField are searchable
mode "exclude" >> only non excluded TextField are searchable are searchable

And I will create FlashFinder.cacheMap(t:TextField) to cache a textField 
Map...
>
> and it just indices every field and adds a on-the-fly textsearch by 
> pressing a standard keyboard
> shortcut like "Ctrl"+"F" (should be contained in the locale settings)
"Ctrl"+"F" is not universal method ?
>
> Further customisation should be possible of course:
>
> var flashFinder:FlashFinder = FlashFinder.getInstance();
>
> flashFinder.include(tF); // normal textfield adding to search
>
> var textFieldResolver:TextFieldResover = new 
> AutoTextFieldResolver(flashFinder, _root.mc); // automatically include 
> all textfields
> textFieldResolver.ignorePattern ("ui*"); // pattern for textfield 
> Names that should be ignored
Great
>
>
> // custom UI
> var myInterface = new SearchUserInterfaceImpl();
> flashFinder.setUI(myUserInterface);
>
> interface ... SearchUserInterface {
>    public function setFinder(finder:FlashFinder):Void;
>    public function onMapInfo(map:Object):Void;
>    public function onSearchInfo(info:Object):Void;
> }
>
>
> If you look at this apporach of setting up the stuff some of the 
> methods you put in some of the classes are just at the wrong place.
>
> Its just my thoughts - what do you think?
Good opinion :-)
I work on it.

Jonas



_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to