March 2017 - Pharo-users - lists.pharo.org

[ANN] MaterialDesignLite for Seaside v1.1.0

by Cyril Ferlicot D.

Hello everyone, Today I released the version v1.1.0 of MaterialDesignLite for Seaside. (https://github.com/DuneSt/MaterialDesignLite) Since this is a minor version it shouldn't break anything existing, but nobody can avoid bugs. If you encounter a regression, feel free to open an issue and I'll try to commit a hotfix soon. Thanks to Philippe Back, Paul Debruicker, Sabine Mana, Tobias Pape, Guillaume Larcheveque and Yann Lesage for the contributions and the feedback. Also thanks to everyone using this project. You can now find an image with the project on pharo-contribution's Jenkins and on PharoLauncher. (https://ci.inria.fr/pharo-contribution/job/MaterialDesignLite) You can find more detail on the README.md to start with the project. One of the future goal would be to add Functional tests with Parasol. Here is the changelog. You can find a more readable version at: https://github.com/DuneSt/MaterialDesignLite/blob/v1.1.0/CHANGELOG.md # [v1.1.0](https://github.com/DuneSt/MaterialDesignLite/compare/v1.0.2...v1.1.… (2017-03-22) ## Bug Fixes * **SelectWidget: Do not upgrade the dom at all node insertion** ([59c2534](https://github.com/DuneSt/MaterialDesignLite/commit/59c2534)) * **MDLDialog>>openButtonId: missing .close eventListener** ([262e6f3](https://github.com/DuneSt/MaterialDesignLite/commit/262e6f3)) * **Chips: Use #ensureId rather than overriding #id & #id:** ([40fcca5](https://github.com/DuneSt/MaterialDesignLite/commit/40fcca5)) * **SortableTable: Visible page might end up out of bounds** ([b1833e8](https://github.com/DuneSt/MaterialDesignLite/commit/b1833e8)) * **NestedList: Tooltips are unusable** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) ## Features * **Anchors as buttons** This add the possibility to have links with the style of buttons to not break semantic ([ba3f0f7](https://github.com/DuneSt/MaterialDesignLite/commit/ba3f0f7)) * **Sliders: New features** This add a label with MD style, possibility to add an icon, possibility to add an output, show the bounds and a demo ([b203a1f](https://github.com/DuneSt/MaterialDesignLite/commit/b203a1f)) * **Dialog: Multiple opening buttons for a dialog** ([209d49a](https://github.com/DuneSt/MaterialDesignLite/commit/209d49a)) * **SelectWidget: Allow to customize the field** ([ace3e31](https://github.com/DuneSt/MaterialDesignLite/commit/ace3e31)) * **SelectWidget: Add tooltips on entries** ([14466d2](https://github.com/DuneSt/MaterialDesignLite/commit/14466d2)) * **SortableTable: Allow to have no pagination** ([aaa6c19](https://github.com/DuneSt/MaterialDesignLite/commit/aaa6c19)) * **SortableTable: Allow to personalize the style** ([69284d7](https://github.com/DuneSt/MaterialDesignLite/commit/69284d7)) * **NestedList: Add way to customize style + add some default styles** ([5f5088c](https://github.com/DuneSt/MaterialDesignLite/commit/5f5088c)) * **NestedList: Ajax actions on clic** ([feaba43](https://github.com/DuneSt/MaterialDesignLite/commit/feaba43)) * **NestedList: possibility to customize an entry** ([9421917](https://github.com/DuneSt/MaterialDesignLite/commit/9421917)) * **NestedList: Possibility to have an icon to the right of the list** ([27fa1fa](https://github.com/DuneSt/MaterialDesignLite/commit/27fa1fa)) * **NestedList: Add a filter** ([9ecffad](https://github.com/DuneSt/MaterialDesignLite/commit/9ecffad)) * **NestedList: Dynamically load children** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) * **NestedList: Search and loading should add a spinner while executing** ([5ef2a08](https://github.com/DuneSt/MaterialDesignLite/commit/5ef2a08)) * **Tooltip: API should let choose the position of the tooltip** ([de33e68](https://github.com/DuneSt/MaterialDesignLite/commit/de33e68)) ## Cleaning * **Dialogs** Clean javascript ([262e6f3]https://github.com/DuneSt/MaterialDesignLite/commit/262e6f3)) * **NestedList** Extract the javascript into a file and use dataset instead of ids ([21c0535](https://github.com/DuneSt/MaterialDesignLite/commit/21c0535)) * **Extract Material Colors in another project** New repositories to get only the MDLColors: [https://github.com/DuneSt/MaterialColors](https://github.com/DuneSt/Materia… ([2efac41](https://github.com/DuneSt/MaterialDesignLite/commit/2efac41)) * **Improve Chips loading scripts** ([b366ddd](https://github.com/DuneSt/MaterialDesignLite/commit/b366ddd)) ## Infrastructure * **Travis and Appveyor CI** ([1afa628](https://github.com/DuneSt/MaterialDesignLite/commit/1afa628)) ## Compatibility ### Squeak * **`MDColor` has a lowercase class variable** ([888fb39](https://github.com/DuneSt/MaterialDesignLite/commit/888fb39)) ### Gemstone * **Use string in baseline and remove #asString** ([868f71b](https://github.com/DuneSt/MaterialDesignLite/commit/868f71b)) -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

March 22, 2017

Re: [Pharo-users] UI with Spec, how to get mouse events ?

by Daniel BLANC

Hi Nicolai, Thanks for the explanation. It gave me the idea to search for the senders of #action, and I found the MorphicImageAdapter. It looks like I won't be able to get the mouse position from within the action block of the image model. I'll try to achieve this another way, may be with Morphic. Daniel On Tue, Mar 21, 2017 at 11:19 PM Nicolai Hess <nicolaihess(a)gmail.com> wrote: 2017-03-21 20:21 GMT+01:00 Daniel BLANC <daniel.blanc(a)gmail.com>: Hi all, I'm building a Spec UI with an ImageModel and a LabelModel. The image is a map, and the label should display the mouse coordinates when the mouse cursor is on the map. I'm a newcomer to Pharo and Smalltalk, I've searched in the pharo image, and looked into events, on:send:to: message, but I don't know how to properly use them with Spec. For testing purpose I've tried just to get a mouse click with this: MyStuff >> initializeWidgets map := self newImage. mousePos := self newLabel. map on: #click send: #mouseClicked to: self But that doesn't work. Any idea how I can do this ? Thanks, Daniel Hi Daniel, I am afraid, mouse move events aren't catched by the image, and therfore you can not use the image model to listen for the mouse position changes. The above code for mouse click events does not work, because the click event is only send to the widget (a ImageMorph) but not to the model. But the model registers itself for the click event when the widget is build. If a click even is send on the image morph, the model calls #value on its action property, just set an apropiate block as action for your ImageModel an example: im := ImageModel new. im image: PolymorphSystemSettings pharoLogoForm. im action:[ActiveHand inspect]. im openWithSpec. clicking on the image will open an inspector with the active hand.

March 22, 2017

UK Smalltalk User Group meeting - Monday, March 27th

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group Meeting will be on Monday, March 27th. We'll meet at our usual venue The Counting House ( http://www.the-counting-house.com/) at 7pm. If you'd like to join us, you can just show up at the pub. You can also sign up in advance at the meeting's Meetup page: https://www.meetup.com/UKSTUG/events/236496721/ <https://www.meetup.com/UKSTUG/events/236496720/> . See you there!

March 22, 2017

Re: [Pharo-users] Magritte extension

by Ben Coman

On Wed, Mar 22, 2017 at 4:35 AM, DiegoLont <diego.lont(a)delware.nl> wrote: > It has been a while that I was really involved in developing on (QC)Magritte > and doing stuff on the web ... btw, what does the "QC" represent? cheers -ben

March 21, 2017

Re: [Pharo-users] UI with Spec, how to get mouse events ?

by Nicolai Hess

2017-03-21 20:21 GMT+01:00 Daniel BLANC <daniel.blanc(a)gmail.com>: > Hi all, > > I'm building a Spec UI with an ImageModel and a LabelModel. The image is a > map, and the label should display the mouse coordinates when the mouse > cursor is on the map. > > I'm a newcomer to Pharo and Smalltalk, I've searched in the pharo image, > and looked into events, on:send:to: message, but I don't know how to > properly use them with Spec. > > For testing purpose I've tried just to get a mouse click with this: > > MyStuff >> initializeWidgets > map := self newImage. > mousePos := self newLabel. > map on: #click send: #mouseClicked to: self > > But that doesn't work. Any idea how I can do this ? > > Thanks, > Daniel > Hi Daniel, I am afraid, mouse move events aren't catched by the image, and therfore you can not use the image model to listen for the mouse position changes. The above code for mouse click events does not work, because the click event is only send to the widget (a ImageMorph) but not to the model. But the model registers itself for the click event when the widget is build. If a click even is send on the image morph, the model calls #value on its action property, just set an apropiate block as action for your ImageModel an example: im := ImageModel new. im image: PolymorphSystemSettings pharoLogoForm. im action:[ActiveHand inspect]. im openWithSpec. clicking on the image will open an inspector with the active hand.

March 21, 2017

Improving Magritte

by Diego Lont

Hi all, Recently there was a question about Magritte extensions on the Pharo users list. It has been a while that I was really involved in developing on (QC)Magritte and doing stuff on the web, but on my todo list, there is feeding back the improvements on Magritte I have made for QCMagritte to Magritte itself. And while doing so, adding tests and cleaning up code where needed. The first extension I would like to feed back into Magritte is the Builder. The background of the builder is the following: - Having a custom component set, and wanting to use this custom component set can be very tiresome for larger applications, because you have to set a component class for all descriptions. - Also it breaks the layering Magritte is trying to build in, as you need to "pollute" your model descriptions, with all kind of stuff, that determine how everything looks like. With stuff that belongs in your UI code instead of your model code. I believe that the builder is a solution for this problem. The actual builder can be injected as an extension (for an example see the QCMagritte demo) and processes all descriptions. As it is a visitor, it can replace or enrich your descriptions with whatever you need in your UI based on the type of description. The builder affects the way the Magritte description is created, so the package contains an override of magritteDescription. If I would implement this on Object (the most logical point), I would need to put the builder into Magritte-Model. Having no builders, this would of course not affect the returned description. Does anyone object to putting this here? And if you have objections, do you have a suggestion to do this elsewhere? Cheers, Diego

March 21, 2017

Re: [Pharo-users] Magritte extension

by DiegoLont

Hi all, It has been a while that I was really involved in developing on (QC)Magritte and doing stuff on the web ... I am all in favour of forming a group of active people to do some improvements on Magritte. I wrote on my todo list that I should feed back some of the improvements made in QCMagritte back to Magritte, but feeling a lack of interest from the community it dropped of my list. Maybe now is a good time to find some room in my schedule for doing so. First of all I want to advertise QCMagritte: This framework is easy to use. It has a seaside like tutorial, that every developer should be able to follow without any significant problems and shows all significant features of both Magritte, Seaside and QCMagritte. Although it lacks documentation on the technical details of the framework, it has documentation included how to use the framework (as a developer). Secondly. I agree that the most easy customisation of Magritte is using custom components. The Magritte components provided are quite basic. That is why in QCMagritte there is a number of components included that support AJAX functionality. It also contains a component that allows inline editing in a report. The idea about Magritte is also that the descriptions do not require a certain set of components. I.e. there was also an attempt on creating a Morph set of components ... that is a bit incomplete. Third. Feeding the improvements I have made in QC Magritte back into Magritte should probably be discussed this on the Magritte mailinglist. So I will do this in a separate post, mailing to bost lists. Cheers, Diego -- View this message in context: http://forum.world.st/Magritte-extension-tp4939046p4939547.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 21, 2017

UI with Spec, how to get mouse events ?

by Daniel BLANC

Hi all, I'm building a Spec UI with an ImageModel and a LabelModel. The image is a map, and the label should display the mouse coordinates when the mouse cursor is on the map. I'm a newcomer to Pharo and Smalltalk, I've searched in the pharo image, and looked into events, on:send:to: message, but I don't know how to properly use them with Spec. For testing purpose I've tried just to get a mouse click with this: MyStuff >> initializeWidgets map := self newImage. mousePos := self newLabel. map on: #click send: #mouseClicked to: self But that doesn't work. Any idea how I can do this ? Thanks, Daniel

March 21, 2017

Re: [Pharo-users] Neural Networks in Pharo

by Alexandre Bergel

Excellent Guillermo! I also wanted to play with the Mnist dataset. I will try your code Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 21, 2017, at 8:24 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Oleksandr, > > I'm working half-time on a team doing simulations of spiking neural networks (on scala). Since the topic is "new" to me, I started following a MOOC on traditional machine learning and putting some of my code in here: > > https://github.com/guillep/neural-experiments <https://github.com/guillep/neural-experiments> > > Also, I wanted to experiment on hand-written characters with the Mnist dataset (yann.lecun.com/exdb/mnist/ <http://yann.lecun.com/exdb/mnist/>) so I wrote a reader for the IDX format to load the dataset. > > https://github.com/guillep/idx-reader <https://github.com/guillep/idx-reader> > > If you want I can take a look and we can discuss further :) > > Guille > > > On Tue, Mar 21, 2017 at 11:30 AM, Oleksandr Zaytsev <olk.zaytsev(a)gmail.com <mailto:olk.zaytsev@gmail.com>> wrote: > I started by implementing some simple threshold neurons. The current goal is a multilayer perceptron (similar to the one in scikit-learn), and maybe other kinds of networks, such as self-organizing maps or radial basis networks. > > I could try to implement a deep learning algorithm, but the big issue with them is time complexity. Probably, it would require the use of GPU, or some advanced "tricks", so I should start with something smaller. > > Also, I want to try different kinds of design approaches, including those that are not based on highly optimized vector algebra (I know that it might not be the best idea, but I want try it and see what happens). For example, a network, where each neuron is an object (normally the whole network is represented as a collection of weight matrices). It might turn out to be very slow, but more object-friendly. For now it's just an idea, but to try something like that I would need a small network with 1-100 neurons. > > Yours sincerely, > Oleksandr >

March 21, 2017

Re: [Pharo-users] Neural Networks in Pharo

by Alexandre Bergel

Having a neuron as an object is exactly what I have in my implementation. Sounds exciting! Share your code when ready! Eager to try it! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 21, 2017, at 7:30 AM, Oleksandr Zaytsev <olk.zaytsev(a)gmail.com> wrote: > > I started by implementing some simple threshold neurons. The current goal is a multilayer perceptron (similar to the one in scikit-learn), and maybe other kinds of networks, such as self-organizing maps or radial basis networks. > > I could try to implement a deep learning algorithm, but the big issue with them is time complexity. Probably, it would require the use of GPU, or some advanced "tricks", so I should start with something smaller. > > Also, I want to try different kinds of design approaches, including those that are not based on highly optimized vector algebra (I know that it might not be the best idea, but I want try it and see what happens). For example, a network, where each neuron is an object (normally the whole network is represented as a collection of weight matrices). It might turn out to be very slow, but more object-friendly. For now it's just an idea, but to try something like that I would need a small network with 1-100 neurons. > > Yours sincerely, > Oleksandr

March 21, 2017