SVN is active

[John Cox]

I have uploaded the changes to the Xaraya code base that I have made
so far. In addition, I have made an initial pass through the modules
looking for low hanging fruit to rid. I still need to go through the
themes to remove blocks, etc. Quick note: It seems with google code,
on the first commit you have to add your username and password to the
commit -m "message" --username blah --password blah, and after that it
will work.

Couple of things TODO in the meantime:

We need to have a discussion on the UI, because there will still be
some things that need to be visible. jQuery and jQueryUI will be
available in the default theme, but will be loaded from the theme,
since that is the rational place to have it, and it will be coming
from google code. How do we want the remaining UI bits to behave?
Single page admin, etc? I am not worried so much on the default
theme, as we can make it look as the webpage with screen shots, etc.

We need to have a discussion on whether to keep the admin / user
distinction. I don't really see a need for it, at least in the core,
and it would rid some overhead.

We need to have a discussion on the modules that will ship. What are
the core things that every application needs to be able to do? I
figure we are going to need to have a version of the scheduler module,
as well as a contact module. I would leave content management to the
applications outside of that. Any other thoughts?

We need to remove restrictions from the index.php to load anything
from a module, and not enforce the bl compiler. That said, are there
any other big restrictions that needs to go?

I did remove the pager functions, because jQuery can handle those
pretty easily. What else can be moved to the behavior layer which is
in the logic layer?

Can we add triggers and views to improve performance anywhere? This
is something that we need to discuss once the code profiler is built.

Speaking of the profiler, what I am looking to do is something similar
here:

http://particletree.com/features/php-quick-profiler/

The license doesn't work for us, if memory serves, and it seems very
buggy, but that's the overall push I am looking for.

That's it for now;)

jc

[Jo]

On Jun 7, 7:40 am, John Cox <john.cox...@gmail.com> wrote:
> I have uploaded the changes to the Xaraya code base that I have made
> so far.  

Thanks, just familiarizing myself with the changes now.

You raised a few areas with a need for discussion. While I have some
initial thoughts on these, some built up from past discussions, it
would probably pay me to think harder now that we're at the point of
disregarding any backward compatibility issues and making large code
changes. Some initial comments:

> How do we want the remaining UI bits to behave?
> Single page admin, etc?  

I tend to like a single admin 'control panel' idea. Until I have a
better idea of the end product though you're going to be better placed
to make suggestions on this for now. No doubt the underlying code will
impact on the final UI and what we can do.

> We need to have a discussion on whether to keep the admin / user
> distinction.  I don't really see a need for it, at least in the core,
> and it would rid some overhead.

Currently, I don't see a need for it. Removal of this dichotomy has
been raised before. While I recall finding it handy in some cases, it
was more of a distinction between 'technical configuration' vs 'user'
that was handy, rather than the 'admin' concept we have now. The
delineation between the current 'admin' vs 'user' setup is hazy in the
least and can be more of a hindrance than help. Probably needs more
thought on my part.

> We need to have a discussion on the modules that will ship.  What are
> the core things that every application needs to be able to do?  I
> figure we are going to need to have a version of the scheduler module,
> as well as a contact module.  I would leave content management to the
> applications outside of that.  Any other thoughts?

First thoughts, modules I find underly other 'expected' core
functionality include scheduler, some type of forms module (I use my
sitecontact module) for contact or other form related activity, mailer
of some type, logging at various activity levels, URL mapping. Not
clear on how close these would be planned to be 'tied' to core or
whether they would be totally separate modules shipped with core. I'm
sure there are other areas that I keep coming back to and wishing were
more accessible as part of a minimal package that is 'always
available'.

Having more of a review and think about the following:

> We need to remove restrictions from the index.php .....That said, are there

> any other big restrictions that needs to go?

> What else can be moved to the behavior layer which is
> in the logic layer?

> Can we add triggers and views to improve performance anywhere?  This
> is something that we need to discuss once the code profiler is built.

> http://particletree.com/features/php-quick-profiler/

More later :)

Jo