June 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Dynabook][Morphic][TLM][Geometry] Re: [ANN] GNU Dr. Geo release 18.06

by H. Hirzel

P.S. This message was meant to be off-list. But as it went out to the list unintentionally there will be some small discussion participation from my side in case there is one :-) On 6/26/18, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hi Hilaire > > > This message is off-list as I do not have the capacity NOW to > maintain a conversation on this list. > > See my comments below > > On 6/23/18, Hilaire <hilaire(a)drgeo.eu> wrote: >> Hi Ben, >> >> They call it Dynabook in the old time... Not yet there 40 years later, >> we are damn slow. > > Yes indeed. > Actually on the hardware level and the software for reading (e-books) > and learning (teaching apps) the dynabook goal has been reached for > many years by now. > > Even the price goal has been under-cut. For 100USD you get a nice > tablet which is considerably less than the 300....400 USD people > originally thought of. > > And with OTG connections you may add a mouse and keyboard. > Raspberry Pi is also very affordable and has millions of users. > > But just using laptops and PCs is also very fine. > >> As an educator, I am all days frustrated with the computed tools we >> have, and the lack of integration. > > This is the main point. Lack of integration. And "authoring > environments" for this. > >> Anyones crazy enough to work on this challenge? > > I think I am working on this. For quite some time. At the moment I > work with Squeak though. > > But as Dr. Geo is using Morphic what I am doing may be extended to be > used there as well. > > What I am doing is not so much inventing new things but making old > things work. The solutions are actually around. They need to be > documented and used. Demos and interaction is needed. Curriculum > integration is then also quite an effort. > > I understand that you are in or around Geneva. Is that correct? > > Kind regards > Hannes > >> Hilaire >> >> >> Le 23/06/2018 Ã 02:03, Ben Coman a Ã©crit : >>> So now we need a DrGeo inside a live document providing a curriculum >>> for teachers... ;) ? >>> >>> cheers -ben >>> >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> >> >

June 26, 2018

Re: [Pharo-users] copy & paste

by Otto Behrens

Thanks for the help. Unfortunately, this does not work. We actually ran it with --encoding UTF-8 --pathenc UTF-8 --textenc UTF-8 I tried utf8, UTF8 and with just --textenc But I see our installation is relatively old. Will comment on another post here. On Sun, Jun 24, 2018 at 11:31 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > I thought that this was fixed a long time ago? > > Try running it with --textenc utf8 and see if it fixes it. > > Peter > > On Sun, Jun 24, 2018 at 11:11 AM, Otto Behrens <otto(a)finworks.biz> wrote: > >> Hi, >> >> A very annoying issue I'm having with Pharo 6.0 (running on Ubuntu 16.04) >> is that if I copy text from other applications (eg. chromium browser), I >> cannot paste it into Pharo. I get text copied in Pharo from a previous copy. >> >> To work around this, I have a "gedit" text editor open and I paste the >> text in there. After that, I cut it from the text editor and paste it into >> pharo. >> >> So, it appears as if this may be an issue with text (/encoding?). Any >> ideas? >> >> Thanks >> Otto >> > >

June 26, 2018

[Dynabook][Morphic][TLM][Geometry] Re: [ANN] GNU Dr. Geo release 18.06

by H. Hirzel

Hi Hilaire This message is off-list as I do not have the capacity NOW to maintain a conversation on this list. See my comments below On 6/23/18, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi Ben, > > They call it Dynabook in the old time... Not yet there 40 years later, > we are damn slow. Yes indeed. Actually on the hardware level and the software for reading (e-books) and learning (teaching apps) the dynabook goal has been reached for many years by now. Even the price goal has been under-cut. For 100USD you get a nice tablet which is considerably less than the 300....400 USD people originally thought of. And with OTG connections you may add a mouse and keyboard. Raspberry Pi is also very affordable and has millions of users. But just using laptops and PCs is also very fine. > As an educator, I am all days frustrated with the computed tools we > have, and the lack of integration. This is the main point. Lack of integration. And "authoring environments" for this. > Anyones crazy enough to work on this challenge? I think I am working on this. For quite some time. At the moment I work with Squeak though. But as Dr. Geo is using Morphic what I am doing may be extended to be used there as well. What I am doing is not so much inventing new things but making old things work. The solutions are actually around. They need to be documented and used. Demos and interaction is needed. Curriculum integration is then also quite an effort. I understand that you are in or around Geneva. Is that correct? Kind regards Hannes > Hilaire > > > Le 23/06/2018 Ã 02:03, Ben Coman a Ã©crit : >> So now we need a DrGeo inside a live document providing a curriculum >> for teachers... ;) ? >> >> cheers -ben >> > > -- > Dr. Geo > http://drgeo.eu > > > >

June 26, 2018

Re: [Pharo-users] Interesting Pharo Launcher feedback

by Ben Coman

On 26 June 2018 at 06:17, Tim Mackinnon <tim(a)testit.works> wrote: > Hi everyone - at tonights month UK Smalltalk Meetup, we got some nice > compliments on the state of Pharo (the participants - all ex small talkers > - although ex in so much as they fondly remembered it and wanted to use it > for something relevant now because they enjoyed it in the past). > > Anyway, one interesting comment stuck out - he had downloaded Pharo > (having used Visual Age 15+ years ago) and was a bit overwhelmed with what > laugher presented to him. He didnât hate it - but was initially a bit lost > as to what it all meant and how to startâ¦ he figured it out, but I thought > the feedback was interesting and made me think that maybe we need some form > of intro wizard to get people off to a quick start but leave them confident > enough that they might come back and try a Pharo 7 or Moose etc. > > I encouraged him to post something on here, but thoughtI would note it (as > it seems quite easy to fix) as an idea while it was fresh in my mind. > > A welcome tutorial is a good idea. And btw, the sort of idea that only comes from broader use of PharoLauncher. cheers -ben

June 26, 2018

Re: [Pharo-users] [Moose-dev] [ann] gt documenter

by Tim Mackinnon

Hi - so I managed to load up the full monty gtDocumentor into an image (a few false starts as it you try and load the full monty on top of just gtDocumentor e.g in a clean image load Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. On top of this Metacello new baseline: 'GToolkitDocumenter'; repository: 'github://feenkcom/gtoolkit-documenter/src'; load. It never completes - I gave up after 30 minutes and whining fans on a MacBook Pro. Anyway - in a completely clean image I loaded just GTookkit and then run GtDocumenter editorForText: BrToggleExamples comment. Which seemed to work fine - and showed me some buttons with different dots on them. So then I went and tried the example I really wanted to see: IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. And it just gives a blank tab in the _Pillar, _Contents and _GT tabs? The contents tab does show me pillar text unrendered. Interestingly, If I then go back to the previous editorForText example, that did work - it now also also show the same blank tabs. So it seems that something get broken? This is on OSX with the a 64bit image - labelled 6.1 - 64bit (tech preview) - so the current stable pharo for 64 bit. Is this a known issue? Tim > On 20 Jun 2018, at 02:53, Tim Mackinnon <tim(a)testit.works> wrote: > > Actually I realised it ended up on the be moose forum - hereâs what Doru replied (for any lurkers) > > > > Sent from my iPhone >> On Jun 18, 2018, at 1:21 PM, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> Guys this is really impressive! > > Thanks. > > > 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - > > 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) > Show Quoted Content > 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - > > 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) > <x-apple-msg-load-wk2:38#>2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >> >> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) > > Show Quoted Content >> 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >> >> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) > > Ok. > > >> 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? > > Indeed, this is due to the fact that loading GToolkitDocumenter does not load GToolkitVisualizer which includes GtMondrian. We are still working on finding the right dependencies balance. > > Until then, please load the whole GToolkit to get the full support. > > >> 3) You canât scroll the Diff tabs of results, only the Code tabs > > Good catch! > > > Cheers, > Doru > > Sent from my iPhone > > On 20 Jun 2018, at 02:47, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: > >> Bump (not sure this got through , and keen to know how to load the diagramming bit) >> >> Guys this is really impressive! >> >> 2 things I noticed when going through the example in a new Pharo 6.1 image (with the latest Iceberg) - >> >> 1) The example "IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillar'. â has changed to âIceLibgitRepository â¦â in the newer iceberg - so it might be worth a note in the readme (Iâll submit a PR) >> >> 2) In a clean 6.1 image I get a walkback (GtPhlowExplicitView>>mondrian DNU) when you try any of the graphical bits , making me think either the dependencies are incorrect on the Baseline (or the instruction for the example also need to mention you need to load something else - presumably Roassal? >> 3) You canât scroll the Diff tabs of results, only the Code tabs >> >> Tim >> >>> On 13 Jun 2018, at 21:57, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >>> >>> Hi, >>> >>> We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: >>> https://github.com/feenkcom/gtoolkit-documenter <https://github.com/feenkcom/gtoolkit-documenter> >>> >>> Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. >>> >>> Attached you can see a preview of how documents look like: >>> >>> <gt-documenter.png> >>> >>> At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: >>> â¢ code documentation >>> â¢ tutorials >>> â¢ interactive data notebook >>> >>> >>> Code documentation >>> ---- >>> Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: >>> https://twitter.com/feenkcom/status/973899862482866176 <https://twitter.com/feenkcom/status/973899862482866176> >>> >>> You can see a live example of documentation by inspecting the following snippet: >>> GtDocumenter editorForText: BrToggleExamples comment. >>> >>> >>> Tutorials: >>> ---- >>> Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: >>> https://twitter.com/feenkcom/status/999975333972541440 <https://twitter.com/feenkcom/status/999975333972541440> >>> >>> The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. >>> >>> The size of the preview can also be adjusted live: >>> https://twitter.com/feenkcom/status/1001152789874167808 <https://twitter.com/feenkcom/status/1001152789874167808> >>> https://twitter.com/feenkcom/status/1001407762285375490 <https://twitter.com/feenkcom/status/1001407762285375490> >>> >>> You can see a live tutorial by inspecting: >>> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. >>> >>> >>> Interactive data notebook: >>> ---- >>> A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: >>> â¢ it supports defining variables in code snippets, and >>> â¢ the execution of code shows an embedded inspector. >>> >>> For example: >>> https://twitter.com/feenkcom/status/996310432225820672 <https://twitter.com/feenkcom/status/996310432225820672> >>> https://twitter.com/feenkcom/status/1002851190475026432 <https://twitter.com/feenkcom/status/1002851190475026432> >>> >>> An example, can be seen by inspecting: >>> IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. >>> >>> >>> As always, please do let us know what you think. >>> >>> Enjoy, >>> The feenk team >>> >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> www.feenk.com <http://www.feenk.com/> >>> >>> "If you can't say why something is relevant, >>> it probably isn't." >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> >>> https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> >>

