PlanetSquires Forums

I wonder is it possible to make FF create Windows 8 GUI. Just for x86 and forget about Windows RT (which is unlikely to survive since MS and OEM are moving to Haswell tablet and away from ARMS).

I do understand PB can only compile for x86.

Is PB compiler a limitation on this in that it can only compile for desktop mode? I mean, is the PB command for creating a window automatically create a desktop window?

I know VB2012, and the upcoming VB2013, still uses .NET for the write behind but uses XAML for the Windows 8 GUI.

VC++ 2012 can compile native write behind code for Windows 8 using its "native compiler" while also uses XAML for the GUI.

If PB is a limitation, then maybe use a C compiler (a number of free ones available and x64 capable too). Will this breath new life and revenue for FF? And not be tied down to PB which doesn't seem to be going anywhere?

And, don't forget to include in the license that prohibit using FF to create a Visual Designer competitor. I know there is already a clause that prohibit creating a derivative.

:) I don't know much about compiler, so dreaming on a Friday afternoon here, after having a late breakfast for lunch.  :)

I haven't put any thought into Windows Metro support. I know that Chris Boss talks about it every now and again for his product. To be honest, I hate that aspect of Windows 8 and I have mine set up to bypass Metro (or whatever it is called these days) and boot directly to the desktop.

Quote
And, don't forget to include in the license that prohibit using FF to create a Visual Designer competitor. I know there is already a clause that prohibit creating a derivative.

There used to be a clause like that in the FireFly EULA but it was removed shortly after FireFly was initially released.

 

Initially, I too dislike the Metro GUI when I tested the preview version. Probably not used to it and probably software I using were still all desktop. (But then I quite like the GUI on iPad and the way it works.) I guess I did not test Windows 8 on the proper hardware. I used my 4:3 (1280x1024) non-touch screen when I should have tested it on a 16:9 (min 1366x768) touch screen. There are limitation with 4:3 screen in that some of the modes are disabled.

My view changed a few months ago when I bought the ASUS VivoBook S300CA.
http://www.asus.com/Notebooks_Ultrabooks/ASUS_VivoBook_S300CA/#overview

It has 16x9 touchscreen pre-loaded with Windows 8 x64. Originally 5 hours battery life, now extended by another 2 hours after I swapped in a SSD.

All the major WinTel PC manufacturers are coming out with similar touchscreen notebook and even all-in-one desktop with touchscreen (think of this as a Windows 8 version of iMac with touchscreen). This is the direction of hardware, so the software OS will have to follow. And Windows 8 is already there.

It is the habit we have that is the obstacle. If you like the tablet and the smartphone GUI, it is like that only bigger. Why I say habit because when I can simply touch the control on screen, I still tend to use the trackpad and click. It takes time. Users can but developers should not wait.

QuoteThere used to be a clause like that in the FireFly EULA but it was removed shortly after FireFly was initially released.

I think you still can put it back:

Quote1.4 The Licensor reserves the right to modify FireFly, and also the terms of this License Agreement at any time, and without prior notification.

Edit to add:
http://www.legalzoom.com/intellectual-property-rights/copyrights/what-are-derivative-works-under

Is it not already covered?

Quote6.1 You may not modify any part of FireFly, including documentation. In particular, de-compilation, reverse engineering or creation of derivative works are expressly forbidden.