date:20170511

Hi Stef,

> Am 10.05.2017 um 22:09 schrieb Stephane Ducasse :
> 
> Norbert 
> 
> I know petri nets and I was wondering if you were interested in worklow (as 
> in microworkflow). 
> because I think that a simple extensible workflow library is missing in Pharo

I'm interested in workflow but came to petri nets as they are similar. But I 
don't know what is the real difference between those two. I've read a bit about 
van der Aalst workflow patterns and a revision of Bröger for them. But I know 
too little of the topic. 
We have more projects where we choose a state machine in order to properly 
manage state changes in our applications. In some projects the transitions are 
simple and clear so that they can be described generically. And that brings me 
to workflow and petri nets. A more generic approach will lower the amount of 
code to be written and opens a way to serialize the flow, have a DSL for it or 
use it together with Roassal.

Norbert

> Stef
> 
> On Wed, May 10, 2017 at 6:13 PM, Norbert Hartl  > wrote:
> 
> > Am 10.05.2017 um 17:46 schrieb Serge Stinckwich  > >:
> >
> > On Wed, May 10, 2017 at 5:36 PM, Norbert Hartl  > > wrote:
> >> Are there any resources regarding petri nets or control flow…/workflow 
> >> patterns in pharo or smalltalk?
> >
> > We have done some work with one student of Alexandre about BPMN:
> > http://a4bp.com/ 
> >
> I downloaded the app but it opens with a black screen on my Mac laptop.
> 
> > and there is PNTalk also:
> > https://github.com/SergeStinckwich/PNTalk 
> > 
> >
> Thanks, that is what I was looking for.
> 
> > Long time ago I was able to do process mining from logs and generate Petri 
> > Nets:
> > https://www.youtube.com/watch?v=wdf80t32v-0 
> > 
> 
> That is really close to what I want to play with. Did you ever encounter van 
> der Aalst workflow pattern in that context. Do you know any material 
> comparing the approaches?
> 
> thank you very much,
> 
> Norbert
> 
> 
>

[Pharo-users] SourceCity

Where can I get a working SourceCity? Even in older Pharo/Moose.

I've got a use case for metrics that would be a pretty good fit.


Philippe

Re: [Pharo-users] Intro to git-only Pharo


> Am 11.05.2017 um 08:54 schrieb jtuc...@objektfabrik.de:
> 
> Hi Norbert,
> 
> thanks for your explanations. 
> So it seems liek I should start by using Pharo6 and load Iceberg and just 
> take a look.
> 
Yes, iceberg has still some issues but is usable and it will evolve quickly. If 
you are the brave type of guy you can start with pharo6 64bits ;)

Norbert

> Joachim
> 
> 
> 
> Am 10.05.17 um 10:34 schrieb Norbert Hartl:
>> Hi Joachim,
>> 
>> I think your timing is quite good. We had some changes in the last years and 
>> it is getting better now. 
>> Before we had only monticello. Monticello is a zip container that contains a 
>> version number in the filename and prior version pointer inside the 
>> repository. Regarding dependencies there was nothing that was used widely. 
>> Then Metacello appeared and solved the problem by providing dependency 
>> management and versioning of dependencies. Dependency management works good, 
>> the integrated versioning has issues. Especially when you look at a system 
>> like git you can see that versioning is solved there. Filetree is needed 
>> because git and other vcs systems are file based so you need to layout your 
>> code in files (how quaint!)
>> To make a long story short: The best thing to use is git with Metacello 
>> Baselines. Filetree is used to store code. Versioning you do with git tags 
>> that can be used in Baselines. Now we have a decent UI (iceberg) that 
>> supports the most needed workflow items. 
>> We have a UI for the dependency management as well (versionner) but it sadly 
>> targets ConfigurationOfs and not BaselineOfs. That needs to be changed.
>> 
>> my 2 cents,
>> 
>> Norbert
>> 
>>> Am 10.05.2017 um 07:56 schrieb Joachim Tuchel >> >:
>>> 
>>> Hi guys,
>>> 
>>> please forgive me if this mail is a sign of ignorance. I am not a regular 
>>> Pharo user and one of the reasons for this is that I didn't like most of 
>>> the source management tools around Monticello. Coming from an envy 
>>> background, it feels like not being ready for prime time. Of course you 
>>> guys have been proving you can work with these tools quite well, but still 
>>> I'd be interested in using Pharo in a pure git-based environment, as it 
>>> most closely resembles some of the most-beloved features of envy.
>>> 
>>> Over the years there was a lot of work and discussion on filetree, 
>>> gitfiletree, iceberg, cypress and maybe quite a few other projects that 
>>> sounded promising and interesting. But I must admit I lost track of what 
>>> was really done and how far things went in the last years.
>>> 
>>> So are there any pointers to info material that I could look at to see what 
>>> the current status of source control in Pharo 5 and Pharo 6 is and/or will 
>>> be soon?
>>> 
>>> I am mostly interested in these topics:
>>> 
>>> git only - no monticello meta info any more - possible?
>>> tools like merge/diff, committing from within the image
>>> dependencies within my own project as well as dependencies on external code 
>>> in - possibly multiple - external repositories
>>> what is the current "most official" source repository for open source code?
>>> best practices for managing complex projects and keeping old versions 
>>> reproducible at any time
>>> tutorial for git newbies in a Pharo context? (Like, how do I start with a 
>>> new packege - create folder first and do git init, or start in the image 
>>> and push into repo later? as I said: beginners' stuff)
>>> Thanks for pointers and help
>>> 
>>> Joachim
>>> 
>> 
> 
> 
> -- 
> ---
> Objektfabrik Joachim Tuchel  mailto:jtuc...@objektfabrik.de 
> 
> Fliederweg 1 http://www.objektfabrik.de 
> 
> D-71640 Ludwigsburg  http://joachimtuchel.wordpress.com 
> 
> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
>

Re: [Pharo-users] Petri nets and workflow patterns

2017-05-11 Thread Serge Stinckwich

On Wed, May 10, 2017 at 6:13 PM, Norbert Hartl  wrote:
>
>> Am 10.05.2017 um 17:46 schrieb Serge Stinckwich :
>>
>> On Wed, May 10, 2017 at 5:36 PM, Norbert Hartl  wrote:
>>> Are there any resources regarding petri nets or control flow…/workflow 
>>> patterns in pharo or smalltalk?
>>
>> We have done some work with one student of Alexandre about BPMN:
>> http://a4bp.com/
>>
> I downloaded the app but it opens with a black screen on my Mac laptop.

Yes this is the usual story  software rots at the end.
I guess you are using last version of mac os x and the VM provided on
the web site does not work anymore.

Give me 3 students and I will change this situation ;-)
I want to continue this work but I have to find motivated students.

>> and there is PNTalk also:
>> https://github.com/SergeStinckwich/PNTalk
>>
> Thanks, that is what I was looking for.
>
>> Long time ago I was able to do process mining from logs and generate Petri 
>> Nets:
>> https://www.youtube.com/watch?v=wdf80t32v-0
>
> That is really close to what I want to play with. Did you ever encounter van 
> der Aalst workflow pattern in that context. Do you know any material 
> comparing the approaches?

I know van der Aalst work but I don't know exactly what do you mean by
workflow pattern. The one described here:
http://www.workflowpatterns.com/patterns/control/index.php

Regards,
-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-users] Petri nets and workflow patterns

2017-05-11 Thread Serge Stinckwich

On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse
 wrote:
> Norbert
>
> I know petri nets and I was wondering if you were interested in worklow (as
> in microworkflow).
> because I think that a simple extensible workflow library is missing in
> Pharo

I guess you talk about this: http://micro-workflow.com/phdthesis/

-- 
Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://www.doesnotunderstand.org/

Re: [Pharo-users] Petri nets and workflow patterns


