On Saturday 22 July 2006 01:53, Nick Grandy wrote:
> Hi there -
>
> A quick note to introduce myself. I just made a bugfix and anticipate
> contributing some more work to SMW.
Great news!
>
> I am setting up a site using SMW. We ran into a problem with inline
> queries, which was previously reported as a bug:
>
> http://sourceforge.net/tracker/index.php?func=3Ddetail&aid=3D1513837&grou=
p_id=3D1
>47937&atid=3D770001
>
> Anyway, I fixed the bug, and will submit the fix. A question: Is it
> better to submit a patch or to commit to CVS? I am new to sourceforge
> (as a contributor).
Well, I am pretty sure that this bug was already fixed in CVS. At least if =
it=20
is the one described here:=20
http://sourceforge.net/mailarchive/message.php?msg_id=3D27994860
I see that I have to clean up the bug reports more eagerly :-/ I will have =
a=20
look at the others this CET afternoon.
>
> I am working with a friend and we are planning on adding to the
> functionality of the inline queries - to add in more advanced options
> like grouping, counting, and summing, and to specify formatting of the
> output. Any pointers to a roadmap for these features? Or shall we
> just code away on our own? :)
OK, that's very nice. We are always looking for contributors. It is also ve=
ry=20
good that you ask before doing major work. Of course, it all depends on how=
=20
much code/new features/changes your are going to do. Do you have any=20
experience with other software projects so far?
One of the main points for inclusion of contributed features into SMW is th=
at=20
the contributors must take responsibility for the code. It is of course fun=
=20
to code some new features, but we also need to be sure that someone will ca=
re=20
for the code when its getting older. Bugs will appear, parts might fail in=
=20
unexpected situations (of which MediaWiki+extensions offers so many), thing=
s=20
that worked fine on your machine will break on some other version of PHP,=20
MySQL, or MediaWiki. We currently have a lot of work with just keeping the=
=20
existing features running.=20
So if you add just some new case: for some existing switch-block, this is n=
ot=20
going to be a big problem for future maintenance. But if you add a couple o=
f=20
hundreds of lines of code, then you need to ensure us that you will take ca=
re=20
of them during their life.
OK, this said, let's come to the inline queries. What exactly do you have i=
n=20
mind? Especially: how should the user write it (we need a very simple synta=
x)=20
and how should it be implemented (we need a very good performance)?
Best regards,
Markus
>
> Thanks,
>
> Nick
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your opinions on IT & business topics through brief surveys -- and earn
> cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Semediawiki-devel mailing list
> Semediawiki-devel@...
> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
=2D-=20
Markus Kr=F6tzsch
Institute AIFB, University of Karlsruhe, D-76128 Karlsruhe
mak@... phone +49 (0)721 608 7362
http://www.aifb.uni-karlsruhe.de/WBS/ fax +49 (0)721 693 717
|