Any need of metatags module with metatags quick?

Hello,
the Metatags Module is currently not ready, thats all.
Therefore the "Meta tags quick" Module.

There are several things that I miss in metatags_quick. Most notable support for tokens and
meta fields for anything except nodes (taxonomy terms, users, views etc.).
Token support is a big issue (http://drupal.org/node/691078), and once the problem is solved "in general", I will put the solution into the module.
Meta fields for entities other than nodes is work in progress :)
I am eager to have a look on metatags code, and will be of course glad to join efforts, but up to now I feel that your question is purely theoretical - even if we need metatags module, it's hard to expect it coming in the nearest future.
I would prefer to be wrong in my pessimism.
Do you see any lack of functionality in metatags_quick?

"Maybe I'm wrong, but I think with keywords and description fields metatag_quick is a good solution, isn't it?"

Yes it is ! Of corse!

If I may express a wish to the Programmers: Is it possible to restrict the Text Area Field to a maximum Number of characters.
Google accepted only 160 Characters, and if The Text Area not accepted more than it is easy to control.
The Number of Characters should be adjustable by the user.

Only my two cents.
Thanks for the great and easy Module

I personally prefer not to limit meta contents to 160 chars in a code, since that limitation is something internal to Google and can change without prior notice. HTML specification does not limit meta element contents (see http://www.w3.org/TR/html4/struct/global.html#h-7.4.4).
Probably character limit should be tunable

Thats the reason why i prefer the possibility of adaptation by the User!

Most people here seem to miss features from nodewords/meta_tags and the project itself claims to be a temporary substitute or quick 'n' dirty workaround if you like. I am pretty confident that most of us will switch to Meta tags once it's out (even a dev version), so I believe we should turn this issue into a task and rename it to something like "Merge with Meta tags module" or even "Deprecate Meta tags quick when Meta tags is released". I am hesitant to do so though, since it might be considered issue hijacking and cause the wrath of others here, so I leave it up to the maintainer and/or JohnnyX that filed the issue initially ;)

Well, mainly because it will have support for tokens I guess. This feature automates lots of work that otherwise would need 'manual labor'. I cannot think of anything else of importance right now, but that feature alone is a hell of a difference that would make most switch (IMO).

Maybe metatags_quick and metatags should be merged to speed up the development...

Yep! That's already been proposed by Valery (the metatags_quick module maintainer) here.

I was trying to build token support via the Rules module. This is what I have this far:

{ "rules_auto_save_meta_tag_description" : {
    "LABEL" : "Auto save meta tag description",
    "PLUGIN" : "reaction rule",
    "REQUIRES" : [ "rules" ],
    "ON" : [ "node_presave" ],
    "IF" : [
      { "node_is_of_type" : { "node" : [ "node" ], "type" : { "value" : { "page" : "page" } } } },
      { "data_is_empty" : { "data" : [ "node:field-description" ] } }
    ],
    "DO" : [
      { "data_set" : { "data" : [ "node:field-description" ], "value" : "[node:summary]" } }
    ]
  }
}

But it crashes so I'm still looking into it. But this could be a "quick" token integration for this module.

Ah the error was caused because my summary was too long. With less text it doesn't crash.

I have posted my opinion in metatags release date discussion (http://drupal.org/node/1052664#comment-4308322):

I feel that I need to make some disclaimer:)
If you ask me what is the biggest problem of the nodewords module, I will easily name upgrade path.
Every stable release, and often development snapshots had required db schema changes, resulting in more than 30 update functions. It may reflect progress in module development and additions in SEO industry, but it's a huge pain for site owners. I know companies which have stopped upgrading to new versions after 2 or 3 subsequent failed upgrades, and stuck to the last version where their data works correctly.
I think it's very important for the fresh start project like metatags to learn from the experience of its predecessor and be as stable in it's schema definition as possible.
So, I have 2 concerns of decision not to use Field API right now for some reason.
First concern is that right now. In other words, there is intent to use Field API in some future versions? Does that mean another non-upgradable version and need to migrate data?
Second concern is decision not to use built-in, standard drupal mechanism for extending site data. I am afraid that this could lead to changes in module schema (new types of meta tags, changes in existing). However, since Dave has more experience in drupal hacking than me, probably he has an idea how to avoid threat of constant schema changes. So the second concern worries me less.

Yesterday I had very productive chat with David Reid on #drupal-seo
He confirmed that metatags (at least initially) will not be based on Field API for technical reasons.
metatags_quick covers basic requirements of meta tags for drupal pages, and Dave thinks it will be very hard or impossible to implement features that he plans using Field API. On the other hand, he agreed to help with creating migration path for those who will opt to use metatags when it will be released.
I continue to develop module based on Fields API.
Those of you, who, like me, think that Fields API can answer all meta tags needs, can safely stay with metatags_quick. We will help others to migrate from metatags_quick to metatags as safe as possible