- Pharo-users - lists.pharo.org

Re: [Pharo-users] Separate compilation with Pillar?

by Alexandre Bergel

> Alex you should use the texmate plugin because the chapter is rendered on Cmd-R. Oh! I did not know this! By the way, is there a way to have the spell checker when using TextMate? I do not have the spell checker when editing Pillar files. Am I the only one? Cheers, Alexandre

July 27, 2015

Re: [Pharo-users] Linux Install -- problems, but eventually successful

by Sean P. DeNigris

Andy Jones wrote > since the instructions at > http://pharo.org/gnu-linux-installation#64-bit-System-Setup seem to be out > of date... > Note that there is no ia32-libs package on Jessie, as far as I can tell. The instructions, under "Ubuntu 14.04 and Later", link to http://pharo.org/gnu-linux-installation#ubuntu-ppa-headless-vm , which advises: sudo add-apt-repository ppa:pharo/stable sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install pharo-vm-core Did you try that? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Linux-Install-problems-but-eventually-successful-tp48… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 27, 2015

Re: [Pharo-users] NativeBoost and variadic functions

by Ben Coman

On Mon, Jul 27, 2015 at 9:56 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >>> >>> And let me remind you that despite that NB implements FFI to speak with >>> C, it is not obliged to implement features of C language itself. It lets >>> you speak with C programs, but not lets you write programs like in C (see >>> the difference? :) >> >> I wasn't implying that implicit type conversion was a good thing that >> needed implementing -- but just a bump if it hadn't needed attention >> to it before when C did it automagically. >> cheers -ben > > > Of course, Ben, i understand that you may miss some of the feature(s), you > get used to when doing things in C. Sorry I wasn't clear so just to emphasise, I agree NB should not implement such a feature. I was trying to say just that it should be explicit** that implicit type conversions are not supported. A lot of programmers at various levels of experience not very aware of implicit type conversions will probably be bitten by the same error. So to avoid the bites, I guess we need to teach this bit of C when teaching NB. ** perhaps with an example demonstrating it, but I don't know what that might be. cheers -ben > But then consider what is involved to implement such feature because it > means determining argument types at run time (at compile time it is > impossible as well as 'compile once when it is invoked for the first time' > that NB does ) > That means that no matter how well you try, the implementation will suck.. > because it will be very slow comparing to one that uses fixed-type > fixed-argument number. > > My philosophy , in general, for programming is avoid bloat and inefficiency > at all costs. When some feature requires bloat and going to be very > inefficient, i simply saying 'No'. > Especially at infrastructural level, which NB belongs to. > Because one thing that you (of me) as implementer knows what is fast & cool > and what is slow & inefficient, but then users come and start using things > in a way you would never think your stuff will be ever used.. and start > spreading inefficiency in their project(s). And more that that, once they > get used to it, then you would be never able to remove it because it is > there and everyone using it and some even loving it :) > > > -- > Best regards, > Igor Stasenko.

July 27, 2015

Re: [Pharo-users] NativeBoost and variadic functions

by Igor Stasenko

> > > > And let me remind you that despite that NB implements FFI to speak with > C, > > it is not obliged to implement features of C language itself. It lets you > > speak with C programs, but not lets you write programs like in C (see the > > difference? :) > > I wasn't implying that implicit type conversion was a good thing that > needed implementing -- but just a bump if it hadn't needed attention > to it before when C did it automagically. > cheers -ben > Of course, Ben, i understand that you may miss some of the feature(s), you get used to when doing things in C. But then consider what is involved to implement such feature because it means determining argument types at run time (at compile time it is impossible as well as 'compile once when it is invoked for the first time' that NB does ) That means that no matter how well you try, the implementation will suck.. because it will be very slow comparing to one that uses fixed-type fixed-argument number. My philosophy , in general, for programming is avoid bloat and inefficiency at all costs. When some feature requires bloat and going to be very inefficient, i simply saying 'No'. Especially at infrastructural level, which NB belongs to. Because one thing that you (of me) as implementer knows what is fast & cool and what is slow & inefficient, but then users come and start using things in a way you would never think your stuff will be ever used.. and start spreading inefficiency in their project(s). And more that that, once they get used to it, then you would be never able to remove it because it is there and everyone using it and some even loving it :) -- Best regards, Igor Stasenko.

July 27, 2015

Re: [Pharo-users] Personal wiki / information manager

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 27/07/15 02:35, stepharo wrote: > > > Le 26/7/15 22:30, Andy Jones a Ã©crit : >> LOL - this is actually what brought me back to Smalltalk again - >> specifically the idea of some sort of programmable Wiki - but I >> certainly don't have any code yet; complete newb here. > > If you want a wiki syntax use pillar because it is the syntax of Pier > and you will get for free all the instratucture and outputter and > editing support. I'm using pandoc's markdown and trying to make pandoc to talk better with Pharo. Pandoc has support for a lot of languages (see graph at [1]), including html and LaTeX, but also a more plural community [2] including plublishers [3] (the post is about using IPython notebook but the supporting format is markdown). In my opinion this is a good example of a place where we need to talk better with external libraries, frameworks and communities. [1] http://pandoc.org/ [2] http://scholarlymarkdown.com/ [3] https://beta.oreilly.com/ideas/jupyter-at-oreilly Cheers, Offray

July 27, 2015

Re: [Pharo-users] Personal wiki / information manager

by Tudor Girba

Indeed, TxText should provide live rendering. In the meantime, we have Rubric and there is a reasonable support for live rendering and linking: http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspe… However, the current problem is the parser. In my solution, I used an island parser based on PetitParser. That's because the main parser is not flexible enough and, for example, does not preserve the locations of AST nodes. So, I would suggest to build on top of the GTInspector extension for now and focus on the Pillar parser. Once the parser will be usable for live rendering, we can switch to the TxText. Who would be interested in participating? Cheers, Doru On Mon, Jul 27, 2015 at 12:21 PM, stepharo <stepharo(a)free.fr> wrote: > Once we will get TxText we will really invest into nice rendering. Now > nothing prevents someone to push to have comments better rendered > based on kasper > > Stef > > Le 27/7/15 10:09, Peter UhnÃ¡k a Ã©crit : > > I think that we would need some better support for text rendering for > Pillar to be usable inside Pharo --- that's reason why I gave up on this > long ago and am still using html (and js) for myself... and also because of > clickable links. > > Kasper Ãsterbye did this some time ago > > â(original thread > http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-td… > ) > > However I have no idea what is the current state of it (Pillar > repository shows only a single commit from April). > > Ideally I want full html+css renderer, but that is hard. > > Peter > > On Mon, Jul 27, 2015 at 9:35 AM, stepharo <stepharo(a)free.fr> wrote: > >> >> >> Le 26/7/15 22:30, Andy Jones a Ã©crit : >> >> LOL - this is actually what brought me back to Smalltalk again - >> specifically the idea of some sort of programmable Wiki - but I certainly >> don't have any code yet; complete newb here. >> >> >> If you want a wiki syntax use pillar because it is the syntax of Pier >> and you will get for free all the instratucture and outputter and >> editing support. >> >> >> On 26 July 2015 21:27:15 BST, Evan Donahue <emdonahu(a)gmail.com> >> <emdonahu(a)gmail.com> wrote: >>> >>> Seems that Pharo is a magnet for this kind of project. I've been writing >>> one as well and using it to organize my research notes. Does anyone working >>> on personal info mgmt tools want to talk offline? I expect we're running >>> into some of the same issues, both conceptual and technical. >>> >>> Evan >>> >>> >>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> >> >> > > -- www.tudorgirba.com "Every thing has its own flow"

July 27, 2015

Re: [Pharo-users] Personal wiki / information manager

by stepharo

Once we will get TxText we will really invest into nice rendering. Now nothing prevents someone to push to have comments better rendered based on kasper Stef Le 27/7/15 10:09, Peter UhnÃ¡k a Ã©crit : > I think that we would need some better support for text rendering for > Pillar to be usable inside Pharo --- that's reason why I gave up on > this long ago and am still using html (and js) for myself... and also > because of clickable links. > > Kasper Ãsterbye did this some time ago > > â(original thread > http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-td… > ) > > However I have no idea what is the current state of it (Pillar > repository shows only a single commit from April). > > Ideally I want full html+css renderer, but that is hard. > > Peter > > On Mon, Jul 27, 2015 at 9:35 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > > > Le 26/7/15 22:30, Andy Jones a Ã©crit : >> LOL - this is actually what brought me back to Smalltalk again - >> specifically the idea of some sort of programmable Wiki - but I >> certainly don't have any code yet; complete newb here. > > If you want a wiki syntax use pillar because it is the syntax of > Pier and you will get for free all the instratucture and outputter > and > editing support. >> >> On 26 July 2015 21:27:15 BST, Evan Donahue <emdonahu(a)gmail.com> >> <mailto:emdonahu@gmail.com> wrote: >> >> Seems that Pharo is a magnet for this kind of project. I've >> been writing one as well and using it to organize my research >> notes. Does anyone working on personal info mgmt tools want >> to talk offline? I expect we're running into some of the same >> issues, both conceptual and technical. >> >> Evan >> >> >> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. > >

July 27, 2015

Re: [Pharo-users] A Morphic ScrumBoard, part 4: Other planning boards

by stepharo

Le 27/7/15 11:04, Tudor Girba a Ã©crit : > We would love to have your demos on Bloc soon :) We all thought the same ;) > > Doru > > On Mon, Jul 27, 2015 at 10:30 AM, Stephan Eggermont <stephan(a)stack.nl > <mailto:stephan@stack.nl>> wrote: > > On 27-07-15 09:38, stepharo wrote: > > you are proving that people can use Morphic to build non > traditional > applications and without roassal :) > > > The Roassal examples made it much easier to get started. > Roassal with Glamour was excellent for building applications > with lots of visualizations. > > I hope having some Morphic examples will give people an easier start. > > Stephan > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

July 27, 2015

Re: [Pharo-users] A Morphic ScrumBoard, part 4: Other planning boards

by Tudor Girba

We would love to have your demos on Bloc soon :) Doru On Mon, Jul 27, 2015 at 10:30 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 27-07-15 09:38, stepharo wrote: > >> you are proving that people can use Morphic to build non traditional >> applications and without roassal :) >> > > The Roassal examples made it much easier to get started. > Roassal with Glamour was excellent for building applications > with lots of visualizations. > > I hope having some Morphic examples will give people an easier start. > > Stephan > > > > -- www.tudorgirba.com "Every thing has its own flow"

July 27, 2015

Re: [Pharo-users] Markdown -> Pillar

by Damien Cassou

HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> writes: > Has anyone implemented a feature to convert a document from Markdown format > to Pillar? not yet. But Jan implemented a full-featured Markdown parser in PetitParser so I guess the hard part has been written already. I know others are interested in that too, e.g., Norbert. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

July 27, 2015