![]() – I think they can become “first class citizens” with much more access to the behavior of the entire app in a much simpler way. ![]() And I think making the framework-stacks like Foundation, Foundry, etc. In the longer term I hope to build some things into the app that utilize the modular power of Stacks. But that means the first versions will be as simple as they can be. Often apps of this size and complexity take a year or more. In the short term our goal is simply to ship a functional app. Or perhaps you mean “what will users be able to do with Stacks5 that they couldn’t do before”: I don’t want to give away any more ideas than I already have. And that I never have any shortage of new ideas – I don’t ever have writers block when it comes to apps.īut I should probably hold off on detailing exactly what stuff I hope to add. I’ve often given RW lists of stuff that I thought would be low hanging fruit to work on. I think there’s huge potentials for new features. If you mean “what will Isaiah be able to do as an app”: What will you be able to do with Stacks app/stacks that you couldn’t do before as a RW plug-in? If I did write it, I assure you it was to mean something entirely boring – and that the author is well aware of that. As in, “with no docs i had to reverse engineer this 3D printer to get it going!” I definitely used it colloquially to mean “it was hard to figure out” something. I don’t think my occasional use is anywhere near the line. Like any tool it can be used for good and bad stuff. I don’t use it often, but do occasionally. There’s not that many Obj-C devs anymore. It seems clear to me that the implied meaning was purposefully different from the literal meaning – that the author hoped to imply I was doing something surprising and unethical but was actually just normal stuff.īut I’ll add a couple more – more specific details for the nerds:Ĭlass dump is specifically Obj-C – so, harder to classify. I think that’s probably sufficient to debunk this right? There was a lengthy private and public beta – lots of people used including RealMac used it for months before release. Site Images was no different from any of dozens of difficult features in Stacks. Is reading header files “reverse engineering”?ĭid I do something nefarious or otherwise unethical? To be clear, this is exactly the same stuff I’d do when using Apple’s frameworks. Like all RW plug-in devs I read the framework header-files, then make educated guesses about their functions, and do a lot of trial and error. There is no documentation similar to Apple’s docs for their frameworks like AppKit, Obj-C, or Swift. It does have framework “header-files” and a few read-me files. ![]() The RapidWeaver Plug-In API has never had any detailed documentation. was it found out in a surprise discovery: No.And that realmac was kept in the dark from a secret and learned in a surprise discovery. This paragraph implies “reverse-engineered” is nefarious. Many of the sites I create are static and informational.But let me give a more nuanced answer as well. Also, with advances in HTML 5 and CSS 3, there’s also a lot of functionality that can be leveraged just knowing HTML & CSS well, maybe even enough for a simple basic website, which is where I prefer Blocs as you can see your code. I’m re-looking at my use of RW as development does not appear to be progressing. I’ve currently chosen the framework route with RW as frameworks are easy to keep updated although they are also more expensive. You also need to know which stacks your site depends on to work (so you don’t delete it) and if you maintain a number of sites that may well be a whole lot of info to keep track of. Over the years I’ve accumulated such a cruft of stacks with no real way of knowing which are still supported. There is an integrated update feature, but nothing to tell you if your stack contains deprecated code or if the developer has ceased updating. With RW where I have my main experience the stacks management is not the best. It can also add more code to your website if plugin developers are using the same open source code and you might get some occasional quirks where different plugins don’t work well together (although that’s very occasional). The difficulty is that the code behind the plugin is developer dependent. These all have to be purchased separately or in a framework (essentially a group of the plugins this is by far the best route in RW.) For example they can allow you to easily add social icons or media players or parallax views. These are essentially plugins that provide extra functionality when creating your site, they are plug and play. For RW and Blocs a lot of functionality comes through RW stacks and Blocs bricks (although with Blocs I believe you can also see the code).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |