Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
Hi Esteban, I'm porting to the new RPackage and I have a few questions: * What is the best way to get the RPackage linked to a MCWorkingCopy? I use aMCWorkingCopy packageSet packages first But is there a better way to do it? * For tags, if the package has only a system category with the same name as the package, will this result in one tag or no tag (i.e. will there be at least one tag in a RPackage?) * RPackageTag has a few assymetries: adding a class to a tag doesn't change its system category, however renaming a tag reclassifies the classes in the tag... * Tracking changes to tags suppose in fact listening to system-category announcements, isn't it? Otherwise, porting to the new RPackage is going along fine :) Thanks for the effort. I haven't found the new Nautilus yet :( Thierry Le 17/10/2013 15:51, Esteban Lorenzano a écrit : yes, because package names changed (no more 1 rpackage = 1 system category), then the export of sources changed too (not the contents). For example, what was AST-Core-*, now is just AST-Core. Esteban On Oct 17, 2013, at 2:51 PM, Marcus Denker marcus.den...@gmail.com wrote: On 17.10.2013, at 13:11, Camillo Bruni camillobr...@gmail.com wrote: Strange... the commit is already there :) too large for the list (7mb) https://github.com/pharo-project/pharo-core/commit/39e14deac5f2ad03e2d1b539ed8100eeb765167b On 2013-10-17, at 13:08, Esteban Lorenzano esteba...@gmail.com wrote: he... the update is already there, github failed to send the diff info (yet) On Oct 17, 2013, at 1:09 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Le 17/10/2013 12:51, Esteban Lorenzano a écrit : On Oct 17, 2013, at 12:57 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Are you using MorphTreeMorph? yep :) I haven't tried to use multi-selection in the tree; the code to handle multi-selection looks fairly complex. I remember having difficulties to understand how to pass and receive objects through drag and drop. I'll have a look as soon as I see the update coming. Unless loading the last Nautilus packages in Pharo3Inbox works :) Thierry Thierry Le 17/10/2013 12:46, Esteban Lorenzano a écrit : btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
On Oct 18, 2013, at 9:57 AM, Goubier Thierry thierry.goub...@cea.fr wrote: Hi Esteban, I'm porting to the new RPackage and I have a few questions: * What is the best way to get the RPackage linked to a MCWorkingCopy? I use aMCWorkingCopy packageSet packages first But is there a better way to do it? well... it should, but it isn't :( I suppose RPackageOrganizer default packageNamed: aMCWorkingCopy packageName should work, but I didn't implemented (feel free to do it and commit a slice :). * For tags, if the package has only a system category with the same name as the package, will this result in one tag or no tag (i.e. will there be at least one tag in a RPackage?) there will be always one tag (homonym to its parent) * RPackageTag has a few assymetries: adding a class to a tag doesn't change its system category, however renaming a tag reclassifies the classes in the tag... mmm... yes, I'm more or less aware. We should fix that, but still not sure how (easiest when is to make the add tag to inform a new system category, but then also rename/remove). Again... if you want to help there, please do it! * Tracking changes to tags suppose in fact listening to system-category announcements, isn't it? yep :( anyway, next year I will remove also System Categories, but in the mean time we need the sync. Otherwise, porting to the new RPackage is going along fine :) Thanks for the effort. cool! I haven't found the new Nautilus yet :( why? it is there :) Esteban Thierry Le 17/10/2013 15:51, Esteban Lorenzano a écrit : yes, because package names changed (no more 1 rpackage = 1 system category), then the export of sources changed too (not the contents). For example, what was AST-Core-*, now is just AST-Core. Esteban On Oct 17, 2013, at 2:51 PM, Marcus Denker marcus.den...@gmail.com wrote: On 17.10.2013, at 13:11, Camillo Bruni camillobr...@gmail.com wrote: Strange... the commit is already there :) too large for the list (7mb) https://github.com/pharo-project/pharo-core/commit/39e14deac5f2ad03e2d1b539ed8100eeb765167b On 2013-10-17, at 13:08, Esteban Lorenzano esteba...@gmail.com wrote: he... the update is already there, github failed to send the diff info (yet) On Oct 17, 2013, at 1:09 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Le 17/10/2013 12:51, Esteban Lorenzano a écrit : On Oct 17, 2013, at 12:57 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Are you using MorphTreeMorph? yep :) I haven't tried to use multi-selection in the tree; the code to handle multi-selection looks fairly complex. I remember having difficulties to understand how to pass and receive objects through drag and drop. I'll have a look as soon as I see the update coming. Unless loading the last Nautilus packages in Pharo3Inbox works :) Thierry Thierry Le 17/10/2013 12:46, Esteban Lorenzano a écrit : btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
Hi Esteban, thanks. This annoucement is very much appreciated, and will help me switch to the new RPackage. Have you changed things in the announcements as well (RPackage created / modified / unregistered?) Thierry Le 17/10/2013 12:20, Esteban Lorenzano a écrit : Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
no, they remain the same. I changed the RPackageOrganizer reaction to them, thought... but that shouldn't be a problem, On Oct 17, 2013, at 12:52 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Hi Esteban, thanks. This annoucement is very much appreciated, and will help me switch to the new RPackage. Have you changed things in the announcements as well (RPackage created / modified / unregistered?) Thierry Le 17/10/2013 12:20, Esteban Lorenzano a écrit : Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
On Oct 17, 2013, at 12:57 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Are you using MorphTreeMorph? yep :) Thierry Le 17/10/2013 12:46, Esteban Lorenzano a écrit : btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
Le 17/10/2013 12:51, Esteban Lorenzano a écrit : On Oct 17, 2013, at 12:57 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Are you using MorphTreeMorph? yep :) I haven't tried to use multi-selection in the tree; the code to handle multi-selection looks fairly complex. I remember having difficulties to understand how to pass and receive objects through drag and drop. I'll have a look as soon as I see the update coming. Unless loading the last Nautilus packages in Pharo3Inbox works :) Thierry Thierry Le 17/10/2013 12:46, Esteban Lorenzano a écrit : btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
Strange... the commit is already there :) https://github.com/pharo-project/pharo-core/commit/39e14deac5f2ad03e2d1b539ed8100eeb765167b On 2013-10-17, at 13:08, Esteban Lorenzano esteba...@gmail.com wrote: he... the update is already there, github failed to send the diff info (yet) On Oct 17, 2013, at 1:09 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Le 17/10/2013 12:51, Esteban Lorenzano a écrit : On Oct 17, 2013, at 12:57 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Are you using MorphTreeMorph? yep :) I haven't tried to use multi-selection in the tree; the code to handle multi-selection looks fairly complex. I remember having difficulties to understand how to pass and receive objects through drag and drop. I'll have a look as soon as I see the update coming. Unless loading the last Nautilus packages in Pharo3Inbox works :) Thierry Thierry Le 17/10/2013 12:46, Esteban Lorenzano a écrit : btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
30495 has it? AltBrowser still works, but it looks all disorganized inside the packages :):) Thierry Le 17/10/2013 13:08, Esteban Lorenzano a écrit : he... the update is already there, github failed to send the diff info (yet) On Oct 17, 2013, at 1:09 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Le 17/10/2013 12:51, Esteban Lorenzano a écrit : On Oct 17, 2013, at 12:57 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Are you using MorphTreeMorph? yep :) I haven't tried to use multi-selection in the tree; the code to handle multi-selection looks fairly complex. I remember having difficulties to understand how to pass and receive objects through drag and drop. I'll have a look as soon as I see the update coming. Unless loading the last Nautilus packages in Pharo3Inbox works :) Thierry Thierry Le 17/10/2013 12:46, Esteban Lorenzano a écrit : btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
On 17.10.2013, at 13:11, Camillo Bruni camillobr...@gmail.com wrote: Strange... the commit is already there :) too large for the list (7mb) https://github.com/pharo-project/pharo-core/commit/39e14deac5f2ad03e2d1b539ed8100eeb765167b On 2013-10-17, at 13:08, Esteban Lorenzano esteba...@gmail.com wrote: he... the update is already there, github failed to send the diff info (yet) On Oct 17, 2013, at 1:09 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Le 17/10/2013 12:51, Esteban Lorenzano a écrit : On Oct 17, 2013, at 12:57 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Are you using MorphTreeMorph? yep :) I haven't tried to use multi-selection in the tree; the code to handle multi-selection looks fairly complex. I remember having difficulties to understand how to pass and receive objects through drag and drop. I'll have a look as soon as I see the update coming. Unless loading the last Nautilus packages in Pharo3Inbox works :) Thierry Thierry Le 17/10/2013 12:46, Esteban Lorenzano a écrit : btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
yes, because package names changed (no more 1 rpackage = 1 system category), then the export of sources changed too (not the contents). For example, what was AST-Core-*, now is just AST-Core. Esteban On Oct 17, 2013, at 2:51 PM, Marcus Denker marcus.den...@gmail.com wrote: On 17.10.2013, at 13:11, Camillo Bruni camillobr...@gmail.com wrote: Strange... the commit is already there :) too large for the list (7mb) https://github.com/pharo-project/pharo-core/commit/39e14deac5f2ad03e2d1b539ed8100eeb765167b On 2013-10-17, at 13:08, Esteban Lorenzano esteba...@gmail.com wrote: he... the update is already there, github failed to send the diff info (yet) On Oct 17, 2013, at 1:09 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Le 17/10/2013 12:51, Esteban Lorenzano a écrit : On Oct 17, 2013, at 12:57 PM, Goubier Thierry thierry.goub...@cea.fr wrote: Are you using MorphTreeMorph? yep :) I haven't tried to use multi-selection in the tree; the code to handle multi-selection looks fairly complex. I remember having difficulties to understand how to pass and receive objects through drag and drop. I'll have a look as soon as I see the update coming. Unless loading the last Nautilus packages in Pharo3Inbox works :) Thierry Thierry Le 17/10/2013 12:46, Esteban Lorenzano a écrit : btw, a couple things that I know still doesn't work in Nautilus with trees: - drag and drop (I failed miserably when trying to implement it, any help here would be welcome :) - multiselection in packages Esteban On Oct 17, 2013, at 12:20 PM, Esteban Lorenzano esteba...@gmail.com wrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
What is the AltBrowser? Any screenshot? Alexandre Le 17-10-2013 à 7:52, Goubier Thierry thierry.goub...@cea.fr a écrit : Hi Esteban, thanks. This annoucement is very much appreciated, and will help me switch to the new RPackage. Have you changed things in the announcements as well (RPackage created / modified / unregistered?) Thierry Le 17/10/2013 12:20, Esteban Lorenzano a écrit : Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] IMPORTANT: RPackage behavior changed and Nautilus updated
Excellent! Doru p.s. It's amazing how often I feel like saying amazing about Pharo these days :) On Thu, Oct 17, 2013 at 12:20 PM, Esteban Lorenzano esteba...@gmail.comwrote: Hi, I just important an important change in Pharo. I made a new step over the integration of RPackage into the system, and as a result there is a different behavior. Although 99% of users shouldn't notice it, that can drive to headaches to tool developers, like Thierry and his AltBrowser (but I'm not sure about that) :) I'm sorry, but this is inevitable... and part of a long path discussed and adopted since almost 1 1/2 years. So, what's the change? Now 1 RPackage 0 1 MCPackage. As a result, package granularity is coarse, and then categories for class are stored as package tags. Other consequence is that RPackageSet is now more or less useless, but I'm keeping it because it provides caching services for monticello, and the speed up resulting is good :) This change opens the path to remove old PackageInfo, finally :) To take the new structure into account (and to add a long time awaited feature), I modified nautilus to use a tree instead a simple list (finally!) And since I was in the mood, I moved groups to same list, taking the idea of the screenshot Stef sent the other day (lots of good ideas that we should adopt there), and then I removed the groups button... in functionality is good, but visually not so much... I accept ideas about :) THERE WILL BE BUGS! This is a really deep and important change, I'm pushing it because we need to test and fix. So, do not hesitate to send your reports! Also, there are features in modified-nautilus that are missing. It would be good to have a list of them so I can implement it :) Please, report any issue around. Enjoy, Esteban -- www.tudorgirba.com Every thing has its own flow
