Manuscript (Case [Issue]22189) UI - Display of fonts in packages pane of System Browser is still broken two years later.

Classic

List

Threaded

♦

♦

Locked 1 message

Pharo Issue Tracker

Reply | Threaded

Open this post in threaded view

♦

♦

|

Manuscript (Case [Issue]22189) UI - Display of fonts in packages pane of System Browser is still broken two years later.

Sven Van Caekenberghe edited Case 22189: Display of fonts in packages pane of System Browser is still broken two years later.: Bug in  UI: 1. Pharo Image  •  You are subscribed to this case Your questions are mostly off topic, it would be better if you asked them in the mailing lists or other community channels. And even then, each issue would deserve a thread. Regarding the Playground, try Command-P followed by either Enter or Command-P, or even by a Command-C. Playground is different, that is the whole point. GT (Inspector and friends) is an exciting alternative rethinking of tools (still evolving/expanding today). Regarding porting important code bases, I would suggest you first get more familiar with all aspects of Pharo (7), the community, the ideas, the goals, the style, etc. And then decide how to proceed. This is a fast moving open source project, not a conservative commercially supported product. (This is not a value judgement) I still remember how I started using VW 1.0 decades ago. It was unlike anything I ever saw/used (apart from a Symbolics Lisp Machine). The biggest lesson however was to "find the shortest path between the current state of the system and your application", aka "don't fight the system but go with it". Priority: 5 – Fix If Time Status: Work Needed Assigned to: Everyone Milestone: Later Go to Case No longer need updates? Unsubscribe from this case. Don't want Manuscript notifications anymore? Update your preferences. A Manuscript case was edited by Sven Van Caekenberghe. Case ID: 22189 Title: Display of fonts in packages pane of System Browser is still broken two years later. Status: Work Needed Category: Bug Project: UI Area: 1. Pharo Image Priority: 5 - Fix If Time Milestone: Later Assigned To: Everyone URL: https://pharo.manuscript.com/f/cases/22189 Your questions are mostly off topic, it would be better if you asked them in the mailing lists or other community channels. And even then, each issue would deserve a thread. Regarding the Playground, try Command-P followed by either Enter or Command-P, or even by a Command-C. Playground is different, that is the whole point. GT (Inspector and friends) is an exciting alternative rethinking of tools (still evolving/expanding today). Regarding porting important code bases, I would suggest you first get more familiar with all aspects of Pharo (7), the community, the ideas, the goals, the style, etc. And then decide how to proceed. This is a fast moving open source project, not a conservative commercially supported product. (This is not a value judgement) I still remember how I started using VW 1.0 decades ago. It was unlike anything I ever saw/used (apart from a Symbolics Lisp Machine). The biggest lesson however was to "find the shortest path between the current state of the system and your application", aka "don't fight the system but go with it". You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.manuscript.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=22189) from this case. _______________________________________________ Pharo-bugtracker mailing list [hidden email] https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker