Hi Ronie, > On 18 Apr 2019, at 18:56, Ronie Salgado <[email protected]> wrote: > > That looks very cool > > For the text editor are you using GtkSourceView or something else?
For now, we are using a plain GtkTextView but we will switch to GtkSourceView later (just because it provides some functionality like adornments for breakpoints and that the I do not want to do myself, even if it would be possible). Esteban > > Greetings, > Ronie > > El jue., 18 abr. 2019 a las 7:23, Esteban Lorenzano (<[email protected] > <mailto:[email protected]>>) escribió: > > >> On 18 Apr 2019, at 13:08, PBKResearch <[email protected] >> <mailto:[email protected]>> wrote: >> >> +1 to Norbert. In particular, does it mean that, from Pharo 8, we will be >> *required* to install Gtk3 backend to use Pharo? > > For now is in early development so there is no easy way to install (since > there are things to replace/fix in current image). > We will provide an install script soon (or maybe a prepared image, while we > arrive to have a reliable baseline). > > And no, you will not need it. Gtk3 bindings are an extra. If you want to do a > desktop application (for example Schmidt is doing it), maybe you will want to > install it. Otherwise you will continue as before. > > And to be clear: Pharo 8 WILL NOT be a Gtk3 application. > Even if eventually the IDE will be able to run with it (since it will be a > Spec 2.0 based IDE), there are a lot of huge things that need to be migrated > before (and the GTInspector is not big: Calypso is). > And still then (maybe in Pharo 9), running with Gtk3 will be a choice. > > Esteban > >> >> Peter Kenny >> >> From: Pharo-users <[email protected] >> <mailto:[email protected]>> On Behalf Of Norbert Hartl >> Sent: 18 April 2019 11:58 >> To: Pharo users users <[email protected] >> <mailto:[email protected]>> >> Cc: Pharo Dev <[email protected] <mailto:[email protected]>> >> Subject: Re: [Pharo-users] [ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 >> bindings) >> >> Great! >> >> Can you explain what is there, what somebody can load and what to expect. >> And even more important: what not to expect? >> >> I don’t get any of the essential details from this mail. >> >> Norbert >> >> >> >>> Am 18.04.2019 um 12:08 schrieb Esteban Lorenzano <[email protected] >>> <mailto:[email protected]>>: >>> >>> People that assisted to Pharo Days 2019 (or that follow my twitter account) >>> already know this, but it needs to be formally announced: >>> >>> >>> We are working on Spec 2.0, and it will provide not just the classic >>> Morphic bindings but also a new option for developers: Gtk3 bindings! >>> >>> Why we want a Spec 2.0 with different backends? >>> >>> There are reasons that converged to decide us to make it: >>> >>> First, to provide a validated abstract Spec 2.0 that can be used with >>> different backends, preparing Pharo to be able to switch backends without >>> needing to recreate the full IDE from scratch each time (a problem we have >>> partially now in our way to deprecate Morphic). >>> Second, because we receive from different sources the requirement of having >>> the possibility of developing real native-looking desktop applications. >>> Yes, in moment where people talk about the cloud, SaaS and web-applications >>> as the "next big thing" (something that is been declared since years, by >>> the way), we believe is important to provide this, for two big reasons: >>> Because there is still an important place for desktop applications market >>> and most medium-size to big business still require them. >>> Because Pharo itself is a desktop application! (And we need to provide the >>> best experience possible on it). >>> >>> For us, this is a fundamental step to continue improving Pharo itself, and >>> it matches also the work we are doing on going real-headless: Pharo users >>> will be able to start the Morphic world, a Gtk application or the next >>> backend to come. >>> >>> Why Gtk3? >>> >>> There are some other important players in the "native widgets scene", so >>> why we choose Gtk3? >>> >>> Again, several reasons were taken into account: >>> >>> Gtk3 is cross platform. Yes, technically is just "native" in linux, but it >>> works on Windows and macOS too. >>> It is very mature and popular. >>> It is made in plain C. >>> >>> Next step: tool migration >>> >>> The only way to know if you have covered what is needed is actually taking >>> real-life use cases and implementing them. We have a list of tools that >>> needs to be migrated and we are starting from them: >>> >>> Old GT tools will be replaced by new Spec tools (while preserving its >>> power). >>> Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now). >>> Pharo launcher as a standalone application is a good example of what you >>> can do with the Gtk3 bindings. >>> >>> And that's it. Pharo 8.0 will come with Spec 2.0 and users will be able to >>> benefit of it immediately :) >>> >>> >>> A small screenshot of the new Inspector (WIP): >>> >>> <Screenshot 2019-04-18 at 12.07.16.png> >>> >>> Esteban >
