yes⦠we have a version of mars that more or less works. Never announced because there is a lot of other âsmall detailsâ to fix, but someone could actually do a desktop app with it. Now⦠there is a difference between making a desktop app and developing with pharo. For desktop apps is most probably that you will want multi windows (even if regularly *you do not use them*, as experience shows: most apps are a single window + dialogs [1][2][3]. Anyway, even if experience says the opposite, you will want many windows). Now, the way pharo is conceived will never work in a multiwindow environment. Just imaging your 10-15 browsers + 5-6 workspaces opened alog with all your other windows (browsers, mails, text editors. terminals, games, whatever). That just cannot work. I have seen this before. People is so used to have it that they *believe* they need it. Just to realise that pharo workflow has nothing to do with a (for example) java workflow. but yes⦠we need to support multiwindows. Not for pharo IDE, but for pharo desktop apps. cheers, Esteban [1] http://upload.wikimedia.org/wikipedia/commons/f/f2/Giancarlo_Mora_Blender_Ju... [2] http://theopensourcery.com/images/javajspEclipse.gif [3] http://microsoft-news.com/wp-content/uploads/2013/10/Outlook-Mail-App-Window... On 15 May 2014, at 22:05, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
2014-05-15 16:57 GMT-03:00 Eliot Miranda <eliot.miranda@gmail.com>:
That single screen has its advantages. It's a very cosy place to be :-)
+1
Plus... unless we got independent process/queues per window (like Smalltalk/X [1]) I don't see the advantage from the development standpoint.
Regards,
[1] In St/X you can kill a window without killing the whole image. Pretty useful if you mess up something :)