- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Presenty UI framework

by Denis Kudriashov

I add like to screencast. Strange that fullscreen button not work. It is same screencast which I send you and Todor few weeks ago. Unfortunately too little time to create more good docs and screencasts. 2011/8/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > denis > > excellent! > I want to have a look at it. Do you know how I could see the video in big? > > Stef > > On Aug 7, 2011, at 8:23 PM, Denis Kudriashov wrote: > > > Hello. > > > > I am glad to announce Presenty - new user interface framework for Pharo > (with MIT license). > > I publish my current version on > http://www.squeaksource.com/Presenty.html and write first articles about > Presenty on blog http://smalltalk-presenty.blogspot.com > > > > There are some problems with current implementation. But step-by-step I > fix it and improved it. And I have many ideas about Presenty future. > > > > Main goal of Presenty is platform independent programming of user > interface: > > > > Pharo can run your application on any OS. Presenty can present your > application on any OS. > > > > With Presenty you can easilly write UI applications which can be > configured for all "user" platforms: mobile phones, tablets, desktop > computers and others. > > Presenty is based on Morphic and I think morphic can simulate every > platform appearance and behavior. And I think simulation is easest then > supporting native backends. > > > > I have two commercial applications for my company which based on > Presenty. So it is really usable although many common UI stuff absent and > some bugs exist. > > One is touch screen oriented application (for basic computer, not mobile > device) and second is basic desktop application (driven by mouse and > keyboard). > > It is different applications for different kind of users but its use same > components of tasks and domain objects. > > So when we implement new logic of user interraction it appears on both > applications but user takes it with different look and feel. > > > > There is problem with speed of presenty application. For my case cog > performance solve it. So I don't worry about it. > > But problem relates to #veryDeepCopy method of morphs. It is very very > slow. This method is used for view creation from prototype morph object. I > have fix with special methods for copy prototype morph. But I don't use it > yet. > > > > Now I prepare presentation for ESUG. So I can take into account of all > your comments and questions. > > > > Best regards, > > Denis > > > > > > >

Aug. 7, 2011

Re: [Pharo-project] cleaning/completing ConfigurationOfPetitParser

by StÃ©phane Ducasse

On Aug 7, 2011, at 8:03 PM, Damien Pollet wrote: > On 7 August 2011 18:14, Lukas Renggli <renggli(a)gmail.com> wrote: >> Indeed, AST-Core is a dependency of PetitSmalltalk. Also Glamour is a >> dependency of PetitGUI. Both packages probably shouldn't be loaded by >> default. > > The Glamour sep is already described. I added PetitSmalltalk and > committed. I'll do others on demand. > >>> Also, why are there less class methods than on other ConfigurationOf... ? >> >> Don't know, probably nobody bothered to update the configurations. >> Feel free to fix them :-) > > I need to read the Metacello chapter first :) please directly add your remarks on the git file. My gut feeling is that we should get an executive summary of this large chapter. > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet >

Aug. 7, 2011

Re: [Pharo-project] [ANN] Presenty UI framework

by StÃ©phane Ducasse

> denis > > excellent! > I want to have a look at it. Do you know how I could see the video in big? I found it. :) On youtube this is better. Question: Do you have a way to generate the code for the prototype one you have created one by direct manipulation? A prototype is like a specification of certain attributes? Question: how do you deals with change notification and update? It would be nice to see with a more striking example how you can put a different presenter for the list. Is the red frame also the presenter? how do we save and publish UI on monticello? Stef > > Stef > > On Aug 7, 2011, at 8:23 PM, Denis Kudriashov wrote: > >> Hello. >> >> I am glad to announce Presenty - new user interface framework for Pharo (with MIT license). >> I publish my current version on http://www.squeaksource.com/Presenty.html and write first articles about Presenty on blog http://smalltalk-presenty.blogspot.com >> >> There are some problems with current implementation. But step-by-step I fix it and improved it. And I have many ideas about Presenty future. >> >> Main goal of Presenty is platform independent programming of user interface: >> >> Pharo can run your application on any OS. Presenty can present your application on any OS. >> >> With Presenty you can easilly write UI applications which can be configured for all "user" platforms: mobile phones, tablets, desktop computers and others. >> Presenty is based on Morphic and I think morphic can simulate every platform appearance and behavior. And I think simulation is easest then supporting native backends. >> >> I have two commercial applications for my company which based on Presenty. So it is really usable although many common UI stuff absent and some bugs exist. >> One is touch screen oriented application (for basic computer, not mobile device) and second is basic desktop application (driven by mouse and keyboard). >> It is different applications for different kind of users but its use same components of tasks and domain objects. >> So when we implement new logic of user interraction it appears on both applications but user takes it with different look and feel. >> >> There is problem with speed of presenty application. For my case cog performance solve it. So I don't worry about it. >> But problem relates to #veryDeepCopy method of morphs. It is very very slow. This method is used for view creation from prototype morph object. I have fix with special methods for copy prototype morph. But I don't use it yet. >> >> Now I prepare presentation for ESUG. So I can take into account of all your comments and questions. >> >> Best regards, >> Denis >> >> > >

Aug. 7, 2011

[Pharo-project] [update 1.3] #13295

by Marcus Denker

13295 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (Part2) -- Marcus Denker -- http://marcusdenker.de

