- Pharo-dev - lists.pharo.org

Re: [Pharo-users] [Ann] Soil v2

by stephane ducasse

Excellent news! S > On 28 Aug 2024, at 14:00, Norbert Hartl <norbert(a)hartl.name> wrote: > > We are proud to announce the availability of Soil version 2. > > This release is dated back to July because we made some bigger changes after that and all the bug fixes before that deserve a release. You can access the new release via > > https://github.com/ApptiveGrid/Soil/tree/v2 > > The changelog is available at > > https://github.com/ApptiveGrid/Soil/blob/v2/docs/changelog.md > The new features need to mature a bit but we expect to have another release in a month or two. > > Enjoy, > > Norbert + Marcus StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Aug. 29, 2024

This week (34/2024) on the Pharo Issue Tracker

by Marcus Denker

This is Aug 16 to Aug 22 (last week) # Features - Enable Calypso to use a custom navigation history #17014 https://github.com/pharo-project/pharo/pull/17014 - Add scroll to index to Lists #1586 https://github.com/pharo-spec/Spec/pull/1586 # Virtual Machine - small change in dead code elimination to considers a method with only comments empty #843 https://github.com/pharo-project/pharo-vm/pull/843 - add a comment explaining why declareCVarsIn: is empty in some subclasses #842 https://github.com/pharo-project/pharo-vm/pull/842 - DruidJIT: Adding super-instructions for jump #831 https://github.com/pharo-project/pharo-vm/pull/831 # Fixes - Fix setting of the position of the TransferMorph in #startDrag: on FTTableMorph to take into account that the eventâs position is in local coordinates #17015 https://github.com/pharo-project/pharo/pull/17015 - Fix senders broken in Calypso editors #17011 https://github.com/pharo-project/pharo/pull/17011 - Adapt test because CI uses another display scale configuration #1587 https://github.com/pharo-spec/Spec/pull/1587 # Refactoring Engine - Speed up more refactoring tests by constricting the refactoring model #17010 https://github.com/pharo-project/pharo/pull/17010

Aug. 29, 2024

Re: [Ann] Soil v2

by Martin Dias

Awesome, thanks for sharing! MartÃn El miÃ©, 28 ago 2024 a la(s) 8:00â¯a.m., Norbert Hartl (norbert(a)hartl.name) escribiÃ³: > We are proud to announce the availability of Soil version 2. > > This release is dated back to July because we made some bigger changes > after that and all the bug fixes before that deserve a release. You can > access the new release via > > [image: Soil.png] > > ApptiveGrid/Soil at v2 <https://github.com/ApptiveGrid/Soil/tree/v2> > github.com <https://github.com/ApptiveGrid/Soil/tree/v2> > <https://github.com/ApptiveGrid/Soil/tree/v2> > > The changelog is available at > > [image: Soil.png] > > Soil/docs/changelog.md at v2 Â· ApptiveGrid/Soil > <https://github.com/ApptiveGrid/Soil/blob/v2/docs/changelog.md> > github.com <https://github.com/ApptiveGrid/Soil/blob/v2/docs/changelog.md> > <https://github.com/ApptiveGrid/Soil/blob/v2/docs/changelog.md> > > The new features need to mature a bit but we expect to have another > release in a month or two. > > Enjoy, > > Norbert + Marcus >

Aug. 28, 2024

Re: [Ann] Soil v2

by Noury Bouraqadi

