

Others = response.css('body > main > div.dictionary > div.res_cell_center > div > div.homograph-entry > div > div > div.hom > h2.titleTypeContainer + div.sense > div.synonymBlock > span.firstSyn > span::text').extract() Norms = response.css('#content > div.lex-container > div.main-content > div > div > div > div > section > div > div:nth-child(1) > div > div > div.synList > div > p > span:not(.sense-registers)::text').extract()īold = response.css('body > main > div.dictionary > div.res_cell_center > div > div.homograph-entry > div > div > div.hom > div:nth-child(2) > div.synonymBlock > nsehead > span.key::text').extract() Words = response.css('#filters-0 > div.relevancy-block > div > ul> li > a > span.text::text').extract()īolds = response.css('#content > div.lex-container > div.main-content > div > div > div > div > section > div > div:nth-child(1) > div > div > div.synList > div > p > strong::text').extract() If ($mode = 'f' | $mode = 'favorites'), callback=self.parse) Public function find($keyword, $mode = null)įile_put_contents($path, json_encode('')) Here's the core PHP file: Tehsaurux.php tsx = $this->getTsx() Do I just dump the entire spider in the models directory, or break it up and spread it out over arbitrary directories to make the MVC framework happy?
#REVIEW RANDOM SYNONYM HOW TO#
I myself am even stumbling to figure out how to integrate it into Laravel, an MVC framework. Some hosts may need scripts in certain locations. The user only needs to know PHP, but requires Python.It will require either user path configuration or more work on my part to automatically find/set paths.

#REVIEW RANDOM SYNONYM WINDOWS#
It may not work on every server, depending on its OS (I'm running Windows 10).I am concerned that they may not be robust for these reasons: I think the two main files - Tehsaurux.php and synoSpider.py - are alright. It works with PHP agnostic and Scrapy for Python. It crawls three thesauruses and will find a random synonym for you. I have just finished core functionality for Tehsaurux.
