From estebanlm at gmail.com Mon Oct 17 19:04:28 2016 From: estebanlm at gmail.com (Esteban Lorenzano) Date: Mon Oct 17 19:04:35 2016 Subject: [Seaside] Re: [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> Message-ID: this is a question more appropriate for Seaside list :) > On 17 Oct 2016, at 20:07, Pierre CHANSON wrote: > > In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x? have been removed and Seaside does not have configuration for pharo6. > > Is there a plan to update the configuration of Seaside ? > > Thanks ! > > Pierre and Norbert From jtuchel at objektfabrik.de Tue Oct 18 04:35:28 2016 From: jtuchel at objektfabrik.de (jtuchel@objektfabrik.de) Date: Tue Oct 18 04:35:33 2016 Subject: [Seaside] =?utf-8?q?=5BANN=5D_Z=C3=BCrich_Smalltalk_Meetup_Nov_8?= =?utf-8?q?th=2C_2016?= Message-ID: <37356cb9-88dd-8fd3-888a-5e2b4b78daf7@objektfabrik.de> There are great news about the upcoming Smalltalker?s Meetup in Z?rich. We?ve found a conference room for the evening and will start off with a ?show us your project? session in a room with a big screen and start the social part after your input at a nice Australian Steakhouse. The best thing is: we already have a first session: Michal is going to show his new Gemstone-based persistence framework for Pharo. It can be used to develop in Pharo and keep your objects stored in Gemstone. We need your input This new setup with a meeting room adds more value to all of us: we can now not only talk about each others? epxeriences and porjects, but see what they?re up to and what they found. So to make this event an even better one than before, we need people who?d like to share their ideas, their latest work on some hobby or professional project. There?s no need for a full-fledged sales pitch with fog and visual effects and such, just bring your laptop and show us what you do! The room is reserved for ca. 1 hour, so we can have, say, 2-3 presentations before we leave for beer and steaks. So if you have something interesting to show or would like to find people to join on some early project you?re starting/planning, give us a chance to learn about it. If you?ve built some interesting tool or use Smalltalk for something very special to you, let us know and share your fascination and ideas. We?ll sure appreciate that! But if you spontaneously decide you want to show something or start some discussion, feel free to do so. You just need to be prepared that we might have to leave the room before it?s your turn. Timeslots are limited. It would be good if you?d pre-announce your demo to me for two reasons: first, we can see if we need to rent tho room for a little longer, but even better, your topic might attract even more people so I can post your topic and make sure people get the message. So where and when? We?ll meet at 7pm on Nov 8th, 2016 at Alpha Sprachwelt AG Stadelhoferstrasse 10 8001 Z?rich Around 8-8:30 pm we?ll walk over to the Outback Lodge where we?ve reserved a table. With Steaks and Drinks we can discuss ideas, talk about the good old times or do some spontaneous hacking. For directions to the Lodge visit http://www.outback-lodge.ch/index.php/stadelhofen How to register? How much is it? This is a meetup of friends, so it?s free to come, we look forward to meeting you and keeping in touch. You pay your meal and drinks, but the rest is free. We ask you to register on our Doodle page at http://doodle.com/poll/c9c7tatwqppyhkhq Please also indicate in a comment to your registration if you want to give a short presentation. See you soon in Z?rich! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161018/d5b7962e/attachment-0001.htm From johan at inceptive.be Tue Oct 18 08:00:40 2016 From: johan at inceptive.be (Johan Brichau) Date: Tue Oct 18 08:00:48 2016 Subject: [Seaside] [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> Message-ID: <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6. I will upload them as soon as I receive them Johan > On 17 Oct 2016, at 21:04, Esteban Lorenzano wrote: > > this is a question more appropriate for Seaside list :) > >> On 17 Oct 2016, at 20:07, Pierre CHANSON wrote: >> >> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x? have been removed and Seaside does not have configuration for pharo6. >> >> Is there a plan to update the configuration of Seaside ? >> >> Thanks ! >> >> Pierre and Norbert > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From johan at inceptive.be Tue Oct 18 08:11:04 2016 From: johan at inceptive.be (Johan Brichau) Date: Tue Oct 18 08:11:11 2016 Subject: [Seaside] [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> Message-ID: <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> I uploaded the changes by Christophe. If it does not work, let me know. I did not try. cheers Johan ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5 > On 18 Oct 2016, at 10:00, Johan Brichau wrote: > > Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6. > > I will upload them as soon as I receive them > > Johan > >> On 17 Oct 2016, at 21:04, Esteban Lorenzano wrote: >> >> this is a question more appropriate for Seaside list :) >> >>> On 17 Oct 2016, at 20:07, Pierre CHANSON wrote: >>> >>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x? have been removed and Seaside does not have configuration for pharo6. >>> >>> Is there a plan to update the configuration of Seaside ? >>> >>> Thanks ! >>> >>> Pierre and Norbert >> >> _______________________________________________ >> seaside mailing list >> seaside@lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > From johan at inceptive.be Tue Oct 18 08:37:52 2016 From: johan at inceptive.be (Johan Brichau) Date: Tue Oct 18 08:37:57 2016 Subject: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261 In-Reply-To: <9A1D5665-35EB-4404-A64F-B627912E947F@hartl.name> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> <9A1D5665-35EB-4404-A64F-B627912E947F@hartl.name> Message-ID: I only received a config for Grease :) In my haste, I did not check you need Seaside :) Right now, I?m a bit too busy so until someone can provide a working config, it will have to wait. cheers Johan > On 18 Oct 2016, at 10:19, Norbert Hartl wrote: > > You uploaded ConfigurationOfGrease but not Seaside. Mistake? > > Norbert > >> Am 18.10.2016 um 10:11 schrieb Johan Brichau : >> >> I uploaded the changes by Christophe. If it does not work, let me know. I did not try. >> >> cheers >> Johan >> >> ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5 >> >>> On 18 Oct 2016, at 10:00, Johan Brichau wrote: >>> >>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6. >>> >>> I will upload them as soon as I receive them >>> >>> Johan >>> >>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano wrote: >>>> >>>> this is a question more appropriate for Seaside list :) >>>> >>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON wrote: >>>>> >>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x? have been removed and Seaside does not have configuration for pharo6. >>>>> >>>>> Is there a plan to update the configuration of Seaside ? >>>>> >>>>> Thanks ! >>>>> >>>>> Pierre and Norbert >>>> >>>> _______________________________________________ >>>> seaside mailing list >>>> seaside@lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >> >> > > From cyril.ferlicot at gmail.com Tue Oct 18 13:41:32 2016 From: cyril.ferlicot at gmail.com (Cyril Ferlicot D.) Date: Tue Oct 18 13:41:52 2016 Subject: [Seaside] [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> Message-ID: Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161018/b09dd159/signature.pgp From tinchodias at gmail.com Tue Oct 18 14:00:18 2016 From: tinchodias at gmail.com (Martin Dias) Date: Tue Oct 18 14:00:40 2016 Subject: [Seaside] [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> Message-ID: After the recent change in metacelloPlatformAttributes, we're having some problems in Voyage in Pharo6, and I investigated a bit. Voyage loads Magritte3 Core stable, which uses - #version351: and - #baseline330ForPharo: These methods contain spec declarations such as #(#'pharo3.x' #'pharo4.x' #'pharo5.x'). So I guess we should add #'pharo6.x' to the list and it will just start working again. To do that, I suppose it's fine to just modify #version351: and #baseline330ForPharo:, right? I mean, no need to create a #version352:only because of that. regards, Martin On Tue, Oct 18, 2016 at 10:41 AM, Cyril Ferlicot D. < cyril.ferlicot@gmail.com> wrote: > Le 18/10/2016 ? 10:11, Johan Brichau a ?crit : > > I uploaded the changes by Christophe. If it does not work, let me know. > I did not try. > > > > cheers > > Johan > > > > ps: right now the configuration is identical for pharo5.x and pharo6.x. > If things start to fail for Pharo 6, we need to make another baseline to > not break the configuration for pharo 4 and pharo 5 > > > > Hi! > > I could load Seaside but when I start the adaptor and go to > localhost:8080 I get an error[1] `receiver of #from:to: is nil`. > There is some error on Jenkin's logs that where not here before[2]. > > > [1] http://puu.sh/rN9fV/780adbcfe0.png > [2] http://puu.sh/rN9rb/dd9de6776a.png > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 2 rue Jacques Pr?vert 01, > 59650 Villeneuve d'ascq France > > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161018/783dd004/attachment.htm From cyril.ferlicot at gmail.com Tue Oct 18 14:18:10 2016 From: cyril.ferlicot at gmail.com (Cyril Ferlicot D.) Date: Tue Oct 18 14:18:25 2016 Subject: [Seaside] [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> Message-ID: <850eb685-f7f3-3127-ed44-34891992f47b@gmail.com> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161018/fb047c50/signature-0001.pgp From johan at inceptive.be Tue Oct 18 14:32:28 2016 From: johan at inceptive.be (Johan Brichau) Date: Tue Oct 18 14:32:33 2016 Subject: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261 In-Reply-To: <16E99A17-AE5E-4EC3-B31A-FFD437923490@hartl.name> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> <9A1D5665-35EB-4404-A64F-B627912E947F@hartl.name> <16E99A17-AE5E-4EC3-B31A-FFD437923490@hartl.name> Message-ID: <717341C8-13ED-4496-8366-6DE0223E92C0@inceptive.be> Can you post the snippet how you load it? > On 18 Oct 2016, at 16:21, Norbert Hartl wrote: > > I tried to but I failed. It is very strange indeed. I added the platform attribute #'pharo6.x' to every location where there is a #'pharo5.x' attribute (see attached configuration). > When loading metacello looks into older versions as well (in this case version 3.1.6). There the platform attribute does not exist and it seems to fallback on a configuration for #pharo where a package Seaside-Pharo-Development is referenced. While trying to find the definition of that package it fails. > > Does somebody know why it behaves that weird? Or even better know a solution :) > > thanks, > > Norbert > > > >> Am 18.10.2016 um 10:37 schrieb Johan Brichau : >> >> I only received a config for Grease :) >> In my haste, I did not check you need Seaside :) >> >> Right now, I?m a bit too busy so until someone can provide a working config, it will have to wait. >> >> cheers >> Johan >> >>> On 18 Oct 2016, at 10:19, Norbert Hartl wrote: >>> >>> You uploaded ConfigurationOfGrease but not Seaside. Mistake? >>> >>> Norbert >>> >>>> Am 18.10.2016 um 10:11 schrieb Johan Brichau : >>>> >>>> I uploaded the changes by Christophe. If it does not work, let me know. I did not try. >>>> >>>> cheers >>>> Johan >>>> >>>> ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5 >>>> >>>>> On 18 Oct 2016, at 10:00, Johan Brichau wrote: >>>>> >>>>> Sure. Christophe Demarey has asked me if he can publish his changes to fix the config for pharo 6. >>>>> >>>>> I will upload them as soon as I receive them >>>>> >>>>> Johan >>>>> >>>>>> On 17 Oct 2016, at 21:04, Esteban Lorenzano wrote: >>>>>> >>>>>> this is a question more appropriate for Seaside list :) >>>>>> >>>>>>> On 17 Oct 2016, at 20:07, Pierre CHANSON wrote: >>>>>>> >>>>>>> In #SmalltalkImage>>metacelloPlatformAttributes, #'pharo5.x' #'pharo5.0.x? have been removed and Seaside does not have configuration for pharo6. >>>>>>> >>>>>>> Is there a plan to update the configuration of Seaside ? >>>>>>> >>>>>>> Thanks ! >>>>>>> >>>>>>> Pierre and Norbert >>>>>> >>>>>> _______________________________________________ >>>>>> seaside mailing list >>>>>> seaside@lists.squeakfoundation.org >>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>> >>>> >>> >>> >> >> > From Das.Linux at gmx.de Tue Oct 18 14:57:16 2016 From: Das.Linux at gmx.de (Tobias Pape) Date: Tue Oct 18 14:57:20 2016 Subject: [Seaside] [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> Message-ID: <3DF853E9-119B-4DF1-A85B-7355746D309B@gmx.de> On 18.10.2016, at 16:00, Martin Dias wrote: > After the recent change in metacelloPlatformAttributes, we're having some problems in Voyage in Pharo6, and I investigated a bit. > > Voyage loads Magritte3 Core stable, which uses > - #version351: and > - #baseline330ForPharo: > > These methods contain spec declarations such as #(#'pharo3.x' #'pharo4.x' #'pharo5.x'). So I guess we should add #'pharo6.x' to the list and it will just start working again. To do that, I suppose it's fine to just modify #version351: and #baseline330ForPharo:, right? I mean, no need to create a #version352:only because of that. No, please _do_ create a new version. The old versions should stay immutable as far as possible. Best regards -Tobias > > regards, > Martin > > > On Tue, Oct 18, 2016 at 10:41 AM, Cyril Ferlicot D. wrote: > Le 18/10/2016 ? 10:11, Johan Brichau a ?crit : > > I uploaded the changes by Christophe. If it does not work, let me know. I did not try. > > > > cheers > > Johan > > > > ps: right now the configuration is identical for pharo5.x and pharo6.x. If things start to fail for Pharo 6, we need to make another baseline to not break the configuration for pharo 4 and pharo 5 > > > > Hi! > > I could load Seaside but when I start the adaptor and go to > localhost:8080 I get an error[1] `receiver of #from:to: is nil`. > There is some error on Jenkin's logs that where not here before[2]. > > > [1] http://puu.sh/rN9fV/780adbcfe0.png > [2] http://puu.sh/rN9rb/dd9de6776a.png > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 2 rue Jacques Pr?vert 01, > 59650 Villeneuve d'ascq France > > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside From johan at inceptive.be Tue Oct 18 15:20:20 2016 From: johan at inceptive.be (Johan Brichau) Date: Tue Oct 18 15:20:24 2016 Subject: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261 In-Reply-To: <5A8A6A19-F14E-47B2-BB42-43C726B7A45D@hartl.name> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> <9A1D5665-35EB-4404-A64F-B627912E947F@hartl.name> <16E99A17-AE5E-4EC3-B31A-FFD437923490@hartl.name> <717341C8-13ED-4496-8366-6DE0223E92C0@inceptive.be> <5A8A6A19-F14E-47B2-BB42-43C726B7A45D@hartl.name> Message-ID: <8EB23CD7-7132-4985-A2B1-CD07102F7726@inceptive.be> > On 18 Oct 2016, at 16:36, Norbert Hartl wrote: > > (ConfigurationOfAster project version: #development) load There are issues with this ?old? way of Metacello loading. Can you try: Metacello new configuration:?Aster?; version: #development; load. (Maybe you need to add the repo to, don?t know). Cheers Johan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161018/95a1b5ae/attachment.htm From cyril.ferlicot at gmail.com Tue Oct 18 17:33:15 2016 From: cyril.ferlicot at gmail.com (Cyril Ferlicot D.) Date: Tue Oct 18 17:33:28 2016 Subject: [Seaside] FileLibrary in Bootstrap. Message-ID: <96947155-8643-0464-f0a0-790d8aed0702@gmail.com> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161018/2b3ff03b/signature.pgp From marianopeck at gmail.com Tue Oct 18 18:20:06 2016 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Tue Oct 18 18:20:08 2016 Subject: [Seaside] FileLibrary in Bootstrap. In-Reply-To: <96947155-8643-0464-f0a0-790d8aed0702@gmail.com> References: <96947155-8643-0464-f0a0-790d8aed0702@gmail.com> Message-ID: On Tue, Oct 18, 2016 at 2:33 PM, Cyril Ferlicot D. wrote: > Hi! > > For an application I want to use Boostrap but I do not want the optional > theme. The problem is that the optional theme is include by default in > the FileLibrary. > > Is there a way to add the FileLibrary except a file? Or should I > subclass the FileLibrary and override #selectorToIncludes? > > I normally follow that path. > -- > Cyril Ferlicot > > http://www.synectique.eu > > 2 rue Jacques Pr?vert 01, > 59650 Villeneuve d'ascq France > > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161018/9c96a953/attachment.htm From cyril.ferlicot at gmail.com Tue Oct 18 18:57:31 2016 From: cyril.ferlicot at gmail.com (Cyril Ferlicot D.) Date: Tue Oct 18 18:57:42 2016 Subject: [Seaside] Bootstrap Navbar Message-ID: <5f797e64-5bab-1a11-e2fd-28535ac663b1@gmail.com> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161018/6dffae18/signature-0001.pgp From johan at inceptive.be Thu Oct 20 17:34:04 2016 From: johan at inceptive.be (Johan Brichau) Date: Thu Oct 20 17:34:10 2016 Subject: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261 In-Reply-To: <8D9D9833-86DB-4E66-A078-308D6ECB0062@hartl.name> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> <9A1D5665-35EB-4404-A64F-B627912E947F@hartl.name> <16E99A17-AE5E-4EC3-B31A-FFD437923490@hartl.name> <717341C8-13ED-4496-8366-6DE0223E92C0@inceptive.be> <5A8A6A19-F14E-47B2-BB42-43C726B7A45D@hartl.name> <8EB23CD7-7132-4985-A2B1-CD07102F7726@inceptive.be> <8D9D9833-86DB-4E66-A078-308D6ECB0062@hartl.name> Message-ID: Done! Looked good to me, but I did not test. If anyone experiences errors, let me know! Johan > On 20 Oct 2016, at 11:39, Norbert Hartl wrote: > > Hi Johan, > > can you please upload the ConfigurationOfSeaside3 I've sent in this thread? > > thanks, > > Norbert > >> Am 18.10.2016 um 17:20 schrieb Johan Brichau >: >> >> >>> On 18 Oct 2016, at 16:36, Norbert Hartl > wrote: >>> >>> (ConfigurationOfAster project version: #development) load >> >> There are issues with this ?old? way of Metacello loading. Can you try: >> >> Metacello new >> configuration:?Aster?; >> version: #development; >> load. >> >> (Maybe you need to add the repo to, don?t know). >> >> Cheers >> Johan > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161020/c66e035d/attachment.htm From johan at inceptive.be Thu Oct 20 17:37:08 2016 From: johan at inceptive.be (Johan Brichau) Date: Thu Oct 20 17:37:13 2016 Subject: [Seaside] [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: <3DF853E9-119B-4DF1-A85B-7355746D309B@gmx.de> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> <3DF853E9-119B-4DF1-A85B-7355746D309B@gmx.de> Message-ID: > On 18 Oct 2016, at 16:57, Tobias Pape wrote: > > No, please _do_ create a new version. > The old versions should stay immutable as far as possible. Given that it?s only adding the new platform attributes because pharo6 removed it?s pharo5 attribute, I think this is OK. Am I missing anything? However, for _any_ change that needs to occur in the future in orde to be pharo6 compatible, then YES, a new version and baseline _must_ be written. cheers Johan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161020/d986a015/attachment.htm From johan at inceptive.be Thu Oct 20 17:42:27 2016 From: johan at inceptive.be (Johan Brichau) Date: Thu Oct 20 17:42:32 2016 Subject: [Pharo-users] [Seaside] Seaside can not be used with Pharo 60261 In-Reply-To: <64AA5D2E-7748-46C4-A5B6-205FD47C7AF8@hartl.name> References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> <9A1D5665-35EB-4404-A64F-B627912E947F@hartl.name> <16E99A17-AE5E-4EC3-B31A-FFD437923490@hartl.name> <717341C8-13ED-4496-8366-6DE0223E92C0@inceptive.be> <5A8A6A19-F14E-47B2-BB42-43C726B7A45D@hartl.name> <8EB23CD7-7132-4985-A2B1-CD07102F7726@inceptive.be> <64AA5D2E-7748-46C4-A5B6-205FD47C7AF8@hartl.name> Message-ID: <061AEB6F-C15D-4382-A20B-D04707D5A685@inceptive.be> I feel you pain. It is vastly underestimated how much work is required to keep up with upgrades that break backwards compatibility, from OS upgrades to Pharo upgrades and everything in between? Then again, the omelet does not make itself and certainly not without breaking the eggs ;) Johan > On 18 Oct 2016, at 17:29, Norbert Hartl wrote: > > Thanks, that worked. Feels really strange encountering this. So one cannot use the commandline handler for loading a configuration anymore. Sad! The same way sad as you cannot use versionner anymore when you start to use BaselineOf instead of ConfigurationOf. > This is not a complaint because I can understand why this happens. It is just that we need more energy to solve all this than we have. Sad! > > Norbert > >> Am 18.10.2016 um 17:20 schrieb Johan Brichau >: >> >> >>> On 18 Oct 2016, at 16:36, Norbert Hartl > wrote: >>> >>> (ConfigurationOfAster project version: #development) load >> >> There are issues with this ?old? way of Metacello loading. Can you try: >> >> Metacello new >> configuration:?Aster?; >> version: #development; >> load. >> >> (Maybe you need to add the repo to, don?t know). >> >> Cheers >> Johan > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161020/c53875c1/attachment.htm From stephan at stack.nl Fri Oct 21 08:31:59 2016 From: stephan at stack.nl (Stephan Eggermont) Date: Fri Oct 21 08:32:32 2016 Subject: [Seaside] Re: [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> <3DF853E9-119B-4DF1-A85B-7355746D309B@gmx.de> Message-ID: On 20/10/16 19:37, Johan Brichau wrote: > >> On 18 Oct 2016, at 16:57, Tobias Pape > > wrote: >> >> No, please _do_ create a new version. >> The old versions should stay immutable as far as possible. > > Given that it?s only adding the new platform attributes because pharo6 > removed it?s pharo5 attribute, I think this is OK. > Am I missing anything? > > However, for _any_ change that needs to occur in the future in orde to > be pharo6 compatible, then YES, a new version and baseline _must_ be > written. That is consistent with the way we dealt with the move from pharo4 to 5. Stephan From tinchodias at gmail.com Mon Oct 24 19:45:45 2016 From: tinchodias at gmail.com (Martin Dias) Date: Mon Oct 24 19:46:08 2016 Subject: [Seaside] Re: [Pharo-users] Seaside can not be used with Pharo 60261 In-Reply-To: References: <81C32C46-C417-4143-A1DC-F678A586B541@gmail.com> <67786F4D-02F1-4964-9BF7-2D584E63CE91@inceptive.be> <715F8B8D-3F88-497A-A2A1-5EB7AD3CE1CB@inceptive.be> <3DF853E9-119B-4DF1-A85B-7355746D309B@gmx.de> Message-ID: Finally I didn't need to change anything, since it started to work... thanks to the person that fixed it! Martin On Fri, Oct 21, 2016 at 5:31 AM, Stephan Eggermont wrote: > On 20/10/16 19:37, Johan Brichau wrote: > >> >> On 18 Oct 2016, at 16:57, Tobias Pape >> > wrote: >>> >>> No, please _do_ create a new version. >>> The old versions should stay immutable as far as possible. >>> >> >> Given that it?s only adding the new platform attributes because pharo6 >> removed it?s pharo5 attribute, I think this is OK. >> Am I missing anything? >> >> However, for _any_ change that needs to occur in the future in orde to >> be pharo6 compatible, then YES, a new version and baseline _must_ be >> written. >> > > That is consistent with the way we dealt with the move from pharo4 to 5. > > Stephan > > > > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161024/b7582e5e/attachment-0001.htm From gareth at inspired.org Mon Oct 24 20:00:34 2016 From: gareth at inspired.org (Gareth Cox) Date: Mon Oct 24 20:01:19 2016 Subject: [Seaside] Pharo/Seaside on Pi! Message-ID: <9c98eee0-b648-d7b0-512c-3367f39b8af7@inspired.org> Hi Just for fun, I've set up my Raspberry Pi 3B with Raspbian and Pharo with Seaside. Thought I'd share the success thus far! Image ----- /home/riverdusty/pharo.app/pharo.image Pharo5.0 Latest update: #50761 Unnamed Virtual Machine --------------- /home/riverdusty/pharo.app/pharo CoInterpreter VMMaker.oscog-rsf.1951 uuid: c714858a-7f63-47bd-a9ec-4bc1350eead2 Oct 20 2016 StackToRegisterMappingCogit VMMaker.oscog-rsf.1951 uuid: c714858a-7f63-47bd-a9ec-4bc1350eead2 Oct 20 2016 VM: 201610190705 https://github.com/estebanlm/opensmalltalk-vm.git $ Date: Wed Oct 19 09:05:15 2016 +0200 $ Plugins: 201610190705 https://github.com/estebanlm/opensmalltalk-vm.git $ Unix built on Oct 20 2016 07:31:59 Compiler: 4.9.2 VMMaker versionString VM: 201610190705 https://github.com/estebanlm/opensmalltalk-vm.git $ Date: Wed Oct 19 09:05:15 2016 +0200 $ Plugins: 201610190705 https://github.com/estebanlm/opensmalltalk-vm.git $ CoInterpreter VMMaker.oscog-rsf.1951 uuid: c714858a-7f63-47bd-a9ec-4bc1350eead2 Oct 20 2016 StackToRegisterMappingCogit VMMaker.oscog-rsf.1951 uuid: c714858a-7f63-47bd-a9ec-4bc1350eead2 Oct 20 2016 Operating System/Hardware ------------------------- unix linux-gnu armv7l (And for those who can see it, a screenshot) KR Dusty -------------- next part -------------- Skipped content of type multipart/related From cyril.ferlicot at gmail.com Sat Oct 29 10:32:33 2016 From: cyril.ferlicot at gmail.com (Cyril Ferlicot D.) Date: Sat Oct 29 10:32:57 2016 Subject: [Seaside] Problem with config? Message-ID: <19ccef05-aee8-8b08-9fbf-172d7de66071@gmail.com> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature Url : http://lists.squeakfoundation.org/pipermail/seaside/attachments/20161029/868e9a57/signature.pgp