# In Program "Check for Updates" **URL:** \ **Category:** Improvement Ideas\ **Created:** [March 29, 2025, 2:16pm UTC](https://librepcb.discourse.group/t/in-program-check-for-updates/916 "2025-03-29T14:16:03Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![kgcjr](https://yyz2.discourse-cdn.com/free1/user_avatar/librepcb.discourse.group/kgcjr/32/730_2.png) [@kgcjr](https://librepcb.discourse.group/u/kgcjr)\ **Post date:** [March 29, 2025, 2:16pm UTC](https://librepcb.discourse.group/t/in-program-check-for-updates/916/1 "2025-03-29T14:16:03Z")
Add a “Check for Program Updates” in the Help Menu, and/or have a pop-up window notification that there is a program/software update available for download. ---
**Author:** ![ubruhin](https://avatars.discourse-cdn.com/v4/letter/u/c89c15/32.png) [@ubruhin](https://librepcb.discourse.group/u/ubruhin)\ **Post date:** [March 29, 2025, 3:19pm UTC](https://librepcb.discourse.group/t/in-program-check-for-updates/916/2 "2025-03-29T15:19:10Z")
Yeah that was already suggested some time ago. I’m now considering to implement it in LibrePCB 2.0, depending on how it fits into the timeline. Thanks for the reminder 😉 ---
**Author:** ![kgcjr](https://yyz2.discourse-cdn.com/free1/user_avatar/librepcb.discourse.group/kgcjr/32/730_2.png) [@kgcjr](https://librepcb.discourse.group/u/kgcjr)\ **Post date:** [March 29, 2025, 5:31pm UTC](https://librepcb.discourse.group/t/in-program-check-for-updates/916/3 "2025-03-29T17:31:45Z")
No problem. When do you anticipate the 2.0 release? ---
**Author:** ![ubruhin](https://avatars.discourse-cdn.com/v4/letter/u/c89c15/32.png) [@ubruhin](https://librepcb.discourse.group/u/ubruhin)\ **Post date:** [March 29, 2025, 6:20pm UTC](https://librepcb.discourse.group/t/in-program-check-for-updates/916/4 "2025-03-29T18:20:38Z")
Oh that’s difficult to say, there’s a huge amount of tasks to do. Especially this one: > > > \_(this is a tracking issue about the progress of the new UI currently in develop…ment and will be updated regularly)\_ > > \# Goals > > The goals of the new UI, compared to the current UI: > > \- Less windows, suitable for both single-monitor and multi-monitor setups > - To be implemented with generic windows containing the different editors as tabs > \- Less modal dialogs & message boxes to avoid distracting the user > \- Efficient usage of screen space (e.g. not wasting lots of space with half-empty toolbars) > \- Dynamic, context-aware content (e.g. only show relevant information depending on state) > \- Responsive design (e.g. make content dependent on window size) > \- Intuitive design, with tooltips, hints etc. helping and guiding the user > \- Generally more modern look, with animations where appropriate > \- More efficient development workflow > \- Slowly moving away from C++ & Qt towards Rust > > See also the blog post \[NGI0 Grant for LibrePCB 2.0\](https://librepcb.org/blog/2024-10-17\_roadmap\_2.0/). > > \# Tasks in This Repository > > \- \[x\] https://github.com/LibrePCB/LibrePCB/pull/1495 > \- \[x\] https://github.com/LibrePCB/LibrePCB/pull/1500 > \- \[x\] https://github.com/LibrePCB/LibrePCB/pull/1499 > \- \[\] https://github.com/LibrePCB/LibrePCB/pull/1504 > \- \[\] Integrate AboutDialog into new Slint UI > \- \[\] Integrate LibraryManager into new Slint UI > \- \[\] Integrate SchematicEditor & BoardEditor into new Slint UI > \- \[\] Integrate OrderPcbDialog into new Slint UI > \- \[\] Integrate OutputJobsDialog into new Slint UI > \- \[\] Integrate LibraryEditor into new Slint UI > \- \[\] Integrate WorkspaceSettingsDialog into new Slint UI > > \# Tasks in Other Repositories > > \- \[x\] https://github.com/LibrePCB/docker-librepcb-dev/pull/57 > \- \[x\] https://github.com/LibrePCB/docker-librepcb-dev/pull/58 > \- \[x\] https://github.com/LibrePCB/docker-librepcb-dev/pull/61 > \- \[x\] https://github.com/LibrePCB/docker-librepcb-dev/pull/62 > > \# Issues to be Solved or Improved > > Note that not all issues are expected to be fully solved in LibrePCB 2.0, some might be completed in a later release. > > \- Solved By Design / Not Relevant Anymore > - \[\] https://github.com/LibrePCB/LibrePCB/issues/36 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/53 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1050 > \- Problems of Current UI, Not Relevant Anymore or Easy to Fix > - \[\] https://github.com/LibrePCB/LibrePCB/issues/903 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/942 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1232 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1371 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1372 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1417 > \- To Be Considered / Reviewed > - \[\] https://github.com/LibrePCB/LibrePCB/issues/359 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/726 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/815 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/915 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1053 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1231 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1258 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1362 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1367 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1424 > \- To be Implemented For Sure > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1051 > \- To be Implemented Sooner or Later > - \[\] https://github.com/LibrePCB/LibrePCB/issues/646 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1045 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1254 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1332 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1354 > - \[\] https://github.com/LibrePCB/LibrePCB/issues/1370 > > \# Related External Issues > > \- \[\] https://github.com/slint-ui/slint/issues/3715 > \- \[\] https://github.com/slint-ui/slint/issues/2723 Generally the plan is to finish it until October, but considering the huge amount of work it may take a few months longer.