by Kevin » June 23rd, 2010, 6:56 pm
Hello Johnathan,
Welcome back!
Okay fine! Geez! You win. I'll spill the beans...
As discussed in a couple of other threads already OPML importing is in the works. There are a number of other things which have to happen before this will be implemented. One of them is a dropping of the use of NSXMLParser for a custom parser in C++. Why, you ask? That is because there is indeed work going on for a desktop version of xFeed. Things are already becoming so fragmented with specifics needed for iPhones, iPads and now iPhone4's that It seems the best option to maintain only one code base across all platforms. It is more work now, but in the future, updates should occur more frequently. It would be nice to implement many of the future enhancements now, however, It seems that it is time better spent getting this new stuff out the door.
Now, the timeline for these things is vague, it's going to be. Thats just the way it is. I apologize ..kind of.

Hello Johnathan,
Welcome back!
Okay fine! Geez! You win. I'll spill the beans...
As discussed in a couple of other threads already OPML importing is in the works. There are a number of other things which have to happen before this will be implemented. One of them is a dropping of the use of NSXMLParser for a custom parser in C++. Why, you ask? That is because there is indeed work going on for a desktop version of xFeed. Things are already becoming so fragmented with specifics needed for iPhones, iPads and now iPhone4's that It seems the best option to maintain only one code base across all platforms. It is more work now, but in the future, updates should occur more frequently. It would be nice to implement many of the future enhancements now, however, It seems that it is time better spent getting this new stuff out the door.
Now, the timeline for these things is vague, it's going to be. Thats just the way it is. I apologize ..kind of. ;)