Re: [Envolution-devel] org. questions... talk with me

[<s.k...@pr...>]

@TiMax:

[...] >  I mean: For better developement of all parts of eNvo (core,
>   module, 3rd-party) we need a Lead Developer, who coordinates all other
devs
>   and delegate things. Look into the document. The description there is
perfect.
>   Also it would be a nice idea, to create local dev-teams (and a Local
Lead
>   Developer). Because perhaps the priorities of eNvo-features
>   differs (users in USA need other features as users in
>   Germany).

i agree ..
who have time  to be our Lead Develper ? [...]

We have to talk about it. What do you think?

[...] >  As we can see on "eNvo network" we have many local sites in
>   many countries. All sites are authonom. This is OK. But it would be
nice, if
>   we can link together some parts of eNvo, i.e. Downloads, Weblinks, some
>   support forum desks. So I can see on eNvo.de, if there is a new upload
on
>   eNvo.com.

i don't agree with that, i already try with this features but not work ....
it not work because is too different for example Italian and english
language,
so sometimes some upload are specifi for Italian users and is not good
for other people. I think is better to have channel or mailing list
dedicated to
all support sites, so all responsables can write in this mailing list all
news,
new download etc other responsable can read it translate it and put in his
download section. [...]

I agree. This is what I meant. I don't want to create a new overall database
for this infos. I think it is enough to create blocks with Links in it,
which lists all new entries of several sites. The idea of backend.php behind
news is the way we can realize it. Because on eNvo.de there are some
fixes/updates (i.e. Banners, RTE, users-system), which are not found on
eNvo.com or eNvo.it (or vise versa). But it would be also interest for
international users.
So, which I would have to do, would be, to upload my fixes on all local
sites (and have to update, if there would be changes). Crazy......
Other solution is, to upload all these files central on eNvo.com and
announce it via backend-block.

[...] I agree .... i see also in PN they changed all credits visible with
credits module to last developer, and i think is
correct to change it also for us, maybe i change it tomorrow, because i
think is correct to have public credit and
contact about last developer work around module, block etc ..... [...]

Good idea. Do it.

[...] >  To produce a final version of eNvo (Version 1.3 ?) we need a
>   identical "look-and-feel" in all core modules. At this time, the layout
of
>   News, Comments, Reviews, Downloads, Weblinks, etc. differs. Possible to
>   coordinate it. Also we can centralize some parts of code into a
secondary API,
>   which will only load if modules needed (not every loadtime as the
pnAPI). Here
>   we can include functions and programs i.e. PopUps, Select-Boxes,
Colorpicker,
>   Imagepicker, DateTime-converter, etc.

i agree ... and we need to write some code rules also [...]

Yes. We need code rules. The module "template" is a good idea to begin a new
module-project, but not enough. For module devs we need some more
informations. For that, I think I start with a secondary API and include
some public functions there, which can be used from several modules. For
example, the colorpicker is a good starting point for sharing functionality
all over eNvo-system.
Then we can write a developer-guidance, which explains what functions there
(in general and secondary API) and how to design the code to get a
wellformed certified eNvo-module.

WindMeUp