> I considered every arguments and thought of the pros
and cons of each
> approaches every time new information came along. I
see the advantage
> of the Objet model from a design point of view but I
still think the
> attachments will add more for flexwiki users. On the
other hand, I
> dont
> have a lot of experience with wikis and I want to do my
part the right
> way. So if the administrators of this project ( since
no user
> participates in determining the requirements ) think
the object model
> is the best way to do it and that attachments doesn't
have its place in
> flexwiki please say it now so everybody can stop
wasting time arguing.
My position is that we should try to hammer out a design
here, but that if
you're putting in the time to implement, then you get to
make the final
design call. As an administrator, I would really hesitate to
veto a change
unless I thought it was really detrimental. (Minor point,
the usual
arrangement for who gets to vote is committers, not admins.)
Of course,
whoever works with you to merge your changes (you don't get
commit
permission at first), may send your changes back due to
insufficient unit
tests, noncompliance with project standards, bugs, etc.
>
> > * What's the metadata story? I.e. how do I attach
properties to an
> > attachment?
> > * What's the content model?
> > * How does addressing work? I.e. what are the URLs
for the attachment
> > itself, the attachment management page, and any
other UI associated
> with an
> > attachment?
> >
>
> Here is how I see it:
> From the page Attachments.aspx you can add and delete
attachments and
> also manage the properties for each attachment.
> There could be built-in properties like comment and
description and a
> way to add custom properties that requires a name and
some text.
>
> The addressing could be done through another page like
Attachment.aspx
> (
> no S ). The link could look something like this :
>
Attachment.aspx?topic=Namespace.Topic&filename=attachmen
t.txt
Please no more horrible query string pages. I know it's the
easiest thing to
implement given ASP.NET's sub-par URL handling, but I think
we can do
better. I'd rather see something like this:
http://www.flexwiki.com/default.aspx/Namespace/To
pic/Attachment
Of course, in retrospect, I think we screwed up when we
required the
default.aspx, but that's a story for another day.
So I'm assuming that the content model is "A topic has
zero or more
attachments. Attachments have a name, a byte stream, and
optionally some
metadata." It's the metadata part where I don't quite
understand where this
is going. Is it just a set of name-value pairs? Freeform
wikitext?
------------------------------------------------------------
-------------
Using Tomcat but need to do more? Need to support web
services, security?
Get stuff done quickly with pre-integrated technology to
make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on
Apache Geronimo
http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki
-users
|
