I think this small thread is an excellent example of the need we have to implement simpler practice:
When we announce a package or project, it would nice if the first paragraph[s] could be a short description of what it's all about! We could even open another thread and agree upon a format for it, and look, we could even have the same text in some specific attribute in the package which could be collected, selected, etc.!! -- Cesar Rabak Em 06/12/2010 07:08, Tudor Girba < [email protected] > escreveu: Good work, Cyrille! For people that might not know what RPackage is, this project aims to replace PackageInfo with a faster and cleaner implementation. At the moment, all categories are mapped one-to-one and in the end, we would like to remove class categories altogether. This infrastructure is also targeted to code browsers. Doru On 6 Dec 2010, at 09:58, Cyrille Delaunay wrote: > Hello, > > Recently I made some improvements about RPackage. What I mainly did, is to > implement the 'SystemAnnounncements listening', to update the organizer when > the system change. With that I implemented a set of tests that should all be > green now (in RPackageMCSynchronisationTest (I should change the name)). > > You can load RPackage by evaluating: > > Gofer new > squeaksource: 'PharoInbox'; > package: 'ConfigurationOfRPackage'; > load. > (Smalltalk at: #ConfigurationOfRPackage) perform: #loadDefault. > > (I think it should work, but squeaksource is down for now, so I was not able > to test it). > > In those tests I started to write some about traits, but after few, I > realized that the events emitted when a trait change are the same that the > one used for classes ? > Then if you have some ideas about what is still missing in RPackage, tell me, > I can add it to my task list :) -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."
