- Pharo-users - lists.pharo.org

[ANN] Package Formulas

by HernÃ¡n Morales Durand

Hi everyone, I have spent some time creating a new package manager UI for Pharo 10 to simplify package finding and installation. It is a Spec application which introduces a new concept: Package Formulas. These are just annotated methods with an installation expression, so they do not depend on Metacello, Gofer, Pakbot or any other package manager. Some features are: - Package Formulas already includes a predefined set of categorized formulas. - UI allows you to install packages in bulk. - It is simple to create a script from selections. - Scripts can be decorated with pre, post, and wrapper actions. - You can request to list your own or recommended formulas by opening issues from the UI. - Then the package formula will be reviewed to avoid naming conflicts, and to prevent adding broken formulas. - The UI could be used with a custom container of your favorite, validated, isolated or private formulas. - (Currently) it does not automatically collect packages from remote repositories or query on-line servers, however, you can easily jump to browse a selected project homepage. - License is MIT. https://github.com/hernanmd/package-formulas Hope you like it. Best, HernÃ¡n

Aug. 12, 2022

ESUG 2022 Camp smalltalk

by Kasper Osterbye

Cheers Does anyone know if there will be a camp smalltalk the weekend before the conference? The page https://esug.github.io/2022-Conference/camp2022.html <https://esug.github.io/2022-Conference/camp2022.html> seems untouched. I had planned to participate. Best, Kasper

Aug. 12, 2022

UK Smalltalk User Group Meeting - 31 August 2022

by Giovanni Corriga

For this month, we'll be welcoming Instantiations' Mariano Martinez Peck and Seth Berman, who will be talking to us about asynchronous programming in Smalltalk. Whether youâre interested in starting a new project or enhancing an existing system, asynchronous programming offers a great way to optimize application speed and help ensure maintainability as complexity increases. Weâll discuss the asynchronous programming approach, why itâs important, and show live demos in the VAST Platform ( https://www.instantiations.com/vast-platform/ ) of how to get started with futures/promises, asynchronous streams/zones, and more! Mariano Martinez Peck ( https://twitter.com/martinezpeck ) is a senior systems engineer specializing in dynamic programming language software. In 2018, he joined Instantiations to further develop the VAST Platform through the addition of new frameworks, libraries and tools, as well as improving the existing code base of VAST. He is active in the Smalltalk development community, and has used his expertise to co-author numerous open source projects. Mariano has a PhD in Computer Science, and his academic research has been published across various international journals. Seth Berman ( https://twitter.com/sethloco78 ) is President & CEO of Instantiations ( https://www.instantiations.com/ ). He leads a dedicated team that tirelessly supports and enhances Instantiations' VAST Platform, while he guides expansion into new software/service areas like IoT, cloud, and edge computing solutions. Before leading Instantiations, Seth joined the company in 2011 as a software engineer working on projects ranging from advanced code editors and cryptography libraries to FFI enhancements and virtual machine implementations. Previously, he worked for the US government in a variety of domains including stochastic simulation, operations research, grid computing, and link analysis. Seth has a B.S. in Computer Science and an M.S. in Software Engineering. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/cbklbrydclbgc/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

Aug. 10, 2022

Re: Omnibase/Monibase repository removal

by Norbert Hartl

FYI As the license situation around Omnibase is unlikely to change and such a license is not an enabler for collaboration I came to the conclusion that there is no other way than to start a new OO database (what a surprise! :) ) If you are interested or want to see what will happen in the next months you can have a look at https://github.com/ApptiveGrid/Soil <https://github.com/ApptiveGrid/Soil> After half a day of work it can already serialize and partition a simple graph and store it to disk in a way it can be read back even when partitioned. Thanks to having Fuel we do not need to reinvent the wheel and have serialization/materialization done. Of course this is super simple and does not comes close to anything usable but a good start. I've also added a documentation in the github repo to describe the most important parts for me that I will target. Questions, critiques and laughs are appreciated, Norbert > Am 08.08.2022 um 15:18 schrieb Norbert Hartl <norbert(a)hartl.name>: > > To all Omnibase and Monibase users. > > It turned out that neither of those are open source. The author of the database contacted me clarifying the situation that he has the copyright and never released something open source. This means that I will remove the Omnibase repositories in few weeks from > > https://github.com/ApptiveGrid/MoniBase <https://github.com/ApptiveGrid/MoniBase> > > and > > https://github.com/pharo-nosql/OmniBase <https://github.com/pharo-nosql/OmniBase> > > I'm very sorry about that but someone just took the code 9 years before, copied it on github and put illegally an MIT license to the repository. We only want free software in our repositories and hence the above will go away. > > As we see it essential to have a good OO database in pharo we will see how much effort it will be build a small and simple OO database that can replace Omnibase. > > regards, > > Norbert

