|
7/26/2007 6:17:20 PM
|
Oppositional
Posts 13
|
The Argotic Syndication Framework is a Microsoft .NET class library framework that enables developers to easily consume and generate web content syndication services from within their own applications.
The framework makes reading and writing syndication data sources in common formats such as RSS, Atom, OPML, RSD, etc. very easy while still remaining powerful enough to handle the myriad of syndication extensions commonly in use today.
Overview of Features
* Consume or generate RSS and Atom syndication feeds.
* Provides an extensible framework for processing any syndication specification extension.
* Support for auto-discovery of syndication services.
* Supports consumption of secure/authenticated syndication services.
* Implements a provider model for storing/retrieving syndication information to your back-end data store of choice.
* Supports conditional get of syndication services data.
The Argotic team is currently looking for developers to contribute to the project! Anyone with in interest in contributing can contact me using this form.
edited by Oppositional on 7/26/2007
|
|
7/27/2007 12:40:57 AM
|
nlinus
Posts 6
|
I'm very glad I signed up to play with this forum. I hadn't seen this on Syndication Framework on codeplex. yay. More stuff with which I can spend endless hours playing while I should be working. I know if I play too much I'll be doing all sorts of "gold plating" on my intranet apps.
|
|
7/27/2007 3:47:21 PM
|
davidbetz
Posts 2
|
That reminds me a bit of my framework: Data Feed Framework, which allows people to create RSS feeds using SQL without forcing them to touch C#. Add an assembly, write a SQL statement, done. My goal was to make it so that no one ever had to edit the code or ever have to touch XML, a text file or anything and I also wanted it to be written in VERY few types as possible so people could understand the code by reading through it in 15 minutes. It was also built with DBAs in mind so that they can write a simple SQL statement and monitor the health of their entire infrastructure.
Docs: http://www.netfxharmonics.com/Materials/DataFeedFramework/February2007/Documentation.htm
Video: http://jampad.net/videos/jampad/DataFeedFramework.asx
SVN: http://svn.netfxharmonics.com/DataFeedFramework/tags/February2007/
|
|
7/27/2007 6:55:46 PM
|
JoshStodola
Posts 3
|
Oppositional, you need to put up some sample code for Argotic, man, seriously!
|
|
7/28/2007 4:39:45 AM
|
michael.minutillo
Posts 28
|
@opositional, what kinds of tasks are you looking for people to do?
|
|
7/30/2007 11:56:47 AM
|
Oppositional
Posts 13
|
Josh,
I hear you man, I hear you. 
David Smith is close to completing a rich example application that utilizes Argotic, it will be posted on his blog when he is finished.
I have figured out how to include help documentation in the compiled help documentation generated using the Sandcastle Help File Builder, and writing documentation, How-To's, and code snippets is the new top priority. I apologize for the sparse documentation, currently you can check out code examples on the Disucssions Forum or view the online API documentation.
|
|
7/30/2007 12:19:39 PM
|
Oppositional
Posts 13
|
Michael,
I am looking for any help people are willing to offer, in whatever role they feel passionate about. I believe that people willing to take on the following roles are currently needed most:
* Code Contributors: People interested in writing code to implement features and/or fix issues in the framework. Features and issues can be viewed at the Issue Tracker.
* Documentation Contributors: People who want to collaborate with the other team members to come up with a list of common use-case scenarios, and then write HTML documentation that provides clear steps on how to solve a use-case/problem using the framework with code examples. The HTML documentation would then be integrated into the compiled help documentation and also made available online.
* Architecture Contributors: People who are willing to do an analysis of the current framework and provide feedback/suggestions on where architectural/performance/API improvements could be made. There is also a need for people to help brainstorm with the other team members on how to best go about implementing some of the more complex features such as Agonstic feed consumption as well as help with how to implement storage of syndication extensions in back-end databases like SQL in as flexible a manner as possible. (Scott, I am looking in your direction...  )
I am sure there are a myriad of ways someone might want to contribute to the project, and would be greatly appreciative of anyone who was willing to take time out of there lives to help improve the framework.
|
|
pages:
1 |
|---|