Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.hi arto,
very cool that you just committed this, i wanted to use the mobile codes module (have you looked at it? maybe your code could live as a submode of mobile codes or be merged with it..?) on my site but then saw that each image is generated via http requests to the nokia server.. this tools would surely integrate perfectly.. unfortunately i dont have much time until next week (preparing for launch) and can't comit any code right now.
anyways if you keep this module separate perhaps a rename of the package to datamatrix would be more readable..
Comments
Comment #1
Arto commentedHi eMPee,
Thanks for the interest, looking forward to feedback if you do make use of the module.
As for your questions: yes, I did look at the Mobile Codes module. While both these modules deal with matrix codes, they have very different approaches and purposes, and I don't think it would necessarily make that much sense to merge them. The Data Matrix API is very much an invisible developer-only, backend infrastructure piece.
As for the name, I pondered it a bit but am not sure I want to change at this point. I specifically chose the project/module name "dmtx" as this is a wrapper for libdmtx, and nothing more. I think the name "datamatrix" should be reserved for something that has wider scope, such as indeed a module that can use a number of backend services, including libdmtx and Nokia's web service, to create matrix codes. Perhaps I'll tackle that someday, and change the name then.
BTW, I looked at your website and it seems we have some congruent interests. You may find these resources interesting:
http://guptaoption.com/8.state_in_a_box.php
http://files.howtolivewiki.com/reykjavik_briefing/
http://vinay.howtolivewiki.com/blog/
http://www.globalswadeshi.net/
Arto
Comment #2
eMPee584 commented> As for the name, I pondered it a bit but am not sure I want to change at this point.
Same reason i filed a name change request with the apache bench module as soon as i saw it appear: the more popular a module gets, the more confusing a name change would be.
> I specifically chose the project/module name "dmtx" as this is a wrapper for libdmtx, and nothing more.
Same reasoning as the ab module author ;)
But think about the situation where you as a site admin look at your modules folder, and every would have two or three letter names. Right now, i got *94* contrib modules on my site (not all active but most). It *does* make a difference if the package folder is called 'ab' or 'apachebench'. Same for this: 'datamatrix' clearly is more descriptive than 'dmtx'. That about the name.
The other thing is, mobile codes provides nothing more than an input filter that uses the nokia server as a backend. This module provides nothing but an API to decode/encode. Would it not make sense to merge these to? This could also live as a submodule of mobile codes but personally i really don't like the exploding number of module's that really would make sense to fuse, it just makes drupal harder to use.
I'm going to open up an issue for the mobile codes module and maybe a solution both beneficial to usability and you're developer's pride can be found ;)
oh and regarding the project: come on join in once it's opened (i.e. tomorrow)!
Comment #3
Arto commentedYou made a compelling argument, and after some further consideration I've therefore bit the bullet and renamed the project and module. Thanks for insisting on it :-)
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.