i'm starting work on http://sesat.no/scarab/issues/id/SKER2149 by analysing today's situation with AbstractSearchCommand.
The goal is not to rewrite the class but to find the concerns it covers and create smaller encapsulating classes that can be delegated to. To divide and conquer the mess that it has become. Documentation is ongoing here: http://sesat.no/new-design-proposal-for-searchcommand-and-abstractsearchcommand.html or the wiki version https://confluence.sesam.no/confluence/display/SESAT/New+design+proposal+for+SearchCommand+and+AbstractSearchCommand Because this class is used in a number of way i'd really appreciate everybody that could spend a little time reading through the page, remembering all the AbstractSearchCommand complaints/limitations they have or issues somewhat related, and giving feedback. and don't presume i'm remembered any previous conversations! ~mck -- We are born naked, wet and hungry. Then things get worse. | semb.wever.org | sesat.no | sesam.no |
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
