Would the Spoon project be relevant for this scenario? Craig mentioned
on the Spoon list that he is working with Cuis.
On 4/23/12 11:53 AM, Bernhard Pieber wrote:
Hi Göran,
Thanks for your question! I have posted the announcement of the Styled Text
Editor to the Pharo list as well because I still have not given up on the idea
to port it to Squeak and Pharo. It is not straightforward but I consider it
possible.
Currently the Styled Text Editor is an external package which is loaded on top
of Cuis 4.0. The API it uses is quite specific to Cuis so to port it alone is
probably too much effort. What I think can be done is the following:
Split Cuis into three parts,
a) the parts which are not needed for Styled Text Editor, like the Cuis tools
b) the parts of Cuis Morphic the Styled Text Editor depends on – this is in my
opinion the most valuable part of Cuis because Juan spent years cleaning it
c) the Smalltalk kernel below
The idea is to port only part b) and the Styled Text Editor. And it has to be
done automatically by a tool which creates packages for Squeak and Pharo,
always from the latest code base. In addition you will probably need small Cuis
portability packages done manually, one for Squeak and one for Pharo.
Being able to always load the latest code base of Styled Text Editor and Cuis
Morphic as an external package in Pharo is a prerequisite to look into
possibilities of sharing more of the code.
I plan to write a more detailed proposal and then to approach ESUG and ask for
support for the funding. Any ideas for other sources of funding are highly
welcome and could speed things up considerably, of course! ;-)
I for one have not given up on the idea that it might be possible to develop
substantial components as you called it – thank you for that as well – in a
more Squeak-dialect-independent way. ;-)
Finally, I would like to take the opportunity and kindly ask everyone who has
not done so yet: Please check out Cuis 4.0 and the Styled Text Editor and give
us feedback, even if it does not (yet) run on your favourite Squeak dialect!
Thank you!
Peace,
Bernhard
P.S. Thanks to Göran and Janko for trying to establish different threads for
the rather off-topic discussions that my announcement posting has caused.
Am 23.04.2012 um 16:04 schrieb Göran Krampe:
Hi!
On 04/23/2012 03:40 PM, Stéphane Ducasse wrote:
Just cloning it off into Pharo and forking seems... less optimal. Any ideas or
thoughts?
I do not get what you mean. I just want to work on our roadmap and make it
getting real.
It is hard enough to get some momentum and to deliver for real.
So can you help us to get focused?
People can do what they want. I wrote a vision document. We have a roadmap
and we will do it.
Ok, let me clarify. I was just wondering how the Pharo community wants to
handle a case where a substantial component (in this case, this new editor) is
not *primarily* developed in Pharo (in this case Cuis).
The simple route is to just copy and fork. But IMHO this doesn't leverage the
team already around this editor, right? We (Pharo) can't just go around and
forking everything and maintaining everything for ourselves, right?
I just got interested in that problem - now, later replies indicated that it
would still need a substantial rewrite for Pharo, so perhaps the situation I am
describing is not really applicable in this case.
regards, Göran
