an outsiders view

--===============1077182926==
Content-Type: multipart/alternative; 
	boundary="----=_Part_7920_8164534.1134749748880"

------=_Part_7920_8164534.1134749748880
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I have been using Binarycloud off and on for about 4 months now and I am
very impressed with how quickly I can get results. The core is really solid=
.
I do have a few concerns about some of the API that I thought I would share=
.
Some of these may come from my lack of knowlege and experience with
Binarycloud, if this is the case please ignore.

The Conf Class is awesome! Why isn't this incorporated more into the Node
class? Instead of having setParam and getParam why not have a node
automagically create its own conf namespace so all nodes have an easy place
to reference;  a uniform interface. In addition with node creation the Conf
class could be used to autocreate a tree manager so you could crawl the tre=
e
and pre and post process nodes in this fashion.

I also think the Event class is great. I just think its a shame that it
isn't being used more, Nodes should fire events when entering the
initialization/process/render steps and fire events that other nodes can
listen for so they can respond without having to know the parent/child
relationship. This would make Nodes insanely powerful.

Having Smarty/Templates integrated so closely to a node sucks in my option,
if you want to output to a template create a template node, or have a
"/template" namespace in Conf. Render should have settings like
HTML,SVG,PDF,JPG etc The public interface to a node is way too big.

I have already implemented alpha code for myself with all the above
including a setCondition and runCondition method on the Node class. These
methods allow one to add conditional nodes inside a node that point to an
NDF file, and automatically creates the child node and runs init and proces=
s
as well.

Speaking of NDFs, I hate XML config files, they are great for porting
configs from one environment to another but to work with by hand is painful=
.
I have patched my Binarycloud install so it runs native php config files, I
find it much easier to deal with. My though with this is to create a simple
web base interface for handling the editing/creation of config files. In
this fashion we could then create resources and the config manager could
automagically manage them and validate that all required parameters are
filled and valid.

I have many more ideas but I don't want to get carried away. I thought I
would share and see if this could be of any use to the direction of
Binarycloud. If so I would be more then happy to contribute to the project,
else I may create a branch if that is ok.

Nathan

------=_Part_7920_8164534.1134749748880
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br>
I have been using Binarycloud off and on for about 4 months now and I
am very impressed with how quickly I can get results. The core is
really solid. I do have a few concerns about some of the API that I
thought I would share. Some of these may come from my lack of knowlege
and experience with Binarycloud, if this is the case please ignore.<br>
<br>
The Conf Class is awesome! Why isn't this incorporated more into the
Node class? Instead of having setParam and getParam why not have a node
automagically create its own conf namespace so all nodes have an easy
place to reference;&nbsp; a uniform interface. In addition with node
creation the Conf class could be used to autocreate a tree manager so
you could crawl the tree and pre and post process nodes in this fashion.<br=
>
<br>
I also think the Event class is great. I just think its a shame that it
isn't being used more, Nodes should fire events when entering the
initialization/process/render steps and fire events that other nodes
can listen for so they can respond without having to know the
parent/child relationship. This would make Nodes insanely powerful.<br>
<br>
Having Smarty/Templates integrated so closely to a node sucks in my
option, if you want to output to a template create a template node, or
have a &quot;/template&quot; namespace in Conf. Render should have settings=
 like
HTML,SVG,PDF,JPG etc The public interface to a node is way too big.<br>
<br>
I have already implemented alpha code for myself with all the above
including a setCondition and runCondition method on the Node class.
These methods allow one to add conditional nodes inside a node that
point to an NDF file, and automatically creates the child node and runs
init and process as well. <br>
<br>
Speaking of NDFs, I hate XML config files, they are great for porting
configs from one environment to another but to work with by hand is
painful. I have patched my Binarycloud install so it runs native php
config files, I find it much easier to deal with. My though with this
is to create a simple web base interface for handling the
editing/creation of config files. In this fashion we could then create
resources and the config manager could automagically manage them and
validate that all required parameters are filled and valid.<br>
<br>
I have many more ideas but I don't want to get carried away. I thought
I would share and see if this could be of any use to the direction of
Binarycloud. If so I would be more then happy to contribute to the
project, else I may create a branch if that is ok.<br>
<br>
Nathan<br>

------=_Part_7920_8164534.1134749748880--

--===============1077182926==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
dev mailing list
dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected]
http://lists.binarycloud.com/mailman/listinfo/dev

--===============1077182926==--