VBA download file from website - popup window

I am trying to automate a file downloading from a website. When I do the download manually, all I have to do is to click on the "save" icon (floppy disk), then another window pops up for a second and the download begins (while the popped up window disappears). What I usually do (when I automate a download) is to find the files URL, then I use the URLDownloadToFile function. But in this case I cannot find the url in the html. I tried to use the .click and FireEvent on the object but nothing worked. So I started to think (based on similar question in this site) that a script generates the URL when I press the "save" icon. Unfortunately I am not familiar with javascript or how it works. Right now I am trying to use my browser's developer tools's console to figure out what happens when I click the object. BTW: this object is an object. I searched the web for answers, and I think that somehow I will have to call the javascript myself if I want to download the file, with something like execScript. But how do I find out which script gets called when I click on the icon? And more importantly will I be able to understand your answer without completely understanding how a webpage works? :) P.S.: I know it would be far easier if I could give you the site address, but it requires a login to see the stuff that I am talking about...

Read More

Laravel Octane Adds Support for Roadrunner v3

The Laravel team release Octane v2 with support for Roadrunner v3! The post Laravel Octane Adds Support for Roadrunner v3 appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ---

Read More

Small but powerful CLI apps with Minicli

 Minicli is a lightweight PHP structure for building order line applications. While it gives a moderate methodology, you can in any case make strong CLI applications with it. Here are some little yet strong CLI application thoughts that you can carry out utilizing Minicli:

Schedule Director: Make an order line application that permits clients to deal with their errands and plans for the day. Clients can add undertakings, mark them as finished, erase errands, and view their rundown.

Climate Correspondent: Foster a CLI application that gets climate information from a climate Programming interface in view of client input (e.g., city or Postal division). It can show current atmospheric conditions, figures, and other important data.

Document Coordinator: Fabricate a CLI application that sorts out records in a registry in light of their sort, expansion, or different models. Clients can determine the source and objective catalogs, and the application will move or duplicate documents in like manner.

Secret phrase Generator: Make a CLI application that produces solid, irregular passwords in view of client characterized models like length, consideration of extraordinary characters, or explicit person sets.

URL Shortener: Foster a CLI application that interfaces with a URL shortening administration Programming interface to abbreviate long URLs and give an abbreviated variant to more straightforward sharing.

Word Counter: Form a CLI application that takes a text document or contribution from the client and counts the quantity of words, characters, lines, or other pertinent insights.

ASCII Workmanship Generator: Foster a CLI application that changes over a picture or text input into ASCII craftsmanship. Clients can determine the information record, textual style, and other customization choices.

Markdown to HTML Converter: Make a CLI application that changes over Markdown documents to HTML. Clients can indicate the information record and alternatively tweak the result document area and arrangement.

Keep in mind, these are only a few guides to kick you off. With Minicli, you have the adaptability to make different sorts of order line applications in view of your particular prerequisites. You can use the effortlessness and extensibility of Minicli to fabricate little yet strong CLI applications custom fitted to your requirements.

Here new way ....

Building CLI applications can be a lot of fun. We don't have to worry about the UI, and we can write beautiful PHP code that doesn't need any build steps.

When building CLI applications in PHP, we aren't as spoilt for choice as in building web applications - but there are some solid contenders. From using the defacto standard Symfony Console component or the extra spicy Laravel Zero. However, when building a CLI application, you may want to be as dependency free as possible - which is where Minicli comes in. Minicli was released a while ago by Erika Heidi as an experiment to build a dependency-free CLI framework that leaned on PHPs readline extension as its only dependency.

I have been spending a lot of time investigating CLI options for a project I am working on. At first, I started with my usual choice: Laravel Zero. It is familiar to me and any other developer who knows Laravel. Then I started questioning the portability aspect and requiring PHP for people who want to use it. This is for work, and not all of our users have PHP installed. So I dived into the world of compiled languages, looking at both GoLang and Rust. While there aren't many options available, the options out there are excellent.

There has been a lot of talk about native PHP recently, which drew my attention back toward the PHP space. What if I could build a lightweight, easy-to-maintain, and portable PHP CLI application? This was when I took another look at Minicli. Having played with it when it first came out, I was impressed with how nice it was to use for something dependency free - but also how easy it was to get started!

The recommended approach for building a Minicli application is to use the application skeleton and composer to set everything up and ready for you.

composer create-project --prefer-dist minicli/application my-awesome-idea

The directories should be familiar enough for you as Laravel developers, having an app directory and namespace. The commands you can create are recommended to be built as Command Controllers, which are class-based commands.

We create a command namespace under app/Commands, where you keep your commands.

mkdir app/Commands/LaravelNews

Under each namespace, you can add multiple commands for different variations. It is inferred that if no arguments are passed, you will want to use the DefaultController. Let's have a look at how to create a command.

declare(strict_types=1);
 
namespace App\Command\LaravelNews;
 
use Minicli\Command\CommandController;
 
final class DefaultController extends CommandController
{
    public function handle(): void
    {
        $this->getPrinter()->display("Laravel News rocks");
    }
}

Each command controller must be handled and doesn't have to return anything - unlike in Symfony or Laravel Zero, where an exit code is expected. To interact with output, you get the printer - and ask it to output something.

So, if we want to add an alternative version - we can create another command controller in our namespace.

declare(strict_types=1);
 
namespace App\Command\LaravelNews;
 
use Minicli\Command\CommandController;
 
final class InfoController extends CommandController
{
    public function handle(): void
    {
        $this->getPrinter()->info("Laravel News rocks");
    }
}

Now we can call our command:

./minicli laravel-news info

Which will give a different view to the default command, and we can use the following other options:

display(): A simple text output.
info(): An informative text output.
error(): An error formatted text output.
success(): A success formatted text output.

Each option accepts a second argument as alt for alternative output, which will do a block color output with writing instead of colored writing.

It isn't as pretty as something like Laravel Zero using Termwind - but sometimes you don't need pretty!

Usually, when building a CLI application, we want to interact with a third-party API or another service to perform an action or logic. In Minicli, this is done by creating services.

// minicli
$app = new App();
$app->registerService(
    'email',
        new MyEmailImplementation(),
);

Then within our commands, we can get the app instance and call our service directly:

public function handle(): void
{
    $service = $this->getApp()->email;
 
    try {
        $service->send(new EmailTemplate());
    } catch (Throwable $exception) {
        $this->getPrinter()->error($exception->getMessage());
    }
}

So we have a lightweight, powerful CLI framework that we can leverage to aid in our development workflow - that has no dependencies allowing us to write beautiful PHP.

Read More