- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Sven Van Caekenberghe

> On 22 Sep 2015, at 08:47, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > > Le 22 sept. 2015 Ã 07:49, philippe.back(a)highoctane.be a Ã©crit : > >> >> Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : >> > >> > >> > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: >> > > >> > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. >> > > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! >> > > We save code that the parser cannot parse. What we fun idea. >> > > So people are bashing for backward compatibility and we remove a bad way to encode >> > > metadata then suddenly it looks like we were doing something bad. >> > > >> > > Stef >> > >> > I am with Stef, it is a silly idea to mix the two. Nobody uses this in Pharo. Cleaning up means simplifying too. >> >> In the code no. But in the comments, that would be good to have back. In color form. As we can write pillar class comments, can't we render them ? Moose as an editor/viewer for pillar files >> >> > > Yes, it is where we want to go: use Pillar for styled comments. > Once we have that, we can remove Text styling from source code / comments. Yes, inside a comment, which should be totally opaque from a language syntax standpoint, you can do whatever you want: HTML, Markdown, Pillar, Pier, ...

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Christophe Demarey

Le 22 sept. 2015 Ã 07:49, philippe.back(a)highoctane.be a Ã©crit : > > Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > > > > > > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: > > > > > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. > > > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! > > > We save code that the parser cannot parse. What we fun idea. > > > So people are bashing for backward compatibility and we remove a bad way to encode > > > metadata then suddenly it looks like we were doing something bad. > > > > > > Stef > > > > I am with Stef, it is a silly idea to mix the two. Nobody uses this in Pharo. Cleaning up means simplifying too. > > In the code no. But in the comments, that would be good to have back. In color form. As we can write pillar class comments, can't we render them ? Moose as an editor/viewer for pillar files > > Yes, it is where we want to go: use Pillar for styled comments. Once we have that, we can remove Text styling from source code / comments.

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by philippe.back＠highoctane.be

Le 22 sept. 2015 07:40, "Sven Van Caekenberghe" <sven(a)stfx.eu> a Ã©crit : > > > > On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: > > > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. > > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! > > We save code that the parser cannot parse. What we fun idea. > > So people are bashing for backward compatibility and we remove a bad way to encode > > metadata then suddenly it looks like we were doing something bad. > > > > Stef > > I am with Stef, it is a silly idea to mix the two. Nobody uses this in Pharo. Cleaning up means simplifying too. In the code no. But in the comments, that would be good to have back. In color form. As we can write pillar class comments, can't we render them ? Moose as an editor/viewer for pillar files. Phil > >

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Sven Van Caekenberghe

> On 21 Sep 2015, at 23:53, stepharo <stepharo(a)free.fr> wrote: > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! > We save code that the parser cannot parse. What we fun idea. > So people are bashing for backward compatibility and we remove a bad way to encode > metadata then suddenly it looks like we were doing something bad. > > Stef I am with Stef, it is a silly idea to mix the two. Nobody uses this in Pharo. Cleaning up means simplifying too.

Sept. 22, 2015

Re: [Pharo-dev] [ANN]: AconcaguaAddOns

by HernÃ¡n Morales Durand

Someone can confirm Aconcagua is loadable through Metacello Configurations under Windows? Cheers, HernÃ¡n 2015-09-18 17:22 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Hi Sean, > > First thanks for sharing this. > > Now I suppose this was AconcaguaDeluxe before? > Do you have a ConfigurationOf for AconcaguaAddOns? > > I want to use it but don't have idea what to load. > > HernÃ¡n > > > 2015-04-21 13:21 GMT-03:00 Sean P. DeNigris <sean(a)clipperadams.com>: > >> I pushed some Aconcagua extensions to >> http://smalltalkhub.com/mc/SeanDeNigris/AconcaguaAddOns/main/ >> >> One part consists of tiny (so far) Aconcagua models of various domains - >> Time*, Money, and Weight at the moment. >> >> The other is the Aconcagua-Magritte package. This gives you >> MAMeasureDescription, which represents an Aconcagua Measure. It mostly >> acts >> like a number field mapped to its amount. You just have to tell it which >> unit to use to convert the amount number into a Measure. >> >> Example usage: >> MAMeasureDescription new >> accessor: #replacementPrice; >> label: 'Replacement Price'; >> unit: AmDollar new; >> yourself >> >> Then, you can type 100 in a Magritte form and "100 dollars" will be saved >> to >> the model. Enjoy! >> >> * Yes, I know Chalten has months and years, but (I think when Chalten was >> extended to handle non-Gregorian calendars) months and year units are no >> longer derived from each other, and so can not be compared. >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/ANN-AconcaguaAddOns-tp4820940.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Craig Latta

