Honestly that approach seems to stifle user input more than anything.
I assume it is referred to as a “Wish” List for a reason, why not aim for the fences? Dare to dream big and fail often, but keep dreaming and more importantly never stop trying.
@Norm has always held the discretion for the direction of the app as the developer. As the developer he should be able too easily assimilate such lengthy requests down into narrower categories. For instance users of an app that is based on the code free principle may not understand that most of those tasks listed above can be sorted down to a few core features of the app.
Without going into specific detail or getting into the facets for either, most could be narrowed down into two core things:
- Support for the complete spectrum of the entire Bootstrap framework.
- More extensive support of the CSS specification and JS support. Both through the GUI and visual tools and via direct in-app preview mode.
Those two would encompass probably 75-85% of that entire list, if done right.
Then it would offer both the ability to accomplish most of those things, but more importantly the ability for users to better help each other to implement them also. So even though the list seems endless or all over the place, in reality it can be paired down to a few well thought out features and abilities at the core of the app. Which I think @Norm fully understands.
You have exceptional design sense @mackyangeles, except for your love of exceedingly small font sizes in your designs ;–). I understand your desire for design and creation to be your core focus. Which is widely the case of most designers who seek out such code-less apps.
I think in general this eventual unrest is common for users of WYSIWYG related apps that are geared towards avoiding code and the underlying source structures of HTML/CSS/JS. Designer types quickly exceed capabilities and/or desperately seek for additional features they see elsewhere in apps or on existing sites they come across.
Because of this, its difficult for visual design centric web apps to be one size fits all especially within the code free space. Users will always be wanting additional features that they themselves don’t have to code.
To be fair to these types of apps, the problem also usually strongly includes the lack of Designers understanding the entry points to add additional things by themselves such as Javascript / CSS / Libraries / etc., either directly in app or worst case scenario via post export edits. These entry points, editing and previewing abilities will hopefully likewise improve as Blocs advances.
I know its no consolation currently but Blocs Version 3, should bring further access for implementing more.
Hopefully to start, offering more built-in Blocs and Brics to chose from. Better access directly in app to entry points for adding, editing and previewing CSS/JS/Libraries/etc. Also through custom Bric’s / Blocs by 3rd party developers (free/paid) as the Developer API emerges and advances further.
If done correctly all of these core things should open up possibilities and opportunities for users to create within Blocs. But also for “user to user” support, helping each other in implementing features and abilities, making it easier to help people implement common things.
So dream on.