August 2011 - Pharo-dev - lists.pharo.org

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

by Denis Kudriashov

2011/8/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Aug 7, 2011, at 9:59 PM, Denis Kudriashov wrote: > > > 2011/8/7 Igor Stasenko <siguctua(a)gmail.com> > > Nice. > > Of course editing stuff with context menu is tedious.. :) > > With editor this may be much easier. > > > > Of course. But it is really simplest thing which can be done. Poor > designer always exists in morphic. So I can focus on more interesting stuff > which I need in practice. > > > > I think it is not difficult to use stuff from resent designer projects > (from null pointer ) > > I do not think so and having a complete scenario is the way to go if you > want people to get involved and using it. > > Complete scenario required time.

Aug. 7, 2011

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

by Denis Kudriashov

2011/8/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Aug 7, 2011, at 9:53 PM, Denis Kudriashov wrote: > > > > > 2011/8/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > 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? > > > > No. Prototype is just basic morph. When guide requested to show presenter > it search saved prototype for presenter and execute "prototype veryDeepCopy" > to create view instance. > > So there is no need to support specification objects. It is all basic > morphs. > > I think that it would be nice to be able to turn a prototype into a class > definition. Because as igor said been able to edit code is often a good way > to reuse. > > Maybe you right. But with current solution you can just open explorer on morph which you want to change and modify it state programmatically as you want. At the end of modifications you just save it as prototype. Also you can easilly get prototype instance and modify it directly. There is "inspect build context" item in halo menu. Also there is menu items for copy prototype from one presenter and paste it to another. But sometimes our clients ask me for xml with skin properties to change x,y of some interface element. I just show him halo menu and they happy.

Aug. 7, 2011

Re: [Pharo-project] About configurationOfPharoRB

by StÃ©phane Ducasse

Dale I added stable: spec <symbolicVersion: #stable> spec for: #'pharo1.0.x' version: '1.2.1'. spec for: #'pharo1.1.x' version: '1.5'. spec for: #'pharo1.2.x' version: '1.7'. spec for: #'pharo1.3.x' version: '1.7'. spec for: #'pharo1.4.x' version: '1.8'. spec for: #'squeak4.x' version: '1.6'. and a new baseline and version but when I do (ConfigurationOfRefactoringBrowser project version: #'stable') load I get an error. Do you have an idea? Stef version18: spec <version: '1.8' imports: #('1.8-baseline' )> spec for: #'common' do: [ spec blessing: #'release'. spec description: 'RefactoringBrowser for pharo 1.4 alpha. For this version we just move the place to look for Refactoring-Changes. Now there is a project for RB for pharo: It is called PharoRB'. spec author: 'StephaneDucasse'. spec timestamp: '2011-08-07T21:54:25+00:00'. "DateAndTime now asString" ]. spec for: #'pharo' do: [ spec package: 'AST-Core' with: 'AST-Core-lr.87'; package: 'AST-Tests-Core' with: 'AST-Tests-Core-lr.11'; package: 'AST-Semantic' with: 'AST-Semantic-lr.15'; package: 'AST-Tests-Semantic' with: 'AST-Tests-Semantic-lr.3'; package: 'Refactoring-Environment' with: 'Refactoring-Environment-lr.7'; package: 'Refactoring-Tests-Environment' with: 'Refactoring-Tests-Environment-lr.1'; package: 'Refactoring-Changes' with: 'Refactoring-Changes-GuillermoPolito.17'; package: 'Refactoring-Tests-Changes' with: 'Refactoring-Tests-Changes-lr.14'; package: 'Refactoring-Core' with: 'Refactoring-Core-lr.153'; package: 'Refactoring-Tests-Core' with: 'Refactoring-Tests-Core-lr.51'; package: 'Refactoring-Critics' with: 'Refactoring-Critics-lr.9'; package: 'Refactoring-Tests-Critics' with: 'Refactoring-Tests-Critics-lr.3'; package: 'Refactoring-Spelling' with: 'Refactoring-Spelling-pmm.25'; package: 'Refactoring-Tests-Spelling' with: 'Refactoring-Tests-Spelling-lr.6'. ]. spec for: #'squeak' do: [ spec description: 'Squeak support based on Squeak4.2-Trunk-10628'. spec package: 'AST-Core' with: 'AST-Core-lr.85'; package: 'AST-Semantic' with: 'AST-Semantic-lr.15'; package: 'Refactoring-Core' with: 'Refactoring-Core-lr.153'; package: 'Refactoring-Environment' with: 'Refactoring-Environment-lr.4'; package: 'Refactoring-Critics' with: 'Refactoring-Critics-lr.4'; package: 'Refactoring-Spelling' with: 'Refactoring-Spelling-lr.23'; package: 'Refactoring-Changes' with: 'Refactoring-Changes-lr.16']. spec for: #'gemstone' do: [ spec author: 'DaleHenrichs'. spec project: 'GsCore' with: '0.241'. spec package: 'AST-Core' with: 'AST-Core-DaleHenrichs.84'; package: 'AST-Tests-Core' with: 'AST-Tests-Core-DaleHenrichs.11'.].

