Re: an outsiders view[2]
"Wim Niemans" <[email protected]> Mon, 19 Dec 2005 12:42:22 +0100
| Newsgroups | gmane.comp.lib.binarycloud.devel |
|---|---|
| Organization | Pb Solo |
| Message-ID | <43A6AAAE.20593.8BF4DB@localhost> |
--===============1555498587== Content-type: text/html; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body <?xml version="1.0" ?><html> <head> <title></title> </head> <body> <div align="left"><font face="Arial"><span style="font-size:10pt">></span></font><font face="Courier New"><span style="font-size:10pt">The Conf Class is awesome! Why isn't this incorporated more into >the Node</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>class? Instead of having setParam and getParam why not have a >node</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>automagically create its own conf namespace so all nodes have an >easy</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>place to reference;  a uniform interface. In addition with node >creation</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>the Conf class could be used to autocreate a tree manager so you >could</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>crawl the tree and pre and post process nodes in this fashion.</span></font></div> <div align="left"><br/></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Nathan, Node creation and conf are different holons.</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">A NodeFactory may create Nodes, but doesn't use conf for that.</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Crawling a tree in pre- or postOrder mode, or Depth- or BreadthFirst mode (I prefer these terms), should be *outside* Node, indeed. I agree totally.</span></font></div> <div align="left"><br/></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>I also think the Event class is great. I just think its a shame >that it</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>isn't being used more, Nodes should fire events when entering >the</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>initialization/process/render steps and fire events that other >nodes can</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>listen for so they can respond without having to know the >parent/child</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>relationship. This would make Nodes insanely powerful.</span></font></div> <div align="left"><br/></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">I can' agree less. Though the Event system lacks true Object registration at the moment.</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Otherwise, IMO, a Node should not know it's parent at all.</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">A Node may controll it's children, obsoleting the need of it's children to give feedback. Well, it's IMO.</span></font></div> <div align="left"><br/></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>Having Smarty/Templates integrated so closely to a node sucks in >my</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>option, if you want to output to a template create a template >node, or</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>have a "/template" namespace in Conf. Render should have >settings like</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>HTML,SVG,PDF,JPG etc The public interface to a node is way too >big.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Most BC people will tend that Smarty is tightly integrated. Let me tell you from experience: it is *not*. The Smarty API is copied into the Node. Eliminating that copied-API is easy without breaking anything.</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">The idea of resource-types for Nodes is interesting. Do you have more ideas on that, ie. how to realize such, or examples?</span></font></div> <div align="left"><br/></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>Speaking of NDFs, I hate XML config files, they are great for >porting</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>configs from one environment to another but to work with by hand >is</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">I do see ndf as a concept, for the moment coded with XML.</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">I still do use Phing to generate native php arrays.</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">MyConf has several 'packers'. These support several fileformats,</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">line ini, txt, php_script(!), sql and on. But the concept remains conf and/or ndf. The 'packers' are just convenience.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>painful. I have patched my Binarycloud install so it runs native >php</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>config files, I find it much easier to deal with. My though with >this is</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>to create a simple web base interface for handling the >editing/creation of</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>config files. In this fashion we could then create resources and >the</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>config manager could automagically manage them and validate that >all</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>required parameters are filled and valid.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Agree on that. It is a definitive need. Though some will say that it is discussed already and before. Herewith ignoring that the need-to-have-it is existent.</span></font></div> <div align="left"><br/></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>There is allready an RenderManager but i  am</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>not sure you can just add a renderer.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Bas, it would be wonderfull if you may point to RenderManager in some more extend. I'm afraight that the term Render is not clear to vereybody in tha same way. At least to me, that is.....</span></font></div> <div align="left"><br/></div> <div align="left"><font face="Arial"><span style="font-size:10pt">></span></font><font face="Courier New" color="#7f0000"><span style="font-size:10pt"> But that might change if you need to hook node up in  a</span></font></div> <div align="left"><font face="Courier New" color="#7f0000"><span style="font-size:10pt">> different way than a simple tree. Not talking about the sepeartion of</span></font></div> <div align="left"><font face="Courier New" color="#7f0000"><span style="font-size:10pt">> Node and Rendering.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">>I would be more then willing to take on this task or help out.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Nodes form a simple Tree. This Tree can be further parameterized, if there are needs. The next step will be a Graph. I think if you go that way, the application of Nodes will be bent as well.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Example: Entities in a database could form a graph with data and relations. Searching the Graph is an application, like: find me the fastest travel connection fromA to B; or: find me the cheapiest supplier for this DVD recorder; or such.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">IMO: there is a fundamental difference between an Entity and a Node. That's why Nodes form a Tree and not a Graph. IMO, that is.</span></font></div> <div align="left"><br/> </div> <div align="left"><font face="Courier New"><span style="font-size:10pt">Cheers,</span></font></div> <div align="left"><font face="Courier New"><span style="font-size:10pt">wim niemans</span></font></div> <div align="left"></div> </body> </html> --===============1555498587== 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 --===============1555498587==--