Re: [Pharo-dev] [ANN] Sparta v1.1

Hi Aliaksei. 2016-10-19 18:06 GMT+02:00 Aliaksei Syrel : > Hi > > I am happy to announce the release of Sparta v1.1 for Pharo 6. > https://github.com/syrel/Sparta/tree/v1.1 > What you think how difficult to move Morphic to Sparta canvas? In the way Athens support was added

Re: [Pharo-dev] [ANN] Sparta v1.1

Yes. At this point, there is no fallback implemented. Doru > On Oct 23, 2016, at 10:43 AM, stepharo wrote: > > Doru > > does it mean that right now with Sparta we do not have any fallback? > > Stef > > > Le 21/10/16 à 15:41, Tudor Girba a écrit : >> Hi Clement, >> >>

Re: [Pharo-dev] [ANN] Sparta v1.1

Doru does it mean that right now with Sparta we do not have any fallback? Stef Le 21/10/16 à 15:41, Tudor Girba a écrit : Hi Clement, Thanks for raising this question. In short, Sparta is inspired from Athens and it has a similar structure. So, there is an in-image interface of the

Re: [Pharo-dev] [ANN] Sparta v1.1

Pointer? Sent from the road > On Oct 22, 2016, at 11:39, stepharo wrote: > > This is what christophe is doing in cargo. > > Stef > > > >> Le 22/10/16 à 17:29, p...@highoctane.be a écrit : >> Looks like we are on the same wavelength but... >> >> Look how this is done in

Re: [Pharo-dev] [ANN] Sparta v1.1

This is what christophe is doing in cargo. Stef Le 22/10/16 à 17:29, p...@highoctane.be a écrit : Looks like we are on the same wavelength but... Look how this is done in PHP with Composer: - simple Json file - declares repositories - requires and requiresdev - uses semver versions so,

Re: [Pharo-dev] [ANN] Sparta v1.1

Hi aliaksei I thought that you were just changing the internal representation of txText to use Ropes and building on top of / improving txText I did not think that you were throwing away all the work igor did. Because he spent a lot of time designing the text model and making it is

Re: [Pharo-dev] [ANN] Sparta v1.1

I wholeheartedly agree that Smalltalk is not desirable as a specification language ... I included the Smalltalk expression as an example of the type of information I am using in tODE (when I make another pass through tODE I will switch from smalltalk to STON) ... So moving forward I think a

Re: [Pharo-dev] [ANN] Sparta v1.1

Superb Phil. PS: For the record: we are working on - bootstrap core and we are making progress - Git support - package manager and distribution building Now we cannot go faster. This is not every year that we change the complete representation of objects.

Re: [Pharo-dev] [ANN] Sparta v1.1

Much appreciated! On 10/22/16 8:30 AM, p...@highoctane.be wrote: Ok, message received. PRs launching. On Sat, Oct 22, 2016 at 3:23 PM, Dale Henrichs > wrote: On 10/22/16 12:08 AM, p...@highoctane.be

Re: [Pharo-dev] [ANN] Sparta v1.1

Ok, message received. PRs launching. On Sat, Oct 22, 2016 at 3:23 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > > > On 10/22/16 12:08 AM, p...@highoctane.be wrote: > >> Dale, >> >> I looked at the docs but it was kind of a hunt as they were a bit kind of >> everywhere.\ >> >> *

Re: [Pharo-dev] [ANN] Sparta v1.1

Looks like we are on the same wavelength but... Look how this is done in PHP with Composer: - simple Json file - declares repositories - requires and requiresdev - uses semver versions so, 'composer install' will fetch and install deps. composer update will update deps. composer.json {

Re: [Pharo-dev] [ANN] Sparta v1.1

On 10/22/16 7:01 AM, Dimitris Chloupis wrote: I really like STON , even more than I like JSON. Very readable and easy to edit format. Very good idea, I would probably something similar but less more elegant. This is why I'm threatening to create MetacelloProjectLoadSpec ... not to be elegant

Re: [Pharo-dev] [ANN] Sparta v1.1

I really like STON , even more than I like JSON. Very readable and easy to edit format. Very good idea, I would probably something similar but less more elegant. You probably know this, but if you host the ston configurations files as you do in that link , Github gives you the ability to directly

Re: [Pharo-dev] [ANN] Sparta v1.1

On 10/22/16 12:52 AM, Dimitris Chloupis wrote: Actually we dont, I am using the terminal to get and build my own images. Curl + use of startup scripts are more than enough. Simply , easy and straightforward. Pharo offers a super easy way to export any method as a command line argument. So

Re: [Pharo-dev] [ANN] Sparta v1.1

On 10/22/16 12:08 AM, p...@highoctane.be wrote: Dale, I looked at the docs but it was kind of a hunt as they were a bit kind of everywhere.\ * Book chapters (Pharo). This including preversions with more info than the published one * Google code wiki pages * Github * Other but can't even

Re: [Pharo-dev] [ANN] Sparta v1.1

On 10/22/16 12:04 AM, p...@highoctane.be wrote: We need some easy to use gem-style installer on the command line. Phil, Since I am not really familiar with ruby, I'm not sure what you mean by "gem-style installer on the command line"? Depending upon what you mean, I think I agree:) For

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-22 11:55 GMT+02:00 Aliaksei Syrel : > MozServices crash is intentional! > When you load Sparta using metacello it runs installer scripts and > automatically starts services. But they are already running if you have > Sparta installed. > > I need to find a pretty

Re: [Pharo-dev] [ANN] Sparta v1.1

Dale, > Am 21.10.2016 um 22:15 schrieb Dale Henrichs > : > > > > On 10/21/2016 07:30 AM, Norbert Hartl wrote: >> Dale, >> >>> Am 21.10.2016 um 16:12 schrieb Dale Henrichs >>> >> >:

Re: [Pharo-dev] [ANN] Sparta v1.1

As Doru already mentioned text editor is an important part of the tools. There are some requirements a text editor should fulfil. 1. Support of large files ( >> 100mb) 2. Support of large pieces of text located in memory 3. Allow developers to embed visual elements (pictures,

Re: [Pharo-dev] [ANN] Sparta v1.1

I use plugin for months and never had a single random crash :) It is very stable On Oct 22, 2016 11:55 AM, "Aliaksei Syrel" wrote: > MozServices crash is intentional! > When you load Sparta using metacello it runs installer scripts and > automatically starts services. But

Re: [Pharo-dev] [ANN] Sparta v1.1

MozServices crash is intentional! When you load Sparta using metacello it runs installer scripts and automatically starts services. But they are already running if you have Sparta installed. I need to find a pretty solution for it. Actually it is complicated. Services can not just stop while

Re: [Pharo-dev] [ANN] Sparta v1.1

Yeah it takes long because of pharo compilation, this is not different than python and ruby. Though python has pyc files which are compiled py files , unfortunately we dont have something similar out of the box. This is where the monolithic nature of the image file bite us back. I dont know if

Re: [Pharo-dev] [ANN] Sparta v1.1

I am having my (local) Jenkins CI do that for me. There are several projects: 1/ P1: download fresh pharo 2/ P2: build "base worker" (an image with all prerequisites to dev) (takes a while: Seaside, Magritte, ) 3/ P3: take recent commits from Git project and build an image based on the base

Re: [Pharo-dev] [ANN] Sparta v1.1

Hi Kilon, 2016-10-22 9:52 GMT+02:00 Dimitris Chloupis : > Actually we dont, I am using the terminal to get and build my own images. > Curl + use of startup scripts are more than enough. Simply , easy and > straightforward. Pharo offers a super easy way to export any method

Re: [Pharo-dev] [ANN] Sparta v1.1

Actually we dont, I am using the terminal to get and build my own images. Curl + use of startup scripts are more than enough. Simply , easy and straightforward. Pharo offers a super easy way to export any method as a command line argument. So there is literally no excuse. Pharo already offers a

Re: [Pharo-dev] [ANN] Sparta v1.1

Dale, I looked at the docs but it was kind of a hunt as they were a bit kind of everywhere.\ * Book chapters (Pharo). This including preversions with more info than the published one * Google code wiki pages * Github * Other but can't even remember Is there an official place for all things

Re: [Pharo-dev] [ANN] Sparta v1.1

We need some easy to use gem-style installer on the command line. Pharo is perfectly usable for any kind of project provided energy is poured in. Things are in flux, yes, and it is frustrating not to have it all perfect. So what? If we weren't interested in wild things why would we be here after

Re: [Pharo-dev] [ANN] Sparta v1.1

Right, but since there are known bugs in Sierra perhaps MozServices is hitting one of them. In our case we hit a bug in poll() which is a bit surprising and apparently the bug is hitting Apple's own curl implementation -- see discussion here[1]... Dale [1]

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-21 16:20 GMT+02:00 Denis Kudriashov : > 2016-10-21 16:15 GMT+02:00 Tudor Girba : > >> > I would kindly ask for patience. What is perhaps less clear is that >> this editor is in the critical path of the GT project and we are committed >> to

Re: [Pharo-dev] [ANN] Sparta v1.1

Hi Dale 2016-10-22 1:20 GMT+02:00 Dale Henrichs : > Denis, > > Sierra seems to have some issues. A couple weeks ago one of our users ran > into a problem with Pharo3.0 and Sierra > Pharo works fine. When I first time load Sparta everything works well. I am not

Re: [Pharo-dev] [ANN] Sparta v1.1

Denis, Sierra seems to have some issues. A couple weeks ago one of our users ran into a problem with Pharo3.0 and Sierra --- Esteban jumped on that pretty quickly, but then we discovered some additional issues with GemStone and Sierra -- in our case it was a known bug in Sierra and we are

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-19 18:06 GMT+02:00 Aliaksei Syrel : > > It can be bootstrapped with the following script: > > Metacello new > baseline: 'Sparta'; > repository: 'github://syrel/sparta:v1.1/src'; > load: #file:core > > Strange crash detected. I just execute twice this script and

Re: [Pharo-dev] [ANN] Sparta v1.1

On 10/21/2016 07:30 AM, Norbert Hartl wrote: Dale, Am 21.10.2016 um 16:12 schrieb Dale Henrichs >: Norbert, I didn't realize that you were claiming that the new text model for Sparta was (potentially) inferior.

Re: [Pharo-dev] [ANN] Sparta v1.1

Actually you are wrong, its not hard to use C libraries from Pharo. UFFI is not a restart, its a continuation of Nativeboost , they are very similar. Pharo FFI, whether its the old FFI, Alien, Nativeboost or UFFI, is more or less the same. In the end an FFI is defined by C syntax , Pharo UFFI

Re: [Pharo-dev] [ANN] Sparta v1.1

> On Oct 21, 2016, at 07:30, Norbert Hartl wrote: > > The current (!) complaint is rather based on the fact that everything > regarding the graphics backend, widget and tools appears sometimes as an > indefinite loop of reinventing stuff and improving and never get the job

Re: [Pharo-dev] [ANN] Sparta v1.1

> On 21 Oct 2016, at 17:19, Esteban Lorenzano wrote: > >> >> On 21 Oct 2016, at 16:43, Sean P. DeNigris wrote: >> >> Tudor Girba-2 wrote >>> I would kindly ask for patience. What is perhaps less clear is that this >>> editor is in the critical path

Re: [Pharo-dev] [ANN] Sparta v1.1

> On 21 Oct 2016, at 16:43, Sean P. DeNigris wrote: > > Tudor Girba-2 wrote >> I would kindly ask for patience. What is perhaps less clear is that this >> editor is in the critical path of the GT project and we are committed to >> deliver an editor that actually works. We

Re: [Pharo-dev] [ANN] Sparta v1.1

Tudor Girba-2 wrote > I would kindly ask for patience. What is perhaps less clear is that this > editor is in the critical path of the GT project and we are committed to > deliver an editor that actually works. We are still investigating > different paths, both on the low level (like with Rope)

Re: [Pharo-dev] [ANN] Sparta v1.1

> On 21 Oct 2016, at 16:30, Norbert Hartl wrote: > > Dale, > >> Am 21.10.2016 um 16:12 schrieb Dale Henrichs >> >: >> >> Norbert, >> >> I didn't realize that you were claiming that the new text

Re: [Pharo-dev] [ANN] Sparta v1.1

On Fri, Oct 21, 2016 at 3:41 PM, Tudor Girba wrote: > Hi Clement, > > Thanks for raising this question. > > In short, Sparta is inspired from Athens and it has a similar structure. > So, there is an in-image interface of the canvas, and there is a concrete > implementation

Re: [Pharo-dev] [ANN] Sparta v1.1

Dale, > Am 21.10.2016 um 16:12 schrieb Dale Henrichs > : > > Norbert, > > I didn't realize that you were claiming that the new text model for Sparta > was (potentially) inferior. > The other day you were expressing sadness about having to use the newer >

Re: [Pharo-dev] [ANN] Sparta v1.1

I think that the concept of a LTS will become useful at one point. Like, every 3 versions or so. On Fri, Oct 21, 2016 at 4:12 PM, Dale Henrichs < dale.henri...@gemtalksystems.com> wrote: > Norbert, > > I didn't realize that you were claiming that the new text model for Sparta > was

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-21 16:15 GMT+02:00 Tudor Girba : > > I would kindly ask for patience. What is perhaps less clear is that this > editor is in the critical path of the GT project and we are committed to > deliver an editor that actually works. We are still investigating different >

Re: [Pharo-dev] [ANN] Sparta v1.1

Hi, > On Oct 21, 2016, at 3:55 PM, Denis Kudriashov wrote: > > > 2016-10-21 15:21 GMT+02:00 Tudor Girba : > > but at the rate we > > reinvent the wheel, I often fear that I will be retired from programming > > before we have a sane text model :/ > >

Re: [Pharo-dev] [ANN] Sparta v1.1

Norbert, I didn't realize that you were claiming that the new text model for Sparta was (potentially) inferior. The other day you were expressing sadness about having to use the newer version of Metacello (which is *only* 3 years old), so I assumed that you were just being generally cranky

Re: [Pharo-dev] [ANN] Sparta v1.1

Hi Norbert, It is not ignored at all. Cheers, Doru > On Oct 21, 2016, at 3:50 PM, Norbert Hartl wrote: > > Dale, > > I was not arguing against evolution. I was refering to the fact that work of > others is mostly ignored just to come up with a potential weaker solution.

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-21 15:21 GMT+02:00 Tudor Girba : > > but at the rate we > > reinvent the wheel, I often fear that I will be retired from programming > > before we have a sane text model :/ > > I would kindly ask for patience. What is perhaps less clear is that this > editor is in

Re: [Pharo-dev] [ANN] Sparta v1.1

Dale, I was not arguing against evolution. I was refering to the fact that work of others is mostly ignored just to come up with a potential weaker solution. Norbert > Am 21.10.2016 um 15:34 schrieb Dale Henrichs > : > > Norbert, > > It is also called

Re: [Pharo-dev] [ANN] Sparta v1.1

Hi Clement, Thanks for raising this question. In short, Sparta is inspired from Athens and it has a similar structure. So, there is an in-image interface of the canvas, and there is a concrete implementation through the plugin (based on Moz2D). To target a completely in-image rendering, it is

Re: [Pharo-dev] [ANN] Sparta v1.1

Norbert, It is also called evolution ... with each step forward new possibilities are revealed and often the old (current) way of doing things needs to change to better leverage these new possibilities ... and evolution is required[4]. Change is also painful and keeping up with an

Re: [Pharo-dev] [ANN] Sparta v1.1

> On Oct 21, 2016, at 4:00 AM, Sean P. DeNigris wrote: > > Denis Kudriashov wrote >> I look at code and it seems you implemented another one new text model? >> Why >> you not use TxText? > > Argh. I know it's bad form to complain about gifts, A bit :). > but at the

Re: [Pharo-dev] [ANN] Sparta v1.1

On 21/10/16 04:00, Sean P. DeNigris wrote: Denis Kudriashov wrote I look at code and it seems you implemented another one new text model? Why you not use TxText? Argh. I know it's bad form to complain about gifts, but at the rate we reinvent the wheel, I often fear that I will be retired from

Re: [Pharo-dev] [ANN] Sparta v1.1

On 19/10/16 18:06, Aliaksei Syrel wrote: Examples are on class side of: MozExamples, MozTextExamples Error: could not coerce arguments primSetAttributeEnum: anEnumValue index: anIndex ^ self ffiCall: #(void moz2d_filter_node_set_attribute_int(self, FFIExternalEnumeration anIndex,

Re: [Pharo-dev] [ANN] Sparta v1.1

> Am 21.10.2016 um 04:00 schrieb Sean P. DeNigris : > > Denis Kudriashov wrote >> I look at code and it seems you implemented another one new text model? >> Why >> you not use TxText? > > Argh. I know it's bad form to complain about gifts, but at the rate we > reinvent

Re: [Pharo-dev] [ANN] Sparta v1.1

Denis Kudriashov wrote > I look at code and it seems you implemented another one new text model? > Why > you not use TxText? Argh. I know it's bad form to complain about gifts, but at the rate we reinvent the wheel, I often fear that I will be retired from programming before we have a sane text

Re: [Pharo-dev] [ANN] Sparta v1.1

Hi Denis Thanks for your questions! They are important. Unfortunately, I didn't have time today to perform a detailed comparison and stress test of txtext model. I will answer tomorrow :) Cheers, Alex On 20 October 2016 at 22:17, Denis Kudriashov wrote: > > 2016-10-20

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-20 1:15 GMT+02:00 Glenn Cavarlé : > Good job Alex! > Yes, the development version of Bloc is already based on Sparta. > The stable version 0.10.1 is the last version with Athens support. > What the repository for Bloc?

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-20 9:07 GMT+02:00 Aliaksei Syrel : > As I understand, Pharo for PC should not make any assumptions about user's > hardware. If gpu accelerated backend can not be used there should be still > a performant fallback backend which also needs a fallback that is >

Re: [Pharo-dev] [ANN] Sparta v1.1

Hi Aliaksei 2016-10-20 9:16 GMT+02:00 Aliaksei Syrel : > Was tough decision :) We decided (in GT) that next moldable tool should be > a "Moldable Text Editor for Pharo". Here are some requirement that must be > full-filled by text editor: > Could you explain what is wrong

Re: [Pharo-dev] [ANN] Sparta v1.1

Good job Alex! Yes, the development version of Bloc is already based on Sparta. The stable version 0.10.1 is the last version with Athens support. Cheers, Glenn. - Glenn Cavarlé -- View this message in context: http://forum.world.st/ANN-Sparta-v1-1-tp4919394p4919438.html Sent from the

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-19 18:06 GMT+02:00 Aliaksei Syrel : > - Added initial text support, for instance rendering and high precision > measurement. I look at code and it seems you implemented another one new text model? Why you not use TxText?

Re: [Pharo-dev] [ANN] Sparta v1.1

2016-10-19 18:06 GMT+02:00 Aliaksei Syrel : > Examples are on class side of: MozExamples, MozTextExamples > I found 18+ example :)))

Re: [Pharo-dev] [ANN] Sparta v1.1

Great! Seems to be the case that we need to take the 64bit border!! Norbert > Am 19.10.2016 um 18:06 schrieb Aliaksei Syrel : > > Hi > > I am happy to announce the release of Sparta v1.1 for Pharo 6. > https://github.com/syrel/Sparta/tree/v1.1 > > It can be bootstrapped

Re: [Pharo-dev] [ANN] Sparta v1.1

Great work! Doru > On Oct 19, 2016, at 5:06 PM, Aliaksei Syrel wrote: > > Hi > > I am happy to announce the release of Sparta v1.1 for Pharo 6. > https://github.com/syrel/Sparta/tree/v1.1 > > It can be bootstrapped with the following script: > > Metacello new > >

Re: [Pharo-dev] [ANN] Sparta v1.1

This is impressive! We are moving right! Alexandre > On Oct 19, 2016, at 1:06 PM, Aliaksei Syrel wrote: > > Hi > > I am happy to announce the release of Sparta v1.1 for Pharo 6. > https://github.com/syrel/Sparta/tree/v1.1 > >