- Pharo-users - lists.pharo.org

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