October 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by S Krish

./startAll first gave an permission denied error , changed to the .hood/platform/linux folder to give permissions.. then it gave "Not implemented yet" realize the startAll has just that echo..!. lead me on a bit more.. On Mon, Oct 6, 2014 at 11:13 AM, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > > > The links has the step by step. I am running it as I type.. > > * For newbies on linux a mention of dependencies viz installing git / > curl/ npm , node.js and bower and any others reqd would be great.. > > Anyways will post my attempt note in a few min.. > > > > On Mon, Oct 6, 2014 at 11:06 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> Great ! >> >> Wasn't there a step by step tutorial somewhere ? >> >> On 05 Oct 2014, at 23:04, Sebastian Sastre <sebastian(a)flowingconcept.com> >> wrote: >> >> > Hi guys, >> > >> > Iâm sharing slides of my presentation at CampSmalltalkVI2014 >> > http://www.slideshare.net/sebastianconcept/flow-39897704 >> > >> > >> > From flowâs readme at github: >> > >> > Flow's mission is to provide consultants, startups and software houses >> with a competitive Smalltalk full-stack framework that allows them to >> quickly deliver a demo with all the modern html5 features the market >> expects today (2014). The idea is that they can tactically use this >> framework to keep momentum up among their prospects and clients and scale >> things to full successful projects delivered by kickass productive teams or >> individuals. >> > >> > sebastian >> > >> > o/ >> > >> > blog: http://sebastianconcept.com >> > LinkedIn: http://www.linkedin.com/in/sebastiansastre >> > github: https://github.com/sebastianconcept >> > >> > >> > >> > >> > >> >> >> >

Oct. 6, 2014

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by stepharo

On 6/10/14 06:40, Tudor Girba wrote: > Hi Sebastian, > > Interesting. Is there a relation between flow and Tide? Indeed I asked myself the same because I would like to see more traction around tide because this is a great framework. > > Cheers, > Doru > > > > On Sun, Oct 5, 2014 at 11:04 PM, Sebastian Sastre > <sebastian(a)flowingconcept.com <mailto:sebastian@flowingconcept.com>> > wrote: > > Hi guys, > > Iâm sharing slides of my presentation at CampSmalltalkVI2014 > http://www.slideshare.net/sebastianconcept/flow-39897704 > > > From flowâs readme at github <https://github.com/flow-stack/flow>: > > Flow's mission is to provide /consultants/, /startups/ and > /software houses/ with *a competitive Smalltalk full-stack > framework* that allows them to quickly deliver a demo with all the > modern html5 features the market expects today (2014). The idea is > that they can tactically use this framework to keep momentum up > among their prospects and clients and scale things to full > successful projects delivered by kickass productive teams or > individuals. > > sebastian <https://about.me/sebastianconcept> > > o/ > > blog: http://sebastianconcept.com <http://sebastianconcept.com/> > LinkedIn: http://www.linkedin.com/in/sebastiansastre > github: https://github.com/sebastianconcept > > > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Oct. 6, 2014

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by S Krish

The links has the step by step. I am running it as I type.. * For newbies on linux a mention of dependencies viz installing git / curl/ npm , node.js and bower and any others reqd would be great.. Anyways will post my attempt note in a few min.. On Mon, Oct 6, 2014 at 11:06 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Great ! > > Wasn't there a step by step tutorial somewhere ? > > On 05 Oct 2014, at 23:04, Sebastian Sastre <sebastian(a)flowingconcept.com> > wrote: > > > Hi guys, > > > > Iâm sharing slides of my presentation at CampSmalltalkVI2014 > > http://www.slideshare.net/sebastianconcept/flow-39897704 > > > > > > From flowâs readme at github: > > > > Flow's mission is to provide consultants, startups and software houses > with a competitive Smalltalk full-stack framework that allows them to > quickly deliver a demo with all the modern html5 features the market > expects today (2014). The idea is that they can tactically use this > framework to keep momentum up among their prospects and clients and scale > things to full successful projects delivered by kickass productive teams or > individuals. > > > > sebastian > > > > o/ > > > > blog: http://sebastianconcept.com > > LinkedIn: http://www.linkedin.com/in/sebastiansastre > > github: https://github.com/sebastianconcept > > > > > > > > > > > > >

Oct. 6, 2014

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by Sven Van Caekenberghe

Great ! Wasn't there a step by step tutorial somewhere ? On 05 Oct 2014, at 23:04, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > Hi guys, > > Iâm sharing slides of my presentation at CampSmalltalkVI2014 > http://www.slideshare.net/sebastianconcept/flow-39897704 > > > From flowâs readme at github: > > Flow's mission is to provide consultants, startups and software houses with a competitive Smalltalk full-stack framework that allows them to quickly deliver a demo with all the modern html5 features the market expects today (2014). The idea is that they can tactically use this framework to keep momentum up among their prospects and clients and scale things to full successful projects delivered by kickass productive teams or individuals. > > sebastian > > o/ > > blog: http://sebastianconcept.com > LinkedIn: http://www.linkedin.com/in/sebastiansastre > github: https://github.com/sebastianconcept > > > > >

Oct. 6, 2014

Re: [Pharo-dev] gt issues

by Tudor Girba

Hi Phil, Sorry for the late reply. I cannot reproduce the stepping problem. Do you have a specific case? "Run to here" exists. It is a contextual action that depends on the cursor position. Hence, it is mapped in the context menu. Cheers, Doru On Sat, Oct 4, 2014 at 11:07 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > I'd say that it is not intuitive at first but the abilities of the GT > inspector are really making up for any inconvenience. > > As for the GT debugger, I've been running in a couple of problems, namely > that stepping when restarting hasn't been working properly after a couple > times. > > Also, I miss the "run to here" option that was in the debuggers before. It > looks like gone. > Why? It is a common option in all languages. > > Phil > > > On Sat, Oct 4, 2014 at 10:56 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> Thanks for the feedback. >> >> Of course, they are not used anywhere else at this point just because the >> inspector is the first tool that was integrated into Pharo :). >> >> You say they are meaningless, but in fact you seem to have no problem >> with what they are and how they work. And you found it out by yourself. I >> agree that it is a different interface than anything else out there, but >> that is not a negative thing. Actually, we also tried other variations, >> but this was the one we stuck with, and most people seem to not have a >> problem with it. What do you mean by "video controller buttons"? >> >> And, you are right in that the contrast is not proper in the Pharo theme. >> This will change. In the meantime, here is how they look like in the >> WhitespaceTheme >> [image: Inline image 1] >> >> Is this better? >> >> Cheers, >> Doru >> >> >> >> On Sat, Oct 4, 2014 at 1:15 PM, kmo <voxkmp(a)gmail.com> wrote: >> >>> Well, one man's intuitive is another man's completely obscure. In the >>> pharo >>> context, the dots are a completely new navigation widget - used nowhere >>> else >>> - and their function is unclear. I think part of the problem is that the >>> dots do not appear on any kind of obvious toolbar - they are more or less >>> just dots on the bottom of the window. There is no visual cue that they >>> have >>> any function at all. They could be mere decoration. Just my two cents. >>> >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/gt-issues-tp4782476p4782557.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 6, 2014

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by S Krish

Abs great .. !.. https://github.com/flow-stack/flow have yet to install and check if it has any issues in my system. Will check it out, infact have a hackathon to see if this can be tried out on it. Nice framework to demo Smalltalk to the crowd in a banking world.. On Mon, Oct 6, 2014 at 2:34 AM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > Hi guys, > > Iâm sharing slides of my presentation at CampSmalltalkVI2014 > http://www.slideshare.net/sebastianconcept/flow-39897704 > > > From flowâs readme at github <https://github.com/flow-stack/flow>: > > Flow's mission is to provide *consultants*, *startups* and *software > houses* with *a competitive Smalltalk full-stack framework* that allows > them to quickly deliver a demo with all the modern html5 features the > market expects today (2014). The idea is that they can tactically use this > framework to keep momentum up among their prospects and clients and scale > things to full successful projects delivered by kickass productive teams or > individuals. > > sebastian <https://about.me/sebastianconcept> > > o/ > > blog: http://sebastianconcept.com > LinkedIn: http://www.linkedin.com/in/sebastiansastre > github: https://github.com/sebastianconcept > > > > > >

Oct. 6, 2014

WhatsUp from: 2014-10-06 until: 2014-10-19

by seaside＠rmod.lille.inria.fr

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: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2014-10-19 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Oct. 6, 2014

Re: [Pharo-dev] Third Addition to GT-Inspector

by Tudor Girba

