[livesupport-dev] "Component-izing" LS components
  • Vote Up0Vote Down importimport
    Posts: 0Member
    Hi all,

    In the recent discussions about the Localizer and other components, I
    wanted to remind you that at one point this spring we were going to try to
    'release' the PHP-based LiveSupport components to the PEAR repository,
    especially the storageServer.

    Tomas did some work in this direction, but I'm not sure where it ended up,
    so I'd like to ask: What ever happened with that? Are the components ready
    to go, and if not, how much work would it take to get them ready?

    A larger question is whether you think this should be done for other
    components as well, such as the Localizer? Can it be component-ized into a
    PEAR module?

    doug

    =============================================
    Media Development Loan Fund
    =============================================
    Douglas Arellanes
    Head of Research and Development
    Center for Advanced Media--Prague (CAMP)
    Na vinicnich horach 24a/1834, 160 00 Prague 6
    Czech Republic
    Tel: + 420 2 3333 5356, Fax: +420 2 2431 5419
    Mobile: +420 724 073 364
    http://www.mdlf-camp.net
    http://www.campware.org
    =============================================
    http://www.mdlf.org
    =============================================
  • 1 Comment sorted by
  • Vote Up0Vote Down importimport
    Posts: 0Member
    On Fri, 7 Oct 2005 11:08:22 +0200 Douglas.Arellanes@mdlf.org wrote:
    > Hi all,
    >
    > In the recent discussions about the Localizer and other components, I
    > wanted to remind you that at one point this spring we were going to try to
    > 'release' the PHP-based LiveSupport components to the PEAR repository,
    > especially the storageServer.
    >
    > Tomas did some work in this direction, but I'm not sure where it ended up,
    > so I'd like to ask: What ever happened with that? Are the components ready
    > to go, and if not, how much work would it take to get them ready?
    >
    > A larger question is whether you think this should be done for other
    > components as well, such as the Localizer? Can it be component-ized into a
    > PEAR module?
    >
    > doug

    Unfortunately there always have been issues with higher priority than
    PEARisation (debugging, new features, meetings) and probably still are
    now.

    If there is some reason for increase priority of PEARisation at the
    expense of something other, we could do some priority changes now after
    release 1.

    BTW: But the first thing is PEARisation of alib (before storageServer),
    because there is a strong relation between alib and storageServer's
    classes.

    Tomas Hlava
    th@red2head.com
Add a Comment