June 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Delete a package in SmalltalkHub

by jannik laval

Yes, we check, but I suspect that it does not work because it is related to a team. I already removed packages / mcz on my own repository and it worked (3 weeks ago). Cheers, Jannik 2014-06-06 18:13 GMT+02:00 stepharo <stepharo(a)free.fr>: > Yes but did you check because it looks like it removes it for real. > > > On 6/6/14 10:49, jannik laval wrote: > >> Hi pharoers, >> >> In SmalltalkHub, we would like to delete a package in a team project. >> When clicking on delete button, we get a message: "The request did not >> succeed". >> >> Any idea ? >> >> -- >> >> ~~Jannik Laval~~ >> Ãcole des Mines de Douai >> Enseignant-chercheur >> http://www.jannik-laval.eu >> http://www.phratch.com >> http://car.mines-douai.fr/ >> >> > > -- ~~Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://car.mines-douai.fr/

June 6, 2014

Re: [Pharo-dev] Different EOL between Save and Save As in Workspace

by Sven Van Caekenberghe

On 06 Jun 2014, at 21:23, Nicolai Hess <nicolaihess(a)web.de> wrote: > Workspace>>#saveString:toFile: ( or FileStream) behaves differently for arguments of type ByteString and Text. > ByteString is used by "Save as" > Text is used by accept. Great catch ! Maybe the easiest fix is to do a #asString before doing the nextPutAll: in #saveString:toFile: - way easier than figuring out the mess of MultiByteFileStream. > Reproduceable with: > > |fileone filetwo text str| > text:='hello > world' asText. > str:='hello > world'. > fileone:='text1.txt'. > filetwo:='text2.txt'. > FileStream forceNewFileNamed: fileone do: [ :stream | > stream converter: (TextConverter newForEncoding: 'utf-8'). > stream wantsLineEndConversion: true. > stream lineEndConvention: #crlf. > stream nextPutAll: text ]. > > FileStream forceNewFileNamed: filetwo do: [ :stream | > stream converter: (TextConverter newForEncoding: 'utf-8'). > stream wantsLineEndConversion: true. > stream lineEndConvention: #crlf. > stream nextPutAll: str ]. > > > > > > 2014-06-06 20:06 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I looked at the Workspace code a bit, but just by looking at it, I can't find anything wrong. Everything (look at the senders) goes through Workspace>>#saveString:toFile: which uses both the chosen encoding and line end convention. > > But I have also not yet tried to reproduce the problem. > > On 06 Jun 2014, at 19:30, phil(a)highoctane.be wrote: > > > Look at the top right arrow-style men in the window of the workspace, there are also some checkboxes in there related to line endings... (near the end). > > > > Phil > > > > > > > > > > On Fri, Jun 6, 2014 at 6:02 PM, stepharo <stepharo(a)free.fr> wrote: > > enter a bug entry. > > > > On 5/6/14 19:16, Esteban A. Maringolo wrote: > > When working in a Workspace, if I choose to save using Ctrl+S, the > > file will have Mac EOL (getting a lot of ^M characters when viewed > > using less or vim), if I choose "Save As" it saves the file "properly" > > (as expected). > > > > I guess this is a Bug, but maybe its not. > > > > Regards! > > > > Esteban A. Maringolo > > > > > > > > > > > > >

June 6, 2014

Re: [Pharo-dev] Different EOL between Save and Save As in Workspace

by Nicolai Hess

Workspace>>#saveString:toFile: ( or FileStream) behaves differently for arguments of type ByteString and Text. ByteString is used by "Save as" Text is used by accept. Reproduceable with: |fileone filetwo text str| text:='hello world' asText. str:='hello world'. fileone:='text1.txt'. filetwo:='text2.txt'. FileStream forceNewFileNamed: fileone do: [ :stream | stream converter: (TextConverter newForEncoding: 'utf-8'). stream wantsLineEndConversion: true. stream lineEndConvention: #crlf. stream nextPutAll: text ]. FileStream forceNewFileNamed: filetwo do: [ :stream | stream converter: (TextConverter newForEncoding: 'utf-8'). stream wantsLineEndConversion: true. stream lineEndConvention: #crlf. stream nextPutAll: str ]. 2014-06-06 20:06 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > I looked at the Workspace code a bit, but just by looking at it, I can't > find anything wrong. Everything (look at the senders) goes through > Workspace>>#saveString:toFile: which uses both the chosen encoding and line > end convention. > > But I have also not yet tried to reproduce the problem. > > On 06 Jun 2014, at 19:30, phil(a)highoctane.be wrote: > > > Look at the top right arrow-style men in the window of the workspace, > there are also some checkboxes in there related to line endings... (near > the end). > > > > Phil > > > > > > > > > > On Fri, Jun 6, 2014 at 6:02 PM, stepharo <stepharo(a)free.fr> wrote: > > enter a bug entry. > > > > On 5/6/14 19:16, Esteban A. Maringolo wrote: > > When working in a Workspace, if I choose to save using Ctrl+S, the > > file will have Mac EOL (getting a lot of ^M characters when viewed > > using less or vim), if I choose "Save As" it saves the file "properly" > > (as expected). > > > > I guess this is a Bug, but maybe its not. > > > > Regards! > > > > Esteban A. Maringolo > > > > > > > > > > > > >

June 6, 2014

Re: [Pharo-dev] issue validation needed

by stepharo

Hi esteban My brain is not working anymore. I'm totally exhausted. I hope tomorrow will be better :). Stef On 4/6/14 21:12, Esteban Lorenzano wrote: > Hi, > > can someone check this metacello issue? > > https://pharo.fogbugz.com/f/cases/13305/ > > I really need it for continue with VM work. > > thanks, > Esteban > > >

June 6, 2014

Re: [Pharo-dev] [ANN] Generating beautiful html books from Pillar

by Sven Van Caekenberghe

On 06 Jun 2014, at 18:11, stepharo <stepharo(a)free.fr> wrote: > superb Yes, +1 Cool.

June 6, 2014

Re: [Pharo-dev] Different EOL between Save and Save As in Workspace

by Sven Van Caekenberghe

I looked at the Workspace code a bit, but just by looking at it, I can't find anything wrong. Everything (look at the senders) goes through Workspace>>#saveString:toFile: which uses both the chosen encoding and line end convention. But I have also not yet tried to reproduce the problem. On 06 Jun 2014, at 19:30, phil(a)highoctane.be wrote: > Look at the top right arrow-style men in the window of the workspace, there are also some checkboxes in there related to line endings... (near the end). > > Phil > > > > > On Fri, Jun 6, 2014 at 6:02 PM, stepharo <stepharo(a)free.fr> wrote: > enter a bug entry. > > On 5/6/14 19:16, Esteban A. Maringolo wrote: > When working in a Workspace, if I choose to save using Ctrl+S, the > file will have Mac EOL (getting a lot of ^M characters when viewed > using less or vim), if I choose "Save As" it saves the file "properly" > (as expected). > > I guess this is a Bug, but maybe its not. > > Regards! > > Esteban A. Maringolo > > > > >

June 6, 2014

Re: [Pharo-dev] Different EOL between Save and Save As in Workspace

by phil＠highoctane.be

Look at the top right arrow-style men in the window of the workspace, there are also some checkboxes in there related to line endings... (near the end). Phil On Fri, Jun 6, 2014 at 6:02 PM, stepharo <stepharo(a)free.fr> wrote: > enter a bug entry. > > On 5/6/14 19:16, Esteban A. Maringolo wrote: > >> When working in a Workspace, if I choose to save using Ctrl+S, the >> file will have Mac EOL (getting a lot of ^M characters when viewed >> using less or vim), if I choose "Save As" it saves the file "properly" >> (as expected). >> >> I guess this is a Bug, but maybe its not. >> >> Regards! >> >> Esteban A. Maringolo >> >> >> > >

June 6, 2014

Re: [Pharo-dev] Brainstorming Pharo4

by Sven Van Caekenberghe

