December 2013 - Pharo-users

Re: [Pharo-users] Shrinking Pharo 3 image

by Ignacio MatÃas Sniechowski

Great. Thanks Pavel. Do you have in mind extending the unreloading to other packages as well? best regards nacho *Lic. Ignacio Sniechowski, MBA* On Wed, Dec 11, 2013 at 1:51 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com>wrote: > Gofer new > smalltalkhubUser: 'Pharo' project: 'SystemConfigurations'; > package: 'UnReloader'; > load. > > > > 2013/12/11 Sergi Reyner <sergi.reyner(a)gmail.com> > >> 2013/12/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >>> >>> Have a look at the ReUnloader package under my project on smalltalkhub. >>> >> >> Which one? >> >> > >

Dec. 12, 2013

Re: [Pharo-users] InstallGemTools does not load

by Paul DeBruicker

GemTools only works in Pharo 1.1.1 You should just use the one click image from here: http://seaside.gemtalksystems.com/downloads.html Also there is a GLASS mailing list here: http://forum.world.st/GLASS-f1460844.html where you can find more answers and ask questions of the GemStone people. Robert Pergl wrote > Hi guys, > > InstallGemTools loading fails both in Pharo 2.0 and 3.0. Is there some fix > please? > > https://code.google.com/p/glassdb/wiki/InstallGemTools > > Thanks, > > with regards, > > Robert > > -- > Ing. Robert Pergl, Ph.D. > Assistant Professor > Department of Software Engineering -- Centre for Conceptual Modelling > http://ccm.fit.cvut.cz > Czech Technical University in Prague, Faculty of Information Technology > ThÃ¡kurova 9, 160 00 Praha 6, Czech Republic > room: A1233 > http://www.fit.cvut.cz/en > e-mail: > robert.pergl@.cvut > tel.: +420 777 042 249 > > -------------- > The content of this e-mail and any attached files are confidential and > may be legally privileged. It is intended solely for the addressee. > Access to this e-mail by anyone else is unauthorized. If you are not the > intended recipient, any disclosure, copying, distribution or any action > taken or omitted to be taken in reliance on it, is prohibited and may be > unlawful. In this case be so kind and delete this e-mail and inform us > about it. -- View this message in context: http://forum.world.st/InstallGemTools-does-not-load-tp4729397p4729436.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 11, 2013

Re: [Pharo-users] InstallGemTools does not load

by phil＠highoctane.be

I guess not. Looks like it is a Pharo 1.x product only. The current work appears to be around here: https://github.com/dalehenrich/tode Phil On Wed, Dec 11, 2013 at 5:49 PM, Robert Pergl <robert.pergl(a)fit.cvut.cz>wrote: > Hi guys, > > InstallGemTools loading fails both in Pharo 2.0 and 3.0. Is there some fix > please? > > https://code.google.com/p/glassdb/wiki/InstallGemTools > > Thanks, > > with regards, > > Robert > > -- > Ing. Robert Pergl, Ph.D. > Assistant Professor > Department of Software Engineering -- Centre for Conceptual Modelling > http://ccm.fit.cvut.cz > Czech Technical University in Prague, Faculty of Information Technology > ThÃ¡kurova 9, 160 00 Praha 6, Czech Republic > room: A1233 > http://www.fit.cvut.cz/en > e-mail: robert.pergl(a)fit.cvut.cz > tel.: +420 777 042 249 > > -------------- > The content of this e-mail and any attached files are confidential and > may be legally privileged. It is intended solely for the addressee. > Access to this e-mail by anyone else is unauthorized. If you are not the > intended recipient, any disclosure, copying, distribution or any action > taken or omitted to be taken in reliance on it, is prohibited and may be > unlawful. In this case be so kind and delete this e-mail and inform us > about it. > > > >

Dec. 11, 2013

Re: [Pharo-users] Shrinking Pharo 3 image

by Pavel Krivanek

Gofer new smalltalkhubUser: 'Pharo' project: 'SystemConfigurations'; package: 'UnReloader'; load. 2013/12/11 Sergi Reyner <sergi.reyner(a)gmail.com> > 2013/12/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> >> Have a look at the ReUnloader package under my project on smalltalkhub. >> > > Which one? > >

Dec. 11, 2013

InstallGemTools does not load

by Robert Pergl

Hi guys, InstallGemTools loading fails both in Pharo 2.0 and 3.0. Is there some fix please? https://code.google.com/p/glassdb/wiki/InstallGemTools Thanks, with regards, Robert -- Ing. Robert Pergl, Ph.D. Assistant Professor Department of Software Engineering -- Centre for Conceptual Modelling http://ccm.fit.cvut.cz Czech Technical University in Prague, Faculty of Information Technology ThÃ¡kurova 9, 160 00 Praha 6, Czech Republic room: A1233 http://www.fit.cvut.cz/en e-mail: robert.pergl(a)fit.cvut.cz tel.: +420 777 042 249 -------------- The content of this e-mail and any attached files are confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. In this case be so kind and delete this e-mail and inform us about it.

Dec. 11, 2013

Re: [Pharo-users] Shrinking Pharo 3 image

by Sergi Reyner

2013/12/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > Have a look at the ReUnloader package under my project on smalltalkhub. > Which one?

Dec. 11, 2013

Re: [Pharo-users] [Pharo-dev] [Pharo Trick: #0001] - Simple TODO list

by phil＠highoctane.be

I do self flag: #TODO. "blah" Senders of symbol works too. Made a nautilus too that gives me the list so that I can click and go there. Phil On Wednesday, December 11, 2013, Bahman Movaqar wrote: > I think what may be needed is a community website with materials like > cookbook recipes, idea sheets, useful links, related blogs and such > --basically anything except maybe mailing lists and forums. Am I right? > > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > > On 12/11/2013 14:46, Torsten Bergmann wrote: > > Hi, > > > > the mailinglist, stackoverflow and other Pharo related medias are > typically used > > in the "here is a question to problem" followed by an "answer from > community" style. > > > > But lets also think the other way around: if we already have a solution > for a > > problem that others may have too or may have in the future we should > share the > > answer/solution as well. > > > > I'm sure many of you have some tricks that make developing with Pharo > much easier > > and others can profit from these tricks if we share them here on the > list. > > > > Be it > > - a simple and useful script > > - a simple key combination other may not yet know of > > - a package one can use or how you use it > > - a link to a nice description on the web related on how to use Pharo > > - a custom tool that makes development easier > > - an algorithm or something that you think was solved very elegant > > - a way you solved a common problem easily in your app > > - ... > > > > Then just describe it in a few lines and post it. Also write in which > Pharo > > version you tried it - this makes it easier for others to see in which > > version the trick/solution is known to work. > > > > The idea goes like this: if you have a trick to share then send a mail > with > > subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND > Pharo user > > list (see http://lists.pharo.org) Make sure to increase the trick > counter xxxx. > > > > Using this special subject one can later easily get the tricks from the > > mailinglist archive. Also others can refer to the trick if it solves a > common > > problem other may ask for on the list. > > > > Lets see if we are able to reach the goals of 100, 1000 or more Pharo > tricks ;) > > > > Bye > > T. > > > > > > I will start with something easy but useful: > > > > > ----------------------------------------------------------------------------------- > > [Pharo Trick: #0001] - Simple TODO > > > ----------------------------------------------------------------------------------- > > Works in: Pharo3.0 Latest update: #30635 but should work in other > versions too > > > ----------------------------------------------------------------------------------- > > > > If you develop an app with Pharo you may not yet fully implement all > features. > > Some kind of marker for future "ToDo's" is often needed. Using a pragma > on a method is > > the easiest solution here: > > > > foo > > <todo: 'Add world later'> > > "That method is not yet fully implemented" > > > > Transcript show: 'Hello' > > > > > > Using a simple expression in the workspace you can browse all the TODOs > for your > > project afterwards in a window: > > > > SystemNavigation default browseAllSendersOf: #todo: > > > > You can even query the system for the todo descriptions if you need the > full > > list of things to work on: > > > > (PragmaCollector filter: [:prg | prg keyword = 'todo:']) > > reset; > > collect: [:each| each arguments first ] > > > > As the pragma keyword #todo: is very common and may be used by others too > > it may be wise to use a custom one like "myappplicationTodo:" or similar. > > > ----------------------------------------------------------------------------------- > > > > > -- --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller

Dec. 11, 2013

Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list

by Bahman Movaqar

I'd be very glad to offer Pharo community a free full-fledged Plone website to use as a community website, a few examples: http://yfl.BahmanM.com http://michael.richter.name The services I can offer include * The ability to create several content types on the websites: + Pages (recipes, articles, ideas, ...) + Links + Forums + Images * Accurate full-text-search * Upload any type of file * And whatever else the community requires Let me know if you are interested in this offer. -- Bahman Movaqar (http://BahmanM.com) ERP Evaluation, Implementation & Deployment Consultant PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) On 12/11/2013 14:55, Bahman Movaqar wrote: > I think what may be needed is a community website with materials like > cookbook recipes, idea sheets, useful links, related blogs and such > --basically anything except maybe mailing lists and forums. Am I right? > > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > > On 12/11/2013 14:46, Torsten Bergmann wrote: >> Hi, >> >> the mailinglist, stackoverflow and other Pharo related medias are typically used >> in the "here is a question to problem" followed by an "answer from community" style. >> >> But lets also think the other way around: if we already have a solution for a >> problem that others may have too or may have in the future we should share the >> answer/solution as well. >> >> I'm sure many of you have some tricks that make developing with Pharo much easier >> and others can profit from these tricks if we share them here on the list. >> >> Be it >> - a simple and useful script >> - a simple key combination other may not yet know of >> - a package one can use or how you use it >> - a link to a nice description on the web related on how to use Pharo >> - a custom tool that makes development easier >> - an algorithm or something that you think was solved very elegant >> - a way you solved a common problem easily in your app >> - ... >> >> Then just describe it in a few lines and post it. Also write in which Pharo >> version you tried it - this makes it easier for others to see in which >> version the trick/solution is known to work. >> >> The idea goes like this: if you have a trick to share then send a mail with >> subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND Pharo user >> list (see http://lists.pharo.org) Make sure to increase the trick counter xxxx. >> >> Using this special subject one can later easily get the tricks from the >> mailinglist archive. Also others can refer to the trick if it solves a common >> problem other may ask for on the list. >> >> Lets see if we are able to reach the goals of 100, 1000 or more Pharo tricks ;) >> >> Bye >> T. >> >> >> I will start with something easy but useful: >> >> ----------------------------------------------------------------------------------- >> [Pharo Trick: #0001] - Simple TODO >> ----------------------------------------------------------------------------------- >> Works in: Pharo3.0 Latest update: #30635 but should work in other versions too >> ----------------------------------------------------------------------------------- >> >> If you develop an app with Pharo you may not yet fully implement all features. >> Some kind of marker for future "ToDo's" is often needed. Using a pragma on a method is >> the easiest solution here: >> >> foo >> <todo: 'Add world later'> >> "That method is not yet fully implemented" >> >> Transcript show: 'Hello' >> >> >> Using a simple expression in the workspace you can browse all the TODOs for your >> project afterwards in a window: >> >> SystemNavigation default browseAllSendersOf: #todo: >> >> You can even query the system for the todo descriptions if you need the full >> list of things to work on: >> >> (PragmaCollector filter: [:prg | prg keyword = 'todo:']) >> reset; >> collect: [:each| each arguments first ] >> >> As the pragma keyword #todo: is very common and may be used by others too >> it may be wise to use a custom one like "myappplicationTodo:" or similar. >> ----------------------------------------------------------------------------------- >> >

Dec. 11, 2013

Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list

by Sergi Reyner

2013/12/11 Tudor Girba <tudor(a)tudorgirba.com> > Better yet: write a blog post and send the link to the list. > With that approach there's the issue that blogs can (and do) go away for various reasons :/ Cheers, Sergi

Dec. 11, 2013

Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list

by Luc Fabresse

or use the Collaboractive Book: http://book.pharo-project.org Luc #Luc 2013/12/11 Tudor Girba <tudor(a)tudorgirba.com> > Better yet: write a blog post and send the link to the list. > > Doru > > > On Wed, Dec 11, 2013 at 12:25 PM, Bahman Movaqar <Bahman(a)bahmanm.com>wrote: > >> I think what may be needed is a community website with materials like >> cookbook recipes, idea sheets, useful links, related blogs and such >> --basically anything except maybe mailing lists and forums. Am I right? >> >> -- >> Bahman Movaqar (http://BahmanM.com) >> >> ERP Evaluation, Implementation & Deployment Consultant >> PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) >> >> On 12/11/2013 14:46, Torsten Bergmann wrote: >> > Hi, >> > >> > the mailinglist, stackoverflow and other Pharo related medias are >> typically used >> > in the "here is a question to problem" followed by an "answer from >> community" style. >> > >> > But lets also think the other way around: if we already have a solution >> for a >> > problem that others may have too or may have in the future we should >> share the >> > answer/solution as well. >> > >> > I'm sure many of you have some tricks that make developing with Pharo >> much easier >> > and others can profit from these tricks if we share them here on the >> list. >> > >> > Be it >> > - a simple and useful script >> > - a simple key combination other may not yet know of >> > - a package one can use or how you use it >> > - a link to a nice description on the web related on how to use Pharo >> > - a custom tool that makes development easier >> > - an algorithm or something that you think was solved very elegant >> > - a way you solved a common problem easily in your app >> > - ... >> > >> > Then just describe it in a few lines and post it. Also write in which >> Pharo >> > version you tried it - this makes it easier for others to see in which >> > version the trick/solution is known to work. >> > >> > The idea goes like this: if you have a trick to share then send a mail >> with >> > subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND >> Pharo user >> > list (see http://lists.pharo.org) Make sure to increase the trick >> counter xxxx. >> > >> > Using this special subject one can later easily get the tricks from the >> > mailinglist archive. Also others can refer to the trick if it solves a >> common >> > problem other may ask for on the list. >> > >> > Lets see if we are able to reach the goals of 100, 1000 or more Pharo >> tricks ;) >> > >> > Bye >> > T. >> > >> > >> > I will start with something easy but useful: >> > >> > >> ----------------------------------------------------------------------------------- >> > [Pharo Trick: #0001] - Simple TODO >> > >> ----------------------------------------------------------------------------------- >> > Works in: Pharo3.0 Latest update: #30635 but should work in other >> versions too >> > >> ----------------------------------------------------------------------------------- >> > >> > If you develop an app with Pharo you may not yet fully implement all >> features. >> > Some kind of marker for future "ToDo's" is often needed. Using a pragma >> on a method is >> > the easiest solution here: >> > >> > foo >> > <todo: 'Add world later'> >> > "That method is not yet fully implemented" >> > >> > Transcript show: 'Hello' >> > >> > >> > Using a simple expression in the workspace you can browse all the TODOs >> for your >> > project afterwards in a window: >> > >> > SystemNavigation default browseAllSendersOf: #todo: >> > >> > You can even query the system for the todo descriptions if you need the >> full >> > list of things to work on: >> > >> > (PragmaCollector filter: [:prg | prg keyword = 'todo:']) >> > reset; >> > collect: [:each| each arguments first ] >> > >> > As the pragma keyword #todo: is very common and may be used by others >> too >> > it may be wise to use a custom one like "myappplicationTodo:" or >> similar. >> > >> ----------------------------------------------------------------------------------- >> > >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Dec. 11, 2013

Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list

by Tudor Girba

Better yet: write a blog post and send the link to the list. Doru On Wed, Dec 11, 2013 at 12:25 PM, Bahman Movaqar <Bahman(a)bahmanm.com> wrote: > I think what may be needed is a community website with materials like > cookbook recipes, idea sheets, useful links, related blogs and such > --basically anything except maybe mailing lists and forums. Am I right? > > -- > Bahman Movaqar (http://BahmanM.com) > > ERP Evaluation, Implementation & Deployment Consultant > PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) > > On 12/11/2013 14:46, Torsten Bergmann wrote: > > Hi, > > > > the mailinglist, stackoverflow and other Pharo related medias are > typically used > > in the "here is a question to problem" followed by an "answer from > community" style. > > > > But lets also think the other way around: if we already have a solution > for a > > problem that others may have too or may have in the future we should > share the > > answer/solution as well. > > > > I'm sure many of you have some tricks that make developing with Pharo > much easier > > and others can profit from these tricks if we share them here on the > list. > > > > Be it > > - a simple and useful script > > - a simple key combination other may not yet know of > > - a package one can use or how you use it > > - a link to a nice description on the web related on how to use Pharo > > - a custom tool that makes development easier > > - an algorithm or something that you think was solved very elegant > > - a way you solved a common problem easily in your app > > - ... > > > > Then just describe it in a few lines and post it. Also write in which > Pharo > > version you tried it - this makes it easier for others to see in which > > version the trick/solution is known to work. > > > > The idea goes like this: if you have a trick to share then send a mail > with > > subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND > Pharo user > > list (see http://lists.pharo.org) Make sure to increase the trick > counter xxxx. > > > > Using this special subject one can later easily get the tricks from the > > mailinglist archive. Also others can refer to the trick if it solves a > common > > problem other may ask for on the list. > > > > Lets see if we are able to reach the goals of 100, 1000 or more Pharo > tricks ;) > > > > Bye > > T. > > > > > > I will start with something easy but useful: > > > > > ----------------------------------------------------------------------------------- > > [Pharo Trick: #0001] - Simple TODO > > > ----------------------------------------------------------------------------------- > > Works in: Pharo3.0 Latest update: #30635 but should work in other > versions too > > > ----------------------------------------------------------------------------------- > > > > If you develop an app with Pharo you may not yet fully implement all > features. > > Some kind of marker for future "ToDo's" is often needed. Using a pragma > on a method is > > the easiest solution here: > > > > foo > > <todo: 'Add world later'> > > "That method is not yet fully implemented" > > > > Transcript show: 'Hello' > > > > > > Using a simple expression in the workspace you can browse all the TODOs > for your > > project afterwards in a window: > > > > SystemNavigation default browseAllSendersOf: #todo: > > > > You can even query the system for the todo descriptions if you need the > full > > list of things to work on: > > > > (PragmaCollector filter: [:prg | prg keyword = 'todo:']) > > reset; > > collect: [:each| each arguments first ] > > > > As the pragma keyword #todo: is very common and may be used by others too > > it may be wise to use a custom one like "myappplicationTodo:" or similar. > > > ----------------------------------------------------------------------------------- > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 11, 2013

Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list

by Bahman Movaqar

I think what may be needed is a community website with materials like cookbook recipes, idea sheets, useful links, related blogs and such --basically anything except maybe mailing lists and forums. Am I right? -- Bahman Movaqar (http://BahmanM.com) ERP Evaluation, Implementation & Deployment Consultant PGP Key ID: 0x6AB5BD68 (keyserver2.pgp.com) On 12/11/2013 14:46, Torsten Bergmann wrote: > Hi, > > the mailinglist, stackoverflow and other Pharo related medias are typically used > in the "here is a question to problem" followed by an "answer from community" style. > > But lets also think the other way around: if we already have a solution for a > problem that others may have too or may have in the future we should share the > answer/solution as well. > > I'm sure many of you have some tricks that make developing with Pharo much easier > and others can profit from these tricks if we share them here on the list. > > Be it > - a simple and useful script > - a simple key combination other may not yet know of > - a package one can use or how you use it > - a link to a nice description on the web related on how to use Pharo > - a custom tool that makes development easier > - an algorithm or something that you think was solved very elegant > - a way you solved a common problem easily in your app > - ... > > Then just describe it in a few lines and post it. Also write in which Pharo > version you tried it - this makes it easier for others to see in which > version the trick/solution is known to work. > > The idea goes like this: if you have a trick to share then send a mail with > subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND Pharo user > list (see http://lists.pharo.org) Make sure to increase the trick counter xxxx. > > Using this special subject one can later easily get the tricks from the > mailinglist archive. Also others can refer to the trick if it solves a common > problem other may ask for on the list. > > Lets see if we are able to reach the goals of 100, 1000 or more Pharo tricks ;) > > Bye > T. > > > I will start with something easy but useful: > > ----------------------------------------------------------------------------------- > [Pharo Trick: #0001] - Simple TODO > ----------------------------------------------------------------------------------- > Works in: Pharo3.0 Latest update: #30635 but should work in other versions too > ----------------------------------------------------------------------------------- > > If you develop an app with Pharo you may not yet fully implement all features. > Some kind of marker for future "ToDo's" is often needed. Using a pragma on a method is > the easiest solution here: > > foo > <todo: 'Add world later'> > "That method is not yet fully implemented" > > Transcript show: 'Hello' > > > Using a simple expression in the workspace you can browse all the TODOs for your > project afterwards in a window: > > SystemNavigation default browseAllSendersOf: #todo: > > You can even query the system for the todo descriptions if you need the full > list of things to work on: > > (PragmaCollector filter: [:prg | prg keyword = 'todo:']) > reset; > collect: [:each| each arguments first ] > > As the pragma keyword #todo: is very common and may be used by others too > it may be wise to use a custom one like "myappplicationTodo:" or similar. > ----------------------------------------------------------------------------------- >

Dec. 11, 2013

[Pharo Trick: #0001] - Simple TODO list

by Torsten Bergmann

Hi, the mailinglist, stackoverflow and other Pharo related medias are typically used in the "here is a question to problem" followed by an "answer from community" style. But lets also think the other way around: if we already have a solution for a problem that others may have too or may have in the future we should share the answer/solution as well. I'm sure many of you have some tricks that make developing with Pharo much easier and others can profit from these tricks if we share them here on the list. Be it - a simple and useful script - a simple key combination other may not yet know of - a package one can use or how you use it - a link to a nice description on the web related on how to use Pharo - a custom tool that makes development easier - an algorithm or something that you think was solved very elegant - a way you solved a common problem easily in your app - ... Then just describe it in a few lines and post it. Also write in which Pharo version you tried it - this makes it easier for others to see in which version the trick/solution is known to work. The idea goes like this: if you have a trick to share then send a mail with subject "Pharo Trick: #xxxx] - Short Description" to the Pharo dev AND Pharo user list (see http://lists.pharo.org) Make sure to increase the trick counter xxxx. Using this special subject one can later easily get the tricks from the mailinglist archive. Also others can refer to the trick if it solves a common problem other may ask for on the list. Lets see if we are able to reach the goals of 100, 1000 or more Pharo tricks ;) Bye T. I will start with something easy but useful: ----------------------------------------------------------------------------------- [Pharo Trick: #0001] - Simple TODO ----------------------------------------------------------------------------------- Works in: Pharo3.0 Latest update: #30635 but should work in other versions too ----------------------------------------------------------------------------------- If you develop an app with Pharo you may not yet fully implement all features. Some kind of marker for future "ToDo's" is often needed. Using a pragma on a method is the easiest solution here: foo <todo: 'Add world later'> "That method is not yet fully implemented" Transcript show: 'Hello' Using a simple expression in the workspace you can browse all the TODOs for your project afterwards in a window: SystemNavigation default browseAllSendersOf: #todo: You can even query the system for the todo descriptions if you need the full list of things to work on: (PragmaCollector filter: [:prg | prg keyword = 'todo:']) reset; collect: [:each| each arguments first ] As the pragma keyword #todo: is very common and may be used by others too it may be wise to use a custom one like "myappplicationTodo:" or similar. -----------------------------------------------------------------------------------

Dec. 11, 2013

Re: [Pharo-users] Shrinking Pharo 3 image

by StÃ©phane Ducasse

On Dec 10, 2013, at 11:37 PM, Ignacio MatÃas Sniechowski <0800nacho(a)gmail.com> wrote: > Thanks for your responses. > I imagine the daunting task unloading Nautilus should have been. :p took time but now it is working. Have a look at the ReUnloader package under my project on smalltalkhub. Ideally I would like to move ushc methods in their respective package/configurationof. Stef > Nacho > > > Lic. Ignacio Sniechowski, MBA > > > > > > > > On Tue, Dec 10, 2013 at 7:10 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I'm trying slowly. Because I want to reload everything with metacello configurations. > Tomorrow I will pair program with pavel to make progress on that. > I could unload > Nautilus > RB > but there are many more. > > Stef > > On Dec 10, 2013, at 8:40 PM, nacho <0800nacho(a)gmail.com> wrote: > > > Hi, > > I'm trying to unload some of the packages from Pharo 3 to come up with a > > reduced Pharo Image. > > I don't know if someone has already succeeded at getting a Pharo kernel > > image. Just the basic and really needed classes and packages. > > And then have the possibility to reload Athens, Zinc, Zodiac, ASM, etc, as > > needed. > > Simply unloading the packages from Monticello does not work, as it seems > > some of the packages are correlated, and I don't really know packages' > > dependencies. > > Any help would be much appreciated. > > Thanks in advance & best regards. > > Nacho > > > > > > > > > > ----- > > Nacho > > Smalltalker apprentice. > > Buenos Aires, Argentina. > > -- > > View this message in context: http://forum.world.st/Shrinking-Pharo-3-image-tp4729041.html > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > >

Dec. 11, 2013

Re: [Pharo-users] Shrinking Pharo 3 image

by Ignacio MatÃas Sniechowski

Thanks for your responses. I imagine the daunting task unloading Nautilus should have been. :p Nacho *Lic. Ignacio Sniechowski, MBA* On Tue, Dec 10, 2013 at 7:10 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > I'm trying slowly. Because I want to reload everything with metacello > configurations. > Tomorrow I will pair program with pavel to make progress on that. > I could unload > Nautilus > RB > but there are many more. > > Stef > > On Dec 10, 2013, at 8:40 PM, nacho <0800nacho(a)gmail.com> wrote: > > > Hi, > > I'm trying to unload some of the packages from Pharo 3 to come up with a > > reduced Pharo Image. > > I don't know if someone has already succeeded at getting a Pharo kernel > > image. Just the basic and really needed classes and packages. > > And then have the possibility to reload Athens, Zinc, Zodiac, ASM, etc, > as > > needed. > > Simply unloading the packages from Monticello does not work, as it seems > > some of the packages are correlated, and I don't really know packages' > > dependencies. > > Any help would be much appreciated. > > Thanks in advance & best regards. > > Nacho > > > > > > > > > > ----- > > Nacho > > Smalltalker apprentice. > > Buenos Aires, Argentina. > > -- > > View this message in context: > http://forum.world.st/Shrinking-Pharo-3-image-tp4729041.html > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > >

Dec. 10, 2013

Re: [Pharo-users] Shrinking Pharo 3 image

by StÃ©phane Ducasse

I'm trying slowly. Because I want to reload everything with metacello configurations. Tomorrow I will pair program with pavel to make progress on that. I could unload Nautilus RB but there are many more. Stef On Dec 10, 2013, at 8:40 PM, nacho <0800nacho(a)gmail.com> wrote: > Hi, > I'm trying to unload some of the packages from Pharo 3 to come up with a > reduced Pharo Image. > I don't know if someone has already succeeded at getting a Pharo kernel > image. Just the basic and really needed classes and packages. > And then have the possibility to reload Athens, Zinc, Zodiac, ASM, etc, as > needed. > Simply unloading the packages from Monticello does not work, as it seems > some of the packages are correlated, and I don't really know packages' > dependencies. > Any help would be much appreciated. > Thanks in advance & best regards. > Nacho > > > > > ----- > Nacho > Smalltalker apprentice. > Buenos Aires, Argentina. > -- > View this message in context: http://forum.world.st/Shrinking-Pharo-3-image-tp4729041.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Dec. 10, 2013

Re: [Pharo-users] Shrinking Pharo 3 image

by Pavel Krivanek

Hi, look at https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/ Cheers, -- Pavel 2013/12/10 nacho <0800nacho(a)gmail.com> > Hi, > I'm trying to unload some of the packages from Pharo 3 to come up with a > reduced Pharo Image. > I don't know if someone has already succeeded at getting a Pharo kernel > image. Just the basic and really needed classes and packages. > And then have the possibility to reload Athens, Zinc, Zodiac, ASM, etc, as > needed. > Simply unloading the packages from Monticello does not work, as it seems > some of the packages are correlated, and I don't really know packages' > dependencies. > Any help would be much appreciated. > Thanks in advance & best regards. > Nacho > > > > > ----- > Nacho > Smalltalker apprentice. > Buenos Aires, Argentina. > -- > View this message in context: > http://forum.world.st/Shrinking-Pharo-3-image-tp4729041.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Dec. 10, 2013

Shrinking Pharo 3 image

by nacho

Hi, I'm trying to unload some of the packages from Pharo 3 to come up with a reduced Pharo Image. I don't know if someone has already succeeded at getting a Pharo kernel image. Just the basic and really needed classes and packages. And then have the possibility to reload Athens, Zinc, Zodiac, ASM, etc, as needed. Simply unloading the packages from Monticello does not work, as it seems some of the packages are correlated, and I don't really know packages' dependencies. Any help would be much appreciated. Thanks in advance & best regards. Nacho ----- Nacho Smalltalker apprentice. Buenos Aires, Argentina. -- View this message in context: http://forum.world.st/Shrinking-Pharo-3-image-tp4729041.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 10, 2013

Re: [Pharo-users] Metacello config with local file based repository

by Paul DeBruicker

That should work fine Esteban A. Maringolo wrote > I'm defining my first Metacello config (ConfigurationOf...) but I > wonder how should I declare a local file based repository. > > Ej: > spec repository: '/home/emaringolo/development/monticello/'. > or its window counterpart: > spec repository: 'E:\users\emaringolo\development\monticello\'. > > Is that possible? > > Esteban A. Maringolo -- View this message in context: http://forum.world.st/Metacello-config-with-local-file-based-repository-tp4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 10, 2013

Metacello config with local file based repository

by Esteban A. Maringolo

I'm defining my first Metacello config (ConfigurationOf...) but I wonder how should I declare a local file based repository. Ej: spec repository: '/home/emaringolo/development/monticello/'. or its window counterpart: spec repository: 'E:\users\emaringolo\development\monticello\'. Is that possible? Esteban A. Maringolo

Dec. 10, 2013

Re: [Pharo-users] Using FFI

by Esteban Lorenzano

Hi Annik, long time without a response to this, I'm sorry. I'm just catching up with this stuff (I'm really full of work this days). The problem here is that FFI does not have the type "int". You need to choose between short, ushort, long and ulong (depending of the real size you need). And you do not have also char** (or any other pointer-pointer). But the non-typed nature of C comes to help here too :) You can easily declare: <apicall: void 'gst_init' (short ulong) module: 'blabla'> since basically size will be the same (and that's the only thing that really matters). you can see the allowed types here: ExternalType class>>#initializeFFIConstants cheers, Esteban On Sat, Nov 9, 2013 at 10:09 AM, <btc(a)openinworld.com> wrote: > > Hi Annick, > > I hope you are able to achieve what you are aiming for (I don't have the > technical knowledge to help) but as a bystander I must make an observation > that I hope will be useful to you. > > While your response "I have answered I think" could be technically correct > if someone wade through the whole thread, its not really an appropriate > answer to a specific question from someone whom you are asking devote their > valuable time to your problem. If you can take the tie to read [1] you > will understand where I am coming from. I personally found it very > worthwhile reading and even like to refresh myself from time to time. > > [1] http://www.catb.org/esr/faqs/smart-questions.html > > I'd be interested in your thoughts on the article. > > In good faith, > cheers -ben > > > > Annick Fron wrote: > > I have answered I think > > EnvoyÃ© de mon iPod > > > > Le 9 nov. 2013 Ã 02:01, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> <stephane.ducasse(a)inria.fr> a Ã©crit : > > Annick > > You cannot expect people to respond to you if you do not provide > full context + information. > On the long term people will stop to reply to you. > Repeat after me: > which image? > which OS version? > which vm version? > > I think that we are pretty nice people but do not force us to always ask the same questions. > We are all busy. > > > Stef > > > > > On Nov 6, 2013, at 6:15 PM, Annick Fron <info(a)afceurope.com> <info(a)afceurope.com> wrote: > > I am using the latest download from version 2 > Annick > > > > Le 31 oct. 2013 Ã 18:47, Esteban Lorenzano <estebanlm(a)gmail.com> <estebanlm(a)gmail.com> a Ã©crit : > > ok... then we have a problem. > but we need more data... > > which image version are you using? > and which vm version? > > cheers, > Esteban > > > > On Oct 31, 2013, at 11:24 AM, Annick Fron <info(a)afceurope.com> <info(a)afceurope.com> wrote: > > I hÃ¢ve thÃ© error on Windows > > EnvoyÃ© de mon iPod > > > > Le 31 oct. 2013 Ã 14:51, Igor Stasenko <siguctua(a)gmail.com> <siguctua(a)gmail.com> a Ã©crit : > > > > > > > On 31 October 2013 11:23, Annick Fron <info(a)afceurope.com> <info(a)afceurope.com> wrote: > Hi Igor > > I have done that, but still gets an error, do I need to remove NativeBoost ? > Annick > > > FFI not supported on ARM > > > > Le 30 oct. 2013 Ã 14:12, Igor Stasenko <siguctua(a)gmail.com> <siguctua(a)gmail.com> a Ã©crit : > > AFAIK, it should be in Configurations browser. > Else try this: > > Gofer new > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfFFI'; > load. > (Smalltalk at: #ConfigurationOfFFI) project lastVersion load > > > > > > On 30 October 2013 09:41, Annick Fron <info(a)afceurope.com> <info(a)afceurope.com> wrote: > My problem is that the Raspberry does not support native boost (as yet !). > Where can I load the old FFI ? > > > > Le 29 oct. 2013 Ã 16:57, Igor Stasenko <siguctua(a)gmail.com> <siguctua(a)gmail.com> a Ã©crit : > > > > > > > On 29 October 2013 16:27, Annick Fron <info(a)afceurope.com> <info(a)afceurope.com> wrote: > Hi > > I want to launch a simple init with the following C signature : > > void gst_init (int *argc, char **argv[]) > > If I write > > <apicall: void 'gst_init' (int*, char**) module: 'blabla'> > > I get a Smalltalk syntax error > > Annick Fron > > > To use this syntax, you must load old FFI implementation. > Or use NativeBoost: > > init: intarg with: chararg > <primitive: 'primitiveNativeCall' module: 'NativeBoostPlugin'> > > > > self nbCall: 'void gst_init (int * intarg, char ** chararg)' module: 'blaba' > > > -- > Best regards, > Igor Stasenko. > > > > -- > Best regards, > Igor Stasenko. > > > > -- > Best regards, > Igor Stasenko. > > > >

Dec. 10, 2013

Re: [Pharo-users] (MimeConverter forEncoding: 'quoted-printable') subclass responsibility

by Sabine KnÃ¶fel

Hi Sven, I read that Pharo 30 will be released in March 2013, so it is absolutely sufficient for me to wait a few months, I want to concentrate on features I really really need to go online officially. This will also take time til Pharo30.... Sabine On Mon, Dec 9, 2013 at 12:41 PM, Sven Van Caekenberghe-2 [via Smalltalk] < ml-node+s1294792n4728723h8(a)n4.nabble.com> wrote: > > On 09 Dec 2013, at 12:34, Sabine KnÃ¶fel <[hidden email]<http://user/SendEmail.jtp?type=node&node=4728723&i=0>> > wrote: > > > Hi Joachim, hi Sven, > > > > thank yor very much for your work! I am looking forward to use Pharo 3.0 > next year. :-) > > If you need this code earlier, I see no reason why you should not be able > to file out the QuotedPrintableMimeConverter[Tests] classes from 3.0 and > file them in in 2.0 - there are no dependencies as far as I can see. > > Maybe this could even be officially back ported to 2.0. > > > Sabine > > > > > > On Mon, Dec 9, 2013 at 11:11 AM, jtuchel [via Smalltalk] <[hidden > email]> wrote: > > Hi Sven, > > > > thanks for porting this and making it available. I will re-integrate > > your improvements in the VAST code if that's okay with you. > > > > Hey, and I am now (very indirectly) a Pharo contributor, how cool! ;-))) > > > > Joachim > > > > > > Am <a href="tel:08.12.13%2023" value="+498121323" target="_blank">08.12.13 > 23:49, schrieb Sven Van Caekenberghe: > > > > > On 08 Dec 2013, at 19:51, Sven Van Caekenberghe <[hidden email]> > wrote: > > > > > >> Next I will actually move your code to the instance side of > QuotedPrintableMimeConverter, the class where we actually need it. I am > sure I can take over your units tests as they are, which is good. > > > Done: > > > > > > > https://pharo.fogbugz.com/f/cases/4825/Quoted-printable-encoding-incomplete > > > > > > > > RESOLVED > > > > > > Slice in 3.0 inbox: > > > > > > === > > > Name: > SLICE-Issue-4825-Quoted-printable-encoding-incomplete-SvenVanCaekenberghe.1 > > > Author: SvenVanCaekenberghe > > > Time: 8 December 2013, 11:45:<a href="tel:09.148454" value="+499148454" > target="_blank">09.148454 pm > > > UUID: af015099-e48b-47f5-9553-840fca62d8e2 > > > Ancestors: > > > Dependencies: Network-MIME-SvenVanCaekenberghe.64, > NetworkTests-SvenVanCaekenberghe.92 > > > > > > A completely new implementation of QuotedPrintableMimeConverter based > on code contributed by Joachim Tuchel (thanks !) including a new set of > unit tests. > > > > > > Note that the older code lacked the encoding part and had no tests at > all. > > > === > > > > > > Sven > > > > -- > > ----------------------------------------------------------------------- > > Objektfabrik Joachim Tuchel mailto:[hidden email] > > Fliederweg 1 http://www.objektfabrik.de > > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > > Telefon: <a href="tel:%2B49%207141%2056%2010%2086%200" value=" > +4971415610860" target="_blank">+49 7141 56 10 86 0 Fax: <a > href="tel:%2B49%207141%2056%2010%2086%201" value="+4971415610861" > target="_blank">+49 7141 56 10 86 1 > > > > > > > > > > If you reply to this email, your message will be added to the discussion > below: > > > http://forum.world.st/MimeConverter-forEncoding-quoted-printable-subclass-r… > > To start a new topic under Pharo Smalltalk Users, email [hidden email] > > To unsubscribe from (MimeConverter forEncoding: 'quoted-printable') > subclass responsibility, click here. > > NAML > > > > > > View this message in context: Re: (MimeConverter forEncoding: > 'quoted-printable') subclass responsibility > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/MimeConverter-forEncoding-quoted-printable-subclass-r… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from (MimeConverter forEncoding: 'quoted-printable') > subclass responsibility, click here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/MimeConverter-forEncoding-quoted-printable-subclass-r… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 9, 2013

Re: [Pharo-users] (MimeConverter forEncoding: 'quoted-printable') subclass responsibility

by Sven Van Caekenberghe

On 09 Dec 2013, at 12:34, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi Joachim, hi Sven, > > thank yor very much for your work! I am looking forward to use Pharo 3.0 next year. :-) If you need this code earlier, I see no reason why you should not be able to file out the QuotedPrintableMimeConverter[Tests] classes from 3.0 and file them in in 2.0 - there are no dependencies as far as I can see. Maybe this could even be officially back ported to 2.0. > Sabine > > > On Mon, Dec 9, 2013 at 11:11 AM, jtuchel [via Smalltalk] <[hidden email]> wrote: > Hi Sven, > > thanks for porting this and making it available. I will re-integrate > your improvements in the VAST code if that's okay with you. > > Hey, and I am now (very indirectly) a Pharo contributor, how cool! ;-))) > > Joachim > > > Am <a href="tel:08.12.13%2023" value="+498121323" target="_blank">08.12.13 23:49, schrieb Sven Van Caekenberghe: > > > On 08 Dec 2013, at 19:51, Sven Van Caekenberghe <[hidden email]> wrote: > > > >> Next I will actually move your code to the instance side of QuotedPrintableMimeConverter, the class where we actually need it. I am sure I can take over your units tests as they are, which is good. > > Done: > > > > https://pharo.fogbugz.com/f/cases/4825/Quoted-printable-encoding-incomplete > > > > > RESOLVED > > > > Slice in 3.0 inbox: > > > > === > > Name: SLICE-Issue-4825-Quoted-printable-encoding-incomplete-SvenVanCaekenberghe.1 > > Author: SvenVanCaekenberghe > > Time: 8 December 2013, 11:45:<a href="tel:09.148454" value="+499148454" target="_blank">09.148454 pm > > UUID: af015099-e48b-47f5-9553-840fca62d8e2 > > Ancestors: > > Dependencies: Network-MIME-SvenVanCaekenberghe.64, NetworkTests-SvenVanCaekenberghe.92 > > > > A completely new implementation of QuotedPrintableMimeConverter based on code contributed by Joachim Tuchel (thanks !) including a new set of unit tests. > > > > Note that the older code lacked the encoding part and had no tests at all. > > === > > > > Sven > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:[hidden email] > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: <a href="tel:%2B49%207141%2056%2010%2086%200" value="+4971415610860" target="_blank">+49 7141 56 10 86 0 Fax: <a href="tel:%2B49%207141%2056%2010%2086%201" value="+4971415610861" target="_blank">+49 7141 56 10 86 1 > > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/MimeConverter-forEncoding-quoted-printable-subclass-r… > To start a new topic under Pharo Smalltalk Users, email [hidden email] > To unsubscribe from (MimeConverter forEncoding: 'quoted-printable') subclass responsibility, click here. > NAML > > > View this message in context: Re: (MimeConverter forEncoding: 'quoted-printable') subclass responsibility > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 9, 2013

Re: [Pharo-users] (MimeConverter forEncoding: 'quoted-printable') subclass responsibility

by Sabine KnÃ¶fel

Hi Joachim, hi Sven, thank yor very much for your work! I am looking forward to use Pharo 3.0 next year. :-) Sabine On Mon, Dec 9, 2013 at 11:11 AM, jtuchel [via Smalltalk] < ml-node+s1294792n4728698h33(a)n4.nabble.com> wrote: > Hi Sven, > > thanks for porting this and making it available. I will re-integrate > your improvements in the VAST code if that's okay with you. > > Hey, and I am now (very indirectly) a Pharo contributor, how cool! ;-))) > > Joachim > > > Am 08.12.13 23:49, schrieb Sven Van Caekenberghe: > > > On 08 Dec 2013, at 19:51, Sven Van Caekenberghe <[hidden email]<http://user/SendEmail.jtp?type=node&node=4728698&i=0>> > wrote: > > > >> Next I will actually move your code to the instance side of > QuotedPrintableMimeConverter, the class where we actually need it. I am > sure I can take over your units tests as they are, which is good. > > Done: > > > > > https://pharo.fogbugz.com/f/cases/4825/Quoted-printable-encoding-incomplete > > > > RESOLVED > > > > Slice in 3.0 inbox: > > > > === > > Name: > SLICE-Issue-4825-Quoted-printable-encoding-incomplete-SvenVanCaekenberghe.1 > > Author: SvenVanCaekenberghe > > Time: 8 December 2013, 11:45:09.148454 pm > > UUID: af015099-e48b-47f5-9553-840fca62d8e2 > > Ancestors: > > Dependencies: Network-MIME-SvenVanCaekenberghe.64, > NetworkTests-SvenVanCaekenberghe.92 > > > > A completely new implementation of QuotedPrintableMimeConverter based on > code contributed by Joachim Tuchel (thanks !) including a new set of unit > tests. > > > > Note that the older code lacked the encoding part and had no tests at > all. > > === > > > > Sven > > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:[hidden email]<http://user/SendEmail.jtp?type=node&node=4728698&i=1> > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/MimeConverter-forEncoding-quoted-printable-subclass-r… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from (MimeConverter forEncoding: 'quoted-printable') > subclass responsibility, click here<http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML<http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/MimeConverter-forEncoding-quoted-printable-subclass-r… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Dec. 9, 2013

Re: [Pharo-users] (MimeConverter forEncoding: 'quoted-printable') subclass responsibility

by Sven Van Caekenberghe

Joachim, On 09 Dec 2013, at 11:09, jtuchel(a)objektfabrik.de wrote: > Hi Sven, > > thanks for porting this and making it available. I will re-integrate your improvements in the VAST code if that's okay with you. Yes, please do, that is the least we could do back. All Pharo code is MIT licensed. > Hey, and I am now (very indirectly) a Pharo contributor, how cool! ;-))) And the code is already part of Pharo 3.0 (it went through the whole process with automatic validation by the CI system and finally integration): One way to see the changes is via github https://github.com/pharo-project/pharo-core/commit/76bf0c7bf67d5ce70f6b7043… So if you download Pharo 3.0 today should get a version 30633 or later. Youâll find your code in QuotedPrintableMimeConverter[Tests]. Thanks again ! Regards, Sven > Joachim > > > Am 08.12.13 23:49, schrieb Sven Van Caekenberghe: >> On 08 Dec 2013, at 19:51, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> Next I will actually move your code to the instance side of QuotedPrintableMimeConverter, the class where we actually need it. I am sure I can take over your units tests as they are, which is good. >> Done: >> >> https://pharo.fogbugz.com/f/cases/4825/Quoted-printable-encoding-incomplete >> >> RESOLVED >> >> Slice in 3.0 inbox: >> >> === >> Name: SLICE-Issue-4825-Quoted-printable-encoding-incomplete-SvenVanCaekenberghe.1 >> Author: SvenVanCaekenberghe >> Time: 8 December 2013, 11:45:09.148454 pm >> UUID: af015099-e48b-47f5-9553-840fca62d8e2 >> Ancestors: >> Dependencies: Network-MIME-SvenVanCaekenberghe.64, NetworkTests-SvenVanCaekenberghe.92 >> >> A completely new implementation of QuotedPrintableMimeConverter based on code contributed by Joachim Tuchel (thanks !) including a new set of unit tests. >> >> Note that the older code lacked the encoding part and had no tests at all. >> === >> >> Sven > > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > >

Dec. 9, 2013