- Pharo-users - lists.pharo.org

Re: [Pharo-users] SQL Server
by Linkerstorm June 12, 2018

June 12, 2018

Thanks for the suggestion but already tried with no luck : only the drivers for MySql, PostgresV2 and Sqlite3exist, no OpenDbx driver available, despite the documentation... Le mar. 12 juin 2018 Ã 22:26, orsayman via Pharo-users < pharo-users(a)lists.pharo.org> a Ã©crit : > I'm not an expert but have a look at DBXTalk > <https://guillep.github.io/DBXTalk/garage/drivers.html> . If I understand > correctly, it is able to connect to SQL Server. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

1 0

Re: "News" section of the website down
by orsayman June 12, 2018

June 12, 2018

I just wanted to bump this thread because it still doesn't work. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

Re: SQL Server
by orsayman June 12, 2018

June 12, 2018

Ah, I have seen your message on SO. Sorry, I can't help more. Maybe someone knows how to install DBXTalk on pharo 6.1. Have you tried to contact the authors or the community (https://guillep.github.io/DBXTalk/contact.html) ? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

SQL Server
by Linkerstorm June 12, 2018

June 12, 2018

Hi. With Pharo 6.1, how to connect to a SQL Server database ? Thanks.

2 1

Macros?
by Debiller 777 June 12, 2018

June 12, 2018

Well, I've already asked about adding new literals to pharo or Smalltalk in general, however this time I have a better idea: macros. Can they be added? Because if I understand correctly they may be the only way to do that.

9 12

[Ann] Iceberg v1.1.0
by Guillermo Polito June 11, 2018

June 11, 2018

Time for the weekly Iceberg update. Thanks to all brave users, issue reporters and contributors :). Key changes: we have introduced some tag support, a new credential manager to manage keys and passwords per host or repository, a new version of tonel, and made a first step towards a simplified contribution to Iceberg by listing it as Pharo's repository. Enjoy, Guille in behalf of all Iceberg contributors Following, the detailed changes log. New Features #842 <https://github.com/pharo-project/pharo/pull/842> Adding Credentials Store #843 <https://github.com/pharo-project/pharo/pull/843> Update Tonel to 1.0.7 #823 <https://github.com/pharo-project/pharo/pull/823> Iceberg repository should be listed as Pharo's one #841 <https://github.com/pharo-project/pharo/pull/841> Basic tag support ( #372 <https://github.com/pharo-project/pharo/pull/372>) Infrastructure #787 <https://github.com/pharo-project/pharo/pull/787> Add Windows ci with Appveyor (not yet green!) Enhancements #827 <https://github.com/pharo-project/pharo/pull/827> Add package dialog has some glitches #833 <https://github.com/pharo-project/pharo/pull/833> replace #asIcon with #iconNamed: #832 <https://github.com/pharo-project/pharo/pull/832> Move Iceberg from MostUsedTools to Tools #830 <https://github.com/pharo-project/pharo/pull/830> Better handling of not github remote urls #825 <https://github.com/pharo-project/pharo/pull/825> Enhance Migrate to tonel commit message #637 <https://github.com/pharo-project/pharo/pull/637> Show tag version instead of "Detached HEAD" #829 <https://github.com/pharo-project/pharo/pull/829> migrate-versions-browser Bug Fixes #835 <https://github.com/pharo-project/pharo/pull/835> Compare file definitions by their binary uninterpreted content #838 <https://github.com/pharo-project/pharo/pull/838> Clone from incorrect github repository fails with DNU #826 <https://github.com/pharo-project/pharo/pull/826> Pushing to virgin repository raises a DNU

3 3

Re: [Pharo-users] [Pharo-dev] Web Frameworks and "Modern" Features
by HernÃ¡n Morales Durand June 9, 2018

June 9, 2018

Hi Paul, I moved the discussion to pharo-users because this has nothing to do with Pharo developement and people could get upset. 2018-06-09 13:10 GMT-03:00 Paul DeBruicker <pdebruic(a)gmail.com>: > Hi > > I think we're doing OK and that its a "discoverability" problem not a "does > not exist or work" problem. E.g. here is Johan's talk about integrating > ReactJS & Seaside https://www.youtube.com/watch?v=1eSGO7QSz5c > > I think part of the problem is that Facebook/Google/Amazon dominate the 'new > hotness' discussions and no one has problems at their scale so the solutions > that work for them that they advocate that people adopt (so e.g. their > hiring pool is better for them) aren't necessarily necessary/appropriate for > smaller sites with fewer engineers. > > For responsive design if he means sites that look good on big or small > screens we're OK as its mostly a CSS problem which can be handled out of the > box by adopting either Torsten's Twitter Bootstrap library > (http://smalltalkhub.com/#!/~TorstenBergmann/Bootstrap) or Cyril's Google > Material Design adaptation (https://github.com/DuneSt/MaterialDesignLite) > if you're using Seaside. Or just setting a few viewport width breakpoints > in your existing css and changing styles appropriately if you don't want to > adopt one of those frameworks or are using Teapot or Iliad or whatever. > So there is no framework refinement, but behavior partitioning into newer tools that require more human training and adoption time. If we don't have the resources of Facebook/Twitter/Google then why we are integrating their solutions? The real value of a framework is evolving to enable new refined instantiations. This is not a problem of being covered by fashioned tools, the problem is we are "buying" solutions from other ecosystems where they don't care at all about Pharo, Seaside, Iliad, etc. We stop building systems to integrate modules. Standard solutions like Bootstrap don't came for free, it has a cost, for example if you have to customize a component, you automatically loose the value of the Smalltalk environment. But this cost is usually hidden behind promotion and noise, the tools survive more than developer investment, and usually after a few years the developer has to invest more time and energy learning and using a newer external library... losing again the chance to gain experience cycles with tools built for its own niche. > > For static-site generators you'd probably want to use Teapot > (http://smalltalkhub.com/#!/~zeroflag/Teapot) and just write the generated > HTML to a file. For Seaside you could make one using WABuilder but would > need to add paths to all of the anchors on your site, which could be done > with a RB transformation rule if you had a ton of links. > I get it, most standard things could be done already. My point is at some point Seaside wasn't easily adaptable to not instantiate web controllers, to define routes programmatically, etc. > > For the multiple competing JS library concern I'm not sure what that means > exactly but also how it could be any different in this community vs e.g. > Ruby/Rails. Just gotta manage the namespaces in the DOM right I think? If > its been a problem for me I've forgotten or haven't noticed. > I mean the time when transition from Prototype/Scriptaculous was promoted in favour first of MooTools (easier syntax, lightweight and more modular than Prototype) and later of jQuery. Not counting other client-side alternatives like Dojo or YUI. It means who's gonna invest time = money, in a small community, building a good adaptor for the next JS libraries? We should really stop assuming someone else will just do it for us. > > > I'd be happy to learn more about the other things he mentions. I know > there's this page that describes how Seaside has some inherent security > protections (http://seaside.st/about/security) but maybe he's referring to > something different? Also testing a Seaside site is pretty straightforward > with https://github.com/SeasideSt/Parasol > > > So anyway, I think its out there. Mostly. Except for buzz. > You're right, the tools could be out there. Except also for the lack of feedback, and (as community) running always behind the big players... > There's definitely a very usable/useful set of things that can be done with > what we have today. > > But no question the Rails or JS communities have more because there are more > engineers/companies/resources in and behind them. > > > Hope this helps. > Thank you, good points. HernÃ¡n > > Paul > > > > Sean P. DeNigris wrote >> Hernan related running into the following limitations with Pharo web >> frameworks. I wonder if these are all still missing or if any are now >> availableâ¦ >> >>> None of them was easily adapted to the emerging web trends for the last >>> years like the >>> appearance of static site generators, adaptive/responsive design, >>> multiple >>> competing JS >>> libraries, semantic web, mobility, etc. not to mention they lack >>> "standard" built-in features >>> such as caching, template, security frameworks. >> >> "adaptive/responsive design" in particular seems like a pretty big >> limitation given current expectationsâ¦ >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

1 0

Pharo 6, bad debugger behaviour
by Tim Mackinnon June 8, 2018

June 8, 2018

Hi, Iâve noticed lately when using a reasonably recent Pharo 6.1 setup that if I restart a method in the debugger - particularly from a breakpoint or correcting a dnu issue the environment frequently locks up. Fearing the worst (after a few seconds), if I repeatedly press cmd . (Say 5 times) after 10 seconds more it comes back with 30 debugger Windows typically with something like Instance of Xxxx dnu: #someMethod (which is legit as I might have a now corrupt inst bar). I understand the error, but why does it lockup and require the cmd . Dance? I dont recall earlier Pharos doing this (and not other smalltalks). Should I report this? Tim Sent from my iPhone

4 6

[Issue Tracker] Please check issue tracker
by Marcus Denker June 8, 2018

June 8, 2018

Hi, If you -> submitted an issue in the past -> have been involved in some discussion about an issue ===> please check the issue tracker. There are many cases where e.g. - some issue has been fixed but the issue tracker entry is not closed - where a discussion came to a conclusion but no action happened. - you reported issue has been fixed in the meantime but the issue tracker entry is still open. https://pharo.fogbugz.com/f/filters/57/All-newest-first We have right now 471 open issues, I am sure we can get that number down! Marcus

1 0

Why do #select:thenXxx methods not return their result
by Tim Mackinnon June 8, 2018

June 8, 2018

Hi - are the methods like #select:thenCollect: frowned upon? They seem quite readable , however in using them Iâve noticed that unlike the core methods they done return the result of evaluation (they are missing a ^). This is a shame, but possibly an oversight? Tim Sent from my iPhone

3 4