| |
Posted February 5, 2007 - 6:42pm by Erwan Loisant
|
The blog module being pretty stable now, just requiring bug fixes and incremental improvements, I have been spending some time on the “online favorites” part, both on the engine and the user interface. “Online favorites” means social bookmarks websites, such as Delicious.
As you may know, we introduced nested folders to our favorites model; it gave us an opportunity to rethink the way we work with online favorites services, and I ended up rewriting almost everything from scratch. So, what do we have now?
You could rush to your Cormorant build, but the user interface being still in progress I would only recommend it to people who would be able to read the source code. But trust me: the engine is ready, and make the interface is just a matter of deciding what to show and write a few lines of XUL. (Maybe in one week or two, we will have a user interface providing enough functionalities for power users to test it.) In short, here are the major changes:
|
|
|
|
|
|
|
Posted January 20, 2007 - 6:26pm by Erwan Loisant
|
(This extension is for Flock Cormorant only - the unstable version of Flock)
Just after Christmas, I started this extension as an experiment to see how hard it would be to put Flock’s blog editor in the bottom. It turned up to be pretty easy and require very few lines of code: the back-end is the same, as well as the rich editor based on Gecko’s <editor> widget. You can look at the source, it’s pretty short. Get it here: Lower Blog
|
|
|
|
|
|
|
Posted October 7, 2006 - 7:26pm by Erwan Loisant
|
In your comments to Will’s recent post about your Top 10 Issues/Concerns, many of you have expressed remarks or expectations about the blog module. I would like to reassure our early users: while today’s Flock is not specifically “the web browser for bloggers”, the blog editor is still a core feature, under active development. I am determined to push the integration with other Flock’s features to keep it on the top of the publishing tools for the desktop.
Here is a sneak peak at the upcoming blog editor:
A lot of cleanup and improvements have been done in the back-end. Atom 1.0 is supported, it is more extensible, and the compatibility with blogging platforms is still growing. However, a lot can still be done on the user interface to improve bloggers’ experience and productivity. So here is your occasion to give your opinion directly to the guy who will be implementing your pet features. Have no mercy for the current blog editor. What’s missing? What’s wrong or weird? What crazy idea do you have that could make it really cool? Also, for blogging platforms compatibility, don’t forget to help us building the blog compatibility list on the wiki. Have your platform listed here greatly increases the chances to have it supported and tested by our QA team.
Blogged with Flock
|
|
|
|
|
|
|
Posted August 23, 2006 - 2:53pm by Erwan Loisant
|
|
Flock users following this blog probably already know about the mapper extension: that little topbar that Jesse and I hacked over a weekend to accumulate addresses using Yahoo! maps.
Many users were happy with it, but that was not enough for the Flock user and developer Tony Farndon. He prefers Google Maps over Yahoo! Maps; as Open Source software is all about choice, he reused our code to develop an extension using Google Maps.
|
|
|
|
|
|
|
Posted August 21, 2006 - 2:18pm by Erwan Loisant
|
|
Dear Flock users blogging on blogger.com,
As you maybe know, Google just released a beta of their blogging service Blogger. It offers a few new features, and still have some bugs; but more important as many of you noticed it is not supported by Flock’s current release. Indeed, Flock uses the Atom API to publish to Blogger blogs, but Google seems to have dropped support for this API.
The new blog do not advertise any API in their field, and trying to use the good old API link (https://www.blogger.com/atom) did not work. By doing research on the problem today, I discovered a note on the Atom API Documentation announcing that the Atom API will be deprecated in favor to the Blogger/GData API.
|
|
|
|
|
|
|
Posted July 17, 2006 - 5:08pm by Erwan Loisant
|
|
People who used Flock 0.5 probably know that there used to be a maps topbar. It’s no longer present in Flock 0.7, but I packaged it as an extension.
You can download it from here.
The Technorati topbar is also available, here.
technorati tags:flock, maps, technorati, extensions
|
|
|
|
|
|
|
Posted June 6, 2006 - 4:15pm by Erwan Loisant
|
|
In short: the Conversation topbar will not be in Cardinal, grab the extension at the bottom of this page if you need it!
When I joined Flock in early 2005, I brought an extension with me: the Technorati topbar, or Conversation topbar, that I developed as a third party developer while I was still preparing my Ph.D. at Tokyo Metropolitan University. The Technorati topbar is a tool to see “who is talking about the page I am reading”. It was the first Flock-specific extension. Since it was a good example of the direction where the web is going, I received a lot of press for it, had dinner with a guy from Technorati in Tokyo, and I even heard that Bill Gates used it in demo at an internal Microsoft seminar.
|
|
|
|
|
|
|
Posted May 2, 2006 - 3:30am by Erwan Loisant
|
|
As a developer, the question I usually ask to myself when I get interested into contributing in an Open Source project is: where do I start from?
Flock’s source weights several megabytes (40 Mb for the 0.5.x branch), and I understand that it can be impressive for anyone willing to dig into Flock’s source. I will try to give an overview of the source code to help the developers interested in our codebase. It’s not so hard, after all Flock’s source code is separated into several modules of reasonable size.
Prepare your Environment (or not)
First of all, I recommand you to set up a Flock development environement. You should not be afraid of it:
|
|
|
|
|
|
|
Posted May 2, 2006 - 3:30am by Erwan Loisant
|
|
As a developer, the question I usually ask to myself when I get interested into contributing in an Open Source project is: where do I start from?
Flock’s source weights several megabytes (40 Mb for the 0.5.x branch), and I understand that it can be impressive for anyone willing to dig into Flock’s source. I will try to give an overview of the source code to help the developers interested in our codebase. It’s not so hard, after all Flock’s source code is separated into several modules of reasonable size.
Prepare your Environment (or not)
First of all, I recommand you to set up a Flock development environement. You should not be afraid of it:
|
|
|
|
|
|
|
Posted May 2, 2006 - 3:30am by Erwan Loisant
|
|
As a developer, the question I usually ask to myself when I get interested into contributing in an Open Source project is: where do I start from?
Flock’s source weights several megabytes (40 Mb for the 0.5.x branch), and I understand that it can be impressive for anyone willing to dig into Flock’s source. I will try to give an overview of the source code to help the developers interested in our codebase. It’s not so hard, after all Flock’s source code is separated into several modules of reasonable size.
Prepare your Environment (or not)
First of all, I recommand you to set up a Flock development environement. You should not be afraid of it:
|
|
|
|
|
|
|
|
Stay connected via email or RSS, all from the comfort of your Flock.
From the personal blogs of the Flock crew.
Read more
If you love Flock, tell everyone about us!
Get buttons and learn how to Spread Flock.
|
|
Other Systems & Languages