(autocorrect-unmangled version... ;) Eliot writes: > ...I was pragmatic and made sure Cog supported the existing > requirements, not some platonic ideal. I wish you would adopt as a > principle that functionality be retained as you are cleaning up > Pharo. Instead I see useful functionality is discarded because of > scruples and I find it "unpleasant". -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by Eliot Miranda

Hi Stef, > On Sep 21, 2015, at 2:53 PM, stepharo <stepharo(a)free.fr> wrote: > > I think that having metadata (style) language and data (source code) mixed together is a bad idea. > I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! > We save code that the parser cannot parse. What we fun idea. > So people are bashing for backward compatibility and we remove a bad way to encode > metadata then suddenly it looks like we were doing something bad. It seems to me you are confusing functionality and implementation. Just because you don't like the implementation is no reason to lose the functionality. No implementation is perfect, so this path leads to a denuded system. The onus is on the community to reimplement things well, not throw things away just because the implementation is problematic. If I had chosen to implement Cog with a much nicer substrate then neither Squeak, nor Pharo nor Newspeak would have been able to benefit. Instead I was pragmatic and made sure Cig supported the existing requirements, not done platonic ideal. I wish you would adopt as a principle that functionality be retained as you are cleaning up Pharo. Instead I see useful fictional its discarded because if scruples and I find it "unpleasant". _,,,^..^,,,_ (phone) > > Stef >

Sept. 22, 2015

Re: [Pharo-dev] TextAttributes in source code or class comment?

by stepharo

I think that having metadata (style) language and data (source code) mixed together is a bad idea. I never like the ]lang[ tag because it is a huge hack. It does not even exist in the Smalltalk syntax!!! We save code that the parser cannot parse. What we fun idea. So people are bashing for backward compatibility and we remove a bad way to encode metadata then suddenly it looks like we were doing something bad. Stef

Sept. 21, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-21 until: 2015-09-30

by phil＠highoctane.be

> On 21-09-15 07:00, seaside(a)rmod.lille.inria.fr wrote: >Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Finished up Seaside app with Datatables and some nice jQuery - Worked on making TilingWindowManager work in Pharo 5.0 - Started Pharo livecoding on https://www.livecoding.tv/philippeback/ for the TWM port - Started some code to access JIRA from Pharo : queries working - Started some code to access Google Sheets from Pharo (using Zn-SSO) : queries working - Reported bugs > ### What's next, until 2015-09-30 (*): > - Finishing the TWM port and integrating it with DesktopManager - More work on the JIRA/GoogleSheets - (later - next livecoding project): getting PyBridge to work in Pharo 5.0 Phil

Sept. 21, 2015

Re: [Pharo-dev] WhatsUp from: 2015-09-21 until: 2015-09-30

by Stephan Eggermont

On 21-09-15 07:00, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: - Build a prototype of a keyboard-controlled editor and created a video - Updated some Seaside configurations - Found annoying bug in Rubric (that combined well with my own) - Made some updates in PlanBoard: adding/(re)moving columns > ### What's next, until 2015-09-30 (*): > > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION - Fix keyboard based editor bug, add some functionality

Sept. 21, 2015