Aug. 10, 2022

Re: Using pharo in a cloud native environment

by Bob Nemec

We use Azure with our GS Seaside app for single sign-on. Once we have the Azure Graph token we then use that token for Graph API calls. Works nicely. I find MS Graph documentation to be excellent, as are all the supporting YouTube videos. Here's a short Seaside summary of the steps we use... 1 - initialRequest: -> redirect toÂ https://login.microsoftonline.com/Â with your Azure application id and redirection URL, which for use is our app URL + ?authenticateÂ 2 - initialRequest: with 'authenticate' -> send request toÂ https://login.microsoftonline.com/Â with the authentication token provided by the MS redirectÂ 3 - extract the Graph access token from the responseÂ 4 - use the Graph access token for Graph web service calls. In our case we useÂ https://graph.microsoft.com/v1.0/meÂ + Bearer <accessToken>Â to get the authenticated user's Graph ID, which we then use to find the application user object.5 - refresh the token before it expires, which is usually under and hour, by checking theÂ expires_in value We've been running this way for a few months now. Next step is to expand our use of MS Graph with Outlook, Teams and SharePoint.Â Hope that helps,Bob Nemec On Friday, August 5, 2022 at 11:39:48 a.m. EDT, Stefan Krecher <stefan.krecher(a)gmail.com> wrote: Hi,every now and thenÂ I get back to smalltalk/ pharo to find out if there's a practical way to use pharo to manage cloud resources, e.g. by calling Azure- or AWS APIs.I know there have been efforts to implement a Smalltalk binding to use the AWS API at least for some of their services but it looks like there's support for only a few, eg S3.I'd love to use pharo to build a seaside app with a nice UI to make calls to Azure and/ or AWS to start/ stop ec2 instances etc.Of course I could create Azure functions that do the API calls and then just call those functions from pharo - but I ask myself if there's a nicer way do do this ...Any recommendations?RegardsStefan

Aug. 9, 2022

Re: Omnibase/Monibase repository removal

by Yanni Chiu

You did say to get a fork, but it wasnât clear whether it was legit to use it. Iâll probably just update the license, and eventually remove the fork. On Tue, Aug 9, 2022 at 10:59 AM Norbert Hartl <norbert(a)hartl.name> wrote: > > > Am 09.08.2022 um 16:56 schrieb Yanni Chiu <yannix7db(a)gmail.com>: > > Vince, > > Thanks for this clarification. For me it means I can use my fork for the > short term. (I can walk to the exit instead of run). Since the license is > clearly not MIT, the rug can be pull at whim, so this code canât be a long > term solution. > > Yes, that's what I wrote in discord to you. Sorry for making you panicking > ;) > > Norbert > > Yanni > > > On Tue, Aug 9, 2022 at 7:13 AM <vinref(a)gmail.com> wrote: > >> Hi Norbert >> >> Posting this here in pharo-users as I am not a member of pharo-dev. >> >> I also emailed David Gorisek late last year regarding the license (for >> Dolphin Smalltalk) and this was his reply. He wrote that I needed only to >> mark the repo as a fork and attach the copyright notice: >> >> >> David Gorisek <david.gorisek@....com> >> >> 12:35 AM (9 hours ago) >> >> to me >> >> Dear Vince, >> >> OmniBase is most definitely not abandonware because it is actively being >> used, improved and even supported for paying customers. We also have a >> version for D7 but since OmniBase is used as a DB repository for STS we >> don't use Github. In my company we use a central STS repository which is >> accessible over HTTPS and we keep all our code there so I haven't had time >> to try Github yet. >> >> There are many versions and forks of OmniBase circling around because >> many people have done re-porting on their own for whatever reasons but >> these ports were not approved and are not supported by us. So, if you want >> to place your fork on Github you just need to indicate that it is a fork >> and that the original code is Copyright (c) by David Gorisek and then write >> what changes you made in your fork. >> >> Thank yout and best regards, >> >> David Gorisek >> E-RACUNI d.o.o. >> Maribor, Slovenia >> >> >> Vince >> > >

Aug. 9, 2022

Re: Omnibase/Monibase repository removal

by Norbert Hartl