Aug. 7, 2011

Re: [Pharo-project] [ANN] Presenty UI framework

by StÃ©phane Ducasse

denis excellent! I want to have a look at it. Do you know how I could see the video in big? Stef On Aug 7, 2011, at 8:23 PM, Denis Kudriashov wrote: > Hello. > > I am glad to announce Presenty - new user interface framework for Pharo (with MIT license). > I publish my current version on http://www.squeaksource.com/Presenty.html and write first articles about Presenty on blog http://smalltalk-presenty.blogspot.com > > There are some problems with current implementation. But step-by-step I fix it and improved it. And I have many ideas about Presenty future. > > Main goal of Presenty is platform independent programming of user interface: > > Pharo can run your application on any OS. Presenty can present your application on any OS. > > With Presenty you can easilly write UI applications which can be configured for all "user" platforms: mobile phones, tablets, desktop computers and others. > Presenty is based on Morphic and I think morphic can simulate every platform appearance and behavior. And I think simulation is easest then supporting native backends. > > I have two commercial applications for my company which based on Presenty. So it is really usable although many common UI stuff absent and some bugs exist. > One is touch screen oriented application (for basic computer, not mobile device) and second is basic desktop application (driven by mouse and keyboard). > It is different applications for different kind of users but its use same components of tasks and domain objects. > So when we implement new logic of user interraction it appears on both applications but user takes it with different look and feel. > > There is problem with speed of presenty application. For my case cog performance solve it. So I don't worry about it. > But problem relates to #veryDeepCopy method of morphs. It is very very slow. This method is used for view creation from prototype morph object. I have fix with special methods for copy prototype morph. But I don't use it yet. > > Now I prepare presentation for ESUG. So I can take into account of all your comments and questions. > > Best regards, > Denis > >

Aug. 7, 2011

[Pharo-project] [update 1.3] #13294

by Marcus Denker

13294 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (Part1) -- Marcus Denker -- http://marcusdenker.de

Aug. 7, 2011

[Pharo-project] [ANN] Presenty UI framework

by Denis Kudriashov

Hello. I am glad to announce Presenty - new user interface framework for Pharo (with MIT license). I publish my current version on http://www.squeaksource.com/Presenty.htmland write first articles about Presenty on blog http://smalltalk-presenty.blogspot.com There are some problems with current implementation. But step-by-step I fix it and improved it. And I have many ideas about Presenty future. Main goal of Presenty is platform independent programming of user interface: Pharo can run your application on any OS. Presenty can present your application on any OS. With Presenty you can easilly write UI applications which can be configured for all "user" platforms: mobile phones, tablets, desktop computers and others. Presenty is based on Morphic and I think morphic can simulate every platform appearance and behavior. And I think simulation is easest then supporting native backends. I have two commercial applications for my company which based on Presenty. So it is really usable although many common UI stuff absent and some bugs exist. One is touch screen oriented application (for basic computer, not mobile device) and second is basic desktop application (driven by mouse and keyboard). It is different applications for different kind of users but its use same components of tasks and domain objects. So when we implement new logic of user interraction it appears on both applications but user takes it with different look and feel. There is problem with speed of presenty application. For my case cog performance solve it. So I don't worry about it. But problem relates to #veryDeepCopy method of morphs. It is very very slow. This method is used for view creation from prototype morph object. I have fix with special methods for copy prototype morph. But I don't use it yet. Now I prepare presentation for ESUG. So I can take into account of all your comments and questions. Best regards, Denis

Aug. 7, 2011

Re: [Pharo-project] Squeaksource is down :(

by Johan Brichau

On 07 Aug 2011, at 18:36, Lukas Renggli wrote: > Again and again, automatic restart is not possible with SqueakSource > because it requires manual intervention after startup to make sure the > model is properly loaded and consistent. People are not stupid. ha ok, I did ask the question before but never got an answer. I hope that the new SmalltalkHUB and SS3 people prepare to not integrate a human being into their system. thanks for the info. cheers, Johan

Aug. 7, 2011

Re: [Pharo-project] cleaning/completing ConfigurationOfPetitParser

by Damien Pollet

On 7 August 2011 18:14, Lukas Renggli <renggli(a)gmail.com> wrote: > Indeed, AST-Core is a dependency of PetitSmalltalk. Also Glamour is a > dependency of PetitGUI. Both packages probably shouldn't be loaded by > default. The Glamour sep is already described. I added PetitSmalltalk and committed. I'll do others on demand. >> Also, why are there less class methods than on other ConfigurationOf... ? > > Don't know, probably nobody bothered to update the configurations. > Feel free to fix them :-) I need to read the Metacello chapter first :) -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 7, 2011

Re: [Pharo-project] Squeaksource is down :(

by StÃ©phane Ducasse

>>> Please do not put unnecessary load on SqueakSource by running >>> additional monitoring services. This does not help at all. >> >> Thanks for the info. I knew that there was a watchdog but not sure it was still running. >> I hope that soon we will be able to let SS rest in peace after all the immense work it offers to us. > > We should run SqueakSource in read-only mode ASAP and shut-it down by > the end of the month. Otherwise nothing will ever happen. It will :) And end of the month there is esug so it should really happen. Nicolas is working with dale to have a better back end than the save as image that was originally planned. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

Aug. 7, 2011