February 2013 - Pharo-users

Re: [Pharo-users] ZnUrl: Add multiple segment string

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > I am guessing you are lazy and want to type as little as possible You know me too well ;) Sven Van Caekenberghe-2 wrote > 'http://endpoint.service.com:9090/v1' asZnUrl > withPathSegments: '/foo/bar/resource.txt' asZnUrl pathSegments. I like this one the best for now, as I didn't want to break up the string, to make it easier to change. Sven Van Caekenberghe-2 wrote > > 'http://endpoint.service.com:9090/v1' asZnUrl > withPathSegments: #(foo bar 'resource.txt'). How about a double dispatch under the covers of withPathSegments:, which does the current behavior for OrderedCollection; and for String, do something like "self findTokens: '/'." and pass that as the argument to withPathSegments:? -- View this message in context: http://forum.world.st/ZnUrl-Add-multiple-segment-string-tp4672728p4672815.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 28, 2013

Re: [Pharo-users] ZnUrl: Add multiple segment string

by Sven Van Caekenberghe

Hi Sean, On 28 Feb 2013, at 16:08, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > What's the best way to do the following (non-working): > aZnUrl / 'path/segment/string'. > > Ways I thought of: > - Ugly: (url asString, 'path/segment/string') asZnUrl. > - Non-working: #addPathSegment: > - Tedious: url / 'path' / 'segment' / 'string' > > It seems like a common-enough thing to do, but I couldn't find a way that I > liked... > > Thanks, > Sean I am guessing you are lazy and want to type as little as possible, then the following are possible: 'http://endpoint.service.com:9090/v1' asZnUrl withPathSegments: '/foo/bar/resource.txt' asZnUrl pathSegments. 'http://endpoint.service.com:9090/v1' asZnUrl / #foo / #bar / 'resource.txt'. 'http://endpoint.service.com:9090/v1' asZnUrl withPathSegments: #(foo bar 'resource.txt'). There is an important difference between the internal and external representation of URL elements, #asZnUrl actually parses: 'http://endpoint.service.com:9090/v1' asZnUrl withPathSegments: '/foo%20bar' asZnUrl pathSegments. 'http://endpoint.service.com:9090/v1' asZnUrl / 'foo bar'. ZnUrl is not a general URL construction packages, the #/ #? and #? that I added for you help a bit, but they are limited. There is also #inContextOf: '/foo/bar/resource.txt' asZnUrl inContextOf: 'http://endpoint.service.com:9090/v1' asZnUrl but that does not merge paths (the v1 part is gone in the last expression). Maybe we could think about an algorithm or semantics to do path merging. Regards, Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Feb. 28, 2013

ZnUrl: Add multiple segment string

by Sean P. DeNigris

What's the best way to do the following (non-working): aZnUrl / 'path/segment/string'. Ways I thought of: - Ugly: (url asString, 'path/segment/string') asZnUrl. - Non-working: #addPathSegment: - Tedious: url / 'path' / 'segment' / 'string' It seems like a common-enough thing to do, but I couldn't find a way that I liked... Thanks, Sean -- View this message in context: http://forum.world.st/ZnUrl-Add-multiple-segment-string-tp4672728.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 28, 2013

Re: [Pharo-users] Aida 6.5 loading in Pharo 2.0!

by stephane ducasse

cool ;) > Sven wrote: >> It would also be quite useful if the CB knew if a config was present and/or loaded > > I started with a new implementation based on spec: > > https://code.google.com/p/pharo/issues/detail?id=7533 > > It displays an icon when the ConfigurationOfXXX is loaded. > > Feel free to help! thanks for helping :) Stef

Feb. 28, 2013

Re: [Pharo-users] datepicker question

by Sabine KnÃ¶fel

ahhh sorry, I sent this message to the pharo list and not to the seaside list. I will send it to the seaside list. Sabine -- View this message in context: http://forum.world.st/datepicker-question-tp4672653p4672654.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 28, 2013

datepicker question

by Sabine KnÃ¶fel

Hi, I use datepicker like this: html textInput value: Date today; callback: [ :value | self date: value ] ; script: (( html jQuery new datepicker) onSelect: html jQuery ajax serializeThis). In case of selecting the date within the datepicker popup (click at a date), it works fine ("self date:" is sent). But if I change the date within the textInput field, without using the datepicker popup, the callback is not fired. How can I set the date: also in case that the user types in the date in the text field? Sabine -- View this message in context: http://forum.world.st/datepicker-question-tp4672653.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 28, 2013

Re: [Pharo-users] Aida 6.5 loading in Pharo 2.0!

by Ben Coman

Torsten Bergmann wrote: >> And I thought 'Untrusted' was going to be renamed 'Community Supported' >> or some such. Did that decision get changed or just slide through the >> cracks? >> > > No "Community supported" sounds like you get something "supported" and working, > but some of them are outdated and even do not contain a #stable definition. > > This "Untrusted" is just a convenience to easily load from the common > http://squeaksource.com/MetacelloRepository/ > and check if they are working. Esteban added it. > > A ConfigurationOfXXX (either in MetacelloRepository or in your own project repo): > - if known to work in Pharo 2.0 it should be copied also to ss3.gemstone.com/ss/MetaRepoForPharo20 > - if known to work in Pharo 1.4 it should be copied also to http://squeaksource.com/MetaRepoForPharo14 > > So the first tab in configuration browser contains the ones that > have been (currently manually) verified to work in the Pharo version you have in front of you > and the ones on the second "untrusted" tab may or may not work in Pharo 2.0. > Maybe we should remove the second tab before release. > > Bye > T. > > > I had made some suggestions a while ago but I had misunderstood the situation. I would now propose tabs named "Verified" and "Unverified". More positive than "Untrusted" while remaining neutral on who supports it, but hinting that the aim is for configurations to move from one state to the other. I think keeping the second tab in the release is useful for several reasons: * the degree to which an old-configuration is broken will vary between packages. * jumpstarts users of varying skill to assist with getting packages verified * continues to promote packages for which effort had been put in previously to verify on past Pharo releases - and hints for newcomers that the package could be loaded on previous version to see it working. cheers -ben

Feb. 28, 2013

Re: [Pharo-users] Aida 6.5 loading in Pharo 2.0!

by stephane ducasse

Phil I started to migrate the projects I will maintain to PharoExtras. If other people maintain other projects then they can host them there. I will try to create a jenkins job for each of the project but it means quite some boring tasks - creating configuration - testing them - creating jnkins job. I will do it but it will take some time. Kind of a long effort but I think it is important to do it. Stef > Yes, I positively hate the 'Untrusted' word. > > Weren't we talkin about extras/contrib and stuff? Isn't that the right > terminology to align with that tab? > > Another question: Why can't we put those things in Smalltalkhub as well? > > Phil > > 2013/2/27 Igor Stasenko <siguctua(a)gmail.com>: >> On 27 February 2013 17:28, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> On 27 Feb 2013, at 17:07, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >>> >>>> And I thought 'Untrusted' was going to be renamed 'Community Supported' >>>> or some such. Did that decision get changed or just slide through the >>>> cracks? >>> >>> Yes, I think that should be done, untrusted is a bit negative. >>> >> +1 >> >> perhaps author meant 'Unofficial', because untrusted is really scary :) >> >> but i think 'Community Supported' is most precise. >> >>> The configuration browser is also too minimal right now, and a bit confusing. >>> >>> We should try to come up with more user friendly phrases on the menu. >>> >>> It would also be quite useful if the CB knew if a config was present and/or loaded. >>> >>> A way to browse the config code would also be welcome. >>> >>>> On 02/27/2013 08:00 AM, Torsten Bergmann wrote: >>>>> Janko wrote: >>>>>> One-click load of Aida from Configuration Browser is now possibl >>>>> >>>>> >>>>> We manually make a copy of configs that are know to work for a specific >>>>> Pharo version into a specific "/MetaRepoForPharoXX". This will be automated in the future >>>>> with automatic validation, etc. >>>>> >>>>> So if Aida is really working in Pharo 2.0 then please make a copy of the sepcific >>>>> ConfigurationOfAida mcz into ss3.gemstone.com/ss/MetaRepoForPharo20 >>>>> using the "Copy" button of the Monticello repo browser. >>>>> >>>>> This way it will appear in "Configurations" tab in configuration browser >>>>> (containing the configs that are know to work). >>>>> >>>>> Currently Aidi is only in "Untrusted" since this is the repo for all configs >>>>> (squeaksource.com/MetacelloRepository) >>>>> >>>>> >>>>> I also think it would be nice if you also >>>>> >>>>> - add a beginners workspace with "SwazooAida start." >>>>> You can use >>>>> >>>>> spec postLoadDoIt: #postloadForCore:package: >>>>> >>>>> with >>>>> postloadForCore: loader package: packageSpec >>>>> >>>>> Workspace openContents: 'SwazooAida start.' >>>>> >>>>> - or you add a menu entry and server start panel, have a look at ConfigurationOfPharoOnlineHelp for an example >>>>> >>>>> This way even a complete beginner can easily start just by >>>>> loading Aida using the config browser in 2.0 and then "jump start" into the browser. >>>>> >>>>> Bye >>>>> T. >>>>> >>>> >>>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> >> >

Feb. 27, 2013

Re: [Pharo-users] Is this possible with XMLWriter?

by stephane ducasse

The videos is nice Thanks. Alexandre told me to merge XMLParser and pastell but I will probably migrate the two projects nicely. Stef > Using XMLWriter writer directly is stream based and will not help you here. > > > In Pharo 2.0 load "Pastell" (ConfigurationOfPastell) from the config browser. > It also loads ConfigurationOfXMLSupport as a single dependency. > > > This "XMLSupport" package is usually used for parsing XML and with "Pastell" > you can easily access nodes like in XPath > see http://www.youtube.com/watch?v=6fUtdQ0-5yA for a pastell video > > > Havent tried but with "XMLSupport" I'm sure you can also manually instantiate/connect/build the > nodes and document, manipulate the object tree and write out the contents as XML file later. > > At least there are methods like #writeXMLOn: aWriter in classes like XMLDocument > XMLNodeWithChildren, ... > > Bye > T. > > > >

Feb. 27, 2013

Re: [Pharo-users] Aida 6.5 loading in Pharo 2.0!

by stephane ducasse

Hi Paul Not really, we are just running after bugs and trying to squeeze them. Esteban is pushing the release like a bull. Igor is trying to find a find to reproduce a bug trashing the vm notably randomly on network access. Really not fun. After the bug on the become: And igor is looking at Delay startUp code with morbid ideas. Reading Delay startup and startEventloop initialization code gets dizzy. I think that Igor will rewrite all the code for 3.0 because it looks that they are many ways to get wrong there. Stef On Feb 27, 2013, at 5:07 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > And I thought 'Untrusted' was going to be renamed 'Community Supported' > or some such. Did that decision get changed or just slide through the > cracks? > > > On 02/27/2013 08:00 AM, Torsten Bergmann wrote: >> Janko wrote: >>> One-click load of Aida from Configuration Browser is now possibl >> >> >> We manually make a copy of configs that are know to work for a specific >> Pharo version into a specific "/MetaRepoForPharoXX". This will be automated in the future >> with automatic validation, etc. >> >> So if Aida is really working in Pharo 2.0 then please make a copy of the sepcific >> ConfigurationOfAida mcz into ss3.gemstone.com/ss/MetaRepoForPharo20 >> using the "Copy" button of the Monticello repo browser. >> >> This way it will appear in "Configurations" tab in configuration browser >> (containing the configs that are know to work). >> >> Currently Aidi is only in "Untrusted" since this is the repo for all configs >> (squeaksource.com/MetacelloRepository) >> >> >> I also think it would be nice if you also >> >> - add a beginners workspace with "SwazooAida start." >> You can use >> >> spec postLoadDoIt: #postloadForCore:package: >> >> with >> postloadForCore: loader package: packageSpec >> >> Workspace openContents: 'SwazooAida start.' >> >> - or you add a menu entry and server start panel, have a look at ConfigurationOfPharoOnlineHelp for an example >> >> This way even a complete beginner can easily start just by >> loading Aida using the config browser in 2.0 and then "jump start" into the browser. >> >> Bye >> T. >> > >

Feb. 27, 2013