Re: [Pharo-dev] License agreement - are you kidding me?

"What you lose is the right to take out your code (and to change the licensing of it retroactively…)." That is only true in one sense. 1) The author cannot demand that the code is removed from the codebase - as the original grant of licence was irrevocable. (Or at least, this is proven true in

Re: [Pharo-dev] Unicode Support

s. A codepoint does not always represent a whole character. On 7 December 2015 at 13:06, Henrik Johansen <henrik.s.johan...@veloxit.no> wrote: > > On 07 Dec 2015, at 1:05 , EuanM <euan...@gmail.com> wrote: > > Hi Henry, > > To be honest, at some point I'm going to l

Re: [Pharo-dev] [Cuis] Sorting Unicode strings (Re: [Unicode] collation sequences (Re: [squeak-dev] Unicode Support))

Dale - is that you can't depend on the value of a codepoint *unless the string is either in fully-composed form (or has just been fully-decomposed from a fully-composed form) * OR are there circumstances where even those two cases cannot be relied upon? On 8 December 2015 at 19:20, Dale Henrichs

Re: [Pharo-dev] Documentation epiphany

The joke it's based on pre-dates use of computers to render complex 3D :-) Here's the world's first computer-generated 3D movie, from the Uni of Utah in 1972: https://vimeo.com/16292363 Compiled languages predate this. On 8 December 2015 at 15:24, Dimitris Chloupis

Re: [Pharo-dev] License agreement - are you kidding me?

"partially anonymous" The correct word is "pseudonimity". In UK law, as long as there is no intent to defraud, you can call yourself anything you like. In UK, you can provide signatures digitally, completely legally. UK law is has a long tradition of sorting out legal issues between two-third

Re: [Pharo-dev] Help needed: old issues issue tracker entries

Excellent. Can I suggest that in future they are simply closed, rather than re-assigned? On 3 December 2015 at 06:35, Nicolai Hess <nicolaih...@gmail.com> wrote: > > Am 03.12.2015 1:08 vorm. schrieb "EuanM" <euan...@gmail.com>: >> >> I had an issue assign

Re: [Pharo-dev] Unicode Support

And indeed, in principle. On 7 December 2015 at 10:51, EuanM <euan...@gmail.com> wrote: > Verifying assumptions is the key reason why you should documents like > this out for review. > > Sven - > > Cuis is encoded with ISO 8859-15 (aka ISO Latin 9) > > Sven, this is

Re: [Pharo-dev] Unicode Support

: > Hi EuanM > > Le 4/12/15 12:42, EuanM a écrit : >> >> I'm currently groping my way to seeing how feature-complete our >> Unicode support is. I am doing this to establish what still needs to >> be done to provide full Unicode support. > > > this is great

Re: [Pharo-dev] Unicode Support

ee with the views on that site. > > > Sent from the road > > On Dec 5, 2015, at 05:08, stepharo <steph...@free.fr> wrote: > > Hi EuanM > > Le 4/12/15 12:42, EuanM a écrit : > > I'm currently groping my way to seeing how feature-complete our > > Unicod

Re: [Pharo-dev] Unicode Support

Steph - I'll dig out the Fr phone book ordering from wherever it was I read about it! I thought I ghad it to hand, but I haven;t found it tonight. It can't be far away. On 5 December 2015 at 13:08, stepharo <steph...@free.fr> wrote: > Hi EuanM > > Le 4/12/15 12:42, EuanM a éc

Re: [Pharo-dev] Java Future

nd take over maintenance? > > Marcus > > On 04 Dec 2015, at 09:49, p...@highoctane.be wrote: > > Question: how long to drop the slice into the inbox? > > On Fri, Dec 4, 2015 at 8:51 AM, EuanM <euan...@gmail.com> wrote: >> >> Hi Steph, >> >> As a newco

Re: [Pharo-dev] Java Future

<steph...@free.fr> wrote: > True help closing bug > Build a great library > Buidl a cool software > > Stef > > Le 30/11/15 04:44, EuanM a écrit : > >> We also need to concentrate on building our community. >> >> We build a better platform fast

[Pharo-dev] Community Building [was: please name your thread]

you thread appropriately. And, we should remember > that acting is the only thing that will push us further. >> On Dec 1, 2015, at 12:18 AM, EuanM <euan...@gmail.com> wrote: >> Welcoming is, as welcoming does. >> On 30 November 2015 at 11:20, Tudor Girba <tu...@tudorgirba.

Re: [Pharo-dev] Digest from slack to the mailing list?

>> > yet) >> > http://slackdigest.com/digest.html >> > >> > It send a DM to interested users, but maybe using Outgoing WebHooks the >> > DM >> > can be forwarded to some service to publish it. >> > >> > >> > >>

Re: [Pharo-dev] Java Future

> Increasing the community is certainly important, and we welcome any action > that anyone would want to undertake in this direction. > > However, talking about the future of Java does not fall in this category. > > Cheers, > Doru > > >> On Nov 30, 2015, at 4:44 AM, EuanM

Re: [Pharo-dev] Java Future

