October 2015 - Pharo-users - lists.pharo.org

Live interaction with SQLite data from Pharo

by Offray Vladimir Luna CÃ¡rdenas

Hi, I have followed the short tutorials[1][2] on SQLite and Pharo and my connection is working properly. But I miss some liveliness on how interact with data base, particularly after seeing the video from Doru at [3], where near to min 38 he shows a connection with a Posgresql data base which after ran on the playground results in a nice vire with a tab for putting the SQL code and another for inspecting the results in a table format, even for adding data live. Is this functionality only available on Postgres or can also be enabled on a connection for SQLite and if yes, how can it be done? [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-October/033564.ht… [2] http://smalltalkhub.com/#!/~PharoExtras/NBSQLite3 [3] https://vimeo.com/97315968 Thanks, Offray

Oct. 18, 2015

Re: [Pharo-users] CiteZen and Pharo 5 / Pharo4 tests

by Stephan Eggermont

On 18-10-15 12:31, Stephan Eggermont wrote: > I've committed a version to the MetaRepoForPharo50 as I > couldn't write in the repo. In Pharo 5 it doesn't load. > I changed the build to use the MetaRepo version and build both 4 and 5 > versions. In Citezen-Reborn-StephaneDucasse.36 there is the method CZSingleAuthorDocBuilder class>>#latex that doesn't compile in Pharo 5 'latex "self latex" | builder | builder := self new fileNamed: ''rmod.bib''; toLatex; french; fieldOrder: #(#author #title #journal #booktitle #volume #pages #publisher #year # school #impactfactor #misc); "removed doi and url since they may contain _ and the generator does not handle that well for the moment." setFilteringOn; yourself. builder generateLatexFile. ' because of the space between # and school. Getting from the Syntax Error: Expecting a literal type to the compilation context is 19 levels deep on the stack. I think it would be useful to present more information than just the error message and the source when loading & compiling a package. BibPhraseLibrary twice uses #allMethodsInCategory: that should be replaced by allSelectorsInProtocol: (deprecated in Pharo 3) in Citezen-Rendering. In baseline1.7 the dependencies on Seaside/Grease/Pier/Magritte versions probably need updates. Magritte2 and Pier2 have never been tried on Pharo5 AFAIK. Smacc has moved to github. Stephan

Oct. 18, 2015

Re: [Pharo-users] Pharo messaging

by Norbert Hartl

> Am 13.10.2015 um 13:53 schrieb Torsten Bergmann <astares(a)gmx.de>: > > Hi, > > Lots of message apps in use today (WhatsApp, Telegram, ...) on phones and mobile > devices. There is "WhatsAPI" [1] - but my understanding is that it was closed for > legal/security reasons. There are other solutions like Telegram that also have an API [2]. > > What options do we have in Pharo these days: > > - to send messages from Pharo to a phone You need to use a combination of push/pull messaging. If you like to do a chat app then XMPP might be useful for this. But that only works when an app is active (foreground) on a phone. For push messaging you need to use a service that provides it. We have our own push message service running in order to do that. An alternative would be urban airship. > - receive messages from an app to control a Pharo image remotely > from a phone or communicate > I'm not sure what you mean by saying "receiving messages". You can have a pharo image installed on a server and a app could use a HTTP interface. Or did you have something special in mind? If time wouldn't be such a sparse resource we could provide a solution to this. We are building most of the pieces to handle device and image management, push services and authentication. If time permits we might build a service where apps and images register themselves and allow each of the entities contact the others available. Norbert > Thanks > T. > > [1] https://github.com/venomous0x/WhatsAPI > [2] https://core.telegram.org/ >

Oct. 18, 2015

Re: [Pharo-users] CiteZen and Pharo 5 / Pharo4 tests

by Stephan Eggermont

On 18-10-15 11:16, stepharo wrote: > Yes. > I'm sorry but I'm sick, failing also the reinstall my machine and was > trying to organise birthday party of my last son ;) No problem. I've committed a version to the MetaRepoForPharo50 as I couldn't write in the repo. In Pharo 5 it doesn't load. I changed the build to use the MetaRepo version and build both 4 and 5 versions. Stephan

Oct. 18, 2015

Re: [Pharo-users] CiteZen and Pharo 5 / Pharo4 tests

by stepharo

