On UBot forum I’ve noticed that no one knows (or want to share info on) how to implement WYSIWYG (what you see if what you get) editor, that’s why I’ve decided to publish a snippet I was using for a while now. In case you don’t know what WYSIWYG editor is, it’s an advanced text editor that will allow you/your users to format text without needing to write HTML code. In this snippet we are using a popular and widely used TinyMCE.
Bellow is a simple snippet which will load valid proxies from TXT file and make them ready to be used inside UBot. Proxies are loaded to a list with name %PROXIES and whenever we want to change a proxy we just need to tell UBot which list item should be used as proxy.
When using UBot navigate command you usually want to make sure that the page you are trying to load really gets loaded, and beside that when using proxies you may also want to re-try loading the page, in case proxy was down when UBot tried to load the page or if the proxy may not work at all. So to make your software more robust you should use some checks after navigate commands, to make sure that the page you are expecting to load has actually loaded and if not, a command that will try to load it again.
In some cases you would want the URL to open in users default browser, instead of opening itself in UBot’s one, and for example that way replacing the custom HTML that you’ve generated previously.
Bellow is a simple UBot script that will open links clicked in UBot browser in users default browser. JQuery part of the code is written the way that it only applies that behavior to links that have attribute target=”_blank” set , so other links will still get opened as usual. In case that invalid URL (not starting with “http”) is passed into the command, it will return “” (blank string) without opening the default browser.
SNIPPET & TEST CODE (UBOT AND JQUERY):
Command Line Arguments plugin will allow you to retrieve Command Line arguments/options by importing that information into UBot environment; it will provide you with 1 command and 1 function which will let you to access attribute/options that were provided when executable was started. You can imagine it as alternative way of loading information from file or UI, by provide that information as attributes when executable gets started.
As you may be aware threading in UBot is not safe and may not work as expect under certain conditions, which would result in threads slowly dying out, so at the end, you only get left with 1 active thread, although you coded the bot to run with multiple.
To solve this problem I have created a plugin which will provide you with a dedicated “threads counter”, which uses atomic increment/decrement operations and will allow you to implement threading properly.
I guess you are excited as me and can’t wait for UBot v5 release. Because the information about v5 is cluttered around the forum and inside emails I’ve decided to create a blog post where I’ll be gathering information about what’s new in Ubot Studio v5.
Advanced Shell plugin will add 5 new UBot commands/functions to your UBot environment, and will allow you to hide that annoying Shell/Command Prompt window (“cmd.exe” will run in background), run Batch File Commands directly from UBot (no external batch files needed) and even retrieve the output from Command Prompt with UBot function (instead of reading additional files).
DATETIME Manipulation plugin will make your life easier when dealing with any kind of date/time format/language. It allows you to convert any date/time to any other format, including conversion from one language/culture to another. For easy of use plugin supports UBOT standard date and time format “$date”, UNIX time-stamp and a few other standard date/time formats.
This plugin will add one new UBot function to your UBot environment, and the function is called $datetime manipulation. Once its ran it will recognize the input date and/or time (specified by Input Format parameter), and it will convert it into a custom date and/or time format (specified by “Output Format”).
This type of encoding/decoding is used when information is transferred through URL parameters. Replacements are made so that valid URLs are maintained (parameter value that contains (decoded) “&” would mean the end of value for that parameter) and information isn’t changed during the transfer (space ” ” could be treated as “+” if not escaped properly).