- Pharo-users - lists.pharo.org

Re: [Pharo-users] Tide installation

by phil＠highoctane.be

I tried to get this working. bower installed Tide loaded as per the slides (with some fiddling as what is there doesn't work). Then TDDispatcher tideIndexPageUrl inspect gives http://localhost:7777/tide/tide/index.html (Why that 'tide' twice in there?) And there, no helios or anything. But that may be because I used the wrong bower 1.2.6 version and set stable for Amber as the commit number didn't work. So, Bernat, which bower and which amber in bower.json ? TIA Phil â

Sept. 3, 2014

Re: [Pharo-users] [Article] Reddit.st - In 10 Cool Pharo Classes

by Pierce Ng

On Mon, Sep 01, 2014 at 11:18:14PM +0200, Sven Van Caekenberghe wrote: > Reddit.st - In 10 Cool Pharo Classes Very nice! Pierce

Sept. 3, 2014

Re: [Pharo-users] Date text converter/formatter

by Sven Van Caekenberghe

On 03 Sep 2014, at 15:44, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Esteban A. Maringolo > > > 2014-09-02 17:46 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> On 02 Sep 2014, at 21:39, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>> Thank you. It is certainly better than the base parser. >>> But for formats I can't pass Date objects to #format:, I have to >>> convert them to ZTimestamp before. >> >> (ZTimestampFormat fromString: '2001/02/03') format: Date today. >> >> Can you give an example of what does not work for you ? > > My own brain doesn't work. > I don't know what I did yesterday, but it works as expected now :) > > | format | > format := (ZTimestampFormat fromString: '03/02/2001') createDate. > format parse: '03/09/2014'. > format format: Date today OK > The only thing I'd change is to throw a specific Exception instead of > an AssertionFailure. > But I'm handling parsing errors fine with AssertionFailure handlers anyway. Yes, using #assert: was laziness in the prototyping phase, I try to improve that part. >>> Curiosity #1: Why did you use an example date string instead of using >>> regular patterns like yyyy, dd, hh/hh24, etc? >> >> That is why the formatter/parser was written in the first place ;-) It is modelled after a Go standard library (http://golang.org/src/pkg/time/format.go) and some Ruby library I can't remember the name of. I implemented this as a proof of concept to see if/how it could be done. > > Fair enough. :) > > > Thank you!

Sept. 3, 2014

Re: [Pharo-users] Date text converter/formatter

by Sven Van Caekenberghe

On 03 Sep 2014, at 15:24, Ben Coman <btc(a)openInWorld.com> wrote: > Sven Van Caekenberghe wrote: >> Hi Sean, >> >> On 03 Sep 2014, at 00:32, Sean P. DeNigris >> <sean(a)clipperadams.com> >> wrote: >> >> >>> Sven Van Caekenberghe-2 wrote >>> >>> >>>> Maybe you got the example and the input mixed up ? >>>> >>>> >>> Oh yeah, I did, but even the example in that case is ambiguous, no? >>> >>> (ZTimestampFormat fromString: '02/03/01 (16:05:06)') >>> parse: '10/10/10 (12:01:01)'. >>> >>> How does it decide whether it's American i.e. Feb 3rd, or European i.e. Mar 2nd? >>> >>> >> >> No, it is not ambiguous. The positions in the pattern are not used to determine the meaning of the elements, only the values. >> > > Okay, but its ambiguous in the sense that, at a glance, without knowing the legend (even though you provided it), at least Sean and myself got confused. > > For me part of that confusion is that you said... > > 1=year > > 2=month > > 3=dayInMonth > > 4=hour (16 in 24 hour format) > > 5=minute > > 6=second > > but the example used > 02=month > 03=day No, it is not confusing: the rule is from largest to smallest unit, thus year, month, day, hour, minute and second. Which is the ISO 8601 representation order BTW, making the most scientific sense IMHO. > In either case, its harder to remember which magnitude an arbitrary index number refers, than using the usual mnemonics like this... > yy=year > mm=month > mmm=month name > d=day of month > dd=zero padded day of month > hh=12 hour > HH=24 hour > etc... and thats just off the top of my head. I think most people are familiar with this. > > Alternatively, if you want to use numbers, the following would be more intuitive to anyone glancing at it without needing to know the legend. > 99=year > 12=month > 31=day > 24=24 hour > 12=12 hour > 60=minute > ?=second. > etc... > > btw, I missed the first part of the >> For example, limited to date elements only: >> >> (ZTimestampFormat fromString: '02/03/01') format: Date today. => '09/03/14' >> >> (ZTimestampFormat fromString: '03/02/01') format: Date today. => '03/09/14' >> >> (ZTimestampFormat fromString: 'Feb 3, 2001') format: Date today. => 'Sep 3, 2014' >> >> (ZTimestampFormat fromString: '02-FEB-2001') format: Date today. => '09-SEP-2014' >> >> (ZTimestampFormat fromString: 'Saturday, Februari 3 ''01') format: Date today. => 'Wednesday, September 3 ''14' >> >> The reference date is 20010203 which was a Saturday, the recognised elements for dates are: >> >> '2001' yearFourDigits >> '01' yearTwoDigits >> '02001' yearFull >> '02' monthTwoDigits >> '2' month >> 'February' monthNameCapitalized >> 'february' monthNameLowercased >> 'FEBRUARY' monthNameUppercased >> 'Feb' monthNameAbbreviatedCapitalized >> 'feb' monthNameAbbreviatedLowercased >> 'FEB' monthNameAbbreviatedUppercased >> '3' day >> '_3' dayTwoDigitsSpacePadded >> '03' dayTwoDigits >> >> See #formatSpecifications, each of those has parse and format methods, like #format:yearTwoDigitsOn: and #parseYearTwoDigitsFrom: >> >> Sven >> >> >> >> >> >> >> >> >> > That interesting. With the call of #formatSpecifications from... > ZTimestampFormat class >> initialize > "Initialize this class, to be redone every time #formatSpecifications changes." > Formats := Dictionary newFromPairs: self formatSpecifications. > FormatKeys := Formats keys sorted: [ :x :y | x size >= y size ] > > it looks like the format specifications could almost be pluggable. What if /Formats/ was instead an instance variable, such that my project could provide an extention method like this... > ZTimestampFormat class >> myFormatSpecifications > ^ #( > 'YYYY' yearFourDigits > 'YY' yearTwoDigits > 'MM' monthTwoDigits > 'M' month > 'Month' monthNameCapitalized > 'month' monthNameLowercased > 'MONTH' monthNameUppercased > 'Mth' monthNameAbbreviatedCapitalized > 'mth' monthNameAbbreviatedLowercased > 'MTH' monthNameAbbreviatedUppercased > 'D' day > '_D' dayTwoDigitsSpacePadded > 'DD' dayTwoDigits > 'h' hour12 > 'hh' hour12TwoDigits > 'HH' hour24TwoDigits > 'PM' daypartUppercased > 'pm' daypartLowercased > 'm' minute > 'mm' minuteTwoDigits > 's' second > 'ss' secondTwoDigits > 'Z' timeZoneZ > '+00:00' timeZone > 'UTC' timeZoneAbbreviated > 'UTCLong' timeZoneAbbreviatedLong > 'Weekday' weekdayNameCapitalized > 'weekday' weekdayNameLowercased > 'WEEKDAY' weekdayNameUppercased > 'Wday' weekdayNameAbbreviatedCapitalized > 'wday' weekdayNameAbbreviatedLowercased > 'WDAY' weekdayNameAbbreviatedUppercased ) > > so I could go something like... > (ZTimestampFormat withSpecification: #myFormatSpecification fromString: 'MM/DD/YY') format: Date today. => '09/03/14' > > That would be coool! > cheers -ben Yes, making it totally pluggable, or at least provide both an example based one and a more classic one makes sense. I'll think about that. Good idea. But the whole concept of the example is that it is easy to remember. Or so it should be ;-) > btw, I didn't understand how yearFull in this line... > '02001' yearFull > was different from yearFourDigits. Some people insist on the fact that using 4 digit years is wrong (http://longnow.org) ;-) For printing, 2001 and 02001 are the same because there is a natural overflow, but for parsing this is not the case: 02001 means using all digits until a non-digit, while 2001 always takes 4, and 01 always takes 2. BTW, these specs are not perfectly deterministic/symmetrical. There are too many date/time formats and conventions.

Sept. 3, 2014

Re: [Pharo-users] Date text converter/formatter

by Esteban A. Maringolo

Esteban A. Maringolo 2014-09-02 17:46 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 02 Sep 2014, at 21:39, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> Thank you. It is certainly better than the base parser. >> But for formats I can't pass Date objects to #format:, I have to >> convert them to ZTimestamp before. > > (ZTimestampFormat fromString: '2001/02/03') format: Date today. > > Can you give an example of what does not work for you ? My own brain doesn't work. I don't know what I did yesterday, but it works as expected now :) | format | format := (ZTimestampFormat fromString: '03/02/2001') createDate. format parse: '03/09/2014'. format format: Date today The only thing I'd change is to throw a specific Exception instead of an AssertionFailure. But I'm handling parsing errors fine with AssertionFailure handlers anyway. >> Curiosity #1: Why did you use an example date string instead of using >> regular patterns like yyyy, dd, hh/hh24, etc? > > That is why the formatter/parser was written in the first place ;-) It is modelled after a Go standard library (http://golang.org/src/pkg/time/format.go) and some Ruby library I can't remember the name of. I implemented this as a proof of concept to see if/how it could be done. Fair enough. :) Thank you!

Sept. 3, 2014

Re: [Pharo-users] Date text converter/formatter

by Ben Coman

Sept. 3, 2014

Re: [Pharo-users] best solution to store data

by Pierce Ng

On Tue, Sep 02, 2014 at 03:23:41PM +0200, Esteban Lorenzano wrote: > so unless you are really constrained for some reason (like imposition of > customers), or you have real use cases (like doing complex tabular > projections), I would always recommend to take another approach than > relational. > > stay in objects as much as you can! SQLite is very popular, and the relational model well known enough that a lot of data is available as SQLite database files or easily transformed into them. When dealing with such data, it is nice to be able to work with SQLite data in Smalltalk. Philosophically, I agree with staying in objects as much as possible. However, right now if I am to build a web app with "real world" storage requirements, i.e. *not* on the scale of FB or Google, I'd probably go with PostgreSQL, just by the sheer availability of knowledge and expertise on running a serious PostgreSQL setup. That, or Gemstone. Pierce

Sept. 3, 2014

Re: [Pharo-users] best solution to store data

by kilon alios

I really like Fuel , nice design and easy moving data between images, Pharo Grid Computing for the win :) I am sure it will come handy. Also great work with Pharo for The Enterprise this book is growing and growing and growing will eventual turn into a encyclopedia for pharo :) On Tue, Sep 2, 2014 at 7:45 PM, stepharo <stepharo(a)free.fr> wrote: > Have a look at the PharoForTheEntreprise chapter (I'm in the high speed > train - no internet connection). > And there is also the web site of Fuel on rmod. > > Stef > > > On 2/9/14 14:01, Roelof Wobben wrote: > > Thanks all. > > Is there a good tutorial how I can work with Fuel ? > > Roelof > > > > stepharo schreef op 2-9-2014 12:31: > > > On 2/9/14 09:11, FranÃ§ois Stephany wrote: > > If you don't want a separate DB, object serialization with Fuel is an > option. It's very easy to serialize a graph of objects to disk. > You can also have a look at SandstoneDB, it's pretty small and some > people use it. > > pay attention that images can get corrupted so I would in addition use a > file based approach (STON or whatever). > > > Cheers, > Francois > > > On Tue, Sep 2, 2014 at 8:17 AM, Roelof Wobben <r.wobben(a)home.nl> wrote: > >> Hello, >> >> I want to try to make a financial app for a organisation. >> >> There are some 50 customers so also 50 invoices a year. >> Then the payments . Also 50 a year. >> >> Cash and bank accounts . Every month some 10 - 20 things. >> >> So on my disk on the programm I now use it costs me some 30 - 50 Kb a >> year. >> >> What are my options for storage of those data. >> >> I could use a database , but I wonder if there are more and better >> options. >> >> Roelof >> >> > > > >

Sept. 3, 2014

Re: [Pharo-users] Moose browsers: Updating an object value from a text pane and from an emergent window

by Tudor Girba

Hi, As I said before, right now, Glamour does not easily the behavior you want, but you can abuse an existing mechanism of capturing changes of a port through a transmission that transforms that value. Here is an example: text := ''. GLMCompositePresentation new wrapper with: [ :wrapper | wrapper show: [ :a | a text ]. wrapper transmit fromOutsidePort: #text; toOutsidePort: #portIDoNotCareAbout; transformed: [ :textComingFromThePresentation | text := textComingFromThePresentation ] ]; openOn: text In this example, we create a transmission that originates in the #text port that will be populated every time you modify something. This transmission sends the value to #portIDoNotCareAbout only to have access to the transformation block where you can do what you want with the textComingFromThePresentation. To check the behavior: - execute the code in a Playground, - type something in the text area that opens, - inspect the text variable ==> you will see that it contains the latest contents from the text editor We should promote this mechanism explicitly in Glamour, but in the meantime it is probably sufficient for your case. Doru On Wed, Sep 3, 2014 at 4:47 AM, Offray Vladimir Luna CÃ¡rdenas < offray(a)riseup.net> wrote: > Hi, > > I'm trying to restate my question to see if I have more luck with any > answer this time. > > I'm making advances with an outliner like app for writing and now I can > add nodes move them and store them in the really nice STON format. But > because information on trees is not editable, I would like to try another > approach: To create an emergent window and put the node tree and node tags > on it, and the update the this values on the tree node. > Also, I would like to update some objects from the a Glamour text pane, > without any special button or action, just while I'm writing on them. If > this is not possible which is the message to select all text in a body > panel and to send it to a object? > > I will be doing some further advances by my own and keep you posted (may > be with some more specific/better questions on how to get this behaviour > from Moose browsers). > > Cheers, > > Offray > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 3, 2014

Re: [Pharo-users] Tide installation

by stepharo

On 3/9/14 11:08, Bernat Romagosa wrote: > Hi Stef, > > I got Tide working alright, the only thing that's a bit off is the > part of the installation steps where it says you have to use a > particular bower version. I can issue a pull request for readme.md > <http://readme.md> correcting this part if you want. Please this is important to remove any little glitches :) > Then I tried Marina and the instructions were bright and clear! Nice > piece of software. There are some things that are not working for me > (paths for elements with spaces in the title, for instance), but > overall it looks like a great example of what you can do with Tide. Nicolas, Esteban and Damien did a good job. I'm checking how I could use it for scripting my web site. I should finish the Mustache chapter too. > Cheers! > Bernat. > > p.s. I watched the video and things are a bit clearer to me now, > although text is a bit hard to read. Yes the videos should have shoot the slides :( > Are the slides shared somewhere? Yes on slideshare > > > 2014-09-03 10:47 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > Bernat > > once you get it working could you issue some pull requests so that > I integrate the changes (if I have right access). > > Stef > > > On 2/9/14 17:05, Bernat Romagosa wrote: >> Hi list! >> >> I wanted to try out Tide, and I'm following the steps at: >> https://github.com/tide-framework/tide >> >> However, I can't get through the bower install step. Here's the >> output: >> >> >> bower amber#0efe3ad09 not-cached >> git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> <http://github.com/amber-smalltalk/amber.git#0efe3ad09> >> bower amber#0efe3ad09 resolve >> git://github.com/amber-smalltalk/amber.git#0efe3ad09 >> <http://github.com/amber-smalltalk/amber.git#0efe3ad09> >> bower amber#0efe3ad09 ENORESTARGET Tag/branch 0efe3ad09 >> does not exist >> Additional error details: >> Available tags: 0.10, 0.10.0, 0.11.0, 0.12.0, 0.12.1, 0.12.2, >> 0.12.3, 0.12.4, 0.12.6, 0.13.0-alpha.1, 0.13.0-alpha.2, 0.9, >> 0.9.1, legacy, legacy2, legacy3-iife >> Available branches: 0.13-prereleases, camillo-hacks, >> chromeos, gh-pages, master, moka, nemo, nw-helios-app, >> stable, website-deployment >> >> >> >> I changed 0efe3ad09 for stable in bower.json and it failed with: >> >> >> bower amber#stable not-cached >> git://github.com/amber-smalltalk/amber.git#stable >> <http://github.com/amber-smalltalk/amber.git#stable> >> bower amber#stable resolve >> git://github.com/amber-smalltalk/amber.git#stable >> <http://github.com/amber-smalltalk/amber.git#stable> >> bower amber#stable checkout stable >> bower amber#stable error Arguments to path.join >> must be strings >> Stack trace: >> TypeError: Arguments to path.join must be strings >> at path.js:360:15 >> at Array.filter (native) >> at Object.exports.join (path.js:358:36) >> at GitHubResolver.GitResolver._cleanup >> (/usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:182:26) >> at >> /usr/local/lib/node_modules/bower/lib/core/resolvers/GitResolver.js:74:25 >> at Promise.apply >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1122:26) >> at Promise.promise.promiseDispatch >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >> at >> /usr/local/lib/node_modules/bower/node_modules/q/q.js:1337:14 >> at flush >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:108:17) >> at process._tickCallback (node.js:415:13) >> Console trace: >> Trace >> at StandardRenderer.error >> (/usr/local/lib/node_modules/bower/lib/renderers/StandardRenderer.js:74:17) >> at Logger.updateNotifier.packageName >> (/usr/local/lib/node_modules/bower/bin/bower:109:18) >> at Logger.EventEmitter.emit (events.js:95:17) >> at Logger.emit >> (/usr/local/lib/node_modules/bower/node_modules/bower-logger/lib/Logger.js:29:39) >> at >> /usr/local/lib/node_modules/bower/lib/commands/install.js:28:16 >> at _rejected >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:808:24) >> at >> /usr/local/lib/node_modules/bower/node_modules/q/q.js:834:30 >> at Promise.when >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:1079:31) >> at Promise.promise.promiseDispatch >> (/usr/local/lib/node_modules/bower/node_modules/q/q.js:752:41) >> at >> /usr/local/lib/node_modules/bower/node_modules/q/q.js:574:44 >> System info: >> Bower version: 1.2.6 >> Node version: 0.10.25 >> OS: Linux 3.11.0-19-generic x64 >> >> >> I'm kind of stuck, any tips? >> >> Thanks! >> >> Bernat. >> >> >> -- >> Bernat Romagosa. > > > > > -- > Bernat Romagosa.

Sept. 3, 2014