- Pharo-users - lists.pharo.org

Refactor without formatting

by Vitor Medina Cruz

Hello, When I run a refactoring, Rename Method, for example, the refactoring is reformatting the code affected. Is it possible to configure Pharo to refactor without reformatting code? Depending on the refactoring, the reformat is so intrusive that make it more worth to make the refactoring by hand. Regards, Vitor

May 19, 2020

Re: [Pharo-users] FFI and absolute path to dll

by Ben Coman

On Tue, 19 May 2020 at 23:09, ASAM <vmax28575(a)gmail.com> wrote: > Of course there is a documentation for the API. > It is even an ISO standard. And if I can do that, I would also like to make > it available on GitHub. That's why it should be good. > > It is the ISO 22900-2 D-PDU-API. > I can also attach the header file. However, the PDF is provided with a > watermark. So please google. > > The API is provided by different manufacturers. > > The process is roughly the following, for Windows systems read a resitre > key > that says where the root.xml is. On Linux the pdu_api_root.xml is under > /etc. > > In the root.xml you can find where the individual suppliers have installed > their dll. With the absolute path you can now load the dll. > > Under Linux it would be a so-file which I have never seen live. I would say > 95% use it only under windos. > > Thanks for help. > > ISO22900_2.h <http://forum.world.st/file/t372350/ISO22900_2.h> > Cool. I have an example using FFIOpaqueObject here... https://blog.openinworld.com/2016/09/pharo-libclang-ffi-part-2-simple-callo… cheers -ben

May 19, 2020

Find/Replace class scoped

by Vitor Medina Cruz

Hello, Is there a way to make find replace in a class scoped way? I can do that with finder, but I figured only with package scoping. I wanna to change the name of a variable in multiple methods, and also I would like to regex replace an expression also in multiple methods. Regards, Vitor

May 19, 2020

Re: [Pharo-users] Siren 9.0 Released

by Ben Coman

On Fri, 15 May 2020 at 04:16, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks Steven this is cool to see that Siren is living and kicking. > Last year I was browsing the old site and I was sad because I thought it > was dead. > Your OSC looks better than the one in Pharo even if we used it > successfully to connect interactive tables with a HCI research group. > > If you need help to migrate from VW let us know because it would be great > to have Siren working in Pharo. > I did not see any Unit tests and the tests saved us when we migrated > Moose. Sometimes we even only kept them because they were > better than the implementation. It took us around six months and we got > free :) > And we have some contacts that would be interested in London. We could put > you in contact. > > Now just some questions and you may know the answer so I ask > > I was thinking but I may be totally wrong that it was forbidden to give VW > images and that the current license > was for personal use only. Long time ago the shrink process was removing > the compiler. Now I saw that your image is 42mb. > > Personally I do not want to download any VisualWorks distribution and sign > their licenses because I want to stay cristal clear > on ANY license and possible issues. I did not look at Visualworks since > 2008 and I feel clean and I will stay like that. > > So I imagine that Iâm not allowed to use your software. Iâm not good in > music sadly so there is no frustration from my side. > > You mention that people can use a non-commercial version of VW but this > license does not exist anymore. > Is there a 64 bits version of VW because VW7.5 starts to show its age and > on recent mac you only have 64 bits. > > > Some people may think that we are just over the top on open-source but > this is not by accident that we took the responsibility to create Pharo. > We could not distribute Moose our open-source platform so after 10 years > of hard work we had to do something. And we created Pharo. > And the problem we got were with the previous version (the non commercial) > of the Cincom license and the new one is even more restrictive. > Some friends of mine told me that some lawyers were starting to get picky > and send letters around. > So watch out. > > BTW I did not see the license of Siren on the git repo. If I may suggest > one, > BSD/MIT are nice, avoid GPL because it means that nobody serious on > Smalltalk will ever look at your system and contribute. > I recently saw an MIT/GPL comparison that I liked which was based on "What Are You Afraid Of?" * The MIT license is if youâre afraid no one will use your code; youâre making the licensing as short and non-intimidating as possible. MIT is good for projects with a small audience where you want to maximize community growth. * The GPL license is if you are afraid of someone else profiting from your work, i.e. how you would feel about that versus how likely it is to happen. GPL can be good for large infrastructure projects (Linux) to reduce money driven feature fracturization of the community. cheers -ben

