GSoc weekly report (Browser Extension Rewrite)
Hi, It's time for weekly report again. Last week. for firefox extension. I * improve firefox's bookmark index * modified the preference dialog ( did a little simplify) * find and fixed a few other bugs ( redirect problem , no-html file problem) And the firefox extension is almost finished . for epiphany extension, I basically work on config-file parse / generate and the index-link feature. What to do next: for firefox extension: code clean-up (remove debug information, check the spelling and words. ) , more test and document . for epiphany extension: add i18n support (using gettext) I think I can finish them in next week . Thanks. -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: GSoc weekly report (Browser Extension Rewrite)
Tao, I was testing the extension, when I noticed this (browser.dump enabled): [beagle] [beaglPref.get beagle.bookmark.active] [Exception... Component returned failure code: 0x8000 (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref] nsresult: 0x8000 (NS_ERROR_UNEXPECTED) location: JS frame :: chrome://newbeagle/content/utils.js :: anonymous :: line 53 data: no] This was getting thrown on the terminal multiple times. Not quite sure what was triggering this. (I didnt set any option explicitly in the preferences) Also, in beagleoverlay.js:writeMetadata, uniddexed should be unindexed (typo). Could you store the URLs as text and not keyword - people should be able to query part of the url too :) ? -- - Debajyoti Bera @ http://dtecht.blogspot.com beagle / KDE fan Mandriva / Inspiron-1100 user ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: GSoc weekly report (Browser Extension Rewrite)
2007/8/7, Joe Shaw [EMAIL PROTECTED]: Hi, On 8/6/07, Tao Fei [EMAIL PROTECTED] wrote: 2007/8/7, Joe Shaw [EMAIL PROTECTED]: I've been playing around with the new extension, and I'm seeing a little inconsistent behavior with it. I wonder if it's related to me having the old Beagle extension installed as well (although I disabled that one). Yes. That's the problem. I use the same preference name beagle.enabled with the old extension. Fixed now. Using beagle.autoindex.active now, the tooltip is also updated. beagle.enabled is wrong word, as it doesn't affect on-demand index. Cool, I'll give it a test later today. We should keep in mind a migration path for the old extension. Ideally the new one will just be a drop-in replacement, and if we could migrate the basic settings (ie, enabled/disabled and a whitelist/blacklist) that would be ideal. Oh. You can import the preference from old extension. ( just open the preference window, and you can see the button). May be I should imported them silently when the new extension is installed. We'll may also want to use the same UUID so that upgrades are done cleanly, if there's no method for obsoleting other extensions. The same UUID ? I guess we only need to modified the install.rdf to change the UUID. -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: GSoc weekly report (Browser Extension Rewrite)
Hey, I've been playing around with the new extension, and I'm seeing a little inconsistent behavior with it. I wonder if it's related to me having the old Beagle extension installed as well (although I disabled that one). Whenever I open a site, I get the little dog icon with an X over it, indicating that it's not indexing that page. The page is not from HTTPS, and when I open the preferences dialog, the Default Action has Index selected. If I click on the icon to toggle it, it gets indexed fine. But I'm not sure why it's not by default. After I toggle the icon, any subsequent page opens are indexed. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: GSoc weekly report (Browser Extension Rewrite)
2007/8/7, Joe Shaw [EMAIL PROTECTED]: Hey, I've been playing around with the new extension, and I'm seeing a little inconsistent behavior with it. I wonder if it's related to me having the old Beagle extension installed as well (although I disabled that one). Yes. That's the problem. I use the same preference name beagle.enabled with the old extension. Fixed now. Using beagle.autoindex.active now, the tooltip is also updated. beagle.enabled is wrong word, as it doesn't affect on-demand index. Whenever I open a site, I get the little dog icon with an X over it, indicating that it's not indexing that page. The page is not from HTTPS, and when I open the preferences dialog, the Default Action has Index selected. If I click on the icon to toggle it, it gets indexed fine. But I'm not sure why it's not by default. After I toggle the icon, any subsequent page opens are indexed. Joe -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
GSoc weekly report (Browser Extension Rewrite)
Hi, It's time for weekly report again. Last week, I work on both firefox and epiphany extension. For firefox: (Thanks for Debajyoti's suggestion) * add referrer url to meta file * index bookmarks (on-demand index or index when close) For Epiphany (now in python): * config file support * basic menu items (index this page , toggle auto-index) * status-bar label And some document. What to do next : * improve firefox's bookmarks index * epiphany extension improvement ( any suggestion?) * solve some usability problem * document You can follow http://beagle-project.org/Browser_Extension 's instructions to install and test the extension, and give me some feedback. Thanks. -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
GSoc weekly report (Browser Extension Rewrite)
Hi, All This has been a relatively slow week. I've basically been looking at the epiphany extension * read more document , read the epiphany source code and some example extension code * write a small script in python ( I take it as an experiment ) http://browser-extension-for-beagle.googlecode.com/svn/trunk/py-epiphany-extension/ The main target of next week, rewirte the epiphany extension ( in C ) * save file to ~/.beagle/ToIndex instead of calling beagle-index-url * add basic config ( index HTTPS or not , exclude /include rule) * UI (It may have some problems as I am not familiar with GTK) Thanks. -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: GSoc Weekly Report (Browser Extension Rewrite)
Hi, On 7/14/07, Tao Fei [EMAIL PROTECTED] wrote: I've noticed that Epiphany can be written in C or in Python. The old extension is written in C. I'm wondering whether it is acceptable if I write the extension in python ? It's a possibility, although I'm not crazy about adding a Python dependency to Beagle (not libbeagle, which already has an optional Python dep for the bindings). It's probably not unreasonable to assume that anyone with Epiphany installed will also have Python, however. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
RE: GSoc Weekly Report (Browser Extension Rewrite)
Hey, a quick note on the subject, I made a haphazard attempt at this rewrite some time ago, and faced the same issue you have now. I think the deciding factor would be your personal experience with the languages. If you have never really worked with C, but have used python, I would think that a well designed and well written python plugin is much better than a haphazard 'My First C' program. The second concern/thought is that a lot of users will leave their browsers open for hours (if not days) at a time, I'm not 100% sure if this applies in the plugin context, but a GC system probably offers some safety net for memory use. Just a quick $0.02, Kevin Kubasik -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Shaw Sent: Friday, July 20, 2007 10:49 AM To: Tao Fei Cc: dashboard-hackers@gnome.org Subject: Re: GSoc Weekly Report (Browser Extension Rewrite) Hi, On 7/14/07, Tao Fei [EMAIL PROTECTED] wrote: I've noticed that Epiphany can be written in C or in Python. The old extension is written in C. I'm wondering whether it is acceptable if I write the extension in python ? It's a possibility, although I'm not crazy about adding a Python dependency to Beagle (not libbeagle, which already has an optional Python dep for the bindings). It's probably not unreasonable to assume that anyone with Epiphany installed will also have Python, however. Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers smime.p7s Description: S/MIME cryptographic signature ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
GSoc Weekly Report (Browser Extension Rewrite)
Hi, all. What I have done in last week , *UI improvement content menu (for status icon and content Area ) / toolbar icon *quick add exclude / include rule *index link (the target can be non-html file) *read some document about Epiphany extension develop What to do next: * more UI improvement for firefox extension * code cleanup , documenting * set up the epiphany extension develop environment and try something I've noticed that Epiphany can be written in C or in Python. The old extension is written in C. I'm wondering whether it is acceptable if I write the extension in python ? Thanks. -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: GSoc Weekly Report (Browser Extension Rewrite)
Sorry for late. I have just got back to home. I got some network problem, and failed to get access to the network until today, There was a recent one opened against the old extension about internationalization. I think that's a pretty important task that this one should address. There is even a patch attached to that bug, although I haven't looked at it closely. Yes,I have notice that. (Debajyoti have cc-ed this bug to me) I'd like to say that the new extension will be translatable. I have put all the UI string in .dtd file and all the javascript string in .properties file (expect some debug information). And I will keep doing that. Thanks. -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: GSoc Weekly Report (Browser Extension Rewrite)
Hi, On 7/6/07, Tao Fei [EMAIL PROTECTED] wrote: I did a little search in http://bugzilla.gnome.org/ , there are some bug reports for the extension. eg, Bug 317605: http://bugzilla.gnome.org/show_bug.cgi?id=317605 In fact , I use status bar label to indicate whether the page is indexed. And use the beagle icon to indicate wheather the beagle is enabled or disabled or in a error state. The icon is global. I think it partly fix the bug . Yeah, I think this is a good idea. I didn't like before that the icon was overloaded for two questions: is this page indexed? and is the extension enabled for this page? Separating those concepts is a good idea. What to do next: * to fix the bugs in bugzilla (or avoid producing them ) There was a recent one opened against the old extension about internationalization. I think that's a pretty important task that this one should address. There is even a patch attached to that bug, although I haven't looked at it closely. Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
GSoc Weekly Report (Browser Extension Rewrite)
Hi, Last week, I * bug fix * test for index (exclude / include filter , status switch ..) * finish the first run-able version . Goals for next week: * remove the jslib related code ( The lib is too big) * add context menu * (if have time ) add index it now button , add filter quick add button. Thanks --- TaoFei (陶飞) ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
GSoc weekly report (Browser Extension Rewrite)
Hi all. Last week, I * move all the literal string in code to beagle.properties , and some help function for i18n * index html page (not enough test) I will have some examination in the next two weeks, so Goals for next week: * more test * remove the jslib realted code ( The lib is too big) * add context menu Thanks. -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
GSoc weekly report (Browser Extension Rewrite)
Hi all. Last week, I * modified the preference code ( remove global vars , documents comments) * some utils function (string operation , wildcard to RE,etc) * filter ( check weather a url should be indexed based on the exclude/include rule) * upload the code to code.google.com (http://code.google.com/p/browser-extension-for-beagle/source) Next week: * do index * some test / log / debug code * i18n (move all the literal string in code to beagle.properties. Thanks. -- Tao Fei (陶飞) My Blog: blog.filia.cn My Summer Of Code Blog: filiasoc.blogspot.com ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
