Issue 7018 in pharo: move unicode initialization methods to the separate package

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo
Status: Accepted
Owner: [hidden email]
Labels: Type-Bug Milestone-2.0

New issue 7018 by [hidden email]: move unicode initialization  
methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

create a new package named Unicode-Initialization and move this methods to  
it:

ByteTextConverter class >> #generateByteToUnicodeSpec:
ByteTextConverter class >> #parseUnicodeOrgSpec:
CombinedChar class >> #loadCompositionMapping
CombinedChar class >> #parseCompositionMappingFrom:
UCSTable class >> #initializeGB2312Table
UCSTable class >> #initializeJISX0208Table
UCSTable class >> #initializeKSX1001Table



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo
Updates:
        Status: HumanReviewNeeded

Comment #1 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

SLICE-Issue-7018-move-unicode-initialization-methods-to-the-separate-package-PavelKrivanek.1


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo

Comment #2 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

I start to really don't like the idea to put methods into a package that  
has no class... hard to understand.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo

Comment #3 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

may be if the package is called InitializeUnicode


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo

Comment #4 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

We have several such packages, eg. Zinc-Patch-HTTPSocket, FamFam-Icons or  
Polymorph-TaksbarIcons. But of course I'm not happy with that. On the other  
hand, to have for example an empty class only with a comment is quite  
strange too.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo

Comment #5 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

If the package as a good name I do not see why this is a problem.
soon we will have metadata per package and a comment that says what it does.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo
Updates:
        Status: WorkNeeded

Comment #6 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

When I merge this, I get a new Unicode-Initialization package, but browsing  
it shows that it is empty


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo

Comment #7 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

issue 7062 must be solved firstly


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo
Updates:
        Blockedon: pharo:7062

Comment #8 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo
Updates:
        Status: FixReviewNeeded

Comment #9 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo
Updates:
        Status: FixToInclude

Comment #10 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

looks good.

Needs postscript:

ScriptLoader new addHomeRepositoryToAllPackages


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 7018 in pharo: move unicode initialization methods to the separate package

pharo
Updates:
        Status: Integrated

Comment #11 on issue 7018 by [hidden email]: move unicode  
initialization methods to the separate package
http://code.google.com/p/pharo/issues/detail?id=7018

in 2.0 453


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker