Skeleton App components

[gianarb]

Hello Guys!

Idea around the best components to build this skeleton application? :)

• php-di
• event-manager
• diactoros

and.. ? :)

• Twig
• doctrine
• monolog

Develop

• VarDump
• filp/whoops

[gianarb]

@EmanueleMinotto can you help me to understand Puli? :)
maybe it could be a good solution to load external components here.

[samsonasik]

twig and filp/whoops ;)

[samsonasik]

but plates is ok

[EmanueleMinotto]

@gianarb sure, ping me on hangout when you want :)
I don't know what you mean with "components", just be aware that Puli is more about resources (not only assets, but no PHP logic, there are PSRs for the PHP logic).

[samsonasik]

@gianarb time for fast-eventmanager usage?

[gianarb]

Yes we must replace it in penny..

Maybe we can write a layer to use it in penny.. :) What do you think?

[samsonasik]

Did you mean layer means separate repo? if yes, then I prefer just use it
in penny repo instead, many repo - many effort to maintain.

Warm Regards,

Abdul Malik Ikhsan

2015-11-10 15:07 GMT+07:00 Gianluca Arbezzano notifications@github.com:

Yes we must replace it in penny..

Maybe we can write a layer to use it in penny.. :) What do you think?

—
Reply to this email directly or view it on GitHub
#40 (comment)
.

[gianarb]

At the moment doesn't exist a good structure to change the event manager, you can replace it by DiC but without a guarantee because doesn't exist interface/s on this implementation :)

[fntlnz]

👍 for php-di + doctrine + twig :)

[gianarb]

many repo - many effort to maintain

@samsonasik too easy! There are a lot of words to spend about this topic.. :)

If we create separate repositories we remove event-manager dependency by penny and every developer can choose your best implementation.

An intermediate project, between Zend\EventManager and penny or between FastEventManager and penny is necessary because penny will require an interface to work with different evm implementations.

for example

<?php
use Penny\Event\PennyEventInterface;

interface PennyEVMInterface
{
    public function trigger($eventName, PennyEventInterface $event);
    public function attach($eventName, callable $listener);
}

To guarantee the correct flow of every evm implementations.

[samsonasik]

Ok ;)

Warm regards,

Abdul Malik Ikhsan

Pada 11 Nov 2015, pukul 08.02, Gianluca Arbezzano notifications@github.com menulis:

many repo - many effort to maintain

@samsonasik too easy! There are a lot of words to spend about this topic.. :)

If we create separate repositories we remove event-manager dependency by penny and every developer can choose your best implementation.

An intermediate project, between Zend\EventManager and penny or between FastEventManager and penny is necessary because penny will require an interface to work with different evm implementations.

for example