Page 38 of 237

Re: [Script] WME Validator 1.1.5 / 06.01.2015

PostPosted: Tue Jan 06, 2015 12:22 am
by berestovskyy
06.01.2015 v1.1.5:
- Temporary disabled #36, 37 (Unneded node A/B)
- Fixed the crash on a new segment save

Re: [Script] WME Validator 1.1.4 / 07.11.2014

PostPosted: Tue Jan 06, 2015 12:33 am
by berestovskyy
SuperMedic wrote:Is there a way to provide an access function that returns an array or object of all of the segments that have been found?

Well, internally there is such an array. Unfortunately due to the compilation process, the fields might change their names from version to version :(

I plan to release an open source version o Validator, so it would be possible to access such an array there.

Re: [Script] WME Validator 1.1.8 / 07.05.2015

PostPosted: Thu May 07, 2015 7:32 pm
by berestovskyy
The update has been published.
Sorry for the inconvenience :(

Re: [Script] WME Validator 1.1.9 / 05.11.2015

PostPosted: Thu Nov 05, 2015 11:08 pm
by berestovskyy
Thanks guys for your patience. The script is updated.

Re: [Script] WME Validator 1.1.13 / 16.11.2015

PostPosted: Mon Nov 16, 2015 9:38 pm
by berestovskyy
KuniaKid wrote:I haven't found any guidelines in this matter, so I add the mark. Is there a way to switch off the check for this in Validator?

Validator Localization Packages
Validator Localization Files at GitHub

New version is out:
- Updated for US #171 'Incorrect abbreviation'
- Added 'At the bottom' option

Re: [Script] WME Validator 1.1.13 / 16.11.2015

PostPosted: Wed Nov 18, 2015 6:44 am
by berestovskyy
crazycaveman wrote:Nice. That repository will be handy to help keep my localizations up to date. I have framework localizations for a number of states, Hawaii is in there, if you want to use that to tweak the existing checks to your needs (out disable then completely).

Wow that's a nice piece of work there!

So I guess we miss a support for states, right?

Re: [Script] WME Validator 1.1.14 / 17.11.2015

PostPosted: Wed Nov 18, 2015 7:05 am
by berestovskyy
SuperDave1426 wrote:I would still prefer it to have its own tab.

Guys, I've played with tabs some time ago and I didn't like the tabs were wrapped onto a second line. I will give it another try, but it's not the highest priority ATM.

We could also try to put it into one of the existing tabs...

Re: [Script] WME Validator 1.1.13 / 16.11.2015

PostPosted: Sat Dec 12, 2015 1:18 pm
by berestovskyy
Zirland wrote:

How are the files on "i18n" repository used? What is their purpose?
Should we migrate to use your repository?
Does "our" greasyfork script have higher priority on values or does "your" i18n file win?

I18n is a public git submodule of Validator. Those are the settings/translations bundled with Validator.

It was always an option to either use an external script or ask me to change somethings it the Validator. So the changes you commit into the Github repo will be shipped with the next version. The greasyfork script will override those settings.

It's up to you to commit into the repo and/or support the script. I suggest you to use the greasy fork script for the tests and commit proven/tested settings to the defaults in i18n repo.

Re: [Script] WME Validator 2018.07.18 (BETA)

PostPosted: Wed Jul 18, 2018 2:16 pm
by berestovskyy
Hi guys,
As you might know the Validator is fully open source now. Source, localization, release files along with instructions are available at GitHub:

I hope that move will help to reborn the script and will make sure it will never die again.

I just made a first public release. The basic script functionality works, but there is a huuuge room for improvements ;)

Unfortunately, there are just two developers working over the project. If you feel you are up to a new challenge, feel free to contact me. We need your help.


Re: [Script] WME Validator 2018.07.18 (BETA)

PostPosted: Thu Jul 19, 2018 3:28 pm
by berestovskyy
TWBudrys wrote:I could help

Great! Here is how:

  1. Clone the repo:
  2. Grab a bug:
    (or whatever you think has to be fixed)
  3. Fix it.
  4. Create a pull request.

If you are not a developer, there definitely will be issues with localizations: