December 2023 - Pharo-dev - lists.pharo.org

Re: [ANN] success story: ApptiveGrid

by Yanni Chiu

Thanks for all the write ups and presentations. Theyâve pointed me at some new technologies, and confirmed that Iâm not the only one thinking along certain lines. Hopefully Iâll finally get something into production in 2024. I think Soil is definitely the way forward. Once youâve stuck a traditional âdatabaseâ into your architecture, you can end up working harder to work around the constraints imposed by the database than was initially saved. Soil eliminates the âwallâ between your code and the database, so you can get objects all the way down. Yanni On Fri, Dec 29, 2023 at 12:25 PM Norbert Hartl <norbert(a)hartl.name> wrote: > Thanks to all of you for the nice comments. > > I wish you, pharo and the community all the best for 2024. In 2024 there > will be a soil release that I promised for this year but I didnât make it. > > Norbert > > > Am 14.12.2023 um 15:19 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > > Yes, this is a really nice project, the front end as well. > > > > It reminds me a bit of FileMaker, but for the web. > > > > I am hoping you have commercial success with ApptiveGrid ! > > > >> On 12 Dec 2023, at 13:02, Norbert Hartl <norbert(a)hartl.name> wrote: > >> > >> I wanted to write this for a very long time nowâ¦so finallyâ¦Iâm very > proud to announce a new success story: ApptiveGrid > >> > >> ApptiveGrid is a SaaS tool to digitalize and automatize business > processes. > >> > >> On the one hand ApptiveGrid is visual database that enables you to > model your database via web frontend. At the same time this model is > available via REST API. > >> > >> <BildschirmÂfoto 2023-12-12 um 12.39.29.png> > >> > >> On top of the data model a form creator turns your model into a form > that you can send e.g. via email to inquire data from other peopleâ¦ > >> > >> <BildschirmÂfoto 2023-12-12 um 12.40.48.png> > >> > >> On the other hand ApptiveGrid is a workflow system where you can define > your work flow in the web frontend and connect to events. These events are > either internal (resulting from a change in your data model) or external > where you can use web hooks to kick of work flows. > >> > >> <BildschirmÂfoto 2023-12-12 um 12.44.10.png> > >> > >> With the combination of both parts ApptiveGrid is able to solve many of > modern digital workflows. It enables to make it for low cost and in almost > no time which are two pretty good reasons to use it. If you want to use it > just visit: http://www.apptivegrid.de. ApptiveGrid provides a start plan > at no cost where most of the functionalities are available. If you have > additional needs just write me. For the people in the pharo community Iâm > sure we can provide a bit more on top. > >> > >> About the tech stack: > >> > >> - The business backend of ApptiveGrid is 100% pharo > >> - It uses https://github.com/svenvc/zinc components for the HTTP > frontend > >> - and https://github.com/ApptiveGrid/Soil as the persistence solution. > >> - Each user has its own database (an empty soil database is 24kb on > disk, could be made even approx. 5kb). There are over 3100 databases in the > system right now > >> - one pharo image holds multiple soil databases open and provides > memory caching for the objects > >> - routing of requests is done with haproxy connection persistence > >> - the web frontend is made with Vue.js and a pharo library that we > transpile to JS with PharoJS > >> > >> If you are interested you can also watch my ESUG videos at > https://www.youtube.com/@esugboard. All talks in the last 2 years were > about ApptiveGrid > >> > >> If you have question, donât hesitate to ask, Iâm happy to answer! > >> > >> Norbert > >> >

Dec. 30, 2023

Re: [ANN] success story: ApptiveGrid

by Norbert Hartl

Thanks to all of you for the nice comments. I wish you, pharo and the community all the best for 2024. In 2024 there will be a soil release that I promised for this year but I didnât make it. Norbert > Am 14.12.2023 um 15:19 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Yes, this is a really nice project, the front end as well. > > It reminds me a bit of FileMaker, but for the web. > > I am hoping you have commercial success with ApptiveGrid ! > >> On 12 Dec 2023, at 13:02, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> I wanted to write this for a very long time nowâ¦so finallyâ¦Iâm very proud to announce a new success story: ApptiveGrid >> >> ApptiveGrid is a SaaS tool to digitalize and automatize business processes. >> >> On the one hand ApptiveGrid is visual database that enables you to model your database via web frontend. At the same time this model is available via REST API. >> >> <BildschirmÂfoto 2023-12-12 um 12.39.29.png> >> >> On top of the data model a form creator turns your model into a form that you can send e.g. via email to inquire data from other peopleâ¦ >> >> <BildschirmÂfoto 2023-12-12 um 12.40.48.png> >> >> On the other hand ApptiveGrid is a workflow system where you can define your work flow in the web frontend and connect to events. These events are either internal (resulting from a change in your data model) or external where you can use web hooks to kick of work flows. >> >> <BildschirmÂfoto 2023-12-12 um 12.44.10.png> >> >> With the combination of both parts ApptiveGrid is able to solve many of modern digital workflows. It enables to make it for low cost and in almost no time which are two pretty good reasons to use it. If you want to use it just visit: http://www.apptivegrid.de. ApptiveGrid provides a start plan at no cost where most of the functionalities are available. If you have additional needs just write me. For the people in the pharo community Iâm sure we can provide a bit more on top. >> >> About the tech stack: >> >> - The business backend of ApptiveGrid is 100% pharo >> - It uses https://github.com/svenvc/zinc components for the HTTP frontend >> - and https://github.com/ApptiveGrid/Soil as the persistence solution. >> - Each user has its own database (an empty soil database is 24kb on disk, could be made even approx. 5kb). There are over 3100 databases in the system right now >> - one pharo image holds multiple soil databases open and provides memory caching for the objects >> - routing of requests is done with haproxy connection persistence >> - the web frontend is made with Vue.js and a pharo library that we transpile to JS with PharoJS >> >> If you are interested you can also watch my ESUG videos at https://www.youtube.com/@esugboard. All talks in the last 2 years were about ApptiveGrid >> >> If you have question, donât hesitate to ask, Iâm happy to answer! >> >> Norbert >>

Dec. 29, 2023

PhD on Pharo completion with machine learning

by stephane ducasse

Code completion for large projects and small languages https://recrutement.inria.fr/public/classic/fr/offres/2023-07003 S -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Dec. 22, 2023

Re: About Undeclared

by Martin Dias

Thanks Marcus. I wasn't aware of all the complexity behind undeclareds. Cheers, MartÃn El miÃ©, 20 dic 2023 a la(s) 12:34â¯p.m., Marcus Denker ( marcus.denker(a)inria.fr) escribiÃ³: > Hi, > > You might have seen that we have done some work related to Undeclared. > > I did some slides to explain how it worked / how it works now / what > remaining problems are / next step. > > > > >

Dec. 22, 2023

About Undeclared

by Marcus Denker

Hi, You might have seen that we have done some work related to Undeclared. I did some slides to explain how it worked / how it works now / what remaining problems are / next step.

Dec. 20, 2023

This week (50/2023) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 11 - 15769-Backport-15767--Pharo11-Fix-hasSameDefinitionAs-for-IndexedSlot #15785 https://github.com/pharo-project/pharo/pull/15785 - 15096-Backport-Pharo11-AdditionalMethodState-do-not-copy-the-AssociationsPragmas-when-growing-or-shrinking-15090 #15786 https://github.com/pharo-project/pharo/pull/15786 # Fixes - Position temp definition before first occurrence of extracted expression, and always in outer scope (fixes #14611) #15781 https://github.com/pharo-project/pharo/pull/15781 - Allow using ProfilerPresenter on code blocks #15772 https://github.com/pharo-project/pharo/pull/15772 - (Re)Moved Profile It command #1491 https://github.com/pharo-spec/Spec/pull/1491 - Fixed SubscriptionRegistry inspection freezing image #644 https://github.com/pharo-spec/NewTools/pull/644 # Rendering / Fonts - Make FreeTypeFont reuse instances #15756 https://github.com/pharo-project/pharo/pull/15756 - Fix #removeAllForFont: and #removeAllForType: on FreeTypeCache to support different scales #15752 https://github.com/pharo-project/pharo/pull/15752 # Spec - Add a Spec component list example #1488 https://github.com/pharo-spec/Spec/pull/1488 - Make sure that the first item is selected when opening a select dialâ¦ #1489 https://github.com/pharo-spec/Spec/pull/1489 # Refactoring Engine - RBCondition directlydefines -> RBDirectlyDefines #15755 https://github.com/pharo-project/pharo/pull/15755 - New Refactoring Driver for Renaming Shared Variables #15774 https://github.com/pharo-project/pharo/pull/15774 # ClassBuilder / Installer - ShiftClassInstaller: remove unused ivar #15748 https://github.com/pharo-project/pharo/pull/15748 - ClassBuilder: cleanups and #hasSameDefinitionAs: #15747 https://github.com/pharo-project/pharo/pull/15747 - 15758-duplicateClassWithNewName-leads-to-wrong-packageTag #15760 https://github.com/pharo-project/pharo/pull/15760 - ClassInstaller: clients can use #update:to: instead of #fillFor: #15765 https://github.com/pharo-project/pharo/pull/15765 - Try the ShAbstractClassChangeDetector new compare implementation #15776 https://github.com/pharo-project/pharo/pull/15776 - some small cleanups related to ClassBuilder / ClassVariables #15784 https://github.com/pharo-project/pharo/pull/15784 - ClassFactoryForTestCase #update:to: #15787 https://github.com/pharo-project/pharo/pull/15787 - Cleanup: old instance migration code (from before Shift) #15789 https://github.com/pharo-project/pharo/pull/15789 # Variables - Move-Slot-Exceptions #15743 https://github.com/pharo-project/pharo/pull/15743 - Remove the empty package Slot-Core #15757 https://github.com/pharo-project/pharo/pull/15757 - Fix: #hasSameDefinitionAs: for IndexedSlot #15767 https://github.com/pharo-project/pharo/pull/15767 - deprecate #anyUserOfClassVarNamed: #15788 https://github.com/pharo-project/pharo/pull/15788 # Fluid - Ring:â¯Use Fluid syntax for definition string #15763 https://github.com/pharo-project/pharo/pull/15763 - Ring: Migrate traits definition to fluid class syntax #15766 https://github.com/pharo-project/pharo/pull/15766 - 8055-RGClassStrategy-is-the-last-caller-of-definitionWithSlots #15775 https://github.com/pharo-project/pharo/pull/15775 # Tools - Remove change sorter #645 https://github.com/pharo-spec/NewTools/pull/645 - Creates Scopes Editor #585 https://github.com/pharo-spec/NewTools/pull/585 - 248-Definition-pane-on-class-inspector-should-let-the-user-edit-the-text-and-the-context-should-be-the-class- #636 https://github.com/pharo-spec/NewTools/pull/636 - Meta inspector tab unselection makes codepane nil #641 https://github.com/pharo-spec/NewTools/pull/641 # Cleanup - Remove not loaded packages #15793 https://github.com/pharo-project/pharo/pull/15793 - Reduce users of ChangeSet #15791 https://github.com/pharo-project/pharo/pull/15791 - Cleanup: setSourcePointer: vs sourcePointer #15762 https://github.com/pharo-project/pharo/pull/15762 - Repackage layout definitions symbols #15764 https://github.com/pharo-project/pharo/pull/15764

