Posted by
Ben Coman on
Jun 17, 2012; 1:11pm
URL: https://forum.world.st/Re-Pharo-project-start-thinking-on-summer-release-of-Pharo-1-4-tp4634610p4635195.html
Esteban Lorenzano wrote:
On Jun 17, 2012, at 5:10 AM, Ben Coman wrote:
Is Nautilus under any consideration to be the default browser for your summer release at all, or are you firmly committed to OB?
I need to know this to continue updating Pharo By Example for 1.4.
this is an interesting and important issue (much more than codenames, he).
I will extend my latest answer, using what I know (maybe Benjamin has another idea, and would be good to know it):
Nautilus is in development, there are some important functionalities that are not there yet, and some others that does not work properly. Refactors and Traits is the most important things I can think of now, but there are probably more.
Also, Nautilus relies in RPackage, which was not ready for 1.4 (but will be ready for 2.0). And some other packages (like OB itself) can be not-loadable after installing Nautilus.
To make all of this work in 1.4 can be a huge job (at least for RPackage, it is, I don't know for Nautilus). I know that RPackage cannot be backported without a lot of effort, but I don't know if Nautilus for 1.4 can be adapted to not use RPackage easily (which AFAIK, should be necessary to make it work propertly).
So, I will like your work (which is IMO terribly important) would take Nautilus. But I also think that loading it for default in 1.4 is probably too much.
Frankly, I don't know what to do now :)
Esteban
This aligns somewhat with my own view. I see a lot of positive
feedback about Nautilus from those that are experienced and confident
to deal with any remaining rough edges - but if a few do remain, then
newcomers are left wondering "what have I done wrong" since they don't
know any better.
A few other considerations from my perspective...
- The existing PBE uses snapshots of OB, so there is less work to
update to 1.4 with OB than with Nautilus.
- I haven't used Nautilus much yet (though I plan to) and would not be
confident to write about it at this time.
- Each chapter should be self contained. An instruction how to load OB
in Chapter 1 being required for a later chapter is not ideal.
Now I am not in a position to dictate, but to draw a line in the sand
for me to proceed, unless vetoed I shall use OB for the 1.4 update to
Pharo By Example. For the inclusion of examples like
BouncingAtomsMorph I am planning to have a ConfigurationOfPBE produce a
PBE.image from a vanilla Pharo1.4.image, which could include OB if
required. So it is not essential for PBE to have OB as the default
browser for 1.4.1, but would still be nice for newcomers to match the
documentation.
cheers -ben
_______________________________________________
Sbe-discussion mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/sbe-discussion