Changeset 5283

Timestamp:

06/17/09 23:15:26 (3 years ago)

Author:

szabgab

Message:

move around some documentation

File:

• trunk/Padre/lib/Padre/Document.pm (modified) (3 diffs)

trunk/Padre/lib/Padre/Document.pm

@@ -66 +66 @@
 in that GUI instead of the mime-type only.
 
+I wonder if we should allow the users (and or plugin authors) to
+change the functions or to add new functions that will map
+file content to mime-type or if we should just tell them to 
+patch Padre. What if they need it for some internal project?
+
 A plugin is able to add new supported mime-types. Padre should
 either check for collisions if a plugin already wants to provide
 an already suported mime-type or should allow multiple support
-modules with a way to select the current one.
+modules with a way to select the current one. (Again I think we
+probably don't need this. People can just come and add the 
+mime-types to Padre core.)
 
 Each mime-type is mapped to one or more lexers that provide 
@@ -340 +347 @@
     }
 
-    # Perl 6:   use v6; class ..., module ...
-    # maybe also grammar ...
-    # but make sure that is real code and not just a comment or doc in some perl 5 code...
-
     # Try derive the mime type from the file extension
     if ( $filename and $filename =~ /\.([^.]+)$/ ) {
@@ -403 +406 @@
 
 # naive sub to decide if a piece of code is Perl 6 or Perl 5.
+# Perl 6:   use v6; class ..., module ...
+# maybe also grammar ...
+# but make sure that is real code and not just a comment or doc in some perl 5 code...
 sub is_perl6 {
     my ($text) = @_;