If you need to file a bug to get on the prerelease channel then just spend 10 minutes perusing the docs. You can file a feedback for a simple spelling or grammar mistake. There’s often little bits here and there lacking in the documentation and finding and highlighting them is not only helpful but would net you an easy “bug” report.
2 Likes
The irony
The irony when it relates to API 1.0 is just … I laughed
1 Like
Where does that comes from?
1 Like
I’ve been pondering about the move from web 1.0 to 2.0 in regards to existing proyects. I know that some code is going to require rewriting and I’m kind of OK with it. The one thing I think will bring me more headaches is the move to bigger controls. In the app I’m currently working on I have around 10 pages that have as many controls as ths one:
Every segment loads a container control that has many controls in them. I know that the layout is a bit convoluted but there is a need to display a lot of info on each page.
I spent a huge amount of time workig on the layout for each page, having to make room for bigger controls is something I’m not looking forward at all.
I know I should wait until the thing actually ships and stabilizes before worring on what could be or could not be but I can’t stop thinking about this.
I’d grab it early and test it as much as you can right now
The new Web 2 system is based on Bootstrap. Xojo are using the default theme but you don’t have to go with that one. Either roll your own or find one that has 22 px high controls to match the current design you have.
Is that information made up right? I don’t want you to get in trouble by sharing information protected by privacy laws.
Pretty sure Greg stated as much in his presentations in previous years and this years as well
based on what has been publicly stated by Xojo, My interpretation would have to do a forklift between web 1.0 projects I have to web 2.0. This means, I would have start start fresh with a new web 2.0 project and re-create the web app from scratch and use my web 1.0 code as reference.
question, does anyone remember when we would be able to write xojo plugins using xojo code would be?
1 Like
Very soon in a bit distant future.
3 Likes
later
its shifted down the roadmap again
considering android was expected this year and its # 6 on the list and plugins made in xojo is #9 I would not plan on that feature any time soon
2 Likes
This is based on a post made by Greg on the Xojo Forum
Thanks for your input! That is what I think but of course I will not be sure until I actually test it.
I always thought that Android and interops made more sense to be delivered one after the other. Hopefuly this year.
I’ve never made a Xojo web app (I typically use PHP) but I’m giving it a go at the moment with the prerelease version. I’m essentially making a simple app to allow you to enter source code and then display its tokens and abstract syntax tree. The UI is very simple but it mostly “just works”. I wouldn’t say I’m impressed but I’m not overly disappointed.
1 Like
What I like the best of Xojo web apps is how easy it is to build complex front ends.
I think whats gotten people about Web 2.0 is we’ve been hearing about it for 3+ years as “coming real soon”
If you told your friend you would be over “real soon now” and then showed up next year they’d be a bit put out
So it HAS to be sooner than that
And for what we can see so far “this year” is the timeline I’d expect
1 Like
I was optimistic that 2.0 was going to be released a couple of months after XDC ( xojo.connect or however it’s called). Now days I believe it won’t be released before the end of July. This could mean that neither android or interops will be delivered this year, neither of which are within the topic of this tread but I feel the need to complain 
1 Like
Interops kept getting shoved down the list
And, without a lot of hand tweaking, interops for windows probably would never happen
Same for linux
iOS, Android’s java API’s and macOS provide a very rich set of meta data and that makes it possible to do
Windows and Linux use more “plain C” style apis with lots of void ptr’s and things that convey no intent of how they are going to be used in the called code
And thats a problem as you need to know intent to know which is the right way to pass something via a declare (interops are basically automated declares)
Joe commented on this some time ago
I’ll see if I can find the post
https://forum.xojo.com/conversation/post/385637
there may be others he posted
link to the roadmap in Xojo’s docs since there seems to be NO link in Xojo’s docs