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

Re: [Pharo-dev] fuel on pharo 3

by Sebastian Sastre

cool thanks On Jan 4, 2014, at 11:23 AM, Sebastian Sastre <SEBASTIAN(a)FLOWINGCONCEPT.COM> wrote: > How you guys are loading fuel on Pharo 3? > > This isn't getting that done: > > Gofer new > url: 'http://smalltalkhub.com/mc/Pharo/Fuel/main'; > package: 'ConfigurationOfFuel'; > load. > > ((Smalltalk at: #ConfigurationOfFuel) project version: #stable) load. > >

Jan. 4, 2014

Re: [Pharo-dev] fuel on pharo 3

by Esteban Lorenzano

no need toâ¦ is in image :) On 04 Jan 2014, at 14:23, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > How you guys are loading fuel on Pharo 3? > > This isn't getting that done: > > Gofer new > url: 'http://smalltalkhub.com/mc/Pharo/Fuel/main'; > package: 'ConfigurationOfFuel'; > load. > > ((Smalltalk at: #ConfigurationOfFuel) project version: #stable) load. > >

Jan. 4, 2014

Re: [Pharo-dev] fuel on pharo 3

by Marcus Denker

On 04 Jan 2014, at 14:24, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > How you guys are loading fuel on Pharo 3? > Fuel is already in no need to load. > This isn't getting that done: > > Gofer new > url: 'http://smalltalkhub.com/mc/Pharo/Fuel/main'; > package: 'ConfigurationOfFuel'; > load. > > ((Smalltalk at: #ConfigurationOfFuel) project version: #stable) load. > >

Jan. 4, 2014

fuel on pharo 3

by Sebastian Sastre

How you guys are loading fuel on Pharo 3? This isn't getting that done: Gofer new url: 'http://smalltalkhub.com/mc/Pharo/Fuel/main'; package: 'ConfigurationOfFuel'; load. ((Smalltalk at: #ConfigurationOfFuel) project version: #stable) load.

Jan. 4, 2014

Re: [Pharo-dev] SIXX on "large" files

by Sebastian Sastre

Thanks for the tip. AFAIK, STON would be best suited for JSON friendly instances. I need something more general. What I was trying to do with sixx is to dump the airflowing odb's to migrate data so pharo 3 can use it.* The object databases are composed by many kinds of objects, only a few of them are JSON-ish PD: All this is due to the change that happened in DateAndTime #jdn -> #julianDayNumber which is forcing me to either abandon Pharo 3, do horrible hacks to it or stay with older pharo. On Jan 4, 2014, at 7:11 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> SIXX is cool but I'm with the feeling that it's time to give fuel a chance > > Or STON ?

Jan. 4, 2014

Case 12494: Replace usage of TimeStamp with DateAndTime for methods stamps

by Sven Van Caekenberghe

Hi, Can somebody (else) please have a look at https://pharo.fogbugz.com/f/cases/12494 (Replace usage of TimeStamp with DateAndTime for methods stamps) We should finish what we startedâ¦ Sven

Jan. 4, 2014

Re: [Pharo-dev] [Glass] printString and asString

by StÃ©phane Ducasse

> > And number, no? For me as* methods are for conversion between types. E.i. if you have string and want it as Integer you use asInteger. no the point is exactly that :) conversion between polymorphic objects asFloat asInteger asFraction asString asSymbol asByteArray asArray asSet not defined in Object :) > > Uko > >> >> #storeString >> Produces legal Smalltalk source code that when executed will produce an >> equivalent object to the receiver. Needs to be implemented only for >> objects that can be specified as literals in Smalltalk syntax, but could >> probably be implemented for a few other simple objects. >> >> #displayString and so on. >> UI frameworks and applications will need to have their own ways of >> textually representing objects, so will add their own messages such as >> #displayString. The *only* messages that any application or framework >> can depend on *all* objects responding to are those that it defines >> itself, and #printString and #printOn:. >> >> Regards, >> >> -Martin

Jan. 4, 2014

Re: [Pharo-dev] Spotlight Demo

by StÃ©phane Ducasse

I want this widget :) and behavior On 04 Jan 2014, at 02:53, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I love the item count - thanks. I saw the double jump too, but the cause wasn't obvious. And I see what you mean about the arrows; I'll look into it. > > I'm really enjoying the collaboration :) > Cheers, > Sean > > View this message in context: Re: Spotlight Demo > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 4, 2014

Re: [Pharo-dev] SIXX on "large" files

by monty

XML documents cannot contain NULL chars or refs to them (), or certain other Unicode points: http://www.w3.org/TR/REC-xml/#dt-charref http://www.w3.org/TR/REC-xml/#NT-Char If SIXX is encoding NULLs, it is in error. ----- Original Message ----- From: Sven Van Caekenberghe Sent: 01/04/14 04:11 AM To: Pharo Development List Subject: Re: [Pharo-dev] SIXX on "large" files On 04 Jan 2014, at 00:38, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > I've discovered that its part of a JsonObject that holds the facebook profile associated with the user. > > SIXX is cool but I'm with the feeling that it's time to give fuel a chance Or STON ? https://github.com/svenvc/ston/blob/master/ston-paper.md > On Jan 3, 2014, at 8:01 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: > >> On 3 January 2014 20:07, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >>> It's probable unrelated to size as expected. >>> >>> For the record: >>> >>> I've changed the XMLParser and the new one complained about a problem on a >>> specific line that has this content >>> >>> <sixx.object sixx.id="1106" sixx.name="key" sixx.type="String" >>>> name</sixx.object> >>> <sixx.object sixx.id="1107" sixx.name="value" sixx.type="String" >>>> Like >>> Mark >>> Twain: >>>  >>> I've >>> never >>> let >>> my >>> school >>> interfere >>> with >>> my >>> education. >>> </sixx.object> >>> </sixx.object> >>> >>> looks like an encoding problem >> >> Was that originally a UTF-32 string or something? Three NULs followed >> by a character... (For the curious, it says 'Like Mark Twain: "I've >> never let my school interfere with my education. "') >> >> frank >> > >

Jan. 4, 2014

Re: [Pharo-dev] [Pharo-users] Help us to have really cool Pharo 3 release!

by StÃ©phane Ducasse

On 04 Jan 2014, at 11:17, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi guys, > > As you know, we are now in beta for Pharo 3. > That means we are just fixing bugs and improving stability (they are some attempts from some very impatient people to add yet new features, but so far we are managing them with the ability of a goal keeper :) ) nice metaphor! It made me think about maradona :) So from argentinian it means that we can also play football with our hands o:) > What we need now is your help! How? > > 1) Is NOW the moment of porting your projects to Pharo 3. Yesâ¦ is not stable, but it improves everyday and if you help us catching bugs, it will in march, when the release should happen) > 2) Report BUGS. Yepâ¦ we still have many of them. Best way to report a bug is: to add a bug entry and to open a discussion in dev mailing list. Just one of both does not works fine because we are in the run, and: if you just open the bug, we can miss his importance, if you just start a thread, we are for sure owing to be covered of work and we will forget your important change. . > 3) If you feel in the mood, you can fix some of your annoying bugs by yourself. With the introduction of Komitter (thanks Ben!) you donât even need to work in a separate imageâ¦ it can be fixed in your working image and you can send a SLICE with just the changes you want. > 4) or you can just help us reviewing fixes (usually in status âFix Reviewed By The Monkeyâ, they need to be moved to âFix To Includeâ, and that in some cases (when is UI related, for instance) requires human intervention. > > Donât wait until tomorrow! > Pharo needs you TODAY! super! > > cheers, > Esteban

Jan. 4, 2014