Active Topics

 



Notices


Reply
Thread Tools
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#331
Originally Posted by dragly View Post
Wow! There has been a lot of posts since I last checked this thread. I'll try to get in here with some comments on the different topics now
Good to see you about Svenn-Arne



Originally Posted by dragly View Post
I believe our best choice for the future is the Qt Mobility Contacts API. The only problem is that the Qt Mobility library is still only in extras-devel, and thus cannot be moved up to extras testing. Our best choice for now is probably to either use your .vcf workaround or figuring out how to talk directly to the abook.
Yep, sounds like a plan. The QRcode plugin actually works now for mime type file opening, but it would probably be preferable to avoid writing a temporary file.

Originally Posted by dragly View Post
I think we should place it in ~/.config/mbarcode/temp/ since that is where the other config files are stored.
It's not a config file though, it's a temp file that I then open using the mime handlers and delete when mBarcode stops.

Originally Posted by dragly View Post
I think we should add a recommendation for the plugins as well (at least the "official" ones) and go for a enable/disable option in the settings. That is the reason why mbarcode depended on the plugins and not the other way around the begin with, but I think we can solve this with the "Recommended:" option in the control file. I'll check this out later (if noone beats me to it).
Yeah, I wasn't sure how the recommends field is handled by HAM, but that would be the ideal method.


Originally Posted by dragly View Post
Isn't the 1D plugin deprecated? I believe it does nothing but to serve as an example plugin at the moment.
Ah, well in that case I won't try to upload it, but it should still compile if it's an example
 
Posts: 111 | Thanked: 80 times | Joined on Oct 2009
#332
Originally Posted by dragly View Post
However, I don't see the great benefit of switching to QWidget* other than having one class less to depend on (i.e. one less #include), or am I missing something?

To me it seems to be only a question of how one likes to structure the relationships between the plugins and the main app.
Yes, it's primarily a code cleanliness issue. Part of what I'm wanting to do with it is reduce the amount of code needed to create a plugin to an absolute minimum - I think that once mbarcode gets into extras, you'll have a LOT of people creating plugins; it's just to much fun to play with! :-)

Regarding the ISBN plugin, I've requested commit access on the project. As soon as that is approved, I'll commit the plugin.
 
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#333
Regarding the complexity of writing plugins, we really do need to write a HowTo (hint, hint )
 
Posts: 252 | Thanked: 252 times | Joined on Nov 2009
#334
Originally Posted by lardman View Post
Regarding the complexity of writing plugins, we really do need to write a HowTo (hint, hint )
There's my first priority! I knew there was something I was supposed to do before hacking on the main window
 
Posts: 252 | Thanked: 252 times | Joined on Nov 2009
#335
Originally Posted by joshn53 View Post
Yes, it's primarily a code cleanliness issue. Part of what I'm wanting to do with it is reduce the amount of code needed to create a plugin to an absolute minimum - I think that once mbarcode gets into extras, you'll have a LOT of people creating plugins; it's just to much fun to play with! :-)

Regarding the ISBN plugin, I've requested commit access on the project. As soon as that is approved, I'll commit the plugin.
I agree that it is a tad cleaner, but at the same time it might be a bit harder to understand what kind of pointer it is that is really passed down. That is, to understand that you might actually hook onto these signals.

I'm really not sure what would be the best approach here, as you do have a point. Maybe we should have a vote for it when more devs come along?
 
Posts: 111 | Thanked: 80 times | Joined on Oct 2009
#336
Originally Posted by lardman View Post
Regarding the complexity of writing plugins, we really do need to write a HowTo (hint, hint )
I've added a very basic TUTORIAL file in the plugins folder. Want to take a look at it and let me know what you think?
 
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#337
Looks good, might be worth adding some comments (eventually) about hosting multiple sinks in a single plugin, but I guess that's for the advanced tutorial anyway

Thanks for adding the isbn plugin, are you going to push it to the autobuilder too?
 
Posts: 111 | Thanked: 80 times | Joined on Oct 2009
#338
Originally Posted by lardman View Post
Thanks for adding the isbn plugin, are you going to push it to the autobuilder too?
Just did; it should hit extras-devel in a couple of minutes.
 
Posts: 4,556 | Thanked: 1,624 times | Joined on Dec 2007
#339
Hmm I tried installing it but it says it requires libqt4.
__________________
Originally Posted by ysss View Post
They're maemo and MeeGo...

"Meamo!" sounds like what Zorro would say to catherine zeta jones... after she slaps him for looking at her dirtily...
 
Posts: 2,102 | Thanked: 1,309 times | Joined on Sep 2006
#340
Originally Posted by Laughing Man View Post
Hmm I tried installing it but it says it requires libqt4.
mBarcode? Yes, it requires Qt, but Qt should now be installed by default on PR1.2 N900 devices.
 
Reply

Tags
barcode, camera, mbarcode


 
Forum Jump


All times are GMT. The time now is 03:19.