RE: [Envolution-devel] File Prefix's

[Andrei K. <ak...@ho...>]

Hi guys,

First of all, this comment is not addressed to anyone in particular.
Thus, it should not be taken as any sort of personal attack.

Now, here is what I think about Envo and PN in their current (released)
state. Both are platforms, and provide common features, like user
management, multi-lingual interface and consistent themes. THAT IS IT!
Oh yeah, and one "integrated" application on top of that, called News!
So, IMHO, at the moment Envo = PN = News module. Most other differences
are in presentation layer. BTW, how many Envo installations disable News
module or at least do not make it the default one? And even this "core"
module is NOT pnAPI (or any other API) compliant. On the other hand, 3rd
party modules that are announced on Envo and PN sites most of the time
claim to be 100% pnAPI (an exception might be pnHTML, but it is a
completely different story). The reason is simple, PN (and its forks)
had promised to support all modules that are pnAPI compliant. So, IMHO,
it is of paramount importance for Envo to support pnAPI as it promised
(if technically feasible, of course). On the other hand, I am all for
"new" envAPI (or whatever we call it). It should take good ideas from
pnAPI and add new features that will make creating modules for Envo
easier and less time consuming. What I don't understand is why we still
don't have Comments API or Ratings API or Notification API. I am sure
most 3rd party developers would love to use these APIs in their own
modules. After all, API is THE ONLY WAY for modules (blocks, or anything
else) to interact with Envo. The same goes for Workflow. And Categories,
and everything else. The question is, do we make a "bridge" between
pnAPI and envAPI? I think not. This is not our job to integrate PN based
modules with all the features Envo can provide. All we ever promised is
that PN modules will not break because some of pn-something functions
can't be found on an envo install. Furthermore, I would suggest we make
all compatibility things into separate downloads, and make sure that
users understand that by using them we can't guarantee that Envo install
with these add-ons will perform as fast as the "clean" one. Think of it
as Wine on Linux. You only use it when there is no alternative, period.


Best Regards,

ak