Aug. 7, 2011

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

by StÃ©phane Ducasse

On Aug 7, 2011, at 9:59 PM, Denis Kudriashov wrote: > 2011/8/7 Igor Stasenko <siguctua(a)gmail.com> > Nice. > Of course editing stuff with context menu is tedious.. :) > With editor this may be much easier. > > Of course. But it is really simplest thing which can be done. Poor designer always exists in morphic. So I can focus on more interesting stuff which I need in practice. > > I think it is not difficult to use stuff from resent designer projects (from null pointer ) I do not think so and having a complete scenario is the way to go if you want people to get involved and using it.

Aug. 7, 2011

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

by StÃ©phane Ducasse

On Aug 7, 2011, at 9:53 PM, Denis Kudriashov wrote: > > 2011/8/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > 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? > > No. Prototype is just basic morph. When guide requested to show presenter it search saved prototype for presenter and execute "prototype veryDeepCopy" to create view instance. > So there is no need to support specification objects. It is all basic morphs. I think that it would be nice to be able to turn a prototype into a class definition. Because as igor said been able to edit code is often a good way to reuse. > > Question: how do you deals with change notification and update? > > I use announcements. Every presenter has announcer and every task has announcer. > In concrete application you can use it as you like. Presenty not provide concrete approach for this. > Now Presenty has no aspect adapters for editing model. > My business application initially based on meta-descriptions so Presenty has only class PtyDataField with description and value. And PtyFieldModel class which can notify about field value changes. Arbitrary object stuff is absent. But I started to implement it. > > It would be nice to see with a more striking example how you can put a different presenter for the list. > > I show it in next screencast and of course on esug presentation. > Purpose of current screencast is show how specify presenter appearance and how program presenters. > > > Is the red frame also the presenter? > > No. It is view of presenter when no prototypes exist for it. > I implement it this way to easy notice what part of ui not designed > > > how do we save and publish UI on monticello? > > Stef > > > This is good question. No solution for this yet. And I don't know how easilly it can be done. > All prototypes of application holds in "guide uiBuilder prototypesManager" (PtyPrototypesManager instance). So special way to store this object should be implemented. > Maybe solutions from UI designers can be used. > For my application I just save this object to "skin" file and load it when needed. Having a class and and at load time you just do MyStyle new and you get your style to add to your style database. Stef

Aug. 7, 2011

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

by Denis Kudriashov

2011/8/7 Igor Stasenko <siguctua(a)gmail.com> > Nice. > Of course editing stuff with context menu is tedious.. :) > With editor this may be much easier. > Of course. But it is really simplest thing which can be done. Poor designer always exists in morphic. So I can focus on more interesting stuff which I need in practice. I think it is not difficult to use stuff from resent designer projects (from null pointer )

Aug. 7, 2011

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

by Denis Kudriashov

2011/8/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > 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? > No. Prototype is just basic morph. When guide requested to show presenter it search saved prototype for presenter and execute "prototype veryDeepCopy" to create view instance. So there is no need to support specification objects. It is all basic morphs. Question: how do you deals with change notification and update? > I use announcements. Every presenter has announcer and every task has announcer. In concrete application you can use it as you like. Presenty not provide concrete approach for this. Now Presenty has no aspect adapters for editing model. My business application initially based on meta-descriptions so Presenty has only class PtyDataField with description and value. And PtyFieldModel class which can notify about field value changes. Arbitrary object stuff is absent. But I started to implement it. It would be nice to see with a more striking example how you can put a > different presenter for the list. > I show it in next screencast and of course on esug presentation. Purpose of current screencast is show how specify presenter appearance and how program presenters. Is the red frame also the presenter? > No. It is view of presenter when no prototypes exist for it. I implement it this way to easy notice what part of ui not designed > > how do we save and publish UI on monticello? > > Stef > > This is good question. No solution for this yet. And I don't know how easilly it can be done. All prototypes of application holds in "guide uiBuilder prototypesManager" (PtyPrototypesManager instance). So special way to store this object should be implemented. Maybe solutions from UI designers can be used. For my application I just save this object to "skin" file and load it when needed.

