René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ENH - put toolbox extraparameter handling in specific classes","articleBody":"Currently, in aas_inittoolbox there is a parsing of toolbox extraparameters. This assumes that the extraparameters for different toolboxes can be handled the same, whereas this is something that is actually quite specific for a particular toolbox. I.e. that if there are colons in the value, then that value should be split.\r\n\r\nSince the extraparameters are specific for a particular toolbox, it makes more sense to put the handling of these parameters as a static method in the specific toolbox class. That also makes it more clear which toolboxes have known extraparameters.\r\n\r\nThe toolboxClass they all derive from would define a do-nothing default method, or even no method at all, since the method will only be called for classes that expect extraparameters.\r\n\r\nIn aas_inittoolbox it could then look something like\r\n\r\n```\r\n        params = {};\r\n        if isfield(TBX,'extraparameters') \u0026\u0026 ~isempty(TBX.extraparameters)\r\n            parse_extra = str2func([tbxname 'Class.parseExtraParameters']);\r\n            params = parse_extra(TBX.extraparameters);\r\n        end\r\n\r\n        constr = str2func([tbxname 'Class']); \r\n        T = constr(TBX.dir,params{:});\r\n```","author":{"url":"https://github.com/AljenU","@type":"Person","name":"AljenU"},"datePublished":"2021-12-08T09:50:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/311/automaticanalysis/issues/311"}