Is Sophie a candidate to replace the role of BookMorph within the Morphic environment?
I've not seen any contextual mention of Morphic when I've looked for info about Sophie, so is it meaningful to suggest that Sophie will fit in there? Or if it is meaningful, is there any analysis about the what, the when, the who and the how?
In the meantime the Morphic/EToys end of things needs to be kept tidy, as was the original point this topic title.
(The bug is not a thing I could easilty fix, so I have to ask.)
Yours
Bob -----------------------
John M McIntosh wrote: Well the Sophie team has beginning of summer delivery date. Likely we'll need to push things out for wider review at some point before then.
On 2-Apr-06, at 6:07 AM, Chris Patrick Schreiner wrote:
Marcus Denker wrote:
On 02.04.2006, at 14:03, stéphane ducasse wrote:
We need to clean BookMorph.... a lot :)
Uhmm... who needs BookMorph when there is Sophie? Marcus
So, *when* will there be Sophie?
ChrisP
--
Hi Robert,
My answer with Sophie was more meant as a reply to Stef's "we need to rewrite BookMorph", not your original Mail...
Is Sophie a candidate to replace the role of BookMorph within the Morphic environment?
No, Sophie replaces Morphic (it's build on top of Tweak, but afaic it re-implements all the widgets... which is supposed to be quite nice stuff..).
I've not seen any contextual mention of Morphic when I've looked for info about Sophie, so is it meaningful to suggest that Sophie will fit in there? Or if it is meaningful, is there any analysis about the what, the when, the who and the how?
In the meantime the Morphic/EToys end of things needs to be kept tidy, as was the original point this topic title.
I can't help it, but reading "tidy" in the context of Morphic... "semantic mismatch" ;-) Tidy it is not.
But you are right that, as long as Morphic is what we use, we should try to fix everything we can.
For 3.9, we have lookend into fixing bugs, and we improved performanc of Morphic a lot (> factor 1.6). Even the Sophie hackers are using Morphic for development, and making opening a browser faster by 0.5 seconds does add up over the years ;-)
(The bug is not a thing I could easilty fix, so I have to ask.)
This was about an old server entry? Should be simple to fix. Did you add a bug report to the bugtracker?
Marcus
On 3-Apr-06, at 12:26 PM, Marcus Denker wrote:
Hi Robert,
My answer with Sophie was more meant as a reply to Stef's "we need to rewrite BookMorph", not your original Mail...
Is Sophie a candidate to replace the role of BookMorph within the Morphic environment?
No, Sophie replaces Morphic (it's build on top of Tweak, but afaic it re-implements all the widgets... which is supposed to be quite nice stuff..).
Well Sophie is an electronic book authoring/reader system, it's to replace Powerpoint, Word and most of MS office. (Sorry no spreadsheets, but if someone wants to add that?).
Since it's built on top of Tweak & Squeak and completely open-source you can choose to add features as you wish.
-- ======================================================================== === John M. McIntosh johnmci@smalltalkconsulting.com 1-800-477-2659 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ======================================================================== ===
Hi All,
I saw a demo of Sophie at C5 and was well impressed. It just felt like document design/creation done right.
Cheers, Darius
Hi All,
I saw a demo of Sophie at C5 and was well impressed. It just felt like document design/creation done right.
Cheers, Darius
John M McIntosh wrote on Mon, 3 Apr 2006 16:49:40 -0700
Well Sophie is an electronic book authoring/reader system, it's to replace Powerpoint, Word and most of MS office. (Sorry no spreadsheets, but if someone wants to add that?).
Since it's built on top of Tweak & Squeak and completely open-source you can choose to add features as you wish.
While Excel has been fabulously successful, that is not the way I would go for a Tweak/Squeak/Sophie spreadsheet. Instead my first priority would be to have the best table layout possible since more people seem to use Excel for that than for actual calculations (not counting simple sorting of tables). And having several smaller tables floating around in a larger document seems nicer to me than a single huge 2D (almost 3D with tabbed "pages") array, though I can understand how such a structured space can make some people feel more secure (probably more veteran users than newbies).
For the second step it would be interesting to look at The Analyst for inspiration and allow arbitrary Smalltalk objects and expressions instead of just numbers and strings.
Third: I would separate the expressions from the actual cells in the style of Lotus Improv. This would encourage the users to think in terms of collections of data like in APL or FScript instead of individual numbers. It would also make doing things across more than one table less awkward. The user interface could still present things in terms of per cell equations when that is more convenient.
Lastly, having such a component I would use it in Sophie for things like timelines instead of hand coding stuff in Tweak.
-- Jecel
squeak-dev@lists.squeakfoundation.org