Because it's not a specific button, it's a simple button used in a specific way Ben On Nov 28, 2011, at 10:44 PM, Ted F.A. van Gaalen wrote:
Hi Ben
All the functionality needed is just to toggle a Display state..
then why use model?
Ted
On Mon, Nov 28, 2011 at 10:32 PM, Benjamin <benjamin.vanryseghem.pharo@gmail.com> wrote: Good idea :)
but imo, it shouldn't be a subclass of SimpleButtonMorph. I think a class representing the model is more appropriate.
Ben
On Nov 28, 2011, at 10:08 PM, Ted F.A. van Gaalen wrote:
Hi there
Thanks for creating version 1.3 !!!!!!!
-loaded Seaside into it. -did a file-in of my Seaside pages Works. OK
Still missing: What I really would like perhaps in the next release a Full Screen Toggle Button somewhere on the desktop..
or -like in the Chrome Internet Browser could you assign it to the F11 key? just an idea.
Don't understand why it is hidden in Settings browser>>appearance>>desktop
(IMHO it does not belong there at all it's not a Setting but just a window state..)
For now, I've solved this by creating this little helper, which, due to my laziness to give it coordinates, drops a button in the upper left corner. Mais enfin, it works.
The class:
SimpleButtonMorph subclass: #FullScreenFlipFlopMorph instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'TGUtil-One'
with just this two instance methods:
initialize super initialize. self target: self; label: 'Full Screen'; color: Color orange; actionSelector: #toggle; openInWorld "target is self is Smalltalk;" toggle Display toggleFullScreen
In a workspace brought to life with evaluating
fullScreenFlipFlop := FullScreenFlipFlopMorph new.
Another question:
As 1.3 uses a cog VM. Is the seasidehosting.st still using a non-cog VM? This would imply a cog VM based image would not run on the seasidehosting?
What happened to the user window styles? (I only see Default and DemoMode) I liked the sort of Aqua themes (I have 7 apples, they are real and in the kitchen :o)
Kind Regards TedvG