May 19, 2020

Re: [Pharo-users] FFI and absolute path to dll

by ASAM

Of course there is a documentation for the API. It is even an ISO standard. And if I can do that, I would also like to make it available on GitHub. That's why it should be good. It is the ISO 22900-2 D-PDU-API. I can also attach the header file. However, the PDF is provided with a watermark. So please google. The API is provided by different manufacturers. The process is roughly the following, for Windows systems read a resitre key that says where the root.xml is. On Linux the pdu_api_root.xml is under /etc. In the root.xml you can find where the individual suppliers have installed their dll. With the absolute path you can now load the dll. Under Linux it would be a so-file which I have never seen live. I would say 95% use it only under windos. Thanks for help. ISO22900_2.h <http://forum.world.st/file/t372350/ISO22900_2.h> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 19, 2020

Re: [Pharo-users] FFI and absolute path to dll

by Ben Coman

Can you specify the API? cheers -ben On Tue, 19 May 2020 at 05:02, ASAM <vmax28575(a)gmail.com> wrote: > Oh. Thank you for your answers. Now that you say it, I remember it. I dealt > with Pharo 2 years ago. And now I come back to load and execute a DLL with > Pharo. > > Does anyone have a more detailed example of FFIOpaqueObjectis object than > in > the book (http://books.pharo.org/booklet-uffi/pdf/2020-02-12-uFFI-V1.0.1) > ? > I don't really understand it yet. > > I want to call a DLL whose API has 33 functions, 41 structures and 15 > enums. > I would like to do it right and I have to understand everything first so > that I can then decide how to implement it. > > Thank you for your help > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

May 19, 2020

Re: [Pharo-users] Siren 9.0 Released

by Serge Stinckwich

On Fri, May 15, 2020 at 4:16 AM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks Steven this is cool to see that Siren is living and kicking. > Last year I was browsing the old site and I was sad because I thought it > was dead. > Your OSC looks better than the one in Pharo even if we used it > successfully to connect interactive tables with a HCI research group. > > If you need help to migrate from VW let us know because it would be great > to have Siren working in Pharo. > I did not see any Unit tests and the tests saved us when we migrated > Moose. Sometimes we even only kept them because they were > better than the implementation. It took us around six months and we got > free :) > And we have some contacts that would be interested in London. We could put > you in contact. > > Now just some questions and you may know the answer so I ask > > I was thinking but I may be totally wrong that it was forbidden to give VW > images and that the current license > was for personal use only. Long time ago the shrink process was removing > the compiler. Now I saw that your image is 42mb. > > Personally I do not want to download any VisualWorks distribution and sign > their licenses because I want to stay cristal clear > on ANY license and possible issues. I did not look at Visualworks since > 2008 and I feel clean and I will stay like that. > > So I imagine that Iâm not allowed to use your software. Iâm not good in > music sadly so there is no frustration from my side. > > You mention that people can use a non-commercial version of VW but this > license does not exist anymore. > Is there a 64 bits version of VW because VW7.5 starts to show its age and > on recent mac you only have 64 bits. > > > Some people may think that we are just over the top on open-source but > this is not by accident that we took the responsibility to create Pharo. > We could not distribute Moose our open-source platform so after 10 years > of hard work we had to do something. And we created Pharo. > And the problem we got were with the previous version (the non commercial) > of the Cincom license and the new one is even more restrictive. > Some friends of mine told me that some lawyers were starting to get picky > and send letters around. > So watch out. > > BTW I did not see the license of Siren on the git repo. If I may suggest > one, > BSD/MIT are nice, avoid GPL because it means that nobody serious on > Smalltalk will ever look at your system and contribute. > > I found the project interesting, but without a clear licence MIT, I can be involved unfortunately. Regards, -- Serge Stinckwic h https://twitter.com/SergeStinckwich

May 19, 2020

Re: [Pharo-users] [ANN] What are good reasons to use Smalltalk?

by Richard O'Keefe

