Jason Hines | 3 Feb 04:06 2004

Debug hookup


The current Debug hookup is not perfect.  As Jim pointed out, this 
embedding of Debug from Init assumes that the output will always be 
HTML.  Another issue I just realized is that because Debug with a 
different Init::GetPage() call, Debug cannot pass resources to the other 
node pipeline because it is a different smarty instance.

The clean way would be to have to include a reference to Debug in every 
NDF, but there must be another way.. Perhaps Node could embed Debug as a 
child of Top if Debug is enabled in Conf.. something like that.  Hmm.

jason
Jean-Christophe Michel | 3 Feb 13:02 2004

Re: Debug hookup

Le mar 03/02/2004 à 04:06, Jason Hines a écrit :
> The current Debug hookup is not perfect.  As Jim pointed out, this 
> embedding of Debug from Init assumes that the output will always be 
> HTML.  Another issue I just realized is that because Debug with a 
> different Init::GetPage() call, Debug cannot pass resources to the other 
> node pipeline because it is a different smarty instance.
> 
> The clean way would be to have to include a reference to Debug in every 
> NDF, but there must be another way.. Perhaps Node could embed Debug as a 
> child of Top if Debug is enabled in Conf.. something like that.  Hmm.

The main pb is that debug must be printed in most cases, even when
normal Node tree fails ;-]
Currently to correct Storage I have enable Log display inline because
Debug never prints.
We should solve two points: the format (html or other) and the way to
print Debug. I think to have a handler registered so as closing the page
would call PrintDebug. Format could be set in Conf and we would format
the array containing debug msgs into the right format when about to be
printed.
--

-- 
Jean-Christophe Michel <jc.michel@...>
Symétrie
ilya | 4 Feb 08:56 2004
Picon

hi!

Hi!

sorry for stupid question, but where I can find archive of
dev-binarycloud conference?

Regards,
Ilya
Jean-Christophe Michel | 4 Feb 09:03 2004

Re: hi!

Le mer 04/02/2004 à 08:56, ilya a écrit :
> where I can find archive of
> dev-binarycloud conference?

Via http://news.gmane.org/gmane.comp.lib.binarycloud.devel
or on http://binarycloud.tigris.org/
--

-- 
Jean-Christophe Michel <jc.michel@...>
Symétrie
Jean-Christophe Michel | 4 Feb 10:30 2004

api

Hi Jason,

Good work with the api.
Would it be possible to change all emails to avoid too much spam ?
either replace in cvs emails@... -> emails at example dot com
or to use smarty javascript mail coding ?
--

-- 
Jean-Christophe Michel <jc.michel@...>
Symétrie
ilya | 4 Feb 13:00 2004
Picon

requirements

Hi, All!

What is requirements for working with binarycloud framework?

PHP5?
As I note is needed xml/xslt supporting?
What for this? Sablotron, xsltproc?

What else needed?

note: I will try on win32 platform.

What is difference between r2 and r1?

Is there reason to investigate r1? or wait for r2rc1
Is there uml diagrams for architecture?

I want to try in work this interesting framework.

Regards,
Ilya
Jean-Christophe Michel | 4 Feb 13:43 2004

Re: requirements

Le mer 04/02/2004 à 13:00, ilya a écrit :
> What is requirements for working with binarycloud framework?
> 
> PHP5?

no, php4

> As I note is needed xml/xslt supporting?

yes, in cgi php (command line) for phing, and xsltproc for apache's php.

> note: I will try on win32 platform.

Have a look on http://webstract.org/static/StartPage.html
particularly Contributor Guide/Windows

Don't forget to edit testsite/build.properties before running phing.

And browse this archive:

On December 17th Deniele wrote:
> Redownloading xsltproc.exe, libxml2 and libxslt from 
> ftp://ftp.zlatkovic.com/pub/libxml/ corrected the problem.

> What is difference between r2 and r1?

r2 is an intermediary development version, non released.
r1 is some years old, i wasn't there :-)
Current almost-release version is r3.

(Continue reading)

ilya | 4 Feb 14:15 2004
Picon

Re[2]: requirements

JCM> no, php4

ok, good :)

>> As I note is needed xml/xslt supporting?
JCM> yes, in cgi php (command line) for phing, and xsltproc for apache's php.

ok

>> note: I will try on win32 platform.
JCM> Have a look on http://webstract.org/static/StartPage.html
JCM> particularly Contributor Guide/Windows

nor http://webstract.org/books/contrib/UINIXInstall.html
nor http://webstract.org/books/contrib/WinInstall.html
opening

also about archives, at http://binarycloud.tigris.org/servlets/SummarizeList?listName=users
mailing list archive stop at Oct 2003...

JCM> Don't forget to edit testsite/build.properties before running phing.

phing is included in binarycloud

JCM> And browse this archive:

JCM> On December 17th Deniele wrote:
>> Redownloading xsltproc.exe, libxml2 and libxslt from 
>> ftp://ftp.zlatkovic.com/pub/libxml/ corrected the problem.

(Continue reading)

Jean-Christophe Michel | 4 Feb 14:52 2004

Re: Re[2]: requirements

Le mer 04/02/2004 à 14:15, ilya a écrit :
> >> note: I will try on win32 platform.
> JCM> Have a look on http://webstract.org/static/StartPage.html
> JCM> particularly Contributor Guide/Windows
> 
> nor http://webstract.org/books/contrib/UINIXInstall.html
> nor http://webstract.org/books/contrib/WinInstall.html
> opening

THis work for me
http://webstract.org/books/contrib/contributor_guide.html#GetWindowsCVS

> also about archives, at http://binarycloud.tigris.org/servlets/SummarizeList?listName=users
> mailing list archive stop at Oct 2003...

Did you try gmane.org ?

> JCM> Don't forget to edit testsite/build.properties before running phing.
> 
> phing is included in binarycloud

Sure, but you need to edit build.properties to choose destination dir
for your built website.

> >> What is difference between r2 and r1?
> JCM> r2 is an intermediary development version, non released.
> JCM> r1 is some years old, i wasn't there :-)
> 
> JCM> Current almost-release version is r3.
> 
(Continue reading)

Jean-Christophe Michel | 4 Feb 19:29 2004

big storage redesign

Hi,

I began to redesign Storage classes to be clearer. I expose here the
ideas retained. Please comment the api and the algorithms detailed.

I keep the idea of handling Entity objects in a general way, so as we
can imagine to have entities extending or related to external
datasources. Each entity specifies its datasource; a Storage instance is
created foreach datasource.

Relations, inheritance are handled at Storage level. A subclass like
StorageSQL must implement low-level actions as set,get,del and get the
opportunity to handle directly inheritance and relations if they are
able to (for example in sql, Get can be done for all inheritance with
1:1 joins in a single query).
StorageSQL in turn still uses lower level calls to StorageSQLmetabase
(or soon StorageSQLcreole).

Queries are named using a fixed prefix (the action: set,get,del or misc)
and some fixed or custom names in a dot separated path-like name
(get.multiple, misc.count_result). Queries are either static (from a
file) or dynamic (generated by user code).

Relation properties will have four states: null means nothing is linked,
'UNKNOWN_VALUE' means relation is not loaded, a single value or an array
of values are the fk, obj or array of obj are really loaded related
entities. Values of 'load' attrib in edf can be none or fk or all.

I added EntityInfo which is an object cache for edf and queries.
that will later be extended to add user custom query generation.
(Continue reading)


Gmane