[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-active
Subject:    Discourse categories and active-client
From:       Giorgos Tsiapaliokas <terietor () gmail ! com>
Date:       2013-09-17 9:36:58
Message-ID: CAODYyLYVx4csebX_mVvtsAA9064fNed-JXFTe4ztUOvbj-Vbzg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hello,

one more thing in the TODO list is to add some basic
support for the discourse in the active-client. The goal
is to retrieve all the topics for each category and the first
post of each topic. So we need two requests like
* http://localhost:3000/category/Forum%20for%20Poker17.json
*
http://localhost:3000/t/in-this-forum-you-can-contact-the-author-of-poker17/26.json

I was thinking to create one new job class(DiscourseCategoryJob) which will
contain those two requests
and to keep this class private. We need the AssetJob finished in order to
start
the discourse requests because the AssetJob contains the url of the
category of the asset.
So we can't add any discourse related API to the session class and I don't
think that it makes
sense, from an API pov discourse is an asset specific thing so it should
stay with the asset.
I think that the best place for DiscourseCategoryJob is the AssetOperations
class and
that's why I proposed one job instead of two in order to keep
AssetOperations clean. The c++ users
of libbodega would be able to take the info from a method like
AssetOperations::discourseCategory()
and for the QML users we will add a
AssetOperations::discourseCategoryModel().

What do you think?

-- 
Giorgos Tsiapaliokas (terietor)

terietor.org

[Attachment #5 (text/html)]

<div dir="ltr"><div>Hello,</div><div><br></div><div>one more thing in the TODO list \
is to add some basic</div><div>support for the discourse in the active-client. The \
goal</div><div>is to retrieve all the topics for each category and the first</div> \
<div>post of each topic. So we need two requests like</div><div>* <a \
href="http://localhost:3000/category/Forum%20for%20Poker17.json">http://localhost:3000/category/Forum%20for%20Poker17.json</a></div><div>* \
<a href="http://localhost:3000/t/in-this-forum-you-can-contact-the-author-of-poker17/2 \
6.json">http://localhost:3000/t/in-this-forum-you-can-contact-the-author-of-poker17/26.json</a></div>
 <div><br></div><div>I was thinking to create one new job class(DiscourseCategoryJob) \
which will contain those two requests</div><div>and to keep this class private. We \
need the AssetJob finished in order to start</div><div> the discourse requests \
because the AssetJob contains the url of the category of the asset.</div><div>So we \
can&#39;t add any discourse related API to the session class and I don&#39;t think \
that it makes</div><div>sense, from an API pov discourse is an asset specific thing \
so it should stay with the asset.</div> <div>I think that the best place for \
DiscourseCategoryJob is the AssetOperations class and</div><div>that&#39;s why I \
proposed one job instead of two in order to keep AssetOperations clean. The c++ \
users</div><div>of libbodega would be able to take the info from a method like \
AssetOperations::discourseCategory()</div> <div>and for the QML users we will add a \
AssetOperations::discourseCategoryModel().</div><div><br></div><div>What do you \
think?</div><div><br></div>-- <br><div dir="ltr">Giorgos Tsiapaliokas \
(terietor)<br><br><a href="http://terietor.org" \
target="_blank">terietor.org</a></div>

</div>



_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


[prev in list] [next in list] [prev in thread] [next in thread]