In 4.2 I'm trying to create a new package and simply save it. However, CodePackage>>writeFeatureSpec: throws a MNU on featureSpec provides (featureSpec is null)... is there a different workflow to creating new packages in 4.2 than simply clicking the 'Create Package' button to get things properly set up? Thanks, Phil _______________________________________________ Cuis mailing list [hidden email] http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org |
Hi Phil: I can't reproduce the problem. Could you comment the exact steps that you follow?
2013/9/30 Phil (list) <[hidden email]>
Saludos / Regards,
Germán Arduino www.arduinosoftware.com _______________________________________________ Cuis mailing list [hidden email] http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org |
On Sep 30, 2013, at 7:39 PM, Germán Arduino wrote:
> Hi Phil: > > I can't reproduce the problem. > > Could you comment the exact steps that you follow? > Not a problem: 1) Open Cuis4.2-1766.image 2) World menu->Open...->Installed Packages (the last two steps are in the package browser) 3) Click 'Create Package' button enter name 4) Click 'Save (overwrite) 5) MNU with nil featureSpec every time I've tried it... Thanks, Phil _______________________________________________ Cuis mailing list [hidden email] http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org |
I am not in the computer now but try with a new image, 1836 currently.
Cheers. El martes, 1 de octubre de 2013, Phil (list) <[hidden email]> escribió: > On Sep 30, 2013, at 7:39 PM, Germán Arduino wrote: > >> Hi Phil: >> >> I can't reproduce the problem. >> >> Could you comment the exact steps that you follow? >> > > Not a problem: > > 1) Open Cuis4.2-1766.image > (the last two steps are in the package browser) > 3) Click 'Create Package' button enter name > 4) Click 'Save (overwrite) > 5) MNU with nil featureSpec every time I've tried it... > > Thanks, > Phil > _______________________________________________ > Cuis mailing list > [hidden email] > http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org > -- Saludos / Regards, Germán Arduino www.arduinosoftware.com _______________________________________________ Cuis mailing list [hidden email] http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org |
1836 does not have this issue. That's what I get for going with stable :-)
Thanks, Phil On Sep 30, 2013, at 9:10 PM, Germán Arduino wrote: I am not in the computer now but try with a new image, 1836 currently. _______________________________________________ Cuis mailing list [hidden email] http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org |
Hi Phil,
On 9/30/2013 10:41 PM, Phil (list) wrote: 1836 does not have this issue. That's what I get for going with stable :-) This kind of issues would be better handling by maintaining 2 branches at the same time (like, a Cuis 4.2 branch that only get bug fixes and a 4.3 alpha branch with deeper/riskier changes, and those breaking compatibility). But Cuis is too small (in users, developers, and resources) to afford to do that. Apologies. On the other hand, we are not doing deep or risky changes, and usually the very latest version is as reliable as any other. (A simpler system is less risky to change) So, the only reason I see to stay with the stable release, would be if you plan to do a development of significant size, and you need the system APIs to be really frozen. BTW, if anybody is doing that, maybe you also have a few hours you could donate to the project from time to time, and we could join efforts to actually start publishing bug fixes for stable releases. Cheers, Juan Vuletich
_______________________________________________ Cuis mailing list [hidden email] http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org |
Juan,
On Oct 1, 2013, at 7:57 AM, Juan Vuletich wrote: > Hi Phil, > > On 9/30/2013 10:41 PM, Phil (list) wrote: >> >> 1836 does not have this issue. That's what I get for going with stable :-) >> >> Thanks, >> Phil > > This kind of issues would be better handling by maintaining 2 branches at the same time (like, a Cuis 4.2 branch that only get bug fixes and a 4.3 alpha branch with deeper/riskier changes, and those breaking compatibility). But Cuis is too small (in users, developers, and resources) to afford to do that. Apologies. > Not a problem... I'd rather have the priority be putting all effort in the dev branch to get to the next stable than duplicating effort by backporting bug fixes. In the future I just need to remember to check any bugs against the latest dev version and make sure I report the bug in stable as fixed in dev so everyone knows that there is an outstanding issue. > On the other hand, we are not doing deep or risky changes, and usually the very latest version is as reliable as any other. (A simpler system is less risky to change) So, the only reason I see to stay with the stable release, would be if you plan to do a development of significant size, and you need the system APIs to be really frozen. > That's exactly why I started with stable: I want reasonably fixed APIs. I've got a medium-ish sized code base that I'd prefer to not migrate more than about every 12 months or so. The last time I migrated it was for 4.0 so it's time. The good news is that since Cuis has already taken out most of the cruft, any breakage is usually not that big of a deal to fix (i.e. my question about ellipse drawing not too long ago, for example). I just didn't think to check against dev when I ran into this issue mainly because I saw all the discussion re: dependency work and thought something might have changed that I just wasn't aware of. > BTW, if anybody is doing that, maybe you also have a few hours you could donate to the project from time to time, and we could join efforts to actually start publishing bug fixes for stable releases. > > Cheers, > Juan Vuletich Thanks, Phil _______________________________________________ Cuis mailing list [hidden email] http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org |
Free forum by Nabble | Edit this page |