tilde-devel — Developement of the LANGUAGE and the SERVER! not anything else.

Re: [Tilde-devel] new config api

[Tobias B. <to...@to...>]

On ons, aug 14, 2002 at 12:02:46 +0200, Tobias Rundström wrote:
 
> when looking at this I think maybe we want to keep tilde_config_data_get()
> and let it do all this?
> 
> What do you think?

Yes I think we should keep it. Both flexibility and simplicity. I like this
new API :)

/tobbe

[Tilde-devel] new config api

[Tobias <to...@to...>]

This is my tought.

tilde_config_data will stay the same. it will be seperated with the "root"
nodes of the config file. 

struct tilde_config_data {
        tilde_hash *hosts;
        tilde_hash *dbmsconfig;
        tilde_hash *serverconfig;
        tilde_hash *mimeconfig;
        tilde_hash *collection;
        void *portsconfig;
};

the new thing will come now :) when you lookup a value from one of those
hashes you will be returned a tilde_config_value struct instead of a
datapointer, and it will only be the first level nodes, not all levels at
the same time, no more "docroot.paths" instead you have to lookup docroot
first then extract paths from the config_value. 

the config_value struct definition looks like this:

struct tilde_config_value {
        
        /* either TILDE_CONFIG_VALUE_PLAIN or TILDE_CONFIG_VALUE_LIST */
        int type;

        /* all properties associated to this site. */
        tilde_hash *properties;
        
        /* if type equals to TILDE_CONFIG_VALUE_LIST this value is set
         * to a sorted list with values */
        tilde_config_value *child;

        /* this values are set if it is a plain value */
        char *directive;
        tilde_binary *data;

        /* list pointers */
        tilde_config_value *next;
        
};


abstraction functions for this struct are:

tilde_config_value *tilde_config_value_create (tilde_mem_zone *zone,
                                               int type,
                                               char *directive);

void tilde_config_value_data_set (tilde_mem_zone *zone, 
                                  tilde_config_value *value, 
                                  tilde_binary *data);

void tilde_config_value_list_add (tilde_mem_zone *zone, 
                                  tilde_config_value *value, 
                                  tilde_config_value *add);

char *tilde_config_value_getprop (tilde_config_value *value,
                                  char *propname);

void tilde_config_value_prop_add (tilde_config_value *value,
                                  char *propname,
                                  char *data);

int tilde_config_value_type (tilde_config_value *value);

int tilde_config_value_as_int (tilde_config_value *value);

char *tilde_config_value_as_string (tilde_config_value *value);



so a example for extracting paths.docroot from the localhost entry could be:


tilde_config_data *data;
tilde_config_value *value;
tilde_hash *hash;
char *foo;

data = tilde_config_init(zone,"tilde.conf.xml");
hash = tilde_config_hostconfig_get(data,"localhost");

value = (tilde_config_value*) tilde_hash_lookup(hash,"paths");
value = tilde_config_value_list_lookup(value,"docroot");

foo = tilde_config_value_as_string(value);


when looking at this I think maybe we want to keep tilde_config_data_get()
and let it do all this?

What do you think?

[Tilde-devel] summary of tilde devel meeting 13/9 2002

[Tobias <to...@to...>]

Hello!

This a summary of the meeting held at tobi's appartment the 13/9 2002.

Precence: Tobi,Ydo,Orbit,Wmike,Humm

First of we disscussed the future of nbsp;Solutions and the tilde language.
Not much where said on this topic since the question is still in the air.
Everyone did agree that we wanted to continue develop tilde whatever
happens.

After this we disscussed som real matters, like code :)

I introduced the new HTTPD and the news in it. We talked about things that
should happen to the new codebase:

The main motivation for building a new HTTPD was to remove some braindead
implementations and make the code a lot more readable. The status for the
HTTPD is that everything _seems_ to be working. There are still some things
todo, this will be added to the Task Manager over at sourceforge.

tilde_config.c needs to be rewritten to be able to finish the new HTTPD.

Image_String will be replaced by image_draw_text function that will draw the
text on a new blank picthure. Orbit will deliver a specification and to the
group and then produce the relevant code.

tilde_net.c is not very nice. Ydo agreed to rewrite it.

Before 1.0 we need also to _REWRITE_ most of the module code to remove the
uglyness of most of the modules.

Big problems with the current codebase are identified as:
-Most of the code is not using all the abstarctions that we already written.
-Some code that havent been rewriten since the time on GV is not that good.
-Lots of old and obsoleeted functions are still in the tree.

This should be corrected before releasing a 1.0 version.

The stable variant of the code will be updated in a 0.4.2 version and then
abandoned for the new codebase.


Other notes, I have opened a sourceforge group and everyone developing tilde
is encouraged to join at sf.net and tell me about it. This is where our
bugtracker and taskmanager will be. So it will be perfect if you all joined
up.

Yet another question that we forgot on the meeting, does everyone agree that
I take the projectplaner / manager role? This does not mean that I will do
all the work, but I will keep track on what is done and what should be done. 
If you don't want me as that just speak up.

Now, that is about everything I remebered, fill in my blanks :)

//Tobias

[Tilde-devel] this is a test.

[Tobias <to...@to...>]

Test of the list.

Welcome to you all.

//Tobias