- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] how to update monticello cypress repository downloaded from github?

by Nicolas Passerini

AFAIK that is the only way > > 1. delete github-cache folder in the image folder > 2. unload all the loaded packages > 3. execute this script again > At least if you have a metadata less github repository, is that the case? But that was the conclusion to which we arrived with Dale a few weeks ago and he's changing stuff, so maybe in the latest version it is already solved.

July 16, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] file dialog replacement experiment

by Sven Van Caekenberghe

> On 16 Jul 2016, at 19:05, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Couple more updates: You rock ! > > If you truncate, you could put the full, non truncated path in a pop over, that would be a cheap way to solve that problem, no ? In any case, in my testing there was enough space. > > Fixed > > > Maybe also add a trailing / to indicate that it represents the directory and not the selection ? > > Fixed > > > the path is initially blank, it only fills when I start clicking. > > Fixed > > > And related to github filetree, what is the proper way to get a new version once you loaded the code ? > > What seems to work is to delete github-cache folder in image directory and unload both file-dialog and BaselineOfFileDialog packages, and then reexecute the load script again. > As this is really stupid, I'll have to ask Thierry or someone. > > And couple of more fixes based on Torsten's feedback: > > 1. the Open/Cancel buttons are swapped on Windows > 2. the FileSystem bookmark has been replaced with available disks on Windows (C:, D:, ...) > 3. Added basic entry completion when saving; note that Dark Theme and the EntryCompletion popup do not like each other --- this has to be fixed inside Pharo. > > <completion.png> > â > > One more thing I want to add really soon: clicking on a file would open a GTInspector on the side (as part of the window), so you can see the preview of text/image/etc > > Peter > > On Sat, Jul 16, 2016 at 2:25 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > On Fri, Jul 15, 2016 at 2:00 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 14 Jul 2016, at 23:49, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> Hi Sven, >> >> What I am missing in the UI is some indication of the path that leads to the current selected file. Right now, I am wondering where exactly I am, I feel a bit lost (this is of course from the technical standpoint of a path in a tree). This could be done with a popup, a trail, a pop-over. >> >> I've added this couple of days ago (as I was missing this too), I just forgot to push the update to github (one downside compared to smalltalkhub :)). >> >> The only problem is that the image directory name is usually really long (the longest I have is 110 characters as it includes the build's name), so it doesn't exactly fit in. >> There is some shortening happening based on the window's width but it's not perfect. > > I had another look. Yes, this is cool. > > If you truncate, you could put the full, non truncated path in a pop over, that would be a cheap way to solve that problem, no ? In any case, in my testing there was enough space. > > If Spec supports it, then it should be easy. > > > Maybe also add a trailing / to indicate that it represents the directory and not the selection ? > > Originally I wanted to make it bold, but again, Spec doesn't support Text properly; trailing slash might be a compromise for now > > > <Screen Shot 2016-07-15 at 13.58.27.png> > > Also when I tested it, using > > FDOpenFileDialog new openModal. > > the path is initially blank, it only fills when I start clicking. > > That's a bug, I'll fix that. > > > BTW, could it be that FDMorphicUIManager becomes default automatically ? > > That seems quite aggressive, I don't feel it's stable enoughâ¦ I could add something like #load, and #loadDefault to the load scriptâ¦ but then you might as well execute the beDefault. I'm not sure yet. > > > And related to github filetree, what is the proper way to get a new version once you loaded the code ? > > I don't know, but it should be the same as with any other (e.g. smalltalkhub) project, since it's both monticello, no? I've never done this, so I don't know. (Usually when I am updating I look at the individual commits because I want to know what has changed.) > > Peter >

July 16, 2016

how to update monticello cypress repository downloaded from github?

by Peter UhnÃ¡k

Hi, how can one update a cypress github repository? e.g. I install it like this Metacello new baseline: 'FileDialog'; repository: 'github://peteruhnak/file-dialog/repository'; load. And then later I want to pull latest changes as the repo itself doesn't contain commits I cannot do it from Monticello Browser. The only way I found was to 1. delete github-cache folder in the image folder 2. unload all the loaded packages 3. execute this script again This is really heavy-handed approach. Maybe the class BaselineOf could contain method #update or something like that that will automatically do this? Or is there a better way? Thanks, Peter

July 16, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] file dialog replacement experiment

by stepharo

super! Thanks for your effort. We should integrate this! Stef Le 16/7/16 Ã 19:05, Peter UhnÃ¡k a Ã©crit : > Couple more updates: > > > If you truncate, you could put the full, non truncated path in a pop > over, that would be a cheap way to solve that problem, no ? In any > case, in my testing there was enough space. > > Fixed > > > Maybe also add a trailing / to indicate that it represents the > directory and not the selection ? > > Fixed > > > the path is initially blank, it only fills when I start clicking. > > Fixed > > > And related to github filetree, what is the proper way to get a new > version once you loaded the code ? > > What seems to work is to delete github-cache folder in image directory > and unload both file-dialog and BaselineOfFileDialog packages, and > then reexecute the load script again. > As this is really stupid, I'll have to ask Thierry or someone. > > And couple of more fixes based on Torsten's feedback: > > 1. the Open/Cancel buttons are swapped on Windows > 2. the FileSystem bookmark has been replaced with available disks on > Windows (C:, D:, ...) > 3. Added basic entry completion when saving; note that Dark Theme and > the EntryCompletion popup do not like each other --- this has to be > fixed inside Pharo. > > > â > > One more thing I want to add really soon: clicking on a file would > open a GTInspector on the side (as part of the window), so you can see > the preview of text/image/etc > > Peter > > On Sat, Jul 16, 2016 at 2:25 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>> wrote: > > > > On Fri, Jul 15, 2016 at 2:00 PM, Sven Van Caekenberghe > <sven(a)stfx.eu <mailto:sven@stfx.eu>> wrote: > > >> On 14 Jul 2016, at 23:49, Peter UhnÃ¡k <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> >> Hi Sven, >> >> What I am missing in the UI is some indication of the path >> that leads to the current selected file. Right now, I am >> wondering where exactly I am, I feel a bit lost (this is of >> course from the technical standpoint of a path in a tree). >> This could be done with a popup, a trail, a pop-over. >> >> I've added this couple of days ago (as I was missing this >> too), I just forgot to push the update to github (one >> downside compared to smalltalkhub :)). >> >> The only problem is that the image directory name is usually >> really long (the longest I have is 110 characters as it >> includes the build's name), so it doesn't exactly fit in. >> There is some shortening happening based on the window's >> width but it's not perfect. > > I had another look. Yes, this is cool. > > If you truncate, you could put the full, non truncated path in > a pop over, that would be a cheap way to solve that problem, > no ? In any case, in my testing there was enough space. > > > If Spec supports it, then it should be easy. > > > Maybe also add a trailing / to indicate that it represents the > directory and not the selection ? > > > Originally I wanted to make it bold, but again, Spec doesn't > support Text properly; trailing slash might be a compromise for now > > > > Also when I tested it, using > > FDOpenFileDialog new openModal. > > the path is initially blank, it only fills when I start clicking. > > > That's a bug, I'll fix that. > > > BTW, could it be that FDMorphicUIManager becomes default > automatically ? > > > That seems quite aggressive, I don't feel it's stable enoughâ¦ I > could add something like #load, and #loadDefault to the load > scriptâ¦ but then you might as well execute the beDefault. I'm not > sure yet. > > > And related to github filetree, what is the proper way to get > a new version once you loaded the code ? > > > I don't know, but it should be the same as with any other (e.g. > smalltalkhub) project, since it's both monticello, no? I've never > done this, so I don't know. (Usually when I am updating I look at > the individual commits because I want to know what has changed.) > > Peter > >

July 16, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] file dialog replacement experiment

by Peter UhnÃ¡k

Couple more updates: > If you truncate, you could put the full, non truncated path in a pop over, that would be a cheap way to solve that problem, no ? In any case, in my testing there was enough space. Fixed > Maybe also add a trailing / to indicate that it represents the directory and not the selection ? Fixed > the path is initially blank, it only fills when I start clicking. Fixed > And related to github filetree, what is the proper way to get a new version once you loaded the code ? What seems to work is to delete github-cache folder in image directory and unload both file-dialog and BaselineOfFileDialog packages, and then reexecute the load script again. As this is really stupid, I'll have to ask Thierry or someone. And couple of more fixes based on Torsten's feedback: 1. the Open/Cancel buttons are swapped on Windows 2. the FileSystem bookmark has been replaced with available disks on Windows (C:, D:, ...) 3. Added basic entry completion when saving; note that Dark Theme and the EntryCompletion popup do not like each other --- this has to be fixed inside Pharo. â One more thing I want to add really soon: clicking on a file would open a GTInspector on the side (as part of the window), so you can see the preview of text/image/etc Peter On Sat, Jul 16, 2016 at 2:25 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > On Fri, Jul 15, 2016 at 2:00 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> >> On 14 Jul 2016, at 23:49, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> Hi Sven, >> >> What I am missing in the UI is some indication of the path that leads to >> the current selected file. Right now, I am wondering where exactly I am, I >> feel a bit lost (this is of course from the technical standpoint of a path >> in a tree). This could be done with a popup, a trail, a pop-over. >> >> I've added this couple of days ago (as I was missing this too), I just >> forgot to push the update to github (one downside compared to smalltalkhub >> :)). >> >> The only problem is that the image directory name is usually really long >> (the longest I have is 110 characters as it includes the build's name), so >> it doesn't exactly fit in. >> There is some shortening happening based on the window's width but it's >> not perfect. >> >> >> I had another look. Yes, this is cool. >> >> If you truncate, you could put the full, non truncated path in a pop >> over, that would be a cheap way to solve that problem, no ? In any case, in >> my testing there was enough space. >> > > If Spec supports it, then it should be easy. > > >> >> Maybe also add a trailing / to indicate that it represents the directory >> and not the selection ? >> > > Originally I wanted to make it bold, but again, Spec doesn't support Text > properly; trailing slash might be a compromise for now > > >> >> >> Also when I tested it, using >> >> FDOpenFileDialog new openModal. >> >> the path is initially blank, it only fills when I start clicking. >> > > That's a bug, I'll fix that. > > >> >> BTW, could it be that FDMorphicUIManager becomes default automatically ? >> > > That seems quite aggressive, I don't feel it's stable enoughâ¦ I could add > something like #load, and #loadDefault to the load scriptâ¦ but then you > might as well execute the beDefault. I'm not sure yet. > > >> >> And related to github filetree, what is the proper way to get a new >> version once you loaded the code ? >> > > I don't know, but it should be the same as with any other (e.g. > smalltalkhub) project, since it's both monticello, no? I've never done > this, so I don't know. (Usually when I am updating I look at the individual > commits because I want to know what has changed.) > > Peter >

July 16, 2016

Re: [Pharo-dev] [Pharo-users] [ANN] file dialog replacement experiment

by Peter UhnÃ¡k

On Fri, Jul 15, 2016 at 2:00 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 14 Jul 2016, at 23:49, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi Sven, > > What I am missing in the UI is some indication of the path that leads to > the current selected file. Right now, I am wondering where exactly I am, I > feel a bit lost (this is of course from the technical standpoint of a path > in a tree). This could be done with a popup, a trail, a pop-over. > > I've added this couple of days ago (as I was missing this too), I just > forgot to push the update to github (one downside compared to smalltalkhub > :)). > > The only problem is that the image directory name is usually really long > (the longest I have is 110 characters as it includes the build's name), so > it doesn't exactly fit in. > There is some shortening happening based on the window's width but it's > not perfect. > > > I had another look. Yes, this is cool. > > If you truncate, you could put the full, non truncated path in a pop over, > that would be a cheap way to solve that problem, no ? In any case, in my > testing there was enough space. > If Spec supports it, then it should be easy. > > Maybe also add a trailing / to indicate that it represents the directory > and not the selection ? > Originally I wanted to make it bold, but again, Spec doesn't support Text properly; trailing slash might be a compromise for now > > > Also when I tested it, using > > FDOpenFileDialog new openModal. > > the path is initially blank, it only fills when I start clicking. > That's a bug, I'll fix that. > > BTW, could it be that FDMorphicUIManager becomes default automatically ? > That seems quite aggressive, I don't feel it's stable enoughâ¦ I could add something like #load, and #loadDefault to the load scriptâ¦ but then you might as well execute the beDefault. I'm not sure yet. > > And related to github filetree, what is the proper way to get a new > version once you loaded the code ? > I don't know, but it should be the same as with any other (e.g. smalltalkhub) project, since it's both monticello, no? I've never done this, so I don't know. (Usually when I am updating I look at the individual commits because I want to know what has changed.) Peter

July 16, 2016

Re: [Pharo-dev] Epicea?

by stepharo

Tx Cyril!! Le 15/7/16 Ã 16:08, Cyril Ferlicot Delbecque a Ã©crit : > > On 15/07/2016 16:01, Nicolas Passerini wrote: >> There has been already a discussion about the same topic a few days ago >> and I think that there is a consensus on considering it a bug that has >> to be solved (look for Â«confused about the "image opening session"Â»). >> Yet I think there is not even a bug in the issue tracker. > Hi, > > I opened a bug entry yesterday because I think it's hard to get changes > back: > https://pharo.fogbugz.com/f/cases/18777/How-should-I-get-back-lost-changes-… > > And there is one about not opening the window if we leave Pharo without > a crash: > https://pharo.fogbugz.com/f/cases/18754/Epicea-should-log-image-saving > >

July 16, 2016

Re: [Pharo-dev] Pharo 5.0 Tiny Feature Request

by Esteban Lorenzano

Hi Sean, just submit an SLICE, for nowâ¦ I will sync the repository. Esteban > On 16 Jul 2016, at 04:42, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Sean P. DeNigris wrote >> But I'm not sure how to commit it. It changes UFFI which has a >> configuration. What do I commit (package, slice, config(s))? And to where >> (UFFI repo, inbox)? > > Bump :) How is it possible that there's not a simple answer to how to commit > a small fix to core?! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Pharo-5-0-Tiny-Feature-Request-tp4901682p4906759.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

July 16, 2016

Re: [Pharo-dev] Pharo 5.0 Tiny Feature Request

by Sean P. DeNigris

Sean P. DeNigris wrote > But I'm not sure how to commit it. It changes UFFI which has a > configuration. What do I commit (package, slice, config(s))? And to where > (UFFI repo, inbox)? Bump :) How is it possible that there's not a simple answer to how to commit a small fix to core?! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-5-0-Tiny-Feature-Request-tp4901682p4906759.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 16, 2016

CFP: 1st Workshop on Meta-Programming Techniques and Reflection (META) with SPLASH 2016

by Stefan Marr

**Call for Papers** ======================================================================== 1st Workshop on Meta-Programming Techniques and Reflection (METAâ16) Co-located with SPLASH 2016 October 30, 2016, Amsterdam, Netherlands http://2016.splashcon.org/track/meta2016 Follow us on twitter @MetaAtSPLASH ======================================================================== The Metaâ16 workshop aims to bring together researchers working on metaprogramming and reflection, as well as users building applications, language extensions such as contracts, or software tools. With the changing hardware and software landscape, and increased heterogeneity of systems, metaprogramming becomes an important research topic to handle the associate complexity once more. Contributions to the workshop are welcome on a wide range of topics related to design, implementation, and application of metaprogramming techniques, as well as empirical studies on and typing for such systems and languages. ### Important Dates 08 Aug 2016 - Abstract Submission 15 Aug 2016 - Paper Submission 05 Sep 2016 - Notification 09 Sep 2016 - Demo, position or work-in-progress paper submission 23 Sep 2016 - Demo, position or work-in-progress paper notification 30 Oct 2016 Workshop ### Topics of Interest The workshop is a venue for all approaches that embrace metaprogramming: - from static to dynamic techniques - reflection, meta-level architectures, staging, open language runtimes applications to middleware, frameworks, and DSLs - optimization techniques to minimize runtime overhead - contract systems, or typing of reflective programs reflection and metaobject protocols to enable tooling - case studies and evaluation of such techniques, e.g., to build applications, language extensions, or tools - empirical evaluation of metaprogramming solutions - security in reflective systems and capability-based designs - meta-level architectures and reflective middleware for modern runtime platforms (e.g. IoT, cyber-physical systems, mobile/cloud/grid computing, etc) - surveys, conceptualization, and taxonomization of existing approaches ### Types of Submissions and Workshop format We welcome both technical papers and work-in-progress and position papers from the academic as well as industrial perspective. Position paper should present new ideas and emerging problems and take a perhaps controversial stance on a specific topic and argue the position well. Furthermore, we plan interactive brainstorming and demonstration sessions between the formal presentations to enable an active exchange of ideas. The workshop papers will be put on the workshop website, if not requested otherwise by the authors, but they are not part of formal proceedings. Papers are to be submitted using the ACM sigplanconf style at 10pt font size. See http://www.sigplan.org/Resources/Author/. - demos and posters: 1-page abstract - position and work-in-progress paper: 1-4 pages - technical paper: up to 8 pages Demos, posters, position and work-in-progress papers can be submitted on a second, later deadline to discuss the latest results and current work. For the submission, please use the submission system at: https://meta16.hotcrp.com/ ### Organizing Committee Shigeru Chiba, University of Tokyo Elisa Gonzalez Boix, Vrije Universiteit Brussel Stefan Marr, Johannes Kepler University Linz ### Program Committee Marcus Denker, INRIA, France Robert Hirschfeld, HPI, Germany Hridesh Rajan, Iowa State University, USA Romain Rouvoy, University Lille 1 and INRIA, France Eric Tanter, University of Chile, Chile Tom Van Cutsem, Bell Labs, Belgium Tijs van der Storm, CWI, Netherlands Takuo Watanabe, Tokyo Institute of Technology, Japan

July 15, 2016