June 25, 2018

Interesting Pharo Launcher feedback

by Tim Mackinnon

Hi everyone - at tonights month UK Smalltalk Meetup, we got some nice compliments on the state of Pharo (the participants - all ex small talkers - although ex in so much as they fondly remembered it and wanted to use it for something relevant now because they enjoyed it in the past). Anyway, one interesting comment stuck out - he had downloaded Pharo (having used Visual Age 15+ years ago) and was a bit overwhelmed with what laugher presented to him. He didnât hate it - but was initially a bit lost as to what it all meant and how to startâ¦ he figured it out, but I thought the feedback was interesting and made me think that maybe we need some form of intro wizard to get people off to a quick start but leave them confident enough that they might come back and try a Pharo 7 or Moose etc. I encouraged him to post something on here, but thoughtI would note it (as it seems quite easy to fix) as an idea while it was fresh in my mind. Tim

June 25, 2018

Re: [Pharo-users] StCAD is open source

by Hilaire

Impressive! Hilaire Le 25/06/2018 Ã 02:05, askoh a Ã©critÂ : > I have just open source StCAD (MIT license) which has the code for freeCAD. > http://askoh.com/stcad > Although written in VisualWorks Smalltalk, I hope Pharo users will port it > in part or whole. -- Dr. Geo http://drgeo.eu

June 25, 2018

Re: [Pharo-users] Smalltalk Programming Competition

by horrido

Today, GemTalk Systems donated $1,000!!! Wow! We now have CA$1,970 from 12 generous contributors in 10 days. Le'ts make this happen! I've just completed the web application for the competition website. I will deploy it as soon as it appears the competition is a go. Still a lot of work ahead, but I'm pumped. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 25, 2018

Re: [Pharo-users] StCAD is open source

by Offray Vladimir Luna CÃ¡rdenas

