Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Friction 1.0.0 Roadmap #142

Open
2 of 4 tasks
rodlie opened this issue May 4, 2024 · 36 comments
Open
2 of 4 tasks

Friction 1.0.0 Roadmap #142

rodlie opened this issue May 4, 2024 · 36 comments
Assignees

Comments

@rodlie
Copy link
Member

rodlie commented May 4, 2024

This issue tracks the progress of v1.0.0.

  • Beta 1 - 16 October (core feature freeze)
  • Beta 2 - 2 December (functional feature freeze)
  • Release Candidate - Early December
  • Release - Mid to late December
@rodlie rodlie added this to the 1.0.0 milestone May 4, 2024
@rodlie rodlie self-assigned this May 4, 2024
@rodlie rodlie pinned this issue May 4, 2024
@rodlie rodlie changed the title Friction 1.0.0 Roadmap Friction 1.0.0 roadmap May 4, 2024
@rodlie rodlie changed the title Friction 1.0.0 roadmap Friction 1.0.0 Roadmap Jul 1, 2024
@rodlie
Copy link
Member Author

rodlie commented Jul 22, 2024

Will do a beta release shortly after the release of 0.9.6.1 (#202), probably this weekend.

@rodlie
Copy link
Member Author

rodlie commented Aug 12, 2024

And... I missed the deadline again.

Anyway, the plan now is to release v0.9.6.1 on Friday and v1.0.0-beta1 on Sunday.

Note that anything may happen, but this is my goal for the week.

Todo for the week

  • Try to finish the HiDPI changes in v1 I started a couple of days ago
  • Get working Linux CI that produces downloadable v1 builds (already added for Windows)
  • Theme adjustments for v1
  • Update release notes for v1 with new features (screenshots/videos)
  • Produce release builds for v0.9.6.1

End the week with v1.0.0-beta1 release.

@eFe-Munoz
Copy link

That's good news!

@rodlie
Copy link
Member Author

rodlie commented Aug 16, 2024

So, timeline for release(s) will look something like this:

  • Release v1.0.0-beta1 (ETA a couple of days after v0.9.6.1 release)
  • Release v1.0.0-beta2 (ETA Early September)
    • If we have important fixes that also apply to the v0.9 branch do a v0.9.6.2 release with backports
  • Release v1.0.0-rc1 (ETA Late September/Early October)
    • If we have important fixes that also apply to the v0.9 branch do a v0.9.6.3 release with backports
  • Release v1.0.0-rc2 if needed
  • Release v1.0.0 (ETA Late October/Early November)

"best-case scenario™" 😄

I will try to release v0.9.6.1 today, but I might just do a quick RC1 and do the final release on Sunday. Don't know yet.

@eFe-Munoz
Copy link

Great news!

@eugenialoli
Copy link

Love it, hope you also include a light theme, because I have an eye condition that i can't read well in dark backgrounds. Also, it would be useful to also create a flatpak (and maybe a snap) for the beta version, because that's how you're going to get exposure and people will be able to find bugs to be fixed for the final 1.0 version. Flatpak is where it's at these days for exposure... plus maybe the phoronix website.

@rodlie
Copy link
Member Author

rodlie commented Sep 7, 2024

Hi Eugenia

hope you also include a light theme

Not for v1. It's hard enough to maintain one theme across platforms. But this is something I can look at in a later release (1.1/1.2).

create a flatpak

To be honest I don't care about all the packaging formats out there. I produce one quality binary bundle that work on anything, that's my priority. I also only support the release binaries. Custom builds, distro builds etc are not supported (for obvious reasons).

It's however simple for someone to repack the release binaries into a flatpak, so if anyone want's to maintain the flathub script let me known and we will make it official.

how you're going to get exposure

Yeah, not my highest priority. I could generate a lot more attention and exposure if I wanted to, but that will just generate more "noise". The more users the more work for me.

At the end of the day this is a tool I and others use at work, nothing else. I only maintain it in that context, in my spare time.

This project has the potential to go places, but then I would have to work full-time on this project, and I don't work for free ;)

I may sound a bit negative, this is not my intent :)

@eFe-Munoz
Copy link

Greetings.

Do you know the release date of BETA 1.0?

@rodlie
Copy link
Member Author

rodlie commented Sep 30, 2024

So, we are now in a feature freeze, any feature requests or features in development will be pushed to next release (v1.1).

I will use a couple of days to iron out any issues introduced and clean up remaining UI/UX stuff then do a beta release. I aim to do a final release by the end of October.

After release of the beta I will try to resolve some of the open bug issues we have.


We have functional CI for both Windows and Linux, so anyone can test the main branch, no need to wait on a release.

Select a commit, scroll down and download zip file.

I have also created simplified url's:

@eFe-Munoz
Copy link

eFe-Munoz commented Sep 30, 2024

Good news.

Is there a portable version?

Do you need a performance report?

@rodlie
Copy link
Member Author

rodlie commented Sep 30, 2024

The snapshots includes portable and installer, note that the portable is actually portable now, settings etc are contained in the folder you run Friction from.

I don't need any reports yet, I will concentrate on finishing UI stuff and make sure the new stuff works "good enough", also need to write release notes, docs etc.

@eFe-Munoz
Copy link

The Timeline and the effects menu look great.
Just a question, has the UI scaling disappeared in the configuration? On large monitor (like mine) the icons look tiny.

@rodlie
Copy link
Member Author

rodlie commented Sep 30, 2024