Yes. I'm sorry but I'm sick, failing also the reinstall my machine and was trying to organise birthday party of my last son ;) Stef Le 17/10/15 13:21, Stephan Eggermont a Ã©crit : > On 17-10-15 12:02, Peter UhnÃ¡k wrote: >> On Fri, Oct 16, 2015 at 6:50 PM, Stephan Eggermont <stephan(a)stack.nl> >> wrote: >>> Uhm, there is a green build on >>> https://ci.inria.fr/pharo-contribution/job/Citezen/ >> >> Well that's nice, but if you install it via Catalog Browser, which >> should >> be the correct way to install packages it is not working. (Maybe because >> green is development and not stable). >> > > Just promote #development to #stable and copy a configuration to the > metarepo. It is a safe-to-fail experiment. Just do it. (and perhaps > als add a #pharo5 spec & build) > > Stephan > > > >

Oct. 18, 2015

Re: [Pharo-users] Pharo and SQLite

by Hilaire

Le 15/10/2015 20:54, Mariano Martinez Peck a Ã©crit : > SQL queries or even writing mappings via a relational mapper are > always a pain. So, my comment is that if you are willing to NOT have > acid, transactions, and many other of the relational db features, you > can use a simple one-file based approach like using plain Fuel, or > even SandstoneDB with Fuel. This scales well for small/medium apps. > The good thing with this approaches is that you do not need to map > classes to tables, and avoid having write queries etc. Pros and cons, > as always. Fuel is *great* indeed to persist a tree of objects. However, one of the greatest downside compare to SQLite is the file format is not stable from one version of Fuel to another one. Is it a mandatory limitation? Hilaire -- Dr. Geo http://drgeo.eu http://google.com/+DrgeoEu

Oct. 18, 2015

Re: [Pharo-users] SQLite error on Pharo 4.

by Offray Vladimir Luna CÃ¡rdenas

Hi again, Many times happens to me that while I'm writing the question, its answer gets clear. It happened again. Thanks to the tutorial at [1], so if anyone is having similar problems just remember that the easy fix is to copy the 32 bits version of your sqlite3 binary to the same path where the image is located. [1] http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2015-January/0… Thanks for the documentation and the tutorial ;-), Offray On 17/10/15 23:04, Offray Vladimir Luna CÃ¡rdenas wrote: > Hi all, > > I have been following the instructions on [1] to install/use SQLite > with Pharo 4. But when I try to run the examples I get: "Error: > function unavailable". Attached is the trace of the error. I think is > related somehow with the fact that I have 64 and 32 bits of sqlite3 > installed in my system (Manjaro Linux) and the Native Boost is picking > the 64 bits one instead of the 32 bits. I don't know how to solve this > though, so any help will be appreciated. > > [1] http://smalltalkhub.com/#!/~PharoExtras/NBSQLite3 > > Cheers, > > Offray

Oct. 18, 2015

SQLite error on Pharo 4.

by Offray Vladimir Luna CÃ¡rdenas

Hi all, I have been following the instructions on [1] to install/use SQLite with Pharo 4. But when I try to run the examples I get: "Error: function unavailable". Attached is the trace of the error. I think is related somehow with the fact that I have 64 and 32 bits of sqlite3 installed in my system (Manjaro Linux) and the Native Boost is picking the 64 bits one instead of the 32 bits. I don't know how to solve this though, so any help will be appreciated. [1] http://smalltalkhub.com/#!/~PharoExtras/NBSQLite3 Cheers, Offray

Oct. 18, 2015

Re: [Pharo-users] Thanks for Pharo

by Adam

