OK. I'm working on it now. Should I update beta2 or create beta3 ?
I'm also adding Shortcuts-Help. Laurent On Tue, Dec 28, 2010 at 2:20 PM, Mariano Martinez Peck < [email protected]> wrote: > Ahh Laurent, don't forget to add those projects also to the group: 'Dev > Tools' in ConfigurationOfPharo > > Cheers > > Mariano > > > > On Tue, Dec 28, 2010 at 11:28 AM, Mariano Martinez Peck < > [email protected]> wrote: > >> >> >> On Mon, Dec 27, 2010 at 12:45 PM, laurent laffont < >> [email protected]> wrote: >> >>> On Sun, Dec 26, 2010 at 10:59 PM, Mariano Martinez Peck < >>> [email protected]> wrote: >>> >>>> >>>> >>>> On Fri, Dec 17, 2010 at 9:04 AM, laurent laffont < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> >>>>> What do you think about adding these packages as default in Pharo 1.2: >>>>> - ConfigurationOfMocketry >>>>> - ConfigurationOfXMLSupport >>>>> - ConfigurationOfCryptography (does'nt exist yet, planned to be >>>>> created in a local coding-dojo on Tuesday). >>>>> >>>>> Motivations: >>>>> - XMLSupport and Cryptography are often needed to consume web services >>>>> - Mocketry because I want to write tests using Mocks and it's easier to >>>>> work when tools are in standard Pharo (and then newcomers can see Mocketry >>>>> examples). >>>>> >>>>> >>>>> I will update ConfigurationOfPharo 1.2 (beta3 ?) if people agree. >>>>> >>>>> >>>> Hi Laurent. I agree it would be nice to include those 3 projects in >>>> PharoDev. Do they have tests? are they all green in pharo 1.2? >>>> >>> >>> >>> - ConfigurationOfMocketry has 479 tests, all green now in Pharo 1.2 + >>> HelpSystem help. >>> - ConfigurationOfXMLSupport version: '1.0.2' has 32 tests, all green (but >>> blessing is #development so I don't know if we can include it). version >>> 1.0.0 has 8 tests, green. >>> - ConfigurationOfAutotest: 27 tests green + HelpSystem help. >>> >>> >> Hi Laurent. I think both kind of tools are important for doing business in >> Pharo: test and XML support. Both have been asked several times in the >> mailing list. Having them in the dev image would be easier for this point of >> view, and users can help detecting bugs, using it, etc. >> >> I would include those 3 projects in the PharoDev. So, go ahead and add it >> in ConfigurationOfPharo. We can always go back. >> >> For Autotest, what I suggest is to have it in the image, but not enable by >> default. THose who want to use it, just open the settings browser and enable >> it. >> >> >>> For Cryptography I've started to look at it but there's some work to be >>> done: there's only one packages with all algorithms + tests + core. So it >>> should be splitted. You are right about MD5 (splitting should resolve this). >>> Actually 10 tests out of 102 fail. >>> >>> >> For the Cryptography I would wait a bit, as you say. Because in pharo >> core we already have the package System-Hashing ... so I am not sure how to >> deal with it. >> >> Cheers >> >> Mariano >> >> >>> Laurent >>> >>> >>> >>> >>> >>>> >>>> If true, and people agree, please feel free to update >>>> ConfigurationOfPharo >>>> >>>> I didn't check ConfigurationOfCryptography but I remember that MD5 and >>>> few other classes where already integrated in PharoCore. We should avoid >>>> collisions. Are those classes still alive in the Cryptography package? >>>> >>>> cheers >>>> >>>> mariano >>>> >>>> >>>>> Cheers, >>>>> >>>>> Laurent Laffont >>>>> >>>> >>>> >>> >> >
