Re: [Pharo-users] Citizen example for manipulating a bibtex file
Hi Offray, I think I better understand what you are doing now, and how you are using STON. What I think might help you (in your use case), is to add two options: 1 - to STONWriter #keepNewlines that converts any newline inside Strings to a newline as specified by #newline: instead of encoding it as unprintable 2 - to STONReader #convertNewlines that converts any newline inside Strings to a newline as specified by #newline: instead of keeping it as is Now, 2 is already there, except that any newline read is kept as it is, while I think it would be better to convert CR, LF and CRLF to just one (to be specified). Similarly, 1 would convert CR, LF and CRLF to a single one (to be specified). Without these conversions, mixups between different line end conventions could easily happen. I think it is too much work to do this in your own models. If you think this would help, I'll put this on my todo. Sven On 18 Nov 2014, at 02:50, Offray Vladimir Luna Cárdenas off...@riseup.net wrote: Hi Sven, Sorry for my late response. The constructive comments on the list and yours in particular are very valuable to my. I was finishing some details, so only until now I have the time to implement your suggestions. The new code for custom keys on bibtex files from pharo is published at [1] (by the grace of Doru's easy publishing of playgrounds on your stfx server) [1] http://ws.stfx.eu/3CEKQQQ3NL2E By the way the article I'm writing is about a tool for open, citizen, garage research and science developed in Pharo. It is published at [2] and was stored nicely using STON[3] and is superb. To test the tool, the article was wrote on it. [2] http://mutabit.com/deltas/repos.fossil/grafoscopio/doc/tip/Docs/Es/Articulos/Libertadores/bootstrapping-objeto-investigacion.pdf [3] http://mutabit.com/deltas/repos.fossil/grafoscopio/doc/tip/Docs/Es/Articulos/Libertadores/bootstrapping-objeto-investigacion.ston [4] http://mutabit.com/deltas/repos.fossil/grafoscopio/doc/tip/Docs/Es/Articulos/Libertadores/bootstrapping-objeto-investigacion.markdown The only thing I would add to STON would be an option to support line breaks so long character sequences can be broken to make the format DVCS friendly (git, fossil, etc) and support collaboration and changes tracking. At this moment, because of the long lines in STON, the files are treated as binaries by fossil :-/. Thanks for STON and your lessons, Offray El 22/10/14 a las #4, Sven Van Caekenberghe escribió: On 22 Oct 2014, at 18:42, Offray Vladimir Luna Cárdenas off...@riseup.net wrote: Hi, Thanks again. I have a small script, using Citezen which does the trick. I can explore and modify the BibTeX File from the playground with this: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | bibFile bibliography bibStream bibOutputer | bibFile := ((FileLocator documents / 'U/Libertadores/Grafoscopio') children detect: [:each | each basename endsWith: 'bib' ]). bibliography := CZBibParser parse: bibFile contents. bibStream := '' writeStream. 1 to: (bibliography size) do: [:index | (((bibliography entries at: index) fields at: 2) key = 'shorttitle') ifTrue: [ (bibliography entries at: index) key: ((bibliography entries at: index) fields at: 2) value]. bibOutputer := CZBibtexOutputer new. bibStream nextPutAll: (bibOutputer entryToBibtexString: (bibliography entries at: index)); cr.]. bibliography. bibFile writeStreamDo: [:stream | stream nextPutAll: bibStream contents withUnixLineEndings ]. bibStream contents. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Some constructive comments about your code (smaller is always better, especially for interactive snippets): - you can change the #detect: to [ :each | each extension = #bib ] - you can iterate directly over the entries with #do: as in bibliography entries do: [ :each | .. ] which saves you the #at: index - there are handy unary shortcuts for accessing elements, like #first, #second and so on (up to #ninth) which also save you parenthesis - you can also construct strings using the idiom String streamContents: [ :bibStream | .. ] Sorry, these jumped to me when I saw your code, I hope you don't mind ;-) I will put some functionality inspired by this on my prototype this weekend. Cheers, Offray On 10/21/2014 01:20 AM, stepharo wrote: Check in the tools there is a bib writer. Stef On 21/10/14 03:33, Offray Vladimir Luna Cárdenas wrote: Thanks Stef and Damien, I have this small script as a proof of concept: === | bibFile bibliography | bibFile := ((FileLocator documents / 'U/Libertadores/Grafoscopio') children detect: [:each | each basename endsWith: 'bib' ]) contents. bibliography := CZBibParser parse: bibFile. 1 to: (bibliography size) do: [:index | (((bibliography entries at: index) fields at: 2) key =
Re: [Pharo-users] RTMultiCompositeShape + Bitmap
Hi! I just tested it in a clean image and now it works fine. Thanks a lot. Cheers, Rosario -- View this message in context: http://forum.world.st/RTMultiCompositeShape-Bitmap-tp4791277p4792375.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] Beginner of smalltalk 80 - first graphic windows and GUI - need help
Hello Hans, the standard way to build GUIs using Pharo is to use Spec. I suggest you have a look at the documentation of Spec online, do the tutorial and then you can start experimenting. The easiest way to see the Spec documentation is here: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/Spec/Spec.pier.html On Nov 26, 2014, at 10:16 AM, Hans Schueren werb...@hans-schueren.de wrote: To whom it may concern , may i ask for some help about standard graphic routines ? As a beginner i just have learned all the first level SYNTAX of smalltalk 80. Now , you can imagine , i am interested in writing little GUI windows and graphics for placing some text in the right positions. Theese are the statements i have studied from my material. Does anybody know why the statements not work? Are there any replacements for the syntax that i posted here as example ? Have a nice day HERE ARE THE EXAMPLES : | window | window := ScheduledWindow new. window component: 'Hello World' asComposedText. window open | window | window := ScheduledWindow new. window label: 'Fenster ohne Inhalt'. window minimumSize: 200 @ 100; maximumSize: 400 @ 300. window open displayOn: aGraphicsContext 1 to: 10 do: [:i| aGraphicsContext translation printString asComposedText displayOn: aGraphicsContext. aGraphicsContext translateBy: 15 @ 15] Greetings Hans The Byte Surfer --- Save our in-boxes! http://emailcharter.org --- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile
[Pharo-users] Beginner of smalltalk 80 - first graphic windows and GUI -2
interested in writing little GUI windows and graphics for placing some text in the right positions. Theese are the statements i have studied from my material. Does anybody know why the statements not work? Are there any replacements for the syntax that i posted here as example ? Have a nice day HERE ARE THE EXAMPLES : | window | window := ScheduledWindow new. window component: 'Hello World' asComposedText. window open | window | window := ScheduledWindow new. window label: 'Fenster ohne Inhalt'. window minimumSize: 200 @ 100; maximumSize: 400 @ 300. window open displayOn: aGraphicsContext 1 to: 10 do: [:i| aGraphicsContext translation printString asComposedText displayOn: aGraphicsContext. aGraphicsContext translateBy: 15 @ 15] Greetings Hans The Byte Surfer -- next part -- An HTML attachment was scrubbed... URL: http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20141126/1e0bfd5a/attachment-0001.html -- Message: 3 Date: Wed, 26 Nov 2014 16:40:28 +0100 From: Sven Van Caekenberghe s...@stfx.eu To: Any question about pharo is welcome pharo-users@lists.pharo.org Subject: Re: [Pharo-users] Citizen example for manipulating a bibtex file Message-ID: cfae9c31-4397-4bb2-a855-a99ff7f24...@stfx.eu Content-Type: text/plain; charset=windows-1252 Hi Offray, I think I better understand what you are doing now, and how you are using STON. What I think might help you (in your use case), is to add two options: 1 - to STONWriter #keepNewlines that converts any newline inside Strings to a newline as specified by #newline: instead of encoding it as unprintable 2 - to STONReader #convertNewlines that converts any newline inside Strings to a newline as specified by #newline: instead of keeping it as is Now, 2 is already there, except that any newline read is kept as it is, while I think it would be better to convert CR, LF and CRLF to just one (to be specified). Similarly, 1 would convert CR, LF and CRLF to a single one (to be specified). Without these conversions, mixups between different line end conventions could easily happen. I think it is too much work to do this in your own models. If you think this would help, I'll put this on my todo. Sven On 18 Nov 2014, at 02:50, Offray Vladimir Luna C?rdenas off...@riseup.net wrote: Hi Sven, Sorry for my late response. The constructive comments on the list and yours in particular are very valuable to my. I was finishing some details, so only until now I have the time to implement your suggestions. The new code for custom keys on bibtex files from pharo is published at [1] (by the grace of Doru's easy publishing of playgrounds on your stfx server) [1] http://ws.stfx.eu/3CEKQQQ3NL2E By the way the article I'm writing is about a tool for open, citizen, garage research and science developed in Pharo. It is published at [2] and was stored nicely using STON[3] and is superb. To test the tool, the article was wrote on it. [2] http://mutabit.com/deltas/repos.fossil/grafoscopio/doc/tip/Docs/Es/Articulos/Libertadores/bootstrapping-objeto-investigacion.pdf [3] http://mutabit.com/deltas/repos.fossil/grafoscopio/doc/tip/Docs/Es/Articulos/Libertadores/bootstrapping-objeto-investigacion.ston [4] http://mutabit.com/deltas/repos.fossil/grafoscopio/doc/tip/Docs/Es/Articulos/Libertadores/bootstrapping-objeto-investigacion.markdown The only thing I would add to STON would be an option to support line breaks so long character sequences can be broken to make the format DVCS friendly (git, fossil, etc) and support collaboration and changes tracking. At this moment, because of the long lines in STON, the files are treated as binaries by fossil :-/. Thanks for STON and your lessons, Offray El 22/10/14 a las #4, Sven Van Caekenberghe escribi?: On 22 Oct 2014, at 18:42, Offray Vladimir Luna C?rdenas off...@riseup.net wrote: Hi, Thanks again. I have a small script, using Citezen which does the trick. I can explore and modify the BibTeX File from the playground with this: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | bibFile bibliography bibStream bibOutputer | bibFile := ((FileLocator documents / 'U/Libertadores/Grafoscopio') children detect: [:each | each basename endsWith: 'bib' ]). bibliography := CZBibParser parse: bibFile contents. bibStream := '' writeStream. 1 to: (bibliography size) do: [:index | (((bibliography entries at: index) fields at: 2) key = 'shorttitle') ifTrue: [ (bibliography entries at: index) key: ((bibliography entries at: index) fields at: 2) value]. bibOutputer := CZBibtexOutputer new. bibStream nextPutAll: (bibOutputer entryToBibtexString: (bibliography entries at: index)); cr.]. bibliography. bibFile writeStreamDo: [:stream | stream nextPutAll: bibStream contents withUnixLineEndings ]. bibStream contents
Re: [Pharo-users] Beginner of smalltalk 80 - first graphic windows and GUI -2
Hello Hans My opinion is that you waste your time trying to find a smalltalk 80 just because you were used to it. Its like me returning back to GWBASIC which is the first programming language I learned to use back in 1988. Why use something so old that cant take advantage of new technology and new software ? It will only make suffer and limit you in many diffirent ways. Pharo is a modern implementation of smalltalk it does not try to stick to the past it prefers to embrace the future of smalltalk. Morphic is what Pharo has inherited from Squeak and is by far the most dominant and most mature GUI API of Pharo. New kids in the block graphic wise is Spec , Athens and Roassal.The only common amongst those three is that they are no GUI APIs but they are graphic libraries Spec is wrapper above GUI APIs currently it wraps only Morphic and makes it easier to create complex GUIs. Unlike Morphic however has a steep learning curve but pharoers prefer it because it is easier to manage. Spec documentation is in a dedicate site (Just google spec pharo and you will find it) and in Pharo For The Enterprise book. Athens is also similarly to spec a wrapper above vector graphics libraries , currently it wraps the cairo libraries and can mix with Morphic . Athens docs are in Pharo For The Enterprise book plus there is a athens interactive tutorial in smalltalkhub Roassal is part of the moose tools a collection of tools for the visualisation and organisation of code. Roassal is also a wrapper above graphic libraries , it wraps both Morphic and Athens and it has also some GUI classes . Roassal documentation is in Deep Into Pharo and I think it has a chapter in Pharo for the Enterprise. Agains all these doc are easily revealed with a simple google search. GUI wise I will say that Morphic is still the undisputed king and Spec becomes slowly very popular as a way to manage Morphic easily. There is also a new and only Morphic replacement in the works that is called Bloc but I have not tested to provide information about it. So both Morphic and Spec are viable options. Obviously Morphic is more documented because of Squeak but Spec is more actively developed right now in Pharo. Whatever you pick any problems you have you ask here and you get your questions answered and you can also ask at stackoverflow if you have already an account there. There are also other GUI and Graphic libraries inside Pharo and outside Pharo , Pharo like squeak comes with several FFIs that allows you to use external C / C++ library (C++ libraries will have to be wrapped as C libraries) which this alone give you access to pretty much every GUI libraries that popular languages use. JNIPORT is Smalltalk library that allow Pharo to use Java libraries so you can also use Swing. I am also working on a way to allow Pharo to use Python libraries , I was partly successful into creating QT GUIs via pyQT which is the python wrappers for QT GUI API . QT is probably the most powerful GUI library out and so much more than that. So in reality you have like a ton of options , everything comes with its advantages and disadvantages but for now Morphic and Spec should be enough for your needs.
[Pharo-users] Alternate browser
Hello, Do we have an installable browser for Pharo, simple but reliable as was Browser? Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu
Re: [Pharo-users] Alternate browser
Le 26/11/2014 21:30, Hilaire a écrit : Hello, Do we have an installable browser for Pharo, simple but reliable as was Browser? What is Browser? A system browser? Thierry Hilaire
Re: [Pharo-users] Alternate browser
Le 26/11/2014 21:44, Thierry Goubier a écrit : Do we have an installable browser for Pharo, simple but reliable as was Browser? What is Browser? A system browser? Yes, to browser code -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu
Re: [Pharo-users] Alternate browser
Le 26/11/2014 21:51, Hilaire a écrit : Le 26/11/2014 21:44, Thierry Goubier a écrit : Do we have an installable browser for Pharo, simple but reliable as was Browser? What is Browser? A system browser? Yes, to browser code Then Stéphane has a simple one, for minimal Pharo. I have one, AltBrowser, which is not so minimal (size-wise, it's a bit larger than the old system browser). It's installable (look for ConfigurationOfAltBrowser) and reliable enough for my coding in Pharo2, Pharo3 and Pharo4. I believe Doru could make a simple one out of GTPlayground in a short time. Sean showed some experiments a while back. Kilon is looking to see if he can build one. I believe he can :) Thierry
[Pharo-users] PEN
programming Pharo Sincerely Your Friend Hans The Byte Surfer PS. Wish to have Smalltalk 80 from XEROX 1987 here. ha ha ha On 26.11.2014 18:00, pharo-users-requ...@lists.pharo.org wrote: Send Pharo-users mailing list submissions to pharo-users@lists.pharo.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org or, via email, send a message with subject or body 'help' to pharo-users-requ...@lists.pharo.org You can reach the person managing the list at pharo-users-ow...@lists.pharo.org When replying, please edit your Subject line so it is more specific than Re: Contents of Pharo-users digest... Today's Topics: 1. Beginner of smalltalk 80 - first graphic windows andGUI - need help (Hans Schueren) 2. Re: Beginner of smalltalk 80 - first graphic windows and GUI - need help (Cl?ment Bera) 3. Re: Citizen example for manipulating a bibtex file (Sven Van Caekenberghe) -- Message: 1 Date: Wed, 26 Nov 2014 14:16:11 +0100 From: Hans Schueren werb...@hans-schueren.de To: pharo-users@lists.pharo.org pharo-users@lists.pharo.org Subject: [Pharo-users] Beginner of smalltalk 80 - first graphic windows and GUI - need help Message-ID: 5475d29b.2070...@hans-schueren.de Content-Type: text/plain; charset=utf-8; format=flowed To whom it may concern , may i ask for some help about standard graphic routines ? As a beginner i just have learned all the first level SYNTAX of smalltalk 80. Now , you can imagine , i am interested in writing little GUI windows and graphics for placing some text in the right positions. Theese are the statements i have studied from my material. Does anybody know why the statements not work? Are there any replacements for the syntax that i posted here as example ? Have a nice day HERE ARE THE EXAMPLES : | window | window := ScheduledWindow new. window component: 'Hello World' asComposedText. window open | window | window := ScheduledWindow new. window label: 'Fenster ohne Inhalt'. window minimumSize: 200 @ 100; maximumSize: 400 @ 300. window open displayOn: aGraphicsContext 1 to: 10 do: [:i| aGraphicsContext translation printString asComposedText displayOn: aGraphicsContext. aGraphicsContext translateBy: 15 @ 15] Greetings Hans The Byte Surfer -- Message: 2 Date: Wed, 26 Nov 2014 14:32:34 +0100 From: Cl?ment Bera bera.clem...@gmail.com To: Any question about pharo is welcome pharo-users@lists.pharo.org Subject: Re: [Pharo-users] Beginner of smalltalk 80 - first graphic windows and GUI - need help Message-ID: CAJrdCbWx1EfaDijSS_vY=bm23ovkbnlfqahgx-wwnjqz7js...@mail.gmail.com Content-Type: text/plain; charset=utf-8 Hello, I don't really know how to answer. Are your examples really from smalltalk-80 ? Were they running on the Xerox-D microcoded machine ? Because I don't think there are anymore smalltalk-80 available right now, nor machine that can run it. There's a smalltalk-78 running on javascript on the web but that's a bit different. Here you're on the Pharo mailing list, which is a smalltalk which has evolved during 35 years starting from smalltalk-80, so it's quite different from smalltalk-80 right now (for example, closures and exceptions were added, support for modern computers too). To use window as you are doing something like that works: | window | window := StandardWindow new. window title: 'Hello World' . window open However nowadays people use frameworks to build UIs in Pharo, not such APIs. So it depends what you want to do. 2014-11-26 14:16 GMT+01:00 Hans Schueren werb...@hans-schueren.de: To whom it may concern , may i ask for some help about standard graphic routines ? As a beginner i just have learned all the first level SYNTAX of smalltalk 80. Now , you can imagine , i am interested in writing little GUI windows and graphics for placing some text in the right positions. Theese are the statements i have studied from my material. Does anybody know why the statements not work? Are there any replacements for the syntax that i posted here as example ? Have a nice day HERE ARE THE EXAMPLES : | window | window := ScheduledWindow new. window component: 'Hello World' asComposedText. window open | window | window := ScheduledWindow new. window label: 'Fenster ohne Inhalt'. window minimumSize: 200 @ 100; maximumSize: 400 @ 300. window open displayOn: aGraphicsContext 1 to: 10 do: [:i| aGraphicsContext translation printString asComposedText displayOn: aGraphicsContext. aGraphicsContext translateBy: 15 @ 15] Greetings Hans The Byte Surfer -- next part -- An HTML attachment was scrubbed... URL: http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20141126/1e0bfd5a
Re: [Pharo-users] Alternate browser
Kilon is looking to see if he can build one. I believe he can :) I wont be building one from scratch , I like your AltBrowser too much to do that. You basically took the 4 panels of the System Browser and reduced them to 2 panels. My goal will be to reduce them to one panel .For that to happens I already forked your browser and I will adding small changes here and there. I am also interested how to make text code more visual, think of it like adding halos to code itself. I am very interested into visual coding. Other ideas I have is dynamic documentation inside the same panel and also the ability to tag methods and classes for easier browsing. So mine will be just an extension to yours. One step at a time and see where it takes me.
[Pharo-users] libevent binding for haro ?
Do someone knows about a libevent binding for Pharo , or made experiments with Pharo and this library ? After some experiment with the standard socket IO handling, I have the feeling that it cannot scale on unix and neither on windows ... TIA Regards Alain
[Pharo-users] ViDI Error: glx not supported
Hi, I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page: Gofer new smalltalkhubUser: 'YuriyTymchuk' project: 'Configuration'; configurationOf: 'Vidi'; load. #ConfigurationOfVidi asClass loadStable When I launch the ViDI option I get the error: Error: glx not supported. I'm using Gentoo Linux with NVidia Optimus graphic card, so I use bumblebee to switch to NVidia and launched pharo using optirun command like this: $ optirun pharo-ui my-image I get glxspheres64 running successfully using the same procedure. How can I activate GLX support inside the Pharo image? I noted the option System Settings FFI Path to OpenGL library (on linux) however I don't see (or I don't know) how to set this value. Thank you.
Re: [Pharo-users] Alternate browser
Le 26/11/14 21:30, Hilaire a écrit : Hello, Do we have an installable browser for Pharo, simple but reliable as was Browser? What is the problem that you have with the current one? Stef Hilaire
Re: [Pharo-users] libevent binding for haro ?
On 26 Nov 2014, at 23:48, Alain Rastoul alf.mmm@gmail.com wrote: Do someone knows about a libevent binding for Pharo , or made experiments with Pharo and this library ? After some experiment with the standard socket IO handling, I have the feeling that it cannot scale on unix and neither on windows … I would be very interested in that, yes. If I understand correctly, this is in the core what makes NodeJS scalable, or not? Marcus
Re: [Pharo-users] Alternate browser
So, I would like to look at AltBrowser, but when I try to install it in a Pharo 4 image I get an exception “ZdcPluginMissing: SSL/TLS plugin initialization failed” Any ideas on where to find it? I’ve already tried installing Zodiac, Zinc-Zodiac and SqueakSSL and still no plugin. Craig From: Pharo-users [mailto:pharo-users-boun...@lists.pharo.org] On Behalf Of kilon alios Sent: 27 November 2014 12:28 AM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Alternate browser Kilon is looking to see if he can build one. I believe he can :) I wont be building one from scratch , I like your AltBrowser too much to do that. You basically took the 4 panels of the System Browser and reduced them to 2 panels. My goal will be to reduce them to one panel .For that to happens I already forked your browser and I will adding small changes here and there. I am also interested how to make text code more visual, think of it like adding halos to code itself. I am very interested into visual coding. Other ideas I have is dynamic documentation inside the same panel and also the ability to tag methods and classes for easier browsing. So mine will be just an extension to yours. One step at a time and see where it takes me.