> Am 11.05.2017 um 09:58 schrieb Serge Stinckwich :
> 
> On Wed, May 10, 2017 at 6:13 PM, Norbert Hartl  wrote:
>> 
>>> Am 10.05.2017 um 17:46 schrieb Serge Stinckwich 
>>> :
>>> 
>>> On Wed, May 10, 2017 at 5:36 PM, Norbert Hartl  wrote:
 Are there any resources regarding petri nets or control flow…/workflow 
 patterns in pharo or smalltalk?
>>> 
>>> We have done some work with one student of Alexandre about BPMN:
>>> http://a4bp.com/
>>> 
>> I downloaded the app but it opens with a black screen on my Mac laptop.
> 
> Yes this is the usual story  software rots at the end.
> I guess you are using last version of mac os x and the VM provided on
> the web site does not work anymore.
> 
Ah, right. I just need to use my own vm to start it. I'll try again :)

Norbert

> Give me 3 students and I will change this situation ;-)
> I want to continue this work but I have to find motivated students.
> 
>>> and there is PNTalk also:
>>> https://github.com/SergeStinckwich/PNTalk
>>> 
>> Thanks, that is what I was looking for.
>> 
>>> Long time ago I was able to do process mining from logs and generate Petri 
>>> Nets:
>>> https://www.youtube.com/watch?v=wdf80t32v-0
>> 
>> That is really close to what I want to play with. Did you ever encounter van 
>> der Aalst workflow pattern in that context. Do you know any material 
>> comparing the approaches?
> 
> I know van der Aalst work but I don't know exactly what do you mean by
> workflow pattern. The one described here:
> http://www.workflowpatterns.com/patterns/control/index.php
> 
> Regards,
> -- 
> Serge Stinckwich
> UCN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
>

Re: [Pharo-users] SourceCity

2017-05-11 Thread Tudor Girba

Hi,

CodeCity was last working in Pharo 4 because it relied on NativeBoost.

The Moose version that works in Pharo 4 is:
http://moosetechnology.org/res/download/moose_image_5_1

You can load the code using:
Gofer new smalltalkhubUser: 'RichardWettel' project: 'CodeCity'; configuration; 
load. 
(Smalltalk at: #ConfigurationOfCodeCity) loadDevelopment

However, something does not seem to work using the latest Pharo 4.0 VM on Mac 
Sierra.

Cheers,
Doru

> On May 11, 2017, at 9:51 AM, p...@highoctane.be wrote:
> 
> Where can I get a working SourceCity? Even in older Pharo/Moose.
> 
> I've got a use case for metrics that would be a pretty good fit.
> 
> 
> Philippe

--
www.tudorgirba.com
www.feenk.com

"No matter how many recipes we know, we still value a chef."

Re: [Pharo-users] Petri nets and workflow patterns


> Am 11.05.2017 um 09:59 schrieb Serge Stinckwich :
> 
> On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse
>  wrote:
>> Norbert
>> 
>> I know petri nets and I was wondering if you were interested in worklow (as
>> in microworkflow).
>> because I think that a simple extensible workflow library is missing in
>> Pharo
> 
> I guess you talk about this: http://micro-workflow.com/phdthesis/
> 
Is the source code available somewhere?

Norbert

[Pharo-users] Fwd: Re: 11/05/17 - Tabular Data Structures for Data Analysis - Oleksandr Zaytsev

-- Message transféré --
De : "p...@highoctane.be" 
Date : 11 mai 2017 10:54
Objet : Re: 11/05/17 - Tabular Data Structures for Data Analysis -
Oleksandr Zaytsev
À : "Nick Papoylias" 
Cc :



On Thu, May 11, 2017 at 10:20 AM, Nick Papoylias 
wrote:

>
>
> On Thu, May 11, 2017 at 5:24 AM, Oleksandr Zaytsev 
> wrote:
>
>>
>> *A. Work done*
>>
>>- Downloaded the threaded VM as suggested by Esteban Lorenzano to
>>make Iceberg work. And it does! I have successfully pushed my 
>> NeuralNetwork
>>code to GitHub: https://github.com/olekscode/MLNeuralNetwork
>>- Joined the PolyMath organization on GitHub
>>- Created a repository for the TabularDataset project
>>https://github.com/PolyMathOrg/TabularDataset
>> as a part of PolyMath
>>organization on GitHub
>>- Fixed a PolyMath issue #25 and made a PR
>>- Read an article from Wolfram Mathematica documentation regarding
>>Dataset. It was one of the reading suggestions sent to me by Nick 
>> Papoylias
>>
>>
>> *B. Next steps*
>>
>>- Fix more issues of PolyMath, using Iceberg. I have to get used to
>>it by the time the coding phase starts
>>- Read the rest of Nick Papoylias's suggestions
>>
>>
>> *C. Help needed*
>>
>>- The Dataset in Wolfram, as well as Pandas in Python, has a very
>>advanced indexing system. Smalltalk has its own special conventions for
>>indexing, so I think that it would be great if I got familiar with them.
>>Could you suggest me some reading on this topic (what are the indexing
>>conventions in Smalltalk?).
>>For example, in Wolfram, I can write *dataset[[-1]]* to extract the
>>last row. But in Pharo indexes can not be negative. In Pharo I would say 
>> *dataset
>>last*. But how about *dataset[[-5]]*?
>>
>> This would be a good exercise for you ;) In Pharo you can easily add
> negative indexing yourself.
>
> *Hint:* You know the index of the last element, since this is the size of
> the collection, so... ;)
>
> No need for changes, this exists already.

Use atWrap: index put: value and atWrap: with negative indexes.
'hello' atWrap: -2

There is a specific version for Array using a primitive.
#[ 10 20 30 40 ] atWrap: -1

atWrap:0 gives you the last item.
atWrap: -1 gives 30

This is different from 0 based index languages.

The interesing thing about atWrap: is that it uses modulo interally so you
do not need to care about that.

($/ split: 'abc/def/ghi/jkl') atWrap: -1
--> 'ghi'

The Matrix class has a bunch of things API wise but the class is highly
inefficient, doing copies all the time etc. It would be nice to have some
kind of futures/copy on write style things in there.

I miss cbind and rbind. These are useful. I have some half baked super
inefficient implementations of these things for Matrix.

https://stat.ethz.ch/R-manual/R-devel/library/base/html/cbind.html

The ability to name columns is also nice to have.

In R one does:

df <- dataframe()
cbind(df, c(1,2,3))
cbind(df, c(4,5,6))
names(df)<-("C1", "C2", "C3")
names can be found back with:

names(df)

A Smalltalkish style would be welcome.

Maybe looking at the Voyage queries can be helpful.

Phil



> Try adding an extention method to Ordrered or SequenceableCollection.
>
> If the Pharo by example chapter is not enough or the MOOC, read the source
> itself in the core, to see how basic methods are implemented (it is less
> scary,
> than it sounds).
>
> You can also try Chapters 9, 10, 11 of the blue book (some API changes may
> apply):
>
> 
> http://sdmeta.gforge.inria.fr/FreeBooks/BlueBook/Bluebook.pdf
>
>
>>- Or what is the best way of implementing this index:
>>*dataset[["name"]]* (extracts a named row), *dataset[[1]*] (extracts
>>the first row)? Should I create two separate messages: *dataset
>>rowNamed: 'name'* and *dataset rowAt: 1*?
>>
>> rowNamed:
rowAt:

yes, look like it.

But if we want to model things like R dataframes for example, this has to
be seen as a vectorized operation, so you can to use row slices, column
slices, and logical indexes.

Check this out:

http://www.r-tutor.com/r-introduction/data-frame/data-frame-row-slice
https://www.r-bloggers.com/working-with-data-frames/



> The internal representation of your data-structure can be anything at the
> moment, *as long as you encapsulate it.*
>
> (ie it can be nested OrderedCollections with meta-data for column-names to
> indexes, or dictionary of collections etc).
>
> *If you don't expose it to the user* (ie return it from the public api,
> or expect knowledge of it in argument passing),
> we can easily change it later. So *first make it work, and we optimize
> later ;)*
>
> For your case it will be a little bit trickier because *you also have the
> notions of a) rows and b) columns*, which
> are exposed to the user. So *you would need to create abstractions* for
> these too.
>
> Cheers,
>
> Nick
>
>>
>>-
>>
>>
>> If someone e

Re: [Pharo-users] Smalltalkers will, eventually, win. So says this old C++ programmer.

2017-05-11 Thread Thibault Raffaillac

> Hi kilon,
> 
> Some weeks ago I tried the C live programming technique for the Ludum Dare.
> It works very well. For that occasion I wrote this short article
> https://ldjam.com/events/ludum-dare/38/smalcoded-a-small-eco-destroyed-world/a-diabolical-game-for-a-diabolical-experiment
> . The game ended pretty well in my opinion:
> https://ldjam.com/events/ludum-dare/38/smalcoded-a-small-eco-destroyed-world
> .
Cool game for a first LD :) (I got till Europe and lost in the snowy mountains 
of Italy...)

Re: [Pharo-users] Wandering Through Dependency Hell

2017-05-11 Thread Milan Vavra via Pharo-users

--- Begin Message ---
Evan wrote:

>If anyone knows how to figure out how to force all the current good code in
>my image into one massive commit, so that other people can check out the
>current, working version, please do not hesitate to let me know.

If you are using mczs, all changes are committed each time.

Each mcz archive is a snapshot of all the classes and methods in the system
category that defines the package at the moment in time when you saved it.
Much like a git commit.

So all you need to do is to save another version of the package. Just make
sure the filename you use is unique.

If in doubt, you can use a version number that resembles a timestamp like
YourPackage-YourName.201705111236.mcz where 201705111236 is 2017-05-11,
12:36.

Best Regards,

Milan Vavra

--
View this message in context: 
http://forum.world.st/Wandering-Through-Dependency-Hell-tp4946266p4946653.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

--- End Message ---

Re: [Pharo-users] Glamour Fast List, double click action. Is it supported?

2017-05-11 Thread Juraj Kubelka


> On May 11, 2017, at 03:58, Esteban Lorenzano  wrote:
> 
> 
>> On 10 May 2017, at 21:00, Juraj Kubelka  wrote:
>> 
>> Hi!
>> 
>> Does Glamour Fast List Presentation allow double click action on a item? 
>> 
>> I cannot find anything like that.
> 
> it should be “strongSelection”, isn’t?

You are right, the double click is calles strongSelection, and the solution is: 

-=-=-=-
browser := GLMTabulator new.
browser column: #one.
browser transmit to: #one; andShow: [ :a |
a fastList 
title: 'List';
onChangeOfPort: #strongSelection 
act: [ :presentation :entity | self inform: 'STRONG 
selection on ', presentation strongSelection asString ] ].

browser openOn: Object allSubclasses  
-=-=-=-

Thanks!
Juraj



> 
> Esteban
> 
>> 
>> Thanks!
>> Juraj
>> 
>> 
> 
>

[Pharo-users] Not much longer...

On my vacation I saw this progress bar about pharo. So looks close to 6 for me 
:)

Re: [Pharo-users] [ann] bloc & cairo+morphic

2017-05-11 Thread Alain Plantec via Pharo-users

--- Begin Message ---
Hello Doru, all,

I’m really happy to see Bloc progresses. 
Even I’m not active since more than one year, Bloc is still an important 
project for me.

but let me complete this short historical presentation a little bit.

Bloc is a project that I initiated in 2013 in collaboration with RMOD following 
experiments made around the ROME project. 
The idea was to completely revisit the 2D framework of Pharo to address Morphic 
limits. 
Following an invitation of the Software Composition Group (thanks to Oscar 
Nierstrasz and to Doru here), 
I presented the first version of Bloc at Bern (March, 2015), then Doru and 
Aliaksel joined the project. 
One year ago, during his PhD at Brest, Glenn Cavarle produced a new version of 
the Bloc infrastructure that is now the 
one used together with the layouting system that was implemented by Aliaksel. 

Please, do not use the humane assessment web site but the github project one 
instead.

I will restart working on Bloc/Brick soon in the context of a project that we 
recently signed with the Thales company.

Thanks,
Cheers

Alain

> On 8 mai 2017, at 23:00, Tudor Girba  wrote:
> 
> Hi,
> 
> We are happy to announce that based on the work of Glenn, Alex extended Bloc 
> (Sparta) to work directly in the Morphic world using Cairo as a backend.
> 
> Cairo is less powerful than Moz2D (see the screenshot below for an example), 
> but the implementation addresses a concern that the community raised 
> regarding a perceived increased liability due to the dependency to Moz2D. 
> Essentially this means that Bloc can be treated as another graphical library 
> that can coexist with Morphic without requiring any external VM plugin.
> 
> 
> 
> I would also like to point out that adding a new backend and host was 
> possible because of the many iterations (including throwing away whole 
> implementations) that Alex and Glenn went through. I think they did an 
> amazing job.
> 
> You can find a bit more details about Bloc here:
> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/
> 
> Another issue raised regarding Bloc was that of the engineering effort 
> required to make it a reality. That is why I would also like to announce that 
> Alex joined feenk.com where he is primarily working on the graphical stack 
> for Pharo.
> 
> Cheers,
> Doru
> 
> 
> --
> www.tudorgirba.com
> www.feenk.com
> 
> "To lead is not to demand things, it is to make them happen."
> 
> 
> 
> 

--- End Message ---

Re: [Pharo-users] [Pharo-dev] [ann] bloc & cairo+morphic

2017-05-11 Thread Alexandre Bergel

Hi Alain!

Thanks for the mail (even if the historial part has always been pretty clear to 
me).
We miss you! Be back soon!

Cheers,
Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev 
>  wrote:
> 
> 
> From: Alain Plantec 
> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic
> Date: May 11, 2017 at 12:36:36 PM GMT-3
> To: Pharo Development List 
> Cc: Alain Plantec , Moose-related development 
> , Any question about pharo is welcome 
> 
> 
> 
> Hello Doru, all,
> 
> I’m really happy to see Bloc progresses. 
> Even I’m not active since more than one year, Bloc is still an important 
> project for me.
> 
> but let me complete this short historical presentation a little bit.
> 
> Bloc is a project that I initiated in 2013 in collaboration with RMOD 
> following experiments made around the ROME project. 
> The idea was to completely revisit the 2D framework of Pharo to address 
> Morphic limits. 
> Following an invitation of the Software Composition Group (thanks to Oscar 
> Nierstrasz and to Doru here), 
> I presented the first version of Bloc at Bern (March, 2015), then Doru and 
> Aliaksel joined the project. 
> One year ago, during his PhD at Brest, Glenn Cavarle produced a new version 
> of the Bloc infrastructure that is now the 
> one used together with the layouting system that was implemented by Aliaksel. 
> 
> Please, do not use the humane assessment web site but the github project one 
> instead.
> 
> I will restart working on Bloc/Brick soon in the context of a project that we 
> recently signed with the Thales company.
> 
> Thanks,
> Cheers
> 
> Alain
> 
> 
>> On 8 mai 2017, at 23:00, Tudor Girba  wrote:
>> 
>> Hi,
>> 
>> We are happy to announce that based on the work of Glenn, Alex extended Bloc 
>> (Sparta) to work directly in the Morphic world using Cairo as a backend.
>> 
>> Cairo is less powerful than Moz2D (see the screenshot below for an example), 
>> but the implementation addresses a concern that the community raised 
>> regarding a perceived increased liability due to the dependency to Moz2D. 
>> Essentially this means that Bloc can be treated as another graphical library 
>> that can coexist with Morphic without requiring any external VM plugin.
>> 
>> 
>> 
>> I would also like to point out that adding a new backend and host was 
>> possible because of the many iterations (including throwing away whole 
>> implementations) that Alex and Glenn went through. I think they did an 
>> amazing job.
>> 
>> You can find a bit more details about Bloc here:
>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/
>> 
>> Another issue raised regarding Bloc was that of the engineering effort 
>> required to make it a reality. That is why I would also like to announce 
>> that Alex joined feenk.com where he is primarily working on the graphical 
>> stack for Pharo.
>> 
>> Cheers,
>> Doru
>> 
>> 
>> --
>> www.tudorgirba.com
>> www.feenk.com
>> 
>> "To lead is not to demand things, it is to make them happen."
>> 
>> 
>> 
>> 
> 
> 
> 
>

Re: [Pharo-users] [Moose-dev] [Pharo-dev] [ann] bloc & cairo+morphic

2017-05-11 Thread Tudor Girba

Hi,

Indeed, this is wonderful news that you will rejoin your baby project :).

Cheers,
Doru


> On May 11, 2017, at 6:40 PM, Alexandre Bergel  wrote:
> 
> Hi Alain!
> 
> Thanks for the mail (even if the historial part has always been pretty clear 
> to me).
> We miss you! Be back soon!
> 
> Cheers,
> Alexandre
> -- 
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
>> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev 
>>  wrote:
>> 
>> 
>> From: Alain Plantec 
>> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic
>> Date: May 11, 2017 at 12:36:36 PM GMT-3
>> To: Pharo Development List 
>> Cc: Alain Plantec , Moose-related development 
>> , Any question about pharo is welcome 
>> 
>> 
>> 
>> Hello Doru, all,
>> 
>> I’m really happy to see Bloc progresses. 
>> Even I’m not active since more than one year, Bloc is still an important 
>> project for me.
>> 
>> but let me complete this short historical presentation a little bit.
>> 
>> Bloc is a project that I initiated in 2013 in collaboration with RMOD 
>> following experiments made around the ROME project. 
>> The idea was to completely revisit the 2D framework of Pharo to address 
>> Morphic limits. 
>> Following an invitation of the Software Composition Group (thanks to Oscar 
>> Nierstrasz and to Doru here), 
>> I presented the first version of Bloc at Bern (March, 2015), then Doru and 
>> Aliaksel joined the project. 
>> One year ago, during his PhD at Brest, Glenn Cavarle produced a new version 
>> of the Bloc infrastructure that is now the 
>> one used together with the layouting system that was implemented by 
>> Aliaksel. 
>> 
>> Please, do not use the humane assessment web site but the github project one 
>> instead.
>> 
>> I will restart working on Bloc/Brick soon in the context of a project that 
>> we recently signed with the Thales company.
>> 
>> Thanks,
>> Cheers
>> 
>> Alain
>> 
>> 
>>> On 8 mai 2017, at 23:00, Tudor Girba  wrote:
>>> 
>>> Hi,
>>> 
>>> We are happy to announce that based on the work of Glenn, Alex extended 
>>> Bloc (Sparta) to work directly in the Morphic world using Cairo as a 
>>> backend.
>>> 
>>> Cairo is less powerful than Moz2D (see the screenshot below for an 
>>> example), but the implementation addresses a concern that the community 
>>> raised regarding a perceived increased liability due to the dependency to 
>>> Moz2D. Essentially this means that Bloc can be treated as another graphical 
>>> library that can coexist with Morphic without requiring any external VM 
>>> plugin.
>>> 
>>> 
>>> 
>>> I would also like to point out that adding a new backend and host was 
>>> possible because of the many iterations (including throwing away whole 
>>> implementations) that Alex and Glenn went through. I think they did an 
>>> amazing job.
>>> 
>>> You can find a bit more details about Bloc here:
>>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/
>>> 
>>> Another issue raised regarding Bloc was that of the engineering effort 
>>> required to make it a reality. That is why I would also like to announce 
>>> that Alex joined feenk.com where he is primarily working on the graphical 
>>> stack for Pharo.
>>> 
>>> Cheers,
>>> Doru
>>> 
>>> 
>>> --
>>> www.tudorgirba.com
>>> www.feenk.com
>>> 
>>> "To lead is not to demand things, it is to make them happen."
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> 
> 
> ___
> Moose-dev mailing list
> moose-...@list.inf.unibe.ch
> https://www.list.inf.unibe.ch/listinfo/moose-dev

--
www.tudorgirba.com
www.feenk.com

"Yesterday is a fact.
 Tomorrow is a possibility.
 Today is a challenge."

Re: [Pharo-users] [Moose-dev] [Pharo-dev] [ann] bloc & cairo+morphic

Doru can you change the humane assessment blog post?


On Thu, May 11, 2017 at 8:07 PM, Tudor Girba  wrote:

> Hi,
>
> Indeed, this is wonderful news that you will rejoin your baby project :).
>
> Cheers,
> Doru
>
>
> > On May 11, 2017, at 6:40 PM, Alexandre Bergel 
> wrote:
> >
> > Hi Alain!
> >
> > Thanks for the mail (even if the historial part has always been pretty
> clear to me).
> > We miss you! Be back soon!
> >
> > Cheers,
> > Alexandre
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel  http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >> On May 11, 2017, at 12:36 PM, Alain Plantec via Pharo-dev <
> pharo-...@lists.pharo.org> wrote:
> >>
> >>
> >> From: Alain Plantec 
> >> Subject: Re: [Pharo-users] [ann] bloc & cairo+morphic
> >> Date: May 11, 2017 at 12:36:36 PM GMT-3
> >> To: Pharo Development List 
> >> Cc: Alain Plantec , Moose-related development
> , Any question about pharo is welcome <
> pharo-users@lists.pharo.org>
> >>
> >>
> >> Hello Doru, all,
> >>
> >> I’m really happy to see Bloc progresses.
> >> Even I’m not active since more than one year, Bloc is still an
> important project for me.
> >>
> >> but let me complete this short historical presentation a little bit.
> >>
> >> Bloc is a project that I initiated in 2013 in collaboration with RMOD
> following experiments made around the ROME project.
> >> The idea was to completely revisit the 2D framework of Pharo to address
> Morphic limits.
> >> Following an invitation of the Software Composition Group (thanks to
> Oscar Nierstrasz and to Doru here),
> >> I presented the first version of Bloc at Bern (March, 2015), then Doru
> and Aliaksel joined the project.
> >> One year ago, during his PhD at Brest, Glenn Cavarle produced a new
> version of the Bloc infrastructure that is now the
> >> one used together with the layouting system that was implemented by
> Aliaksel.
> >>
> >> Please, do not use the humane assessment web site but the github
> project one instead.
> >>
> >> I will restart working on Bloc/Brick soon in the context of a project
> that we recently signed with the Thales company.
> >>
> >> Thanks,
> >> Cheers
> >>
> >> Alain
> >>
> >>
> >>> On 8 mai 2017, at 23:00, Tudor Girba  wrote:
> >>>
> >>> Hi,
> >>>
> >>> We are happy to announce that based on the work of Glenn, Alex
> extended Bloc (Sparta) to work directly in the Morphic world using Cairo as
> a backend.
> >>>
> >>> Cairo is less powerful than Moz2D (see the screenshot below for an
> example), but the implementation addresses a concern that the community
> raised regarding a perceived increased liability due to the dependency to
> Moz2D. Essentially this means that Bloc can be treated as another graphical
> library that can coexist with Morphic without requiring any external VM
> plugin.
> >>>
> >>> 
> >>>
> >>> I would also like to point out that adding a new backend and host was
> possible because of the many iterations (including throwing away whole
> implementations) that Alex and Glenn went through. I think they did an
> amazing job.
> >>>
> >>> You can find a bit more details about Bloc here:
> >>> http://www.humane-assessment.com/blog/bloc-flexible-backends-hosts/
> >>>
> >>> Another issue raised regarding Bloc was that of the engineering effort
> required to make it a reality. That is why I would also like to announce
> that Alex joined feenk.com where he is primarily working on the graphical
> stack for Pharo.
> >>>
> >>> Cheers,
> >>> Doru
> >>>
> >>>
> >>> --
> >>> www.tudorgirba.com
> >>> www.feenk.com
> >>>
> >>> "To lead is not to demand things, it is to make them happen."
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
> > ___
> > Moose-dev mailing list
> > moose-...@list.inf.unibe.ch
> > https://www.list.inf.unibe.ch/listinfo/moose-dev
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "Yesterday is a fact.
>  Tomorrow is a possibility.
>  Today is a challenge."
>
>
>
>
>
>

Re: [Pharo-users] Not much longer...

excellent!


On Thu, May 11, 2017 at 3:42 PM, Norbert Hartl  wrote:

> On my vacation I saw this progress bar about pharo. So looks close to 6
> for me :)
>
>
>
>

Re: [Pharo-users] Issue with Pillar

Hi alexandre

This is a problem I identified and I'm trying to fix it.
Now the version works for book, it is the one I used for all the booklets
and new books
I'm writing.

Stef


On Wed, May 10, 2017 at 7:42 PM, p...@highoctane.be 
wrote:

> Forget about that way which doesn't work.
>
> Use this: https://github.com/cdlm/docker-texlive
>
> Works nicely and removes 90% of the setup frustration (you'll need latest
> docker-ce for this to work).
>
> Phil
>
> On Wed, May 10, 2017 at 5:38 PM, Alexandre Bergel  > wrote:
>
>> Hi!
>>
>> I am trying to get Pillar working on OS X. I followed the instruction
>> given on https://ci.inria.fr/pharo-contribution/job/EnterprisePhar
>> oBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html
>>
>> I did:
>> curl https://raw.githubusercontent.com/pillar-markup/pillar/maste
>> r/download.sh | bash
>> ./pillar archetype welcome
>> make book-result/welcome.html
>>
>> The two first instruction do not seem to cause any trouble. Work as
>> expected. The make instruction produces:
>> -=-=-=-=
>> /tmp/pillar> make book-result/welcome.html
>> mkdir -p ./book-result
>> find . -type d -path ./book-result -prune -o -wholename "*/figures" -exec
>> cp {} --parents -r ./book-result \;
>> cp -r support/ ./book-result
>> ./pillar export --to=html --outputDirectory=./book-result
>> --outputFile=welcome.pillar welcome.pillar
>> MessageNotUnderstood: FileReference>>jsonWriteOn:
>> FileReference(Object)>>doesNotUnderstand: #jsonWriteOn:
>> [ :assoc |
>> needComma
>> ifTrue: [ aStream nextPut: $, ]
>> ifFalse: [ needComma := true ].
>> assoc key jsonWriteOn: aStream.
>> aStream nextPut: $:.
>> assoc value jsonWriteOn: aStream ] in Dictionary>>jsonWriteOn: in Block:
>> [ :assoc | ...
>> [ :each | each ifNotNil: [ aBlock value: each ] ] in
>> Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock
>> value: each ] ]
>> Array(SequenceableCollection)>>do:
>> Dictionary>>associationsDo:
>> Dictionary>>jsonWriteOn:
>> PRExportPhase>>asJson:withConfiguration:
>> [ :outStream |
>> self
>> writeOutput: (self asJson: output withConfiguration: cocoonConfiguration)
>> toStream: outStream ] in PRExportPhase>>write:using: in Block: [
>> :outStream | ...
>> [ aBlock value: stream ] in 
>> FileReference(AbstractFileReference)>>writeStreamDo:
>> in Block: [ aBlock value: stream ]
>> BlockClosure>>ensure:
>> FileReference(AbstractFileReference)>>writeStreamDo:
>> FileReference(AbstractFileReference)>>pillarWriteDuring:
>> PRExportPhase>>outputStreamDuring:
>> PRExportPhase>>write:using:
>> PRExportPhase>>actionOn:
>> PRExportPhase class(PRPhase class)>>executeOn:
>> [ :input | self executeOn: input ] in PRExportPhase class(PRPhase
>> class)>>buildPipe: in Block: [ :input | self executeOn: input ]
>> LPPhase>>executeOn:
>> [ :subResult :next | next executeOn: subResult ] in
>> LPPipeline>>executeOn: in Block: [ :subResult :next | next executeOn:
>> subResult ]
>> [ :each | nextValue := binaryBlock value: nextValue value: each ] in
>> OrderedCollection(Collection)>>inject:into: in Block: [ :each |
>> nextValue := binaryBlock value: nextValu...etc...
>> OrderedCollection>>do:
>> OrderedCollection(Collection)>>inject:into:
>> LPPipeline>>executeOn:
>> PRPillarConfiguration>>export
>> [ :exporter | (configuration getConfigurationNamed: exporter) export ] in
>> [ configuration defaultExporters
>> do: [ :exporter | (configuration getConfigurationNamed: exporter) export
>> ] ] in PRExportCommandLineHandler>>export in Block: [ :exporter |
>> (configuration getConfigurationNamed...etc...
>> Array(SequenceableCollection)>>do:
>> [ configuration defaultExporters
>> do: [ :exporter | (configuration getConfigurationNamed: exporter) export
>> ] ] in PRExportCommandLineHandler>>export in Block: [ configuration
>> defaultExporters...
>> BlockClosure>>on:do:
>> PRExportCommandLineHandler>>export
>> PRExportCommandLineHandler>>activate
>> make: *** [book-result/welcome.html.json] Error 1
>> rm book-result/welcome.html.json
>> -=-=-=-=
>>
>> Any idea what’s wrong?
>>
>> Cheers,
>> Alexandre
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel  http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>

Re: [Pharo-users] Issue with Pillar

so
./pillar archetype book

will work.

On Thu, May 11, 2017 at 8:43 PM, Stephane Ducasse 
wrote:

> Hi alexandre
>
> This is a problem I identified and I'm trying to fix it.
> Now the version works for book, it is the one I used for all the booklets
> and new books
> I'm writing.
>
> Stef
>
>
> On Wed, May 10, 2017 at 7:42 PM, p...@highoctane.be 
> wrote:
>
>> Forget about that way which doesn't work.
>>
>> Use this: https://github.com/cdlm/docker-texlive
>>
>> Works nicely and removes 90% of the setup frustration (you'll need latest
>> docker-ce for this to work).
>>
>> Phil
>>
>> On Wed, May 10, 2017 at 5:38 PM, Alexandre Bergel <
>> alexandre.ber...@me.com> wrote:
>>
>>> Hi!
>>>
>>> I am trying to get Pillar working on OS X. I followed the instruction
>>> given on https://ci.inria.fr/pharo-contribution/job/EnterprisePhar
>>> oBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html
>>>
>>> I did:
>>> curl https://raw.githubusercontent.com/pillar-markup/pillar/maste
>>> r/download.sh | bash
>>> ./pillar archetype welcome
>>> make book-result/welcome.html
>>>
>>> The two first instruction do not seem to cause any trouble. Work as
>>> expected. The make instruction produces:
>>> -=-=-=-=
>>> /tmp/pillar> make book-result/welcome.html
>>> mkdir -p ./book-result
>>> find . -type d -path ./book-result -prune -o -wholename "*/figures"
>>> -exec cp {} --parents -r ./book-result \;
>>> cp -r support/ ./book-result
>>> ./pillar export --to=html --outputDirectory=./book-result
>>> --outputFile=welcome.pillar welcome.pillar
>>> MessageNotUnderstood: FileReference>>jsonWriteOn:
>>> FileReference(Object)>>doesNotUnderstand: #jsonWriteOn:
>>> [ :assoc |
>>> needComma
>>> ifTrue: [ aStream nextPut: $, ]
>>> ifFalse: [ needComma := true ].
>>> assoc key jsonWriteOn: aStream.
>>> aStream nextPut: $:.
>>> assoc value jsonWriteOn: aStream ] in Dictionary>>jsonWriteOn: in Block:
>>> [ :assoc | ...
>>> [ :each | each ifNotNil: [ aBlock value: each ] ] in
>>> Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock
>>> value: each ] ]
>>> Array(SequenceableCollection)>>do:
>>> Dictionary>>associationsDo:
>>> Dictionary>>jsonWriteOn:
>>> PRExportPhase>>asJson:withConfiguration:
>>> [ :outStream |
>>> self
>>> writeOutput: (self asJson: output withConfiguration: cocoonConfiguration)
>>> toStream: outStream ] in PRExportPhase>>write:using: in Block: [
>>> :outStream | ...
>>> [ aBlock value: stream ] in 
>>> FileReference(AbstractFileReference)>>writeStreamDo:
>>> in Block: [ aBlock value: stream ]
>>> BlockClosure>>ensure:
>>> FileReference(AbstractFileReference)>>writeStreamDo:
>>> FileReference(AbstractFileReference)>>pillarWriteDuring:
>>> PRExportPhase>>outputStreamDuring:
>>> PRExportPhase>>write:using:
>>> PRExportPhase>>actionOn:
>>> PRExportPhase class(PRPhase class)>>executeOn:
>>> [ :input | self executeOn: input ] in PRExportPhase class(PRPhase
>>> class)>>buildPipe: in Block: [ :input | self executeOn: input ]
>>> LPPhase>>executeOn:
>>> [ :subResult :next | next executeOn: subResult ] in
>>> LPPipeline>>executeOn: in Block: [ :subResult :next | next executeOn:
>>> subResult ]
>>> [ :each | nextValue := binaryBlock value: nextValue value: each ] in
>>> OrderedCollection(Collection)>>inject:into: in Block: [ :each |
>>> nextValue := binaryBlock value: nextValu...etc...
>>> OrderedCollection>>do:
>>> OrderedCollection(Collection)>>inject:into:
>>> LPPipeline>>executeOn:
>>> PRPillarConfiguration>>export
>>> [ :exporter | (configuration getConfigurationNamed: exporter) export ]
>>> in [ configuration defaultExporters
>>> do: [ :exporter | (configuration getConfigurationNamed: exporter) export
>>> ] ] in PRExportCommandLineHandler>>export in Block: [ :exporter |
>>> (configuration getConfigurationNamed...etc...
>>> Array(SequenceableCollection)>>do:
>>> [ configuration defaultExporters
>>> do: [ :exporter | (configuration getConfigurationNamed: exporter) export
>>> ] ] in PRExportCommandLineHandler>>export in Block: [ configuration
>>> defaultExporters...
>>> BlockClosure>>on:do:
>>> PRExportCommandLineHandler>>export
>>> PRExportCommandLineHandler>>activate
>>> make: *** [book-result/welcome.html.json] Error 1
>>> rm book-result/welcome.html.json
>>> -=-=-=-=
>>>
>>> Any idea what’s wrong?
>>>
>>> Cheers,
>>> Alexandre
>>>
>>> --
>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>> Alexandre Bergel  http://www.bergel.eu
>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>
>>>
>>>
>>>
>>
>

Re: [Pharo-users] Intro to git-only Pharo

Joachim

many people are using Pharo to develop ***COMPLEX*** Pharo applications and
it works. They use monticello and metacello and it works.
So you do not have to have Github to make great software in Pharo.

Now in addition many people are using github to build complex applications
with github.

Stef


On Thu, May 11, 2017 at 9:54 AM, Norbert Hartl  wrote:

>
> Am 11.05.2017 um 08:54 schrieb jtuc...@objektfabrik.de:
>
> Hi Norbert,
>
> thanks for your explanations.
> So it seems liek I should start by using Pharo6 and load Iceberg and just
> take a look.
>
> Yes, iceberg has still some issues but is usable and it will evolve
> quickly. If you are the brave type of guy you can start with pharo6 64bits
> ;)
>
> Norbert
>
> Joachim
>
>
>
> Am 10.05.17 um 10:34 schrieb Norbert Hartl:
>
> Hi Joachim,
>
> I think your timing is quite good. We had some changes in the last years
> and it is getting better now.
> Before we had only monticello. Monticello is a zip container that contains
> a version number in the filename and prior version pointer inside the
> repository. Regarding dependencies there was nothing that was used widely.
> Then Metacello appeared and solved the problem by providing dependency
> management and versioning of dependencies. Dependency management works
> good, the integrated versioning has issues. Especially when you look at a
> system like git you can see that versioning is solved there. Filetree is
> needed because git and other vcs systems are file based so you need to
> layout your code in files (how quaint!)
> To make a long story short: The best thing to use is git with Metacello
> Baselines. Filetree is used to store code. Versioning you do with git tags
> that can be used in Baselines. Now we have a decent UI (iceberg) that
> supports the most needed workflow items.
> We have a UI for the dependency management as well (versionner) but it
> sadly targets ConfigurationOfs and not BaselineOfs. That needs to be
> changed.
>
> my 2 cents,
>
> Norbert
>
> Am 10.05.2017 um 07:56 schrieb Joachim Tuchel :
>
> Hi guys,
>
> please forgive me if this mail is a sign of ignorance. I am not a regular
> Pharo user and one of the reasons for this is that I didn't like most of
> the source management tools around Monticello. Coming from an envy
> background, it feels like not being ready for prime time. Of course you
> guys have been proving you can work with these tools quite well, but still
> I'd be interested in using Pharo in a pure git-based environment, as it
> most closely resembles some of the most-beloved features of envy.
>
> Over the years there was a lot of work and discussion on filetree,
> gitfiletree, iceberg, cypress and maybe quite a few other projects that
> sounded promising and interesting. But I must admit I lost track of what
> was really done and how far things went in the last years.
>
> So are there any pointers to info material that I could look at to see
> what the current status of source control in Pharo 5 and Pharo 6 is and/or
> will be soon?
>
> I am mostly interested in these topics:
>
>- git only - no monticello meta info any more - possible?
>- tools like merge/diff, committing from within the image
>- dependencies within my own project as well as dependencies on
>external code in - possibly multiple - external repositories
>- what is the current "most official" source repository for open
>source code?
>- best practices for managing complex projects and keeping old
>versions reproducible at any time
>- tutorial for git newbies in a Pharo context? (Like, how do I start
>with a new packege - create folder first and do git init, or start in the
>image and push into repo later? as I said: beginners' stuff)
>
> Thanks for pointers and help
>
>
> Joachim
>
>
>
>
>
> --
> ---
> Objektfabrik Joachim Tuchel  mailto:jtuc...@objektfabrik.de 
> 
> Fliederweg 1 http://www.objektfabrik.de
> D-71640 Ludwigsburg  http://joachimtuchel.wordpress.com
> Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1
>
>
>
>

Re: [Pharo-users] Petri nets and workflow patterns

yes :)
I contacted the guy to ask for the smalltalk code but he never replied to
me may be someone else should try.

stef

On Thu, May 11, 2017 at 9:59 AM, Serge Stinckwich <
serge.stinckw...@gmail.com> wrote:

> On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse
>  wrote:
> > Norbert
> >
> > I know petri nets and I was wondering if you were interested in worklow
> (as
> > in microworkflow).
> > because I think that a simple extensible workflow library is missing in
> > Pharo
>
> I guess you talk about this: http://micro-workflow.com/phdthesis/
>
> --
> Serge Stinckwich
> UCN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
>
>

Re: [Pharo-users] Intro to git-only Pharo

2017-05-11 Thread Thierry Goubier


Le 11/05/2017 à 20:52, Stephane Ducasse a écrit :

Joachim

many people are using Pharo to develop ***COMPLEX*** Pharo applications
and it works. They use monticello and metacello and it works.
So you do not have to have Github to make great software in Pharo.

Now in addition many people are using github to build complex applications
with github.


And people have been building complex applications with Monticello, 
Metacello and Github...


Thierry



Stef


On Thu, May 11, 2017 at 9:54 AM, Norbert Hartl mailto:norb...@hartl.name>> wrote:



Am 11.05.2017 um 08:54 schrieb jtuc...@objektfabrik.de
:

Hi Norbert,

thanks for your explanations.
So it seems liek I should start by using Pharo6 and load Iceberg
and just take a look.


Yes, iceberg has still some issues but is usable and it will evolve
quickly. If you are the brave type of guy you can start with pharo6
64bits ;)

Norbert


Joachim



Am 10.05.17 um 10:34 schrieb Norbert Hartl:

Hi Joachim,

I think your timing is quite good. We had some changes in the
last years and it is getting better now.
Before we had only monticello. Monticello is a zip container that
contains a version number in the filename and prior version
pointer inside the repository. Regarding dependencies there was
nothing that was used widely. Then Metacello appeared and solved
the problem by providing dependency management and versioning of
dependencies. Dependency management works good, the integrated
versioning has issues. Especially when you look at a system like
git you can see that versioning is solved there. Filetree is
needed because git and other vcs systems are file based so you
need to layout your code in files (how quaint!)
To make a long story short: The best thing to use is git with
Metacello Baselines. Filetree is used to store code. Versioning
you do with git tags that can be used in Baselines. Now we have a
decent UI (iceberg) that supports the most needed workflow items.
We have a UI for the dependency management as well (versionner)
but it sadly targets ConfigurationOfs and not BaselineOfs. That
needs to be changed.

my 2 cents,

Norbert


Am 10.05.2017 um 07:56 schrieb Joachim Tuchel
mailto:jtuc...@objektfabrik.de>>:

Hi guys,

please forgive me if this mail is a sign of ignorance. I am not
a regular Pharo user and one of the reasons for this is that I
didn't like most of the source management tools around
Monticello. Coming from an envy background, it feels like not
being ready for prime time. Of course you guys have been proving
you can work with these tools quite well, but still I'd be
interested in using Pharo in a pure git-based environment, as it
most closely resembles some of the most-beloved features of envy.

Over the years there was a lot of work and discussion on
filetree, gitfiletree, iceberg, cypress and maybe quite a few
other projects that sounded promising and interesting. But I
must admit I lost track of what was really done and how far
things went in the last years.

So are there any pointers to info material that I could look at
to see what the current status of source control in Pharo 5 and
Pharo 6 is and/or will be soon?

I am mostly interested in these topics:

  * git only - no monticello meta info any more - possible?
  * tools like merge/diff, committing from within the image
  * dependencies within my own project as well as dependencies
on external code in - possibly multiple - external repositories
  * what is the current "most official" source repository for
open source code?
  * best practices for managing complex projects and keeping old
versions reproducible at any time
  * tutorial for git newbies in a Pharo context? (Like, how do I
start with a new packege - create folder first and do git
init, or start in the image and push into repo later? as I
said: beginners' stuff)

Thanks for pointers and help


Joachim







--
---
Objektfabrik Joachim Tuchel  mailto:jtuc...@objektfabrik.de
Fliederweg 1 http://www.objektfabrik.de 

D-71640 Ludwigsburg  http://joachimtuchel.wordpress.com

Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

Re: [Pharo-users] Petri nets and workflow patterns

2017-05-11 Thread serge . stinckwich

I ask him but he don't have the code anymore, maybe this is possible to do a 
retroengineering from the PhD thesis ?

Envoyé de mon iPhone

> Le 11 mai 2017 à 20:54, Stephane Ducasse  a écrit :
> 
> yes :)
> I contacted the guy to ask for the smalltalk code but he never replied to me 
> may be someone else should try. 
> 
> stef
> 
>> On Thu, May 11, 2017 at 9:59 AM, Serge Stinckwich 
>>  wrote:
>> On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse
>>  wrote:
>> > Norbert
>> >
>> > I know petri nets and I was wondering if you were interested in worklow (as
>> > in microworkflow).
>> > because I think that a simple extensible workflow library is missing in
>> > Pharo
>> 
>> I guess you talk about this: http://micro-workflow.com/phdthesis/
>> 
>> --
>> Serge Stinckwich
>> UCN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>> 
>

[Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding

2017-05-11 Thread Udo Schneider


All,

I'm hitting an error where fetching web content fails. The website does 
indeed use invalid characters.


The easiest way to reproduce:

ZnEasy get: 
'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-with-a-new-(borrowed)-distribution-method/a/d-id/1328723'


Is there any way to tell Zinc to simply ignore that error and to continue?

CU,

Udo

Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding

2017-05-11 Thread Sven Van Caekenberghe

Hi Udo,

> On 11 May 2017, at 21:37, Udo Schneider  wrote:
> 
> All,
> 
> I'm hitting an error where fetching web content fails. The website does 
> indeed use invalid characters.
> 
> The easiest way to reproduce:
> 
> ZnEasy get: 
> 'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-with-a-new-(borrowed)-distribution-method/a/d-id/1328723'
> 
> Is there any way to tell Zinc to simply ignore that error and to continue?
> 
> CU,
> 
> Udo

That server/page has a mime-type text/plain with no explicit encoding (charset) 
setting, so we have to guess. Like utf-8, pure latin1/iso88591 does not work. 
The following does work, but you can't be sure everything went well (beLenient 
takes some bytes as they are).

ZnDefaultCharacterEncoder 
  value: ZnCharacterEncoder latin1 beLenient 
  during: [ 
ZnClient new 
  get: 
'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-with-a-new-(borrowed)-distribution-method/a/d-id/1328723';

  yourself ].

I added some API earlier today, so that the following should also work (you 
need to load Zn #bleedingEdge first).

ZnClient new 
  defaultEncoder: ZnCharacterEncoder latin1 beLenient; 
  get: 
'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-with-a-new-(borrowed)-distribution-method/a/d-id/1328723';
  yourself. 

HTH,

Regards,

Sven

Re: [Pharo-users] [Zinc] ZnInvalidUTF8: Illegal leading byte for utf-8 encoding

2017-05-11 Thread Udo Schneider

Hi Sven,

that's perfect. To be honest I don't care about the content - I'm just
parsing the header. And even if there is a wrong decoding in there... I
can live with that.

Thank you very very much! For your help but also your stuff in general.

CU,

Udo

Am 11/05/17 um 22:35 schrieb Sven Van Caekenberghe:

Hi Udo,

On 11 May 2017, at 21:37, Udo Schneider wrote:

All,

I'm hitting an error where fetching web content fails. The website does indeed
use invalid characters.

The easiest way to reproduce:

ZnEasy get:
'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-with-a-new-(borrowed)-distribution-method/a/d-id/1328723'

Is there any way to tell Zinc to simply ignore that error and to continue?

CU,

Udo

That server/page has a mime-type text/plain with no explicit encoding (charset)
setting, so we have to guess. Like utf-8, pure latin1/iso88591 does not work.
The following does work, but you can't be sure everything went well (beLenient
takes some bytes as they are).

ZnDefaultCharacterEncoder
value: ZnCharacterEncoder latin1 beLenient
during: [
ZnClient new
get:
'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-with-a-new-(borrowed)-distribution-method/a/d-id/1328723';
yourself ].

I added some API earlier today, so that the following should also work (you
need to load Zn #bleedingEdge first).

ZnClient new

defaultEncoder: ZnCharacterEncoder latin1 beLenient;
get:
'http://www.darkreading.com/partner-perspectives/malwarebytes/locky-returns-with-a-new-(borrowed)-distribution-method/a/d-id/1328723';
yourself.

HTH,

Regards,

Sven

Re: [Pharo-users] Issue with Pillar

Will work in creating the book artifact.

But not the PDF because of some crap in TeX.

Docker container alleviates that pain.

We could make a book builder thing using AppVeyor and docker I think.

Phil

On Thu, May 11, 2017 at 8:44 PM, Stephane Ducasse 
wrote:

> so
> ./pillar archetype book
>
> will work.
>
> On Thu, May 11, 2017 at 8:43 PM, Stephane Ducasse  > wrote:
>
>> Hi alexandre
>>
>> This is a problem I identified and I'm trying to fix it.
>> Now the version works for book, it is the one I used for all the booklets
>> and new books
>> I'm writing.
>>
>> Stef
>>
>>
>> On Wed, May 10, 2017 at 7:42 PM, p...@highoctane.be 
>> wrote:
>>
>>> Forget about that way which doesn't work.
>>>
>>> Use this: https://github.com/cdlm/docker-texlive
>>>
>>> Works nicely and removes 90% of the setup frustration (you'll need
>>> latest docker-ce for this to work).
>>>
>>> Phil
>>>
>>> On Wed, May 10, 2017 at 5:38 PM, Alexandre Bergel <
>>> alexandre.ber...@me.com> wrote:
>>>
 Hi!

 I am trying to get Pillar working on OS X. I followed the instruction
 given on https://ci.inria.fr/pharo-contribution/job/EnterprisePhar
 oBook/lastSuccessfulBuild/artifact/book-result/PillarChap/Pillar.html

 I did:
 curl https://raw.githubusercontent.com/pillar-markup/pillar/maste
 r/download.sh | bash
 ./pillar archetype welcome
 make book-result/welcome.html

 The two first instruction do not seem to cause any trouble. Work as
 expected. The make instruction produces:
 -=-=-=-=
 /tmp/pillar> make book-result/welcome.html
 mkdir -p ./book-result
 find . -type d -path ./book-result -prune -o -wholename "*/figures"
 -exec cp {} --parents -r ./book-result \;
 cp -r support/ ./book-result
 ./pillar export --to=html --outputDirectory=./book-result
 --outputFile=welcome.pillar welcome.pillar
 MessageNotUnderstood: FileReference>>jsonWriteOn:
 FileReference(Object)>>doesNotUnderstand: #jsonWriteOn:
 [ :assoc |
 needComma
 ifTrue: [ aStream nextPut: $, ]
 ifFalse: [ needComma := true ].
 assoc key jsonWriteOn: aStream.
 aStream nextPut: $:.
 assoc value jsonWriteOn: aStream ] in Dictionary>>jsonWriteOn: in
 Block: [ :assoc | ...
 [ :each | each ifNotNil: [ aBlock value: each ] ] in
 Dictionary>>associationsDo: in Block: [ :each | each ifNotNil: [ aBlock
 value: each ] ]
 Array(SequenceableCollection)>>do:
 Dictionary>>associationsDo:
 Dictionary>>jsonWriteOn:
 PRExportPhase>>asJson:withConfiguration:
 [ :outStream |
 self
 writeOutput: (self asJson: output withConfiguration:
 cocoonConfiguration)
 toStream: outStream ] in PRExportPhase>>write:using: in Block: [
 :outStream | ...
 [ aBlock value: stream ] in 
 FileReference(AbstractFileReference)>>writeStreamDo:
 in Block: [ aBlock value: stream ]
 BlockClosure>>ensure:
 FileReference(AbstractFileReference)>>writeStreamDo:
 FileReference(AbstractFileReference)>>pillarWriteDuring:
 PRExportPhase>>outputStreamDuring:
 PRExportPhase>>write:using:
 PRExportPhase>>actionOn:
 PRExportPhase class(PRPhase class)>>executeOn:
 [ :input | self executeOn: input ] in PRExportPhase class(PRPhase
 class)>>buildPipe: in Block: [ :input | self executeOn: input ]
 LPPhase>>executeOn:
 [ :subResult :next | next executeOn: subResult ] in
 LPPipeline>>executeOn: in Block: [ :subResult :next | next executeOn:
 subResult ]
 [ :each | nextValue := binaryBlock value: nextValue value: each ] in
 OrderedCollection(Collection)>>inject:into: in Block: [ :each |
 nextValue := binaryBlock value: nextValu...etc...
 OrderedCollection>>do:
 OrderedCollection(Collection)>>inject:into:
 LPPipeline>>executeOn:
 PRPillarConfiguration>>export
 [ :exporter | (configuration getConfigurationNamed: exporter) export ]
 in [ configuration defaultExporters
 do: [ :exporter | (configuration getConfigurationNamed: exporter)
 export ] ] in PRExportCommandLineHandler>>export in Block: [ :exporter
 | (configuration getConfigurationNamed...etc...
 Array(SequenceableCollection)>>do:
 [ configuration defaultExporters
 do: [ :exporter | (configuration getConfigurationNamed: exporter)
 export ] ] in PRExportCommandLineHandler>>export in Block: [
 configuration defaultExporters...
 BlockClosure>>on:do:
 PRExportCommandLineHandler>>export
 PRExportCommandLineHandler>>activate
 make: *** [book-result/welcome.html.json] Error 1
 rm book-result/welcome.html.json
 -=-=-=-=

 Any idea what’s wrong?

 Cheers,
 Alexandre

 --
 _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
 Alexandre Bergel  http://www.bergel.eu
 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.




>>>
>>
>

Re: [Pharo-users] Petri nets and workflow patterns

I read that paper too and I was wondering about the trempoline piece he
uses.

Is there someone having implemented that using Pharo? His code was VW.

Phil

On Thu, May 11, 2017 at 8:54 PM, Stephane Ducasse 
wrote:

> yes :)
> I contacted the guy to ask for the smalltalk code but he never replied to
> me may be someone else should try.
>
> stef
>
> On Thu, May 11, 2017 at 9:59 AM, Serge Stinckwich <
> serge.stinckw...@gmail.com> wrote:
>
>> On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse
>>  wrote:
>> > Norbert
>> >
>> > I know petri nets and I was wondering if you were interested in worklow
>> (as
>> > in microworkflow).
>> > because I think that a simple extensible workflow library is missing in
>> > Pharo
>>
>> I guess you talk about this: http://micro-workflow.com/phdthesis/
>>
>> --
>> Serge Stinckwich
>> UCN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>>
>>
>

Re: [Pharo-users] Petri nets and workflow patterns

There is code in several papers, including this one:

https://www.dropbox.com/s/lc2ev4841lzn9q0/Worfklow-Continuations.pdf?dl=0

Phil



On Thu, May 11, 2017 at 9:07 PM,  wrote:

> I ask him but he don't have the code anymore, maybe this is possible to do
> a retroengineering from the PhD thesis ?
>
> Envoyé de mon iPhone
>
> Le 11 mai 2017 à 20:54, Stephane Ducasse  a
> écrit :
>
> yes :)
> I contacted the guy to ask for the smalltalk code but he never replied to
> me may be someone else should try.
>
> stef
>
> On Thu, May 11, 2017 at 9:59 AM, Serge Stinckwich <
> serge.stinckw...@gmail.com> wrote:
>
>> On Wed, May 10, 2017 at 10:09 PM, Stephane Ducasse
>>  wrote:
>> > Norbert
>> >
>> > I know petri nets and I was wondering if you were interested in worklow
>> (as
>> > in microworkflow).
>> > because I think that a simple extensible workflow library is missing in
>> > Pharo
>>
>> I guess you talk about this: http://micro-workflow.com/phdthesis/
>>
>> --
>> Serge Stinckwich
>> UCN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>>
>>
>

Re: [Pharo-users] Wandering Through Dependency Hell

2017-05-11 Thread Evan Donahue

Thanks for the replies.

With Juraj's help, I figured out the first layer of my problem. I needed to
recompile all the methods after loading the code with Monticello, because
their bytecode was all messed up. Now I can get code out of the image via
plain Monticello. Tests were failing not because of reversion, but because
of random bytecode issues. There is still some odd versioning behavior, but
it's not my biggest problem.

Now I am trying to create a ConfigurationOf with Versionner. I followed this
video:

https://www.youtube.com/watch?v=cFRJDuWL-Q0

When I go to commit, Versionner gives me an array out of bounds due to the
"KommitStagingArea" not having any elements in its packages array. Sometimes
this yields no upload, sometimes it uploads a Config that does not seem to
work when I try to download with it, and sometimes I get a debugger on
smalltalkhub while trying to view the source. I'm not sure how to predict or
interpret which will happen.

Essentially, I am just trying to find the simplest, easiest way to let
people download a project and its dependencies. The above errors have
happened in more or less every project I've tried to commit, and I know
other people don't have the same difficulty I do in trying to get code out
of and into an image, so I suspect that it is something about my workflow
that is off, or possibly my computer. So my first question is, is that video
still up to date, or has the system changed?

Thanks,
Sorry for what I know is not a lot of detail. I'm not really sure where to
start with this one.
Evan





--
View this message in context: 
http://forum.world.st/Wandering-Through-Dependency-Hell-tp4946266p4946815.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] [Moose-dev] [Pharo-dev] [ann] bloc & cairo+morphic