TomasT Posted March 12, 2009 Report Share Posted March 12, 2009 Hi all, In the process of fixing known issues and improving the product towards its release, our development team may be required to perform breaking changes to the product Quote Link to comment Share on other sites More sharing options...
EinsteinTech Posted March 13, 2009 Report Share Posted March 13, 2009 Nice guys finish last, Tomas. It's a beta so I say do whatever you have to do to make the product as good as it can be when it is released. It would be a shame to see a v1 product burdened with the cross of backwards compatibility with a beta. Perhaps if I can offer a suggestion regarding re-creating extensively configured web parts... Maybe you can provide an option to configure the web part with some external XML files, or at least XML that could be entered into the web part properties pane. That would make it easier for users in the future to move their customizations between staging and production environments and make it easier to deal with changes to the interface. Kinda like how PowerGadgets can be customized with .pgt files. Quote Link to comment Share on other sites More sharing options...
CPdev Posted March 17, 2009 Report Share Posted March 17, 2009 Hi, As we now this product is a beta version, we must remind that the product may change radically. But we participate in this change ! Also, introduce as many changes as you need to give us the best product (as others from softwareFX ;-) ) After that, we have the knowledge of the product and the portability of our apps may be done quickly (we hope) Pierre for CPDev Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.