has the UI scaling disappeared in the configuration? On large monitor (like mine) the icons look tiny.

Ahh, yes. I improved hdpi on Windows and the setting didn't seem to fix/do anything on my setup, so I disabled it. But if it's not the case I will figure out something else.

What resolution are you using and are you using display scaling (if so how much)? A screenshot could also help.

@eFe-Munoz
Copy link

eFe-Munoz commented Sep 30, 2024

I see it smaller than the screenshot because my screen resolution is higher than 72 pp (standard), I think it is around 150 pp approx.

This is how I see it now (beta 1):
imagen

And this is how I see it in version 0.9.6.1 at 150%:
imagen

@rodlie
Copy link
Member Author

rodlie commented Sep 30, 2024

you set Friction 0.9 to 150% or the display?

@eFe-Munoz
Copy link

Yes, because the resolution of my monitor is about 150 dpi, not 72 dpi (as they usually are) and that makes everything smaller.

@rodlie
Copy link
Member Author

rodlie commented Sep 30, 2024

Ok, try this build when done (will take ~13min to build): https://github.com/friction2d/friction/actions/runs/11105014852
Screenshot from 2024-09-30 13-33-23

Didn't have the time to test on Windows, but should bring back scaling override.

@eFe-Munoz
Copy link

Hi, I have installed the version, I rescale UI to 150% it tells me to reboot and when I reboot it keeps scaling to 100%.

@rodlie
Copy link
Member Author

rodlie commented Oct 1, 2024

Works fine on my setup (Win11 laptop with 1920x1080).

Windows Scaling 100% - Friction Scaling Auto

friction1-win11-display-100-friction-auto

Windows Scaling 100% - Friction Scaling 150%

friction1-win11-display-100-friction-150

Windows Scaling 125% - Friction Scaling Auto

friction1-win11-display-125-friction-auto

Windows Scaling 150% - Friction Scaling Auto

friction1-win11-display-150-friction-auto


Everything looks as expected.

@rodlie
Copy link
Member Author

rodlie commented Oct 1, 2024

Also tested on my Windows 10 workstation using a ProArt 27" 4k, works fine there as well. Some icons with Windows scaling set to 200% on 4k look a bit stretched, but there are limits to what I care to support/test.

Setting scaling in Friction also works fine here.

Windows 100% - Friction 150%

friction1-win10-windows-100-friction-150-proart24-4k

@eFe-Munoz
Copy link

ok I must have the wrong version.

imagen

@rodlie
Copy link
Member Author

rodlie commented Oct 2, 2024

9f3055eb is the correct version (or newer). The warning you get is because something is wrong with the dpi, what is the requested icon size in the warning?

Requested icon size X is not available

@eFe-Munoz
Copy link

I downloaded and installed that version and scaling the UI still doesn't change anything. Neither the reboot.

imagen

imagen

@rodlie
Copy link
Member Author

rodlie commented Oct 3, 2024

Not able to replicate.

@eFe-Munoz
Copy link

Ok, I got it! the secret was that “Auto” was active and the changes did not take effect. Everything is fine now.

imagen

imagen

@rodlie
Copy link
Member Author

rodlie commented Oct 3, 2024

Good 👍

I was supposed to ask you about that yesterday, but forgot.

@rodlie
Copy link
Member Author

rodlie commented Oct 3, 2024

Should probably disable the slider if auto is enabled, will add it later today.

@eFe-Munoz
Copy link

Maybe, yes.

@rodlie
Copy link
Member Author

rodlie commented Oct 3, 2024

Done, slider is disabled if 'auto'.

@rodlie rodlie removed this from the 1.0.0 milestone Oct 5, 2024
@rodlie
Copy link
Member Author

rodlie commented Oct 8, 2024

Blocker before release: friction2d/skia#1 (so I don't forget).

@rodlie
Copy link
Member Author

rodlie commented Oct 15, 2024

Will try to release v1.0 beta tomorrow, depends on how my internal testing goes today (win 10/11, intel/nvidia, linux rpm/portable/appimage etc). Been using v1.0/main at work for a couple of weeks now.

Also need to write release notes, unsure if I'm able to finish them today, a lot of changes has happened and I'm not even sure I remember all of them. Worst case the release notes will be very simplified compare to final.

@eFe-Munoz
Copy link

eFe-Munoz commented Oct 16, 2024

Ok, here's an example.

I import an image and I want to align and animate it according to its base. But when I create an object or import a file its default axis is in the center (example image):
imagen

It would be great if in the alienation options you could alienate the pivot with respect to the dimensions of the object/image. For example, add an “object-related” option. This way you could easily place the axis of an object/image on the base in the center without having to do it by hand and not very precisely.
imagen
It would thus be aligned at the bottom center. Other times it is necessary to align top right or center left...
imagen

@rodlie
Copy link
Member Author

rodlie commented Oct 25, 2024

Did some updates to the release schedule (see first post). Expect a beta 2 release by the end of next week. Then RC(s) and final release in November.

We are generally in good shape, but I want some extra time for testing/QA etc.

@eFe-Munoz
Copy link

Very much looking forward...

@rodlie
Copy link
Member Author

rodlie commented Nov 25, 2024

Delays, delays, delays ... 😄

Ok, Beta 2 is now scheduled for Saturday (30 November).

This will be a hard feature freeze, whatever feature is not done by Friday will not be part of v1.0.x.

@eFe-Munoz
Copy link

Let's go!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants