Hi All,
some quick ideas/todo for the website: - collecting and adding illustrations to main page - removing icons from footer (this is how to edit the footer: http://www.contentmanagementsoftware.info/plone-book/editfooter/index_html) - removing pd webring from sidebar - eventually some further tuning of the CSS (visited links' colors, etc.) - testing and making adjustments for mobile browsers (not only for width; seems that for mobiles the old template is applied!) - rethinking main menu? - upgrading Plone (in a sandbox first)
please add your thoughts
András
On 04/24/2013 22:08, András Murányi wrote:
Hi All,
some quick ideas/todo for the website:
- collecting and adding illustrations to main page
- removing icons from footer (this is how to edit the footer:
http://www.contentmanagementsoftware.info/plone-book/editfooter/index_html)
whatever one does, please don't "customize" anything before checking whether there's already a customized version of the given file in portal_skins/custom/
plone history is not very good in the backend.
vhvmdsf IOhannes
thanks IOhannes, that's good to know!
Andras, good items there. I think that's most of the important stuff to look at shortly. As for the mobile version, I do see the new template on my Nexus 4, all looks good :)
with which device have you tried?
-- Marco Donnarumma New Media + Sonic Arts Practitioner, Performer, Teacher, Director. Embodied Audio-Visual Interaction Research Team. Department of Computing, Goldsmiths University of London ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Portfolio: http://marcodonnarumma.com Research: http://res.marcodonnarumma.com Director: http://www.liveperformersmeeting.net
On Thu, Apr 25, 2013 at 9:00 AM, IOhannes m zmölnig zmoelnig@iem.at wrote:
On 04/24/2013 22:08, András Murányi wrote:
Hi All,
some quick ideas/todo for the website:
- collecting and adding illustrations to main page
- removing icons from footer (this is how to edit the footer:
http://www.contentmanagementsoftware.info/plone-book/editfooter/index_html )
whatever one does, please don't "customize" anything before checking whether there's already a customized version of the given file in portal_skins/custom/
plone history is not very good in the backend.
vhvmdsf IOhannes
Pdweb mailing list Pdweb@iem.at http://lists.puredata.info/listinfo/pdweb
On Sat, Apr 27, 2013 at 4:28 PM, Marco Donnarumma devel@thesaddj.comwrote:
thanks IOhannes, that's good to know!
Andras, good items there. I think that's most of the important stuff to look at shortly. As for the mobile version, I do see the new template on my Nexus 4, all looks good :)
with which device have you tried?
Well it's an el cheapo IPhone emulator called iBBDemo3. It's an Adobe Air app, so maybe this is a stupid caching issue? The looks alrite with the Android emulator. Got no real smartphone ;)
András
Hello all,
I think the main question is concerning the upgrade of plone. Shall we upgrade or not? If we want to upgrade the website, many modifications will be made another way (css, footer, ...) and really simpler, so I'm not sure they are useful to work on now. But as we have discussed before the upgrade is a complex process, and Iohannes has to be involved for a few key operations.
here is a copy of one of my mail of last november, that is still pertinent: -- 1 - installing a new hidden plone. 2 - thinking the architecture of the new site 3 - filling the architecture with the "old" content 4 - graphical design of the new site 5 - filling the website with member contents 6 - checking and switching to the new version.
A proposal on how we should do that: step 1 : handled by Iohannes/Andras? step 2 : discussion on this list step 3 : handled by section responsables (if we agree on this kind of organisation) step 4 : discussion on this list and marco's implementation. step 5 : maybe we can send a mail to every member of the actual site to have them move their own content? step 6 : pdweb-list and maybe pd-list help.
I think it's no problem if we have all this switching lasting a few months. The longest step for me is step 5, and I think it's really better if we let a long time to people to switch their content. An intermediate part of the website between members and architecture is the community section, where it is good to have people create their own page for patching circles and others. I am ok to write a little tutorial to achieve an homogen creation of specific pages, and to write individual mails to each local groups member. --
I think it's a very important point to upgrade plone, for now and future years... best, n
Le 24/04/13 22:08, András Murányi a écrit :
Hi All,
some quick ideas/todo for the website:
- collecting and adding illustrations to main page
- removing icons from footer (this is how to edit the footer:
http://www.contentmanagementsoftware.info/plone-book/editfooter/index_html)
- removing pd webring from sidebar
- eventually some further tuning of the CSS (visited links' colors, etc.)
- testing and making adjustments for mobile browsers (not only for
width; seems that for mobiles the old template is applied!)
- rethinking main menu?
- upgrading Plone (in a sandbox first)
please add your thoughts
András
Pdweb mailing list Pdweb@iem.at http://lists.puredata.info/listinfo/pdweb
On Sun, Apr 28, 2013 at 9:50 AM, Nicolas Montgermont < nicolas_montgermont@yahoo.fr> wrote:
Hello all,
I think the main question is concerning the upgrade of plone. Shall we upgrade or not? If we want to upgrade the website, many modifications will be made another way (css, footer, ...) and really simpler, so I'm not sure they are useful to work on now. But as we have discussed before the upgrade is a complex process, and Iohannes has to be involved for a few key operations.
here is a copy of one of my mail of last november, that is still pertinent:
1 - installing a new hidden plone. 2 - thinking the architecture of the new site 3 - filling the architecture with the "old" content 4 - graphical design of the new site 5 - filling the website with member contents 6 - checking and switching to the new version.
A proposal on how we should do that: step 1 : handled by Iohannes/Andras? step 2 : discussion on this list step 3 : handled by section responsables (if we agree on this kind of organisation) step 4 : discussion on this list and marco's implementation. step 5 : maybe we can send a mail to every member of the actual site to have them move their own content? step 6 : pdweb-list and maybe pd-list help.
I think it's no problem if we have all this switching lasting a few months. The longest step for me is step 5, and I think it's really better if we let a long time to people to switch their content. An intermediate part of the website between members and architecture is the community section, where it is good to have people create their own page for patching circles and others. I am ok to write a little tutorial to achieve an homogen creation of specific pages, and to write individual mails to each local groups member. --
I think it's a very important point to upgrade plone, for now and future years... best, n
Thinking about this, a reasonable approach could be to upgrade before/instead of putting more work into the old site. The upgrade shall go as described by Nicholas, which means that in practice it will be a migration rather than an upgrade. Whenever IOhannes (1.) installs a blank copy of the newest Plone anywhere on the server, and eventually (2.) gives us read-only access to the old database and (3.) read-write access to the new database, we can start playing around without any risk involved.
András
On 04/28/2013 05:32 PM, András Murányi wrote:
Whenever IOhannes (1.) [...]
bien sur.
but in 10 days from now, the LAC will start in Graz, and this will keep me busy till then :-)
fgmasdrt IOhannes
i meant "whenever" literally :-) this is really not something of urgency anyway, thanks in advance!
András
On Sun, Apr 28, 2013 at 10:27 PM, IOhannes zmölnig zmoelnig@iem.at wrote:
On 04/28/2013 05:32 PM, András Murányi wrote:
Whenever IOhannes (1.) [...]
bien sur.
but in 10 days from now, the LAC will start in Graz, and this will keep me busy till then :-)
fgmasdrt IOhannes
______________________________**_________________ Pdweb mailing list Pdweb@iem.at http://lists.puredata.info/**listinfo/pdwebhttp://lists.puredata.info/listinfo/pdweb
IOhannes, perhaps we can have a chat about it over a beer during LAC! :P
-- Marco Donnarumma New Media + Sonic Arts Practitioner, Performer, Teacher, Director. Embodied Audio-Visual Interaction Research Team. Department of Computing, Goldsmiths University of London ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Portfolio: http://marcodonnarumma.com Research: http://res.marcodonnarumma.com Director: http://www.liveperformersmeeting.net
On Sun, Apr 28, 2013 at 6:06 PM, András Murányi muranyia@gmail.com wrote:
i meant "whenever" literally :-) this is really not something of urgency anyway, thanks in advance!
András
On Sun, Apr 28, 2013 at 10:27 PM, IOhannes zmölnig zmoelnig@iem.atwrote:
On 04/28/2013 05:32 PM, András Murányi wrote:
Whenever IOhannes (1.) [...]
bien sur.
but in 10 days from now, the LAC will start in Graz, and this will keep me busy till then :-)
fgmasdrt IOhannes
______________________________**_________________ Pdweb mailing list Pdweb@iem.at http://lists.puredata.info/**listinfo/pdwebhttp://lists.puredata.info/listinfo/pdweb
Pdweb mailing list Pdweb@iem.at http://lists.puredata.info/listinfo/pdweb
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-05-01 21:38, Marco Donnarumma wrote:
IOhannes, perhaps we can have a chat about it over a beer during LAC! :P
now that's a very optimistic view of my availability during the conference :-)
let's see.
fgamsdr IOhannes
On 04/28/2013 11:32 AM, András Murányi wrote:
On Sun, Apr 28, 2013 at 9:50 AM, Nicolas Montgermont < nicolas_montgermont@yahoo.fr> wrote:
Hello all,
I think the main question is concerning the upgrade of plone. Shall we upgrade or not? If we want to upgrade the website, many modifications will be made another way (css, footer, ...) and really simpler, so I'm not sure they are useful to work on now. But as we have discussed before the upgrade is a complex process, and Iohannes has to be involved for a few key operations.
here is a copy of one of my mail of last november, that is still pertinent:
1 - installing a new hidden plone. 2 - thinking the architecture of the new site 3 - filling the architecture with the "old" content 4 - graphical design of the new site 5 - filling the website with member contents 6 - checking and switching to the new version.
A proposal on how we should do that: step 1 : handled by Iohannes/Andras? step 2 : discussion on this list step 3 : handled by section responsables (if we agree on this kind of organisation) step 4 : discussion on this list and marco's implementation. step 5 : maybe we can send a mail to every member of the actual site to have them move their own content? step 6 : pdweb-list and maybe pd-list help.
I think it's no problem if we have all this switching lasting a few months. The longest step for me is step 5, and I think it's really better if we let a long time to people to switch their content. An intermediate part of the website between members and architecture is the community section, where it is good to have people create their own page for patching circles and others. I am ok to write a little tutorial to achieve an homogen creation of specific pages, and to write individual mails to each local groups member. --
I think it's a very important point to upgrade plone, for now and future years... best, n
Thinking about this, a reasonable approach could be to upgrade before/instead of putting more work into the old site. The upgrade shall go as described by Nicholas, which means that in practice it will be a migration rather than an upgrade. Whenever IOhannes (1.) installs a blank copy of the newest Plone anywhere on the server, and eventually (2.) gives us read-only access to the old database and (3.) read-write access to the new database, we can start playing around without any risk involved.
I think upgrading plone would be super valuable, thank y'all for leading this effort! I guess my only concern with this plan, as someone who used to do quite a few upgrades of this sort 10+ years ago, is that a migration would be massively labor intensive.
Does plone have migration tools to smooth that process? There should be an "upgrade path" for the current plone install.
.hc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2013-05-08 03:01, Hans-Christoph Steiner wrote:
Does plone have migration tools to smooth that process? There should be an "upgrade path" for the current plone install.
in theory there is. in practice it is not so simple, since: - - the plone instance on pd.info is about 10 years old (probably more). there have been several major releases since then, and python is not what it used to be (pd-portal is running on python2.3/2.4!!!) - - there are a number of products installed on the portal that are no longer developped/supported, so they lack migration paths
there's a small ray of hope, by exporting the database into an intermediate format (zexp), but it will require a lot of work.
alternatively, it might be possible to dump the database via webdav to a filesystem and re-import it (worrying about ownership and permissions LATER)
fgamsdr IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 05/08/2013 04:53 AM, IOhannes m zmoelnig wrote:
On 2013-05-08 03:01, Hans-Christoph Steiner wrote:
Does plone have migration tools to smooth that process? There should be an "upgrade path" for the current plone install.
in theory there is. in practice it is not so simple, since: - the plone instance on pd.info is about 10 years old (probably more). there have been several major releases since then, and python is not what it used to be (pd-portal is running on python2.3/2.4!!!) - there are a number of products installed on the portal that are no longer developped/supported, so they lack migration paths
there's a small ray of hope, by exporting the database into an intermediate format (zexp), but it will require a lot of work.
alternatively, it might be possible to dump the database via webdav to a filesystem and re-import it (worrying about ownership and permissions LATER)
fgamsdr IOhannes
Ok, makes sense. Migration is the way forward! I guess ownership should be quite easy since everything should be editable by logged in users except for member folders. Since member folders are named after the username, that makes it easy to set the ownership.
.hc
-
András Murányi -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
IOhannes zmölnig
-
Marco Donnarumma -
Nicolas Montgermont