Since I switched to Windows last year I'm using Microsoft's Powershell as my main shell environment (on my personal laptop). At first I didn't really look into Powershell's feature until around half a year ago when I found the motivation to work on a nicer prompt and spent some time migrating my ZSH profile to Powershell. I ended up creating a different profile that suits my needs, and that I had lot of fun building.

That's how my prompt looks:

It has the following features:

• Used for both Windows and Linux subsystem
• Current directory
• A dynamic "main directory" used to specify the context
• Git branch
• Current time
• Last command success/failure
• Admin user label

That was a cool and fun way to learn more about Powershell features, after spending all my life with sh, bash, and zsh it was refreshing to try out a different way to write shell scripts.

Some implementation details

Left and right prompt

That's a very common feature in other...

This week we released updates to HabitCat, our simple mobile app to develop and track new routines and habits.

1. We created an improved welcome screen that displays our cute cat logo and looks a bit more welcoming.

2. Habits can now be deleted and reorganize from the home screen! Just click on the "Edit" button on the top right corner.

3. Someone reached out to us on Twitter to suggest a randomized default color for habits. That's a simple, neat little detail, so we did it.
4. We were (and still are) looking for ways to improve our form to create new habits. We are trying a new way to present the colors as a wheel instead of a grid. We should maybe think about making it more interactive (would it be cool to be able to spin it?) in the future.
5. Improved localization for our three supported languages: French, German, and English. The back button and date content (months, days, etc) are now localized correctly everywhere.
6. Some touch are...

I'm currently learning to use the game engine and editor Godot, and I just realized today that you can see and inspect the complete scene tree of a running Godot project.

It's easy to do, but somehow I didn't know about it, the button to click has an unexpected name ("Remote") that doesn't really communicate what it does!

1. Start your scene (with F5 or by clicking on the Play button on the top right corner)

2. Now that the scene is running, notice that at the top of the "Scene" section you now have two labels, Local and Remote

3. Local shows you the tree as it is in your scene file, while Remote shows you the tree as it is on a "remote running process"! Click on it and you can now inspect any node as they are in your game. As an example, in the following screenshot Tile is a node added dynamically from a script.

Note This article is a part of a series of tutorials "Creating an Electron application with Svelte 3 and TypeScript".

• Part 1 - Introduction and setup our dev environment
• Part 2 - Define our goals and implement an interactive search bar
• Part 3 - Display search results and call the API
• Part 4 - Coming soon... Stay tuned! 👀

Check out the rest if you haven't yet 😉.

As a reminder, in part 2 I made a mockup of the application that we are building. That's how the list of result was represented:

What can we get from this?

• Our application has a top menu (that we already created) and a content section
• The content section is divided in two panels, the list of articles is on the left side, and article detail on the right side
• The list is displayed vertically, and is likely to be scrollable
• Every r...

Note This article is a part of a series of tutorials "Creating an Electron application with Svelte 3 and TypeScript".

• Part 1 - Introduction and setup our dev environment
• Part 2 - Define our goals and implement an interactive search bar
• Part 3 - Display search results and call the API
• Part 4 - Coming soon... Stay tuned! 👀

Check out the rest if you haven't yet 😉.

Before starting to work on our project, let's define a plan and a set of goals.

We know that we want to interact with Wikipedia's API, so what do we need for this? A first version would be like this. I will keep our goals simple for now, we can always add more things later.

Abstractly we have 3 components:

• a simple search for in a menu bar available at the top of the application. The first version will only have an input text and a button to call the API.
• a listing of search results in a left pan
• a right pan to vi...