Dec. 18, 2023

Re: [ANN] success story: ApptiveGrid

by Tim Mackinnon

Dec. 15, 2023

Re: [ANN] success story: ApptiveGrid

by Sean Glazier

That's really great! Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Sven Van Caekenberghe <sven(a)stfx.eu> Sent: Thursday, December 14, 2023 8:19:06 AM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Cc: Pharo users users <pharo-users(a)lists.pharo.org> Subject: [Pharo-dev] Re: [ANN] success story: ApptiveGrid Yes, this is a really nice project, the front end as well. It reminds me a bit of FileMaker, but for the web. I am hoping you have commercial success with ApptiveGrid ! > On 12 Dec 2023, at 13:02, Norbert Hartl <norbert(a)hartl.name> wrote: > > I wanted to write this for a very long time nowâ¦so finallyâ¦Iâm very proud to announce a new success story: ApptiveGrid > > ApptiveGrid is a SaaS tool to digitalize and automatize business processes. > > On the one hand ApptiveGrid is visual database that enables you to model your database via web frontend. At the same time this model is available via REST API. > > <BildschirmÂfoto 2023-12-12 um 12.39.29.png> > > On top of the data model a form creator turns your model into a form that you can send e.g. via email to inquire data from other peopleâ¦ > > <BildschirmÂfoto 2023-12-12 um 12.40.48.png> > > On the other hand ApptiveGrid is a workflow system where you can define your work flow in the web frontend and connect to events. These events are either internal (resulting from a change in your data model) or external where you can use web hooks to kick of work flows. > > <BildschirmÂfoto 2023-12-12 um 12.44.10.png> > > With the combination of both parts ApptiveGrid is able to solve many of modern digital workflows. It enables to make it for low cost and in almost no time which are two pretty good reasons to use it. If you want to use it just visit: http://www.apptivegrid.de. ApptiveGrid provides a start plan at no cost where most of the functionalities are available. If you have additional needs just write me. For the people in the pharo community Iâm sure we can provide a bit more on top. > > About the tech stack: > > - The business backend of ApptiveGrid is 100% pharo > - It uses https://github.com/svenvc/zinc components for the HTTP frontend > - and https://github.com/ApptiveGrid/Soil as the persistence solution. > - Each user has its own database (an empty soil database is 24kb on disk, could be made even approx. 5kb). There are over 3100 databases in the system right now > - one pharo image holds multiple soil databases open and provides memory caching for the objects > - routing of requests is done with haproxy connection persistence > - the web frontend is made with Vue.js and a pharo library that we transpile to JS with PharoJS > > If you are interested you can also watch my ESUG videos at https://www.youtube.com/@esugboard. All talks in the last 2 years were about ApptiveGrid > > If you have question, donât hesitate to ask, Iâm happy to answer! > > Norbert >

