Re: [phoenix-dev] ProjectInfoAPI Documenation

[Karl Matthias <karl.matthias@xxxxxxxxxxx>]

I didn't think you could do this in a dynamic way (meaning you don't
have to track the DB schema by hand in the class' member variables)
without manipulating the PHP language structs like SimpleXML does.  We
built the setup Nathan is documenting because we were trying to build a
solution that didn't require hand-coding objects to track the DB keys.
SimpleXML is written in C so it has all the access to the PHP internals
and thus can manipulate member variable names however it likes.  This
was previously not possible from PHP.  However, it seems that in PHP5
you can now do this from PHP code!  Here's an article on it:

http://www.ibm.com/developerworks/xml/library/os-php-flexobj/

I suggest that we implement the classes as they are now--and as Nathan
has done a nice job of documenting--because we are running out of time
to complete the page conversion before the end of the quarter.  But I
think we could make a significant improvement to usability if we built a
dynamic ProjectInfo class next quarter.

Karl


Bjorn Freeman-Benson wrote:
> Nathan,
> I think it would be better to have an API link SimpleXML 
> <http://www.php.net/simplexml> uses:
> 
> $projectInfo = new ProjectInfo( 'tools.ajdt' );
> $projectInfo->name
> $projectInfo->modulepath
> $projectInfo->release[0]->status
> $projectInfo->release[0]->name
> ...etc...
> 
> Wouldn't that just be easier for people to use?
> 
> - Bjorn
> 
>>>
>>> I’ve spent some time writing down some documentation for the new ProjectInfo 
>>> Database Methods that we plan to add to eclipse.org-common.
>>>
>>> http://wiki.eclipse.org/ProjectInfoAPI
>>>
>>>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> phoenix-dev mailing list
> phoenix-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/phoenix-dev