[Pharo-project] First pharo-dev with limited package set
Hi, I've just released the first pharo-dev which contains a limited package set. See http://code.google.com/p/pharo/wiki/Packages for the list of packages we want in Pharo. You can download the image at https://gforge.inria.fr/frs/download.php/7404/pharo0.1-10074dev08.09.2.zip. Here is the list of packages included in this release: AST version 160 eCompletion version 0.90 OB-Enhancements version 0.203 OmniBrowser version 0.416 OmniBrowser-Morphic version 0.52 OmniBrowser-Refactory version 1.0 OmniBrowser-Regex version 0.9.1 OmniBrowser-Standard version 0.346 Pharo packages version 0.3 Refactoring Core version 5 RoelTyper version 0.60 Shout version 3.15-tween.72 ShoutWorkspace version 1-tween.2 VBRegex version 1.9 -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
This sounds good. Now we should be able to see the overrides of ecompletion. Stef On Sep 23, 2008, at 8:20 AM, Damien Cassou wrote:
Hi,
I've just released the first pharo-dev which contains a limited package set. See http://code.google.com/p/pharo/wiki/Packages for the list of packages we want in Pharo.
You can download the image at https://gforge.inria.fr/frs/download.php/7404/pharo0.1-10074dev08.09.2.zip .
Here is the list of packages included in this release:
AST version 160 eCompletion version 0.90 OB-Enhancements version 0.203 OmniBrowser version 0.416 OmniBrowser-Morphic version 0.52 OmniBrowser-Refactory version 1.0 OmniBrowser-Regex version 0.9.1 OmniBrowser-Standard version 0.346 Pharo packages version 0.3 Refactoring Core version 5 RoelTyper version 0.60 Shout version 3.15-tween.72 ShoutWorkspace version 1-tween.2 VBRegex version 1.9
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Damien, Thanks, looks good! Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo. Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace: Workspace Workspace (without colourisation) Shout Workspace There ought to be just one, and in the right place. Cheers, Adrian On Sep 23, 2008, at 09:52 , Stéphane Ducasse wrote:
This sounds good. Now we should be able to see the overrides of ecompletion.
Stef
On Sep 23, 2008, at 8:20 AM, Damien Cassou wrote:
Hi,
I've just released the first pharo-dev which contains a limited package set. See http://code.google.com/p/pharo/wiki/Packages for the list of packages we want in Pharo.
You can download the image at https://gforge.inria.fr/frs/download.php/7404/pharo0.1-10074dev08.09.2.zip .
Here is the list of packages included in this release:
AST version 160 eCompletion version 0.90 OB-Enhancements version 0.203 OmniBrowser version 0.416 OmniBrowser-Morphic version 0.52 OmniBrowser-Refactory version 1.0 OmniBrowser-Regex version 0.9.1 OmniBrowser-Standard version 0.346 Pharo packages version 0.3 Refactoring Core version 5 RoelTyper version 0.60 Shout version 3.15-tween.72 ShoutWorkspace version 1-tween.2 VBRegex version 1.9
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think? -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
On Sep 23, 2008, at 1:58 PM, Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
uh? does not work for me no idea what is a Smalltalk workspace. Let us kill one Shout workspace is always -> Workspace I would put the coloring workspace by default and if people do not like it they fix it.
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
For sake of simplicity I would prefer to have just one menu item. I would put just the workspace without highlighting. Like Bill, I don't need my notes or code snippets in the workspace colorized. Which version of the workspace do people use most often? Adrian On Sep 23, 2008, at 13:58 , Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi, I think the one with color highlighting is the useful one for two reasons: - I would like to discourage people to put text/code that has no structure at all in the workspace. I would say that most of the highlighting problems in the workspace come from not putting a dot at the end of the line. This is a rather small cost to pay for having the colors working. - You can always disable the highlighting for a piece of text by putting it in a comment. Cheers, Doru On Sep 23, 2008, at 2:23 PM, Adrian Lienhard wrote:
For sake of simplicity I would prefer to have just one menu item. I would put just the workspace without highlighting. Like Bill, I don't need my notes or code snippets in the workspace colorized.
Which version of the workspace do people use most often?
Adrian
On Sep 23, 2008, at 13:58 , Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Tue, 2008-09-23 at 14:23 +0200, Adrian Lienhard wrote:
For sake of simplicity I would prefer to have just one menu item. I would put just the workspace without highlighting. Like Bill, I don't need my notes or code snippets in the workspace colorized.
Which version of the workspace do people use most often?
I use Shout not very often but every time I meet the colored workspace it annoys me :) The coloring in the code pane I like. It gives you back a little of this eclipse feeling. Wise chosen colours! :) my 2... Norbert
Adrian
On Sep 23, 2008, at 13:58 , Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
for me the color is really nice because it gives iformation when I type a wrong selector. This is something that you get for free boxes in red means it does not exist box in grey means there is a boxSomething selector Stef On Sep 23, 2008, at 2:23 PM, Adrian Lienhard wrote:
For sake of simplicity I would prefer to have just one menu item. I would put just the workspace without highlighting. Like Bill, I don't need my notes or code snippets in the workspace colorized.
Which version of the workspace do people use most often?
Adrian
On Sep 23, 2008, at 13:58 , Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Tue, Sep 23, 2008 at 2:17 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
uh? does not work for me no idea what is a Smalltalk workspace.
a workspace to write Smalltalk code as opposed to a workspace to write text. At the beginning, the ShoutWorkspace replaced the Workspace but some people complained. That's why there are two workspaces now. I've never used the non-colored workspace: when I want to write text, I enclose it in quotes. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
2008/9/23 Damien Cassou <damien.cassou@gmail.com>:
On Tue, Sep 23, 2008 at 2:17 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
uh? does not work for me no idea what is a Smalltalk workspace.
a workspace to write Smalltalk code as opposed to a workspace to write text.
At the beginning, the ShoutWorkspace replaced the Workspace but some people complained. That's why there are two workspaces now. I've never used the non-colored workspace: when I want to write text, I enclose it in quotes.
I never use any advanced workspace features, only for holding a useful text like todos & doits. So, i don't care if it auto-colored or not, but i'd like to not have a magic like holding temp vars. As for me, a simple text editor and Alt-d/Alt-p shortcuts is more than enough to work efficiently :) Maybe it would be better then to keep two options, but name them differently: - simple text editor - workspace
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.
Damien I would go for the workspace with color. and we should set the pref to have to type | | to declare varaibles. stef On Sep 23, 2008, at 4:30 PM, Damien Cassou wrote:
On Tue, Sep 23, 2008 at 2:17 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
uh? does not work for me no idea what is a Smalltalk workspace.
a workspace to write Smalltalk code as opposed to a workspace to write text.
At the beginning, the ShoutWorkspace replaced the Workspace but some people complained. That's why there are two workspaces now. I've never used the non-colored workspace: when I want to write text, I enclose it in quotes.
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Attached is a fileout of the Shout Workspace class, modified so that the Syntax Highlighting can be toggled from the title bar menu. see attached pic It remembers the last toggle value in a class inst var and uses that as the default for any new workspaces opened. This could easily be changed to be a real Preference setting. You can try it out in the pharo-dev image, just install it and open a new Workspace. What do people think? Cheers, Andy "Adrian Lienhard" <adi@netstyle.ch> wrote in message news:1E60C000-96B4-44FE-95F8-F19B951E0D41@netstyle.ch... For sake of simplicity I would prefer to have just one menu item. I would put just the workspace without highlighting. Like Bill, I don't need my notes or code snippets in the workspace colorized. Which version of the workspace do people use most often? Adrian On Sep 23, 2008, at 13:58 , Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I like it. I think this is a good compromise. Adrian On Sep 23, 2008, at 21:47 , Andrew Tween wrote:
Attached is a fileout of the Shout Workspace class, modified so that the Syntax Highlighting can be toggled from the title bar menu. see attached pic It remembers the last toggle value in a class inst var and uses that as the default for any new workspaces opened. This could easily be changed to be a real Preference setting.
You can try it out in the pharo-dev image, just install it and open a new Workspace.
What do people think?
Cheers, Andy
"Adrian Lienhard" <adi@netstyle.ch> wrote in message news:1E60C000-96B4-44FE-95F8-F19B951E0D41@netstyle.ch ... For sake of simplicity I would prefer to have just one menu item. I would put just the workspace without highlighting. Like Bill, I don't need my notes or code snippets in the workspace colorized.
Which version of the workspace do people use most often?
Adrian
On Sep 23, 2008, at 13:58 , Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project < SHWorkspace .st
<shworkspacetoggle.PNG>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Very good solution. Now we just have to discuss which is the default setting: on or off? :))) Norbert On Tue, 2008-09-23 at 20:47 +0100, Andrew Tween wrote:
Attached is a fileout of the Shout Workspace class, modified so that the Syntax Highlighting can be toggled from the title bar menu. see attached pic It remembers the last toggle value in a class inst var and uses that as the default for any new workspaces opened. This could easily be changed to be a real Preference setting.
You can try it out in the pharo-dev image, just install it and open a new Workspace.
What do people think?
Cheers, Andy
"Adrian Lienhard" <adi@netstyle.ch> wrote in message news:1E60C000-96B4-44FE-95F8-F19B951E0D41@netstyle.ch... For sake of simplicity I would prefer to have just one menu item. I would put just the workspace without highlighting. Like Bill, I don't need my notes or code snippets in the workspace colorized.
Which version of the workspace do people use most often?
Adrian
On Sep 23, 2008, at 13:58 , Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Tue, Sep 23, 2008 at 5:04 PM, Igor Stasenko <siguctua@gmail.com> wrote:
Maybe it would be better then to keep two options, but name them differently: - simple text editor - workspace
I think that is the best solution. For the text editor, Stef also proposed TextPad. What do you prefer? -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
On Tue, Sep 23, 2008 at 9:47 PM, Andrew Tween <amtween@hotmail.com> wrote:
Attached is a fileout of the Shout Workspace class, modified so that the Syntax Highlighting can be toggled from the title bar menu. see attached pic It remembers the last toggle value in a class inst var and uses that as the default for any new workspaces opened. This could easily be changed to be a real Preference setting.
You can try it out in the pharo-dev image, just install it and open a new Workspace.
What do people think?
This is the best solution I think. Please post it to SqueakSource and I will update the Universe. Thank you -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
"Damien Cassou" <damien.cassou@gmail.com> wrote in message news:6ac749c10809232226h45195cecg94ba10fb82421a44@mail.gmail.com...
On Tue, Sep 23, 2008 at 9:47 PM, Andrew Tween <amtween@hotmail.com> wrote:
Attached is a fileout of the Shout Workspace class, modified so that the Syntax Highlighting can be toggled from the title bar menu. see attached pic It remembers the last toggle value in a class inst var and uses that as the default for any new workspaces opened. This could easily be changed to be a real Preference setting.
You can try it out in the pharo-dev image, just install it and open a new Workspace.
What do people think?
This is the best solution I think. Please post it to SqueakSource and I will update the Universe.
Thanks Damien, It's here - http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.3.mcz Andy
Thank you
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
--------------------------------------------------------------------------------
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Yes On Sep 23, 2008, at 10:29 PM, Adrian Lienhard wrote:
I like it. I think this is a good compromise. Adrian
On Sep 23, 2008, at 21:47 , Andrew Tween wrote:
Attached is a fileout of the Shout Workspace class, modified so that the Syntax Highlighting can be toggled from the title bar menu. see attached pic It remembers the last toggle value in a class inst var and uses that as the default for any new workspaces opened. This could easily be changed to be a real Preference setting.
You can try it out in the pharo-dev image, just install it and open a new Workspace.
What do people think?
Cheers, Andy
"Adrian Lienhard" <adi@netstyle.ch> wrote in message news:1E60C000-96B4-44FE-95F8-F19B951E0D41@netstyle.ch ... For sake of simplicity I would prefer to have just one menu item. I would put just the workspace without highlighting. Like Bill, I don't need my notes or code snippets in the workspace colorized.
Which version of the workspace do people use most often?
Adrian
On Sep 23, 2008, at 13:58 , Damien Cassou wrote:
On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo.
Universes and Installer are present. They are not listed because I installed them by hand and not by using Universe. I will fix it for the next version.
Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace
I think we need to keep two entries. Something like 'Smalltalk workspace' and 'Text workspace'. What do you think?
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu) _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project < SHWorkspace .st
< shworkspacetoggle.PNG>_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Wed, Sep 24, 2008 at 9:02 AM, Andrew Tween <amtween@hotmail.com> wrote:
It's here - http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.3.mcz
I think I found a bug : 1- Open a shout workspace 2- Activate syntax highlighting 3- Type any non smalltalk text ('etekjkldg' for example) 4- It appears in red which is correct 5- Deactivate syntax highlighting 6- It is still red which is incorrect -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
"Damien Cassou" <damien.cassou@gmail.com> wrote in message news:6ac749c10809240351o32c3b4f3qff0a9ba9988d851a@mail.gmail.com...
On Wed, Sep 24, 2008 at 9:02 AM, Andrew Tween <amtween@hotmail.com> wrote:
It's here - http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.3.mcz
I think I found a bug :
1- Open a shout workspace 2- Activate syntax highlighting 3- Type any non smalltalk text ('etekjkldg' for example) 4- It appears in red which is correct 5- Deactivate syntax highlighting 6- It is still red which is incorrect
Thanks, I think I've fixed it - http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.4.mcz Cheers, Andy
-- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
--------------------------------------------------------------------------------
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Wed, Sep 24, 2008 at 1:26 PM, Andrew Tween <amtween@hotmail.com> wrote:
I think I found a bug : I think I've fixed it - http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.4.mcz
Indeed, thank you very much. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)
participants (7)
-
Adrian Lienhard -
Andrew Tween -
Damien Cassou -
Igor Stasenko -
Norbert Hartl -
Stéphane Ducasse -
Tudor Girba