. >> >> However, talking about the future of Java does not fall in this category. >> >> Cheers, >> Doru >> >> >> > On Nov 30, 2015, at 4:44 AM, EuanM <euan...@gmail.com> wrote: >> > >> > We also need to concentrate on b

Re: [Pharo-dev] red banner and links with safari?

> On 23 November 2015 at 07:24, Stephan Eggermont wrote: > Why the link to StackOverflow? It is not our data, our community or the > possibility to influence the answers. Please delete it. > I'll continue answering questions there, we should not point people there. A link to

Re: [Pharo-dev] Does Pharo stores original author of methods?

01:00 Marcus Denker <marcus.den...@inria.fr>: >> >> >> > On 22 Nov 2015, at 20:12, EuanM <euan...@gmail.com> wrote: >> > >> > Is there any reason against amending Monticello to store and save all >> > author's names? >> >> It

Re: [Pharo-dev] About the announcements model for SUnit

When Kent Beck was doing Smalltalk consulting, he wouldn't give SUnit to his client corporation. He would get any dev group to write it themselves from the concepts. All of which means I don't think we need to be too precious about the code - we don;t need to fear it :-) On 26 November 2015

Re: [Pharo-dev] About the announcements model for SUnit

Sandi Metz on this issue of fear: https://youtu.be/npOGOmkxuio?t=1077 (You might want to back up a little after watching these 15 seconds, to get a some context) On 30 November 2015 at 00:51, EuanM <euan...@gmail.com> wrote: > When Kent Beck was doing Smalltalk consulting, he wouldn't g

Re: [Pharo-dev] Digest from slack to the mailing list?

> makes sense to just compose a huge email of all discussions, but we can try > to do that. > > Cheers. > Uko > >> On 23 Nov 2015, at 00:21, EuanM <euan...@gmail.com> wrote: >> >> I agree - if we can have each 24 hours of chat archived to somewhere >

Re: [Pharo-dev] Digest from slack to the mailing list?

And of course, we can stop doing it manually once threading arrives. On 30 November 2015 at 03:52, EuanM <euan...@gmail.com> wrote: > I have been talking to the Slack dev team and they assure me that > threading is on its way - as a priority. > > I am happy to manually curate

Re: [Pharo-dev] Does Pharo stores original author of methods?

Does git not allow additional attribute objects that it benignly stores and ignores? (I suspect I can guess the answer, but...) On 30 November 2015 at 05:55, Thierry Goubier <thierry.goub...@gmail.com> wrote: > > Le 30 nov. 2015 5:24 AM, "EuanM" <e

Re: [Pharo-dev] Does Pharo stores original author of methods?

I did not mean storing all versions. I mean storing all authors of previous veesions. On 23 Nov 2015 11:13, "Marcus Denker" <marcus.den...@inria.fr> wrote: > > > On 22 Nov 2015, at 20:12, EuanM <euan...@gmail.com> wrote: > > > > Is there any reason ag

Re: [Pharo-dev] Does Pharo stores original author of methods?

Is there any reason against amending Monticello to store and save all author's names? Presumably, we'd also want a tool that could extract amnders' names all the way back to the first commit of a package? How many on-line Monticello repositories are in common use? (I know of SqueakSource.com,

Re: [Pharo-dev] Preparing for the (already here) future world of multi-core PCs

Maybe a 'pack' of Seasides is the wrong collective. A 'shoreline' of Seasides? A 'coast'? On 19 November 2015 at 15:22, EuanM <euan...@gmail.com> wrote: > There are also uses that don't involve the GPU - any headless server > use, e.g. running a pack of headless Seasides. >

Re: [Pharo-dev] Preparing for the (already here) future world of multi-core PCs

ation and an open mind. Sometimes the > quickest way to reach a goal is not a straight line . > > The truth however is even I that works with 3d graphics I find myself barely > needing 1 CPU core, so you need to first make sure that you need such a > feature before implementing it. >

[Pharo-dev] Preparing for the (already here) future world of multi-core PCs

(And yes, I know it's actually here already). Now that clock-speed rises have stalled, basically forever, desktop and laptop PCs are growing ever-increasing numbers of cores in their CPU chips, Is there design and conceptualisations work going on to see how Pharo will deal with providing

Re: [Pharo-dev] Preparing for the (already here) future world of multi-core PCs

I agree that parallelism and concurrency are different things. For easy parallelism : - a multi-VM version of something like PharoLauncher. - tools for tailor each VM + Image - tools to manage and track each running VM + Image. - tolls to try to mak sure that different running VMs and images have

Re: [Pharo-dev] keyboard events in the windows VM

I think anything that makes a consistent UI to Pharo for users on different platforms is a good thing. However, I do not know what the downside-effects of this change are. The key thing is to capture all breaks caused by the changed, so they can be coded through or around. And ensure that the

Re: [Pharo-dev] keyboard events in the windows VM

I'm happy to test on Windows 7, and on Raspbian Linux (Although Raspbian Linux runs Pharo UI events slo-o-owly, so I am not the best person to do the Linux testing) On 12 November 2015 at 15:42, EuanM <euan...@gmail.com> wrote: > I think anything that makes a consistent UI to Pharo