The browsers are *way* more compatible than Smalltalk systems are. I once spoke to a manager at a company I shan't name (it does not exist any more) about a new international standard being developed relating to their product (not Smalltalk). "We don't care about the standard," he replied, "we ARE the standard." Come to think of it, an open source system (again not Smalltalk) I used heavily for a while decided to ignore the developing standard. That project is dead and an attempt to revive it failed. It's not hard to build web sites that work with the major browsers. You just have to seriously want to. On Tue, 19 May 2020 at 11:01, horrido <horrido.hobbies(a)gmail.com> wrote: > It's 2020 and we're still faced with browser compatibility issues?!! > > Man, the web is really a piece o' sh*t. > > > > Offray Vladimir Luna CÃ¡rdenas-2 wrote > > Same for Firefox. I thought the poll was closed when I visited. Now I > > can check it works on Chromium. I wonder how many people tried to > > participate before but has not the proper browser to do it and not even > > a clue about that. > > > > How could be this pull be made more open and accessible? > > > > Cheers, > > > > Offray > > > > On 15/05/20 4:35 p. m., Esteban Maringolo wrote: > >> I don't know what is behind the poll system, but it doesn't work in > >> Brave browser. It simply says "Thanks for participating in the poll." > >> > >> I find the questions confusing though. > >> > >> Esteban A. Maringolo > >> > >> On Wed, May 13, 2020 at 4:43 PM Richard Kenneth Eng > >> < > > > horrido.hobbies@ > > > > wrote: > >>> > https://smalltalk.tech.blog/2020/05/13/what-are-good-reasons-to-use-smallta… > >>> > >>> Please participate in the poll. > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

May 19, 2020

Re: [Pharo-users] [ANN] What are good reasons to use Smalltalk?

by Richard Sargent

On Mon, May 18, 2020 at 4:01 PM horrido <horrido.hobbies(a)gmail.com> wrote: > It's 2020 and we're still faced with browser compatibility issues?!! > > Man, the web is really a piece o' sh*t. > Ah, you forgot the little detail about having to authorize 3-4 dozen(!) scripts from many different sources to run on your computer before the site is remotely usable. And, then you get to their programmers' definition of usable. > > > Offray Vladimir Luna CÃ¡rdenas-2 wrote > > Same for Firefox. I thought the poll was closed when I visited. Now I > > can check it works on Chromium. I wonder how many people tried to > > participate before but has not the proper browser to do it and not even > > a clue about that. > > > > How could be this pull be made more open and accessible? > > > > Cheers, > > > > Offray > > > > On 15/05/20 4:35 p. m., Esteban Maringolo wrote: > >> I don't know what is behind the poll system, but it doesn't work in > >> Brave browser. It simply says "Thanks for participating in the poll." > >> > >> I find the questions confusing though. > >> > >> Esteban A. Maringolo > >> > >> On Wed, May 13, 2020 at 4:43 PM Richard Kenneth Eng > >> < > > > horrido.hobbies@ > > > > wrote: > >>> > https://smalltalk.tech.blog/2020/05/13/what-are-good-reasons-to-use-smallta… > >>> > >>> Please participate in the poll. > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

May 18, 2020

Cant add local git repo to Iceberg

by Michael Burns

