SpiderBasic 1.00 is out !

[Olby]

The plan is to bring web apps to iOS/Android trough native JS containers, but more on this when SpiderBasic will be up and running

Now this sounds cool! Looking forward to it. Best of luck!

[Danilo]

You can't change the skin at runtime for now, but you can change it in the HTML (look for 'class="claro"').

I replaced the complete include line in the generated HTML:

Code: Select all

<script type="text/javascript" src="... javascript/...../claro.js"></script>

with some other skins. Same for the gadget skins, but it looked a bit ugly.
Will check again, thanks for the hint. I guess changing it at runtime would require some !DirectJS to travel the DOM structure and
change some attributes.

I will change the topic name to identify new alpha, don't worry. It will be probably released on sunday, with tons of improvements.

Nice, can't wait! Thank you very much!

[User_Russian]

Do you plan to OOP in SpiderBasic?
JS supports it and logically add to Basic.

[Fred]

Do you plan to OOP in SpiderBasic?
JS supports it and logically add to Basic.

No. And JS doesn't natively support it either.

[Kuron]

Fred, I hope I won't get slapped for prolonging this discussion. But... With everything you said above, can I ask you why did you decide to go with web development instead of native Android/iOS support in the first place? I personally don't know much about developing websites but if it is so limited in many ways wouldn't you as a company have wider market audience (thus income) by supporting more native platforms? Don't get me wrong, I have seen quite a few nifty pure-web applications (and have been working on one indirectly) but non the less they all stop (brick-wall) when you have to do more trivial tasks which, again, takes us back to native level software application development. Perhaps you might want to share your thoughts on the future of SB: what kind of functionality you plan on adding and what kind of web applications we will be able to build once it hits a certain point of maturity?

Well, yes, the question was whether the restrictions imposed by 'sand-boxed' browser web application format will not limit the full potential of the product.

Fred did mention the other day that there would eventually likely be exporters for Android/iOS.

Here is another way to look at Spider in its current state. If you were to make a game in Spider, you could have the game available to users of almost ANY device/system. Your game could be played by iOS users and you would NOT have to deal with the App store and the licensing and maintain a developer account. The same for Android. Even extremely simple web-based games can be profitable if you license your game properly. I am talking games you could turn out in a day, if not a weekend.

[Karellen]

I'd like to embed a Spider app in a webpage using an iframe. Is it possible to support the #PB_Window_Borderless flag in future versions?

[Num3]

[naw]

I would ask you guys who are concerned about support for PureBasic to consider the larger picture. Fred is currently working fulltime on Fantaisie Software and no matter how many projects he takes on, trust me that's a good thing.

Netmaestro is absolutely right, though Fred may not (want to) admit it, the PB licencing model is almost certainly not sustainable. Lifetime updates is simply to generous - developers have bills to pay like the everyone else, so while SpiderBASIC (I really hate the name BTW) may not get the size of userbase that PB has, it will probably offer a better / more reliable / long term income for Fantaisie software. Even if effort is now to be split between SB & PB, there should be benefits to PB - assuming that there is common code between the two environments. Unfortunately, a promise of lifetime updates for all cannot be reversed - so a new product is required. Simples...

[fsw]

I have some questions:

Is the target audience of SpiderBasic just game developers?
Asking because creating an app for a browser without some sort of database access doesn't make any sense to me.
(apps like WaveMaker come to mind...)

How can a SpiderBasic app be deployed onto an iOS/Android phone/tablet without going through the app store?
My understanding is that it's not possible (might be wrong though...)

Thank you for any clarification, much appreciated.

[Kuron]

s the target audience of SpiderBasic just game developers?

No

How can a SpiderBasic app be deployed onto an iOS/Android phone/tablet without going through the app store?

By using their browser to visit your site/page that has your app running on it.

[Danilo]

Is it possible to use a typical table layout for gadgets in future? Like a common website layout without movable separate windows.

I think so. In PB slang, it would be a borderless window with the size of the whole browser area,
and you have your gadgets, images and canvas stuff within this area.

Programming your own website should be possible with Spider...

[Justin]

Do you plan to OOP in SpiderBasic?
JS supports it and logically add to Basic.

No. And JS doesn't natively support it either.

This is not true. Js support it natively, 'new', 'this' what are they for?

[Danilo]

Just wait and see, guys. It is just the beginning of another product.
No need for it? Just wait for the usual PB update then, like you always did
in the last 10+ years...

[naw]

Just a thought: if SpiderBASIC is to be a Web Client, is there a good reason for a Server only version with all the GUI stuff stripped out with consistent Syntax for various Unix / Windows versions. I'm assuming that the major difficulty for porting PB to different platforms has been the differences in the GUI APIs. A Server-side only version of PB wouldn't need the GUI stuff - just the ability to do handle multiple connections and process text.

[fsw]

Examples do not run on IE9/Win7Pro, only get an empty window.
Had to install FireFox26 to see something.

What I find strange (not being a Web developer) is that there are windows inside the browser.
This means that the browser acts like a desktop (with the possibility to display several windows) and not as a single window (with the possibility to display several gadgets).
Tried to maximize the window in order to fill the browser's client area but doesn't work.

Floating windows inside the browser's client area just doesn't make any sense to me...