I was about to write something similar. I experienced strange bahavior of Playground window under Pharo 4, and before reporting it I try it under Pharo 5. It was fixed. This little thing remembers me, it is not obvius to have such a great project. So many thanks to everyone no only for this fix, but also for whole positive atmosphere around Pharo. Adam Dne PÃ¡ 16. ÅÃjna 2015 17:14:54, Jimmie Houchin napsal(a): > Sometimes conversations revolve around perceived deficiencies in Pharo. > What Pharo is missing. Or what Pharo doesn't do as well as my previous > language, my favorite language, my other language, etc... These > conversations are necessary to understand where Pharo is and to provide > understanding on where Pharo needs some work. > > However, not enough gets said sometimes for all the goodness Pharo > already provides and thanks to all of those who have contributed over > the years to Smalltalk/Pharo. > > I know sometimes we get stuck in the minutiae and lose the big picture. > > I just want to say thanks to all that have contributed to Pharo in big > and small way. Thank you. > > A special thanks to Stef, Marcus and company who have been working hard > on this all the way back when it was still Squeak. Who had a vision for > a clean, empowering, business ready, vision fulfilling Smalltalk > inspired tool we call Pharo. Thanks. > > And a thanks to Eliot and all who contribute on the VM side of things. > Enabling us to have a nicely performing and stable vm to run the Pharo > image. > > My apologies for not naming everyone who deserves thanks. I intend no > offense to anyone not named, but also deserving. Your names are included > in all the contributor documentation. Thanks. > > And while I am being thankful, which is a good habit for all of us to be > in. Being thankful not only improves the spirits of those being thanked. > But those of us who are grateful are the biggest beneficiaries. > > I want to take time to appreciate some things in Pharo that make us > appreciate having a tool like Pharo and which distinguishes itself from > other languages and environments. I think these things either > distinguish themselves either in the relative uniqueness or in quality > of their implementation. They are not necessarily distinguishing from > other Smalltalks but from other non-Smalltalk languages. > > > > Superior persistent live object environment. > This is the game changer and affects and enables all other benefits. > """I'm not complaining. I know that there is a good chance that we break > the system when improving it. I have no problem with that and I prefer a > living system with some bugs > for a while than a dead system with no bug""" Stef - Sept. 7, 2015 > > > IDE, debugging and refactoring, all live, all the time. > > > Because of the truly persistent live environment, there is no concept of > shutdown, restart. We only know hibernate and resume. This is to use OS > terms. For me this is an amazing boost to productivity. I can at any > time save my image. Even close my saved image and resume exactly where I > stopped. At any time, on any supported OS, on any machine. Powerful. > > There truly is no edit, compile, run cycle similar to other languages, > even dynamically typed languages with REPLs. > If I am not in Pharo, even if that language has an amazing notebook or > repl available. It is nothing like coding in the live environment. The > separation of editor and the compiler and/or application or VM makes > development not as smooth and fluid. Even if I can enter and execute > code in a notebook or repl to explore and learn in a version of a live > environment. I still at some point have to leave my editing environment > and write, edit and save my source code. And yes there are languages, > editors, IDEs and tools that attempt to close the gap. But no, there > still is a significant gap. The edited source code is the only thing > that persists. Everything that gets executed in the repl or notebook is > transient and will go away. > > MIT, equivalent or better licensed ecosystem. > > For me these are game changers. They set a standard by which I view any > other programming experience. Thusly all other programming experience > falls far short. > > Whenever I (we) experience a present weakness in Pharo. Remember the above. > Not only does Pharo have these distinguishing factors. I do not know of > any language or environment which even has a culture or worldview of > programming which seeks to bring these features to their favored > language or tools. > > Every time I have to restart my computer I think, Smalltalk solved this > decades ago. Ugh!!! > Where is my Pharo machine. :) > > If you have any Pharo distinctives that you appreciate and would like to > share. Reply and let us know. > What I mean by distinctive is something that Pharo (or Smalltalk) has > that is either not in other languages or is in general significantly > inferior. Especially those that other languages have no vision to ever > have. It just isn't a part of who they are. > > If we keep these things before us as we work through the tedious work of > cleaning the image, repairing fail attempts at various things. Or > anything that may be a frustration for the moment, but is temporary. > Remember what we gain and are blessed with having, that we would lose > any where else. Or at a minimum have a far inferior substitute. And look > forward to what we will have as these things become complete. The future > is ours. Let's enjoy the journey. > > Just some thoughts in my head I wanted to let out. > This is reminder to me. If any of you are blessed and inspired, that is > a plus. > > Thanks and Shalom. > > Jimmie

Oct. 17, 2015

Re: [Pharo-users] Making a ring pie chart draggrable

by Offray Vladimir Luna CÃ¡rdenas

HI, Peter and @latsabben <https://pharoproject.slack.com/messages/@latsabben> in the slack pharo channel helped me with this and I have the opportunity to help finding a bug for Roassal, so it has been a really nice morning. Here is the code snippet: http://ws.stfx.eu/KDHLP57L6LIX The bug is related with RTArc and the fact that you can not drag it more that once. Peter already told to Alexandre. This is a good example of the goodness pharo brings everyday, following the line of the last "Thanks for Pharo" thread by Jimmie. Thanks, as always :-). Offray On 17/10/15 08:00, Offray Vladimir Luna CÃ¡rdenas wrote: > Hi all :), > > When I'm starting to prototype a visualization I like to make all > elements draggable so I can test easily several layouts. This works > well for simple elements, but I can't understand well how to make it > work with complex ones like the|||RTPieBuilder. > > |Consider the code at http://ws.stfx.eu/1HC0HALHUKIC . There I create > a ring pie chart and visualize it. I would like to make it draggable > and add more elements to a the view. I have browsed the layout chapter > by Peter on Agile visualization[1], but still I don't get it. I will > made a detailed reading to catch what I'm missing and redo some > proposed exercises, but any help is greatly appreciated. > > [1] > https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Layout/0107… > > Cheers, > > Offray

Oct. 17, 2015