On 06-04-16 19:31, Sean P. DeNigris wrote:
[rant]I find the whole text system very confusing. What the heck does
a paragraph know about insertion points?? A view has one paragraph
object, even if there are several paragraphs (as understood by the
rest of humanity as a block of text with breaks
2016-04-06 19:31 GMT+02:00 Nicolai Hess :
> (As it is based on TxText (or a fork) maybe it isn't that difficult to add
> rendering on athens ?)
It should be not difficult. In Twisty end rendering on canvas is just 1% of
code (or less).
I plan to adopt it for Bloc. And for
).
text
Best regards,
Henrik
From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Nicolai
Hess
Sent: Wednesday, April 6, 2016 8:23 PM
To: Pharo Development List <pharo-dev@lists.pharo.org>
Subject: Re: [Pharo-dev] TxText model
2016-04-06 18:11 GMT+02:00 p...@highoct
2016-04-06 18:11 GMT+02:00 p...@highoctane.be :
> Ok. Call me stupid but in Pharo I don't see how to do that easily.
>
> Phil
>
At least for Rubric, it can not be that difficult. I saw a GT-Inspector
with a XML-styer
>
> On Wed, Apr 6, 2016 at 5:41 PM, Stephan Eggermont
I have two or three Moleskine books full of notes about all of this text
stuff.
Still a maddening thing to deal with.
Especially when you send wrong things and the whole UI freezes all over.
Phil
On Wed, Apr 6, 2016 at 7:31 PM, Sean P. DeNigris
wrote:
>
> > What are the
> What are the main problems with Text, Paragraph, ... and other old
> TextComponents?
> And how are these solved with TxText?
> Stephan Eggermont wrote
>> |t1 t2 ball page|
>> page := Morph new.
>> ...
Yes, this example brackets the situation quite nicely. The current text
system "makes hard
On 6 April 2016 at 20:31, Nicolai Hess wrote:
>
>
> 2016-04-06 18:00 GMT+02:00 Igor Stasenko :
>
>>
>>
>> On 6 April 2016 at 18:34, Nicolai Hess wrote:
>>
>>>
>>> Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko"
2016-04-06 18:00 GMT+02:00 Igor Stasenko :
>
>
> On 6 April 2016 at 18:34, Nicolai Hess wrote:
>
>>
>> Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" :
>> >
>> > btw,
>> >
>> > if you wanna feel a difference, why we wanted vector
Ok. Call me stupid but in Pharo I don't see how to do that easily.
Phil
On Wed, Apr 6, 2016 at 5:41 PM, Stephan Eggermont wrote:
> On 06-04-16 11:13, p...@highoctane.be wrote:
>
>> Another pain is the styling of text where the only styler we have is the
>> SHSt80Styler (class
On 6 April 2016 at 18:34, Nicolai Hess wrote:
>
> Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" :
> >
> > btw,
> >
> > if you wanna feel a difference, why we wanted vector based rendering, by
> yourself, open:
> >
> > Morph comment asText asMorph
On 06-04-16 11:13, p...@highoctane.be wrote:
Another pain is the styling of text where the only styler we have is
the SHSt80Styler (class name out of my mind, need to check) and that's
a huge pain to support other stylings.
Styling with different stylers worked in TextMorph. In Squeak it is
Nice! I addd this as #example method to TxAthensLayoutView.
Gesendet: Mittwoch, 06. April 2016 um 17:20 Uhr
Von: "Igor Stasenko" <siguc...@gmail.com>
An: "Pharo Development List" <pharo-dev@lists.pharo.org>
Betreff: Re: [Pharo-dev] TxText model
btw,
if you
Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" :
>
> btw,
>
> if you wanna feel a difference, why we wanted vector based rendering, by
yourself, open:
>
> Morph comment asText asMorph openInSceneView
>
> and then
>
> | sceneView view |
> sceneView := AthensSceneView new.
>
btw,
if you wanna feel a difference, why we wanted vector based rendering, by
yourself, open:
Morph comment asText asMorph openInSceneView
and then
| sceneView view |
sceneView := AthensSceneView new.
view := TxAthensLayoutView on: Morph comment asTxModel extent: 400@400.
sceneView scene:
On 6 April 2016 at 17:07, Nicolai Hess wrote:
>
>
> 2016-04-06 10:56 GMT+02:00 Igor Stasenko :
>
>>
>>
>> On 6 April 2016 at 11:36, Nicolai Hess wrote:
>>
>>>
>>>
>>> Thanks Igor.
>>> Maybe some more Info? (I don't have much
2016-04-06 10:56 GMT+02:00 Igor Stasenko :
>
>
> On 6 April 2016 at 11:36, Nicolai Hess wrote:
>
>>
>>
>> Thanks Igor.
>> Maybe some more Info? (I don't have much experience with this and don't
>> fully understand what is missing).
>>
>>
>>> 1. No
Nice!
2016-04-06 12:18 GMT+02:00 Stephan Eggermont :
> On 06-04-16 10:36, Nicolai Hess wrote:
>
>> In what use cases is this a problem ? (Paragraph and DisplayScanner have
>> good support for justified text (left / right / center), indentation
>> wrapping and (I don't know if
On 06-04-16 10:36, Nicolai Hess wrote:
In what use cases is this a problem ? (Paragraph and DisplayScanner
have good support for justified text (left / right / center),
indentation wrapping and (I don't know if this works in pharo anymore
but squeak had) even filling text in arbitary shaped
On Wed, Apr 6, 2016 at 11:02 AM, Igor Stasenko wrote:
>
>
> On 6 April 2016 at 11:56, Denis Kudriashov wrote:
>
>> Hi
>>
>> 2016-04-06 9:07 GMT+02:00 Nicolai Hess :
>>
>>> What are the main problems with Text, Paragraph, ... and
2016-04-06 10:56 GMT+02:00 Denis Kudriashov :
> Hi
>
> 2016-04-06 9:07 GMT+02:00 Nicolai Hess :
>
>> What are the main problems with Text, Paragraph, ... and other old
>> TextComponents?
>
>
> I don't want to write crappy words. But to understand what
On 6 April 2016 at 11:56, Denis Kudriashov wrote:
> Hi
>
> 2016-04-06 9:07 GMT+02:00 Nicolai Hess :
>
>> What are the main problems with Text, Paragraph, ... and other old
>> TextComponents?
>
>
> I don't want to write crappy words. But to understand
Hi
2016-04-06 9:07 GMT+02:00 Nicolai Hess :
> What are the main problems with Text, Paragraph, ... and other old
> TextComponents?
I don't want to write crappy words. But to understand what was wrong you
can try with them:
- remove blinking cursor for specific morph
On 6 April 2016 at 11:36, Nicolai Hess wrote:
>
>
> Thanks Igor.
> Maybe some more Info? (I don't have much experience with this and don't
> fully understand what is missing).
>
>
>> 1. No support for vector graphics
>>
>
> I know some parts of Athens (with Cairo font
On 6 April 2016 at 11:36, Nicolai Hess wrote:
>
>
> 2016-04-06 9:59 GMT+02:00 Igor Stasenko :
>
>>
>>
>> On 6 April 2016 at 10:07, Nicolai Hess wrote:
>>
>>>
>>>
>>> 2016-04-06 7:57 GMT+02:00 p...@highoctane.be
2016-04-06 9:59 GMT+02:00 Igor Stasenko :
>
>
> On 6 April 2016 at 10:07, Nicolai Hess wrote:
>
>>
>>
>> 2016-04-06 7:57 GMT+02:00 p...@highoctane.be :
>>
>>>
>>>
>>> On Wed, Apr 6, 2016 at 2:07 AM, Sean P. DeNigris
On 6 April 2016 at 10:07, Nicolai Hess wrote:
>
>
> 2016-04-06 7:57 GMT+02:00 p...@highoctane.be :
>
>>
>>
>> On Wed, Apr 6, 2016 at 2:07 AM, Sean P. DeNigris
>> wrote:
>>
>>> philippe.b...@highoctane.be wrote
>>> > So, I ended
2016-04-06 7:57 GMT+02:00 p...@highoctane.be :
>
>
> On Wed, Apr 6, 2016 at 2:07 AM, Sean P. DeNigris
> wrote:
>
>> philippe.b...@highoctane.be wrote
>> > So, I ended up in ParagraphEditor, Text attributes etc.
>>
>> Ugh. How many beautiful projects
On Wed, Apr 6, 2016 at 2:07 AM, Sean P. DeNigris
wrote:
> philippe.b...@highoctane.be wrote
> > So, I ended up in ParagraphEditor, Text attributes etc.
>
> Ugh. How many beautiful projects have died because of Paragraph and
> associated editors?!
A damn lot, I can tell
philippe.b...@highoctane.be wrote
> So, I ended up in ParagraphEditor, Text attributes etc.
Ugh. How many beautiful projects have died because of Paragraph and
associated editors?! This is where my vim keybindings experiment came
screeching to a halt.
-
Cheers,
Sean
--
View this message in
On 5 April 2016 at 04:16, Ben Coman wrote:
> On Mon, Apr 4, 2016 at 9:49 PM, Igor Stasenko wrote:
> >
> >
> > On 4 April 2016 at 16:32, Thierry Goubier
> wrote:
> >>
> >>
> >>
> >> 2016-04-04 15:23 GMT+02:00 Igor Stasenko
On Mon, Apr 4, 2016 at 9:49 PM, Igor Stasenko wrote:
>
>
> On 4 April 2016 at 16:32, Thierry Goubier wrote:
>>
>>
>>
>> 2016-04-04 15:23 GMT+02:00 Igor Stasenko :
>>>
>>>
>>> Analogies don't work. Right :) I never used
Le 04/04/2016 22:02, Damien Pollet a écrit :
On 4 April 2016 at 17:21, Thierry Goubier > wrote:
Did you had a look at the Doc code (of Design Pattern fame)? It has
allways been freely available.
no, what is it? do you have
Le 04/04/2016 22:02, Damien Pollet a écrit :
On 4 April 2016 at 17:21, Thierry Goubier > wrote:
Did you had a look at the Doc code (of Design Pattern fame)? It has
allways been freely available.
no, what is it? do you have
On 4 April 2016 at 17:21, Thierry Goubier wrote:
> Did you had a look at the Doc code (of Design Pattern fame)? It has
> allways been freely available.
no, what is it? do you have a link?
--
Damien Pollet
type less, do more [ | ]
On 04-04-16 16:47, Thierry Goubier wrote:
A short look through the layout part of it and I saw it has support
for arbitrary object spans. It also supposes a certain API from it's
model (interacting back to indicate where lines should be ended). A
text is a list of spans, isn't it? And spans
2016-04-04 17:16 GMT+02:00 Igor Stasenko :
> Glad to hear that you did not thrown away your project.
If you skip my announcement it here
http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2015-November/116027.html.
And look at videos.
2016-04-04 17:07 GMT+02:00 Igor Stasenko :
>
>
>> For now, external objects can't extend below the baseline.
>>
>
> Slightly not like that. An external object are bound to concrete position
> in text. And layout of a single line are computed based on dimensions of
> that
2016-04-04 17:10 GMT+02:00 Stephan Eggermont :
> On 04-04-16 16:49, Thierry Goubier wrote:
>
>> Framemaker-like or web-page like? Thierry
>>
> Framemaker.
Really challenging. Did you had a look at the Doc code (of Design Pattern
fame)? It has allways been freely available.
On 4 April 2016 at 17:47, Denis Kudriashov wrote:
>
> 2016-04-04 16:11 GMT+02:00 Thierry Goubier :
>
>> It is. Five packages, 1609 + 2647 lines of code (excluding tests and
>> styler).
>>
>> I think Denis has worked on it (and extended it).
>>
>
>
On Apr 4, 2016 4:24 PM, "Sven Van Caekenberghe" wrote:
>
>
> > On 04 Apr 2016, at 16:02, philippe.b...@highoctane.be <
philippe.b...@gmail.com> wrote:
> >
> > Is TxText part of the image?
>
> Try (in 5.0):
>
> TxViewContainer exampleOneLineEditor.
>
> TxViewContainer editText:
On 4 April 2016 at 17:47, Thierry Goubier wrote:
>
>
> 2016-04-04 16:14 GMT+02:00 Igor Stasenko :
>
>>
>>
>> On 4 April 2016 at 17:03, Thierry Goubier
>> wrote:
>>
>>>
>>>
>>> 2016-04-04 15:49 GMT+02:00 Igor Stasenko
2016-04-04 16:51 GMT+02:00 Thierry Goubier :
> Twisty renders only on Athens too?
Only Morphic now. It should not be hard to support Athens, TxText can be
used as example.
Twisty is on Smalltalkhub, right?
Yes
2016-04-04 16:11 GMT+02:00 Thierry Goubier :
> It is. Five packages, 1609 + 2647 lines of code (excluding tests and
> styler).
>
> I think Denis has worked on it (and extended it).
>
History was that:
At some point I realised that I can't use old TextMorph anymore. For
2016-04-04 16:04 GMT+02:00 Stephan Eggermont :
> On 04-04-16 15:49, Thierry Goubier wrote:
>
>> Are you thinking of writing a text typesetting engine in Pharo?
>>
>
> Would I like to? Sure. Don't know how to finance that, though.
Framemaker-like or web-page like?
Thierry
>
2016-04-04 16:14 GMT+02:00 Igor Stasenko :
>
>
> On 4 April 2016 at 17:03, Thierry Goubier
> wrote:
>
>>
>>
>> 2016-04-04 15:49 GMT+02:00 Igor Stasenko :
>>
>>>
>>>
>>> On 4 April 2016 at 16:32, Thierry Goubier
2016-04-04 16:47 GMT+02:00 Denis Kudriashov :
>
> 2016-04-04 16:11 GMT+02:00 Thierry Goubier :
>
>> It is. Five packages, 1609 + 2647 lines of code (excluding tests and
>> styler).
>>
>> I think Denis has worked on it (and extended it).
>>
>
>
> On 04 Apr 2016, at 16:02, philippe.b...@highoctane.be
> wrote:
>
> Is TxText part of the image?
Try (in 5.0):
TxViewContainer exampleOneLineEditor.
TxViewContainer editText: 'Philippe Back'.
Sven
On 04-04-16 15:49, Thierry Goubier wrote:
Are you thinking of writing a text typesetting engine in Pharo?
Would I like to? Sure. Don't know how to finance that, though.
Stephan
On 4 April 2016 at 17:03, Thierry Goubier wrote:
>
>
> 2016-04-04 15:49 GMT+02:00 Igor Stasenko :
>
>>
>>
>> On 4 April 2016 at 16:32, Thierry Goubier
>> wrote:
>>
>>>
>>>
>>> 2016-04-04 15:23 GMT+02:00 Igor Stasenko
On 04-04-16 13:18, Stephan Eggermont wrote:
On 04-04-16 11:58, Igor Stasenko wrote:
Apart from being 'cool to have', full-fledged word processing is not
a thing, that you dealing with on a daily basis in environment, like
Pharo.
I'm sure that is the case for you. I wonder if that is the case
2016-04-04 16:02 GMT+02:00 philippe.b...@highoctane.be <
philippe.b...@gmail.com>:
>
> On Apr 4, 2016 3:54 PM, "Igor Stasenko" wrote:
> >
> >
> >
> > On 4 April 2016 at 16:41, Stephan Eggermont wrote:
> >>
> >> On 04-04-16 14:49, Igor Stasenko wrote:
> >>>
On 4 April 2016 at 16:49, Igor Stasenko wrote:
>
>
> On 4 April 2016 at 16:32, Thierry Goubier
> wrote:
>
>>
>>
>> 2016-04-04 15:23 GMT+02:00 Igor Stasenko :
>>
>>>
>>>
Analogies don't work. Right :) I never used Pillar and
2016-04-04 15:49 GMT+02:00 Igor Stasenko :
>
>
> On 4 April 2016 at 16:32, Thierry Goubier
> wrote:
>
>>
>>
>> 2016-04-04 15:23 GMT+02:00 Igor Stasenko :
>>
>>>
>>>
Analogies don't work. Right :) I never used Pillar and have
On Apr 4, 2016 3:54 PM, "Igor Stasenko" wrote:
>
>
>
> On 4 April 2016 at 16:41, Stephan Eggermont wrote:
>>
>> On 04-04-16 14:49, Igor Stasenko wrote:
>>>
>>> Oh, and aside all of that.. Making a full-fledged word processor is not
>>> just a regular
On 4 April 2016 at 16:41, Stephan Eggermont wrote:
> On 04-04-16 14:49, Igor Stasenko wrote:
>
>> Oh, and aside all of that.. Making a full-fledged word processor is not
>> just a regular engineering task. You need an expert of publishing, expert
>> in fonts and typography.
2016-04-04 15:41 GMT+02:00 Stephan Eggermont :
>
> I know enough about typesetting and producing technical documentation.
Are you thinking of writing a text typesetting engine in Pharo?
Thierry
On 4 April 2016 at 16:32, Thierry Goubier wrote:
>
>
> 2016-04-04 15:23 GMT+02:00 Igor Stasenko :
>
>>
>>
>>> Analogies don't work. Right :) I never used Pillar and have remote ideas
>> about what it does or requires. From that perspective you
On 04-04-16 14:49, Igor Stasenko wrote:
Oh, and aside all of that.. Making a full-fledged word processor is not
just a regular engineering task. You need an expert of publishing, expert
in fonts and typography. That's right from the beginning.
And i am not that expert in this domain(s).
So, next
On 4 April 2016 at 16:31, Stephan Eggermont wrote:
> On 04-04-16 14:14, Igor Stasenko wrote:
>
>> If you have doubts about model, feel free to point it out and we can
>> discuss details.
>>
>
> As a text storage model it works pretty well. My major concerns are with
> the
2016-04-04 15:23 GMT+02:00 Igor Stasenko :
>
>
>> Analogies don't work. Right :) I never used Pillar and have remote ideas
> about what it does or requires. From that perspective you appeal to wrong
> person. On your place i would be asking a guy who knows Pillar innards
>
On 04-04-16 14:14, Igor Stasenko wrote:
If you have doubts about model, feel free to point it out and we can
discuss details.
As a text storage model it works pretty well. My major concerns are with
the line-breaking.
Stephan
On 4 April 2016 at 16:14, philippe.b...@highoctane.be <
philippe.b...@gmail.com> wrote:
>
> >
>
> Is there a doc explaining TxText somewhere?
>
> One of first things I wanted to do in Pharo (was 1.2 or 1.3 at the time)
> was to have text with clickable links, pictures etc.
> And not in a web
On 4 April 2016 at 16:14, Thierry Goubier wrote:
>
>
> 2016-04-04 15:02 GMT+02:00 Igor Stasenko :
>
>>
>>
>> On 4 April 2016 at 15:44, Thierry Goubier
>> wrote:
>>
>>>
>>>
>>> 2016-04-04 14:24 GMT+02:00 Igor Stasenko
2016-04-04 15:10 GMT+02:00 Igor Stasenko :
>
>
> On 4 April 2016 at 15:44, Thierry Goubier
> wrote:
>>
>>
>> Have you really looked into what is the core of the TeX algorithm? The
>> fact that an interactive version of it was done multiple times in
On Apr 4, 2016 3:03 PM, "Igor Stasenko" wrote:
>
>
>
> On 4 April 2016 at 15:44, Thierry Goubier
wrote:
>>
>>
>>
>> 2016-04-04 14:24 GMT+02:00 Igor Stasenko :
>>>
>>>
>>>
>>> On 4 April 2016 at 14:28, Thierry Goubier
2016-04-04 15:02 GMT+02:00 Igor Stasenko :
>
>
> On 4 April 2016 at 15:44, Thierry Goubier
> wrote:
>
>>
>>
>> 2016-04-04 14:24 GMT+02:00 Igor Stasenko :
>>
>>>
>>>
>>> On 4 April 2016 at 14:28, Thierry Goubier
On 4 April 2016 at 15:44, Thierry Goubier wrote:
>
>
> Have you really looked into what is the core of the TeX algorithm? The
> fact that an interactive version of it was done multiple times in history?
> (Self / InterViews to cite the ones I know and have used)
>
>
On 4 April 2016 at 15:44, Thierry Goubier wrote:
>
>
> 2016-04-04 14:24 GMT+02:00 Igor Stasenko :
>
>>
>>
>> On 4 April 2016 at 14:28, Thierry Goubier
>> wrote:
>>
>>>
>>>
>>> 2016-04-04 13:18 GMT+02:00 Stephan Eggermont
2016-04-04 14:49 GMT+02:00 Igor Stasenko :
> Oh, and aside all of that.. Making a full-fledged word processor is not
> just a regular engineering task. You need an expert of publishing, expert
> in fonts and typography. That's right from the beginning.
>
That's why I said
Oh, and aside all of that.. Making a full-fledged word processor is not
just a regular engineering task. You need an expert of publishing, expert
in fonts and typography. That's right from the beginning.
And i am not that expert in this domain(s).
So, next time, when we start talking about things
2016-04-04 14:14 GMT+02:00 Igor Stasenko :
>
>
> On 4 April 2016 at 14:18, Stephan Eggermont wrote:
>
>> On 04-04-16 11:58, Igor Stasenko wrote:
>>
>>> Apart from being 'cool to have', full-fledged word processing is not a
>>> thing, that you dealing with on
2016-04-04 14:24 GMT+02:00 Igor Stasenko :
>
>
> On 4 April 2016 at 14:28, Thierry Goubier
> wrote:
>
>>
>>
>> 2016-04-04 13:18 GMT+02:00 Stephan Eggermont :
>>
>>> On 04-04-16 11:58, Igor Stasenko wrote:
>>>
Apart from being
On 4 April 2016 at 14:28, Thierry Goubier wrote:
>
>
> 2016-04-04 13:18 GMT+02:00 Stephan Eggermont :
>
>> On 04-04-16 11:58, Igor Stasenko wrote:
>>
>>> Apart from being 'cool to have', full-fledged word processing is not a
>>> thing, that you
On 4 April 2016 at 14:18, Stephan Eggermont wrote:
> On 04-04-16 11:58, Igor Stasenko wrote:
>
>> Apart from being 'cool to have', full-fledged word processing is not a
>> thing, that you dealing with on a daily basis in environment, like Pharo.
>>
> I'm sure that is the case
2016-04-04 13:18 GMT+02:00 Stephan Eggermont :
> On 04-04-16 11:58, Igor Stasenko wrote:
>
>> Apart from being 'cool to have', full-fledged word processing is not a
>> thing, that you dealing with on a daily basis in environment, like Pharo.
>>
> I'm sure that is the case for
On 04-04-16 11:58, Igor Stasenko wrote:
Apart from being 'cool to have', full-fledged word processing is not a
thing, that you dealing with on a daily basis in environment, like Pharo.
I'm sure that is the case for you. I wonder if that is the case for many
Pharo users.
AFAIK there are a lot
76 matches
Mail list logo