Re: Antw: Re: [Envolution-devel] little resume from italian discussion

[Arden W. <ar...@li...>]

On Fri, 2003-05-30 at 09:42, Stefan Koehler wrote:
> I remember we add Oracle integration (+/- ready), new version of
>subjects, messages with outbox, personal avatar with 
> upload, expansion of user profile, new version of RTE lot of fix and
>clean code.

I want to know if
http://www.swingerz.ca/user.php?op=register&module=NS-NewUser
is possible to finish.  I put the personal avatar hack in there but
can't get the javascript correct.  I think would be nice feature for
eNvolution. Maybe need function after uid is added to the database then
tie it in with moderation screen.

> @sjah:
> 
> 1. We create a simple theme name Default as a default theme. It should be more functional rather than stylist theme, less of images except eNvo logo, 
> less of scripts, clean, white background, not grey :) and only with text links on the left column such as Home, Admin, Help etc. ... [...]
> 
> I agree. Nothing to say. You have explained it detaily ;-)

Yes I agree to make very crisp clear sharp white theme.

>On Fri, 2003-05-30 at 09:42, Stefan Koehler wrote:
> The backward compatibility to PN-modules is nice and a must-have for
>older modules. But PN and eNvo goes not the same way and the devs of
>the two CMS make changes, add several functions and recode basis code.
> It will be more and more harder to integrate PN-module (I mean newer
>and newest modules) into eNvo.
> Look on PN-CVS. They have add some new code in the API-functions. And
>the module- and 3rd-party-devs will use this now and in near future.
> So we have to find needed modules and make them compatible with eNvo.
>Problems can be, to check updates of this programs.
> 
> [...] 3. We create procedures for webmaster to configure his site for the first time installation. Such as go first to the setting, modules, blocks etc. We define two types of modules, main modules and addons modules. ... [...]
> Possible solution is an installation wizzard. Here we can define some step-by-step calls to several admin setups as you describe.
> 
> 4. To showoff the eNvo capabilites, we create layout possibilities snapshot as much as possible. Corporate style, weblog style, designers style, fancy, 

So out of all this I ask why does the install routine still try and
upgrade .64 mutant releases and others???  When do we draw the line. I
just finished upgrading my eNvo1.1 multi-site portals by hand to eNvo1.2
standards and it was big big job.  Many changes yes many.

I think the install routine should be the focal point for creating
installation wizards.  I have and want to upload to cvs some scripts
with much reiteration and instantiation of the tables to install many
sites, stories and also change many stories and settings based on the
install routine.  

To me it seems like a good idea if a user could choose options he would
like activated before or during the install routine.  If it were
possible to even configure your default stories, blocks, modules and
themes some way during the install for say corporate, personal or
organization.

Also I promote eNvolution here recently:
http://slideml.org/files/slidesets/495/title.html