[MIG] Migration from PorteAil to hugo-portal

This commit is contained in:
Olivier DOSSMANN 2016-01-21 20:27:23 +01:00
parent 44ba3a32d3
commit 820fa8f2b6
1131 changed files with 100 additions and 1869 deletions

4
.gitignore vendored
View File

@ -1,3 +1 @@
porteail/*
.gitignore
www/*
public

674
COPYING
View File

@ -1,674 +0,0 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<http://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<http://www.gnu.org/philosophy/why-not-lgpl.html>.

View File

@ -1,120 +0,0 @@
###########
# LICENCE #
###########
# Copyright (C) 2011 DOSSMANN Olivier <olivier@dossmann.net> ##
# This file is part of PorteAil.
#
# PorteAil is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# PorteAil is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with PorteAil. If not, see <http://www.gnu.org/licenses/>.
######################################################################
# définition de cibles particulières
.PHONY: clean
## VARIABLES ##
VERSION=0.1.3-trunk
## CONFIG PAR DEFAUT
include paconfigrc
## CONFIG UTILISATEUR
include configrc
## AUTRES CONFIGS
##--[[ adresses ]]--##
INTRO_ADDR = $(COMPONENTS)/$(INTRO)
MENU_ADDR = $(COMPONENTS)/$(MENU)
# programmes
PROG_ECHO = `which echo`
PROG_TEST = `which test`
PROG_RM = `which rm`
PROG_LUA = `which lua`
PROG_SH = `which sh`
PROG_MKDIR = `which mkdir`
# vérification des programmes
ifndef PROG_ECHO
error_echo = 1
endif
ifndef PROG_TEST
error_test = 1
endif
ifndef PROG_RM
error_rm = 1
endif
ifndef PROG_MKDIR
error_mkdir = 1
endif
ifndef PROG_SH
error_sh = 1
endif
ifndef PROG_LUA
error_lua = 1
endif
## DEBUT
# création de tous les fichiers
all: test homepage
## TEST
# divers tests sur l'existence des dossiers/fichiers
# création si besoin
test:
$(if $(error_echo), exit 1)
@$(PROG_ECHO) -e "Lancement des tests…"
@$(PROG_ECHO) -e "\t…existence des différents programmes"
$(if $(error_test), @$(PROG_ECHO) -e "\t\ttest : MANQUANT." ; exit 1)
$(if $(error_mkdir), @$(PROG_ECHO) -e "\t\tmkdir : MANQUANT." ; exit 1)
$(if $(error_sh), @$(PROG_ECHO) -e "\t\tsh : MANQUANT." ; exit 1)
$(if $(error_rm), @$(PROG_ECHO) -e "\t\trm : MANQUANT." ; exit 1)
$(if $(error_lua), @$(PROG_ECHO) -e "\t\tlua : MANQUANT." ; exit 1)
@$(PROG_ECHO) -e "\t…existence des dossiers '$(IMAGES)', '$(CATEGORIES)' et '$(CSS)'"
@for i in $(IMAGES) $(CATEGORIES) $(CSS) ; \
do \
$(PROG_TEST) -d $$i || exit 1 ; \
done ; \
$(PROG_ECHO) -e "\t…création des dossiers cibles '$(DESTINATION)' et '$(DESTINATION)/$(IMAGES_DESTINATION)'"
@for j in $(DESTINATION) $(DESTINATION)/$(IMAGES_DESTINATION) ; \
do \
$(PROG_TEST) -d $$j || $(PROG_MKDIR) $$j ; \
done
@$(PROG_ECHO) -e "\t…option introduction dans la page"
$(if $(INTRO), @$(PROG_TEST) -f $(INTRO_ADDR) || exit 1)
$(if $(INTRO), @$(PROG_ECHO) -e "\t\t-> activée", @$(PROG_ECHO) -e "\t\t-> désactivée")
@$(PROG_ECHO) -e "\t…option ajout d'un menu (vérification de l'existence)"
$(if $(MENU), @$(PROG_TEST) -f $(MENU_ADDR) || exit 1)
$(if $(MENU), @$(PROG_ECHO) -e "\t\t-> activée", @$(PROG_ECHO) -e "\t\t-> désactivée")
@$(PROG_ECHO) -e " …terminé."
## CATEGORIES
# création de la page d'accueil
homepage:
@$(PROG_ECHO) -e "Création de la page d'accueil…"
@VERSION=$(VERSION) $(PROG_LUA) create_homepage.lua || exit 1
@$(PROG_ECHO) -e " …terminée."
install:
@SRCDIR=$(DESTINATION) DESTDIR=$(INSTALLDIR) $(PROG_SH) install.sh || exit 1
## NETTOYAGE
# nettoyage des fichiers générés
clean:
@$(PROG_ECHO) -e "Nettoyage des fichiers en cours…"
@$(PROG_RM) -rf $(DESTINATION)
@$(PROG_ECHO) -e " …terminé."

419
README.md
View File

@ -1,419 +0,0 @@
# Programme PorteAil ##
## À propos
PorteAil est un portail web statique dont le but principal est, comme son nom
l'indique, de partager un ensemble de liens divers ou partagé par un seul et
même projet.
Cf. [L'article sur les portails sur l'encyclopédie Wikipédia](http://fr.wikipedia.org/wiki/Portail_%28web%29) pour de plus amples
informations.
PorteAil est un jeu de mot entre *Porte*, *portail* et *Ail*.
### Site Web / Exemple
La page officielle du projet, mais également page d'exemple est disponible à
l'adresse suivante :
[http://porteail.depotoi.re/](http://porteail.depotoi.re/ "Se rendre sur le site officiel du projet PorteAil")
### Contact
Cf. Chapitre Contact / Bugs" en bas de page.
### Licence
Le programme PorteAil est sous **licence GPLv3**.
Vous êtes libre de diffuser le programme, de le modifier et de le
redistribuer sous la même licence en précisant le nom de l'auteur.
Pour plus de renseignements je vous invite à lire le fichier *COPYING*
joint avec les fichiers du programme.
## Description
Le script makefile permet de générer un dossier contenant les fichiers
suivants :
- index.html : page de garde du portail web *PorteAil*
- defaut.css : feuille de style de PorteAil
- img : dossier contenant l'ensemble des fichiers images (icônes) pour
l'affichage des éléments dans la page de garde
## Pré - requis
Ce programme fonctionne à l'aide de **GNU Make** que vous pouvez installer
sur votre machine, par exemple sous GNU/Linux Debian à l'aide de la
commande suivante :
apt-get install make
Mais également **Lua 5.1**, installable à l'aide de la commande suivante :
apt-get install lua5.1 luarocks
Puis de **LuaFileSystem** :
luarocks install luafilesystem
Votre système devrais aussi détenir les commandes suivantes :
- rm
- sh
- echo
- test
- mkdir
Normalement ces éléments sont inclus de base ou disponibles dans
nimporte quel système dexploitation POSIX.
## Installation
Le programme ne requièrt aucune installation particulière. Placez le où
vous voudrez.
En revanche il est possible d'utiliser le script **install.sh** pour copier
le contenu du dossier **porteail** dans celui du dossier **~/public_html**.
Pour de plus amples informations sur ce script, lisez le chapitre **install.sh**.
## Configuration
Copiez le fichier **configrc.exemple** (ou bien renommez le) en *configrc*.
Sans ce fichier *configrc* le programme ne peut pas fonctionner (depuis la
version 0.1.1).
Pour de plus amples informations sur ce fichier, lisez le chapitre **configrc**.
## Utilisation
Il vous suffit de lancer la commande suivante dans le dossier du projet :
make
Cela devrait générer le dossier **porteail** dans lequel se trouve un exemple
de résultat possible.
Un nouveau dossier **porteail** apparaît dans lequel il y a :
- un fichier *index.html*
- une feuille de style nommée *defaut.css*
- un dossier *img* contenant… des images !
Pour supprimer les fichiers générés, il faut utiliser cette commande :
make clean
et cela aura pour effet de supprimer le dossier **porteail** et le fichier
**categories.html** crée par différents scripts au moment de la génération
de la page.
## Fonctionnement basique
Dans sa version 0.1 le programme s'utilise via plusieurs fichiers :
- le fichier configrc
- le dossier categ
- le fichier composants/introduction.html
- le fichier composants/menu.html
- le dossier img
Pour chaque élément, veuillez vous référer au chapitre adéquat.
Si vous désirez personnaliser encore plus la page PorteAil, vous pouvez
lire la section « Pour aller plus loin » qui permet de comprendre un
peu mieux le fonctionnement du programme.
### configrc
Ce fichier apparaît depuis la version 0.1.1. Il vous permettra de changer,
par exemple, le titre de votre page PorteAil. Ceci se fait via la
ligne suivante :
TITLE=
Par exemple pour afficher "Mon super site" sur la page PorteAil, modifiez ceci
dans le fichier configrc :
TITLE = Mon super site
D'autres éléments peuvent être modifiés afin de personnaliser le résultat de
PorteAil. Pour de plus amples renseignements à ce sujet, je vous invite à lire
le chapitre **Pour aller plus loin** du présent document.
### Le dossier *categ*
Le dossier **categ** est le dossier qui va contenir nos catégories
d'éléments.
Il faut savoir que :
- un fichier texte portant l'extension *.txt* est considéré comme
UNE catégorie
- le programme n'accepte que les fichiers comportant une et une
seule description de catégorie
- le programme va lire les éléments renseignés dans le fichier
Le format de fichier accepte 3 cas possible de lignes :
1. les commentaires
2. une description d'une catégorie
3. une description d'un élément
Voici un commentaire :
# un commentaire dans le fichier
Voici une description de catégorie :
[[Titre de ma catégorie]]Description de ma catégorie
Voici la description d'un élément (un élément par ligne) :
Titre##URL##DESC##ADDR_IMG
où :
- Titre : est le nom affiché sur le portail de l'élément.
- URL : est l'adresse COMPLÈTE du site sur lequel l'utilisateur ira
- DESC : est la description complète de notre élément pour le passage de la
souris sur le lien
- ADDR_IMG : est l'adresse relative vers l'image (Cf. ci-après pour plus de
renseignements)
Des exemples sont donnés dans le dossier **categ**. À vous de les modifier comme
bon vous semble.
Astuce : Pour ordonner les catégories dans la page résultante, ajouter des
chiffres devant chacun de vos fichiers catégories. Par exemple :
00-ma_categorie.txt
01-autre_categorie.txt
Vous obtiendrez donc *ma_categorie* en premier lieu, puis *autre_categorie*
en second lieu.
### Le dossier *img* et Adresse de l'image
Dans la version 0.1.1, il faut indiquer l'adresse dite absolue de l'image.
C'est à dire l'adresse à partir du dossier image source (par défaut c'est
le dossier **img** dans lequel nous irons chercher les images).
Le dossier image source est le dossier contenant l'ensemble des images. C'est
un dossier dans lequel le programme va *piocher* les éléments.
Sachant que le dossier **img** contient l'ensemble des images disponibles,
il faut tout d'abord trouver l'adresse d'une image qu'on voudrait, par
exemple **apps/clock.png**.
Dans un fichier catégorie, on donnera donc l'adresse suivante comme adresse de
l'image :
apps/clock.png
Pour un exemple plus criant, je vous propose de lire le fichier suivant :
categ/education.txt
qui contient un exemple de catégorie avec plusieurs éléments.
### Le fichier introduction.html
Le fichier **composants/introduction.html** contient du texte en HTML à
insérer en début de la page PorteAil, il faut donc connaître un peu le
langage HTML pour permettre un affichage correct de ce que vous voulez.
Par défaut cet élément n'est pas activé. Pour l'activer il suffit de
changer la ligne suivante dans le fichier **configrc** :
#INTRO = introduction.html
par
INTRO = introduction.html
Vous l'aurez compris, il suffit d'enlever le premier dièse **#** du début de
ligne.
### Le fichier menu.html
À l'instar du fichier **introduction.html**, le fichier **menu.html** permet
d'insérer un menu dans la page du PorteAil. Ceci est très utile si vous
voulez agrémenter le portail de tout un tas d'autres pages.
Par défaut cet élément n'est pas activé. Pour l'activer il suffit de
changer la ligne suivante dans le fichier **configrc** :
#MENU = menu.html
par
MENU = menu.html
Comme pour l'introduction, il suffit de supprimer le dièse **#** en début de
ligne.
### Publication
Pour publier le résultat dans un dossier web, il vous suffit d'utiliser la
commande suivante :
make install
Ceci permet de déplacer le résultat du programme PorteAil dans un dossier
de votre choix.
Par défaut le script essaie de copier le tout dans le dossier **public_html**
du dossier personnel. Par exemple le dossier **/home/olivier/public_html**
si votre dossier personnel se trouve dans **/home/olivier**.
Pour modifier les valeurs d'origine et de destination de la copie, éditez le
fichier de configuration *configrc* et modifiez les valeurs suivantes :
- DESTINATION : contient l'adresse relative du dossier où se situe les fichiers
à copier (résultant d'une compilation de PorteAil)
- INSTALLDIR : contient l'adresse exacte où copier les fichiers (la destination).
## Pour aller plus loin
Tous les éléments expliqués ci-avant ne seront que partiellement ou pas du
tout expliqué pour des raisons évidentes de redondance d'information.
Nous allons donc aborder plusieurs points qui concernent la personnalisation
de PorteAil afin d'adapter le programme pour qu'il en résulte une page d'une
structure différente de celle de base.
Cela est utile dans le cas où :
- vous connaissez le langage HTML pour faire des pages internet
- vous connaissez le langage CSS pour manier visuellement la page sans modifier
le contenu
- vous n'avez pas peur de modifier quelques lignes dans des fichiers afin de
voir le résultat
### Utilisation de la commande make
Pour plus d'informations sur l'utilisation de la commande **make**, je vous
renvoie à la page de manuel disponible en tapant :
man make
Cependant sachez que dans le fichier **GNUmakefile** il existe plusieurs sections
susceptibles d'être utilisées. Les principales sont :
- all : génère la page de PorteAil après avoir fait divers tests d'existence
des éléments.
- clean : permet de nettoyer le dossier nommé **porteail**
- test : fait quelques tests sur l'existence des ficheirs nécessaires pour
la compilation de la page.
### configrc
Le fichier **configrc** contient tout les éléments utiles pour personnaliser
la page de résultat.
Les lignes contenant des dièses **#** sont des commentaires pour vous aider
à mieux comprendre le contenu du fichier.
Le fichier est scindé en plusieurs parties afin de simplifier la découverte
des éléments :
- configuration basique : quelques éléments à modifier pour changer
rapidement la page de résultat
- configuration avancée : des éléments plus complexes qui ont un impact
plus grand sur la page de résultat.
Configuration basique :
- TITLE : Cf. chapitre **Fonctionnement basique**
- STYLE : nom de la feuille de style qui ajoutera des couleurs à PorteAil
(seconde feuille de style en somme). Redéfinir l'ensemble des classes
CSS de ce fichier vous permettra de reconfigurer toute l'apparence de
PorteAil.
- MENU : Cf. chapitre **Fonctionnement basique**
- INTRO : Cf. chapitre **Fonctionnement basique**
- DESTINATION : nom du dossier dans lequel sera généré le portail web.
Configuration avancée :
- LANG : Langue utilisée pour les traductions de la page (enqueue
principalement)
- HOMEPAGE : Titre de la page tel qu'il s'affichera sur un navigateur
- CATEGORIES_EXT : extension des fichiers qui seront lus pour générer
les catégories
- DEFAUT_IMG : nom de l'image - contenue par défaut dans le dossier img -
par défaut pour un élément qui n'a pas d'image ou n'en a pas trouvé.
- TEMPLATE_ELEMENT : nom du fichier contenant le code HTML d'un élément.
Se trouve par défaut dans le dossier *COMPONENTS*.
- TEMPLATE_INDEX : nom du fichier contenant le code HTML de la page finale.
Se trouve par défaut dans le dossier *COMPONENTS*.
- TEMPLATE_CATEG : nom du fichier contenant le code HTML d'une catégorie.
Se trouve par défaut dans le dossier *COMPONENTS*.
- COMPONENTS : dossier contenant les éléments qui constitueront la page
finale
- CATEGORIES : dossier contenant les fichiers sources des catégories.
- IMAGES : dossier par défaut contenant les images pour les éléments.
- CSS : dossier par défaut des feuilles de style
- INSTALLDIR : dossier utilisé lors de la commande *make install* permettant
de copier le résultat final dans un dossier web.
- IMAGES_DESTINATION : nom du dossier qui contiendra les images utilisées par la
page finale
- CSS_NAME : nom du fichier CSS final
Pour plus de renseignements, veuillez vous référer au chapitre **Les
composants**.
### Les composants
Les composants sont les éléments qui permettent de composer la page HTML
finale.
À cet effet la page a été scindés en plusieurs éléments :
- index.html : contient l'ensemble du HTML pour la page d'accueil.
- element.html : contient l'ensemble du HTML pour UN élément donné
- categories.html : contient l'ensemble du HTML pour une catégorie donnée.
(sans les éléments)
- introduction.html : contient du HTML pouvant être ajouté après le titre
principal de la page
- menu.html : un menu à ajouter à notre page
Pour personnaliser il suffit d'éditer chacun des fichiers afin d'en
modifier le code source.
### Le dossier style
Le dossier **style** est prévu pour contenir l'ensemble des feuilles de style
disponible pour l'apparence de notre page PorteAil.
Déposez donc ici vos feuille de style et changez la variable *STYLE* du
fichier **configrc** (Cf. Chapitre **configrc**).
### Le dossier img
Le dossier **img** contient, depuis la version 0.1, l'ensemble des images
utilisées pour la page finale.
Déposez-y les images que vous allez utiliser.
## SOURCES
Les sources du programme peuvent être récupérées sur
[le dépôt Gitorious](http://gitorious.org/porteail/) ou via la commande
suivante (à l'aide de l'outil git) :
git clone https://git.gitorious.org/porteail/master.git
## Contact / Bugs
Pour toute suggestion, critique constructive, remarque, notification de bugs,
je vous invite à me joindre à l'adresse courriel suivante :
olivier+porteail CHEZ dossmann POINT net
Pensez à ajouter, en début d'objet de votre courriel, l'élément suivant :
[PorteAil]
Ceci me permettra de savoir directement de quel sujet le courriel traite.
Merci d'avance, et amusez-vous bien avec PorteAil ;-)

141
TACHES
View File

@ -1,141 +0,0 @@
À FAIRE :
----------
- Valider la page à l'aide de TIDY (doit être facultatif)
- Choisir le nombre de colonne d'élément :
#corps ul.ensemble_element li {
width: 11em;
margin: auto;
}
Mettre à width = auto. Si on veut 1 colonne, alors on met 11x1 + 1x1, si on veut deux colonne, alors on met 11x2 + 1x2, 3 colonnes font 11x3 + 1x3
>>> Pour la v0.1.4 :
- activer menu avec une variable du genre "MENU_ACTIVE = 1" (par exemple)
- favicon.ico ?
- création du fichier configrc s'il n'existe pas (dans test)
- Transformer la doc en README.asciidoc ?
- Bug: si caractères accentués dans les titres/description. Souci qui semble se régler en mettant HTML au lieu de XHTML pour la page index
>>> Pour la v0.2 :
- Transformer le fichier GNUmakefile en makefile pour bmake
- changer les sed -i en "sed -e 's/chaine/autrechaine/g' > file.new && mv file.new file" (avec ou sans -e, c'est selon)
- changer les VAR= en VAR:=
- changer l'utilisation du shell par TXTs = $(shell ls $(dossier)/*$(ext)), par exemple.
>>> Pour la v0.3 :
- Documentation en anglais
- faire une page "print.css"
- mettre en noir et blanc
- ajouter le nom des liens en fin de chaque lien
- Tenter d'utiliser la description de l'élément pour faire une fenêtre qui s'affiche quand on passe sur le cadre de l'élément (tout en CSS si possible !)
- Ajout d'un lien vers le site dont proviennent les images
- Ajouter une option qui affiche sous chaque cadre la description de l'élément (ou bien une autre façon d'afficher les liens)
- permettre l'ajout d'un pied de page
- afficher un marqueur graphique qui définit si on sort du site actuel ou pas (genre IN/OUT dans la configuration des éléments, ce qui affiche une icône différente)
===============================================================================
===============================================================================
FAITES :
---------
- faire un makefile basique
- faire un .gitignore pour les fichiers/dossiers inutiles
- faire un fichier TACHES
- ajouter une licence/copyright
- faire une page d'exemple avec un menu et une feuille de style en noir et blanc
- faire une page d'exemple sans menu et avec une feuille de style en noir et blanc
- permettre l'ajout facultatif d'un menu
- gérer le fait que le css change si on a un menu ou pas (Cf. dossier exemple avec le(s) fichier(s) patch)
- migration des fichiers .html dans un dossier prévu à cet effet
- indenter le code de parcours_categ.sh pour n'avoir plus que deux espaces au lieu de 4
- trouver une syntaxe pour les fichiers de catégories contenant des éléments
Par exemple : ### Ma super catégorie ###
- dans dossier categ : un fichier par catégorie et les éléments contenus dans la catégories. Le format est un peu comme celui ci :
#commentaire
[[Titre de la catégorie]]Description de la catégorie (pour mettre dans des <p></p>
titre_element##URL##Description##adresse_image##titre_image##description_image
- test de l'existence du dossier CATEG dans le script parcours_categ.sh
- BUG : On ne peut pas avoir plusieurs catégories => changer script creation_categ.sh pour ne PAS détruire le fichier categories.html (le makefile doit le faire)
- ajouter des ECHO avant chaque ligne pour définir où ça plante quand c'est
le cas
- rendre la page valide XHTML Strict via validator.w3.org
- permettre l'ajout d'un texte d'introduction au début de la page
- changer les variables contenues dans les fichiers HTML par @@NOM_VARIABLE@@
- ajout de l'adresse URL du dépôt GIT dans le pied de page (soulier) du portail : Généré par <a href="http://git.dossmann.net/scripts/porteail.git/" title="Se rendre sur le dépôt source du projet PorteAil">PorteAil</a>
- amélioration de la recherche des fichiers dans le dossier catégorie, avec choix d'une extension
- Supprimer l'ensemble des variables @@quelque chose@@ dans le fichier à la fin du traitement (pour nettoyage)
- ajouter une licence comme LPRAB
- ajouter les éléments de chaque catégorie dans la page html
(car plus pratique)
- parcours_categ : normer les variables pour avoir categ_titre et element_titre plutôt que titre_categ et element_titre…
- dans le makefile s'occuper de faire une section pour les catégories contenant
des éléments
- ajouter des fichiers images au bon format et sous licence libre
- compatibilité avec d'autres navigateurs pour le CSS -moz-border-radius et -moz-box-shadow
- Éviter l'utilisation d'un patch pour le CSS avec/sans menu. Proposer deux variables contenant les deux versions du fichier CSS.
- Modifier le fichier introduction.html pour donner quelques infos à l'utilisateur sur comment comprendre/utiliser le programme => parler du fichier LISMOI et du dossier 'categ'
- Enlever le dièse de INTRO
- Dans la doc : faire un paragraphe "CONTACT" afin de me contacter pour bugs éventuels
- compléter le fichier LISMOI pour expliquer le fonctionnement du logiciel
- les dossiers à avoir
- les fichiers à avoir
- les dossiers résultants
- les variables à changer pour personnaliser
- ajouter un paragraphe LICENCE pour expliquer la licence appliquée
- des h3 mais pas de h2, WTF ?
- améliorer visibilité sur écran 22" avec : {margin-left:10%;margin-right:10%;}
- créer un site internet parlant de PorteAil avec une page générée par PorteAil comportant l'ensemble des sites utilisant Porteail
- Essayer de faire en sorte que le lien soit écarté jusqu'aux bords de tout l'élément afin que le clic sur l'élément renvoie sur la page
- Faire la feuille de style bleue pour le site avec un menu
- Voir si possibilité de faire un "source configrc" pour inclure les variables modifiables du programme, histoire de n'éditer que le fichier 'configrc' du programme
- améliorer la connexion entre le makefile et creation_categ.sh afin de ne plus toucher aux variables de creation_categ.sh
- trouver une méthode qui permet de récupérer toujours les dernières versions sources sans écraser la version que nous avons. configrc.exemple par exemple, à copier en configrc ;)
- Prévoir un script d'export des données entrées par l'utilisateur s'il utilise un dépôt git OU trouver un système de mise à jour du logiciel => réglé avec le fichier configrc.exemple en configrc
- faire des "which" pour les programmes utilisés (notamment pour sha1 ou md5). Quitter le makefile si dans TEST les "which" sont vides
- ANNULE du fait qu'on peut utiliser le makefile pour vérifier ces modifications (makefile est fait pour ça) | dans dossier categ on fait une somme sha1 ou md5 de tous les fichiers. On copie dans le dossier porteail. Au début du programme, on compare somme de tous les fichiers du dossier categ avec la somme contenue dans dossier porteail (s'il existe). Si les sommes sont pareilles, alors on quitte le makefile
- http://stackoverflow.com/questions/1657232/how-can-i-calculate-an-md5-checksum-of-a-directory
- find directory -type f -print0 | xargs -0 md5sum >> file.md5 (ceci est pour vérifier par exemple les *.txt !!!)
- Tenter un ls categ |md5sum ou bien for i in `ls categ`; do md5sum categ/$i; done > somme.md5
- Utiliser ça pour vérifier sommes de contrôle : md5 * | diff /path/to/md5.checksum -
- find categ -type f -name *.txt -exec md5sum {} + | awk '{print $1}' |sort |diff somme.md5 -|wc -l
- compléter l'adresse des images pour l'insertion dans le contenu
- vérifier l'existence de l'image avant de l'ajouter
- si pas d'image ou image inexistante, mettre une image générique
- Doc : donner l'astuce pour ordonner les catégories dans le fichier : mettre 00-nom_fichier.txt, puis 01-autre_categorie.txt, etc.
- imaginer un système d'héritage des feuilles de style pour ne modifier que les couleurs de la page, en dehors de la structure. => fait avec une double inclusion de feuille de style dans la page HTML
- permettre l'ajout de plusieurs CSS dans HEAD
- créer plusieurs feuilles de style (couleurs, positionnement des éléments, etc.)
- ne copier QUE les images utilisées
- faire un export en XHTML si possible (ajouter l'extension au fichier de destination choisi)
- Simplifier le code HTML et CSS
- enlever les div en trop
- changer les div#abc en #abc dans le CSS
- commenter le code CSS
- Fait. Seulement pas de inline-block pour un meilleur affichage | Changer les DIV en une liste d'éléments puis mettre display: inline-block; pour l'affichage. Si liste, alors mettre des point-virgules à la fin de chaque ligne (et les cacher en css)
- Supprimer les descriptions des logos pour un meilleur affichage (Cf. elinks par exemple pour une démonstration verbeuse) : les ajouter dans le CSS. Alt = rien du tout, et title = nom donné.
- Meilleur affichage dans les navigateurs textes (seulement les alt des images à modifier)
- ajouter une extension aux fichiers images copiées
- Simplifier le fichier LISMOI
- ne donner que quelques lignes simples pour lancer le programme : installer, configurer, lancer !
- supprimer les chapitres inutiles
- Simplifier le fichier Makefile au niveau des variables pour réduire leur nombre
- FAIT | Réorganiser les variables du GNUmakefile pour rendre plus simple le choix des variables par l'utilisateur. Afin qu'il n'ai JAMAIS à mettre d'autre variables dans le contenu. Par exemple jamais écrire cela : $(DOSSIER)/fichier.html !!!!
- FAIT | ne laisser que la variable CSS_COULEUR ? => trouver une solution potable
- FAIT | ne laisser que les variables fondamentales pour l'utilisateur comme le choix du titre, si intro, si menu
- FAIT | déplacer les variables inutiles à l'utilisateur dans un autre fichier de config qu'on inclue ? Ou bien les mettre avant le include configrc, comme ça l'utilisateur peut les redéfinir si besoin !
- FAIT | mettre toutes les variables en majuscules OU en minuscule (peut-être les variables en majuscules pour les principales, et celles du Makefile en minuscule
- FAIT | renommer les variables correctement !
- Vérifier/optimiser les cibles du makefile
- Vérifier/optimiser les dépendances du makefile
- Vérifier l'existence des dossiers suivants : COMPOSANTS, IMAGE, STYLE, CSS, CIBLE
- ajouter les fichiers générés pour chaque section du makefile (ceci de manière intelligente… si possible !)
- Bug: si une URL possède plusieurs &
- HTML 5 avec header et footer
- Trouver une méthode plus fine pour trouver le nombre de catégories par fichier (autre qu'un grep par exemple)
- Permettre d'ajouter des fichiers statiques (pour permettre par exemple de donner un lien vers une version d'un logiciel sur la page d'accueil)
- aside en NAV !!!
- faire une section install dans le makefile permettant d'installer dans DESTDIR
- Transformer variables en anglais
- Que donne une ligne vide dans le fichier de catégorie ? => à tester comme cas possible

10
config.toml Normal file
View File

@ -0,0 +1,10 @@
languageCode = "fr"
title = "Depotoi.re"
disableRSS = true
disableSitemap = true
buildDrafts = true
uglyURLs = true
[params]
style = "blue.css"
default_img = "generique.png"

View File

@ -1,44 +0,0 @@
###########################
## Main configuration ##
###########################
# Homepage title
TITLE = Depotoire
# CSS color file
STYLE = black.css
# Menu (if needed)
#MENU = menu.html
# Introduction (if needed)
INTRO = intro.html
# Destination directory
DESTINATION = porteail
###########################
## Additional config ##
###########################
##--[[ miscellaneous ]]--##
LANG = fr
#HOMEPAGE = Homepage - My portal
## File extension to be used to read categories
CATEGORIES_EXT = dp
## Default image
#DEFAULT_IMG = generique.png
## Templates
#TEMPLATE_ELEMENT = element.html
#TEMPLATE_INDEX = index.html
#TEMPLATE_CATEG = categories.html
#
###--[[ directories ]]--##
#
#COMPONENTS = composants
#CATEGORIES = categ
#IMAGES = img
#IMAGES_DESTINATION = image
#CSS = style
INSTALLDIR = ./www
#
###--[[ style ]]--##
#
#CSS_NAME = defaut.css

View File

@ -1,44 +0,0 @@
###########################
## Main configuration ##
###########################
# Homepage title
TITLE = My portal
# CSS color file
STYLE = black.css
# Menu (if needed)
#MENU = menu.html
# Introduction (if needed)
#INTRO = introduction.html
# Destination directory
DESTINATION = porteail
###########################
## Additional config ##
###########################
##--[[ miscellaneous ]]--##
#LANG = en
#HOMEPAGE = Homepage - My portal
## File extension to be used to read categories
#CATEGORIES_EXT = txt
## Default image
#DEFAULT_IMG = generique.png
## Templates
#TEMPLATE_ELEMENT = element.html
#TEMPLATE_INDEX = index.html
#TEMPLATE_CATEG = categories.html
#
###--[[ directories ]]--##
#
#COMPONENTS = composants
#CATEGORIES = categ
#IMAGES = img
#IMAGES_DESTINATION = image
#CSS = style
#INSTALLDIR = ${HOME}/public_html
#
###--[[ style ]]--##
#
#CSS_NAME = defaut.css

View File

@ -0,0 +1,14 @@
+++
date = "2016-01-21T19:38:18+01:00"
draft = false
title = "Domaines"
+++
Ils s'hébergent chez nous :
* {{< button title="Arche à blogs" href="http://arche.depotoi.re" src="actions/go-home.png" >}}
* {{< button title="Fabuleux" href="http://fabuleux.depotoi.re" src="fabuleux_logo.png" >}}
* {{< button title="Almanax Dofus" href="http://almanax.depotoi.re" src="dofus.png" >}}
* {{< button title="Lighty Dmap" href="http://dmap.depotoi.re" src="dofus.png" >}}
* {{< button title="Portail Dofus" href="http://dofus.depotoi.re" src="dofus.png" >}}

View File

@ -0,0 +1,13 @@
+++
date = "2016-01-21T19:38:18+01:00"
draft = false
title = "Nos projets"
+++
* {{< button title="Forge" href="http://forge.depotoi.re" src="forge_64.png" >}}
* {{< button title="BlogBox" href="http://blogbox.depotoi.re" src="apps/utilities-file-archiver.png" >}}
* {{< button title="ELI" href="http://eli.depotoi.re" src="actions/view-pim-notes.png" >}}
* {{< button title="Makefly" href="http://makefly.depotoi.re" src="makefly-48x48.gif" >}}
* {{< button title="hugo-portal" href="http://github.com/blankoworld/hugo-portal" src="actions/office-chart-ring.png" >}}
* {{< button title="Rave Comment" href="http://rave.depotoi.re/" src="rave.png" >}}

View File

@ -1,317 +0,0 @@
#!/usr/bin/env lua
-- porteail.lua
--[[ Requirements ]]--
require 'lfs'
--[[ Variables ]]--
-- Mandatories files
local configFile = './' .. 'configrc'
-- Default directories values
local currentpath = os.getenv('CURDIR') or '.'
local default_dir_category = 'categ'
local default_dir_component = 'composants'
local default_dir_destination = 'porteail'
local default_dir_img_destination = 'image'
local default_dir_img_source = 'img'
local default_dir_css_source = 'style'
local default_dir_lang = 'lang'
-- Default files values
local default_img_filename = 'generique.png'
local default_index_filename = 'index.html'
local default_template_index_filename = 'index.html'
local default_template_categ_filename = 'categories.html'
local default_template_element_filename = 'element.html'
local default_css_filename = 'black.css'
local default_css_menu_without = 'without_menu.css'
local default_css_menu_with = 'with_menu.css'
-- Other defaults values
local version = os.getenv('VERSION') or '(Unknown version)'
local default_categ_extension = 'txt'
local DIR_SEP = '/'
local default_css_name = 'Default'
local default_title = 'My portal'
local default_homepage_title = ' - Homepage'
local default_language = 'en'
--[[ Functions ]]--
function readFile(path, mode)
result = ''
if not mode then
mode = 'r'
end
if mode ~= 'r' and mode ~= 'rb' then
print('Unknown read mode!')
os.exit(1)
end
attr = lfs.attributes(path)
if attr and attr.mode == 'file' then
f = assert(io.open(path, mode))
result = assert(f:read('*a'))
assert(f:close())
end
return result
end
function getConfig(file)
result = {}
f = assert(io.open(file, 'r'))
while true do
line = f.read(f)
if not line then break end
local key = line:match('([^#].-)[ ]+=')
local val = line:match('=[ ]+(.*)')
local comment = string.find(line, '^#+(.*)')
if comment then
-- do nothing with comment
elseif key then
result[key] = val
end
end
assert(f:close())
return result
end
function replace(string, table)
return string:gsub("$(%b{})", function(string)
return table[string:sub(2,-2)]
end)
end
function listing (path, extension)
files = {}
if lfs.attributes(path) then
for file in lfs.dir(path) do
if file ~= "." and file ~= ".." then
local f = path..'/'..file
local attr = lfs.attributes (f)
filext = (string.match(file, "[^\\/]-%.?([^%.\\/]*)$"))
if attr.mode == 'file' and filext == extension then
table.insert(files, f)
end
end
end
else
files = nil
end
return files
end
function basename (string, suffix)
string = string or ''
local basename = string.gsub (string, '[^'.. DIR_SEP ..']*'.. DIR_SEP ..'', '')
if suffix then
basename = string.gsub (basename, suffix, '')
end
return basename
end
function processImage(image, source, img_destination, destination, default_img)
-- if no image given, use default one
if not image or image == nil or image == '' then
image = default_img
end
-- create image weblink
result = img_destination .. '/' .. basename(image)
-- check if this image exists
attr = lfs.attributes(destination .. '/' .. result)
if not attr then
img_path = source .. '/' .. image
f = assert(io.open(img_path, 'rb'))
img_src = assert(f:read('*a'))
assert(f:close())
img_dest = assert(io.open(destination .. '/' .. result, 'wb'))
assert(img_dest:write(img_src))
assert(img_dest:close())
end
return result
end
function process(filepath, template_categ, template_element, img_destination, destination, img_source, default_img)
-- parse given file
local elements = {}
local categ_title = ''
local categ_description = ''
local categ_count = 0
-- parse category file
for line in io.lines(filepath) do
local element = ''
-- check if this line is:
-- a comment ("# my comment"),
-- a category ("[[My category]]Its description")
-- or an element ("Title##Description##URL##Image")
is_comment = string.find(line, '^#+.*')
is_title = string.find(line, '%[%[(.*)%]%](.*)')
is_element = string.find(line, '(.*)##(.*)##(.*)##(.*)')
-- processing lines to fetch data
if is_comment then
-- do nothing because it's a comment
elseif is_title then
for t in string.gmatch(line, '%[%[(.*)%]%].*') do categ_title = categ_title .. t end
for d in string.gmatch(line, '%[%[.*%]%](.*)') do categ_description = categ_description .. d end
categ_count = categ_count + 1
elseif is_element then
title = ''
description = ''
url = ''
img = ''
for t in string.gmatch(line, '(.*)##.*##.*##.*') do title = title .. t end
for d in string.gmatch(line, '.*##.*##(.*)##.*') do description = description .. d end
for u in string.gmatch(line, '.*##(.*)##.*##.*') do url = url .. u end