xojo - impressions after a few months

I’m not the kind of guy who writes reviews. And that is much because it takes time and in most cases I don’t feel that a product deserved that time to be spent on writing something about the product.

That being said, here’s my limited experience with xojo after a few months with it.

I had not heard about xojo until end of Feb this year, when I again searched the Internet for practical ways to develop web applications within a single framework. A few years ago, when I migrated my infrastructure toward Apple, I started developing my apps in xcode. Nice to work with, almost perfect, but not when it comes to web development. PHP was never an option for me, nor was it an option that I invest 25% or more of my time just to keep my development environment up to date. All I wanted was a single platform (for Mac, of course) which allowed me to develop business applications for the web.

In late Feb I searched the Internet again, and found xojo. I don’t remember why I visited the web site, and I cannot say why I haven’t visited it before. It just was outside of my search results (I’m using startpage.com, and avoid Google).

After downloading and installing it, it took only a few hours until I realized that xojo would provide exactly what I missed all the years. I bought some package, with database and web. Lucky me that this pack also allows me to compile console apps (for some daemons that I have created for application housekeeping). What I specifically like very much is the comfort that lies in the fact that xojo allows you to develop your apps in one IDE and compiles something that will then be executed on either the server or the client, depending on where it belongs. It is more or less transparent to the user. Of course it helps if you have a deeper understanding of the concepts of HTML apps and browsers, but anyway, even a kid can now develop web apps.

Xojo cannot do everything, and there’s always room for improvements. I have experienced some of its limitations, but I guess with a bit more experience, I will learn to expand its capabilities with plug-ins. Until now, I have refrained from using plug-ins or writing some, until such time that I feel that I have understood the limitations. I’m still in the mid of a learning curve.

Xojo has caused me waste some hours of time, and this exercise usually with a confusing compiler error message accompanied by a online documentation that does not even touch the topic in question. I remember full well that I went through all the code and my database schema in order to find that root cause for this error message: “Task.getbyID - There are several items with this name and it is not clear which one the call refers to”.

The real reason was that I assigned an Integer value from a database without cast. Instead of
id=rs.field(“id”)
the correct would be
id=rs.Field(“id”).IntegerValue

Instead seeing the obvious, I started looking for ‘several items with this name’. This is where compiler messages can get you. But there are other obstacles in other development environments, too. and it alsways take time to learn about some weird messages from compilers.

Overall, xojo is the best development I have seen in the last few years. Perhaps some compilers are better, or some linkers are better, or some IDE are better. But what counts is the entire package. Xojo simply fits together. You don’t need to become a HTML / Objective C / Javascript / Apache / Database whatever expert just to deliver basic results. And ‘basic results’ is what 99% of any business application is all about.

Cost: I think the cost for the license is fair. I remember some 820 Euros or so for the full license. I could have saved that money and instead using tons of open source stuff. But then I would have invested factors of this amount just for getting to the point where I was after just installing xojo. Time is money, and the xojo license is among the best investments I ever made. (I just checked the price: it’s now 738 € for a limited time…)

Today, most people think that the Internet provides everything for free. However, we should all be cognizant of the fact that these guys are fathers, mothers and they have to feed their families. Nobody eats bits and drinks bytes, and even bitcoins cost real money in the end.

Enough for now. :wink:

Best
Andreas.

Welcome and see you at the next conference :slight_smile:

for the problem with Field()
The DatabaseField class has 6 Operator_Convert methods: Boolean, date, double, Int32, picture and String.

And there is problem: The compiler does not know whether to use int32 or double version. That causes the problem.

Ideally, the compiler would tell me this. :slight_smile:

I think it’s a bug. The compiler could tell you the candidates to help finding the problem.
And it should see that integer is required here.
And maybe DatabaseField class should not have double and integer operators.

Made case 33765 about the problem.

and case 33766 about operator_convert with double/integer.

and 33767 asks for better compiler error.

33765, 33766, 33767 …

Christian, how many requests have you filed throughout the years? 30% of them?

J

I think they are different things.
One Operator_Convert, one compiler error and one DatabaseField class.

I made 865 cases so far which is only 2.5%

[quote=94273:@Andreas Leitzbach]33765, 33766, 33767 …
Christian, how many requests have you filed throughout the years? 30% of them?
[/quote]
Not even close - he’s well behind me - I’ve filed 1500+ :slight_smile:
Last we checked I was #1 and the next top 4 or 5 spots were all engineers

maybe you can present someday a top 5 of the non engineers?

[quote=94279:@Norman Palardy]Not even close - he’s well behind me - I’ve filed 1500+ :slight_smile:
Last we checked I was #1 and the next top 4 or 5 spots were all engineers[/quote]

And i thought you guys get payed to make the list shorter! Hope Geoff doesn’t see this conversation otherwise i guess your bonus is gone with the wind! :wink:

I think the Feedback app is their todo list, so anything they see is filled for to be done later.

Some statistics would be nice.
Like number of open, fixed, merged, etc. cases.

In descending order reports against the IDE are
Greg is within 50 reports of me

Norman Palardy
Greg Olone
<big gap of 500+ reports here>
Christian Schmitz
Geoff Perlman
Robin Laryssen-Mitchell
Tim Jones
Aaron Ballman
Joe Ranieri
Michael Diehr
Bob Keeney
William Yu
Thomas Templemann
Josh Hague
Paul Lefbvre

if you just measure total reports (which would include internal projects, feedback, web site, etc) the top of the list switches as greg also files a lot of reports about feedback & the web site - it puts him ahead of me by about 30 reports

[quote=94287:@Christian Schmitz]I think the Feedback app is their todo list, so anything they see is filled for to be done later.
[/quote]
It is

[quote=94287:@Christian Schmitz]Some statistics would be nice.
Like number of open, fixed, merged, etc. cases.[/quote]
I’m not sure I have the liberty to publish more than the list above

Luckily I’m way behind Norman in the number of bugs assigned to me :stuck_out_tongue: