Re: Plone - Again

[Ramon Navarro Bosch <ramon epsem upc edu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The basic idea is that :

Use the custom script to test something in live, it's much easier and
close to reality than making an static page. After testing you should
make the change in the svn and then I'll update.

I just updated the last changes on the svn.

Ramon

En/na Ricky Zhou ha escrit:
> Ramon Navarro Bosch wrote:
>> CSS : In order to work on the css files I recomend to log in on
>> the gnome-web ZMI ( https://edit.gnome.jardigrec.eu/manage ) I
>> created a username with manager permisions so you can go to
>>
> https://edit.gnome.jardigrec.eu/portal_skins/gnome_custom_styles/manage_main
>
>> and
>> https://edit.gnome.jardigrec.eu/portal_skins/gnome_styles/manage_main
>>  where you can select on css and make a custom copy and edit it.
>> You must remember that on the https://edit.gnome.jardigrec.eu
>> there is no cache so if you want to change css you should use
>> this url instead of http://gnome.jardigrec.eu. To get the
>> username/password please send me an email.
> Actually, now that I think about this a bit, this might conflict
> with the idea of keeping CSS/theme changes in SVN (as a side note,
> there has been some talk about possibly moving gnometheme in
> GNOME's SVN recently).  I'm kind of afraid that collaboration will
> not work as smoothly when changes aren't tracked in SVN.  Most
> projects seem to push updates at regular times, so a cronjob or
> even a post-commit hook that triggers an svn update/export would
> probably do the job nicely, if it's possible.
>
> Thanks, Ricky
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGrW6Ak3vgE06ET70RAuzIAJ0UQSHMAp3zZHgnND++EJZGYXHl/ACgjzcp
Z5LGXX7p5BsgANGO3cHN1zs=
=D8DE
-----END PGP SIGNATURE-----