Re: [Pharo-users] Glorp PostgreSQL Drivers in Ubuntu 12.04
32 or 64 bits? On Thu, Dec 12, 2013 at 3:53 AM, Esteban A. Maringolo wrote: > Hi there, > > I'm moving my development server (Windows) into production (Ubuntu > 12.04) and I'm facing some issues with, among other things, the > PostgreSQL driver. > > I'm getting an: > "Error: External module not found" > > My database login is as follows: > > sampleLogin > ^Login new > database: (PostgreSQLPlatform new characterEncoding: 'utf8'); > username: 'user'; > password: 'secret'; > connectString: 'localhost_db'; > encodingStrategy: (DBXStaticEncoding newForEncoding: #utf8). > > And then just a regular accessor for the previous login: > > DatabaseAccessor forLogin: self sampleLogin. > > > How should I install the dependencies? > > I have a libpq.dll in my windows environment, and I already installed > libpq5 drivers in the server (apt-get install libpq5) > > What else should I do? > > Regards, > > Esteban A. Maringolo > >
[Pharo-users] [Pharo Trick: #0003] - halt in button
[Pharo Trick: #0003] - halt in button when you are building a user interface and you want to define the behavior of a button but you do not really know. you can use self halt or self inspect and you get an inspector/debugger on your application model Stef
Re: [Pharo-users] Shrinking Pharo 3 image
Our goal is to be able to check new configurations for all the items in the image. Now to be able to do so we should first be able to unload. While unloading we discover nasty/hidden dependencies and Pharo should not be a spaghetti. So we will continue - for example just unloading ProfStef is not easy to do cleanly. Doing so we want to add to configuration the notion of unloading. Stef PS: when I learned Envy Joseph Pelrine told me that good guys would consider their job done once their project would load and UNLOAD cleanly. And he is RIGHT. On Dec 12, 2013, at 2:25 AM, Ignacio Matías Sniechowski <0800na...@gmail.com> wrote: > 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 > wrote: > Gofer new > smalltalkhubUser: 'Pharo' project: 'SystemConfigurations'; > package: 'UnReloader'; > load. > > > > 2013/12/11 Sergi Reyner > 2013/12/11 Stéphane Ducasse > > Have a look at the ReUnloader package under my project on smalltalkhub. > > Which one? > > >
[Pharo-users] Glorp PostgreSQL Drivers in Ubuntu 12.04
Hi there, I'm moving my development server (Windows) into production (Ubuntu 12.04) and I'm facing some issues with, among other things, the PostgreSQL driver. I'm getting an: "Error: External module not found" My database login is as follows: sampleLogin ^Login new database: (PostgreSQLPlatform new characterEncoding: 'utf8'); username: 'user'; password: 'secret'; connectString: 'localhost_db'; encodingStrategy: (DBXStaticEncoding newForEncoding: #utf8). And then just a regular accessor for the previous login: DatabaseAccessor forLogin: self sampleLogin. How should I install the dependencies? I have a libpq.dll in my windows environment, and I already installed libpq5 drivers in the server (apt-get install libpq5) What else should I do? Regards, Esteban A. Maringolo
Re: [Pharo-users] Shrinking Pharo 3 image
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 wrote: > Gofer new > smalltalkhubUser: 'Pharo' project: 'SystemConfigurations'; > package: 'UnReloader'; > load. > > > > 2013/12/11 Sergi Reyner > >> 2013/12/11 Stéphane Ducasse >> >>> >>> Have a look at the ReUnloader package under my project on smalltalkhub. >>> >> >> Which one? >> >> > >
Re: [Pharo-users] InstallGemTools does not load
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.
Re: [Pharo-users] InstallGemTools does not load
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 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.pe...@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. > > > >
Re: [Pharo-users] Shrinking Pharo 3 image
Gofer new smalltalkhubUser: 'Pharo' project: 'SystemConfigurations'; package: 'UnReloader'; load. 2013/12/11 Sergi Reyner > 2013/12/11 Stéphane Ducasse > >> >> Have a look at the ReUnloader package under my project on smalltalkhub. >> > > Which one? > >
[Pharo-users] InstallGemTools does not load
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.pe...@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.
Re: [Pharo-users] Shrinking Pharo 3 image
2013/12/11 Stéphane Ducasse > > Have a look at the ReUnloader package under my project on smalltalkhub. > Which one?
Re: [Pharo-users] [Pharo-dev] [Pharo Trick: #0001] - Simple TODO list
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: #] - Short Description" to the Pharo dev AND > Pharo user > > list (see http://lists.pharo.org). Make sure to increase the trick > counter . > > > > 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 > > > > "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:p...@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
Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list
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: #] - Short Description" to the Pharo dev AND Pharo >> user >> list (see http://lists.pharo.org). Make sure to increase the trick counter >> . >> >> 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 >> >> "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. >> --- >> > signature.asc Description: OpenPGP digital signature
Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list
2013/12/11 Tudor Girba > 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
Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list
or use the Collaboractive Book: http://book.pharo-project.org Luc #Luc 2013/12/11 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 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: #] - Short Description" to the Pharo dev AND >> Pharo user >> > list (see http://lists.pharo.org). Make sure to increase the trick >> counter . >> > >> > 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 >> > >> > "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" >
Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list
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 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: #] - Short Description" to the Pharo dev AND > Pharo user > > list (see http://lists.pharo.org). Make sure to increase the trick > counter . > > > > 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 > > > > "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"
Re: [Pharo-users] [Pharo Trick: #0001] - Simple TODO list
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: #] - Short Description" to the Pharo dev AND Pharo > user > list (see http://lists.pharo.org). Make sure to increase the trick counter > . > > 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 > > "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. > --- > signature.asc Description: OpenPGP digital signature
[Pharo-users] [Pharo Trick: #0001] - Simple TODO list
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: #] - Short Description" to the Pharo dev AND Pharo user list (see http://lists.pharo.org). Make sure to increase the trick counter . 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 "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. ---