On 06 Jun 2014, at 17:46, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > And related to this I hope to make alpha 32-bit Spur Squeak VMs and images available today. Cool ! > Sven > > On 05 Jun 2014, at 10:14, phil(a)highoctane.be wrote: > > > On Thu, Jun 5, 2014 at 8:31 AM, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > > As Kilon say, this is a personal wishlist. Any direction you mentioned is worth and will have impact. > > > > However, here's my personal top 5: > > > > - **Git in the image**, that would be awesome to be able integrate the gitflow way of developing in team. Easy branching/merging is a must. > > - **Slots**. I still need to check the current implementation and see what's possible (Property slots?) but as I have understood you've planned even more for pharo4? > > - **Text Editor with sensible keybindings**. > > - **ARM support** > > - **Athens** > > > > Keybindings that do work on Linux > > VM on enterprise OS (CentOS/RHEL), including GLIBC < 2.15 > > Debugger that actually doesn't throws you in space after a couple of restart/through/over (this one really is taking power away from the whole experience) > > Faster UI in general > > Easier Git merges without metadata issues etc > > Ability to recover frozen images (as in "Oz") > > Ability to somehow get back control of the image through some mechanism at the VM level when frozen and no way to interrupt anything. I am ready to pay some performance in order to work that way. > > Removal of all passwords, including whatever could be in the .changes (which will disappear per se but you get my drift). > > +1 for Mpeg and Camera plugins; > > Traits should indeed be given a better treatment in Nautilus. > > > > Phil > > > > > > > > On Wed, Jun 4, 2014 at 9:06 PM, jannik laval <jannik.laval(a)gmail.com> wrote: > > Hi all, > > > > From my point of view, I like the progrss on the ARM VM. > > I hope to have an Android VM that works. > > Also I hope to see Pharo3.0 and Pharo4.0 working on iOS. > > > > Another question is about two interesting plugins: Mpeg3Plugin and CameraPlugin. > > Is it possible to integrate them in the VM build ? > > > > Thank you guys for all the work done. > > Jannik > > > > > > 2014-06-04 20:53 GMT+02:00 stepharo <stepharo(a)free.fr>: > > > > > > Hi Esteban, > > > > As you mentioned a lot of new tools and protocols were introduced, > > people (me included) does not well about those ones. > > As an example I am slowly discovering announcement and now AFAIK the > > image use three different protocols for this: change/update, observer > > and Announcement! > > Yes we know that the situation is not ideal. > > We started to move more to announcement. The problem is that some of the widgets > > requires the change/update. For the observer I do not know what you mean. > > > > > > Personally I beg for a great Pharo 4.x series of iterative > > cleaning+consolidations. > > > > Thanks > > > > Hilaire > > > > Le 04/06/2014 17:36, Esteban Lorenzano a Ã©crit : > > Hi, > > > > A couple of weeks ago we started to plan Pharo4. This work became stagnated for many reasons, but mainly because I needed to travel to Argentina. > > Now I'm slowly resuming the work and I wanted to share with you what we have been talking/dreaming. > > In esence, we have two important drivers for this release: > > > > 1) Improving tools > > Turns out that we have introduced a lot of kernel improvements (opal compiler, layouts, slots, etc.) and tools are still not aware of them. Even worst: we have traits since a lot of time and our tools are still now aware enough to provide good interoperability. > > But not just that: we have introduced things that are not well used yet: keybindings (who do not want a better keybindings structure... coherent and editable?), spec should allow us to continue enhancing existing tools and to replace old ones. > > > > 2) Modularisation > > One of the fundamental ideas behind Pharo is to provide a modular environment. But well... since Pharo start to the moment, we prepared things to allow it, but still few direct effort has been made. > > In our dreams, Pharo should be built starting for a small kernel image and adding different modules to get a complete version. In this idea Pharo=Kernel+GUI(Morphic)+Tools. > > This has huge advantages (I do not think is necesary to explain them, isn't ;)?) > > > > We brainstomed around this and we get this list of issues (not all of them directly related to the objectives, but well... good stuff also :) ) > > > > Web site: > > - add catalog > > - add videos > > - enhance it in general > > > > Infrastructure: > > - support more vm platforms > > > > VM: > > - spur > > - 64bits > > - make vm embedable and UI independent (with SDL2 and OSWindow) > > > > Image: > > - Modularisation > > - Removing old compiler > > - Repackage Morphic (to allow better modularisation) > > - Athens (replace old bitblt) > > > > Tools > > - Replace changes with Ombu/Epicea > > - Replace sources with a better abstraction > > - Git support inside image (with libgit2 + tools) > > - Pass on Spec > > - Include Glamour? > > - Make Ring unloadable > > - Fonts with FreeType > > > > And lots of bugfixes :) > > > > We would like to exchange ideas with you. > > So, what do you think? > > > > Esteban > > > > > > > > > > > > > > > > > > -- > > ~~Jannik Laval~~ > > Ãcole des Mines de Douai > > Enseignant-chercheur > > http://www.jannik-laval.eu > > http://www.phratch.com > > http://car.mines-douai.fr/ > > > > > > > > > > >

June 6, 2014

Re: [Pharo-dev] Delete a package in SmalltalkHub

by Nicolas Petton

stepharo <stepharo(a)free.fr> writes: > Yes but did you check because it looks like it removes it for real. I'm adding that to my todo list of things to check next monday :) Cheers, Nico > > On 6/6/14 10:49, jannik laval wrote: >> Hi pharoers, >> >> In SmalltalkHub, we would like to delete a package in a team project. >> When clicking on delete button, we get a message: "The request did not >> succeed". >> >> Any idea ? >> >> -- >> >> ~~Jannik Laval~~ >> Ãcole des Mines de Douai >> Enseignant-chercheur >> http://www.jannik-laval.eu >> http://www.phratch.com >> http://car.mines-douai.fr/ >> -- Nicolas Petton http://nicolas-petton.fr

June 6, 2014

Re: [Pharo-dev] Delete a package in SmalltalkHub

by stepharo

Yes but did you check because it looks like it removes it for real. On 6/6/14 10:49, jannik laval wrote: > Hi pharoers, > > In SmalltalkHub, we would like to delete a package in a team project. > When clicking on delete button, we get a message: "The request did not > succeed". > > Any idea ? > > -- > > ~~Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > http://www.phratch.com > http://car.mines-douai.fr/ >

June 6, 2014