"I think the mod scene should exist to be a counterpoint to the official, stock firmware, that's almost always a piece of sh**. Considering this, I really think everybody should have the right to use anybody's piece of code that's released to the same scope. If HyperX did not cridt Marco for his work at first, this is wrong, but it was corrected afterwards. So, in my opinion, Marco is a crying baby, who wants to be more importante than he really is. Don't take me wrong: He IS important, but not to that extent. Go ahead, credit him and release something that many others would benefit from!! HyperX and Marco: Thanks for your amazing work so far! Cheers! Lino"
I second that!
Lino - 1 year ago
I think the mod scene should exist to be a counterpoint to the official, stock firmware, that's almost always a piece of sh**.
Considering this, I really think everybody should have the right to use anybody's piece of code that's released to the same scope.
If HyperX did not cridt Marco for his work at first, this is wrong, but it was corrected afterwards.
So, in my opinion, Marco is a crying baby, who wants to be more importante than he really is. Don't take me wrong: He IS important, but not to that extent.
Go ahead, credit him and release something that many others would benefit from!!
HyperX and Marco: Thanks for your amazing work so far!
Cheers!
Lino
jRoy - 1 year ago
Marco has every right to be upset for his dll(s) were renamed but he should also understand that its still his work that is being used and the community (I am sure) is greatful for that. It may not have been clear at the start but by the mention in the change log and this poll sure makes it clear that he had an important contribution to make to this project. We are all very thankful to you all for putting in time and effort to make our phones loveable and we'll continue to use your software with gratitude (and contributions :) ).
So with the start of the festive season, lets all be happy to have earch others support and start collaborating on marvels that we amaze ourselves and the community with. After all, according to the Mayans, we've got 2 more years to enjoy this world before it returns to dust :P
Mike Horne - 1 year ago
I chose the YES option, but mostly because I know how annoyed people can get and how protective they can be. However, with negotiation between the parties, I'm sure some compromise can be reached. If not, perhaps we (the user community) can just live with the normal version of RomPatcher?
Simon - 1 year ago
text formatting is a pain here! :(
Check the latest emails: http://localhostr.com/files/GtCL4XL/emails.zip
Simon - 1 year ago
But as far as I understood it has been modded only to use different names, to avoid conflicts with the original RP files.
The text below is pasted from the latest emails and it seems that they found an agreement.
Yes basically it is for the names that you choosed and the people could think that those components have been developed by you as part of your software.
So, if it is easier for you to rename them, you can apply the changes below and everybody will be happy:
-for autostart: use RomPatcherAuto2.exe or RomPatcherA.exe in case the first is too long
-for dll: use RomPatcherEngine2.dll or RomPatcherE.dll in case the first is too long
-for patches folder: use c:\patche2\
-for RPPlus.dat: use RPPlu2.dat
So there will be no conflicts with original RP+
Let me know if those names are ok, or if are still too long.
Marco.
Paul - 1 year ago
The HX-V10-Final-1-0 isn't renamed only,this is a modded dll.
Simon - 1 year ago
The RomPatcherEngine.dll has been renamed in HX-V10-Final-1-0.dll...
But help me to understand another thing, in the latest email marco gived hyperx the right to use the dll, hyperx just have to choose a name similar to the RomPatcherEngine.dll so why it's happening all this mess???
Paul - 1 year ago
yust a' moment,i can found one dll in RomPatcher.
RomPatcherEngine.dll
You write on your Page.
We have renamed some dll dependencies that are normaly used by the app Rompatcher itself.
Which dll's you mean ???
"I think the mod scene should exist to be a counterpoint to the official, stock firmware, that's almost always a piece of sh**. Considering this, I really think everybody should have the right to use anybody's piece of code that's released to the same scope. If HyperX did not cridt Marco for his work at first, this is wrong, but it was corrected afterwards. So, in my opinion, Marco is a crying baby, who wants to be more importante than he really is. Don't take me wrong: He IS important, but not to that extent. Go ahead, credit him and release something that many others would benefit from!! HyperX and Marco: Thanks for your amazing work so far! Cheers! Lino"
I second that!
I think the mod scene should exist to be a counterpoint to the official, stock firmware, that's almost always a piece of sh**.
Considering this, I really think everybody should have the right to use anybody's piece of code that's released to the same scope.
If HyperX did not cridt Marco for his work at first, this is wrong, but it was corrected afterwards.
So, in my opinion, Marco is a crying baby, who wants to be more importante than he really is. Don't take me wrong: He IS important, but not to that extent.
Go ahead, credit him and release something that many others would benefit from!!
HyperX and Marco: Thanks for your amazing work so far!
Cheers!
Lino
Marco has every right to be upset for his dll(s) were renamed but he should also understand that its still his work that is being used and the community (I am sure) is greatful for that. It may not have been clear at the start but by the mention in the change log and this poll sure makes it clear that he had an important contribution to make to this project. We are all very thankful to you all for putting in time and effort to make our phones loveable and we'll continue to use your software with gratitude (and contributions :) ).
So with the start of the festive season, lets all be happy to have earch others support and start collaborating on marvels that we amaze ourselves and the community with. After all, according to the Mayans, we've got 2 more years to enjoy this world before it returns to dust :P
I chose the YES option, but mostly because I know how annoyed people can get and how protective they can be. However, with negotiation between the parties, I'm sure some compromise can be reached. If not, perhaps we (the user community) can just live with the normal version of RomPatcher?
text formatting is a pain here! :(
Check the latest emails: http://localhostr.com/files/GtCL4XL/emails.zip
But as far as I understood it has been modded only to use different names, to avoid conflicts with the original RP files.
The text below is pasted from the latest emails and it seems that they found an agreement.
Yes basically it is for the names that you choosed and the people could think that those components have been developed by you as part of your software.
So, if it is easier for you to rename them, you can apply the changes below and everybody will be happy:
-for autostart: use RomPatcherAuto2.exe or RomPatcherA.exe in case the first is too long
-for dll: use RomPatcherEngine2.dll or RomPatcherE.dll in case the first is too long
-for patches folder: use c:\patche2\
-for RPPlus.dat: use RPPlu2.dat
So there will be no conflicts with original RP+
Let me know if those names are ok, or if are still too long.
Marco.
The HX-V10-Final-1-0 isn't renamed only,this is a modded dll.
The RomPatcherEngine.dll has been renamed in HX-V10-Final-1-0.dll...
But help me to understand another thing, in the latest email marco gived hyperx the right to use the dll, hyperx just have to choose a name similar to the RomPatcherEngine.dll so why it's happening all this mess???
yust a' moment,i can found one dll in RomPatcher.
RomPatcherEngine.dll
You write on your Page.
We have renamed some dll dependencies that are normaly used by the app Rompatcher itself.
Which dll's you mean ???