Hi David and others,
- I have noticed that you have removed inst var
'resolver' from
InternalLink, which was there in SW1 and was used to determine the
target of
the internal link. Now there's a setting method for the target
instead. So
is your intention to set this target every time when a link is
created, in
WikiParser>>createLink ? I'm not sure if that's the ways to go because
you
haven't done any preparation for that in WikiParser.
I'm not sure about this yet, basically also because of the confusion if
folders and pages should be unified or not, what would have an impact
on the way of resolving links.
I know a lot of people that do not like the concept of folders and
pages, but personally I like them a lot and that's why I introduced
them into SmallWiki. Most people are confused with the folder, so I
tried to eliminate them in the current version. The comments of Ralph
Johnson made me think again and gives some more reasons to keep them, I
didn't thought of. Maybe we should discuss it this afternoon again ;)
- Some components that aren't implemented yet I
don't understand. For
instance the NearbyLinksComponent, what should be its purpose? When is
a
link "nearby" another? Or the PopularLinksComponent. To implement such
a
thing, we need something like an access counter for every page. Is your
intention to add such a counter?
Hehe ... have a look what your enemy has in their standard wiki
implementation ;)
* NearbyLinksComponent: I thought that this component should list
wiki-structures that have a similar title to the current page.
* PopularLinksComponents: Pages that have been edited a lot in the
past. Of course the thing with the access counter would be an
interesting feature too.
I will have a look at your code now and continue with some coding. Also
I intend to update to the latest version of Seaside.
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org