Thanks for your answer.I do not know what a DNU is, but your suggestion worked.
What is the procedure now to fix this package?
The Pharo version should remove the dependecy, but the Squeak version might want to keep it. What is the policy in Pharo when this happens?
I'm mailing in the signed license agreement today, and going through the commit procedure described here:
On Mon, Nov 9, 2009 at 10:51, Henrik Sperre Johansen [via Smalltalk]
<[hidden email]> wrote:
You can't, since Player has been removed and there's no plans for
bringing it back..
However, that also means you don't really need those methods, if you
browse them, you can see they're really only utility methods for
setting the properties of a LatexMorph from a player.
So to load in Pharo, you can click the "Browse" button in Monticello,
then right-click the LatexMorph-category and do "Load class category"...
Well, you *should* be able to at least, both squeak and Pharo seem to
give a DNU if the classes don't exist in system yet... So instead,
select the LatexMorph category, select each of the three classes in
turn, and do "Load class" from the right-click menu.
Cheers,
Henry
On Nov 9, 2009, at 10:13 02AM, alesch wrote:
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
View this message in context: Re: [Pharo-project] Satisfying LatexMorph depencies
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project