Thank you, Sven. Doru On Sun, Oct 5, 2014 at 11:10 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > My third addition to GT-Inspector: > > === > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.61 > Author: SvenVanCaekenberghe > Time: 5 October 2014, 11:07:12.742994 pm > UUID: 5a40e21d-c56d-467a-ae31-7878678f6254 > Ancestors: GT-InspectorExtensions-Core-AndreiChis.60 > > Allow items of String and ByteArray to be inspected (removed > #gtInspectorItemsIn: for those classes) > > Switched index and item columns in > SequenceableCollection>>#gtInspectorItemsIn: > > Added ByteArray>>#gtInspectorBytesIn: to show > - a hex string > - a set of formatted hex blocks > - latin1 interpretation > - utf8 interpretation > - integer interpretation (big endian) > - reversed integer interpretation (little endian) > with error handling and interactive size protection > === > > It looks like this: > > > This is based on what we had in EyeByteArrayInspector. > > Needs to be looked at I guess. > > Sven > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 6, 2014

Re: [Pharo-dev] [ANN] flow: a living full-stack #âframework for the web

by Tudor Girba

Hi Sebastian, Interesting. Is there a relation between flow and Tide? Cheers, Doru On Sun, Oct 5, 2014 at 11:04 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > Hi guys, > > Iâm sharing slides of my presentation at CampSmalltalkVI2014 > http://www.slideshare.net/sebastianconcept/flow-39897704 > > > From flowâs readme at github <https://github.com/flow-stack/flow>: > > Flow's mission is to provide *consultants*, *startups* and *software > houses* with *a competitive Smalltalk full-stack framework* that allows > them to quickly deliver a demo with all the modern html5 features the > market expects today (2014). The idea is that they can tactically use this > framework to keep momentum up among their prospects and clients and scale > things to full successful projects delivered by kickass productive teams or > individuals. > > sebastian <https://about.me/sebastianconcept> > > o/ > > blog: http://sebastianconcept.com > LinkedIn: http://www.linkedin.com/in/sebastiansastre > github: https://github.com/sebastianconcept > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Oct. 6, 2014

Re: [Pharo-dev] Issue 14160: Introduce isXXX dialect testing methods to SmalltalkImage to ease cross-dialect development

by David T. Lewis

Speaking as the maintainer of an external package (OSProcess/CommandShell) I agree with both Stef and Johan. Feature detection is better, because "pharo" (or "squeak", or "gemstone") is meaningless over time as the dialect changes. If you need to test for some feature, it is better to test for it explicitly than to assume that it exists in all versions of a specified dialect. As Stef says, Seaside with Grease is the way to go. The test for any given feature belongs in an external package (Grease), not in the core images. For a significant external package such as Seaside, use the abstraction layer of Grease. For simpler cases (e.g. OSProcess) put the required tests directly into that external package. But either way the isFoo tests belong in the external packages, and not in pharo/squeak/gemstone proper. Dave On Sun, Oct 05, 2014 at 10:29:26AM +0200, Johan Brichau wrote: > It?s true that when you do a lot of cross-dialect development, such a method is often what you desire. > However, I think it?s better to do feature detection instead of dialect detection. So, something like: > > ((Smalltalk includesKey: #CharacterWriteStream) ifTrue:[ > stream := CharacterWriteStream on: (String new: 10) > ] ifFalse:[ > stream := WriteStream on: (String new: 10) > ] > > And yes: use Grease where applicable. We try to maintain Grease across Pharo, Squeak and Gemstone. I also think it?s actively ported to VA. > > cheers > Johan > > On 05 Oct 2014, at 09:00, stepharo <stepharo(a)free.fr> wrote: > > > Hi jan > > > > Thanks for the proposal. > > I thought about it and I'm against because it goes again the idea of dispatch. > > I prefer to have a class and some dispatch. Seaside with Grease is the way to go from my perspective. > > Finally I do not want such methods in the systems because I spent my time removing isXXXX because of bad design. > > Let us see what other people think. > > > > Stef > > > > On 4/10/14 22:14, Jan Vrany wrote: > >> Hi guys, > >> > >> I've just opened: > >> > >> https://pharo.fogbugz.com/f/cases/14160/Introduce-isXXX-dialect-testing-met… > >> > >> Introduce isXXX (isPharo, isVisualWorks, ...) dialect testing methods to > >> SmalltalkImage to ease multi-dialect development. > >> > >> RATIONALE: > >> > >> Commonly used approach to solve differences among dialect is to use a > >> sort of platform object and dispatch there for troublesome operations > >> that has to be specialized. This platform object is usually in platform > >> specific package. > >> Other option is to load some library like Grease or Sport. > >> > >> The problem of the first approach is that brings to much (unnecessary) > >> burden when used for two, three things. The amount of of the code and > >> management is way to bigger then the amount of the code that has to be > >> specialized. Loading Grease/Sport on the other hand introduces a > >> dependency on an external package - not worth of for two or three > >> things. > >> > >> The proposed dialect testing messages would allow for simple, > >> #ifdef-like idiom like: > >> > >> | stream | > >> ... > >> ((Smalltalk respondsTo: #isSomeCoolDialect) and:[Smalltalk > >> isSomeCoolDialect]) ifTrue:[ > >> stream := CharacterWriteStream on: (String new: 10) > >> ] ifFalse:[ > >> stream := WriteStream on: (String new: 10) > >> ] > >> > >> The #respondsTo: check, while not nice, is required as at the moment not > >> all dialects could be trusted to have these testing messages. > >> > >> Putting these methods may not stick with Pharo standard (whatever it > >> is), but Smalltalk global is probably one of the > >> very few that are present in pretty much every Smalltalk implementation. > >> Other option would be to place them to the class side of an Object > >> (which is amost certainly present everywhere), however > >> > >> Smalltalk isPharo > >> > >> reads better than > >> > >> Object isPharo. > >> > >> Best, Jan > >> > >> > >> > > > > >

Oct. 6, 2014