Re: [Silva-general] Silva 3.0 - beta testing
Jonathan Bowlas <[email protected]> Mon, 15 Aug 2011 10:09:30 +0100
| Newsgroups | gmane.comp.web.zope.silva.devel,gmane.comp.web.zope.silva.general |
|---|---|
| Message-ID | <CAGq+fUFk7GTKwVm_B-DWmgOjUAYfHNqR=w97da+CtVN_mPDGJg@mail.gmail.com> |
--===============0533691949112128274== Content-Type: multipart/alternative; boundary=000e0cd32f321869cb04aa87a067 --000e0cd32f321869cb04aa87a067 Content-Type: text/plain; charset=ISO-8859-1 Hi Slyvain. Looking great. I'll see if I can get anyone from UCL to do a little testing. However whilst clicking around myself I noticed a bug with the Silva News Category Filter - one cannot be added without an error being returned. Cheers Jon On 15 August 2011 09:03, Sylvain Viollon <[email protected]> wrote: > > Hello, > > We are now polishing Silva 3.0, in hope to release it soon. > > In this major version, we completely rebuild the SMI, using ajax > technologies, to make it a lot faster, > specially for sites with lot of content. > > It would be great to have beta tester that help us to identify the last > bugs in order to clear them out. > If you have a bit of free time and want to contribute, it would be great ! > Please contact me if you wish > to be beta tester. > > Major changes includes: > > - A new SMI interface (still themable), > > - A new document type with a new editor, that integrate links and images > references and code > sources, like Kupu used to do. > > A demo site is available at http://demo30.silvacms.org/ > > Extension / product changes > --------------------------------------- > > The following products have been removed: > > - Products.SilvaViews > > - Products.FileSystemDirectory > > - Products.Kupu > > - silva.resourceinclude > > After migration: > > - Products.SilvaDocument > > - Products.SilvaNews > > - Products.ParsedXML > > The following extension have been added: > > - silva.ui (SMI UI code. All the SMI forms are still defined in > silva.core.smi). > > - silva.core.editor (Integration of CKEditor, with link, image, anchor > plugins, configuration service) > > - silva.app.document (new document type) > > - silva.app.news (new news product based on the new document type) > > - silva.fanstatic (this is a new system to include resources based on > fanstatic. It is 100% backward compatible > with the old one, and provide a better merging support, minified > support, and more flexibility to include resources > in only a view or a page). > > The SMI is still themable, however the 2.3 SMI theme won't work with Silva > 3.0 (since the code is completely > different). > > Code source changes > ------------------------------ > > Code sources have been improved. The code source service now tracks all > usable code sources present in your > Silva site, and let you quickly identify broken ones. On the code sources > those improvements have been > implemented: > > - The LookupField have been replaced by a ReferenceField, that let you > pick a content the same, but store > it as a reference instead of a path, so if the document or the target > move, the value won't be broken. > > - All values are provided to the code source in the correct format: an > integer is an integer, a boolean is a boolean, > a reference the referred object. > > - If no value was inputed by the user, the default is correctly provided > to the source. > > - IMPORTANT: request.model is not used and available in Silva anymore. You > should use the parameters > model and version that are given to the source. This was causing lot of > bugs and trouble when sources > played with this request data. > > Installation from the file system of sources have been simplified. It is > now really easy to write your sources on the > filesystem in your extension and refresh them in ZMI. > > Upgrading to 3.0 > ----------------------- > > You need first to update your custom code in order to have it work in an > empty Silva site. silva.core.layout layouts > didn't change at all, it should work by default. Silva Legacy layouts (in > ZODB) doesn't work anymore. > > Since SilvaViews is not used anymore, the only way to define a content is > to define an add and edit form using > zeam.form.silva, and define a public view using silva.core.views. If you > already updated your content to use > those techniques in Silva 2.3, you won't have anything to change either. > > If you didn't do any of those tasks for your upgrade to Silva 2.3, you > will have to do it for Silva 3.0. > > After for the contnet migration, the conversion script correctly create > new document type out of the old one, > storing links, images and sources correctly (as well for Silva news). > However if you wish to upgrade to Silva 3.0 > you will have to upgrade first to Silva 2.3. After running the first part > of the upgrade (the zodbupdate script), > you have to start Zope and fix the code sources parameters form of all > code sources so the document migration > can work. The new screens of the code source service can help you to > achieve this. After code sources works, > you can resume the migration using the silvaupdate script. > > Silva 3.0 uses Python 2.7 and Zope 2.13. > > If you have any question, don't hesitate to contact me, or reply to this > email. > > Regards, > > Sylvain, > > -- > Sylvain Viollon -- Infrae > t +31 10 243 7051 -- http://infrae.com > Hoevestraat 10 3033GC Rotterdam -- The Netherlands > > > > _______________________________________________ > silva-general mailing list > silva-general-IAPFreCvJWM6s/[email protected] > https://lists.infrae.com/mailman/listinfo/silva-general > --000e0cd32f321869cb04aa87a067 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Slyvain.<br><br>Looking great. I'll see if I can get anyone from UCL= to do a little testing.<br><br>However whilst clicking around myself I not= iced a bug with the Silva News Category Filter - one cannot be added withou= t an error being returned.<br> <br>Cheers<br><br>Jon<br><br><div class=3D"gmail_quote">On 15 August 2011 0= 9:03, Sylvain Viollon <span dir=3D"ltr"><<a href=3D"mailto:sylvain@infra= e.com">[email protected]</a>></span> wrote:<br><blockquote class=3D"gma= il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef= t:1ex;"> <br> Hello,<br> <br> =A0 We are now polishing Silva 3.0, in hope to release it soon.<br> <br> =A0 In this major version, we completely rebuild the SMI, using ajax techn= ologies, to make it a lot faster,<br> =A0 specially for sites with lot of content.<br> <br> =A0It would be great to have beta tester that help us to identify the last= bugs in order to clear them out.<br> =A0If you have a bit of free time and want to contribute, it would be grea= t ! Please =A0contact me if you wish<br> =A0to be beta tester.<br> <br> =A0Major changes includes:<br> <br> =A0- A new SMI interface (still themable),<br> <br> =A0- A new document type with a new editor, that integrate links and image= s references and code<br> =A0 =A0sources, like Kupu used to do.<br> <br> =A0A demo site is available at <a href=3D"http://demo30.silvacms.org/" tar= get=3D"_blank">http://demo30.silvacms.org/</a><br> <br> =A0Extension / product changes<br> =A0---------------------------------------<br> <br> =A0The following products have been removed:<br> <br> =A0- Products.SilvaViews<br> <br> =A0- Products.FileSystemDirectory<br> <br> =A0- Products.Kupu<br> <br> =A0- silva.resourceinclude<br> <br> =A0After migration:<br> <br> =A0- Products.SilvaDocument<br> <br> =A0- Products.SilvaNews<br> <br> =A0- Products.ParsedXML<br> <br> =A0The following extension have been added:<br> <br> =A0- silva.ui (SMI UI code. All the SMI forms are still defined in silva.c= ore.smi).<br> <br> =A0- silva.core.editor (Integration of CKEditor, with link, image, anchor = plugins, configuration service)<br> <br> =A0- silva.app.document (new document type)<br> <br> =A0- silva.app.news (new news product based on the new document type)<br> <br> =A0- silva.fanstatic (this is a new system to include resources based on f= anstatic. It is 100% backward compatible<br> =A0 =A0with the old one, and provide a better merging support, minified su= pport, and more flexibility to include resources<br> =A0 =A0in only a view or a page).<br> <br> =A0The SMI is still themable, however the 2.3 SMI theme won't work wit= h Silva 3.0 (since the code is completely<br> =A0different).<br> <br> =A0Code source changes<br> =A0------------------------------<br> <br> =A0Code sources have been improved. The code source service now tracks all= usable code sources present in your<br> =A0Silva site, and let you quickly identify broken ones. On the code sourc= es those improvements have been<br> =A0implemented:<br> <br> =A0- The LookupField have been replaced by a ReferenceField, that let you = pick a content the same, but store<br> =A0 =A0 it as a reference instead of a path, so if the document or the tar= get move, the value won't be broken.<br> <br> =A0- All values are provided to the code source in the correct format: an = integer is an integer, a boolean is a boolean,<br> =A0 =A0a reference the referred object.<br> <br> =A0- If no value was inputed by the user, the default is correctly provide= d to the source.<br> <br> =A0- IMPORTANT: request.model is not used and available in Silva anymore. = You should use the parameters<br> =A0 =A0model and version that are given to the source. This was causing lo= t of bugs and trouble when sources<br> =A0 =A0played with this request data.<br> <br> =A0Installation from the file system of sources have been simplified. It i= s now really easy to write your sources on the<br> =A0filesystem in your extension and refresh them in ZMI.<br> <br> =A0Upgrading to 3.0<br> =A0-----------------------<br> <br> =A0You need first to update your custom code in order to have it work in a= n empty Silva site. silva.core.layout layouts<br> =A0 didn't change at all, it should work by default. Silva Legacy layo= uts (in ZODB) doesn't work anymore.<br> <br> =A0 Since SilvaViews is not used anymore, the only way to define a content= is to define an add and edit form using<br> =A0 zeam.form.silva, and define a public view using silva.core.views. If y= ou already updated your content to use<br> =A0 those techniques in Silva 2.3, you won't have anything to change e= ither.<br> <br> =A0 If you didn't do any of those tasks for your upgrade to Silva 2.3,= you will have to do it for Silva 3.0.<br> <br> =A0After for the contnet migration, the conversion script correctly create= new document type out of the old one,<br> =A0storing links, images and sources correctly (as well for Silva news). H= owever if you wish to upgrade to Silva 3.0<br> =A0you will have to upgrade first to Silva 2.3. After running the first pa= rt of the upgrade (the zodbupdate script),<br> =A0you have to start Zope and fix the code sources parameters form of all = code sources so the document migration<br> =A0can work. The new screens of the code source service can help you to ac= hieve this. After code sources works,<br> =A0you can resume the migration using the silvaupdate script.<br> <br> =A0Silva 3.0 uses Python 2.7 and Zope 2.13.<br> <br> =A0If you have any question, don't hesitate to contact me, or reply to= this email.<br> <br> =A0Regards,<br> <br> =A0Sylvain,<br> <br> --<br> Sylvain Viollon -- Infrae<br> t <a href=3D"tel:%2B31%2010%20243%207051" value=3D"+31102437051">+31 10 243= 7051</a> -- <a href=3D"http://infrae.com" target=3D"_blank">http://infrae.= com</a><br> Hoevestraat 10 3033GC Rotterdam -- The Netherlands<br> <br> <br> <br> _______________________________________________<br> silva-general mailing list<br> <a href=3D"mailto:silva-general-IAPFreCvJWM6s/[email protected]">[email protected]= e.com</a><br> <a href=3D"https://lists.infrae.com/mailman/listinfo/silva-general" target= =3D"_blank">https://lists.infrae.com/mailman/listinfo/silva-general</a><br> </blockquote></div><br><div style=3D"visibility: hidden; left: -5000px; pos= ition: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top:= 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10p= x; text-align: left; line-height: 130%;" id=3D"avg_ls_inline_popup"> </div> --000e0cd32f321869cb04aa87a067-- --===============0533691949112128274== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ silva-dev mailing list silva-dev-IAPFreCvJWM6s/[email protected] https://lists.infrae.com/mailman/listinfo/silva-dev --===============0533691949112128274==--