[FLOW3-general] Best Practice for a plugin-based app in flow3

[Andreas Förthner]

Hi Chris,

I'll try to answer the role part ;-) As you already said the roles are app
wide, but this is completely fine as this part will probably never be
dynamic. What I think you want to do dynamically is assigning those app
wide roles to user accounts. That means an account will have different
roles based on some context. The easiest way to achieve this would be your
own account model extending the FLOW3 account and implement this magic
there. Of course you will have to find some good way to define so dynamic
rules for your accounts.

I hope I got you right and could help for a start. And well, as soon as
you have this implemented I'm curious to see the code ;-)

Greets Andi

Am 29.03.12 09:30 schrieb "Christian Peters" unter
<chp at digitale-avantgarde.com>:

>Hey list,
>
>after a few month of testing and playing around with Flow3 (and Extbase),
>I
>have to decide now, which framework to use for the next bigger project.
>
>I'm really enthusiastic of flow3 and a big fan of the core concepts and
>philosophy - but scared because of the lack of a complete documentation.
>I'm willing to experiment and view code, but I don't want to write code
>around the framework ("am Framework vorbeiprogrammieren" in german).
>
>Having said that, here are some key points of my app and I want to know if
>best practice does exist:
>
>*How to write a plugin based system in flow3?*
>
>Inutitively I would think of every plugin as a package, but I'm not really
>sure how to manage e.g. the view, for plugin based templates? Is there a
>three-level inheritance like in symphony's view?
>
>In general, is there a recommended way of doing this or are there any
>already existing examples of an application that has plugins, that are
>designed for this application (and not just shareable packages)?
>
>*
>*
>*Is there a recommended way to have advanced user management?`*
>*
>*
>As I understand the documentation, you define roles in yaml and there are
>app-wide. I need dynamic roles (user x is admin in this plugin, his group
>y
>is user in this plugin, but he is overall manager).
>
>Is this something that is somehow supported by the framework or how would
>I
>do this?
>
>*
>*
>*Are there any plans to update the documentation?*
>*
>*
>I've asked this question a lot and got answers like "it's an ongoing
>process" and "yes, documentation will be finalised". I really like your
>efforts and work and I know you may have pressure to proceed with other
>important stuff, but: Are there plans in terms of "There is a task in
>sprint y that will take place at xx-xx-xx" for some key documents (session
>handling, deployment, errors and exceptions, testing framework,
>architectual overview ...)?
>
>
>Thanks for reading!
>
>Best
>Chris
>
Andreas Förthner
Leiter Web-Entwicklung

Telefon: +49 (911) 539909 - 0
E-Mail: andreas.foerthner at netlogix.de
Website: media.netlogix.de


--
netlogix GmbH & Co. KG
IT-Services | IT-Training | Media
Andernacher Straße 53 | 90411 Nürnberg
Telefon: +49 (911) 539909 - 0 | Fax: +49 (911) 539909 - 99
E-Mail: info at netlogix.de | Internet: http://www.netlogix.de

netlogix GmbH & Co. KG ist eingetragen am Amtsgericht Nürnberg (HRA 13338)
Persönlich haftende Gesellschafterin: netlogix Verwaltungs GmbH (HRB 20634)
Umsatzsteuer-Identifikationsnummer: DE 233472254
Geschäftsführer: Stefan Buchta, Matthias Schmidt



_______________________________________________
>FLOW3-general mailing list
>FLOW3-general at lists.typo3.org
>http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general