[Phrame-devel] Phrame Heavy & Phrame Lite

[Scott L. <sco...@ho...>]

Hello everyone,

Been away from the project for awhile, but getting back into the thick =
of
things again.=20

Had some thoughts and wanted to get yours:
----------------------------------------------------------------------

I've noticed a lot of work being done from various developers and some
issues some are having in regards to the term "forking" the project.

I have seen comments from more advanced programmer types (as well as on =
the
list) that they would like to see PHRAME adhere more to the way of doing
things like the most popular standard MVC STRUTS so that JAVA =
programmers
would take more interest and enjoy working in PHP. (ex: WEB-INF =
directory,
dispatchers, etc.)

I also have seen comments from more of the designer & developer types =
that
they liked PHRAME's simplicity and are ecstatic about the entry type =
level
MVC and that they get more interested to the ideas of OOP, reusability =
and
frameworks in their development process.

As for my own predicament; I am starting a new project and want to use
PHRAME, as I was going through the stable released 2.0 version as well =
as
looking through all the excellent additions from other developers like =
Jason
and Alex on their own projects. I found myself spending way too much =
time on
debating what features and directory structures to use and implement =
from
the original and forked renditions of PHRAME and other ideas from STRUTS
itself.=20

Then a thought came to mind that at the time of my confusion made some =
sense
and wanted to pass it onto the group.

What about...2 types or categories of PHRAME?=20

A more advanced PHRAME (like Arnold, Alex and Jason's additions, sorry =
if I
left anyone else's efforts out here, just making an example) that =
adheres'
to the more advanced STRUT's standard, allowing a programmer to have a
choice between 2 great open source languages PHP and JAVA and feel more
comfortable working with both languages, but staying in the same train =
of
thought of STRUTS.

And a LITE version of PHRAME which would be considered the current =
stable
release of PHRAME, allowing designers and developers to enjoy learning =
OOP,
reusability and frameworks in their design and development process or =
just
want to apply a simple framework to a simple website and not get too far =
out
of their designer element trying to comprehend the complexity of STRUTS.

...of course the Lite version would need to be able to scale into the =
STRUTS
version if need be.

Thoughts on names to help get the idea across:

	Advanced Version
	* PHRAME Struts
	* P2EE
	* PHRAME PRO
	* PHRAME Adv.
	* PHRAME MVC Struts
	* PHRAME Heavy

	Current Released Version
	* PHRAME Lite
	* P2 Standard
	* PHRAME DEV
	* PHRAME
	* PHRAME MVC Lite

----------------------------------------------------------------------Loo=
kin
g forward to hearing other thoughts, easy on the flaming, I may of just =
had
a long night staring at a bright screen and wake up tomorrow and all of =
this
sounds way too out there. ;)

Cheers!
=09