David,

Thanks for taking the time to help answer my questions. I have seen the
documentation and  that you mentioned and the preview tutorial.
Unfortunately it covers a lot of the information I already know. It's just
the last 20% which is missing.... Thats why it is a preview tutorial I
suppose.


You can switch routing off:
<setting name="use_routing">false</
>
> setting>
> in settings.xml, or, since 1.0 (the above still works):
> <parameter name="enabled">false</parameter>
> for <routing> in factories.xml.


Where can I find out this information myself.  I have no point of reference
to know how to craft these settings myself.

As for the routing & URL generation. I have a class which I built from my
early days in Mojavi which does URL generation, matched with my rewrite
rules. I find it easier to implement. The Agavi routing gets in the way. I
want to use Agavi to provide my application structure, I'm not interested in
the internationalization, inflections, routing, logging etc etc. I have my
own tools which I want a nice lightweight *framework *to hang my tools on.
I'm sure Agavi can provide this.

I don't care that Agavi does not seem that popular, Mojavi was very niche in
it's day. I like the power it gives me. However not everyone is as stubborn
as me to understand it and  shape it into something they can use. I asked
about how far it has been deployed to look for resources to get it up and
running. Also the framework is not really the point of all this effort, it's
what you can do with it.

Like any tool, you just want to sit down, read the manual and get to work.

Who cares about the paint brush, lets see the painting.

Thanks again





2008/9/16 David Zülke <[EMAIL PROTECTED]>

> Jason,
>
> thank you for your interest in Agavi. The sample application that is
> distributed with the framework gives a basic overview and examples of many
> features, including routing, form handling, security, configuration, web
> services, output types, layouting, internationalization and validation.
>
> We're also working on a brand new manual that will be ready in time for the
> final 1.0 release. The tutorial, a work in progress, is already available at
> http://agavi.org/docs/tutorial/. A reference manual that explains the
> structure, the configuration system and the various features is currently
> being written and will be published soon. All documentation is of course
> managed through the Subversion repository, so you can track activity there.
>
> Of course, we have plenty of users all around the world, mostly working for
> companies that use Agavi to build their products and services. I'm not aware
> of any open source projects that use Agavi as their framework, but I can
> name these two big sites that were built using Agavi:
> - sevenload.com
> - mtv.de
>
> The name of the Agavi session cookie can be changed using a <parameter
> name="session_name">PHPSESSID</parameter> for the <storage> in
> factories.xml.
>
> To use MySQL for sessions, you'd simply use AgaviMysqlSessionStorage
> instead of AgaviSessionStorage for <storage>, again in factories.xml.
>
> You do not have to manage sessions yourself, of course.
>
> You can switch routing off:
> <setting name="use_routing">false</setting>
> in settings.xml, or, since 1.0 (the above still works):
> <parameter name="enabled">false</parameter>
> for <routing> in factories.xml.
>
> I do not understand, however, why you want to use mod_rewrite. mod_rewrite
> does not allow you to generate URLs from your definitions. The Agavi routing
> can also do many other things, like applying callbacks to routes, setting
> output types, and much more. It's one of the framework's biggest strengths.
>
> Last but not least, be advised that there has been a feature freeze long
> ago. 1.0 contains mostly refactorings, cleanup, and a testing system when
> compared to 0.11. We've been cleaning up the framework over the last months
> and also put time and money into documentation. A website is coming sometime
> over the next weeks, as well.
>
> The future is bright.
>
> Stay strong,
>
> David
>
>
>
> Am 16.09.2008 um 02:47 schrieb jason simmons:
>
>  I spotted the a video of a Agavi Presentation held a t a London PHP
>> conference. It prompted me to look at Agavi again. I had a quick look
>> earlier this year and it has changed so much from my beloved  Mojavi. To be
>> Honest, its only the love of Mojavi which has made me continue to try and
>> understand Agavi.
>>
>> I'm glad that Agavi is still being developed, and it has evolved in
>> complexity which does makes it harder to grasp with in-complete
>> documentation.
>>
>> I have looked on sourceforge, tutorial sites, PHP Classes trying to find a
>> project based on Agavi which I can learn and see how it is applied. I can't
>> find anything
>> Is anyone actually using Agavi ?
>>
>> Some of the more experienced users of Agavi must of an application that
>> could be used as a sample application.
>>
>> I like the structure of Agavi/Mojavi. The user object, actions with
>> credentials/securtity, request data and all manipulated via my Models.
>> Fantastic.. However a few of the extra partially documented features are
>> getting in the way of me exploiting the framework.
>>
>> Agavi Config
>> Does any one have a list of some of the correct attributes to use in these
>> XML config files ( I miss the PHP config files), Like the PHPDocs for the
>> classes. The key one being routing.xml. I actually want to just switch it
>> off. I find it annoying. I use mod_rewrite for this type of stuff.
>>
>> Session Management
>> How can I override the Agavi session cookie? and set a PHPSESSID instead ?
>> Where do sessions get started, is it just after Dispatch or at the
>> ExecuctionFilter ?
>> Has anyone used Mysql based sessions... Could I see some example code. ?
>> Do I have to code my own session management Models, Session Destroy,
>> Start, hasCookie() etc ?
>>
>> In my opinion I think agavi should have a feature freeze.  it's a
>> fantastic framework which is just needs presenting with a bit more polish.
>>
>> I would appreciate it if anyone can share a real world application. Once I
>> understand Agavi, I will write some tutorials and applications demonstrating
>> it's power
>> it's obviously needed.
>>
>> Many thanks
>>
>> Jason
>>
>>
>>
>> _______________________________________________
>> users mailing list
>> [email protected]
>> http://lists.agavi.org/mailman/listinfo/users
>>
>
>
> _______________________________________________
> users mailing list
> [email protected]
> http://lists.agavi.org/mailman/listinfo/users
>
>
_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users

Reply via email to