> Am 09.08.2022 um 16:56 schrieb Yanni Chiu <yannix7db(a)gmail.com>: > > Vince, > > Thanks for this clarification. For me it means I can use my fork for the short term. (I can walk to the exit instead of run). Since the license is clearly not MIT, the rug can be pull at whim, so this code canât be a long term solution. > Yes, that's what I wrote in discord to you. Sorry for making you panicking ;) Norbert > Yanni > > > On Tue, Aug 9, 2022 at 7:13 AM <vinref(a)gmail.com <mailto:vinref@gmail.com>> wrote: > Hi Norbert > > Posting this here in pharo-users as I am not a member of pharo-dev. > > I also emailed David Gorisek late last year regarding the license (for Dolphin Smalltalk) and this was his reply. He wrote that I needed only to mark the repo as a fork and attach the copyright notice: > > > > David Gorisek <david.gorisek@....com> > > 12:35 AM (9 hours ago) > > to me > > Dear Vince, > > OmniBase is most definitely not abandonware because it is actively being used, improved and even supported for paying customers. We also have a version for D7 but since OmniBase is used as a DB repository for STS we don't use Github. In my company we use a central STS repository which is accessible over HTTPS and we keep all our code there so I haven't had time to try Github yet. > > There are many versions and forks of OmniBase circling around because many people have done re-porting on their own for whatever reasons but these ports were not approved and are not supported by us. So, if you want to place your fork on Github you just need to indicate that it is a fork and that the original code is Copyright (c) by David Gorisek and then write what changes you made in your fork. > > Thank yout and best regards, > > David Gorisek > E-RACUNI d.o.o. > Maribor, Slovenia > > > > Vince >

Aug. 9, 2022

Re: Omnibase/Monibase repository removal

by Yanni Chiu

Vince, Thanks for this clarification. For me it means I can use my fork for the short term. (I can walk to the exit instead of run). Since the license is clearly not MIT, the rug can be pull at whim, so this code canât be a long term solution. Yanni On Tue, Aug 9, 2022 at 7:13 AM <vinref(a)gmail.com> wrote: > Hi Norbert > > Posting this here in pharo-users as I am not a member of pharo-dev. > > I also emailed David Gorisek late last year regarding the license (for > Dolphin Smalltalk) and this was his reply. He wrote that I needed only to > mark the repo as a fork and attach the copyright notice: > > > David Gorisek <david.gorisek@....com> > > 12:35 AM (9 hours ago) > > to me > > Dear Vince, > > OmniBase is most definitely not abandonware because it is actively being > used, improved and even supported for paying customers. We also have a > version for D7 but since OmniBase is used as a DB repository for STS we > don't use Github. In my company we use a central STS repository which is > accessible over HTTPS and we keep all our code there so I haven't had time > to try Github yet. > > There are many versions and forks of OmniBase circling around because many > people have done re-porting on their own for whatever reasons but these > ports were not approved and are not supported by us. So, if you want to > place your fork on Github you just need to indicate that it is a fork and > that the original code is Copyright (c) by David Gorisek and then write > what changes you made in your fork. > > Thank yout and best regards, > > David Gorisek > E-RACUNI d.o.o. > Maribor, Slovenia > > > Vince >

Aug. 9, 2022

Re: Omnibase/Monibase repository removal

by danhunfeldz＠mail.com

This is on the Cincom site regarding OmniBase: #### Licence Agreement The OmniBase object database is provided as it is and with allÂ faults, known or unknown. The source code and other information contained in the sourceÂ code package is COPYRIGHT (C) by David Gorisek (the author).Â Portions of the source code can not be used without prior authorâsÂ written permission. OmniBase object database is licenced and sold under aÂ âper developer sitâ licence model. You may install and use an unlimited number of copies of OmniBase object database on computers, including workstations, terminals Â or other digital electronic devices to design, develop, and testÂ your software application(s), however, you must acquire and Â dedicate a license for each separate developer who is developing software using OmniBase. A license for the OmniBase object database may not be shared or used concurrently by different users. In no event shall the author be liable for any special, incidental, indirect, punitive or consequential damages whatsoever arising out of or in any way related to the use of or inability to use the OmniBase object database. By using the OmniBase object databaseÂ you accept this licence agreement and the fact that you are using the database at your own risk. The author reserves all rights notÂ expressly granted to you in this License agreement. The OmniBase object database is protected by copyright laws of the Republic of Slovenia and other intellectual property laws and treaties.

Aug. 9, 2022

Re: Omnibase/Monibase repository removal

by Konrad Hinsen

Hi Norbert, > This means that I will remove the Omnibase repositories in few weeks from > > https://github.com/ApptiveGrid/MoniBase <https://github.com/ApptiveGrid/MoniBase> > > and > > https://github.com/pharo-nosql/OmniBase <https://github.com/pharo-nosql/OmniBase> I hope you are aware that all of GitHub is archived by Software Heritage. MoniBase doesn't seem to be in there yet, but there are a few repositories called OmniBase, some of which belong to accounts associated with Pharo: https://archive.softwareheritage.org/browse/search/?q=OmniBase&with_visit=t… Deleting a repository from GitHub doesn't delete its archival copy on Software Heritage. Removal there has to be requested explicitly: https://www.softwareheritage.org/legal/content-policy/ Cheers, Konrad

Aug. 9, 2022