Re: [Pharo-users] About DuneSt / ChartJs
Le mar. 11 févr. 2020 à 17:07, Sven Van Caekenberghe a
écrit :
> Hi,
>
> I am trying to use DuneSt / ChartJs [ https://github.com/DuneSt/ChartJs ]
> and it looks good. Thanks for another nice library.
>
You're welcome and we are pleased that you use it :-)
>
> My first question is about loading the code. I would like to load the
> minimum possible. I guess the stylesheet code is needed, but not the prism
> code ?
>
You are totally right, Prism is required by the demo to display the code.
You will not load it by using the 'core' group
>
> NeoJSON and Seaside are already in my project's dependencies, but Seaside3
> seems to never resolve to the same thing, so I would like to skip that. Is
> that possible ? I have this issue often with Seaside. I could fork and edit
> the baseline, but I'd rather not.
>
I have the same opinion, if you have a solution to manage it in a nice way
i would be pleased to add it. I only see as a solution to create a group
that do not load Seaside3 but maybe Cyril know a better way to do it (he is
far better than me about baselines)
>
> I got a Bar chart on 2D data running right away.
>
> But how can I use 'horizontalBar' as type ?
>
> var myBarChart = new Chart(ctx, {
> type: 'horizontalBar',
> data: data,
> options: options
> });
>
> I see that the types are encoded a classes, but the list seems rather
> limited.
>
We implemented the minimum that is required for us. It is really easy to
add new ones as you already discovered. I will add these as soon as
possible or if you already did it, create a pull request. There is many
improvement that can be done in this project and it would be great to have
your contribution about it.
We will move to the new version of the ChartJs library when we will have
time to improve it. Of course the API of our project will stay the same and
changes will not impact your project.
>
> Thx,
>
> Sven
>
>
>
--
*Guillaume Larcheveque*
Re: [Pharo-users] is PetitParser eager by default?
Yes, the #any asParser star consume all your stream. for your example you can do: str := 'a0b'. #digit asParser negate star, #digit asParser, #any asParser star parse: str. 2017-01-20 15:24 GMT+01:00 Peter Uhnak : > Is PetitParser eager by default? > > I've used PetitParser countless times so I am really baffled why this > doesn't work > > str := 'a0b'. > #any asParser star, #digit asParser, #any asParser star parse: str. > > -> PPFailure (input expected at: 3) > > > Thanks, > Peter > > -- *Guillaume Larcheveque*
Re: [Pharo-users] Dues anybody try Artifact with non latin characters?
I forwarded the conversation to Olivier. Embed fonts are not yet implemented by Artefact so we will see with Olivier if we will join the development of it (if you plan to do it) or if we will just help you by answering your questions if we do not have time to code it. 2016-11-12 12:07 GMT+01:00 Sabine Manaa : > lets wait what Olivier or Guillaume say > > 2016-11-12 11:28 GMT+01:00 Denis Kudriashov [via Smalltalk] <[hidden > email] <http:///user/SendEmail.jtp?type=node&node=4922788&i=0>>: > >> >> 2016-11-11 21:07 GMT+01:00 Sabine Manaa <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4922787&i=0>>: >> >>> Hi Denis, >>> >>> perhaps this is the same topic (I am not sure): >>> http://forum.world.st/Artefact-and-WideString-td4857147.html#a4857325 >>> >> >> Thank's Sabine. But it is not helps. And google too. It seems that I need >> embed fonts which is not implemented by Artifact. >> >> >> -- >> If you reply to this email, your message will be added to the discussion >> below: >> http://forum.world.st/Dues-anybody-try-Artifact-with-non-lat >> in-characters-tp4922747p4922787.html >> To start a new topic under Pharo Smalltalk Users, email [hidden email] >> <http:///user/SendEmail.jtp?type=node&node=4922788&i=1> >> To unsubscribe from Pharo Smalltalk Users, click here. >> NAML >> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > > > -- > View this message in context: Re: Dues anybody try Artifact with non > latin characters? > <http://forum.world.st/Dues-anybody-try-Artifact-with-non-latin-characters-tp4922747p4922788.html> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. > -- *Guillaume Larcheveque*
Re: [Pharo-users] [Pharo-dev] websockets in pharo?
Yes and it works very well!! (I'm using it for Telescope) There is a chapter in the pharo for enterprise book about websockets 2016-08-24 14:28 GMT+02:00 Pavel Krivanek : > Zinc-WebSocket-* packages in the repository http://mc.stfx.eu/ > ZincHTTPComponents > > -- Pavel > > 2016-08-24 14:20 GMT+02:00 Tudor Girba : > >> Hi, >> >> Can anyone tell me if there is a Websocket implementation for Pharo? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "From an abstract enough point of view, any two things are similar." >> >> >> >> >> >> > -- *Guillaume Larcheveque*
Re: [Pharo-users] How to execute code when after loading a package
you can also define your code in a class in the #initialize method (class side) 2015-08-24 17:21 GMT+02:00 Mariano Martinez Peck : > I know there was/is a way in Monticello itself, but I think it was never > widely used. I think most common solution is to use #postLoadDoIt: at > different levels (packages, groups, whole project, etc) of Metacello. But > yeah, you need a Metacello conf for that. > > On Thu, Aug 20, 2015 at 4:11 PM, Julien Delplanque > wrote: > >> Hi all, >> >> I have a package for which I need to execute some code after it is loaded >> in an image. >> >> This package have no dependency so I don't know if it is possible to do >> it without using a baseline but I guess it's not. >> >> Thanks, >> >> Julien >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- *Guillaume Larcheveque*
Re: [Pharo-users] Users of Versionner?
I'm using it for Artefact, Telescope and all Synectique's projects 2015-03-18 14:40 GMT+01:00 Johan Fabry : > > I rarely have the need for making or updating configurations. When I do, I > use it, but only in the most simple way. I still have not figured out > completely how it works but it easily beats coding all of this by hand! > > > On Mar 18, 2015, at 05:46, Stephan Eggermont wrote: > > > > Who is actually using Versionner to maintain configurations? > > Especially configurations that are used in other configurations? > > > > Stephan > > > > > > > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > -- *Guillaume Larcheveque*
Re: [Pharo-users] PetitParser problem with plus
So you just have to remove the #star in notA or replace it by #plus to makes it succeed only when it consume at least one character 2014-12-18 7:54 GMT+01:00 Guillaume Larcheveque < guillaume.larcheve...@gmail.com>: > > With x, x it will only go to 2 level deep. > > With the plus you allow to go as far as the x rule succeed and your x rule > always succeed because notA always succeed due to the star without > consuming anything so you fall into infinite loop. > > 2014-12-18 6:47 GMT+01:00 James Foster : >> >> There is something about plus that I don’t understand. In the following >> code if I parse for (x , x) then I get what I expect. If I parse for (x >> plus) then the image hangs. What am I doing wrong? >> >> James >> >> | a notA x y | >> a := $a asParser. >> notA := $a asParser negate star flatten. >> x := a / notA. >> y := x , x. “works fine” >> y := x plus. “never finishes” >> ^y end parse: 'ab’. >> >> >> > > -- > *Guillaume Larcheveque* > > -- *Guillaume Larcheveque*
Re: [Pharo-users] PetitParser problem with plus
With x, x it will only go to 2 level deep. With the plus you allow to go as far as the x rule succeed and your x rule always succeed because notA always succeed due to the star without consuming anything so you fall into infinite loop. 2014-12-18 6:47 GMT+01:00 James Foster : > > There is something about plus that I don’t understand. In the following > code if I parse for (x , x) then I get what I expect. If I parse for (x > plus) then the image hangs. What am I doing wrong? > > James > > | a notA x y | > a := $a asParser. > notA := $a asParser negate star flatten. > x := a / notA. > y := x , x. “works fine” > y := x plus. “never finishes” > ^y end parse: 'ab’. > > > -- *Guillaume Larcheveque*
Re: [Pharo-users] [ANN] BabyMock 2
I think you can have your mock send an exception by using #answers:aBlock and signal the exception in the block 2014-04-08 15:58 GMT+02:00 Christophe Demarey : > Hello, > > Thanks. Very nice library! > > I have a question: is it possible to expect a method to throw an Exception? > > I would like something like: > protocol describe > once: mock recv: #aMethod ; > signal: anError. > I did not find anything in the documentation. > > I don't want to test that the mock signals an error but I want to test a > code that needs to take into account an exception. > > Best regards, > Christophe. > > Le 11 mars 2014 à 12:30, Attila Magyar a écrit : > > > I'm pleased to announce the 2.0 version of BabyMock. BabyMock is a visual > > mock object library that supports test-driven development. > > > > This version has a new syntax which is incompatible with the old version. > > Therefore it has a new repository > > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > > (BabyMock 1 is still available at its old location, but in the future > I'd to > > focus on the development of BabyMock2, so don't expect too many changes > > regarding the old version). > > > > Changes in 2.0 > > > > - A new, extensible DSL (no more should/can) > > - Improved error messages, history of messages, detailed information > about > > argument mismatches > > - An improved, Spec based GUI > > - Clicking on a mock opens an inspector on the expectations > > - Clicking on a message opens an inspector on the message > > - Object methods can be mocked by defaults > > - Blocks can be executed after receiving a message by the mock. The block > > has access to the arguments of the incoming message. > > - Any argument matcher > > - Cleanups and simplifications in the code > > > > I hope you don't mind the changes regarding the syntax. Personally I > think > > it has lot more pros than cons. > > > > More information > > > > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > > > > p.s. > > It needs Pharo3.0. > > > > Attila > > > > > > > > -- > > View this message in context: > http://forum.world.st/ANN-BabyMock-2-tp4748530.html > > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > -- *Guillaume Larcheveque*
Re: [Pharo-users] JPEG support in Artifact
If I remember well, we used this way to get some data about image required by PDF format. Maybe there is a smarter way to do this, I will have a look with Olivier about this. 2014-04-03 10:32 GMT+02:00 Stephan Eggermont : > Reg Krock took a look at how difficult it would be to port Artefact to > Gemstone. > He found that JPEG support uses a plugin based reader/writer, and seems to > render the JPEG using BitBlt and Form. > > Why are JPEGs rendered? I'd think embedding them should be enough > (and be better for speed and image quality) > > Stephan > -- *Guillaume Larcheveque*
Re: [Pharo-users] [ANN] BabyMock 2
Cool!!! I use BabyMock a lot and I'm curious to see the new DSL. Thanks a lot for your work. 2014-03-11 12:30 GMT+01:00 Attila Magyar : > I'm pleased to announce the 2.0 version of BabyMock. BabyMock is a visual > mock object library that supports test-driven development. > > This version has a new syntax which is incompatible with the old version. > Therefore it has a new repository > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > (BabyMock 1 is still available at its old location, but in the future I'd > to > focus on the development of BabyMock2, so don't expect too many changes > regarding the old version). > > Changes in 2.0 > > - A new, extensible DSL (no more should/can) > - Improved error messages, history of messages, detailed information about > argument mismatches > - An improved, Spec based GUI > - Clicking on a mock opens an inspector on the expectations > - Clicking on a message opens an inspector on the message > - Object methods can be mocked by defaults > - Blocks can be executed after receiving a message by the mock. The block > has access to the arguments of the incoming message. > - Any argument matcher > - Cleanups and simplifications in the code > > I hope you don't mind the changes regarding the syntax. Personally I think > it has lot more pros than cons. > > More information > > http://smalltalkhub.com/#!/~zeroflag/BabyMock2 > > p.s. > It needs Pharo3.0. > > Attila > > > > -- > View this message in context: > http://forum.world.st/ANN-BabyMock-2-tp4748530.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- *Guillaume Larcheveque*