Dec. 14, 2023

Re: [ANN] success story: ApptiveGrid

by Sven Van Caekenberghe

Yes, this is a really nice project, the front end as well. It reminds me a bit of FileMaker, but for the web. I am hoping you have commercial success with ApptiveGrid ! > On 12 Dec 2023, at 13:02, Norbert Hartl <norbert(a)hartl.name> wrote: > > I wanted to write this for a very long time nowâ¦so finallyâ¦Iâm very proud to announce a new success story: ApptiveGrid > > ApptiveGrid is a SaaS tool to digitalize and automatize business processes. > > On the one hand ApptiveGrid is visual database that enables you to model your database via web frontend. At the same time this model is available via REST API. > > <BildschirmÂfoto 2023-12-12 um 12.39.29.png> > > On top of the data model a form creator turns your model into a form that you can send e.g. via email to inquire data from other peopleâ¦ > > <BildschirmÂfoto 2023-12-12 um 12.40.48.png> > > On the other hand ApptiveGrid is a workflow system where you can define your work flow in the web frontend and connect to events. These events are either internal (resulting from a change in your data model) or external where you can use web hooks to kick of work flows. > > <BildschirmÂfoto 2023-12-12 um 12.44.10.png> > > With the combination of both parts ApptiveGrid is able to solve many of modern digital workflows. It enables to make it for low cost and in almost no time which are two pretty good reasons to use it. If you want to use it just visit: http://www.apptivegrid.de. ApptiveGrid provides a start plan at no cost where most of the functionalities are available. If you have additional needs just write me. For the people in the pharo community Iâm sure we can provide a bit more on top. > > About the tech stack: > > - The business backend of ApptiveGrid is 100% pharo > - It uses https://github.com/svenvc/zinc components for the HTTP frontend > - and https://github.com/ApptiveGrid/Soil as the persistence solution. > - Each user has its own database (an empty soil database is 24kb on disk, could be made even approx. 5kb). There are over 3100 databases in the system right now > - one pharo image holds multiple soil databases open and provides memory caching for the objects > - routing of requests is done with haproxy connection persistence > - the web frontend is made with Vue.js and a pharo library that we transpile to JS with PharoJS > > If you are interested you can also watch my ESUG videos at https://www.youtube.com/@esugboard. All talks in the last 2 years were about ApptiveGrid > > If you have question, donât hesitate to ask, Iâm happy to answer! > > Norbert >

Dec. 14, 2023

Re: [ANN] success story: ApptiveGrid

by Noury Bouraqadi

That's one cool success story. Kudos! Noury On Dec 12 2023, at 1:02 pm, Norbert Hartl <norbert(a)hartl.name> wrote: > I wanted to write this for a very long time nowâ¦so finallyâ¦Iâm very proud to announce a new success story: ApptiveGrid > > ApptiveGrid is a SaaS tool to digitalize and automatize business processes. > On the one hand ApptiveGrid is visual database that enables you to model your database via web frontend. At the same time this model is available via REST API. > > > On top of the data model a form creator turns your model into a form that you can send e.g. via email to inquire data from other peopleâ¦ > > > On the other hand ApptiveGrid is a workflow system where you can define your work flow in the web frontend and connect to events. These events are either internal (resulting from a change in your data model) or external where you can use web hooks to kick of work flows. > > > With the combination of both parts ApptiveGrid is able to solve many of modern digital workflows. It enables to make it for low cost and in almost no time which are two pretty good reasons to use it. If you want to use it just visit: http://www.apptivegrid.de. ApptiveGrid provides a start plan at no cost where most of the functionalities are available. If you have additional needs just write me. For the people in the pharo community Iâm sure we can provide a bit more on top. > About the tech stack: > - The business backend of ApptiveGrid is 100% pharo > - It uses https://github.com/svenvc/zinc components for the HTTP frontend > - and https://github.com/ApptiveGrid/Soil as the persistence solution. > - Each user has its own database (an empty soil database is 24kb on disk, could be made even approx. 5kb). There are over 3100 databases in the system right now > - one pharo image holds multiple soil databases open and provides memory caching for the objects > - routing of requests is done with haproxy connection persistence > - the web frontend is made with Vue.js and a pharo library that we transpile to JS with PharoJS > > If you are interested you can also watch my ESUG videos at https://www.youtube.com/@esugboard. All talks in the last 2 years were about ApptiveGrid > If you have question, donât hesitate to ask, Iâm happy to answer! > Norbert

Dec. 14, 2023