@sbegaudeau

Proud dad, Web developer at Obeo, Marvel enthusiast and sushi lover

 Nantes, France
sbegaudeau.com
Joined October 2009
  • Tweets4.1K
  • Following301
  • Followers529
317Media
Replying to @_AxelRICHARD_
@_AxelRICHARD_ just showcased how to migrate an Eclipse plugin using @EclipseSirius + Xtext to @code by ♻️ Keeping the same Xtext tooling 🔥 Reusing existing odesign files with the Sirius Desktop compatibility layer 🧩 Integrating Sirius Web in a VSCode extension #EclipseCon
Register existing odesign files in Sirius Web to use the Sirius Desktop compatibility layer

ALT Register existing odesign files in Sirius Web to use the Sirius Desktop compatibility layer

Leverage Sirius Components to integrate diagrams from Sirius Web in any web based applications such as VS Code

ALT Leverage Sirius Components to integrate diagrams from Sirius Web in any web based applications such as VS Code

The existing Eclipse plugin based on Xtext and Sirius Desktop

ALT The existing Eclipse plugin based on Xtext and Sirius Desktop

The new VS Code extension using Xtext LSP and Sirius Web

ALT The new VS Code extension using Xtext LSP and Sirius Web

6
Great presentation by @melaniebats showing some of the latest features of Sirius Web in action @EclipseCon 👨‍💻 Domain and diagram definitions directly in the browser 🔥 Creation of form representations using our new WYSIWYG editor 📈 Charts in form representations #EclipseCon
Define the concepts of your domain directly in the web browser, no need to generate code

ALT Define the concepts of your domain directly in the web browser, no need to generate code

A Sirius Web diagram defined in the web browser with our new View DSL

ALT A Sirius Web diagram defined in the web browser with our new View DSL

Charts are now available in our form representations

ALT Charts are now available in our form representations

Bar charts are also available, here you can see one in our new form descriptions WYSIWYG editor

ALT Bar charts are also available, here you can see one in our new form descriptions WYSIWYG editor

3
10
Maintaining a couple of npm packages but don't want / can't switch to a monorepo just yet? I wrote an article showing how you can use Yalc to try locally development versions of your npm libraries sbegaudeau.com/2022/05/05/ya…
3
Stéphane Bégaudeau retweeted
Axel RICHARD@_AxelRICHARD_5 Nov 2021
Hi! We recently talked about #Sirius integration in @code and @theia_ide with @sbegaudeau at @EclipseCon 2021. It's now available on youtube: youtube.com/watch?v=yvTk63ke…
6
5
Seven years later, time for a new generation
1
2
I just spent way too much time debugging my SQL query before I realized that I used a keyword as a variable name #MondayMorning
1
2
That moment when you change everything in your build and it works on the first try
1
4
and it’s broken again...
1
Stéphane Bégaudeau retweeted
Chadwick Boseman
@chadwickboseman29 Aug 2020
134,535
1,743,735
817,803
6,754,452
Without MDN, we may end up using w3schools...
Storybook 6.0 is here! 🥳 We retooled @storybookjs for professional devs: 💎 Zero config setup 🧬 Next-gen story format 🎛 Live edit components 🌐 Combine Storybooks 📚 Documentation overhaul 👉 medium.com/storybookjs/story…
21
310
32
959
Stéphane Bégaudeau retweeted
React
@reactjs10 Aug 2020
Today, we’re releasing the first Release Candidate for React 17! This release is rather unusual: it contains no new features. 👀 reactjs.org/blog/2020/08/10/…
The React 17 release is unusual because it doesn’t add any new developer-facing features. Instead, this release is primarily focused on making it easier to upgrade React itself. We’re actively working on the new React features, but they’re not a part of this release. The React 17 release is a key part of our strategy to roll them out without leaving anyone behind. In particular, React 17 is a “stepping stone” release that makes it safer to embed a tree managed by one version of React inside a tree managed by a different version of React.

ALT The React 17 release is unusual because it doesn’t add any new developer-facing features. Instead, this release is primarily focused on making it easier to upgrade React itself. We’re actively working on the new React features, but they’re not a part of this release. The React 17 release is a key part of our strategy to roll them out without leaving anyone behind. In particular, React 17 is a “stepping stone” release that makes it safer to embed a tree managed by one version of React inside a tree managed by a different version of React.

62
955
233
3,476
After having properly setup my SSH keys with SSH Agent and macOS Keychain a couple weeks ago, now I finally took some time to configure my GPG keys
1
That moment when you see a negative balance on your Google Cloud Platform account and you rush to add some additional money to compensate only to find out that a negative amount means that you already have too much money on it
2
First time playing for real with #Git interactive staging and it’s amazing. So many features and options easily accessible. I may have found my new favorite command
1
With the little one asleep, it was the perfect evening for a tabletop game. Today, Dice Forge with its expansion, Rebellion. It’s a great mix of luck and strategy 👍
1
VSCode finally integrated in #Github?
GitHub
@github6 May 2020
Introducing GitHub Codespaces, a complete dev environment within GitHub that lets you contribute immediately. You’ll be up and developing in less time than it takes to read this post. #GitHubSatellite
I need to write down even more documentation. After hours debugging #reactjs hooks interactions, I think it's good now. 4 useEffects, user interactions and WebSocket messages are working as expected. And all that with the help of state machines
Starting the day with a complex lifecycle issue involving #reactjs, some third party dependencies and of course my code 😝
1
1
more replies
One of my third-party dependencies is taking control of one of my div using useRef() as I am expecting it. It seems that this dependency is destroying and recreating this div and that React is keeping an old version in memory which is not in the parent div anymore...
1
Adding an intermediary div seems to fix the issue. My third-party dependency does not touch it and I can tell React to delete it without issue. React does not care that some content inside it was not under its control anymore. I'll have to write a lot of doc for that one div.
1
Load more