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

[Stefan K. <Ste...@ga...>]

[...] we talk about number of next release,  me and some of us think 1.2.1 =
is not good because we add some feautures in this=20
release and for that we need to show it in our number release maybe with =
1.2.5
I remember we add Oracle integration (+/- ready), new version of subjects, =
messages with outbox, personal avatar with=20
upload, expansion of user profile, new version of RTE lot of fix and clean =
code. [...]

I agree. We can tell people we have 4 internal (unofficial) releases ( .1 =
to .4) and will public the stable release 1.2.5
But, I think, for oracle integration we need some more time.

[...] we talk about our chaos code for css, styles, classes etc ....=20
about that Tchichi and @ngelspike work to clean code, to prepare list of =
class we must use in modules and core, so all people use same class when =
write modules, blocks or themes, they want to release public list in next =
days.
Tchichi work also to check, delete or remplace deprecated class in our =
code [...]

Ah. Two new names: Tchichi and @ngelspike are developers? Or designers? Or =
what?
Please remember my points of view. I talk about developers, and I meant =
workers for the core and basis eNvo system.
I think you mix on italian discussion all we have to do in core AND =
design. But we have to share tasks. We need persons for both parts and we =
have to group them into different teams:
1. Core-Dev: Make code stable and wellformed
2. Core-Dev: Re-code some parts of core modules to get same look-and-feel =
(Input- and output-masks, not theme design)
3. Core-Dev: check classes (i.e. pnAPI, pnHTML, ...)
4. Core-Dev: create new classes and functions for use in several modules
5. Core-Dev: Optimize and clean core to make it faster and eliminate =
overheads (code not needed)

6. Themes-Dev: Check CSS and modify it
7. Themes-Dev: Create a basic, non-grafical theme to check module =
functions and system integritiy (i.e. for module devs.)
8. Themes-Dev: Check existing themes (Experience, Borobudur, Michelangelo).=
 It seems, that there are some bugs.
9. Themes-Dev: Write docus and descriptions how to use Encompass (Smarty), =
modify existing themes and create themes on basis of Experience or =
Borobudur (I know this is under process).

... to be continued


[...]We all agree to keep compatiblity with modules and blocks Postnuke, =
and sure after next release we can take time to check and clean some =
modules for eNvolution [...]

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.

[...] I think also we need to promote explain promote explain and explain =
promote eNvolution to let know people and graphic men power of envolution =
and what they can make  with eNvolution, we need to have themes themes .. =
[...]

I agree. This is part of Support- and Themes-Dev-Team.

[...] About modules and blocks i just put online www.envoaddon.com, that =
want to be our demo site where we can show modules, blocks addons show =
with envolution,... [...]

Good work. We need it.

[...] Maybe we can think also about something like xaraya, one repository =
where we or developer can assign number for each module and let know =
people about what he mean develope and status of developement.[...]

This is, what I want installate with my ToDo-module. And we can combine it =
with "credits" and "envoDev".

WindMeUp