Ir al contenido principal.
Enlaces relacionados:  Presse  Société  Clientes  Nous contacter
Solsoft

Forum

mfnrange and other wxis-like functionality


Auteur Message
le: 05. 05. 2003 [14:14]
fgomez@criba.edu.ar
=?Windows-1252?Q?Fernando_J._G=F3mez?
Auteur du fil
Inscrit depuis: 31.12.1969
Interventions: 0
Hi!

The recent message interchange between Roger and Braulio (about wxis'
mfnrange) has brought to my atention once again a point that I mentioned in
one of my first postings to this list.

This is a personal view, but I suppose that it represents the point of view
of many other people. I have been working with wxis for some time (more than
two and a half years); so I am used to expect some basic functionality when
working with Isis databases, such as:

-do task=mfnrange: loop through a range of contiguous records
-do task=keyrange: loop through a range of contiguous dictionary keys
-etc.

So, when I consider the possibility of migrating some wxis applications to
PHP, or designing new applications entirely with PHP, it seems natural to
expect that this "standard" functionality should be part of the new API.

I was not sure about whether Braulio had taken into account these facts when
designing his API; now I see that (apparently) he hadn't. Maybe we do not
have the right to tell him how the API should be, and of course anyone with
the appropriate programming skills can design his/her own API. But, of
course, it's easier for us to say "hey, Braulio, do things the way we like!"
icon_wink.gif

Another point which seems a bit uncomfortable to me, is the fact that
repeated fields are treated differently than non-repeated ones. This fact
forces us to branch the code using the is_array() function, which to me is a
bit unnatural.

To conclude, I would post the following question: can Braulio modifiy his
extension to take into account this sort of "wishlist" (which would
presumably make traditional Isis programmer's feel more "at home"), or
should we instead try to figure out how to make our own tailor-made
extension? Personally, I would prefer that the de facto standard
php-openisis (i.e., Braulio's) be the one who makes us all feel "at home".

That's all for now. I hope my point was clearly expressed...

Fernando


======================================================Fernando J. Gómez

Biblioteca Dr. Antonio Monteiro
Instituto de Matemática de Bahía Blanca (CONICET/UNS)
Av. Alem 1253
8000 Bahía Blanca - Argentina
======================================================
------------------------------------------
Posted to Phorum via PhorumMail
le: 05. 05. 2003 [15:02]
paul@OpenIsis.org
Klaus Ripke
Inscrit depuis: 31.12.1969
Interventions: 0
¡Hola!

On Monday 05 May 2003 20:14, Fernando J. Gómez wrote:
> So, when I consider the possibility of migrating some wxis applications to
> PHP, or designing new applications entirely with PHP, it seems natural to
> expect that this "standard" functionality should be part of the new API=2E
>
definitively it should and will be.
However, our approach was to first develop a solid and flexible basis API,
upon which higher level functions like mfnrange or keyrange can be based.
It is just now that the second generation of the core API,
giving access to a lot of new features, is stabilizing and will then
be available also from PHP.

> not have the right to tell him how the API should be, and of course anyone
> with the appropriate programming skills can design his/her own API. But, of
> course, it's easier for us to say "hey, Braulio, do things the way we
> like!" icon_wink.gif
Clearly, it's not the idea of open software that anybody has to do it
themselves; sharing is the idea.

As I see there's more vitality in the list now,
I will create a Wiki within the next days for Isis, OpenIsis and PHP-OpenIsis.
Everybody can post their code examples and convenience functions there.
Some people can maintain a collection of this stuff as their own but public
PHP module, integrating anything they seem fit, and others can decide
for themselves whose module is their preferred PHP-OpenIsis library.

Probably one module will be more targeted at people accustomed to WXIS,
another one rather at people who never used an Isis database at all.
For example, for long term ISIS users, it will be very natural to have
something with the name "v", while others would very much dislike
the idea of importing a database library and having a "v" in their namespace.

> Another point which seems a bit uncomfortable to me, is the fact that
> repeated fields are treated differently than non-repeated ones. This fact
> forces us to branch the code using the is_array() function, which to me is
> a bit unnatural.
A convenience routine (called v?) may fix this.

> To conclude, I would post the following question: can Braulio modifiy his
> extension to take into account this sort of "wishlist" (which would
> presumably make traditional Isis programmer's feel more "at home"), or
> should we instead try to figure out how to make our own tailor-made
> extension? Personally, I would prefer that the de facto standard
> php-openisis (i.e., Braulio's) be the one who makes us all feel "at home".
Of course, wishlists are very important for us developers,
and we will try to match them as much as possible.
If we can clearly figure out which collection of utilities is agreed
upon by a majority of users, we will stamp it as "very official"
(if somebody cares) and include it in distributions.
However, the core programmed in C will remain as small as possible,
not meant to be convenient but efficient,
with just enough features so that the rest can (and will) be done in PHP.

> I hope my point was clearly expressed...
si icon_smile.gif

cheers
Klaus

------------------------------------------
Posted to Phorum via PhorumMail



Identification de l'utilisateur

Entrez votre nom d'utilisateur et votre mot de passe pour vous identifier:
Identification

Mot de passe oublié ?


Copyright © 2003-2009, Solsoft de Costa Rica S.A.
Charte de confidentialité