MetacelloBrowser ui...
Locked
12
12
 
|
On Apr 27, 2011, at 1:38 AM, Tudor Girba wrote: > Hi, > > On 27 Apr 2011, at 03:23, Dale Henrichs wrote: > >> >> On Apr 26, 2011, at 5:27 PM, Tudor Girba wrote: >> >>> Hi Dale, >>> >>> On 27 Apr 2011, at 02:22, Dale Henrichs wrote: >>> >>>> On 04/26/2011 05:01 PM, Tudor Girba wrote: >>>>> Hi Dale, >>>>> >>>>> Glamour is independent from the rendering, just like Omnibrowser is. Here is a short description: >>>>> http://www.themoosebook.org/book/internals/glamour/rendering >>>>> >>>>> We already have a working Seaside rendering code for the basic widgets of Glamour. For an example, take the following steps: >>>>> >>>>> 1. download >>>>> http://hudson.moosetechnology.org/job/moose-with-glamour-seaside/lastSuccessfulBuild/artifact/moose-seaside/*zip*/moose-seaside.zip >>>>> >>>>> 2. run: >>>>> WAKom startOn: 8081 >>>>> >>>>> 3. go to: >>>>> http://localhost:8081/moose/metaBrowser >>>>> >>>>> Cheers, >>>>> Doru >>>> >>>> I'll hold off exploring the scope of the Glamour port until I see if Glamour can be used to construct the configuration wizard:) >>>> >>>> I'm not skeptical as much as I am very busy... >>>> >>>> Did I provide you with enough info for the use case? >>> >>> Not really :). >> >> okay? > > > I re-read the original mail, and indeed there is enough information :). I will try to give it a try. What I saw is that there is basically no dependency between steps. Is that correct? If yes, then all steps would fit in a simple Magritte form. The challenging aspects of the wizard involve allowing a user to select from a list of repositories (for the repository information), from a (filtered) list of packages and a list of projects when building the basic specs to be included in a baseline. At the next level of complexity, one must be allowed to define dependencies (required:) between packages and put the specs in different for:do: blocks ... Within the Metacello, there is an API and a model for managing these, but I a m sure that the API/model can be improved when we get to this point. So I suppose that the initial wizard could be done in Magritte... Dale |
|
|
In reply to this post by Tudor Girba
Hi,
Am 2011-04-27 um 10:28 schrieb Tudor Girba: > Hi, > > This is the default way to load the latest version: > > Gofer new > squeaksource: 'Glamour'; > package: 'ConfigurationOfGlamourSeaside'; > load. > (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. > > Cheers, > Doru This does not work even for the Metacello Part, as you are using a customized #ensureMetacello that will not work on a vanilla Squeak, there is no Gofer available. Shall I update your configs so that they at least can try to work? So Long -Tobias |
|
|
Hi Tobias,
On 27 Apr 2011, at 11:41, Tobias Pape wrote: > Hi, > > Am 2011-04-27 um 10:28 schrieb Tudor Girba: > >> Hi, >> >> This is the default way to load the latest version: >> >> Gofer new >> squeaksource: 'Glamour'; >> package: 'ConfigurationOfGlamourSeaside'; >> load. >> (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. >> >> Cheers, >> Doru > > This does not work even for the Metacello Part, as you are using > a customized #ensureMetacello that will not work on a vanilla > Squeak, there is no Gofer available. > Shall I update your configs so that they at least can try to work? Please just load Metacello first manually and then try GlamourSeaside. Cheers, Doru > So Long > -Tobias > -- www.tudorgirba.com "Every thing has its own flow." |
|
|
Am 2011-04-27 um 12:03 schrieb Tudor Girba: > Hi Tobias, > > On 27 Apr 2011, at 11:41, Tobias Pape wrote: > >> Hi, >> >> Am 2011-04-27 um 10:28 schrieb Tudor Girba: >> >>> Hi, >>> >>> This is the default way to load the latest version: >>> >>> Gofer new >>> squeaksource: 'Glamour'; >>> package: 'ConfigurationOfGlamourSeaside'; >>> load. >>> (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. >>> >>> Cheers, >>> Doru >> >> This does not work even for the Metacello Part, as you are using >> a customized #ensureMetacello that will not work on a vanilla >> Squeak, there is no Gofer available. >> Shall I update your configs so that they at least can try to work? > > Please just load Metacello first manually and then try GlamourSeaside. Is there a reason that you don't us a standard ensureMetacello? so long -tobias |
|
|
Hi,
On 27 Apr 2011, at 12:29, Tobias Pape wrote: > > Am 2011-04-27 um 12:03 schrieb Tudor Girba: > >> Hi Tobias, >> >> On 27 Apr 2011, at 11:41, Tobias Pape wrote: >> >>> Hi, >>> >>> Am 2011-04-27 um 10:28 schrieb Tudor Girba: >>> >>>> Hi, >>>> >>>> This is the default way to load the latest version: >>>> >>>> Gofer new >>>> squeaksource: 'Glamour'; >>>> package: 'ConfigurationOfGlamourSeaside'; >>>> load. >>>> (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. >>>> >>>> Cheers, >>>> Doru >>> >>> This does not work even for the Metacello Part, as you are using >>> a customized #ensureMetacello that will not work on a vanilla >>> Squeak, there is no Gofer available. >>> Shall I update your configs so that they at least can try to work? >> >> Please just load Metacello first manually and then try GlamourSeaside. > > Is there a reason that you don't us a standard ensureMetacello? No reason other than that the "standard" is evolving and due to the current copy paste solution, the configurations are bound to remain behind. On top of that, I do not know what the current standard actually is. Cheers, Doru > so long > -tobias > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding." |
|
|
The current recommended #ensureMetacello method is documented here:
http://code.google.com/p/metacello/wiki/EnsureMetacello The method bootstraps Gofer and will work correctly if either SqueakSource or GemSource is down. After Gofer is bootstrapped the ConfigurationOfMetacello is loaded using Gofer ... the changes were made around 1.0beta.27 and were aimed at making the #ensureMetacello implementation less volatile... Dale On Apr 27, 2011, at 3:41 AM, Tudor Girba wrote: > Hi, > > On 27 Apr 2011, at 12:29, Tobias Pape wrote: > >> >> Am 2011-04-27 um 12:03 schrieb Tudor Girba: >> >>> Hi Tobias, >>> >>> On 27 Apr 2011, at 11:41, Tobias Pape wrote: >>> >>>> Hi, >>>> >>>> Am 2011-04-27 um 10:28 schrieb Tudor Girba: >>>> >>>>> Hi, >>>>> >>>>> This is the default way to load the latest version: >>>>> >>>>> Gofer new >>>>> squeaksource: 'Glamour'; >>>>> package: 'ConfigurationOfGlamourSeaside'; >>>>> load. >>>>> (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. >>>>> >>>>> Cheers, >>>>> Doru >>>> >>>> This does not work even for the Metacello Part, as you are using >>>> a customized #ensureMetacello that will not work on a vanilla >>>> Squeak, there is no Gofer available. >>>> Shall I update your configs so that they at least can try to work? >>> >>> Please just load Metacello first manually and then try GlamourSeaside. >> >> Is there a reason that you don't us a standard ensureMetacello? > > No reason other than that the "standard" is evolving and due to the current copy paste solution, the configurations are bound to remain behind. On top of that, I do not know what the current standard actually is. > > Cheers, > Doru > > >> so long >> -tobias >> > > -- > www.tudorgirba.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > |
|
|
Thanks, Dale. I updated ConfigurationOfGlamourSeaside and I will slowly update the other Moose-related configurations.
Cheers, Doru On 27 Apr 2011, at 12:57, Dale Henrichs wrote: > The current recommended #ensureMetacello method is documented here: > > http://code.google.com/p/metacello/wiki/EnsureMetacello > > The method bootstraps Gofer and will work correctly if either SqueakSource or GemSource is down. After Gofer is bootstrapped the ConfigurationOfMetacello is loaded using Gofer ... the changes were made around 1.0beta.27 and were aimed at making the #ensureMetacello implementation less volatile... > > Dale > > On Apr 27, 2011, at 3:41 AM, Tudor Girba wrote: > >> Hi, >> >> On 27 Apr 2011, at 12:29, Tobias Pape wrote: >> >>> >>> Am 2011-04-27 um 12:03 schrieb Tudor Girba: >>> >>>> Hi Tobias, >>>> >>>> On 27 Apr 2011, at 11:41, Tobias Pape wrote: >>>> >>>>> Hi, >>>>> >>>>> Am 2011-04-27 um 10:28 schrieb Tudor Girba: >>>>> >>>>>> Hi, >>>>>> >>>>>> This is the default way to load the latest version: >>>>>> >>>>>> Gofer new >>>>>> squeaksource: 'Glamour'; >>>>>> package: 'ConfigurationOfGlamourSeaside'; >>>>>> load. >>>>>> (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. >>>>>> >>>>>> Cheers, >>>>>> Doru >>>>> >>>>> This does not work even for the Metacello Part, as you are using >>>>> a customized #ensureMetacello that will not work on a vanilla >>>>> Squeak, there is no Gofer available. >>>>> Shall I update your configs so that they at least can try to work? >>>> >>>> Please just load Metacello first manually and then try GlamourSeaside. >>> >>> Is there a reason that you don't us a standard ensureMetacello? >> >> No reason other than that the "standard" is evolving and due to the current copy paste solution, the configurations are bound to remain behind. On top of that, I do not know what the current standard actually is. >> >> Cheers, >> Doru >> >> >>> so long >>> -tobias >>> >> >> -- >> www.tudorgirba.com >> >> "Problem solving efficiency grows with the abstractness level of problem understanding." >> >> >> > -- www.tudorgirba.com "Obvious things are difficult to teach." |
|
|
In reply to this post by Dale Henrichs
Should all the metacello configurations be updated to this version?
Cheers El mié, 27-04-2011 a las 03:57 -0700, Dale Henrichs escribió: > The current recommended #ensureMetacello method is documented here: > > http://code.google.com/p/metacello/wiki/EnsureMetacello > > The method bootstraps Gofer and will work correctly if either SqueakSource or GemSource is down. After Gofer is bootstrapped the ConfigurationOfMetacello is loaded using Gofer ... the changes were made around 1.0beta.27 and were aimed at making the #ensureMetacello implementation less volatile... > > Dale > > On Apr 27, 2011, at 3:41 AM, Tudor Girba wrote: > > > Hi, > > > > On 27 Apr 2011, at 12:29, Tobias Pape wrote: > > > >> > >> Am 2011-04-27 um 12:03 schrieb Tudor Girba: > >> > >>> Hi Tobias, > >>> > >>> On 27 Apr 2011, at 11:41, Tobias Pape wrote: > >>> > >>>> Hi, > >>>> > >>>> Am 2011-04-27 um 10:28 schrieb Tudor Girba: > >>>> > >>>>> Hi, > >>>>> > >>>>> This is the default way to load the latest version: > >>>>> > >>>>> Gofer new > >>>>> squeaksource: 'Glamour'; > >>>>> package: 'ConfigurationOfGlamourSeaside'; > >>>>> load. > >>>>> (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. > >>>>> > >>>>> Cheers, > >>>>> Doru > >>>> > >>>> This does not work even for the Metacello Part, as you are using > >>>> a customized #ensureMetacello that will not work on a vanilla > >>>> Squeak, there is no Gofer available. > >>>> Shall I update your configs so that they at least can try to work? > >>> > >>> Please just load Metacello first manually and then try GlamourSeaside. > >> > >> Is there a reason that you don't us a standard ensureMetacello? > > > > No reason other than that the "standard" is evolving and due to the current copy paste solution, the configurations are bound to remain behind. On top of that, I do not know what the current standard actually is. > > > > Cheers, > > Doru > > > > > >> so long > >> -tobias > >> > > > > -- > > www.tudorgirba.com > > > > "Problem solving efficiency grows with the abstractness level of problem understanding." > > > > > > > -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx |
|
|
It wouldn't hurt...I poked around a bit last night and noted that most
of the configs bootstrap gofer and then load the config. The newer config will at least bootstrap Gofer even if SqueakSource is down ... Dale On 04/27/2011 08:03 AM, Miguel Cobá wrote: > Should all the metacello configurations be updated to this version? > > Cheers > > El mié, 27-04-2011 a las 03:57 -0700, Dale Henrichs escribió: >> The current recommended #ensureMetacello method is documented here: >> >> http://code.google.com/p/metacello/wiki/EnsureMetacello >> >> The method bootstraps Gofer and will work correctly if either SqueakSource or GemSource is down. After Gofer is bootstrapped the ConfigurationOfMetacello is loaded using Gofer ... the changes were made around 1.0beta.27 and were aimed at making the #ensureMetacello implementation less volatile... >> >> Dale >> >> On Apr 27, 2011, at 3:41 AM, Tudor Girba wrote: >> >>> Hi, >>> >>> On 27 Apr 2011, at 12:29, Tobias Pape wrote: >>> >>>> >>>> Am 2011-04-27 um 12:03 schrieb Tudor Girba: >>>> >>>>> Hi Tobias, >>>>> >>>>> On 27 Apr 2011, at 11:41, Tobias Pape wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> Am 2011-04-27 um 10:28 schrieb Tudor Girba: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> This is the default way to load the latest version: >>>>>>> >>>>>>> Gofer new >>>>>>> squeaksource: 'Glamour'; >>>>>>> package: 'ConfigurationOfGlamourSeaside'; >>>>>>> load. >>>>>>> (Smalltalk at: #ConfigurationOfGlamourSeaside) loadDefault. >>>>>>> >>>>>>> Cheers, >>>>>>> Doru >>>>>> >>>>>> This does not work even for the Metacello Part, as you are using >>>>>> a customized #ensureMetacello that will not work on a vanilla >>>>>> Squeak, there is no Gofer available. >>>>>> Shall I update your configs so that they at least can try to work? >>>>> >>>>> Please just load Metacello first manually and then try GlamourSeaside. >>>> >>>> Is there a reason that you don't us a standard ensureMetacello? >>> >>> No reason other than that the "standard" is evolving and due to the current copy paste solution, the configurations are bound to remain behind. On top of that, I do not know what the current standard actually is. >>> >>> Cheers, >>> Doru >>> >>> >>>> so long >>>> -tobias >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Problem solving efficiency grows with the abstractness level of problem understanding." >>> >>> >>> >> > |
|
|
Dale
Am 2011-04-27 um 17:16 schrieb Dale Henrichs: > It wouldn't hurt...I poked around a bit last night and noted that most of the configs bootstrap gofer and then load the config. The newer config will at least bootstrap Gofer even if SqueakSource is down ... > > Dale > > On 04/27/2011 08:03 AM, Miguel Cobá wrote: >> Should all the metacello configurations be updated to this version? >> >> Cheers >> >> El mié, 27-04-2011 a las 03:57 -0700, Dale Henrichs escribió: >>> The current recommended #ensureMetacello method is documented here: >>> >>> http://code.google.com/p/metacello/wiki/EnsureMetacello >>> >>> The method bootstraps Gofer and will work correctly if either SqueakSource or GemSource is down. After Gofer is bootstrapped the ConfigurationOfMetacello is loaded using Gofer ... the changes were made around 1.0beta.27 and were aimed at making the #ensureMetacello implementation less volatile... Can you please put the bootstrapPackage:from:-method there, to? It is used when Gofer is not found. Best -Tobias |
|
|
In reply to this post by Tudor Girba
Hi,
>> >> Is it usable in Squeak4.2? > > I never tried but you are welcome to. If you do, please let us know what happened :) Sorry for replying so late. When I got the Configuration to exectute, somewhere in the middle I get the following: This package depends on the following classes: MorphTreeColumn TabGroupMorph MorphTreeModel SubscriptionRegistry DialogWindow MorphTreeNodeModel ThemeIcons Announcer Announcement TabPanelBorder StandardWindow MultistateButtonMorph UIThemeWatery2 You must resolve these dependencies before you will be able to load these definitions: GLMAccumulator :/ It seems a lot of tweeking is necessary to overcome the Squeak/Pharo divergences here. Doru, can you send me some screenshots of Glamour/GlamourSeaside so that I can get an impression? Best -Tobias |
|
|
In reply to this post by Tobias Pape-3
Done[1]...
Dale [1] http://code.google.com/p/metacello/wiki/BootstrapPackageFrom ----- Original Message ----- | From: "Tobias Pape" <[hidden email]> | To: [hidden email] | Sent: Tuesday, May 31, 2011 1:26:56 PM | Subject: Re: [Metacello] MetacelloBrowser ui... | | Dale | | | Am 2011-04-27 um 17:16 schrieb Dale Henrichs: | | > It wouldn't hurt...I poked around a bit last night and noted that | > most of the configs bootstrap gofer and then load the config. The | > newer config will at least bootstrap Gofer even if SqueakSource is | > down ... | > | > Dale | > | > On 04/27/2011 08:03 AM, Miguel Cobá wrote: | >> Should all the metacello configurations be updated to this | >> version? | >> | >> Cheers | >> | >> El mié, 27-04-2011 a las 03:57 -0700, Dale Henrichs escribió: | >>> The current recommended #ensureMetacello method is documented | >>> here: | >>> | >>> http://code.google.com/p/metacello/wiki/EnsureMetacello | >>> | >>> The method bootstraps Gofer and will work correctly if either | >>> SqueakSource or GemSource is down. After Gofer is bootstrapped | >>> the ConfigurationOfMetacello is loaded using Gofer ... the | >>> changes were made around 1.0beta.27 and were aimed at making the | >>> #ensureMetacello implementation less volatile... | | Can you please put the bootstrapPackage:from:-method there, to? | It is used when Gofer is not found. | | Best | -Tobias | | | |
«
Return to Metacello
|
1 view|%1 views
| Free forum by Nabble | Edit this page |