Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Perhaps a bit premature since 1.06 isn't oficially released, but I'm sure some have worked with the beta and have some insight on what the implications of 1.06 are on those who are currently using ffp 0.5.
I love the capabilities ffp 0.5 provide and want to have a smooth transition to FW 1.06 (for its enhancements and bug fixes) while retaining the functionality ffp 0.5 provides.
Is it worthwile to start a thread that provides guidance to those ffp users who are embarking on a 1.06 firmware upgrade? Pitfalls, how to's, lessons learned, comments. I'm just thinking ahead as I intend to upgrade if 1.06 is solid and will need to consider how to do it properly.
Offline
One of the conditions on which beta software is made available to beta testers is non disclosure.
Offline
Good point! ... Perhaps we can continue this topic when 1.06 is released. Hopefully very soon.
Offline
IANAL but I read the confidentiality agreement with my beta testing email -- it seemed pretty reasonable and boilerplate. It explicits prohibits dissassembling or distribution/transfer etc. of the software or of confidential information. In fact, it seems less restrictive by far than the commercial Microsoft shrinkware.
From my layman's reading, I think it would be a stretch to interpret it as forbidding people from revealing their own personal experiences with the software. Plus the change list itself has been released publicly.
I don't see any problem with saying things like: "funplug works/doesn't work with it." or "big improvement" or "still has too many kinks" or "creates incompatibility with 3rd party program xyz"
After all, we are all just trying to help each other here.
Offline
well.. since the original firmware war released under the GPL and newer version are based on the original one it would be illegal not to publish the sourcecode as well.
so, if giving the betaversion to selected betatesters qualifies as publishing, the sourcecode has to be published as well.
Offline