-
Notifications
You must be signed in to change notification settings - Fork 81
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
Will this project be affected by AGS v2(Astal) #456
Comments
Once AGS v2 releases this project will be transitioning to it. |
FYI Astal is a library so you don't have to rely on AGS anymore, you could already start the migration process. |
That makes sense, thank you for the clarification. I'll probably start the migration process soon; appreciate it Aylur. |
@Jas-SinghFSU I would love to help in the transition given we make a milestone with tasks. Then anyone interested can take a task and migrate the codebase to astal. We can start out with a next branch I also think we should halt the bigger fixes and completely stop new features until the migration otherwise we would have to work twice |
@Aylur is there a performance gain of any sorts from the current implementation. I was mostly interested in this. |
Its negligible amount if there is any. We are still just calling into C code, spidermonkey (gjs) is very well optimized so you shouldn't be worrying about it. Only real difference between a gjs+gtk and a vala/c+gtk project is just some extra memory gjs allocates to do its thing, performance difference won't be noticeable. |
It will be great to have this be bundled in the AUR. |
I totally forgot missed this until this thread just got pinged to me due to a new message. Sorry about that. I haven't had a chance to make milestones since between work and life I have only had brief pockets of time so I've just used those to migrate as much as I can. Hopefully in the future I get a chance to make it more collaborative and get some time to set up some milestones. |
Hi, as the title suggests, I would like to know if this project will be affected by this upcoming merge in AGS, and possibly how.
Aylur/ags#504
The text was updated successfully, but these errors were encountered: