OGo/J Re: Re: code documentation [Was: Re: [OGo-Documentation] code documentation]

On 17.12.2007, at 15:38, Adam Tauno Williams wrote:
> If OGo moves toward Java I think that would be a generally good thing;
> using a more "modern" [or perceived as modern] platform can only help.
> Not to mention having better tools.

Actually I don't think that the Java tools are better for maintaining  
"stable" products. They are someone better for quickly producing  
crap ;-)

A proper build cycle is as hard with Java. In fact I think that ObjC  
is better here, producing real binaries with proper makefiles.
BTW: I would LOVE to have GCJ compiled JOPE packages! :-)

> Has any of the OGo core functionality (Logic) been ported over to  
> Jope?

Yes, I have rewritten a pretty big part of Logic in 2007, though its  
not complete. (I mostly did what I needed for my stuff)
I expect to complete most of it in Q1/Q2 2008 as part of an ongoing  
project.

> (is it "Jope" or "JOPE"?).

Its JOPE (SOPE was Skyrix Object Publishing Environment after ZOPE,  
well and JOPE is supposed to mean Java OPE).
Anyways, I'm not attached to it at all ... Definitely not a good  
marketing term. But then, I don't really want to market it ;-)


> Just curious because I've been building on the zOGI API with one eye  
> on
> the possibility that someday I may just have to port the backend to
> something else;  that in itself doesn't look that hard (as far as
> "Logic" is concerned) but I'd loose all the other nice stuff OGo
> provides like DAV/GroupDAV (IMO the really hard hard) and thus  
> Funambol.

I don't fully understand the content of this part. Yes, you can still  
use ZideStore since what I did so far should be compatible with the  
ObjC frontends (advanced stuff obviously can't be exposed, eg I did  
some things on permissions).

Wrt to DAV/GroupDAV in Java, I think it should be reasonably easy to  
rewrite that in JOPE (but so far I did not do DAV in JOPE).

> I've also played with building a general-purpose ASP.NET WebUI using  
> the
> gaia [http://ajaxwidgets.com/] widgets (again on the zOGI API as I
> didn't want to get too welded to one backend).


Yes, I also explored a few things. In fact JOPE has a few quite cool  
features for doing AJAX (eg refreshing parts of a page component).
Though I would probably start with an old-style UI to get things  
running quickly (AJAX apps _are_ much harder than just doing a bunch  
of HTML pages).

Greets,
   Helge
-- 
Helge Hess
http://www.helgehess.eu/
-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss