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

Re: [Pharo-users] [ANN] success story: surgery appointments digitalised

by Tudor Girba

Nice work! Doru > On Jun 22, 2017, at 2:40 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > I'm sorry I forgot to post this much earlier. Anywayâ¦. > > We are proud to add another success story to the pharo portfolio > > http://zweidenker.de/en/project/operationstermine-digitalisiert > > It is an operation planning tool for an eye surgery clinic. The core system is pharo4 and voyage (using mongo). The user interface is done with seaside. It interfaces with a legacy patient information system, microsoft exchange and other stuff in order to orchestrate the arrangement of surgery dates. The tool automates planning (which doctor works on which day and has still time to do the operation,â¦.). Finalized plans are produced in PDF an printed by the staff. > > This as a short info. If you have question don't hesitate to ask. > > Implanting more pharo everywhere :) > > Norbert > -- www.tudorgirba.com www.feenk.com "Be rather willing to give than demanding to get."

June 22, 2017

Re: [Pharo-users] vested interest in PharoJS?

by askoh

There seem to be some interesting work with SqueakJS by Craig Latta. https://thiscontext.com/ I hope Smalltalk of all dialects can get together to develop a killer web development environment. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/vested-interest-in-PharoJS-tp4951357p4952310.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 22, 2017

Re: [Pharo-users] PharoJS

by askoh

There seem to be some interesting work with SqueakJS by Craig Latta. https://thiscontext.com/ I hope Smalltalk of all dialects can get together to develop a killer web development environment. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Re-PharoJS-tp4952267p4952306.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 22, 2017

Re: [Pharo-users] [Pharo-dev] vested interest in PharoJS?

by Norbert Hartl

> Am 22.06.2017 um 13:57 schrieb Siemen Baader <siemenbaader(a)gmail.com>: > > Very cool, Norbert. I have been watching what you are doing at 2denker and thought you might be interested ;) > > What is holding you back - do you need more from PharoJS before starting to use it commercially, or are you waiting for a (paid) project before you can start? > What is keeping me? A project and the feasibility. The amber project we could do because the project was more of a research project so I said "why not". For anything serious you need to check if it is feasible to use. And my trials with PharoJS were only little so I don't have the feeling, yet, if it is a huge benefit using it. But I feel a huge potential in it so it is on my list of things I wanna try but not on top. Norbert > -- Siemen > > On Thu, Jun 22, 2017 at 1:08 PM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > I thought I responded already. We are interested in pharoJS. We developed stuff with amber but stopped using it. We have one app in the app store with ionic and amber and I'd like to do another one with pharoJS. Additionally I think that combining pharoJS with electron could be a nice thing to have in order to create desktop apps. And finally I was shortly researching native callouts from javascript with javascript core on ios and it seems you can do pharo code, transpile to javascript that calls javascript functions which are OS-native functions. > > Norbert > > > Am 14.06.2017 um 11:46 schrieb Siemen Baader <siemenbaader(a)gmail.com <mailto:siemenbaader@gmail.com>>: > > > > Hi all, > > > > Is anyone else interested in PharoJS and making it mature for their own commercial mobile and single page web app (and node.js) development? > > > > I think it has a huge potential because it brings the browser runtime and many libraries and online services from the JS world to us Smalltalkers while letting us keep our agile development and good CS practices. But it does not yet have the necessary features and documentation to work smoothly. > > > > -- Siemen > >

June 22, 2017

Re: [Pharo-users] PharoJS

by andrew glynn

I was wondering: a) I'm assuming PharoJS would be much like Amber but inside the Pharo VM. b) How much of the Amber codebase could be re-used for it? I'm interested on the one hand, mainly due to the demand for Angular code in the browser (jQuery is great in Seaside, but many clients are looking for Angular recently), and my distaste for debugging JavaScript. Amber is ok but lacks the depth of tooling in Pharo, and isn't keeping up with the (constant) breaking changes in node and NPM. (Not that I blame the developers of Amber, it's a problem with the mindset of the developers in the JavaScript ecosystem - the way that Angular2 is almost completely different from Angular is an example of the lack of interest in the existing user base). The problem I see is that PharoJS would have the same issues. As a result it would not only be a fair amount of work to accomplish, it would be far more to maintain. The Pharo ecosystem is based on an entirely opposite mindset to the JS ecosystem - a few very good frameworks and a reasonable number of very good libraries, resulting in highly maintainable code even on projects with only one or two developers. On top of that it would have to deal with the issues with JS itself that make writing decent tools virtually impossible. Andrew Glynn -----Original Message----- From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of pharo-users-request(a)lists.pharo.org Sent: Thursday, June 22, 2017 8:41 AM To: pharo-users(a)lists.pharo.org Subject: Pharo-users Digest, Vol 50, Issue 108 Send Pharo-users mailing list submissions to pharo-users(a)lists.pharo.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org or, via email, send a message with subject or body 'help' to pharo-users-request(a)lists.pharo.org You can reach the person managing the list at pharo-users-owner(a)lists.pharo.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Pharo-users digest..."

June 22, 2017

Re: [Pharo-users] [ANN] success story: surgery appointments digitalised

by Sven Van Caekenberghe

> On 22 Jun 2017, at 14:40, Norbert Hartl <norbert(a)hartl.name> wrote: > > I'm sorry I forgot to post this much earlier. Anywayâ¦. > > We are proud to add another success story to the pharo portfolio > > http://zweidenker.de/en/project/operationstermine-digitalisiert > > It is an operation planning tool for an eye surgery clinic. The core system is pharo4 and voyage (using mongo). The user interface is done with seaside. It interfaces with a legacy patient information system, microsoft exchange and other stuff in order to orchestrate the arrangement of surgery dates. The tool automates planning (which doctor works on which day and has still time to do the operation,â¦.). Finalized plans are produced in PDF an printed by the staff. Very nice, well done ! > This as a short info. If you have question don't hesitate to ask. Yes, what's up with the hipster photographs at http://zweidenker.de/en/about-us ? Just kidding, nice website ! > Implanting more pharo everywhere :) > > Norbert >

June 22, 2017

[ANN] success story: surgery appointments digitalised

by Norbert Hartl

I'm sorry I forgot to post this much earlier. Anywayâ¦. We are proud to add another success story to the pharo portfolio http://zweidenker.de/en/project/operationstermine-digitalisiert <http://zweidenker.de/en/project/operationstermine-digitalisiert> It is an operation planning tool for an eye surgery clinic. The core system is pharo4 and voyage (using mongo). The user interface is done with seaside. It interfaces with a legacy patient information system, microsoft exchange and other stuff in order to orchestrate the arrangement of surgery dates. The tool automates planning (which doctor works on which day and has still time to do the operation,â¦.). Finalized plans are produced in PDF an printed by the staff. This as a short info. If you have question don't hesitate to ask. Implanting more pharo everywhere :) Norbert

June 22, 2017

Re: [Pharo-users] [Pharo-dev] vested interest in PharoJS?

by Siemen Baader

Very cool, Norbert. I have been watching what you are doing at 2denker and thought you might be interested ;) What is holding you back - do you need more from PharoJS before starting to use it commercially, or are you waiting for a (paid) project before you can start? -- Siemen On Thu, Jun 22, 2017 at 1:08 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > I thought I responded already. We are interested in pharoJS. We developed > stuff with amber but stopped using it. We have one app in the app store > with ionic and amber and I'd like to do another one with pharoJS. > Additionally I think that combining pharoJS with electron could be a nice > thing to have in order to create desktop apps. And finally I was shortly > researching native callouts from javascript with javascript core on ios and > it seems you can do pharo code, transpile to javascript that calls > javascript functions which are OS-native functions. > > Norbert > > > Am 14.06.2017 um 11:46 schrieb Siemen Baader <siemenbaader(a)gmail.com>: > > > > Hi all, > > > > Is anyone else interested in PharoJS and making it mature for their own > commercial mobile and single page web app (and node.js) development? > > > > I think it has a huge potential because it brings the browser runtime > and many libraries and online services from the JS world to us Smalltalkers > while letting us keep our agile development and good CS practices. But it > does not yet have the necessary features and documentation to work smoothly. > > > > -- Siemen > >

June 22, 2017

Re: [Pharo-users] [Pharo-dev] vested interest in PharoJS?

by Norbert Hartl

I thought I responded already. We are interested in pharoJS. We developed stuff with amber but stopped using it. We have one app in the app store with ionic and amber and I'd like to do another one with pharoJS. Additionally I think that combining pharoJS with electron could be a nice thing to have in order to create desktop apps. And finally I was shortly researching native callouts from javascript with javascript core on ios and it seems you can do pharo code, transpile to javascript that calls javascript functions which are OS-native functions. Norbert > Am 14.06.2017 um 11:46 schrieb Siemen Baader <siemenbaader(a)gmail.com>: > > Hi all, > > Is anyone else interested in PharoJS and making it mature for their own commercial mobile and single page web app (and node.js) development? > > I think it has a huge potential because it brings the browser runtime and many libraries and online services from the JS world to us Smalltalkers while letting us keep our agile development and good CS practices. But it does not yet have the necessary features and documentation to work smoothly. > > -- Siemen

June 22, 2017

Re: [Pharo-users] Setting rowHeight: for Spec FastTableModel

by Stephan Eggermont

On 22/06/17 10:51, Juraj Kubelka wrote: > Hi, > > I have a code like this: > > FastTableModel new > displayBlock: [ :node | node name ]; > items: Collection withAllSubclasses; > openWithSpec. > > Which works fine. But I would like to define row height for each item. > FTTableMorph has a method rowHeight:. > Is it possible? Sure. Not all properties of fasttable are exposed, and I never got a good answer on the design question of what and how to expose and propagate properties in Spec. I see the following design questions: Exposing all the Morphic properties makes for a stronger dependency on Morphic. Spec itself is written so it can be easily ported from one underlying widget & gui layer to another (bloc, cocoa, qt, less so for web?), and different layers have different properties. What is common and what needs adapters or even layer-specific code? When nesting components, how do properties propagate? Define once and reuse everywhere is the goal, but that requires defining where components can find property values: Theme, Application, Session. In Spec there is no model/API defined for that, and there is no systematic approach taken, just pragmatic choices. Stephan

June 22, 2017