summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--COPYING674
-rw-r--r--Cargo.lock26
-rw-r--r--Cargo.toml2
-rw-r--r--INSTALL368
-rwxr-xr-xcrates/gipfel-web/serve-here.sh12
-rw-r--r--crates/wipfel/Cargo.toml (renamed from crates/gipfel-web/Cargo.toml)4
-rw-r--r--crates/wipfel/README.md (renamed from crates/gipfel-web/README.md)6
-rw-r--r--crates/wipfel/index.html (renamed from crates/gipfel-web/index.html)2
-rwxr-xr-xcrates/wipfel/serve-here.sh12
-rw-r--r--crates/wipfel/src/app.rs (renamed from crates/gipfel-web/src/app.rs)4
-rw-r--r--crates/wipfel/src/bridge.rs (renamed from crates/gipfel-web/src/bridge.rs)0
-rw-r--r--crates/wipfel/src/canvas_view.rs (renamed from crates/gipfel-web/src/canvas_view.rs)0
-rw-r--r--crates/wipfel/src/compass.rs (renamed from crates/gipfel-web/src/compass.rs)0
-rw-r--r--crates/wipfel/src/main.rs (renamed from crates/gipfel-web/src/main.rs)0
-rw-r--r--crates/wipfel/src/markers.rs (renamed from crates/gipfel-web/src/markers.rs)0
-rw-r--r--crates/wipfel/src/widgets.rs (renamed from crates/gipfel-web/src/widgets.rs)0
-rw-r--r--crates/wipfel/www/style.css (renamed from crates/gipfel-web/www/style.css)0
-rw-r--r--plan.md371
-rw-r--r--wasm-plan.md10
19 files changed, 1452 insertions, 39 deletions
diff --git a/COPYING b/COPYING
new file mode 100644
index 0000000..f288702
--- /dev/null
+++ b/COPYING
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://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 <https://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
+<https://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
+<https://www.gnu.org/licenses/why-not-lgpl.html>.
diff --git a/Cargo.lock b/Cargo.lock
index 829f24f..0be6ad5 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -1816,19 +1816,6 @@ dependencies = [
]
[[package]]
-name = "gipfel-web"
-version = "0.5.5"
-dependencies = [
- "flate2",
- "gipfel-core",
- "js-sys",
- "wasm-bindgen",
- "wasm-bindgen-futures",
- "web-sys",
- "yew",
-]
-
-[[package]]
name = "gl_generator"
version = "0.14.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
@@ -6673,6 +6660,19 @@ dependencies = [
]
[[package]]
+name = "wipfel"
+version = "0.5.5"
+dependencies = [
+ "flate2",
+ "gipfel-core",
+ "js-sys",
+ "wasm-bindgen",
+ "wasm-bindgen-futures",
+ "web-sys",
+ "yew",
+]
+
+[[package]]
name = "wit-bindgen"
version = "0.57.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
diff --git a/Cargo.toml b/Cargo.toml
index 5de748e..196bcda 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
[workspace]
resolver = "2"
-members = ["crates/gipfel-core", "crates/gipfel-cli", "crates/gipfel-app", "crates/gipfel-wasm", "crates/gipfel-web"]
+members = ["crates/gipfel-core", "crates/gipfel-cli", "crates/gipfel-app", "crates/gipfel-wasm", "crates/wipfel"]
# Single source of truth for metadata inherited by every crate via
# `version.workspace = true` etc. Bump `version` here on release; the
diff --git a/INSTALL b/INSTALL
new file mode 100644
index 0000000..e82fd21
--- /dev/null
+++ b/INSTALL
@@ -0,0 +1,368 @@
+Installation Instructions
+*************************
+
+ Copyright (C) 1994-1996, 1999-2002, 2004-2017, 2020-2021 Free
+Software Foundation, Inc.
+
+ Copying and distribution of this file, with or without modification,
+are permitted in any medium without royalty provided the copyright
+notice and this notice are preserved. This file is offered as-is,
+without warranty of any kind.
+
+Basic Installation
+==================
+
+ Briefly, the shell command './configure && make && make install'
+should configure, build, and install this package. The following
+more-detailed instructions are generic; see the 'README' file for
+instructions specific to this package. Some packages provide this
+'INSTALL' file but do not implement all of the features documented
+below. The lack of an optional feature in a given package is not
+necessarily a bug. More recommendations for GNU packages can be found
+in *note Makefile Conventions: (standards)Makefile Conventions.
+
+ The 'configure' shell script attempts to guess correct values for
+various system-dependent variables used during compilation. It uses
+those values to create a 'Makefile' in each directory of the package.
+It may also create one or more '.h' files containing system-dependent
+definitions. Finally, it creates a shell script 'config.status' that
+you can run in the future to recreate the current configuration, and a
+file 'config.log' containing compiler output (useful mainly for
+debugging 'configure').
+
+ It can also use an optional file (typically called 'config.cache' and
+enabled with '--cache-file=config.cache' or simply '-C') that saves the
+results of its tests to speed up reconfiguring. Caching is disabled by
+default to prevent problems with accidental use of stale cache files.
+
+ If you need to do unusual things to compile the package, please try
+to figure out how 'configure' could check whether to do them, and mail
+diffs or instructions to the address given in the 'README' so they can
+be considered for the next release. If you are using the cache, and at
+some point 'config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file 'configure.ac' (or 'configure.in') is used to create
+'configure' by a program called 'autoconf'. You need 'configure.ac' if
+you want to change it or regenerate 'configure' using a newer version of
+'autoconf'.
+
+ The simplest way to compile this package is:
+
+ 1. 'cd' to the directory containing the package's source code and type
+ './configure' to configure the package for your system.
+
+ Running 'configure' might take a while. While running, it prints
+ some messages telling which features it is checking for.
+
+ 2. Type 'make' to compile the package.
+
+ 3. Optionally, type 'make check' to run any self-tests that come with
+ the package, generally using the just-built uninstalled binaries.
+
+ 4. Type 'make install' to install the programs and any data files and
+ documentation. When installing into a prefix owned by root, it is
+ recommended that the package be configured and built as a regular
+ user, and only the 'make install' phase executed with root
+ privileges.
+
+ 5. Optionally, type 'make installcheck' to repeat any self-tests, but
+ this time using the binaries in their final installed location.
+ This target does not install anything. Running this target as a
+ regular user, particularly if the prior 'make install' required
+ root privileges, verifies that the installation completed
+ correctly.
+
+ 6. You can remove the program binaries and object files from the
+ source code directory by typing 'make clean'. To also remove the
+ files that 'configure' created (so you can compile the package for
+ a different kind of computer), type 'make distclean'. There is
+ also a 'make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+ 7. Often, you can also type 'make uninstall' to remove the installed
+ files again. In practice, not all packages have tested that
+ uninstallation works correctly, even though it is required by the
+ GNU Coding Standards.
+
+ 8. Some packages, particularly those that use Automake, provide 'make
+ distcheck', which can by used by developers to test that all other
+ targets like 'make install' and 'make uninstall' work correctly.
+ This target is generally not run by end users.
+
+Compilers and Options
+=====================
+
+ Some systems require unusual options for compilation or linking that
+the 'configure' script does not know about. Run './configure --help'
+for details on some of the pertinent environment variables.
+
+ You can give 'configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here is
+an example:
+
+ ./configure CC=c99 CFLAGS=-g LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+ You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you can use GNU 'make'. 'cd' to the
+directory where you want the object files and executables to go and run
+the 'configure' script. 'configure' automatically checks for the source
+code in the directory that 'configure' is in and in '..'. This is known
+as a "VPATH" build.
+
+ With a non-GNU 'make', it is safer to compile the package for one
+architecture at a time in the source code directory. After you have
+installed the package for one architecture, use 'make distclean' before
+reconfiguring for another architecture.
+
+ On MacOS X 10.5 and later systems, you can create libraries and
+executables that work on multiple system types--known as "fat" or
+"universal" binaries--by specifying multiple '-arch' options to the
+compiler but only a single '-arch' option to the preprocessor. Like
+this:
+
+ ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
+ CPP="gcc -E" CXXCPP="g++ -E"
+
+ This is not guaranteed to produce working output in all cases, you
+may have to build one architecture at a time and combine the results
+using the 'lipo' tool if you have problems.
+
+Installation Names
+==================
+
+ By default, 'make install' installs the package's commands under
+'/usr/local/bin', include files under '/usr/local/include', etc. You
+can specify an installation prefix other than '/usr/local' by giving
+'configure' the option '--prefix=PREFIX', where PREFIX must be an
+absolute file name.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+pass the option '--exec-prefix=PREFIX' to 'configure', the package uses
+PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like '--bindir=DIR' to specify different values for particular
+kinds of files. Run 'configure --help' for a list of the directories
+you can set and what kinds of files go in them. In general, the default
+for these options is expressed in terms of '${prefix}', so that
+specifying just '--prefix' will affect all of the other directory
+specifications that were not explicitly provided.
+
+ The most portable way to affect installation locations is to pass the
+correct locations to 'configure'; however, many packages provide one or
+both of the following shortcuts of passing variable assignments to the
+'make install' command line to change installation locations without
+having to reconfigure or recompile.
+
+ The first method involves providing an override variable for each
+affected directory. For example, 'make install
+prefix=/alternate/directory' will choose an alternate location for all
+directory configuration variables that were expressed in terms of
+'${prefix}'. Any directories that were specified during 'configure',
+but not in terms of '${prefix}', must each be overridden at install time
+for the entire installation to be relocated. The approach of makefile
+variable overrides for each directory variable is required by the GNU
+Coding Standards, and ideally causes no recompilation. However, some
+platforms have known limitations with the semantics of shared libraries
+that end up requiring recompilation when using this method, particularly
+noticeable in packages that use GNU Libtool.
+
+ The second method involves providing the 'DESTDIR' variable. For
+example, 'make install DESTDIR=/alternate/directory' will prepend
+'/alternate/directory' before all installation names. The approach of
+'DESTDIR' overrides is not required by the GNU Coding Standards, and
+does not work on platforms that have drive letters. On the other hand,
+it does better at avoiding recompilation issues, and works well even
+when some directory options were not specified in terms of '${prefix}'
+at 'configure' time.
+
+Optional Features
+=================
+
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving 'configure' the
+option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'.
+
+ Some packages pay attention to '--enable-FEATURE' options to
+'configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to '--with-PACKAGE' options, where PACKAGE
+is something like 'gnu-as' or 'x' (for the X Window System). The
+'README' should mention any '--enable-' and '--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, 'configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the 'configure' options '--x-includes=DIR' and
+'--x-libraries=DIR' to specify their locations.
+
+ Some packages offer the ability to configure how verbose the
+execution of 'make' will be. For these packages, running './configure
+--enable-silent-rules' sets the default to minimal output, which can be
+overridden with 'make V=1'; while running './configure
+--disable-silent-rules' sets the default to verbose, which can be
+overridden with 'make V=0'.
+
+Particular systems
+==================
+
+ On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC
+is not installed, it is recommended to use the following options in
+order to use an ANSI C compiler:
+
+ ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
+
+and if that doesn't work, install pre-built binaries of GCC for HP-UX.
+
+ HP-UX 'make' updates targets which have the same timestamps as their
+prerequisites, which makes it generally unusable when shipped generated
+files such as 'configure' are involved. Use GNU 'make' instead.
+
+ On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
+parse its '<wchar.h>' header file. The option '-nodtk' can be used as a
+workaround. If GNU CC is not installed, it is therefore recommended to
+try
+
+ ./configure CC="cc"
+
+and if that doesn't work, try
+
+ ./configure CC="cc -nodtk"
+
+ On Solaris, don't put '/usr/ucb' early in your 'PATH'. This
+directory contains several dysfunctional programs; working variants of
+these programs are available in '/usr/bin'. So, if you need '/usr/ucb'
+in your 'PATH', put it _after_ '/usr/bin'.
+
+ On Haiku, software installed for all users goes in '/boot/common',
+not '/usr/local'. It is recommended to use the following options:
+
+ ./configure --prefix=/boot/common
+
+Specifying the System Type
+==========================
+
+ There may be some features 'configure' cannot figure out
+automatically, but needs to determine by the type of machine the package
+will run on. Usually, assuming the package is built to be run on the
+_same_ architectures, 'configure' can figure that out, but if it prints
+a message saying it cannot guess the machine type, give it the
+'--build=TYPE' option. TYPE can either be a short name for the system
+type, such as 'sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS
+ KERNEL-OS
+
+ See the file 'config.sub' for the possible values of each field. If
+'config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the option '--target=TYPE' to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with '--host=TYPE'.
+
+Sharing Defaults
+================
+
+ If you want to set default values for 'configure' scripts to share,
+you can create a site shell script called 'config.site' that gives
+default values for variables like 'CC', 'cache_file', and 'prefix'.
+'configure' looks for 'PREFIX/share/config.site' if it exists, then
+'PREFIX/etc/config.site' if it exists. Or, you can set the
+'CONFIG_SITE' environment variable to the location of the site script.
+A warning: not all 'configure' scripts look for a site script.
+
+Defining Variables
+==================
+
+ Variables not defined in a site shell script can be set in the
+environment passed to 'configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the 'configure' command line, using 'VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+causes the specified 'gcc' to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an
+Autoconf limitation. Until the limitation is lifted, you can use this
+workaround:
+
+ CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+'configure' Invocation
+======================
+
+ 'configure' recognizes the following options to control how it
+operates.
+
+'--help'
+'-h'
+ Print a summary of all of the options to 'configure', and exit.
+
+'--help=short'
+'--help=recursive'
+ Print a summary of the options unique to this package's
+ 'configure', and exit. The 'short' variant lists options used only
+ in the top level, while the 'recursive' variant lists options also
+ present in any nested packages.
+
+'--version'
+'-V'
+ Print the version of Autoconf used to generate the 'configure'
+ script, and exit.
+
+'--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally 'config.cache'. FILE defaults to '/dev/null' to
+ disable caching.
+
+'--config-cache'
+'-C'
+ Alias for '--cache-file=config.cache'.
+
+'--quiet'
+'--silent'
+'-q'
+ Do not print messages saying which checks are being made. To
+ suppress all normal output, redirect it to '/dev/null' (any error
+ messages will still be shown).
+
+'--srcdir=DIR'
+ Look for the package's source code in directory DIR. Usually
+ 'configure' can determine that directory automatically.
+
+'--prefix=DIR'
+ Use DIR as the installation prefix. *note Installation Names:: for
+ more details, including other options available for fine-tuning the
+ installation locations.
+
+'--no-create'
+'-n'
+ Run the configure checks, but stop before creating any output
+ files.
+
+'configure' also accepts some other, not widely useful, options. Run
+'configure --help' for more details.
diff --git a/crates/gipfel-web/serve-here.sh b/crates/gipfel-web/serve-here.sh
deleted file mode 100755
index 54038a6..0000000
--- a/crates/gipfel-web/serve-here.sh
+++ /dev/null
@@ -1,12 +0,0 @@
-#!/bin/sh
-# Build gipfel-web for wasm and refresh the static dist dir served from
-# /tmp/gipfel-web-dist (python http.server on :8090). Dev-only helper.
-set -e
-cd "$(dirname "$0")/../.."
-cargo build -p gipfel-web --target wasm32-unknown-unknown --release
-DIST=/tmp/gipfel-web-dist
-mkdir -p "$DIST"
-wasm-bindgen --target web --out-dir "$DIST" target/wasm32-unknown-unknown/release/gipfel-web.wasm
-cp crates/gipfel-web/www/style.css "$DIST/"
-gzip -9 -n -c gipfel.dat > "$DIST/gipfel.dat.gz"
-echo "dist refreshed: $(ls -la "$DIST" | awk '{s+=$5} END {print s" bytes"}')"
diff --git a/crates/gipfel-web/Cargo.toml b/crates/wipfel/Cargo.toml
index 303750a..e1e39e1 100644
--- a/crates/gipfel-web/Cargo.toml
+++ b/crates/wipfel/Cargo.toml
@@ -1,9 +1,9 @@
[package]
-name = "gipfel-web"
+name = "wipfel"
version.workspace = true
edition.workspace = true
license.workspace = true
-description = "gipfel web — browser front end (WASM)"
+description = "wipfel — web based gipfel photogrammetry for mountain images"
[dependencies]
gipfel-core = { path = "../gipfel-core" }
diff --git a/crates/gipfel-web/README.md b/crates/wipfel/README.md
index 74e93c5..37c09ea 100644
--- a/crates/gipfel-web/README.md
+++ b/crates/wipfel/README.md
@@ -1,4 +1,4 @@
-# gipfel-web
+# wipfel
Browser front end for gipfel (WASM, Yew + canvas 2D). See
[`/wasm-plan.md`](../../wasm-plan.md) for the overall plan and milestones.
@@ -18,7 +18,7 @@ cargo install --locked trunk
Serve with hot reload:
```sh
-cd crates/gipfel-web
+cd crates/wipfel
trunk serve --port 8090 # then open http://localhost:8090
```
@@ -43,5 +43,5 @@ trunk build --release
- The base image is decoded by the browser (`createImageBitmap`), not
by the `image` crate — faster decode and GPU-backed blitting.
-- The crate compiles natively (`cargo check -p gipfel-web`) so it can
+- The crate compiles natively (`cargo check -p wipfel`) so it can
be checked in CI without a wasm toolchain; runtime is wasm-only.
diff --git a/crates/gipfel-web/index.html b/crates/wipfel/index.html
index 32ec87f..d00adbe 100644
--- a/crates/gipfel-web/index.html
+++ b/crates/wipfel/index.html
@@ -3,7 +3,7 @@
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <title>gipfel web</title>
+ <title>wipfel — web based gipfel photogrammetry</title>
<link data-trunk rel="css" href="www/style.css" />
<link data-trunk rel="rust" />
</head>
diff --git a/crates/wipfel/serve-here.sh b/crates/wipfel/serve-here.sh
new file mode 100755
index 0000000..9667965
--- /dev/null
+++ b/crates/wipfel/serve-here.sh
@@ -0,0 +1,12 @@
+#!/bin/sh
+# Build wipfel for wasm and refresh the static dist dir served from
+# /tmp/wipfel-dist (python http.server on :8090). Dev-only helper.
+set -e
+cd "$(dirname "$0")/../.."
+cargo build -p wipfel --target wasm32-unknown-unknown --release
+DIST=/tmp/wipfel-dist
+mkdir -p "$DIST"
+wasm-bindgen --target web --out-dir "$DIST" target/wasm32-unknown-unknown/release/wipfel.wasm
+cp crates/wipfel/www/style.css "$DIST/"
+gzip -9 -n -c gipfel.dat > "$DIST/gipfel.dat.gz"
+echo "dist refreshed: $(ls -la "$DIST" | awk '{s+=$5} END {print s" bytes"}')"
diff --git a/crates/gipfel-web/src/app.rs b/crates/wipfel/src/app.rs
index f4b0de4..eeb82d6 100644
--- a/crates/gipfel-web/src/app.rs
+++ b/crates/wipfel/src/app.rs
@@ -679,8 +679,8 @@ pub fn app() -> Html {
html! {
<div class="app" ondrop={on_drop} ondragover={on_dragover}>
<aside class="sidebar">
- <h1>{ "gipfel" }</h1>
- <p class="tag">{ "web · W2 markers" }</p>
+ <h1>{ "wipfel" }</h1>
+ <p class="tag">{ "web gipfel photogrammetry" }</p>
<button onclick={open_picker}>{ "Open image…" }</button>
<button onclick={fit} disabled={bitmap.is_none()}>{ "Fit to window" }</button>
<input
diff --git a/crates/gipfel-web/src/bridge.rs b/crates/wipfel/src/bridge.rs
index 6dbba93..6dbba93 100644
--- a/crates/gipfel-web/src/bridge.rs
+++ b/crates/wipfel/src/bridge.rs
diff --git a/crates/gipfel-web/src/canvas_view.rs b/crates/wipfel/src/canvas_view.rs
index 9d4338e..9d4338e 100644
--- a/crates/gipfel-web/src/canvas_view.rs
+++ b/crates/wipfel/src/canvas_view.rs
diff --git a/crates/gipfel-web/src/compass.rs b/crates/wipfel/src/compass.rs
index b539e07..b539e07 100644
--- a/crates/gipfel-web/src/compass.rs
+++ b/crates/wipfel/src/compass.rs
diff --git a/crates/gipfel-web/src/main.rs b/crates/wipfel/src/main.rs
index 741393b..741393b 100644
--- a/crates/gipfel-web/src/main.rs
+++ b/crates/wipfel/src/main.rs
diff --git a/crates/gipfel-web/src/markers.rs b/crates/wipfel/src/markers.rs
index d024f2e..d024f2e 100644
--- a/crates/gipfel-web/src/markers.rs
+++ b/crates/wipfel/src/markers.rs
diff --git a/crates/gipfel-web/src/widgets.rs b/crates/wipfel/src/widgets.rs
index 1d22bac..1d22bac 100644
--- a/crates/gipfel-web/src/widgets.rs
+++ b/crates/wipfel/src/widgets.rs
diff --git a/crates/gipfel-web/www/style.css b/crates/wipfel/www/style.css
index 5122c43..5122c43 100644
--- a/crates/gipfel-web/www/style.css
+++ b/crates/wipfel/www/style.css
diff --git a/plan.md b/plan.md
new file mode 100644
index 0000000..9796beb
--- /dev/null
+++ b/plan.md
@@ -0,0 +1,371 @@
+# Plan: Porting gipfel to a Cosmic DE Application in Rust
+
+Status: **planning only — no implementation started**
+Reference: C++/FLTK sources in `src/` (gipfel 0.4.1, commit `45425dd`)
+
+---
+
+## 1. Analysis of the Existing Application
+
+### 1.1 What gipfel does
+
+gipfel is "georeferencing for arbitrary images": given a photo, the GPS position of
+the camera, and two or more manually identified peaks in the image, it fits the
+camera view parameters and then labels all other peaks/POIs from a GPS database
+directly on the image. It also stitches referenced images into panoramas.
+
+### 1.2 Module map (current C++/FLTK)
+
+| Component | Files | Responsibility |
+|---|---|---|
+| Main / control window | `gipfel.cxx` | CLI parsing, two FLTK windows (control + scrolled image), menu bar, sliders/dials, stitching & export CLI modes |
+| Image canvas | `GipfelWidget.cxx/.H` | Draws image + labels + markers + GPS track; mouse interaction (see 1.4) |
+| Domain model | `Panorama.cxx/.H` | Viewpoint (lat/lon/height), hill DB, azimuth/nick/distance with earth curvature (`EARTH_RADIUS 6371000.785`), refraction model (Tom Chester approximation), hidden-object detection (cone model + `hide_value` / "Visibility" slider), visible-hill computation |
+| Projection + fit | `ProjectionLSQ.*`, `ProjectionRectilinear.*`, `ProjectionCylindrical.*` | Non-linear least squares (GSL `gsl_multifit_fdfsolver_lmsder`, max 100 iterations) over `ViewParams {a_center, a_nick, a_tilt, scale, k0, k1, x0}`. Fit level depends on # marked hills: 1 hill → 2 params, 2–3 → 4 params, ≥4 → 7 params (lens distortion calibration) |
+| **Symbolic codegen** | `lsq_rectilinear.mac`, `lsq_cylindrical.mac`, `expr2c.mac`, `Makefile.lsq_funcs` | **maxima** computes the projection equations and all analytic partial derivatives (Jacobian) symbolically and emits C functions `mac_x`, `mac_y`, `mac_x_d*` into `Projection*_funcs.cxx` |
+| Data model | `Hill.cxx/.H` | `Hill {phi, lam, height, alph, a_nick, dist, x, y, flags}`, `Hills` collection, CSV loader, duplicate marking, sorting |
+| Metadata | `ImageMetaData.cxx/.H` | EXIF read via exiv2 (GPS lat/lon/alt, focal length, 35mm-equiv, Make/Model) + own serialization of fit results into the **JPEG comment** (`gipfel: longitude …, latitude …, height …, direction …, nick …, tilt …, focal_length_35mm …, projection type N, k0 …, k1 …, x0 …`) |
+| Stitching | `Stitch.*`, `ScanImage.*`, `OutputImage.*`, `JPEG/TIFF/PreviewOutputImage.*` | Resample a view-angle range across referenced images (nearest/bicubic), output JPEG/TIFF (8/16-bit) or on-screen preview |
+| Custom widgets | `Fl_Value_Dial.*`, `Fl_Search_Chooser.*`, `choose_hill.*` | Compass dial (view direction), searchable hill picker dialog |
+| Preferences | `GipfelWidget.cxx` (Fl_Preferences) | Distortion profiles in `$HOME/.fltk/Johannes.HofmannATgmx.de/gipfel` |
+| Data file | `gipfel.dat` (~21k rows) | `SHORTNAME,NAME,DESCRIPTION,LATITUDE,LONGITUDE,HEIGHT` per line |
+
+### 1.3 Data flow
+
+```
+gipfel.dat ─┐
+EXIF/JPEG ──┼─► Panorama (viewpoint, angles, distances, refraction, visibility)
+user marks ─┘ │
+ ▼
+ ProjectionLSQ.comp_params() ◄── maxima-generated mac_* + Jacobian
+ │ ViewParams
+ ▼
+ get_coordinates(alph, nick) → (x, y) per hill ─► GipfelWidget redraw
+```
+
+### 1.4 Interaction model (to preserve / improve)
+
+- **Middle-click** a label cross → mark hill as known (turns red)
+- **Left-drag** a marked cross → position it on the peak; on release, refit
+- **Right-click** → context menu: "Find Peak", "Hide/Unhide <name>"
+- **Hover** → tooltip "name (height m), distance x.xkm"
+- Control window: compass dial (view direction), sliders (nick, tilt, focal length
+ in 35mm, visibility, track width), numeric inputs (viewpoint lat/lon/height,
+ distortion k0/k1/x0)
+- CLI modes: `-s` stitch, `-e/-E` export hills, `-p` export position
+
+### 1.5 Constraints carried into the port
+
+- **The algorithm stays as-is**: same projection math, same LM fit strategy, same
+ refraction/visibility models, **same maxima-based symbolic derivative generation**.
+- Wire formats stay compatible: `gipfel.dat` CSV, the JPEG-comment parameter string
+ (so images referenced with the old gipfel still open correctly), distortion
+ profile semantics.
+
+---
+
+## 2. Target Application
+
+**gipfel-rs**: a native [Cosmic](https://system76.com/cosmic) DE application built
+with `cosmic-toolkit` (`cosmic::app`, iced under the hood), single window, with
+optional image zooming.
+
+### 2.1 UI concept — single window
+
+The FLTK version uses two windows (control + image) plus modal dialogs. The Cosmic
+port consolidates everything into one window:
+
+```
+┌──────────────────────────────────────────────────────────────────────┐
+│ ⌘ Menu (File / Projection / Distortion / Options / Help) │
+├──────────────────────────────────────────────────────────────────────┤
+│ Viewpoint: <Innsbruck, …> [✎] Lat [____] Lon [____] Hgt [____] │
+├───────────────────────────────┬──────────────────────────────────────┤
+│ │ Controls (collapsible sidebar) │
+│ │ ┌───────────┐ ┌────────────────┐ │
+│ Image canvas │ │ compass │ │ Focal length ⌬ │ │
+│ (custom iced Canvas) │ │ dial │ │ Nick ⌬ │ │
+│ │ │ (view dir)│ │ Tilt ⌬ │ │
+│ - pan: drag / space+drag │ └───────────┘ │ Visibility ⌬ │ │
+│ - zoom: ctrl+scroll, +/-, │ │ Track width ⌬ │ │
+│ pinch; fit / 1:1 buttons │ Distortion k0/k1/x0 [advanced] │
+│ - labels, markers, track │ Projection: ○ normal ● panoramic │
+│ │ [Compute] [Reset] [Show hidden ☐] │
+├───────────────────────────────┴──────────────────────────────────────┤
+│ Status: hover → "Simetsberg (1836 m), distance 12.4 km" · zoom 150% │
+└──────────────────────────────────────────────────────────────────────┘
+```
+
+Design principles:
+- **One window, no modal dialogs for the core loop.** Viewpoint selection becomes an
+ inline searchable overlay (iced `text_input` + filtered list in a popover/panel),
+ replacing the `choose_hill` dialog.
+- **Zoom is optional and non-destructive**: a viewport transform (scale + offset)
+ applied at render time; all hit-testing and label placement in image coordinates.
+ Labels stay screen-space (constant font size) so they remain readable when zoomed.
+- Context menus (Find Peak, Hide/Unhide) via `cosmic::widget::popover` / context-menu.
+- Overlays (viewpoint picker, find-peak, about) as Cosmic **dialogs** (they render
+ inside/over the app window) — no secondary top-level windows.
+
+### 2.2 UI options to explore first (spikes, before committing)
+
+| Option | Pros | Cons |
+|---|---|---|
+| **A. cosmic-toolkit (`cosmic::app`)** — recommended | Native look & feel, app menu, dialogs, popover, theming, Cosmic conventions, active development | API still moving; pin a release/tag |
+| B. Plain iced 0.13 | More stable API, more examples | Not "Cosmic-native"; lose cosmic widgets/menus/theming |
+| C. Slint / GTK4 / Qt | Mature canvas options | Not idiomatic for Cosmic DE |
+
+Exploration tasks (throwaway prototypes, no product code):
+1. **Canvas perf spike**: draw a 6000×4000 JPEG in an iced `Canvas`, pan/zoom at
+ 60 fps (texture upload cost, `wgpu` backend, downscale-on-zoom-out strategy).
+2. **Text spike**: render ~300 hill labels + leader lines via glyphon/iced canvas
+ text; measure frame times; decide label decluttering strategy.
+3. **Input spike**: verify middle-mouse (or map "toggle known" to click + `K` key /
+ double-click if middle-click is unreliable under Wayland), drag-and-drop of image
+ files into a Cosmic window, ctrl+scroll zoom gesture.
+4. **Widget inventory**: sliders, radio groups, menu bar, dialog, popover,
+ searchable list — confirm cosmic-widget coverage; identify what needs a custom
+ canvas widget (compass dial, canvas).
+5. **Packaging spike**: minimal `cosmic-app-library` hello-world, `.desktop` file,
+ `cargo vendor` build without network.
+
+---
+
+## 3. Rust Architecture
+
+Cargo workspace:
+
+```
+gipfel-rs/
+├── Cargo.toml # workspace
+├── crates/
+│ ├── gipfel-core/ # pure domain logic, no UI, fully testable
+│ │ ├── geo.rs # distance/azimuth/nick, earth radius, refraction
+│ │ ├── hill.rs # Hill, Hills, flags, CSV loader, duplicate marking
+│ │ ├── panorama.rs # Panorama: viewpoint, visible/hidden computation
+│ │ ├── projection/
+│ │ │ ├── mod.rs # Projection trait, ViewParams, get_coordinates
+│ │ │ ├── rectilinear.rs
+│ │ │ ├── cylindrical.rs
+│ │ │ └── generated/{rectilinear,cylindrical}_funcs.rs # ← maxima output
+│ │ ├── lsq.rs # Levenberg–Marquardt driver (lmsder-equivalent)
+│ │ ├── metadata.rs # EXIF read + JPEG-comment read/write (gipfel: string)
+│ │ ├── stitch.rs # scan/resample pipeline (nearest + bicubic)
+│ │ └── prefs.rs # distortion profiles (~/.config/gipfel/)
+│ ├── gipfel-codegen/ # maxima scripts + generator (see 3.2)
+│ │ ├── lsq_rectilinear.mac
+│ │ ├── lsq_cylindrical.mac
+│ │ └── expr2rust.mac
+│ └── gipfel-app/ # Cosmic application
+│ ├── src/app.rs # cosmic::Application: Model/Message/view/update
+│ ├── src/canvas.rs # image viewport widget (pan/zoom/labels/hit-test)
+│ ├── src/panels.rs # controls sidebar, viewpoint picker, dialogs
+│ └── i18n/
+├── data/gipfel.dat # unchanged format
+└── examples/ # CLI: stitch, export (clap subcommands)
+```
+
+### 3.1 Keeping the algorithm identical
+
+- Port `Panorama`/`ProjectionLSQ` logic **line-for-line in spirit**: same formulas,
+ same initial-value heuristics (`comp_scale`, alpha-monotonicity fix in the
+ cylindrical case), same fit levels (2/4/7 params), same 100-iteration LM loop.
+- **Derivatives stay symbolic via maxima** (explicit requirement):
+ - Port `expr2c.mac` → `expr2rust.mac` (emit `pub fn mac_x(c_view: f64, …) -> f64`
+ with the same `_1.._n` temporary-variable scheme maxima already produces).
+ - Reuse `lsq_rectilinear.mac` / `lsq_cylindrical.mac` unchanged except for the
+ `expr2c(...)` calls.
+ - Generated `*_funcs.rs` files are **committed to the repo** (like today's
+ generated `.cxx`), regenerated manually by the maintainer via a `just`/`make`
+ target; optionally a `build.rs` that regenerates if `maxima` is on `$PATH`.
+ - Validation: differential test comparing generated Rust vs. original C output
+ bit-for-bit on a parameter grid, and vs. numerical finite differences.
+- **Solver**: two candidates, decide during M2:
+ 1. `gsl` crate (bind to GSL `multifit_fdfsolver_lmsder`) — bit-identical behavior,
+ keeps the C dependency (acceptable: Cosmic is Linux-first).
+ 2. Pure-Rust LM (small problem: n≤2·#hills, p≤7) with QR-based inner steps
+ (e.g. `levmar`-style, `ndarray` + householder QR) — no C deps, needs
+ equivalence testing against the GSL reference.
+ Default preference: **(1) gsl crate** to honor "algorithm stays as it is".
+
+### 3.2 Replacements for C libraries
+
+| C dependency | Rust replacement |
+|---|---|
+| FLTK | `cosmic-toolkit` / iced |
+| libjpeg/libtiff (via FLTK/exiv2) | `image` crate (jpeg, tiff features) |
+| exiv2 (read) | `kamadak-exif` (EXIF + GPS tags) |
+| exiv2 (write JPEG comment) | custom JPEG segment writer: parse markers, replace/insert `COM` (0xFFFE) segment — small, well-defined; keeps the exact `gipfel: …` string format |
+| GSL | `gsl` crate (see 3.1) |
+| Fl_Preferences | `directories` + simple key-file (or `confy`) for distortion profiles |
+| getopt | `clap` (subcommands: `gui`, `stitch`, `export-hills`, `export-position`) |
+
+### 3.3 State & concurrency model
+
+- `cosmic::Application` Elm architecture: `App` holds `AppState` (loaded image,
+ `Panorama` model, viewport transform, UI state).
+- Heavy operations (image decode of large JPEGs, LM fit, stitching) run via
+ `cosmic::task::future` / `tokio` background tasks; messages (`Msg::FitFinished(ViewParams)`,
+ `Msg::ImageLoaded(..)`) return results to the UI — keeps the window responsive
+ (the C version blocks with a wait cursor today; this is an improvement we keep).
+- The 21k-row hill DB is loaded once and indexed (grid by lat/lon) for the
+ "close mountains" pre-filter (the C code rescans linearly).
+
+---
+
+## 4. Milestones
+
+### M0 — UI exploration (spikes from §2.2) — ✅ DONE
+Deliverables (see `../gipfel-spikes/`):
+- `spike-render/` — headless wgpu+glyphon benchmark, **executed** on lavapipe:
+ 24 MP JPEG decode 206 ms, texture upload 60 ms (once), image frame 5.3 ms,
+ 300 glyphon labels 0.8 ms → rendering approach viable
+- `spike-canvas/` — iced 0.14 custom viewport widget (zoom/pan/middle-click
+ markers/300 screen-space labels/sidebar), compile-verified
+- `spike-cosmic/` — libcosmic app with menu bar + key binds, dialog, popover,
+ settings section, `.desktop` file, compile-verified
+- `MEMO.md` — decision memo (toolkit = libcosmic pinned to tag; custom `Widget`
+ viewport; `GSL` crate for `lmsder`; Ctrl tracked via event subscription;
+ middle-click exists in iced 0.14; cosmic's iced fork = 0.14.2 API parity)
+
+Deferred (no display server in spike env): interactive runtime feel, middle-click
+verification under a real Cosmic session, file-chooser choice.
+
+### M1 — Core port (`gipfel-core`, headless) — ✅ DONE
+
+Repo: `~/gipfel-rs` (workspace: `crates/gipfel-core`, `crates/gipfel-cli`,
+`codegen/`, `tests/`). All behaviour is verified against the original C++
+through committed golden files (`tests/gen_golden.sh` regenerates them).
+
+- [x] `hill.rs`: `Hill`/`Hills` + CSV loader (Latin-1, `atof` semantics, both
+ 6-field and 3-field record layouts), `mark_duplicates`, all five sort orders
+- [x] `panorama.rs`: geodesy — `distance`/`alpha`/`nick`/`refraction`/
+ `get_earth_radius`/`get_real_distance`, `mark_hidden` (incl. the original's
+ `fabs(alph_diff > pi/2)` quirk, ported as-is), close/visible bookkeeping
+- [x] `projection/`: `Projection` trait (16 macro entry points, defaults `NAN`
+ like the C++ base class) + rectilinear/cylindrical impls
+- [x] `codegen/expr2rust.mac` + `lsq_{rectilinear,cylindrical}.mac` + `fixup.py`
+ + `regen.sh`; generated `*_funcs.rs` committed (16 + 10 functions)
+- [x] `lsq.rs`: `gsl_multifit_fdfsolver_lmsder` via a minimal hand-written FFI,
+ identical 2/4/7-parameter levels and identical two-pass schedule
+- [x] `metadata.rs`: `gipfel:` JPEG-comment read/write (byte-identical format),
+ EXIF fallback (GPS/focal/make/model), atomic save
+- [x] Golden tests: 200-point function grid, full fit for both projections
+ (agreement to ~1e-15), export output, comment round-trip, real `gipfel.dat`
+- [x] `gipfel-cli`: `export-position`, `export-hills`, `info` — `export-position`
+ is byte-identical to the C binary, `export-hills` matches the C pipeline
+
+Notes / deviations from the C original (all deliberate):
+- `gsl_multifit_fdfsolver_lmsder` is a **pointer** in GSL ≥ 2.7; the FFI models
+ it as `*const` (the C++ code dereferences implicitly). Using the struct form
+ yields `failed to allocate space for multifit solver state`.
+- Upstream C bug fixed in the reference tree: `ImageMetaData::load_image_jpgcom`
+ took `c_str()` of a temporary `std::string`, so `-p` read garbage. The Rust
+ port is correct; the C tree was patched only to produce valid goldens.
+- Upstream C bug not reproduced: `Hill`'s copy constructor does not copy
+ `a_nick`, so fitting a *copy* of a hill fed the solver uninitialised memory.
+ The harness sets `a_nick` explicitly to model real-app behaviour.
+- Rust `Hill` is plain data (no manual `strdup`/`free`); `Panorama` keeps one
+ `Vec<Hill>` plus index lists instead of three aliasing pointer arrays.
+- `rint` → `round_ties_even` (matches C's round-half-to-even); `atof` prefix
+ parsing reproduced exactly.
+
+### M2 — Cosmic app skeleton ✅ DONE (2026-10-25)
+- [x] `cosmic::app` project (`crates/gipfel-app`, libcosmic pinned to rev
+ `430f3d4`), app menu (File/View/Projection/Help), Ctrl+O/S/D/T/V/F/Q
+ (menu `KeyBind` map is display-only → real dispatch via
+ `event::listen_with` subscription)
+- [x] Open image (xdg-portal file dialog via `cosmic::dialog::file_chooser`,
+ feature `xdg-portal`), drag&drop (`Event::Window(FileDropped)`), hill DB
+ load (`--data` / `$GIPFEL_DATA` / XDG + system paths), EXIF/gipfel-comment
+ driven initial state (`apply_image_metadata`)
+- [x] Controls sidebar: custom compass dial widget (center angle), sliders for
+ focal (1–300), nick (−40…20), tilt (−10…10), visibility (0.01–0.1),
+ track width (1–500); lat/lon/height + k0/k1/x0 inputs (on submit);
+ projection radios; show-hidden toggle; zoom/fit buttons
+- [x] Status-bar hover info (name/height/distance, like C's FL_MOVE label)
+- Notes: cosmic fork text API differs from crates.io iced 0.14 — text is
+ measured via `paragraph::Plain::<R::Paragraph>` + `fill_paragraph`, and
+ `cosmic::Renderer` is the *fallback* (wgpu+tiny-skia) renderer. `Point`/`Rectangle`
+ are f32; hill coords stay f64 in core, cast at the draw boundary.
+
+### M3 — Canvas & interaction ✅ DONE (2026-10-25)
+- [x] `ViewportWidget` production widget (`src/viewport.rs`): ctrl+scroll zoom
+ anchored at cursor (image-space anchor math), wheel/drag pan, fit/zoom
+ buttons; single draw pass image→geometry→text
+- [x] Crosses + leader lines (yellow), known-hill flags (red ≤3, green >3),
+ decluttered labels (port of C `set_labels` collision push-up, cached in
+ widget Tree state keyed by a version counter), GPS track polyline with
+ distance-scaled width (C `get_rel_track_width`), hidden hills blue and
+ only drawn with show-hidden on
+- [x] Interactions: left-drag known marker → live move + refit on release
+ (`comp_params`), middle-click **and double-click** toggle known,
+ right-click context dialog (Find Peak / Hide-Unhide), hover highlight
+- [x] Viewpoint & Find-Peak pickers: searchable dialog (name filter, sorted,
+ 300-row cap), Find Peak places the marker at the right-click position
+ exactly like C's `find_peak_cb`
+- [x] Save Image (file dialog → `md_from_state` → `gipfel:` comment write),
+ Screen Dump (re-decode + render markers/labels/track via fontdue → PNG/JPG),
+ Load Track (3-field CSV, `TRACK_POINT` flags, indices remapped by name
+ across reloads)
+- Core change for M3: `Panorama` no longer re-sorts `hills` (keeps insertion
+ order + `alpha_order` index list) so hill indices are stable handles — the
+ C port used stable pointers; golden tests unaffected.
+- Not yet verified interactively (no display in dev env) — needs a real
+ Wayland/X11 session run-through.
+- Field fixes after live testing on real Wayland:
+ - text labels + overlay z-order: overlay recorded in its own graphics
+ layer (`start_layer`/`end_layer`); strong `Plain` paragraph refs kept
+ alive in widget Tree state (renderer only holds `Weak`)
+ - **segfault on marker-drag refit**: the hand-written GSL FFI struct
+ `gsl_multifit_function_fdf` was missing the trailing `nevalf`/`nevaldf`
+ counters (gsl_multifit_nlin.h) — GSL's `fdfsolver_set` wrote 16 bytes
+ past the struct, corrupting `lsq()`'s stack. Fixed; regression test
+ runs the fit on a 128 KB stack (guard-page canary).
+
+### M4 — Stitching & export ✅ DONE
+- [x] Port `ScanImage` (nearest + bicubic) and `Stitch` resampling
+ (`gipfel-core/src/stitch.rs`; bit-for-bit golden tests vs C harness
+ `stitchdump.cxx` for nearest/bicubic, rect/cyl, with and without
+ distortion — sampling on the C 0..=65025 scale, Keys cubic, `rint`)
+- [x] `gipfel-cli stitch -j/-t/-4/-w/-h/-r/-b` parity (C defaults kept:
+ 2000x500, range 0..380 deg); TIFF writer matches C `TIFFOutputImage`
+ (RGBA, deflate, 8/16-bit, alpha 65025), JPEG q90
+- [x] App: File → “Stitch Cylindrical TIFF…” — exports the current image
+ as a cylindrical 16-bit TIFF (bicubic) spanning the lens FOV derived
+ from the fitted projection (edge-angle inverse + vertical Newton),
+ for external stitching tools (Hugin etc.)
+- [ ] Preview of stitched result in-app (optional, not done)
+
+### M5 — Polish & packaging
+- [x] Distortion profiles: `gipfel-core/src/profile.rs` reads/writes the
+ C version's FLTK prefs file (`~/.fltk/Johannes.HofmannATgmx.de/gipfel/
+ DistortionProfiles.prefs`) so profiles are shared with the C binary
+ (verified both directions with a Fl_Preferences probe). Auto-match by
+ camera+focal length on load (comment > profile > zero, C order). App:
+ Distortion section has a profile name field, Save/Load buttons and a
+ stored-profiles dropdown; CLI gains `profiles`/`profile-save`.
+- [ ] Config/data dir handling (`XDG_DATA_HOME`), ship `gipfel.dat`
+- [ ] i18n (de/en), theming (light/dark), HiDPI scaling
+- [ ] `.desktop` file, icon, Cargo vendor for offline builds, CI (fmt, clippy, tests)
+- [ ] Docs: README port, migration notes from the C version
+
+---
+
+## 5. Risks & Mitigations
+
+| Risk | Mitigation |
+|---|---|
+| iced canvas performance with huge images + many labels | M0 spike; tile/downscale pyramid; label decluttering; only draw visible viewport |
+| cosmic-toolkit API churn | pin to a tagged release; isolate UI in `gipfel-app` only |
+| LM solver divergence from GSL reference | use `gsl` crate first; differential golden tests vs C binary |
+| JPEG comment writing corner cases (progressive, large EXIF) | dedicated marker-walker with tests on real-world photos; atomic write via temp file (as C version does) |
+| maxima output differs from C expectations | generated-code diff tests; keep maxima version pinned/documented |
+| Middle-mouse availability on Wayland/touchpads | alternative binding (double-click or key modifier) decided in M0 |
+
+## 6. Explicit non-goals (for now)
+
+- No changes to the mathematical models (refraction, cone-visibility, distortion).
+- No new projection types, no southern-hemisphere bugfix sweep, no GUI stitching mode.
+- No Windows/macOS support; Linux/Cosmic first.
+- No database rewrite (keep flat CSV; in-memory index is internal only).
diff --git a/wasm-plan.md b/wasm-plan.md
index d030b0d..8e73cfe 100644
--- a/wasm-plan.md
+++ b/wasm-plan.md
@@ -1,4 +1,4 @@
-# gipfel-web — plan for a real browser (WASM) version
+# wipfel — plan for a real browser (WASM) version
Status: **planning**. Feasibility spike done and verified on this branch
(`crates/gipfel-wasm`): the full computational core — hill DB, JPEG
@@ -116,11 +116,11 @@ the primary product; the web version is a second front end on the same
## 3. Crate / module layout
-New crate `crates/gipfel-web` (on this branch; `gipfel-wasm` folds into
+New crate `crates/wipfel` (on this branch; `gipfel-wasm` folds into
it or becomes its `demo/`):
```
-crates/gipfel-web/
+crates/wipfel/
src/lib.rs Yew root component, routing between views
src/state.rs app state + reducer (port of GipfelApp fields/Message)
src/canvas_view.rs viewport canvas: bitmap layer + overlay layer,
@@ -208,7 +208,7 @@ spike already retired the two scariest risks (core-in-wasm, fit speed).
|---|---|---|
| Canvas label metrics differ from iced → label layout drift | cosmetic | layout code is width-driven; tune line-height constant on real browser |
| Memory on mobile (4080×3072 RGBA ≈ 50 MB + wasm heap) | OOM on low-end phones | downscale preview bitmap for display (keep full-res only in dump path); measure iOS Safari early (W1) |
-| `image`/`exif`/`flate2` wasm compile surprises | days | all pure Rust; verify in W1 scaffold (`cargo check --target wasm32-unknown-unknown -p gipfel-web`) |
+| `image`/`exif`/`flate2` wasm compile surprises | days | all pure Rust; verify in W1 scaffold (`cargo check --target wasm32-unknown-unknown -p wipfel`) |
| Service worker caching stale DB/app | confusing updates | versioned cache keys, skipWaiting flow with "update available" toast |
| Scope creep toward desktop parity | never ships | non-goals table is binding for v1; stitch/GPX explicitly deferred |
| Two front ends drift apart (desktop fixes not applied to web) | long-term maintenance | shared core + shared golden tests; web-specific tests only for glue |
@@ -218,6 +218,6 @@ spike already retired the two scariest risks (core-in-wasm, fit speed).
## 6. Open questions (decide before W1)
1. **Where does it live?** subdomain (web.gipfel.flpsed.org?) + which static host.
2. **Bundle the full 21k hill DB** (~1 MB gz ≈ 300 KB) or offer regional subsets? Default: full, it fits the budget.
-3. Name: same "gipfel" brand for web, or distinct (e.g. "gipfel web")?
+3. Name: same "gipfel" brand for web, or distinct (e.g. "wipfel")?
4. Does the web version need its own About/privacy page text (all-local processing statement)?
5. Framework confirmation: Yew per A1, or do you want to evaluate Leptos first? (One-day spike would settle it; Yew default stands.)