Johannes BrakensiekIn case you‘re interested in the state of #ObjGTK (which turns out to be my project for learning GObject), I’ve put some notes here: https://git.nil.im/ObjFW/discussions/issues/16#issuecomment-319
(At a later point I'm going to generate #ObjC bindings for #libpurple 3 using #ObjGTK and then use #ObjFW to integrate libpurple into #Adium. But I never said that, because probably it will never happen.)
Little bit sad I missed #FrosCon and the Phosh @ev meetup this year.
#Phosh was one of the reasons I started working on #ObjGTK four years ago. And so I‘m really happy this project became an indepedent association. Glad to further support it and I hope I may be able to meet people at a later point.
And: Also gives some motivation to get some more bits and pieces done on #ObjGTK.
#Phosh was one of the reasons I started working on #ObjGTK four years ago. And so I‘m really happy this project became an indepedent association. Glad to further support it and I hope I may be able to meet people at a later point.
And: Also gives some motivation to get some more bits and pieces done on #ObjGTK.
So the conclusion is: If I want to improve what I'm using, I need to get my hands dirty and learn to write and fix that kind of software written in #GObject #C.
I'm happy there is @objfw as well which makes facing C less of a pain.
#ObjGTK probably will never be "finished", but it already helps using #GTK without me needing to learn #Rust, which I won't be able to achieve in my spare hours.
Looks like being on vacation for almost two weeks now helps a little. I‘m gaining motivation again to resume programming and add #ObjGTK to @elementary at some point.
It's that time of the year again. Time to plan some #HappyHolidayHacking!
What do I wanna do?
1. Create a new plugin for #Foyer, our #Wordpress based #DigitalSignage solution.
2. Document the whole solution, since it's completely #FLOSS and very recommended to reproduce.
3. Create a #Hugo based front page for the #SynodIm app and a template for the @librechurch project site.
4. Fix memory management for the #ObjGTK generator.
What do I wanna do?
1. Create a new plugin for #Foyer, our #Wordpress based #DigitalSignage solution.
2. Document the whole solution, since it's completely #FLOSS and very recommended to reproduce.
3. Create a #Hugo based front page for the #SynodIm app and a template for the @librechurch project site.
4. Fix memory management for the #ObjGTK generator.
@tylerburton I‘m still working on #ObjGTK (your former #CoreGTK), hoping to implement #GObject instance/memory handling by the beginning of the next year. I only have very few time to work on it, but evolves steadily. 😉
@el_gaucho If you like to create/use the backend in C and #ObjC (use @objfw), then you will be able to use #ObjC for the frontend. Either using #AppKit #UIKit on Apple devices or using #ObjGTK on other Posix devices as soon as I manage to complete it. As long you may want to look at @vala_lang which provides C bindings for many #FLOSS libraries and more if you create VAPIs yourself.
Really need to get back to @elementary at some point. It‘s beauty is a huge motivation to work on @GTK and #ObjC, also because #ObjGTK just feels like it belongs there.
@gugurumbe It was the best idea for a free (libre) desktop environment. But it was ahead of his time (and maybe not done that well at its time), which is why people wrote #GNOME and that took over and #GNUstep got stuck. #GUI never reached a mature state, #Foundation is quite nice, but installs desktop stuff with its setup. The only stable runtime is #GNU, #libobjc2 has not got much support by the very little community.