Thanks a lot. BTW, the page at [1] looks really good for a graphical software. Maybe some of its looks could be put in the CAD software repos, just to give a glimpse of what is possible with FreeCAD and StCAD. [1] http://www.ar-cad.com/index.html Cheers, Offray On 24/06/18 19:05, askoh wrote: > Hi: > > I have just open source StCAD (MIT license) which has the code for freeCAD. > http://askoh.com/stcad > Although written in VisualWorks Smalltalk, I hope Pharo users will port it > in part or whole. > > All the best, > Aik-Siong Koh > > What is 'StCAD'? > > 'StCAD' is a basic 3D CAD framework in Smalltalk (VisualWorks 8.x). It > extends > the GF/ST 2D drawing framework into 3D. It also include 'StCAD-Geo' which is > the 3D geometric domain, 'StCAD-Math' which provides the mathematical > support > for 3D CAD and motion simulation computations, and 'StCAD-Doc' which is a > simple word processor. 'StCAD-Math' is also suitable for engineering, > scientific and business computing. The parcels are open source using MIT > License. Users can use these parcels with other private software to create > 3D > applications like motion simulation, finite element analysis, CAD, > scientific > visualization, etc. > > 'StCAD' allows users to create and manipulate assemblies, which are > collections of 3D parts. The parts are 3D solids, which can be connected by > joints, constraints, contacts, actuators, springs, dampers or forces. The > parts and connections define the structure or mechanism that the assembly is > meant to represent. Animation is possible, if the user can provide time > series > of position and orientation data for the parts. > > Users can also obtain output data in the form of plots and tables. XY plots > can be zoomed and set to equal scales. Data series available include linear > and angular displacements, velocities, accelerations and other user > generated > data. > > 'StCAD' has been used to create a freeware called 'freeCAD' which is a 3D > CAD > with Motion Simulation. For more information visit: > http://www.askoh.com > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

June 25, 2018

Re: [Pharo-users] Pharo 7 streams API

by Richard O'Keefe

Experience with Java taught me to loath ethe "do I/O by composing lots of little wrappers" approach for several reasons: - the fact that the commonest case was not the default case, so that simple obvious code was somewhere between disgracefully slow and wrong - the extra complexity needed to get it right (having to know a plethora of wrapper classes instead of just getting sensible defaults) - the poor performance. In my own Smalltalk system I hewed to the ANSI Smalltalk standard and if you do FileStream read: aFileName or FileStream write: aFileName you get a text file using the encoding set by your environment's locale, the native line ending convention, Simple, easy, and leaves Java's I/O performance in the dust. Of course wrappers are available for the rare cases when you need them, but you don't _have_ to use them. One reason this matters is that there are two ways to write a stream: s2 := WrapperClass on: s1 -- closing s2 just closes s2, not s1. s2 := WrapperClass onOwn: s1 -- closing s2 closes s1 as well And yes, both of these *are* used. On 24 June 2018 at 04:53, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Peter, > > > On 23 Jun 2018, at 15:39, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > Hi, > > > > I'm starting to familiarize myself with new streams, and one thing I've > noticed is the removal of #lineEndConvention (which I use all the time). > > > > So a statement like this > > > > aFile writeStreamDo: [ :stream | > > stream lineEndConvention: #lf. > > stream << '...' > > ]. > > > > has to be written like so > > > > aFile writeStreamDo: [ :rawStream | |stream| > > stream := (ZnNewLineWriterStream on: rawStream) forLf. > > stream << '...' > > ]. > > > > which feels very messy because I am mixing writing with the > configuration. And I don't even take account for buffered/encoded > decorators. Plus it increases the incidental complexity -- I need another > variable, and I can accidentally write to the wrong stream, etc. > > > > Would a method like #writeStream:do: (or #writeStreamTransform:do:) make > sense? E.g. > > > > aFile writeStreamTransform: [ :stream | (ZnNewLineWriterStream on: > stream) ] do: [ :stream | > > stream << '...' > > ] > > > > To separate the composition from the usage? > > > > Thanks, > > Peter > > The goals of the 'new' (they have existed for quite a while) streams is to > go from single big complex do all classes and replace that with a > composition of much simpler single purpose classes. Another goal is to > reduce the API so that it becomes easier to create new stream classes. Of > course, a consequence is that you need composition to get the functionality > you want. But I think you understand the tradeoff. > > If the mixing of configuration/setup with writing/reading bothers you, > then I would suggest using two methods. One that does only the > writing/reading assuming a limited API, and another that does the > configuration/setup, using composition. > > Note that the streams that you get already are a composition (most often a > BinaryFileStream wrapped in a Buffered stream wrapped in a > Encoding/Decoding stream). EOL translation is not a standard part of that. > But there is quite some system code that does uses EOL translation. > > Sven > > > >

June 25, 2018