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 <[email protected]> > 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 > > > > > > >
