Hi, Because I was mentioned. I did not "fork" h2. At least not in my mind ;-) I made contribution: refactoring , fixes, improvements. Soon this will me merged to mainline. As you see ( or not ) I also revised bug tracker list - add some labels, some longterm issues was even closed after all. My changes around engine are not so big. I have my small list of features that I want to implement , but this will be done IN h2 ( not from the side ) - and for each feature I'll create "ticket" for self on github soon. OFC my first pull request is one big patch and I understand resistance for implementing it, but in future my changes will be more precise, because I achieved some level of stability ( i.e. fixed bugs that stopped me from using h2 on stage ).
One of h2 advantages for me is stability/maturity. I see no any reason for revolution. Of course there is a lot to do - there is a lot of code to just sort out, but this could be done without rewriting logic. To summarize things .. I feel about my role here as regular devel / contributor. As Jacob said, he tried to "revitalize" entire app. IMHO will be much better for entire community ( mostly for users ) if Jacob can improve GUI code but in H2 scope. As I understand no one here actively develop QT code. And if we talking about coding style / cleaning mess .. I think we all want same thing here ! ... and there is also this idea from Thijs about new site for contributors For me - if this is acceptable - Jacob should try to work in H2 scope - even if this sometimes slow down he's work - there is huge benefit for community to have just one hydrogen. It's only my two cents here ;-) After all if Jacob just can't work with us - and he want/need/must rewrite this app - then his project should not share "hydrogen" name. This will be misleading for regular users and distro packages ( mean - two apps Hydrogen / HydrogenFusion in same repo. Possible - but insane ;-). P. Dnia Piątek, 3 Stycznia 2014 17:12 Sebastian Moors <[email protected]> napisał(a) > Hi Jacob, > > wolke did already a very nice summary of the current state of hydrogen. > But there is one point i would like to add: There's is currently another > interesting fork (from Pawel) who works a lot on the transport and > audio-core related stuff in his github repository. I think it would be > great if we could combine your efforts. I don't have any problems with a > fork, but i guess it won't be optimal for the users if there is one fork > of hydrogen with a nice audio backend and one fork of hydrogen with a > nice user interface :) Most of the changes that you've made make sense > to me and it would be great to see them somehow in combination with the > changes made by Pawel. As wolke i'm not so sure about the change to > qmake, but that's just my private opinion. It seems that every developer > has his own favorite build system :) As a matter of fact, we already had > two build systems in parallel for a while in the past (qmake for > windows, scons for linux/mac os x). > > Do you plan any conceptual changes in the future which would make it > impossible to merge your work with the hydrogen main repository? > > Best regards, > Sebastian > > > Jacob Dawid wrote: > > Hello everyone, > > > > I just wanted to say hello to the Hydrogen devs, as the IRC channel on > > FreeNode seemed to be empty. > > > > I have forked Hydrogen on github and refactored a lot of code. As I > > have seen that all Qt widgets are based on pixmaps, I started to > > refactor code. Since I made some radical changes, like switching over to > > qmake, rebuilding the widgets with Qt standard widgets and made all > > windows dockable, I thought about using a different name than "Hydrogen" > > (derivative work). > > > > Since I also want to maintain compatibility with Hydrogen (especially > > the Hydrogen file format), I thought about calling it "Hydrogen Fusion". > > If there are any objections to that from your side, I can also choose a > > completely different name. > > > > Happy hacking > > Jacob > > > > ------------------------------------------------------------------------------ > > Rapidly troubleshoot problems before they affect your business. Most IT > > organizations don't have a clear picture of how application performance > > affects their revenue. With AppDynamics, you get 100% visibility into your > > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics > > Pro! > > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > > _______________________________________________ > > Hydrogen-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/hydrogen-devel > > > ------------------------------------------------------------------------------ > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application performance > affects their revenue. With AppDynamics, you get 100% visibility into your > Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > _______________________________________________ > Hydrogen-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/hydrogen-devel ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
