Hi, On 11 Dec 2011, at 15:49, Esteban Lorenzano wrote:
Hi Lukas,
I just loaded Magritte2 into Pharo 1.4 and it loads well with all tests in green. Also, Magritte-Morph loads and seems to run well... just a small change:
replace:
PluggableListMorphOfMany
with:
PluggableListMorph ... beMultipleSelection
Thanks for looking into this :).
(now, I want to deprecate #description for #magritteDescription and add a pragma builder with <magritte> and <magritteContainer> keywords :)
I think that would be most welcome. Cheers, Doru
cheers, Esteban
El 11/12/2011, a las 10:58a.m., Stéphane Ducasse escribió:
Thanks for this really bad and sad message. So you are implying that Seaside, Magritte, Pier, OB, PetitParser will not be maintained on Pharo 1.4.
This is important for us to know that and this is a really nice stab in our back and this will kill a lot of the effort we build over the years.
Thanks again lukas! At least this is clear.
Stef
On Dec 11, 2011, at 12:33 PM, Lukas Renggli wrote:
- then that OB can be loaded on top of Pharo. Remember we are not against OB we just do not have the knowledge to maintain it. So if lukas gets OB working for 1.4 beta then we will probably include in Pharo. Now if OB is working for 1.4 only three months after 1.4 is released then we will not include it.
Yes please, do not wait for me.
Just to repeat myself: With Pharo 1.4 having uncountable changes in core parts of the system and with the system including more and more forked and increasingly incompatible versions of packages (AST, RB, FS, Shout, Regex, ...) I am unwilling to go through the same pain as with Pharo 1.3 again. In the current state, I don't see any of the code I am involved with (including Seaside, Magritte, Pier, OB, PetitParser, ...) to move forward. I suspect that moving to another development platform soon causes less pain than to move to adopt the next Pharo :-(
Lukas
-- Lukas Renggli www.lukas-renggli.ch
-- www.tudorgirba.com "Quality cannot be an afterthought."