Related Posts

Archive

Remote Bookmark : Tools

July 24th, 2007

0 : Why even make this post

If anything becomes popular, or at least noted, with other people, questions will come up of “Why didn’t you use x?”. These are the reasons I chose what I did to begin with.

1 : Languages

PHP: because it’s a lot more popular than Ruby.

MySQL: …do I really have to answer this? The most likely to be supported by PHP. Otherwise, I would have liked to try SQLite.

JavaScript: Cross-browser compatibility. This shouldn’t require plugins. I don’t even know how to code in ActiveX.

2 : Libraries

ezSQL : Unified SQL interface for PHP. The above said, MySQL might not be what people want to use - and I don’t want to:

  1. mess with major rewrites
  2. mess with php’s multipe database interfaces

I’d rather code.

jQuery : will be used in viewing and modifying bookmarks - NOT in their submission. I’m actually used to working with prototype.js, but I don’t need that large of a library for CSS-like selector support, or the simple effects I’ll probably add before this is done. it’s a list of bookmarks - it should load quickly.

3 : Repository

Bazaar : I use CVS at work. I prefer Subversion. But when it comes to setting up a repository version control - with working remote access - I don’t want to deal with it. ‘It’ including servers, URLs, and firewalls. And I don’t need a central repository, as I am using ssh anyway. I just want to have a backup for when I inevitably screw up. That’s where ‘distributed’ versioning comes in handy. Init, add, commit, and go.

4 : Conclusion

Um… this will get more interesting.

-Sud.

Posted in Remote Bookmark |

Comments are closed.

Previous post: Remote Bookmark : Scope

Next Post: Remote Bookmark : Bookmarklet Architecture