[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] wiki.sparemint.org as default?



On Wed, Jul 21, 2010 at 4:52 AM, Jo Even Skarstein <joska@online.no> wrote:
> On 07/20/2010 08:10 PM, Miro Kropacek wrote:
>>> adding articles about other projects to this wiki? Personally I don't
>>> like it very much, as these can easily be outdated. A link directly to
>>> the source is better.
>> Well, it depends on how far this wiki should come :) No harm with
>> direct links, of course.
>
> IMO if there is a site dedicated to the project, then link to this site.
> If not, it might be sensible to add a stub/article to the wiki. In this
> case, be sure to keep the stub/article up to date.
>
one of the problems I have found is that unless a project is currently
maintain, most websites are gone in some way, so if there is a link to
the project website, alternative links to download, especially source,
should be provided "just in case". As for up-to-date, until recently,
for Atari ST based stuff that can mean 4-7 years old, but as long as
it is accurate there should not be a problem.

>> Idea behind this is simple -- you've got *MiNT set all up and you want
>> to try some project to compile. You try kernel and libs but you might
>> be interested in other Atari projects as well, so you'll find it
>> here... not all of them have website and/or clear access
>> information...
>
> It's a good idea. Just make sure to keep it updated. Incorrect
> information is worse than no information ;-) To keep maintenance down I
> suggest replacing the login/checkout information with direct links where
> appropriate.
>
> Jo Even
>
This is is the essence of what my points have been, developer related
info in a central (interlinked) place, one that can also link to
offsite stuff as direct reference, even if that info is just
minimalistic (ie. it does not have to be some great large expanse)

Standa's hyp viewer allows use to point directly inside hyp documents,
and he now has  dedicated url for it, so if it is moved later on the
links will not change:
 http://libhyp.atari.org/hypview.cgi?url=http://some.server.net/path/to/hyp/doc.hyp
I have successfully used this with .hyp docs in the current FreeMiNT
CVS, and he has support for various compressed formats (zip,lha,tgz)

I have instigated The Skeleton Project on atariforge, if approved, it
will be used to maintain various skeletons for development purposes,
including but not limited to Makefile with multilib & cross-tool
support, command line skeleton with ARG processing, SH/BASH skeleton
with ARG processing, GEM C skeleton.. etc including documentation
skeletons, and code with requirements for Doxygen & UDO use (at source
level)

I believe it to be possible to provide C source skeletons that are gcc
295, gcc 3/4, Pure C & AHCC compliant.

Paul