Aug. 7, 2011

Re: [Pharo-project] About configurationOfPharoRB

by StÃ©phane Ducasse

I'm currently checking configurationOfRefactoringBrowser and it would be good that package: 'Refactoring-Changes' with: [ spec repository: 'http://www.squeaksource.com/PharoTaskForces'; requires: 'Refactoring-Environment' ]; gets moved to PharoRB project. I will start to do that for 1.4 and after I will add the changes we did in the other configurations if I succeed to make it load what I want. At least having only one configuration should help. Stef

Aug. 7, 2011

Re: [Pharo-project] About configurationOfPharoRB

by StÃ©phane Ducasse

> Stef, > > Where did ConfigurationOfPharoRB come from? There is a ConfigurationOfRefactoringBrowser and the stable: method matches. In ConfigurationOfRefactoringBrowser there are versions 1.0 through 1.7.1, so ConfigurationOfPharoRB might just be dead code ... Ok I see the PharoRB was a configuration we did (probably because we forgot about the other because we needed to start changing part. For example to have Environment not referencing RBParser so that we can use them independently. There was also something about AST. Now I puzzled because I have the two following specs, when I do (ConfigurationOfPharoRB project version: '1.0') load or (ConfigurationOfPharoRB project version: '1.0') load: 'Tests' 'Refactoring-Extensions-Environment' is not load but it is part of Core Do you have an idea? I will at ConfigurationOfRefactoringBrowser baseline10: spec <version: '1.0-baseline'> spec for: #pharo do: [ spec repository: 'http://www.squeaksource.com/rb'. spec package: 'AST-Core' with: [spec repository: 'http://www.squeaksource.com/PharoRB' ]; "We split the original package into two so that AST does not depend on RBParser." package: 'AST-Tests-Core' with: [ spec requires: 'AST-Core' ]; package: 'AST-Semantic' with: [ spec requires: 'AST-Core' ]; package: 'AST-Tests-Semantic' with: [ spec requires: 'AST-Semantic' ]; package: 'Refactoring-Environment' with: [ spec requires: 'AST-Core'. spec repository: 'http://www.squeaksource.com/PharoRB' ]; "We were refactoring the way rb deals with environments because we want it to be parametrized over an environment (since the complete chain should be environmentized so that we can deal with remote compilation and others off image manipulation. so far RB has the idea that an environment by default represents the complete universe and we will have to change that in the future." package: 'Refactoring-Tests-Environment' with: [ spec requires: 'Refactoring-Environment'. spec repository: 'http://www.squeaksource.com/PharoRB' ]; package: 'Refactoring-Extensions-Environment' with: [ spec repository: 'http://www.squeaksource.com/PharoRB' ]; package: 'Refactoring-Changes' with: [ spec repository: 'http://www.squeaksource.com/PharoRB'; requires: 'Refactoring-Environment' ]; package: 'Refactoring-Tests-Changes' with: [ spec requires: 'Refactoring-Changes' ]; package: 'Refactoring-Core' with: [ spec requires: 'Refactoring-Changes' ]; package: 'Refactoring-Tests-Core' with: [ spec requires: 'Refactoring-Core' ]; package: 'Refactoring-Critics' with: [ spec requires: 'Refactoring-Changes' ]; package: 'Refactoring-Tests-Critics' with: [ spec requires: 'Refactoring-Critics' ]; package: 'Refactoring-Spelling' with: [ spec requires: 'Refactoring-Critics'. spec postLoadDoIt: #postLoadRBSpelling ]; package: 'Refactoring-Tests-Spelling' with: [ spec requires: 'Refactoring-Tests-Critics'. ]. spec group: 'default' with: #('Core' ); group: 'Core' with: #( 'AST-Core' 'AST-Semantic' 'Refactoring-Environment' 'Refactoring-Extensions-Environment' 'Refactoring-Changes' 'Refactoring-Core' 'Refactoring-Critics' 'Refactoring-Spelling' ); group: 'Tests' with: #( 'AST-Tests-Core' 'AST-Tests-Semantic' 'Refactoring-Tests-Environment' 'Refactoring-Tests-Changes' 'Refactoring-Tests-Core' 'Refactoring-Tests-Critics' 'Refactoring-Tests-Spelling' ); group: 'Core Tests' with: #('Core' 'Tests' ); yourself. ]. baseline10: spec <version: '1.0-baseline'> spec for: #pharo do: [ spec repository: 'http://www.squeaksource.com/rb'. spec package: 'AST-Core' with: [spec repository: 'http://www.squeaksource.com/PharoRB' ]; "We split the original package into two so that AST does not depend on RBParser." package: 'AST-Tests-Core' with: [ spec requires: 'AST-Core' ]; package: 'AST-Semantic' with: [ spec requires: 'AST-Core' ]; package: 'AST-Tests-Semantic' with: [ spec requires: 'AST-Semantic' ]; package: 'Refactoring-Environment' with: [ spec requires: 'AST-Core'. spec repository: 'http://www.squeaksource.com/PharoRB' ]; "We were refactoring the way rb deals with environments because we want it to be parametrized over an environment (since the complete chain should be environmentized so that we can deal with remote compilation and others off image manipulation. so far RB has the idea that an environment by default represents the complete universe and we will have to change that in the future." package: 'Refactoring-Tests-Environment' with: [ spec requires: 'Refactoring-Environment'. spec repository: 'http://www.squeaksource.com/PharoRB' ]; package: 'Refactoring-Extensions-Environment' with: [ spec repository: 'http://www.squeaksource.com/PharoRB' ]; package: 'Refactoring-Changes' with: [ spec repository: 'http://www.squeaksource.com/PharoRB'; requires: 'Refactoring-Environment' ]; package: 'Refactoring-Tests-Changes' with: [ spec requires: 'Refactoring-Changes' ]; package: 'Refactoring-Core' with: [ spec requires: 'Refactoring-Changes' ]; package: 'Refactoring-Tests-Core' with: [ spec requires: 'Refactoring-Core' ]; package: 'Refactoring-Critics' with: [ spec requires: 'Refactoring-Changes' ]; package: 'Refactoring-Tests-Critics' with: [ spec requires: 'Refactoring-Critics' ]; package: 'Refactoring-Spelling' with: [ spec requires: 'Refactoring-Critics'. spec postLoadDoIt: #postLoadRBSpelling ]; package: 'Refactoring-Tests-Spelling' with: [ spec requires: 'Refactoring-Tests-Critics'. ]. spec group: 'default' with: #('Core' ); group: 'Core' with: #( 'AST-Core' 'AST-Semantic' 'Refactoring-Environment' 'Refactoring-Extensions-Environment' 'Refactoring-Changes' 'Refactoring-Core' 'Refactoring-Critics' 'Refactoring-Spelling' ); group: 'Tests' with: #( 'AST-Tests-Core' 'AST-Tests-Semantic' 'Refactoring-Tests-Environment' 'Refactoring-Tests-Changes' 'Refactoring-Tests-Core' 'Refactoring-Tests-Critics' 'Refactoring-Tests-Spelling' ); group: 'Core Tests' with: #('Core' 'Tests' ); yourself. ].

Aug. 7, 2011

Re: [Pharo-project] About configurationOfPharoRB

by Dale Henrichs

Stef, Where did ConfigurationOfPharoRB come from? There is a ConfigurationOfRefactoringBrowser and the stable: method matches. In ConfigurationOfRefactoringBrowser there are versions 1.0 through 1.7.1, so ConfigurationOfPharoRB might just be dead code ... Dale ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: "pharo-project Development" <Pharo-project(a)lists.gforge.inria.fr> | Sent: Sunday, August 7, 2011 12:12:04 PM | Subject: [Pharo-project] About configurationOfPharoRB | | Hi | | there is | | stable: spec | <symbolicVersion: #stable> | spec for: #'pharo1.0.x' version: '1.2.1'. | spec for: #'pharo1.1.x' version: '1.5'. | spec for: #'pharo1.2.x' version: '1.7'. | spec for: #'pharo1.3.x' version: '1.7'. | spec for: #'squeak4.x' version: '1.6'. | | Now I'm confused because there is only a version 1.0 in this | configuration. | Did I miss something obvious or this is just deadcode? | | Stef | |

Aug. 7, 2011