61–70 of 125 posts
Having said that, this looks like it could provide a great starting point for development.
Do you see this product as a tool for developers or a tool for designers to publish their creations directly to the web?
I think this is cool, but ultimately I think the dream of developing bespoke applications without having to code will be just that ... at least until the singularity occurs and artificial life forms take over the job of building APIs and presentation layers. Having said that, this looks like it could provide a great starting point for development. Do you see this product as a tool for developers or a tool for designe…
Pagedraw is not a code free tool. It never will be. I don't think it's possible either.
Programming needs to happen in language. Even if you did something like Scratch, (to which I prefer typing,) you still need the arbitrary constructs of language in order to express whatever you want.
Pagedraw is not programming, which only works because we don't really think HTML and CSS are either.
You will absolutely still need to write code to make novel algorithms and custom business logic until the AGI revolution comes. Pagedraw is meant to be used side by side with code implementing the business logic, state management, and anything else novel about your app. Pagedraw will take over more and more of the non-turing complete parts.
Today, with Pagedraw you write state management and API code just like you did before.
> Do you see this product as a tool for developers or a tool for designers to publish their creations directly to the web?
Yes. Both, eventually :) Today the product is a strict replacement for HTML and CSS, so it's something a developer would use to bring designs into production after the designer's done with them.
The robo dog asking me if I know John Connor is giving me bad vibes. I do like what I see. I don't understand the demo though what am I supposed to do?
Did you get to https://pagedraw.io/tutorials/basics? It's the button in the first section that says "Continue to demo"
Is Vue support planned?
yes, depending on demand. Get your friends / coworkers to message us if they need it too
Also I think that Vue is arguably more straightforward than React in the minimal model-view one-way binding use case. Whereas React is a subset of the more general functional reactive programming model and will probably be outpaced at some point with something language-agnostic.
Earlier quoted context omitted.
From the site: "Pagedraw generates code guaranteed to work correctly and in all browsers". So luckily they can fix this issue by re-generating their site, using their site.
Actually, yes! All the parts of our site which are made in Pagedraw are fully cross-browser supported. That includes our landing page, dashboard, and parts of our editor. Based on the feedback in this thread we're going to bump up the priority of this concern. Getting this kind of feedback is why we're doing this launch thread, so we really appreciate it.
- What was the thinking behind supporting only Chrome?
- For a tool that support cross-browser, wouldn't it expected that tool itself runs on multiple browsers?
- Is it really reasonable not to spend time to support multiple browsers and have let possible first adapters to have bad taste with the product ?
I couldn't find any reference to this in your documentation. Exactly how easy and/or do you have any samples projects I can check out? ReactNative would be my primary use and I assume alot of other potential users as well.
I'm a designer, so definitely interested in this. But I got a 'Sorry, our editor is optimised for Chrome' message. I'm using the latest version of Firefox... what features does Chrome have that FF hasn't? I get it's early stage, so you might have just done a blanket 'If not Chrome show message' check. If the latest version of FF can support, I would do a more fine grained check. Will check with Chrome later...
tl;dr: would you like the Electron app instead? It's available at https://documentation.pagedraw.io/electron/
It was tough for us, because we're big believers in the standards-based web. We 100% promise that all the code we generate works across all browsers.
Our editor was almost electron-only, but felt it was better to launch with Chrome + Electron than just Electron. Our editor isn't a normal webpage; it's doing all kinds of crazy nonstandard things webpages shouldn't do. It's only in the browser at all so we can re-use a web engine as our editor's rendering engine, since we occasionally show you snippets of compiled code.
I'm personally really sorry as an engineer that we don't support Firefox, Safari, and other browsers yet. It's on our roadmap :)
>> Another is the ability to easily retarget for AngularJS, Backbone, React Native, and so on by just swapping the compiler backend. I couldn't find any reference to this in your documentation. Exactly how easy and/or do you have any samples projects I can check out? ReactNative would be my primary use and I assume alot of other potential users as well.