You are not logged in.
Pages: 1
Hello everyone!
Today I just started work on a simple plugin for the tinycm system. So far it's pretty basic. Creation of threads, posts, and so on so forth. It's not perfect, but I just compiled a few features I thought about off the top of my head today, and I haven't really gotten much work done on it yet.
However, for those feeling lucky, I uploaded a tar.gz'd copy of the repository to dropbox, so anyone is free to download it as they please.
I'm also considering licensing issues. Any help there would be very useful! Especially considering what you guys seem to do, I'm not sure how works. But if it does, then that's great. However, for the meantime feel free to post about it here and bash my horrible layout and coding skills. I'll improve the code vastly at a later date. Currently it's horribly unoptimized and may break anything, who knows.
Anyway, link: https://dl.dropboxusercontent.com/u/5579836/forum.tar.gz
Offline
I fixed a few things, and added support for deleting threads (don't know exactly why I didn't do this yesterday, but I was tired so it was done in a hurry).
The layout has also been updated, and looks a bit better now.
Offline
Hi,
I'm so happy to see the first TinyCM contributor \o/
Your code is fine and I would be happy to include it, for that you can have access to the Hg repos repo or you can notify me for update and I will commit.
But before... would you be ok to merge my code with yours since I also coded a forum plugin, it's not in the repos since I wanted more test on it and I miss somr time to do all what I want. You will see that out coding style are similar and I guess you will quickly undertand what I did in my forum plugin.
The few diffs are: more test (if user is the owner of a post, file existance), editing a post and mainly #hashtag. I guess a #hashtag based forum is better than a categorised one and much easier to code. So here is my code:
http://people.slitaz.org/~pankso/projects/forum-pankso.tar.gz
- Christophe
Offline
The base structure of TinyCM is pretty stable (although there's a few hit and miss issues that I'll probably address at a later point, if no one else does), so using it for the very base of any kind of content management seems a logical choice to me. Although there's a few things where I'm not entirely sure which method would be the most ideal.
I'll probably elaborate on the issues that are currently persistent within either tinycm and/or the entire structures of the SliTaz shell/CGI-based systems. Although they're all very much functional, stable, and incredibly useful, there are certain areas where they may have certain slight issues. Again, more on that at a later date.
I'll have a look at the project you coded (I am, in fact, already skimming through most of the code and merging where it seems logical, and/or where the code is most usable and flexible. Certain other variables determine what I merge, but when I'm done, you can of course look through it and decide whether or not my evaluation suits the SliTaz project.
I'm still not really sure about the whole licensing issue, and I'd like to eventually get some feedback on what options would be prefered by you guys.
Offline
Finished merging. Link refers to updated repository.
Please comment and criticize my merge. All feedback is welcome!
Offline
I furtherly updated it to fix a few missing pieces of the puzzle. Here's the hg log:
6:67a87b69aed9:
Fix missing "HG Log" button in forum_tools section.
5:cc0303c53ac7:
Add 'Forum' button to hashtag viewing page.
Fix number of replies in hashtag viewing page.
Update edit and save sections to redirect non-auth users to login page.
Update index page to display only ${count} number of new threads.
Offline
Pages: 1
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]