2016-05-24 16:18 GMT+02:00 Esteban Lorenzano <esteba...@gmail.com>:

>
> On 24 May 2016, at 16:11, Thierry Goubier <thierry.goub...@gmail.com>
> wrote:
>
>
>
> 2016-05-24 15:18 GMT+02:00 Dimitris Chloupis <kilon.al...@gmail.com>:
>
>> Well technically the python part works fine, BUT I also always wanted it
>> to be friendly to begineers . So nope , its same project. And you are
>> correct its still focused in coding 3d graphics but I came to realisation
>> that if I want some people to use it, obviously i dont expect the massive
>> majority to give up the comforts of python but for those that are curious I
>> have to provide an enviroment thats is even easier to code in than python
>> is currently for Blender.
>>
>> My goal is to provide a development enviroment for Blender addons that is
>> simple, and easy to use and learn.
>>
>> So providing a minimal pharo image that is self documented has always
>> being a dream for Ephestos.
>>
>> By the way whats the news on the matter of modular pharo image ? Is there
>> any work done to provide a minimal pharo image ?
>>
>
> There is a minimal image, which is I think usable as-is, except that what
> you want is something in between the minimal image (no gui, no tools) and a
> full image, and that is a bit complex to set-up.
>
> I started some work on doing that with Pharo4 (put a place with baselines
> I could use to load the HEAD of the Pharo main repository and load the
> right packages), but Pharo5 changed the way external projects are included,
> and my approach wasn't good anymore.
>
> I think the overall Pharo organisation could benefit from such an effort;
> it would exercise all the planned mechanisms for the modular image, in
> maybe an easier way than a modular full image, and with someone motivated
> to debug and maintain the process: you!
>
>
> honestly, I wouldn’t.
> working in a parallel image is too much work (believe me, I know something
> about keeping an image going).
>

Well, I am technically working in a parallel image for the past ... 3 years
? So, no, as long as you handle a changing minimal image and a well
mastered set of slow changing packages over it, it is doable.

The base Pharo isn't changing much. As long as you don't use what is
changing a lot, then this is doable. Maintaining changes all over all the
fast moving packages that are in the full Pharo, then I agree with you,
Esteban.


> Pavel and Christophe are working on the bootstrap process who should be
> working in one-two months, with that, building custom images will be
> finally a reality…from there you might want to give it a try.
>

This, given the timeframe, is both an excellent suggestion and good to know
:)


> But I would better invest on document (something that you have been doing
> very well and I’m very thankful for that) than in keeping alive what is, in
> fact, a fork.
>

Racing to document all the fast moving packages in Pharo can really be a
challenge, still.

Thierry


>
> cheers,
> Esteban
>
>
> Thierry
>
>
>
>
>>
>> I would hate to replicate what is already done.
>>
>> On Tue, May 24, 2016 at 3:59 PM Ben Coman <b...@openinworld.com> wrote:
>>
>>> On Tue, May 24, 2016 at 7:01 PM, Dimitris Chloupis
>>> <kilon.al...@gmail.com> wrote:
>>> > So I was reading the complains from Sven and got Inspiration from
>>> Torsten
>>> > Pharo image and CUIs and made me wonder what if we had an image which
>>> has
>>> > the least amount of libraries and every library inside it is full
>>> commented
>>> > in class, package and method and even has tutorial using inside help
>>> tool.
>>> >
>>> > So I think I will give this project a try. I know there is a plan to
>>> make
>>> > pharo image more modular, but modularity does not equal minimalism ,
>>> > simplicity and ease of use.
>>> >
>>> > I think I will follow the CUIs example and do the development via
>>> Github.
>>> >
>>> > But I am open to ideas and suggestions.
>>> >
>>> > My intention is to remove the excess fat, to make Pharo prettier
>>> (improve
>>> > theme support and make available several themes ) and to have
>>> everything
>>> > commented and self documented.
>>> >
>>> > Obviously this will be a long term project and in no way a walk in the
>>> park
>>> > but I was looking for a nice project to name "Ephestos" :D seem as
>>> good as
>>> > any
>>>
>>> Did this project not pane out?...
>>>
>>> https://pharoweekly.wordpress.com/2014/07/16/ephestos-using-and-coding-blender-from-inside-pharo/
>>>
>>> Seems you're quite attached to that name :)
>>> but is there a minor chance of confusion?
>>>
>>> cheers -ben
>>>
>>>
>
>

Reply via email to