Printable version + language independence +integrate other php-scripts?

Général
1

Bonjour à tous,

Several questions:

#1: At the home site (http://www.uzine.net), I could see a function to
make printable pages, made by a script named imprimersans.php3. Now, I
could not find this script in the 1.02 release package. Is this function
going to be included in future releases?

#2: How do I integrate other php-scripts with SPIP? Is there any
specific guidelines available?

#3: A great addition would be if you guys (and ladies?) could make SPIP
more language independent by put all text variables in a separate file,
much like phpnuke does. I know that this probably will slow down the
performance a little bit, but I think it would broaden the user base.

#4: Is it possible to make more "skeletons" available for learning
experience? The guide on uzine.net is ok, but how about including some
specific "skeletons" for various uses, for example one for online
magazines, one for organizations, one for educational use etc?
  
#5: How about some kind of roadmap on development? Maybe this already
exists?

#6: Mon dieu, life is not always that easy, is it? Why did I chose
German instead of French when I was in school? :wink:

Best regards,
H.Kim

2

@ Hi-Young Kim (hkim@psykolog.nu) :

Bonjour à tous,

Bonjour

Several questions:

#1: At the home site (http://www.uzine.net), I could see a function to
make printable pages, made by a script named imprimersans.php3. Now, I
could not find this script in the 1.02 release package. Is this function
going to be included in future releases?

The skeleton is there : http://www.uzine.net/imprimersans.html

#2: How do I integrate other php-scripts with SPIP? Is there any
specific guidelines available?

You can add your scripts inside the skeleton. The page is composed by
integrating the data from the database into the skeleton; the resulting page
is then "included" as php, so it may contain any script you need. You can
even pas arguments to your script by using a scheme like

<BOUCLE_....>
<? $value = stripslashes([(#TITRE|add_slashes)]);
</BOUCLE...>

#3: A great addition would be if you guys (and ladies?) could make SPIP
more language independent by put all text variables in a separate file,
much like phpnuke does. I know that this probably will slow down the
performance a little bit, but I think it would broaden the user base.

We're thinking about it, but I think this would be work for a specific i18n
(internationalization) team. As we do not pretend to be good at English,
German, Spanish or whatever language we would need. To just prepare the
infrastructure for i18n will be OK.

#4: Is it possible to make more "skeletons" available for learning
experience? The guide on uzine.net is ok, but how about including some
specific "skeletons" for various uses, for example one for online
magazines, one for organizations, one for educational use etc?

We encourage sites to publish their own skeletons if they wish. uzine.net
skeletons are available via http://uzine.net/(skeleton name).html ; others
are elsewhere. We should spend some effort grouping these.

#5: How about some kind of roadmap on development? Maybe this already
exists?

Yes: see the TODO file on spip / spip · GitLab

#6: Mon dieu, life is not always that easy, is it? Why did I chose
German instead of French when I was in school? :wink:

Maybe you wanted to join the Chaos Computer Club?

3

#1: At the home site (http://www.uzine.net), I could see a function to
make printable pages, made by a script named imprimersans.php3. Now, I
could not find this script in the 1.02 release package. Is this function
going to be included in future releases?

That's true, imprimersans.php3 is not included in SPIP. But you can take the one in uZine (just get "imprimersans.html" and create the right ".php3" file to use it).

#2: How do I integrate other php-scripts with SPIP? Is there any
specific guidelines available?

The simpliest way is to just include php scripts into the skeletons (for instance, a specific counter, an ad generator...). You just have to include them in the HTML part of the skeletons as you would for a normal HTML page.

#3: A great addition would be if you guys (and ladies?) could make SPIP
more language independent by put all text variables in a separate file,
much like phpnuke does. I know that this probably will slow down the
performance a little bit, but I think it would broaden the user base.

We will have to do that...

#4: Is it possible to make more "skeletons" available for learning
experience? The guide on uzine.net is ok, but how about including some
specific "skeletons" for various uses, for example one for online
magazines, one for organizations, one for educational use etc?

That would be great, but... we didn't have time to do that by ourselves. We just hope that over contributors will create and distribute skeletons, in the same way many graphists create themes for Nuke.

#5: How about some kind of roadmap on development? Maybe this already
exists?

Nope. We have a little "to do" list, but no roadmap.

As there are very few of us develepping SPIP, and as we very much try to include functions that the first users request, we prefer to deliver whatever is necessary just when it's ready.

#6: Mon dieu, life is not always that easy, is it? Why did I chose
German instead of French when I was in school? :wink:

Ich weiss nicht was soll es beteuten, das ich so traurig bin... Whatever :-))

ARNO*

--
Le Scarabée : http://www.scarabee.com
uZine 2 : http://www.minirezo.net

DH/DSS, 0x11930F0B, DEEB 602D B344 644B AF88 BF73 85F4 2297 1193 0F0B