- Pharo-users - lists.pharo.org

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Peter UhnÃ¡k

As this is a real nuisance, I might have a partial solution â remove the repos :) Apart from contributing to pharo (which is done in clean images) I never needed reference to those repositories, so I don't see why I would need them there. So a startup script to the rescue StartupPreferencesLoader default executeAtomicItems: { StartupAction name: 'remove references to Pharo50 and Pharo50Inbox' code: [ |rx group| rx := '([0-9]{5})' asRegex. (rx matchesPrefix: Smalltalk image shortImageName) ifFalse: [ group := MCRepositoryGroup default. group repositories detect: [ :each | each location includesSubstring: 'Pharo/Pharo50Inbox/main' ] ifFound: [ :repo | group removeRepository: repo ]. "This repo is added twice for whatever reason (once main and once main/ or whatever." group repositories detect: [ :each | each location includesSubstring: 'Pharo/Pharo50/main' ] ifFound: [ :repo | group removeRepository: repo ]. group repositories detect: [ :each | each location includesSubstring: 'Pharo/Pharo50/main' ] ifFound: [ :repo | group removeRepository: repo ] ] ] runOnce: true. } Peter On Fri, Jun 3, 2016 at 8:49 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > > > On 6/3/16 2:43 AM, Otto Behrens wrote: > > For FileTree repos it is even better to just load the package (Monticello > does a good job of only loading the changed packages and we're looking at > packages already on disk) ... ... I have an extension to Metacello for > Filetree repos (it's only been around for about 3 years) that ignores > version numbers and "loads" all of the packages from the the repo (I > mentioned _this_ to Thierry:) ... which for FileTree repos is actually the > proper behavior ... I happen to be very busy at the moment so I don't have > time to blow the dust off of that extension ... the big gotcha is everyone > has to have the extension present in their image for this kind of thing to > work and AFAIK pharo is not kept up-to-date with the latest versions that I > publish on github, so I'm afraid that much breakage would ensure if only a > few individuals started using this extension ... Seems to be that we're > stuck between a rock and a had place... I wish there was a better way to > keep the Metacello distribution up-to-date in images that I have no control > over ... > > FWIW, I've found that if I manually flush the cache for each package before > I save it, I don't have to wait the minute or so for all of the repos to be > refreshed ... > > Dale, will you please publish this stuff somewhere, with dust on, as > is? (Or tell us where we can find it). > > Well let's see there's the Metacello-Cypress package is in the Metacello > repo[1] and the following should load the Cypress support into an image > with Metacello already loaded: > > Metacello image > baseline: 'Metacello'; > load: ' Cypress' > > To use the Cypress support, implement a #projectClass method in your > BaselineOf that returns MetacelloCypressBaselineProject: > > projectClass > ^MetacelloCypressBaselineProject > > and you should be in business ... > > IIRC the MetacelloCypressBaselineProject should be usable with any > BaselineOf. The only difference for Cypress is that Monticello versions are > ignored when making loading decisions --- at least that's the intent. > > Before going full scale, we'd need to add some tests for the Cypress > project and of course make sure that the Cypress support gets loaded by > default ... > > [1] > https://github.com/dalehenrich/metacello-work/tree/master/repository/Metace… > > We've just battled sooo much in this area. I wonder if it is worth it > to think again about this whole git / monticello / metacello thing. > For me, it's just too much to comprehend. As soon as I dig into > something here, I get lost within minutes. > > I believe the complexity has to do with trying to maintain too many > different ways of solving the problem. We are trying to keep things > (Monticello / Metacello) working with or without git or filetree or > whatever else people are using. > > I would really like to do merging in git and just have a fast and > simple way of loading / compiling into an image (and GemStone). I do > not want a package cache, 3 way merging and all the other things, > because it makes what I end up with unpredictable. But you see, other > people want to work in other ways, which I understand. My perception > is that the result is messy. > > We should try to strive more towards *fewer* ways of doing things, > without killing innovation to try different ways. It feels as if there > are enormous, yet very incomplete silos of efforts to solve problems. > > > I basically agree with everything you say here. > > I added the Cypress package support several years ago when Richard Sargent > wrote a Cypress implementation for the base GemStone[2], so we've had the > bits a pieces necessary for a cleaner simpler mechanism for a while at > least for GemStone ... > > I would like to distinguish between Cypress and FileTree. > > FileTree was created (by you:) to support disk-based repos while > maintaining full Monticello compatibility. Over the years I've (stubbornly) > maintained that the Monticello meta data be preserved in FileTree > repositories. By preserving Monticello meta data, the packages can be > easily moved between FileTree and SmalltalkHub, etc. while faithfully > preserving the Monticello ancestry. Maintaining Monticello meta data is > critical for folks to be able to "dip their toe into the git pool" while > preserving Monticello ancestry. > > When I say "Cypress" (as opposed to FileTree), I think of a stripped down > implementation of FileTree where Monticello meta data is not stored on disk > and, perhaps more importantly the package loading code, in-image package > management and tool support is also stripped down to support a simple model > where package history and version numbers are non-existent. This particular > model is aimed at projects that spend their entire lives in "git" repos and > there is no desire, nor need to keep a parallel ancestry in the Monticello > meta data and I think that what you are asking for ... in fact with Cypress > package names do not need any package meta data ... the SHA of the commit > is all that is needed to uniquely identify packages [in tODE the > development environment is focused on the Metacello project and the package > is not really the focus, so right now the Metacello registry is capable of > tracking the SHA of the commit used to load a _project_, so I don't think > that a package needs to have any additional meta data like UUID or version > number or and the SHA of the commit at _project_ load time is all that is > needed] > > For Pharo, I think that GitFileTree provides you with support for a > metadata-less disk footprint, but the in-image support is still based on > Monticello --- at least that's what I understand about GitFileTree, since > up to now I haven't spent any time working with it ... that will change > this summer as I am working on a project in Pharo5. GitFileTree is an > extension of the "FileTree model" in that it is compatible with the current > in-image tools that all pretty much expect Monticello packages --- this > approach is needed because it is a big job to incorporate an alternate > source code management scheme in the in-image tools across the board ... If > one were to switch the pharo tool focus from the _package_ (Monticello > Browser) to the the _project_ (Project Browser) there would be additional > work to be done: 'save' of project means save all dirty packages in project > as well as a `git commit`, 'diff' of project means show changes for all > dirty packages in project, and there would be analogs for 'load', 'revert', > 'history' etc. > > For GemStone, I have written tODE to be git-aware from the beginning and I > have built tools to support Cypress package management as well[3] although > they _are_ 3 years old and would deserve additional work ... Internally we > are seriously considering adding Cypress support to the base image for the > GemStone 3.4 release and of course in the process of doing that work, I > assume that we'd make the code available for use in 3.2 and 3.3 as well. > > In the short term I think that a combination of Cypress package support > from Metacello, GitFileTree in Pharo and the updating of the Cypress tools > for tODE will allow you to share packages between Pharo and GemStone > without needing to create and maintain Monticello meta data ... in the > midterm Cypress support is slated for this year and if necessary I can make > changes to the current tODE FileTree implementation to allow the writing of > metadata-less packages -- I think GitFileTree records whether or not a > repository is metadata-less in a repository property file that I can use if > necessary ... > > Does this make sense? > > Dale > > [2] https://github.com/rjsargent/CypressReferenceImplementation > [3] > https://github.com/dalehenrich/tode/tree/master/repository/Topez-Server-Cyp… > >

July 10, 2016

Re: [Pharo-users] Disabling welcome window

by Peter UhnÃ¡k

Very delayed thanks :) Somehow I missed your response. Thanks! Peter On Wed, May 18, 2016 at 12:32 AM, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: > World submorphs > > select: [ :sm | > > sm isSystemWindow and: [ sm label = > PharoWelcomePage title ] > > ] > > thenDo: [ :window | window delete ]. > > > > Best regards, > > Henrik > > > > *From:* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *On > Behalf Of *Peter UhnÃ¡k > *Sent:* Wednesday, May 18, 2016 12:20 AM > *To:* Pharo-Users List <pharo-users(a)lists.pharo.org> > *Subject:* [Pharo-users] Disabling welcome window > > > > Is there a clean way how to close or not open the Pharo 5.0 welcome window? > > > > Short of going through the stack and closing it (courtesy of Cyril) > > > > (SystemWindow allInstances select: [ :w | w labelString > includesSubstring: 'Welcome' ]) do: #delete > > > > Thanks, > > Peter >

July 10, 2016

Re: [Pharo-users] SQLite + Pharo

by Bernardo Ezequiel Contreras

Mark, im using this Metacello new smalltalkhubUser: 'TorstenBergmann' project: 'UDBC'; configuration: 'UDBC'; version: #bleedingEdge; load. on pharo 5 On Sat, Jul 9, 2016 at 7:41 AM, Mark Bratcher <mdbratch(a)gmail.com> wrote: > Is UDBCSQLite3 available somewhere? I've tried Google and it turns up > nothing but maybe two threads discussing it. > > > > On 7/9/2016 6:33 AM, Esteban Lorenzano wrote: > >> On 09 Jul 2016, at 11:42, Pierce Ng <pierce(a)samadhiweb.com> wrote: >>> >>> On Wed, Jul 06, 2016 at 11:24:51AM +0200, Hilaire wrote: >>> >>>> I guess UDBC is for Pharo 5, and for Pharo 4 it is the NB version, >>>> right? >>>> >>> Yes. >>> >>> I guess both version has the same public interface. >>>> >>> Yes, but. :-) Some bits of NBSQLite3, notably the online backup API but >>> possibly other small stuff, isn't in UDBCSQLite3 yet. >>> >>> After making UDBCSQLite3 work with Glorp on Pharo 5, I've >>> decided/realized that >>> I don't have time to maintain both it and NBSQLite3. I'm leaving >>> NBSQLite3 more >>> or less as is, and continue to work on UDBCSQLite3. >>> >> +1 >> I think this is the way to go :) >> >> Pierce >>> >>> >> > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

