| Re: working on yogurt module |
| by ipwgc on 2010/1/4 15:45:39 SocialNet 2010, is not the same thing that yogurt, 1. The codes were translated from portuguese to english and changed for $socialnet 2. The names and the codes were changed and adapted for the integration of the 11 modules and sections that are participating of the SocialNet project. 3. In SocialNet 2010 doesn't exist any sentence or word related to yogurt. 4. Fallow the turorial from here, I'm working on this tuturial for USERS and for WEBMASTERS http://www.ipwgc.com/socialnet/modules/socialnet/treemenu.php/?tac=3 5. Prove and download from here http://www.ipwgc.com/socialnet/modules/TDMDownloads/ Regards, David Yanez Osses |
| Re: working on yogurt module |
| by aslani606 on 2010/1/4 9:13:13 SocialNet http://www.ipwgc.com/socialnet/modules/TDMDownloads/ develop Yogurt.????!!! when? |
| Re: working on yogurt module |
| by TheShadow on 2009/5/30 22:13:25 Quote: I am sure if somebody offers to pay for a such conversion, there will be developers who will be willing to do it, because they would treat it just as another client engagement. Mowaffaq offered 1000 USD to develop Yogurt. Maybe you guys missed his offer. |
| Re: working on yogurt module |
| by xgarb on 2009/5/26 17:56:33 kudos to people who are putting their time into Yogurt but I think it is missing the point of XOOPS in that you have the core and then you add the bits you want to make the site you want. Some might choose one module over another for a purpose (ie one gallery module might be chosen for it's simplicity or another for features). Sticking loads of functions into one module stops this from working. My opinion is the basic social networking features should be built into the core so modules can call on them as necessary. Functions such as Comments, Ratings, Recommendations, Polls, Member links, Tags, Notifications etc should have basic versions in the core that every module can hook into. These should be written in a way that enables enhanced versions to be dropped in as modules. It's tricky to get the balance right between a streamline core and having basic functionality that all modules have access to. I mentioned this a looooooong time ago but XOOPS for me was always a Community Management System rather than a Content Management System. |
| Re: working on yogurt module |
| by Kiwi_Chris on 2009/5/16 4:37:36 Problem with Elgg is its not much good on a shared hosting environment. Even on the sites that support it advise this. Then it becomes a price thing - because you start needing VPS or Dedicated Hosting. |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|