Code refactoring & Download system rework

• Brought code up to PEP8 standards
• Redid download system. No more non-functional GUI; it uses automatic installation. In addition, the over size of the dependencies has decreased to ~700 MB from ~1.5 GB
• Couple of bug fixes

v1.4.5: More bugs, string compare function

• Fixed bug with NLTK verb phrase extractor
• Added a string compare function
• Example application code refactoring

Bug updates, Phrase Extractor

• More code refactoring. This time, I redid the structure of the main folder, making it simpler to understand
• Updating code. Previously, I used global variables to store file-wide variables. This has now been changed and done properly through the self variable
• User interface change. Instead of the confusing arguments that previously existed whenever calling a function, a new simpler interface has been created. Details are above
• Multiple bug fixes
• Added Phrase Extractor class. This allows the user to get noun, verb, and prepositional phrases within a text
• Updated pip information and comments

Topic analysis, bug fixes, some code refactoring

• Toolkit NLTK dependency bug. This could have caused the dependency function to not work, but it now does
• Topic analysis update. There is a new function which allows you to extract the important information from within a text
• Code refactoring. Tests have been redone, allowing for flexible updates in the future to be added with ease. In addition, a lot of other code has been changed
• Toolkit POS Tagger update. The update brings an interesting feature which allows you to get the POS tag from all 3 parsers, and regex4dummies will tally up the results, giving you the choice to pick which tag you think is correct

Miscellaneous Update & overall performance improvement

• Accuracy tester is a lot better ( except for semantic comparisons ). A new "corpus" will be added soon to get accurate semantic comparisons
• Literal parser improvements ( which are numerous ). Multiple bug fixes, sub-patterns are not gathered ( patterns within a larger pattern no longer count as individual patterns ), and some general improvements
• Behind-the-scenes work to update code and make it more flexible for future updates
• GUI update. It is now backwards compatible
• Toolkit update! It should now work, and I apologize for it not working in previous updates
• Topic analyzer update. It should find more topics, as well as returning the topics in order from most-likely to be the main topic to least likely. In the future, an update will allow the extraction of the most important information as a whole ( not just the topics )
• Source code is smaller. Removed some code that was not being used, helping reduce the size of the repository

Import error fix

This will not be released on PyPI because it has incomplete feature updates, but it contains a fix to the Toolkit() class which allows it to be used.

Feature additions and some minor updates

• Two new functions have been added! The tokenizer function will return the tokenized version of the string passed using the given parser ( pattern, nlpnet, or nltk ). The dependency function will return the string with the added dependency information using a specific parser( pattern, nltk, or nlpnet )
• FuzzyWuzzy is the new applicability score. In the past, it has been pretty hard to find a good way to implement the applicability score, and this has been reflected in the quality of the score. Hopefully, this update will greatly improve the accuracy of this score
• Small topic finder update

Bug fixes and examples update

This is overall a minor update, except for a bug fix that could have caused the literal parser to crash.

• Accuracy Tester released
• Multiple bug fixes
• GUI updated to the newest version of regex4dummies ( it is not backwards compatible )

Fatal bug fix

A fatal bug was introduced in 1.3.5. This has been fixed and the issue has been corrected.

Feature Update

• Topic identifier has been added. This is currently in "beta" and only features NLTK's NE chunker. In the next releases, functionality will increase. Think of this as a preview of what is to come
• Substantial code refactoring. The semantic parser code structure has been changed. This is mostly intended for developers only who would like to develop their own modules for regex4dummies, but it also make the code easier to read
• Behind-the-scenes parser update. A Stemmer has been implemented in pattern comparison to help the parsers be more accurate ( only applies to individual parser calls, not the "all parser" call )