I already have a GitHub repository named FredsLunch-Pharo. The local clone of that (using shell and git) is Importing repository from /Users/Michael/Development/gitRepos/FredsLunch-Pharo > [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% git status > On branch master > Your branch is up-to-date with 'origin/master'. > Changes to be committed: > (use "git reset HEAD <file>..." to unstage) > > modified: FredsLunch.st > new file: FredsLunchCSV.st > new file: FredsLunchLunch.st > new file: FredsLunchLunchData.st > new file: FredsLunchLunchList.st > new file: FredsLunchMain.st > new file: FredsLunchMember.st > new file: FredsLunchMemberList.st > new file: FredsLunchParticipant.st > new file: FredsLunchTest.st > modified: FredsLunchTests.st > new file: ManifestFredsLunch.st > > Untracked files: > (use "git add <file>..." to include in what will be committed) > > pharo-local/ > > [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% pwd > /Users/Michael/Development/gitRepos/FredsLunch-Pharo > [graphe:~/Development/gitRepos/FredsLunch-Pharo] Michael% > The files currently in that repo were the result of doing a fileOut of each of the classes in the package. Now, Iâm trying to register that local repository in Iceberg. After I supply the pathname for the repository and press OK I get an exception window. Copy stack from debug window: > FFICallout>>loaderForArgNamed: > FFICallout>>loaderForArgNamed:indirectIndex: > FFIVariableArgument>>resolveUsing: > [ :arg2 | arg2 resolveUsing: arg1 ] in FFIFunctionSpec>>resolveUsing: in Block: [ :arg2 | arg2 resolveUsing: arg1 ] > OrderedCollection>>do: > FFIFunctionSpec>>resolveUsing: > FFICalloutMethodBuilder>>generateMethodFromSpec: > FFICalloutMethodBuilder>>generate > FFICalloutMethodBuilder>>build: > FFICalloutAPI>>function:library: > FFICalloutAPI>>function:module: > LGitRepository(LGitExternalObject)>>callUnchecked:options: > LGitRepository>>repository_open:bare_path: > [ self > repository_open: self > bare_path: self repositoryReference pathString ] in LGitRepository>>open in Block: [ self... > LGitRepository(LGitExternalObject)>>withReturnHandlerDo: > LGitRepository>>open > IceLibgitRepository>>repositoryHandle > [ | tmp1 | > self isValid > ifFalse: [ ^ #() ]. > tmp1 := self repositoryHandle allRemotes. > ^ tmp1 > collect: [ :arg1 | > | tmp3 | > tmp3 := IceGitRemote name: arg1 remoteName url: arg1 url. > tmp3 > localRepository: self; > yourself ] ] in IceLibgitRepository>>remotes in Block: [ | tmp1 |... > BlockClosure>>on:do: > IceLibgitRepository>>handleLibgitError: > IceLibgitRepository>>remotes > IcePharoPlugin class>>isAvailableFor: > [ :arg2 | arg2 isAvailableFor: arg1 ] in IcePlugin class>>allAvailableFor: in Block: [ :arg2 | arg2 isAvailableFor: arg1 ] > OrderedCollection>>select: > IcePlugin class>>allAvailableFor: > IcePluginManager>>availablePluginsFor: > IcePluginManager>>initializeRepository: > IcePluginManager class>>managerFor: > IceLibgitRepository(IceRepository)>>pluginManager > IceRepositoryCreator>>addLocalRepository > > If I try to Fuel out the exception I get another exception whose stack looks like this: > File>>openForWrite: > File>>openForWrite > File>>writeStream > File>>writeStreamDo: > FLPharo7Platform>>fileNamed:writeStreamDo: > FLSerializer>>serialize:toFileNamed: > FuelOutStackDebugAction class>>serializeTestFailureContext:toFileNamed: > FuelOutStackDebugAction>>serializeStack > FuelOutStackDebugAction>>executeAction > FuelOutStackDebugAction(DebugAction)>>execute > [ self execute ] in FuelOutStackDebugAction(DebugAction)>>asGlamourAction in Block: [ self execute ] > BlockClosure>>glamourValueWithArgs: > GLMGenericAction(GLMAction)>>actOn: > GLMGenericAction(GLMAction)>>morphicActOn: > [ | tmp2 | > (tmp2 := selector numArgs) = 0 > ifTrue: [ target perform: selector ] > ifFalse: [ tmp2 = arguments size > ifTrue: [ target perform: selector withArguments: arguments ] > ifFalse: [ target perform: selector withArguments: (arguments copyWith: arg1) ] ]. > self > showShortcut; > changed ] in ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: in Block: [ | tmp2 |... > BlockClosure>>ensure: > CursorWithMask(Cursor)>>showWhile: > ToggleMenuItemMorph(MenuItemMorph)>>invokeWithEvent: > ToggleMenuItemMorph(MenuItemMorph)>>mouseUp: > ToggleMenuItemMorph(MenuItemMorph)>>handleMouseUp: > MouseButtonEvent>>sentTo: > ToggleMenuItemMorph(Morph)>>handleEvent: > MorphicEventDispatcher>>dispatchDefault:with: > MorphicEventDispatcher>>handleMouseUp: > MouseButtonEvent>>sentTo: > [ ^ arg1 sentTo: self ] in MorphicEventDispatcher>>dispatchEvent:with: in Block: [ ^ arg1 sentTo: self ] > BlockClosure>>ensure: > MorphicEventDispatcher>>dispatchEvent:with: > ToggleMenuItemMorph(Morph)>>processEvent:using: > MorphicEventDispatcher>>dispatchDefault:with: >

May 18, 2020