Hi,
We again got carried away and forgot to update the world about what is up in
our corner. Here is a summary:
--
Bloc & Brick
--
- Text editor stability has been significantly improved
- Improved support for selection in the text editor
- Support for typical editing keybindings (copy, cut,
Very impressive!! Hope Bloc and Brick move along to be included in pharo soon!!
Norbert
> Am 25.05.2018 um 13:30 schrieb Tudor Girba :
>
> Hi,
>
> We were a bit silent the last couple of months. Quite a bit happened in the
> meantime, so here is a summary (for more fine
Hi Tudor.
Very impressive progress.
I have one question about scrolling support. How it works or is it works
with elements which are based on infinite layout like mentioned grid
widget?
Does grid implemented with PannableElement too?
2018-05-25 14:30 GMT+03:00 Tudor Girba
Hi,
We were a bit silent the last couple of months. Quite a bit happened in the
meantime, so here is a summary (for more fine grained announcements, you can
follow us on Twitter):
Bloc
- Scrolling. We finally have a good scrolling support:
Hi,
Here is an update of the work on Bloc, Brick and GT. As always, please do let
us know what you think.
Bloc:
- Improved the deletion in the text editor and covered the scenarios with
examples
- Worked on the text selection. Still work needed for selection to be
production ready:
Hi,
Here is an update of the work on Bloc and GT. As always, please do let us know
what you think.
Bloc:
- Eventing saw a deep overhaul. They are now dispatched using the Announcements
engine. The previous mechanism is still in place in order to help people
compare the impact. In the process,
Hi,
Here is an update of the work on Bloc and GT:
Bloc:
- Bezier curves (cubic and quadratic).
https://twitter.com/feenkcom/status/93476564021504
https://twitter.com/feenkcom/status/934856909001252865
- Dragging is now possible through a BlDragHandler that can be attached to any
element.
A good trick to get the same is to have self inspect in the buttons or
widgets you are developing/using.
Stef
On Sun, Nov 12, 2017 at 6:42 PM, Todd Blanchard wrote:
> The most productive environment I have ever used was Hypercard and that was
> because you could cmd-opt
The most productive environment I have ever used was Hypercard and that was
because you could cmd-opt click on any button or field or UI element and the
script for that would open and you could edit it.
I have always wanted that in Smalltalk.
> On Nov 12, 2017, at 9:10 AM, Ben Coman
A feature I believe would be useful is to help a user to dig into the
application code behind a button (e.g. Hierarchy button). This would help
discoverability of the system. I learnt a lot using Halos>Debug but it's a
bit tedious deciphering from the instance variables what system application
2017-11-12 16:10 GMT+01:00 Tudor Girba :
>
> > On Nov 12, 2017, at 4:00 PM, Denis Kudriashov
> wrote:
> >
> > 2017-11-11 22:39 GMT+01:00 Tudor Girba :
> > Hi Denis,
> >
> > It is not a global function.
> >
> > It is a class-side
> On Nov 12, 2017, at 4:00 PM, Denis Kudriashov wrote:
>
> 2017-11-11 22:39 GMT+01:00 Tudor Girba :
> Hi Denis,
>
> It is not a global function.
>
> It is a class-side method because it relies on the following logic:
> - if the element is attached
2017-11-11 22:39 GMT+01:00 Tudor Girba :
> Hi Denis,
>
> It is not a global function.
>
> It is a class-side method because it relies on the following logic:
> - if the element is attached to a space, it uses that space to dispatch
> the event.
> - otherwise, it creates a
BTW doru
Class comments are important
Look at the comment of BlSpace. I did not know that it was limited to a window.
On Sat, Nov 11, 2017 at 10:39 PM, Tudor Girba wrote:
> Hi Denis,
>
> It is not a global function.
>
> It is a class-side method because it relies on the
Hi Denis,
It is not a global function.
It is a class-side method because it relies on the following logic:
- if the element is attached to a space, it uses that space to dispatch the
event.
- otherwise, it creates a temporary space and uses that one.
The use case for such simulators is needed
Nice explanation.
Aliaksei do you add it to the BLSpace class comment?
Stef
On Fri, Nov 10, 2017 at 10:36 PM, Aliaksei Syrel wrote:
> Hi Sean,
>
>> Why not `anElement simulateClick`?
>
>
> Good question :)
> We indeed evaluated a possibility to have (BlElement >>
Thanks Doru this is cool to see this happening.
Stef
On Fri, Nov 10, 2017 at 7:47 PM, Tudor Girba wrote:
> Hi,
>
> Over the past couple of weeks Alex worked on stabilizing a first beta01
> version for Pharo 6.1:
> https://twitter.com/feenkcom/status/929031849879461889
>
>
Hi Aliaksei
2017-11-10 22:36 GMT+01:00 Aliaksei Syrel :
> Hi Sean,
>
> Why not `anElement simulateClick`?
>
>
> Good question :)
> We indeed evaluated a possibility to have (BlElement >> #simulateClick)
> but then decided to make BlSpace class to be responsible for that.
>
On 10-11-17 22:36, Aliaksei Syrel wrote:
To wrap up, we decided that it should be a responsibility of the Space
_class_ to create a new temporary instance of itself, add an element to
it, simulate click event and then delete itself. In order to show the
intent and a process behind we decided
Hi Sean,
Why not `anElement simulateClick`?
Good question :)
We indeed evaluated a possibility to have (BlElement >> #simulateClick) but
then decided to make BlSpace class to be responsible for that.
First we should realise that when we simulate a click we do literally
simulate user's action
Tudor Girba-2 wrote
> - support for programatic testing of bloc mouse events:
> https://twitter.com/feenkcom/status/925672206763511808
Why not `anElement simulateClick`?
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Hi,
Over the past couple of weeks Alex worked on stabilizing a first beta01 version
for Pharo 6.1:
https://twitter.com/feenkcom/status/929031849879461889
This is available as a beta01 tag in the pharo61 branch here:
https://github.com/pharo-graphics/Bloc/tree/beta01
The main readme was updated
Hi,
The BlScalableElement is a utility element that zooms the elements inside.
Indeed, all elements can be transformed, but this is a low level ability. The
ScalableElement allows us to think in terms of elements, and strategies of
zooming.
The mouse wheel is an event issue that can be added
I think that testing more SDL and using it will help there.
On Fri, Oct 27, 2017 at 4:50 AM, Ben Coman wrote:
>
>
> On Thu, Oct 26, 2017 at 4:00 AM, Tudor Girba wrote:
>>
>> Hi,
>>
>> > On Oct 25, 2017, at 8:11 PM, Sean P. DeNigris
On Thu, Oct 26, 2017 at 4:00 AM, Tudor Girba wrote:
> Hi,
>
> > On Oct 25, 2017, at 8:11 PM, Sean P. DeNigris
> wrote:
> >
> > Denis Kudriashov wrote
> >> Good initiative.
> >
> > +1 :)
> >
> >
> > Denis Kudriashov wrote
> >> Here is my twitter
On Thu, Oct 26, 2017 at 2:15 PM, Clément Bera
wrote:
> Hi,
>
> Good work,
>
> In PolyMaths/SciSmalltalk vectors and matrix are already implemented
> efficiently. I would recommend to share the same implementation.
>
By this, you mean move the "base" vector/matrix objects
Hi Doru,
you say BLVector is implemented as having instance vars x,y instead of
using an Array (like polymath), i guess perhaps because of speed
considerations? but i wonder why you then dont use FloatArrays for
vectors, their precision, although generally bad, is sufficient for
graphics and they
Hi Clément,
I did not know that you had an interest in optimizing vector and matrix
operations. Awesome!
We definitely want to take a look at synergies. These low level things are
needed for Bloc, but they definitely do not have to be in Bloc.
Doru
> On Oct 26, 2017, at 8:15 AM, Clément
Hi,
Good work,
In PolyMaths/SciSmalltalk vectors and matrix are already implemented
efficiently. I would recommend to share the same implementation. In the
next few years, I think we will improve the performance of those
vectors/matrix library using the processor vector instructions, and it
Tudor Girba-2 wrote
> We now have BlScalableElement which handles the zooming
Gotcha. So an entire "World" (I'm assuming that's a Bloc Space?) can be
zoomed in and out?
-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
On Wed, Oct 25, 2017 at 7:04 PM, Aliaksei Syrel wrote:
> Hi Stef,
>
> In this email I will enumerate what features are missing that we are aware
> of. The problem is that we discover what we need spontaneously during
> experiments and not beforehand :)
Yes for the extras
Ok :)
Stef
On Wed, Oct 25, 2017 at 7:58 PM, Tudor Girba wrote:
> Hi Stef,
>
> The log is not a replacement of the roadmap. It is only to help people see
> what we do live.
>
> The roadmap and documentation are coming as well, but these are separate.
>
> Cheers,
> Doru
>
>
2017-10-25 22:00 GMT+02:00 Tudor Girba :
> Hi,
>
> > On Oct 25, 2017, at 8:11 PM, Sean P. DeNigris
> wrote:
> >
> > Denis Kudriashov wrote
> >> Good initiative.
> >
> > +1 :)
> >
> >
> > Denis Kudriashov wrote
> >> Here is my twitter questions:…
> >
>
Hi,
> On Oct 25, 2017, at 8:11 PM, Sean P. DeNigris wrote:
>
> Denis Kudriashov wrote
>> Good initiative.
>
> +1 :)
>
>
> Denis Kudriashov wrote
>> Here is my twitter questions:…
>
> Mine are:
> 1. Is it possible/easy/smooth to zoom in/out?
We now have
Denis Kudriashov wrote
> Good initiative.
+1 :)
Denis Kudriashov wrote
> Here is my twitter questions:…
Mine are:
1. Is it possible/easy/smooth to zoom in/out?
2. Is there an equivalent to Morphic-stepping?
-
Cheers,
Sean
--
Sent from:
Hi,
That is the point of making fine grained things explicit: to have the chance to
disagree and discuss :).
I will spawn a separate thread.
Doru
> On Oct 25, 2017, at 7:42 PM, Alexandre Bergel wrote:
>
>> Personally (10, 20) for a vector is not really nice and I
Hi Stef,
The log is not a replacement of the roadmap. It is only to help people see what
we do live.
The roadmap and documentation are coming as well, but these are separate.
Cheers,
Doru
> On Oct 25, 2017, at 6:45 PM, Stephane Ducasse wrote:
>
> Doru having a few
> Personally (10, 20) for a vector is not really nice and I would really
> like to have a discussion before.
+1
The Pharo syntax should remain an asset, not become a trap.
Alexandre
>
>
> On Wed, Oct 25, 2017 at 6:45 PM, Stephane Ducasse
> wrote:
>> Doru having
Hi Stef,
In this email I will enumerate what features are missing that we are aware
of. The problem is that we discover what we need spontaneously during
experiments and not beforehand :)
Missing / broken
- error handling library. If there is an exception during event handling
or rendering,
Hi Denis,
The reason for BlVector2D is that we also have BlVector*3*D.
In case of translation a Point (x@y) should be converted to (x,y,0). For
scale it is converted as (x,y,1). You see, the same Point object has
different meanings when it comes to different transformations.
Additionally, Point
Personally (10, 20) for a vector is not really nice and I would really
like to have a discussion before.
On Wed, Oct 25, 2017 at 6:45 PM, Stephane Ducasse
wrote:
> Doru having a few tweets is nice but I do not think that you
> communicate well around bloc.
>
> What I
Doru having a few tweets is nice but I do not think that you
communicate well around bloc.
What I would like to get is a roadmap for Bloc V1.0.
- Here are the missing features (documentation),
- Here are where we are.
Because else it feels like Bloc will never ends.
You will argue and tell me
Doru using comma for creating vectors is not really because it will
just make the life of type inferencers more difficult.
On Wed, Oct 25, 2017 at 5:53 PM, Tudor Girba wrote:
> Hi,
>
> Our team is working on a couple of projects that are relevant for the core of
> Pharo,
Hi.
Good initiative.
Here is my twitter questions:
- What the reason to introduce BlVector2D instead of using existing Point?
- How often this vector will be constructed by hands in user code? It is
related to my question about comma message: is it really needed?
Now you can evaluate (10*,* 20)
Hi,
Our team is working on a couple of projects that are relevant for the core of
Pharo, namely GT and Bloc/Brick. At ESUG we were asked by several people, and
Stef in particular, to make the progress on these projects more transparent. To
this end, we will start two streams of signals:
- fine
45 matches
Mail list logo