Download & Extend
freelinking » Issues

Freelinking 3 - Roadmap

Posted by Grayside on October 24, 2009 at 2:16am
Project:freelinking
Version:6.x-3.x-dev
Component:Miscellaneous
Category:support request
Priority:normal
Assigned:Unassigned
Status:closed (won't fix)
Issue tags:FL3UX

Issue Summary

I am now a co-maintainer on Freelinking, and have a number of thoughts about Freelinking 3. I wanted to start a roadmap discussion with anyone interested before I continue.

Here's to Brainstorming!

  1. Use hooks to create plugins, ala #612434: Freelinking 3 Plugins via Hooks
  2. Cleaner optional integration with Search and Prepopulate
  3. Extending the nodetitle/prepopulate pattern to optionally include taxonomy, book, and og. (Drawing from the linking node.)
  4. Plugins may opt-in to be manipulated by a hook_freelink_alter, allowing other modules to manipulate the link arguments before they are passed to l(), or perhaps a specified rendering function. (Overkill, or a leap forward in broad freelinking usefulness?)
  5. Plugins may opt-in for distinct links in a page to be added to the node links. (Useful?)
  6. Plugins may specify a failover plugin (Search and Create Node failovers becoming full plugins)
  7. Expansion of Wikipedia plugin into a Freelinking_Interwiki module. (As mentioned in eafarris' blog entry.)

All thoughts welcome.

Login or register to post comments

Comments

#1

Posted by arhak on November 2, 2009 at 9:02am

subscribing

PS: please remember to add the link for each topic that gets into its own issue

#2

Posted by Grayside on April 2, 2010 at 11:30pm
Version:6.x-3.0-alpha2» 6.x-3.x-dev
Component:Code» Miscellaneous

Issue Summary

If you wish to discuss these issues at greater length, please post to the linked issue or create one. (Issues forthcoming for all points.) Issues are broken up by the release in which significant work is planned to begin. It is entirely subject to change.

Alpha 4

  1. Failover Action. Plugins may specify what to do in the event a good replacement cannot be generated. (Begun in Alpha3, finished here.)
  2. Plugin Weight. A pre-requisite of Plugin Self-Matching to allow the selection of a dominant plugin for a given syntax.
  3. Enhance Argument Processing from Syntax. For example, [[target|link text|tooltip|nodetype=blog]].
  4. New Plugin: Freelinking File. Provide [[file:filename.txt]] and [[image:image.jpg]]. Carrying forward under the banner of #428706: respect mediawiki-style image tags like [[Image:File.jpg|Text]].
  5. New Plugin: Freelinking Path. Specify an internal path based on path or URL alias. Includes support for configurable "basepath".

Alpha 5

  1. #647940: Syntax Definition by Plugin. Allow plugins to define the rules by which they will be found in the text.
  2. #634348: Configuration by Input Format. Right now Freelinking is either enabled or disabled in a given Format.
  3. #650364: Token-enhanced Links
  4. #650382: Freelinking Developer Plugin Pack

Unknown Target/Ongoing

  1. #621180: Building a Robust FL3 API. Support deep Freelinking enhancement from separate modules & projects.
  2. #621586: Theming support. Currently discussing how to enable modules to theme themselves without overriding the theme function.
  3. #633842: Wysiwyg API Integration
  4. #634332: Freelinking UI. Create an Admin UI for creating and overriding Freelinking plugins. This discussion may start here and move to a separate project.
  5. #465360: freelinks don't redirect properly when content is cached and #637842: FL3 DB Functionality Through Separate Project to address that.

#3

Posted by arhak on November 2, 2009 at 5:37pm

Next time open the issue with a title but without the list of topics/sub-issues, then write the roadmap as the first comment which will remain editable as long as nobody replies to it. Otherwise start or join a group (groups.drupal.org) for discussing freelinking roadmap.

#4

Posted by arhak on November 3, 2009 at 1:31am

8. Theming support #621586: Theming support

#5

Posted by arhak on November 19, 2009 at 11:30pm

it should be reconsider whether an FL3 release should have DB or not

+1 to not have DB support in FL3's core
+1 to have FL3 "bug free" #465360: freelinks don't redirect properly when content is cached

would the middle point be #637842: FL3 DB Functionality Through Separate Project?

#6

Posted by Grayside on November 20, 2009 at 5:10pm

I have been wondering whether Freelinking DB should be a separate project or a sub-module, I will continue discussion in #637842: FL3 DB Functionality Through Separate Project.

#7

Posted by AlanAtLarge on July 17, 2010 at 7:47am

subscribing

#8

Posted by juampy on August 14, 2011 at 10:16am
Status:active» closed (won't fix)

Closing. Issue left alone. As suggested in comment #3, further discussions should be taken in a group at groups.drupal.org.

nobody click here