Well done Norbert and Marcus! Noury On Aug 28 2024, at 2:00 pm, Norbert Hartl <norbert(a)hartl.name> wrote: > We are proud to announce the availability of Soil version 2. > > This release is dated back to July because we made some bigger changes after that and all the bug fixes before that deserve a release. You can access the new release via > > Soil/docs/changelog.md at v2 Â· ApptiveGrid/Soil (https://github.com/ApptiveGrid/Soil/blob/v2/docs/changelog.md) > github.com (https://github.com/ApptiveGrid/Soil/blob/v2/docs/changelog.md) > > > > > > > > > > > > > > The new features need to mature a bit but we expect to have another release in a month or two. > > Enjoy, > > Norbert + Marcus

Aug. 28, 2024

[Ann] Soil v2

by Norbert Hartl

We are proud to announce the availability of Soil version 2. This release is dated back to July because we made some bigger changes after that and all the bug fixes before that deserve a release. You can access the new release via https://github.com/ApptiveGrid/Soil/tree/v2ï¿¼ ApptiveGrid/Soil at v2 github.com The changelog is available at https://github.com/ApptiveGrid/Soil/blob/v2/docs/changelog.mdï¿¼ Soil/docs/changelog.md at v2 Â· ApptiveGrid/Soil github.com The new features need to mature a bit but we expect to have another release in a month or two. Enjoy, Norbert + Marcus

Aug. 28, 2024

This week (33/2024) on the Pharo Issue Tracker

by Marcus Denker

# This week (33/2024) on the Pharo Issue Tracker This is Aug 9 to Aug 15 # Virtual Machine - fix warnings related to multiple include of the same header file #840 https://github.com/pharo-project/pharo-vm/pull/840 - a better comment support for Slang #838 https://github.com/pharo-project/pharo-vm/pull/838 - remove unused cast and expression #837 https://github.com/pharo-project/pharo-vm/pull/837 - Fix a lot of unused expression #832 https://github.com/pharo-project/pharo-vm/pull/832 - a first version of Slang with no type conflict and an exception if one appear #819 https://github.com/pharo-project/pharo-vm/pull/819 # Features - Fix missing users of shared pools #17004 https://github.com/pharo-project/pharo/pull/17004 - Add Shout code styler tool #17002 https://github.com/pharo-project/pharo/pull/17002 # Fixes - Fix UndeclaredVariableTest with CleanBlockClosures #16998 https://github.com/pharo-project/pharo/pull/16998 - Missing default setting in Cly navigation history configuraiton #16997 https://github.com/pharo-project/pharo/pull/16997 # Refactoring Engine - Fix for Disable push down variable from final class #17007 https://github.com/pharo-project/pharo/pull/17007 - Clean rename variable command #16993 https://github.com/pharo-project/pharo/pull/16993 - Fix Issue #16945: Refactorings -> add argument: fails on unary messages #17001 https://github.com/pharo-project/pharo/pull/17001 # Rules - Change rule option ban UI #16989 https://github.com/pharo-project/pharo/pull/16989 - Reorganisation renraku package #16934 https://github.com/pharo-project/pharo/pull/16934 # Cleanup - Add BrowserSearch dialog for Calypso #821 https://github.com/pharo-spec/NewTools/pull/821 - Remove deprecated classes #16674 https://github.com/pharo-project/pharo/pull/16674 - Remove some dead code in Calypso #16990 https://github.com/pharo-project/pharo/pull/16990 - Rename pattern classes to start with AST #17003 https://github.com/pharo-project/pharo/pull/17003 - Rename some AST abstract classes to start with AST #16946 https://github.com/pharo-project/pharo/pull/16946 - Remove references to SystemAnnouncer from Breakpoint tests #17000 https://github.com/pharo-project/pharo/pull/17000 - Rename SystemDictionary into SystemEnvironment #16999 https://github.com/pharo-project/pharo/pull/16999

Aug. 28, 2024

This week (32/2024) on the Pharo Issue Tracker

by Marcus Denker

This is the week of August 2 to August 8 # Pharo 12 - [Backport] Remove usage of cached repository from file base repositories #16930 https://github.com/pharo-project/pharo/pull/16930 # Fixes - When opening the protocol chooser, select the current protocol if not nil #819 https://github.com/pharo-spec/NewTools/pull/819 - Add Alerts to Iceberg's IceTipNewRepositoryPanel to Inform User of Incomplete Information #1834 https://github.com/pharo-vcs/iceberg/pull/1834 - Make #selectAll work before opening the presenter #1582 https://github.com/pharo-spec/Spec/pull/1582 # Features - Process Browser:â¯Make full stack the default #16983 https://github.com/pharo-project/pharo/pull/16983 - Add a setting to enable to set the ClyBrowserMorph navigation history #16982 https://github.com/pharo-project/pharo/pull/16982 # Refactoring Engine - remove RBFindAndReplace #16975 https://github.com/pharo-project/pharo/pull/16975 - Remove inspectIn: fix #11750 #16977 https://github.com/pharo-project/pharo/pull/16977 - Rename 'copy all package' to 'duplicate package' #16980 https://github.com/pharo-project/pharo/pull/16980 # Rules - Remove unused ReCollectionMessagesToExternalObjectRule #16968 https://github.com/pharo-project/pharo/pull/16968 - fix issue #12916: Autofix of Single branch condition lint removed method comment #16941 https://github.com/pharo-project/pharo/pull/16941 # Cleanup - Further Monticello sliming #16973 https://github.com/pharo-project/pharo/pull/16973 - Remove now unused CBUnifiedDiffJoinSection #800 https://github.com/pharo-spec/NewTools/pull/800 - Remove dead code from Iceberg #1836 https://github.com/pharo-vcs/iceberg/pull/1836

Aug. 27, 2024

This week (31/2024) on the Pharo Issue Tracker

by Marcus Denker

# This week (31/2024) on the Pharo Issue Tracker We will send the reports for the last weeks this week, this one is for week 31 (the week startig 26 July) # Features - Adding "OnStack replacement" feature to Reflectivity #16919 https://github.com/pharo-project/pharo/pull/16919 - Inspection tab for inspecting selectors of a Context #812 https://github.com/pharo-spec/NewTools/pull/812 - Adding command to add breakpoints in the debugger #807 https://github.com/pharo-spec/NewTools/pull/807 - Remember debugger size and position #795 https://github.com/pharo-spec/NewTools/pull/795 # Fixes - Use withAdapterDo: to set the scrolling height, courtesy of @jecisc #1579 https://github.com/pharo-spec/Spec/pull/1579 - Fix scrollTo: on SpScrollableLayout not working #1370 https://github.com/pharo-spec/Spec/pull/1370 - Fix for SettingsBrowser shows rule class and not rule text #16962 https://github.com/pharo-project/pharo/pull/16962 - 16923-ReferenceFinder-should-not-look-at-ephemeron-references #16955 https://github.com/pharo-project/pharo/pull/16955 - Avoid analyzing classes in Manifest methods while checking ReClassesHaveNoReferencesCondition #16954 https://github.com/pharo-project/pharo/pull/16954 - Provide error information directly when class definition loading fails #16898 https://github.com/pharo-project/pharo/pull/16898 - Fix keyboard focus of rename method refactoring window #16835 https://github.com/pharo-project/pharo/pull/16835 - Speed up refactoring tests by constricting refactoring models #16807 https://github.com/pharo-project/pharo/pull/16807 - Fix calypso browsing of Ring models #16802 https://github.com/pharo-project/pharo/pull/16802 - Fix Duplicate class command UX issues #16967 https://github.com/pharo-project/pharo/pull/16967 - Fix clean blocks serialization #16235 https://github.com/pharo-project/pharo/pull/16235 # Comments / Documentation - A small fix in a FileReference method comment, as suggested by @Ducasse #16966 https://github.com/pharo-project/pharo/pull/16966 - Update GitHub issue templates #16959 https://github.com/pharo-project/pharo/pull/16959 # Cleanup - Cleaning up FFI usage of SDL2 #16798 https://github.com/pharo-project/pharo/pull/16798 - Remove dead code in Monticello #16961 https://github.com/pharo-project/pharo/pull/16961 - Remove MCTool #16952 https://github.com/pharo-project/pharo/pull/16952 - Remove unused author #1833 https://github.com/pharo-vcs/iceberg/pull/1833

Aug. 26, 2024

Metacello Dependency Version Best Practice

by sean＠clipperadams.com

I recently experienced some CI problems for several of my projects because of an (IMO unnecessarily tight) version specification of XML-XPATHâs dependency on XMLParser: \`github://pharo-contributions/XML-XMLParser:v3.6.x/src\`. At minimum, it seems the dependency should be on the major version (e.g. v3), not the minor (unless Iâm missing a needed feature that was added in 3.6). More importantly though, it raises questions about what the best practice is here. In summary, it seems to me that in general itâs better to only pin versions in reaction to CI failures because pinning has significant downsides and uncertainties. Defensive pinning smells like premature optimization IMO. In more detail, partially pinning (to major or minor version)Â *by default* doesn't seem right to me for several reasons unless we're talking about a tagged release that should be reproducible because: * We have limited community resources to manage these pinnings, which create cascading conflict problems with all other dependent projects. * Pinnings seem somewhat arbitrary because oftenÂ communityÂ maintainers are not familiar enough with both projects or have enough time to do a thorough investigation. How does the maintainer know whether a particular dependency version really âworksâ with the project? Unless they are intimately familiar with both projects (and even then I wouldnât have confidence in a manual review), the best way I can think of is to rely on passing CI, and in that caseâ¦ * It seems easier to just react to CI failures; defensive pinning smells like premature optimization IMO * Partial pinning (minor or major version) will not lead to reproducible builds because the patch is floating * What does reproducibility even mean from an untagged baseline? Looking through a bunch of repos, it doesnât seem that there is consensus either way. Some specify baselines and some specific versions. p.s. for tracking the major, I like ba-stâs naming convention of v{integer} instead of adding â.xââs of unclear value

Aug. 4, 2024

Re: EU Citizen Initiative for consumers to have access to apps they purchased

by James Foster

How would this impact software that is licensed on a subscription basis? What if some functionality in the application requires a server component. Is the vendor required to provide that server component forever? Or is the vendor prohibited from building applications that have a server component? I have a deep suspicion of government regulation of business arrangements like this. James > On Aug 3, 2024, at 5:47â¯AM, David Mason <dmason(a)torontomu.ca> wrote: > > There is currently a citizen initiative to get a law in place that makers of software must not make the software become unusable after they end support. > > While this is directly about games, it has implications for things like cars, tractors, medical devices, and anything that has a significant software component. > > I encourage my EU friends and colleagues to consider signing and explaining to their friends why it's important for them to sign even if they don't play games. > > Here's a video that explains it: https://www.youtube.com/watch?v=mkMe9MxxZiI > > Here's tha petition: https://www.stopkillinggames.com/ > > Sorry this is a bit off-topic, but I think it's important to the entire software industry. > > ../Dave

Aug. 3, 2024