- Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects - How do you save changes without committing? After adding a dependent project to the baseline, "Update de" (sic, label cut-off) doesn't seem to do anything. Clicking away from the baseline warns me of losing changes but doesn't offer the opportunity to save. - If I select a project in Versionner, and then click the "New prone" button, the title of the window that pops is the name of the previously selected project, not the newly-created one. Where will the changes actually go? i.e. is it just a labeling error, or am I editing the wrong project? - I reported before, but Versionner needs a standard repositoryChooser that allows to select from known repos or create a new one from a template ( like MC Browser, but hopefully better ;) ) This tool is so important. Thanks for all the work :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Strange-Versionner-behavior-tp4736758.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Sean P. DeNigris wrote
- Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects
Okay, I see that a baseline and version have been created with sample data. I thought Versionner was in a more usable state⦠I will be patient :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Strange-Versionner-behavior-tp4736758p4736763.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Am 14.01.2014 um 20:31 schrieb Sean P. DeNigris <sean@clipperadams.com>:
Sean P. DeNigris wrote
- Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects
Okay, I see that a baseline and version have been created with sample data. I thought Versionner was in a more usable state⦠I will be patient :)
I was asking myself the same. I used it in 2.0 for months but in 3.0 it doesnât seem to work. Norbert
Hi Norbert, Le 15 janv. 2014 à 00:38, Norbert Hartl a écrit :
Am 14.01.2014 um 20:31 schrieb Sean P. DeNigris <sean@clipperadams.com>:
Sean P. DeNigris wrote
- Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects
Okay, I see that a baseline and version have been created with sample data. I thought Versionner was in a more usable state⦠I will be patient :)
I was asking myself the same. I used it in 2.0 for months but in 3.0 it doesnât seem to work.
I need user feedback so I will be happy to know what does not work for you. Regards, Christophe.
Hi Sean, Le 14 janv. 2014 à 20:31, Sean P. DeNigris a écrit :
Sean P. DeNigris wrote
- Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects
Okay, I see that a baseline and version have been created with sample data.
It is a side effect of this slice: https://pharo.fogbugz.com/f/cases/10578 It is not related to Versionner. Metacello ToolBox uses this template to create new configurations. It is wrong to add examples in this class. I will propose a fix.
I thought Versionner was in a more usable state⦠I will be patient :)
You and I pay the price that Pharo3.0 evolves fast. Versionner is a high level tool and is dependent on tools with a lot of updates (spec, komitter, metacello, etc). To focus on Versionner, I do not have a lot of users and I need users to improve it. :) That said, thank you for being a beta-tester ;) Cheers, Christophe.
Le 14 janv. 2014 à 20:12, Sean P. DeNigris a écrit :
- Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects
answered in a previous mail
- How do you save changes without committing? After adding a dependent project to the baseline, "Update de" (sic, label cut-off)
It works fine on my laptop. Can you send me a screenshot?
doesn't seem to do anything.
It should. It is the way to save changes. Maybe I should rename the button to "Save Changes" and just keep the "release" and "commit" buttons aside.
Clicking away from the baseline warns me of losing changes but doesn't offer the opportunity to save. - If I select a project in Versionner, and then click the "New prone" button, the title of the window that pops is the name of the previously selected project, not the newly-created one. Where will the changes actually go? i.e. is it just a labeling error, or am I editing the wrong project? - I reported before, but Versionner needs a standard repositoryChooser that allows to select from known repos or create a new one from a template ( like MC Browser, but hopefully better ;) )
It looks like a Spec problem. It worked well some days ago. I will investigate. Thanks, Christophe
Le 15 janv. 2014 à 10:54, Christophe Demarey a écrit :
Le 14 janv. 2014 à 20:12, Sean P. DeNigris a écrit :
- Creating a new configuration adds fileSystemLegacy and fuelMetalevel as dependent projects
answered in a previous mail
- How do you save changes without committing? After adding a dependent project to the baseline, "Update de" (sic, label cut-off)
It works fine on my laptop. Can you send me a screenshot?
doesn't seem to do anything.
It should. It is the way to save changes. Maybe I should rename the button to "Save Changes" and just keep the "release" and "commit" buttons aside.
Clicking away from the baseline warns me of losing changes but doesn't offer the opportunity to save. - If I select a project in Versionner, and then click the "New prone" button, the title of the window that pops is the name of the previously selected project, not the newly-created one. Where will the changes actually go? i.e. is it just a labeling error, or am I editing the wrong project?
It looks like a Spec problem. It worked well some days ago. I will investigate.
I forgot to answer this one:
- I reported before, but Versionner needs a standard repositoryChooser that allows to select from known repos or create a new one from a template ( like MC Browser, but hopefully better ;) )
I planned to do that friday. I extracted the repository chooser from Komitter to share it with Versionner.
On Jan 15, 2014, at 5:51 AM, Christophe Demarey [via Smalltalk] <ml-node+s1294792n4736853h31@n4.nabble.com> wrote:
I forgot to answer this one:
- I reported before, but Versionner needs a standard repositoryChooser that allows to select from known repos or create a new one from a template ( like MC Browser, but hopefully better ;) )
I planned to do that friday. I extracted the repository chooser from Komitter to share it with Versionner.
Great! One place it's needed is when specifying the repository of a dependent project. For example, I loaded BabyMock via the config at MetaRepoFor20, but the main repo is sthub/.../BabyMock. Even though #2 is in the system, because the packages were loaded from there, it doesn't appear on the list - only #1 does. So I had to pick #1 and then copy/paste #2 in later. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Strange-Versionner-behavior-tp4736758p4737315.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
participants (3)
-
Christophe Demarey -
Norbert Hartl -
Sean P. DeNigris