automa VS Uno Platform

Automa open source tool to automate connection request on linkedin

I was able to make this happen by using a chrome extension called automa. Download Automa Here is a link to my workflow using that extension: Download

I use Automa for repetitive web searches. I'll use the integration with Google Sheets to pull whatever column I'm needing, loop through the data, run a script looking for specific anchor tags and save the href values into a table that can be read / exported once the automation is done running.

Automa [0] is just another no-code extension to automate browser. I used it to scrape excel files from the website of an open-end fund, which does not expose public API for its daily NAV historical data. This extension not only saved me time to manually point and click 1000s of url, but also give me a reason to procrastinate teaching myself selenium.

[0] https://www.automa.site/

Interesting, I don't know javascript though. In chrome I use the Automa extension, which is connecting lines with blocks (and you still have to pick up some js. I didn't even know what an 'element' was when I started). Even a beginner can do something useful after an hour of study or so. YMMV.

https://github.com/AutomaApp/automa

https://docs.automa.site/

There's a library of scripts you can copy from

https://www.automa.site/workflows

And Uno Platform (https://platform.uno/) is akin to React Native in terms of native controls usage.

also UNO Platform (C#) which is suitable for simple or complex cross platform business applications : https://platform.uno/

Why is this a problem? At face value, it isn't a problem. Taking a step back at a more global level, what does "uComponents" mean to the rest of the world? Many of the .NET developers who heavily use NuGet may have not even heard of Umbraco CMS, let alone a 3rd party plugin for it. What if people from the Uno Platform community are browsing NuGet for some kind of components extension library? You can see, this could get confusing outside the scope of the Umbraco community/ecosystem. On top of this, uComponents was developed against Umbraco v4, with its last release in 2016, now it's there to be lingering on the NuGet repository until the end of time, set in stone.

Not a fan of XAML after trying to get into it, but there is Uno Platform. It wraps native widgets on mobile, just like React Native (which is good for accessibility), and uses C#. https://platform.uno/

My guess is that it's mainly focused on mobile. On Windows, it has no overhead (behaving like a normal WinUI 3 app), on macOS I think it uses Catalyst by default (which was developed by Apple to make more iOS apps available for Mac desktops) and on Linux it draws its own widgets that the devs try imitating the GTK style with.

On Android and iOS, it just uses the native widgets which I think is a better experience so you can see my reasons for guessing it's mobile-first. That may or may not be what you want.

5- Uno

> ...building UIs with the document/element api

When the whole premise is flawed, JSX or not, does it really matter if there is a better or worse way of misusing a technology not meant for UIs?

Leave HTML and JavaScript to Wikipedia and other hypertext document libraries.

Unfortunately, WASM is not there yet, but people are trying: https://platform.uno.

Uno Platform is fully open source, under Apache 2.0 license. You can see the license here https://github.com/unoplatform/uno/blob/master/License.md