July 9, 2016

Re: [Pharo-users] Database band reports...

by Ben Coman

I had a poke around and couldn't find any API documentation. If you can find this someone could give a more considered opinion. If you store your data in a relational database, perhaps you could use a third party report generator like Pentaho or JasperReports[1]. I believe these are designed to be bolted on to applications, so perhaps they'll have a more accessible API. From Pharo you should be able to use a REST based API [2] of Pentaho. It apparently does band reports [3]. [1] http://www.innoventsolutions.com/comparison-matrix.html [2] https://help.pentaho.com/Documentation/6.0/0R0/070 [3] http://wiki.pentaho.com/display/Reporting/band Disclaimer - This is just info I found for curiosity. I haven't used any of these. cheers -ben P.S. Band reports features like the table in [1] would be a great addition to the Pharo ecosystem. On Sat, Jul 9, 2016 at 2:29 AM, anonyme <sitepublique(a)free.fr> wrote: > Ok, thanks you for responses. A band report is more than a PDF generator... > It's a queries manager with varaible management facilities : details queries > connect to master query, and you can manage sub report bottlenek into other > master reports. The band report generator has the ability to manage page > organisation, and editor add text styled... I can't use samlltalk database > without a good band report component. > > But argos band report displayed under look to be fine, if there is a > possibility to use it with smaltalk... It looks like argos is a server. But > what about interfaces with smalltalk ? > > cheers - Patrick > > > > Le 08/07/2016 Ã 16:08, Ben Coman a Ã©crit : >> >> On Fri, Jul 8, 2016 at 5:45 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi patrick >>> >>> What is a band report? >> >> http://webhelp.evisions.com/HelpFiles/Argos/4.2/en/Content/10101001.html >> >> Sorry Patrick. Pharo has such a GUI report generator. But Artefact >> seems to provide similar features via code... >> >> https://ci.inria.fr/pharo-contribution/view/Books/job/EnterprisePharoBook/l… >> >> cheers -ben >> >>> Did you check Artefact because you can generate pdf with Artefact. >>> >>> Stef >>> >>> >>> >>>> Hi, >>>> >>>> My previous message stayed without responses, so I published it agin... >>>> I'm >>>> looking for a database band report component. The goal is to build >>>> quickly >>>> a >>>> PDF report from SQL requests. An exemple is Lazreport, this is a >>>> tutorial >>>> <http://wiki.lazarus.freepascal.org/LazReport_Tutorial> . >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://forum.world.st/Database-band-reports-tp4905523.html >>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>>> >>>> >>> >> > >

July 9, 2016

Re: [Pharo-users] [Pharo-dev] Spec Tutorial First chapter

by Yuriy Tymchuk

Yes, tutorials about UI frameworks are uber-important. Thank Johan!! P.S. we need some cool documentation meta framework, because now I have documentation about my stuff in 3 places: Comments, Pharo Help & Github ReadMe. > On 09 Jul 2016, at 12:39, stepharo <stepharo(a)free.fr> wrote: > > Tx :) > > This is great that Johan is really pushing because my energy is low. > > Stef > > Le 9/7/16 Ã 10:22, Sven Van Caekenberghe a Ã©crit : >>> On 08 Jul 2016, at 19:50, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi >>> >>> Johan Fabry is writing a great tutorial (and this is cool to see all the material I gathered or wrote with him in the past) >>> >>> to take such great form. >>> >>> I attached the first chapter. I will post the chapter one by one once I review them (so far I have nothing to do - great feeling). >>> >>> Well done Johan! >>> >>> Stef >>> >>> <FirstContact.pdf> >> Great work, thank you ! >> >> Books make a lot of difference, even today. >> >> >> > >

July 9, 2016

Re: [Pharo-users] SQLite + Pharo

by Hilaire

Le 09/07/2016 11:42, Pierce Ng a Ã©crit : > After making UDBCSQLite3 work with Glorp on Pharo 5, I've decided/realized that > I don't have time to maintain both it and NBSQLite3. I'm leaving NBSQLite3 more > or less as is, and continue to work on UDBCSQLite3. It is fine and your contribution is nice! I am in the process of learning how to use sqlite3 (itself and with Pharo) and it is coincidence my working image is Pharo4, but later it will move to newer Pharo5. One question on the top of my head, is how you deal with concurrent access to sqlite tables from seaside sessionS. Is the solution as naive as a waiting loop for the database to become accessible ? Thanks Hilaire -- Dr. Geo http://drgeo.eu

July 9, 2016

Re: [Pharo-users] SQLite + Pharo

by stepharo

Le 9/7/16 Ã 12:33, Esteban Lorenzano a Ã©crit : >> On 09 Jul 2016, at 11:42, Pierce Ng <pierce(a)samadhiweb.com> wrote: >> >> On Wed, Jul 06, 2016 at 11:24:51AM +0200, Hilaire wrote: >>> I guess UDBC is for Pharo 5, and for Pharo 4 it is the NB version, right? >> Yes. >> >>> I guess both version has the same public interface. >> Yes, but. :-) Some bits of NBSQLite3, notably the online backup API but >> possibly other small stuff, isn't in UDBCSQLite3 yet. >> >> After making UDBCSQLite3 work with Glorp on Pharo 5, I've decided/realized that >> I don't have time to maintain both it and NBSQLite3. I'm leaving NBSQLite3 more >> or less as is, and continue to work on UDBCSQLite3. > +1 > I think this is the way to go :) + 1 :) > >> Pierce >> > >

July 9, 2016

Re: [Pharo-users] SQLite + Pharo

by Mark Bratcher

Is UDBCSQLite3 available somewhere? I've tried Google and it turns up nothing but maybe two threads discussing it. On 7/9/2016 6:33 AM, Esteban Lorenzano wrote: >> On 09 Jul 2016, at 11:42, Pierce Ng <pierce(a)samadhiweb.com> wrote: >> >> On Wed, Jul 06, 2016 at 11:24:51AM +0200, Hilaire wrote: >>> I guess UDBC is for Pharo 5, and for Pharo 4 it is the NB version, right? >> Yes. >> >>> I guess both version has the same public interface. >> Yes, but. :-) Some bits of NBSQLite3, notably the online backup API but >> possibly other small stuff, isn't in UDBCSQLite3 yet. >> >> After making UDBCSQLite3 work with Glorp on Pharo 5, I've decided/realized that >> I don't have time to maintain both it and NBSQLite3. I'm leaving NBSQLite3 more >> or less as is, and continue to work on UDBCSQLite3. > +1 > I think this is the way to go :) > >> Pierce >> >

July 9, 2016

Re: [Pharo-users] [Pharo-dev] Spec Tutorial First chapter

by stepharo

Tx :) This is great that Johan is really pushing because my energy is low. Stef Le 9/7/16 Ã 10:22, Sven Van Caekenberghe a Ã©crit : >> On 08 Jul 2016, at 19:50, stepharo <stepharo(a)free.fr> wrote: >> >> Hi >> >> Johan Fabry is writing a great tutorial (and this is cool to see all the material I gathered or wrote with him in the past) >> >> to take such great form. >> >> I attached the first chapter. I will post the chapter one by one once I review them (so far I have nothing to do - great feeling). >> >> Well done Johan! >> >> Stef >> >> <FirstContact.pdf> > Great work, thank you ! > > Books make a lot of difference, even today. > > >

July 9, 2016

Re: [Pharo-users] SQLite + Pharo

by Esteban Lorenzano

> On 09 Jul 2016, at 11:42, Pierce Ng <pierce(a)samadhiweb.com> wrote: > > On Wed, Jul 06, 2016 at 11:24:51AM +0200, Hilaire wrote: >> I guess UDBC is for Pharo 5, and for Pharo 4 it is the NB version, right? > > Yes. > >> I guess both version has the same public interface. > > Yes, but. :-) Some bits of NBSQLite3, notably the online backup API but > possibly other small stuff, isn't in UDBCSQLite3 yet. > > After making UDBCSQLite3 work with Glorp on Pharo 5, I've decided/realized that > I don't have time to maintain both it and NBSQLite3. I'm leaving NBSQLite3 more > or less as is, and continue to work on UDBCSQLite3. +1 I think this is the way to go :) > > Pierce >

July 9, 2016