Re: [binarycloud-dev] binarycloud vs. other web app frameworks

[Nico G. <sc...@ac...>]

--* Alex Black (Sat, May 19, 2001 at 02:02:21PM -0700) *--

> uh, so if I can huff-and-puff for a moment, I really haven't seen anyon=
e
> even trying something as deep as r2 with php.=20

> the concepts and the code that will come out for this release will allo=
w you
> to speed the development of your projects by a factor of 5.

ok, i was afraid you were going to say that ;) actually, i'm very
interesting in getting involved with binarycloud, especially because you
seem to be very groovy stuff with xml/xslt, although i don't fully
understand how it all fits together yet, especially the 'entity'
concept.

> It will have a number of groovy features:
>     -document version tracking
>     -multi-language versions of the same document
>     -an inline rich (read visual html) editor which works with IE5.5+

Now this is something very cool that I've tried out at
binarycloud.com/bc_edit... too bad it's only supported bye IE5.5+

>     -everything will be xslt

never done it, but i usually get convinced into using this kinda stuff
quite easily :)

>     -we might get around to building a caching module for ripping docum=
ents
> ...this would probably be generalized, though - so you can flag a page =
as
> "cached" in the page def xml, and the system will automatically create =
a
> repository for cached markup and check that first.
>=20
> I think pear has a caching class, so we might just be able to plug it i=
n!

i know pear has this, i think it was written by ulf wendel and that he's
got extensive docs online on his website, but all in german (argh!).
consequence: i don't even understand the concept of a 'caching module'.
anyone care to explain??=20

> This is a point, but what we're trying to do is actually much more
> integrated with the system than "just a cms"

true. all that i'm afraid of is that 'implementing' a cms with this
groovy state-of-the-art framework could be more timeconsuming and
'banging-your-head-against-the-wall' than just trying to use something
that's been built allready. true, it takes the fun out of it, and limits
the extensibility of your system...=20

> also, with the stuff we're doing, it will almost be easier to re-build =
a
> simple app than to port it in. the new formbuilder will only spit xml o=
ut,
> so we'll run that through a global xsl - that means you can write one x=
sl
> for 90% of the forms on your site. one document.
>=20
> for example, a forum:
>     -define an entity: post
>     -another: thread
>     -another entity: forum

now, this i don't get. maybe i should take a look at your 'complex
example' post. should i take the 'r2 path release' and untar the
'complex example' in that tree??

--nicolas

--
nico galoppo   -   tremelo/leuven, belgium
               -   erasmus/socrates student in grenoble, france
               -   4, rue b=E9ranger -- phone: +33-(0)76-85 23 19
---------------------------------------------------------------
[bash]:~$ man woman                 nico at crossbar dot net
No manual entry for woman           debian linux :: vim powered