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 out there!
Well my motivation is mainly contributing new modules i have written for making drupal "enterprise wiki ready" ( http://wiki.impressive-media.de ). I mainly focus on access rights, WYSIWYG and usability plugins and yet did not publish one of them, while i have written arround 20 modules yet.
Modules like
- "easy node linking" for tinyMCE, round-robbin with linking using nid only
- trashbin implementation,
- tabeedit (seperate edit form with the help of jquery tabs)
- easy image upload
I want to start my official contributions with a filenodes-api and a attach-api. Mainly, this should help people handle complex file types like Image, Video while implementing file-versioning to D6 again. Also providing an easy-to-use api for attaching those complex files to nodes and also embding them into the content. I want to build 2-3 lightweight plugins which hardly will not have any dependencies. Thats the main difference to all current implementations like fileframework, filenode and others. They concentrate on specific content types or specific frontends or backends. This API should be open for any types, backends or frontend.
I hope i can also contribute to the german or russian translation teams also.
I have written some drupal-themes, some are subthemes, some are made from-the-scratch. I think with the time i will contribute them also.
--------
The project i want to start - its finished and attached - is called tagging. Its a replacement for the Drupal-Tag-Interface with his own API, based on a jquery-plugin i wrote. It is very cleanly written, using the FAPI very deeply. It should get highly extensible and has already right now a quite good UX. Tags can be added/removed by mouse or using the autocomplete field. Terms are not seperated by a comma, they are added visually to a list. This gives the user a much better feedback what he has done.
It also exports a hook, hook_suggestion. This plugin enables other plugins to provide terms as suggestion for the current node. This suggestions are shown and the user can choose suggestion by clicking on them.
In the long run, i want to combine this module with extractor and opencalias for generating proper suggestion. It also should provide autotagging by a single click (using the top5 suggestions).
This module should be the successor of active_tags(very bad written, buggy, not extensible, no API), simple_tags(dead), taxonomy_single_tag(well, this plugin has no use, seems more the user misted the core API?). It should provide all the funcionality with the focus on usability and on semantic generation of suggestions using other modules.
So summarized, i want to maintain / create the project "tagging". I want to probably help with modalframe. I want to help Thomas with the german translation and i want to help on media + backporting the D7 fielapi.
best regards
Eugen
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | tagging.tgz | 16.31 KB | eugenmayer |
Comments
Comment #1
eugenmayer commentedPlugin topic:
Goals
Usability
This plugin should provide the ability and usability to tag content. Tagging should be fast as hell, it should be inviting. This is one goal.
On the fly tagging
Tag content without switiching into the edito mode. Provide easy and fast interfaces for those purposes
Extensibility
This plugin should become very stable and use the current Drupal-API by best practice - as much as possible. Its not the primary goal to have the newest features in here as fast as possible, its more about getting them done right.
This should provide the ability to be highly extensible, providing a API for other plugins to reuse the UX-Parts and write better Tagging-tools. One of the primary Tools are semantic suggestions for tags
Tag-Suggestions
This plugin should provide the needed API to let other modules provide suggestions for the most important tags for the current content. The user can be supported to learn, how tagging should work. Also, the user can save a lot of time, because he can simply click on a set of suggested terms, using his mouse. Or remove them - by using his mouse again.
Autotagging
As a long term goal, based on the suggestions, user should be able to have a "autotag this content" button
Installation
You need JQuery and taxonomy, which are both in the Drupal-Core.
Note
You have to activate the Tagging-Widget for every vocabulary
API
hook_tagging_suggestion($vid, $node)
Every time a module gets edited, all registered modules using hook_suggestions are called. They get the current vocabulary ID and the current node as arguments. The hooks are expected to return an array of terms they wont to provide as suggestion.
This way you can include suggestions using opencalais or extractor
theme_tagging_suggestions($suggestions,$vid)
Render the list of suggestions as HTML
theme_tagging_widget()
Render the whole tagging_widget. Give it a new layout or a new UX.
jQuery Plugin: Tagging
$('selectorname-ID').tagging()
Thats pretty anything you need to initialize any input element on the page. You have to provide some wrappers:
The JQuery-Plugin will ge more generic so it can be used more widely. Most of the options which are static right now, should be changeable by options. The current one should be the default
Contributions / Issues
Contributions are highly respected, also feedback on issues or patches.
Feature requests
Please don't hassle with feature request, but please think about them properly, before you file in a issue-ticket. Please provide a basic outline of what the goal or the benefit of this feature would be. Outline the group of user you think is interested in.
Implement them! :)
[Edited by kiamlaluno to remove the tags <hx>]
Comment #2
eugenmayer commentedComment #3
eugenmayer commentedScreenshot
http://www.ubuntu-pics.de/bild/32880/screenshot_008_olIp4Q.png
Comment #4
dave reidHave you thought about joining forces with the Suggested Terms project? Seems like it could be a project that could use some improvement and looks like it's trying to do about the same thing that you've proposed.
Comment #5
eugenmayer commentedWell he is more focusing on a technical-UX - iam not. Iam not gonna let comma-seperated list happen again. Or removing by deling it manually. Suggested terms also provides no API for other plugins to provide suggestions.
It has not proper JS implementation, it does not use elements at all, which is basically the idea of sharing work with others later. He basically dodges all further UX.
Simple as that, my current version is a completely rewrite of his work, if you might want to see it that way. It also provides a JQuery plugin where the UX part can be extenden.
His last checking was October 08, while he still has 13 issues and 5 patches to merge.
Basicaly, join forces with him is downgrading. So i would not go for it
Comment #6
aaron commentedEugenMayer has collaborated in the past with the Media module, and I'm interested in having him on the team for that project. Once his CVS application has been approved, I intend to add him to its list of maintainers, since he's expressed interest in helping continue the backport to d6.
Comment #7
aaron commentedlooking at the specific proposal, i like that it's an api -- hook_tagging_suggestions allows for future extensibility from external sources such as open calais, for example.
Comment #8
aaron commentedthis proposal gets a +1 from me. the code looks sound (other than some suggested improvements in irc that have been addressed) and useful. plus, EugenMayer is already a prolific contributor to the drupal community.
Comment #9
dave reidOk, my concern is that we have some overlap with the initial proposal with current projects. Nothing that shouts 'Hey this would be a duplicate of me!' but still a little overlap. So I'd like for you to make sure that you do your best to document your module in comparison to other taxonomy modules with similar functionality. Document on project page, in module handbook page, on http://drupal.org/node/206734, and http://groups.drupal.org/similar-module-review.
However, my gut says I can't hold this back because of that. There isn't *too* much competition in this area so it should be good to have some fresh development.
Your CVS account has been approved! Please use it responsibly and make sure to think and review whenever you create new projects if you can join an already existing project. Enjoy contributing!
Comment #10
eugenmayer commentedThank you!
Comment #12
avpaderno